Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Stat 6.3 - Upgrade Notes

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.
Open <STAT_HOME>/config/
Locate the parameter CONNECTION_IDLE_TIME=15, and modify the time.

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.
Unzip the contents of 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.
For Windows, go to <STAT_HOME2>\app\bin, open the file standalone.conf.bat in a text editor, and locate the line:
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:
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.

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

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.

Backup or archive the stat.conf file for each Stat Oracle Agent you want to upgrade.
Locate the stat installation directory: <stat installation cd>/stat_agent_ora_apps.
Copy the from the Stat installation CD to the Oracle E-Business Suite server.
Unzip 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.
Set STAT_JAVA_HOME to the JVM that should be used by the Stat Oracle Agent.
Example: $>STAT_JAVA_HOME=/opt/java/18
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 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.
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.
Open the file located in $ORACLE_HOME/bin/ and locate the following:
Open the file located in $ORACLE_HOME/bin/ and locate the following:
NOTE: For R12.2, make sure to change these values on both Run and Patch Editions.
Remove xmlparserv2.jar from the <STAT_HOME>/lib/oracle directory.
Review Appendix F of the System Administrator Guide if you have a firewall between your Stat Oracle Agents and your Stat Central Agent.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation