Stat 6.3 - Upgrade Notes

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>.

Create an environment system variable called STAT_HOME2 with a value of <STAT_HOME2> from the above step.

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%" -Dstat.server.config.file=%SERVER_CONFIG% -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 -Dstat.server.config.file=$SERVER_CONFIG -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.

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.

Testing database and server connections

If you have already defined any database and server connections in the Stat® Repository, you can test the connections in the Stat Web Client after installing the Stat Central Agent.

TIP: You can also test connections in the Stat Windows Client. For more information, see the Stat System Administration Guide, Chapter 4, General Maintenance Tables.

You can validate the connections between the Stat Central Agent and all the databases, ftp file servers, email servers, and VCM repositories currently defined in the Stat Repository.

NOTE: To test connections in Stat Web, you must be assigned the user class right, Agent Test Connect.

To test database and server connections:

Open your internet browser and go to the URL address for Stat Web.

•

http://localhost:8080/stat

Enter your assigned user name and password and click Login or press <Enter>. This logs you into the Stat Web Console.

Click Menu in the Stat Web Console menu bar. This opens the Stat Menu window.

Click Test Connect.

Select the tab for the type of database or server you want to test.

Select the checkbox for each database or server you want to test.

Click Test Connect.

The Stat Central Agent attempts to connect to each database or server you selected and then reports the results in the Status column. Connection errors are reported with a brief description of the problem.

Upgrade the Stat Oracle Agent (Oracle E- Business Suite only)

The following upgrade must be performed on each Oracle® E-Business Suite server that will be managed by Stat®. You must re-install each Stat Oracle Agent defined on each server before you can upgrade them from 5.8.x to 6.3.0. To save time, however, it is recommended that you first create a backup of the stat.conf file for each agent. This way, after installing a Stat Oracle Agent from the 6.3 installation cd, you can reuse your 6.1.0 configurations by copying configuration data from the archived stat.conf file to the new stat.conf file you just installed.

To use the Oracle E-Business Suite functionality supported by Stat, install and run the Stat Oracle Agent after you have installed and run the Stat Central Agent.

To upgrade a Stat Oracle Agent:

Stop all instances of the agent.

Execute the following command for each environment:

statctl.sh -e <envCode> -e stop

Backup or archive the stat.conf file for each Stat Oracle Agent you want to upgrade.

Create a user to own the Stat Oracle Agent files. All Oracle E-Business Suite OS accounts on the server must have read and execute permissions for these files.

The new Stat user account should exist in the same group as the Oracle E-Business Suite accounts (e.g. dba). The Stat Oracle Agent can also be installed under a different directory with the existing Stat user account.

Locate the stat installation directory: <stat installation cd>/stat_agent_ora_apps.

Copy the stat_ora.zip from the Stat installation CD to the Oracle E-Business Suite server.

Unzip stat_ora.zip in the home directory of the new user created for the Stat Oracle Agent files, or the new directory if the existing user is being used. This directory is referred to below as STAT_HOME.

Set <STAT_HOME> and PATH in the profile of each Oracle E-Business Suite user (e.g. applmgr) on the server.

Example:

$>STAT_HOME=/home/stat

$>export STAT_HOME

$>PATH=$PATH:$STAT_HOME/bin

Set STAT_JAVA_HOME to the JVM that should be used by the Stat Oracle Agent.

Example: $>STAT_JAVA_HOME=/opt/java/18

The Stat Oracle Agent requires Java® 8. It will be necessary to install a suitable version if one is not already available.

TIP: You can also use the Java version supplied in your E-Business environment. The version used by Stat should be equal to or greater than the one in the E-Business environment.

For users migrating file and schema objects that include diacritic marks (umlauts, tildes, breves, etc.), do the following to change the character set to ISO-8859-1:

Open statctl.sh.

Locate the line:

-Dfile.encoding=UTF-8 \

Modify it to:

-Dfile.encoding=ISO8859-1 \

If the Oracle E-Business database is configured with Oracle NDE (Network Data Encryption), include the encryption type of RC4_256 in sqlnet.ora of the database server.

For each Stat Oracle Agent that you are upgrading, open the stat.conf file that you backed up/archived in step 2, copy the configuration settings you want to re-use, and paste them in the corresponding 6.3.0 stat.conf file located in <STAT_HOME>/conf.

In each 6.3.0 stat.conf file, specify the new Stat 6.3.0 configuration settings as needed.

See Additional changes for information on new Stat 6.3.0 configuration parameters.

If you are running a Release 12 Oracle E-Business Suite environment, do the following:

Open the stat.conf file located in <STAT_HOME>/conf and add the parameter <env>.env.CONTEXT_NAME:<sid_hostname>.

The following parameters are no longer required in the stat.conf file for 12.x and are automatically read from the Context File. If they are present in stat.conf, they will override the values read from the Context File.

<env>.env.APPL_TOP

<env>.env.ORACLE_HOME

<env>.env.TWO_TASK

<env>.env.APPLFENV

<env>.env.CONTEXT_FILE

<env>.env.APPLTMP

<env>.env.APPLREP

<env>.env.LD_LIBRARY_PATH

(Optionally) If you experience issues with compiling RDF Report File, you may need to patch the reports.sh file located in $ORACLE_HOME/bin directory:

•

Open the reports.sh file located in $ORACLE_HOME/bin/ and locate the following:

TNS_ADMIN=$ORACLE_HOME/network/admin