Chat now with support
Chat with Support

Stat 6.1 - Upgrade Notes

Configuring the Web Client to use HTTPS

This functionality is supported for the standalone platform only. It is recommended that you first configure the Stat™ Central Agent without https and validate that it can be started and is functional before switching to https.

To configure the Web Client to use HTTPS:
1
Shut down the agent.
2
Delete <STAT_HOME>/app/standalone/tmp.
3
Obtain a keystore with a self-signed certificate from your security group or build it yourself, if authorized.
You need to know the keystore file name and the password that opens it.
4
Once you have the keystore, move it to <STAT_HOME>/app/standalone.
5
Do the following to turn on SSL:
a
Go to <STAT_HOME>/app/ standalone/ standalone-full.xml and turn on SSL.
b
Look for this block in the file:
<!--
<security-realm name="SslRealm">
<server-identities>
<ssl>
<keystore path="keystore.jks"
relative-to="jboss.server.config.dir"
keystore-password="changeme"/>
</ssl>
</server-identities>
</security-realm>
-->
c
Uncomment the block by moving the trailing --> to the end of this line:
<!--
d
Modify the keystore-password to equal the password written in the keystore.
e
Modify the path to match the keystore file name (in the example above, change only the keystore.jks to the appropriate name).
The edits will now look like this:
<!-- -->
<security-realm name="SslRealm">
<server-identities>
<ssl>
<keystore path="statagent.keystore"
relative-to="jboss.server.config.dir"
keystore-password="password"/>
</ssl>
</server-identities>
</security-realm>
f
Look for this block in the file:
<!--
<https-listener name="default-ssl" socket-binding="https" security-realm="SslRealm" max-post-size="999999999"/>
-->
g
Uncomment the block by moving the trailing --> to the end of this line:
<!--
The edits will now look like this:
<!-- -->
<https-listener name="default-ssl" socket-binding="https" security-realm="SslRealm" max-post-size="999999999"/>
At this point users can log in as http://servername:8080/stat or as https://servername:8443.
6
Do the following to have the port location automatically change from 8080 to 8443 when logging into the Stat Web Client:
a
Stop the agent.
b
Move <STAT_HOME>/app/standalone/deployments/stat-agent.ear to a location outside of the <STAT_HOME> folder for backup purposes.
c
Locate the stat-agent.ear file in stat-agent-https.zip from this distribution package and copy it into <STAT_HOME>/app/standalone/deployments.
7
Restart your agent.
8
Access the Stat Web Client as before.
If you input http://servername:8080/stat, you will automatically be directed to the secure location of https://servername:8443/stat.
9
If you have a firewall, make sure that port 8443 is open on the firewall.

Modifying connection pool idle time

This feature allows the site to define the length of time before the Stat™ Central Agent connection pool times out database connections. The default is 15 minutes. However, Java® could take up to twice as long to actually disconnect from the environment.

* 
IMPORTANT: Shorter times could adversely affect agent performance.
To modify pool idle time:
1
Open <STAT_HOME>/config/stat.properties.
2
Locate the parameter CONNECTION_IDLE_TIME=15, and modify the time.
3
Stop and restart the agent.

Installing multiple servers on the same host

Stat™ currently supports installing up to four Stat Central Agents on the same host machine (provided there are no port conflicts). Additional Stat Central Agents are installed basically the same way as the first server, except you will need to install the additional servers to separate directories, define separate system variables, modify the startup files, and assign the servers to different port profiles.

If you need to install more than four servers on the same computer, contact Technical Support.

* 
NOTE: You can install only one Stat Central Agent per Stat Repository.
To install an additional Stat Central Agent on the same machine:
1
Unzip the contents of stat_standalone.zip to a location on the host computer that is different from the location where the first Stat Central Agent is installed. This location will be referred to as <STAT_HOME2>.
2
Create an environment system variable called STAT_HOME2 with a value of <STAT_HOME2> from the above step.
3
Do one of the following, depending on your platform:
•
For Windows, go to <STAT_HOME2>\app\bin, open the file standalone.conf.bat in a text editor, and locate the line:
set "JAVA_OPTS=-Xms64M -Xmx512M -XX:MaxPermSize=256M -Dstat.home="%STAT_HOME%" -Djboss.socket.binding.port-offset=0 -Dmail.mime.charset=ISO-8859-1 -Duser.language=en -Duser.region=US -Dcom.microsoft.tfs.jni.native.base-directory="%STAT_HOME%/tfs-native-dlls" -Doracle.jdbc.V8Compatible=true"
Change the value "%STAT_HOME%" to "%STAT_HOME2%".
Change the value for –Djboss.socket.binding.port-offset from zero to a proper value.
•
For Unix, go to <STAT_HOME2>/app/bin, open the file standalone.conf in a text editor, and locate the line:
JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Stack=true -Dstat.home=$STAT_HOME -Djboss.socket.binding.port-offset=0 -Dmail.mime.charset=ISO-8859-1 -Duser.language=en -Duser.region=US -Dcom.microsoft.tfs.jni.native.base-directory=$STAT_HOME/tfs-native-dlls -Doracle.jdbc.V8Compatible=true"
Change the value $STAT_HOME to $STAT_HOME2.
Change the value for –Djboss.socket.binding.port-offset from zero to a proper value.
The value for port-offset assigns a new offset of ports to the second Stat Central Agent. See Resolving port and firewall conflicts for information on choosing the proper value for port-offset and resolving port conflicts.
4
Continue installing the second Stat Central Agent the same way you did the first using the Configuration Assistant.
Remember that the URL address for the Configuration Assistant will be different for the second Stat Central Agent. After changing the port-offset, the default URL for the second Stat Central Agent is calculated by adding the port-offset to 8080. For example, if port-offset is set to 1, then the URL is http://localhost:8081/stat-config.

Upgrading the Stat Central Agent on Oracle WebLogic 11g/12c

As an alternative to the recommended Stat® standalone platform, the Stat Central Agent can be installed on Weblogic 11g or Weblogic 12c (v12.1.x-v12.2.x).

To install the Stat Central Agent on Oracle WebLogic 11g/12c:
1
If you have not already done so, install Oracle® WebLogic 11g/12c.
The directory where you install Oracle WebLogic 11g/12c will be referred to in this document as <WL_HOME>. You do not need to set this variable.
2
Create a directory for named Stat in <WL_HOME>/user_projects/domains/.
For a second Stat Central Agent, against a test repository you may create a new folder called <WL_HOME>/user_projects/domains/stat2 (or stat580).
* 
NOTE: If you have port conflicts, see Resolving port conflicts (WebLogic).
3
Create a variable named <STAT_HOME> and set it to <WL_HOME>/user_projects/domains/stat.
4
Create a variable named <STAT_HOME2> and set it to <WL_HOME>/user_projects/domains/stat2.
5
On the installation media, go to the \stat_server\weblogic folder and unzip the file stat_weblogic.zip to <WL_HOME>/user_projects/domains/stat.
* 
NOTE: For Unix®, use the -a modifier to unzip the file.
Next, you need to edit the startup script, startWebLogic.cmd located in <STAT_HOME>, so that it references the correct wlserver folder name and (optionally) a different JDK version.
You will need to modify <WL_HOME>/user_projects/domains/stat/startweblogic.cmd (or startweblogic.sh for Unix) to point <STAT_HOME> to this new location or to the variable described in step 4.
6
Edit startWebLogic.cmd as follows:
a
Locate the wlserver_10x or wlserver_12x folder under <WL_HOME>, and edit the line
set WL_HOME=%STAT_HOME%\..\..\..\wlserver_10 so that it specifies the exact folder name (e.g., wlserver_10.3).
* 
NOTE: WebLogic names its wlserver folder based on the minor release installed.
b
(Optional) If you want to use a different 1.7.x JDK version, replace the line JAVA_HOME=..\..\..\jdk160_45 with the path for the new version (e.g., JAVA_HOME=C:\j2sdk170_25).
7
If you are using WebLogic 12.2.x and on Windows, edit the following lines in <WL_HOME>/user_projects/domains/stat/bin/setDomainEnv.cmd:
Locate the lines:
call "%WL_HOME%\common\bin\commEnv.cmd"
@REM For 12.2.x
@REM call "%WL_HOME%\..\oracle_common\common\bin\commEnv.cmd"
and change to:
@REM call "%WL_HOME%\common\bin\commEnv.cmd"
@REM For 12.2.x
call "%WL_HOME%\..\oracle_common\common\bin\commEnv.cmd"
8
If you are using WebLogic 12.2.x and on Unix, edit the following lines in <WL_HOME>/user_projects/domains/stat/bin/setDomainEnv.sh:
Locate the lines:
. ${WL_HOME}/common/bin/commEnv.sh
# For 12.2.x
# . ${WL_HOME}/../oracle_common/common/bin/commEnv.sh
and change to:
# . ${WL_HOME}/common/bin/commEnv.sh
# For 12.2.x
. ${WL_HOME}/../oracle_common/common/bin/commEnv.sh
9
Copy the files wlclient.jar, wljmsclient.jar, and wlthint3client.jar to each workstation where the Stat Windows Client is installed.
These files are located in <WL_HOME>/wlserver_10.x/server/lib.
* 
NOTE: For Oracle applications only, wlclient.jar and wljmsclient.jar must also be copied to each Stat Oracle Agent. See Upgrade the Stat Oracle Agent (Oracle E- Business Suite only).
10
Do one of the following:
•
If on Windows, run script startWebLogic.cmd.
•
If on Unix, run the script, startweblogic.sh.
The first time you start the WebLogic server, the Stat Connection is not properly defined; therefore the server will start with errors.
11
Configure Oracle WebLogic 11g as follows:
a
Start the WebLogic console from the following url: http://hostname:8081/console
b
Login with the following credentials:
•
Username = weblogic
•
Password = irv200038stat
c
Click Services and then Data Sources on the Domain Structure tree on the left side of the screen.
d
Click StatDataSource on the Configuration tab.
e
Click the Connection Pool tab.
f
Click Lock & Edit on the upper left portion of the screen.
g
Depending on whether your Stat database is on Oracle or SQL Server®, update the DriverName, Properties, and URL.
For Oracle:
•
Update the URL with your Stat Database information:
•
@hostname:port:sid
•
DriverName="oracle.jdbc.driver.OracleDriver"
•
Properties=v$session.program=STAT
•
Set the user name to STAT and set the password for Stat user.
For SQL Server:
•
Update the URL with your Stat repository information:
•
//hostname:port/databasename
•
DriverName="net.sourceforge.jtds.jdbc.Driver"
•
Properties="user=STAT
•
appName=”Stat Central Agent on WebLogic"
•
URL="jdbc:jtds:sqlserver://hostname:port/databasename"
•
If your connection needs more properties such as instance or sll, append those properties to the Properties value.
For example if you are running the Stat Database as an instance, append the instance name to the Properties value:
Properties="appName=Stat Central Agent on WebLogic;instance=instance name"
If you enabled ssl on Stat Database server running SQL Server, append the ssl name to the Properties value:
Properties="appName=Stat Central Agent on WebLogic;ssl=require"
h
Click Save on the Connection Pool tab.
* 
NOTE: If you do not receive a green check mark with the message Settings Updated Successfully, edit your savings and try again.
i
Click Activate Changes under Lock & Edit.
You should receive a green check mark with the message All Changes have been activated. No restarts are necessary.
j
Log out of the console.
12
Restart the Stat Central Agent.
13
Open a browser and go http://hostname:8081/stat (host name is the name of the machine where weblogic is installed).
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating