Stat 6.1 - Upgrade Notes

Chat now with support

Before starting the Stat Central Agent Resolving port and firewall conflicts Stopping the Stat Central Agent Configuring the Stat Central Agent as a Windows service Installing DB2 support for the Stat Central Agent Configuring the Stat Central Agent character map Setting up support for AES256 ciphers for SFTP Configuring the Web Client to use HTTPS Modifying connection pool idle time Installing multiple servers on the same host

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

Configuring the Stat Central Agent as a Windows service (WebLogic) Installing DB2 support for the Stat Central Agent (WebLogic) Resolving port conflicts (WebLogic) Deleting data sources and connection pools (WebLogic) Support IMAP via TLS

Testing database and server connections

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

Assign user class rights

Appendix: Upgrade Checklist

Deleting data sources and connection pools (WebLogic)

Data sources and connection pools are automatically deleted from your environments by default each time you first access the datasource upon a new re-start. This allows the agent to re-connect to an environment even if its connection configuration (such as usernames, encrypted passwords, and port numbers) has been changed, or if the environment has been moved to a new location.

Clearing connection information is controlled by a parameter in the stat.properties file. If for any reason you want to persist connection information after re-starting the agent, open the stat.properties file in <STAT_HOME>/config and change the value of the parameter ClearDatasource to No.

If you change this setting, it is your responsibility to manually delete the datasources if you make any configuration changes (such as usernames, encrypted passwords, and port numbers). To resolve this issue you need to log in to the WebLogic web console interface and manually remove the unwanted data source and its corresponding connection pool from the WebLogic configuration file. After deleting the unwanted data source and connection pool, the Stat® Central Agent will re-create the data source and connection pool with the updated connection information the next time the data source is accessed.

To delete Oracle WebLogic data sources and connection pools:

Go to http://localhost:8081/console, where local host is the name of the machine the agent is running on and login using the same username and password used to start WebLogic.

Click Services and then Data Sources on the Domain Structure tree on the left side of the screen.

Click Lock and Edit on the Change Center box in the upper left of the screen.

Select the Data Source to be deleted.

IMPORTANT: Do not remove StatDataSource. This is the Stat Repository configuration.

Click Delete.

You will be prompted to validate the datasource you have selected for deletion. Click Yes.

Click Activate Changes on the Change Center box in the upper left of the screen.

Validate that you receive a message with a green check mark: “All changes have been activated. No restarts are necessary”.

Support IMAP via TLS

In order to support Imap via TLS, the Stat Central Agent needs at least version 1.4.5 of Java® Mail.jar, which you can obtain from Oracle at: http://www.oracle.com/technetwork/java/javamail/index-138643.html.

To implement mail.jar:

Extract mail.jar from the .zip file and place it at \WL_Home\jdk160_21\jre\lib\ext (jdk162_21 may be different on your site).

Restart the Stat Central Agent if it is running.

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 book, Stat 6.1.0: System Administration, 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.

•

On the standalone platform: http://localhost:8080/stat

•

On Weblogic: http://localhost:8081/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.1.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.1 installation cd, you can reuse your 6.0.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/17

The Stat Oracle Agent requires Java® 7 or 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 \

For users that have installed the Stat Central Agent on Weblogic, locate the files wlclient.jar, wljmsclient.jar, and wlthint3client.jar in <WL_HOME>/wlserver_10.x/server/lib and copy them to the ~/lib/weblogic directory for each Oracle Agent that you have set up.

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.1.0 stat.conf file located in <STAT_HOME>/conf.

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

See Additional changes for information on new Stat 6.1.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