IMPORTANT: Shorter times could adversely affect agent performance. |
1 |
Open <STAT_HOME>/config/stat.properties. |
2 |
Locate the parameter CONNECTION_IDLE_TIME=15, and modify the time. |
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. |
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. |
• |
For Windows, go to <STAT_HOME2>\app\bin, open the file standalone.conf.bat in a text editor, and locate the line: |
• |
For Unix, go to <STAT_HOME2>/app/bin, open the file standalone.conf in a text editor, and locate the line: |
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. |
NOTE: To test connections in Stat Web, you must be assigned the user class right, Agent Test Connect. |
2 |
Enter your assigned user name and password and click Login or press <Enter>. This logs you into the Stat Web Console. |
3 |
Click Menu in the Stat Web Console menu bar. This opens the Stat Menu window. |
7 |
Click Test Connect. |
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.
3 |
Backup or archive the stat.conf file for each Stat Oracle Agent you want to upgrade. |
5 |
Locate the stat installation directory: <stat installation cd>/stat_agent_ora_apps. |
6 |
7 |
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. |
8 |
Set <STAT_HOME> and PATH in the profile of each Oracle E-Business Suite user (e.g. applmgr) on the server. |
9 |
Set STAT_JAVA_HOME to the JVM that should be used by the Stat Oracle Agent. |
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. |
a |
Open statctl.sh. |
11 |
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. |
12 |
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. |
13 |
a |
Open the stat.conf file located in <STAT_HOME>/conf and add the parameter <env>.env.CONTEXT_NAME:<sid_hostname>. |
b |
(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: |
• |
c |
(Optionally) If you experience issues with compiling Form File, you may need to patch the frmcmp_batch.sh file located in $ORACLE_HOME/bin directory: |
• |
NOTE: For R12.2, make sure to change these values on both Run and Patch Editions. |
d |
15 |
Review Appendix F of the System Administrator Guide if you have a firewall between your Stat Oracle Agents and your Stat Central Agent. |
© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center