Stat 6.3 - Install Notes

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.

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

The following installation must be performed on each Oracle® E-business Suite server that will be managed by Stat®. The Stat Oracle Agent must run as the owner of the APPL_TOP, however only a single installation is needed for each server.

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. If the Stat Central Agent is not installed or is shut down for any reason, the Stat Agent for Ora Apps will not process any commands.

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

NOTE: The <env>.CONTEXT_NAME parameter is required for Release 12 support.

NOTE: For R12.2, make sure to change these values on both Run and Patch Editions.

Configuration

The stat_ora.zip file includes a default stat.conf file, which after installation is located in the user home directory under <STAT_HOME>/conf. All the mandatory parameters and most commonly used parameters are included in this default configuration file. The values for some of these parameters will need to be updated. Additional parameters listed in this section may not be included in the default stat.conf file and, if applicable, will need to be defined by the user. The syntax for all parameters is name:value pair. Comments begin with a # character and end with the end of the line.

Some parameters apply to all instances of an agent (e.g. parameters to identify the Stat® Repository), while others apply to each instances of an agent (e.g. parameters specific for an Oracle® E-Business Suite environment).

When the Stat Oracle Agent is started, the stat.conf configuration parameters are cached in memory. You need to restart the agent before a parameter change can take effect.

Modify stat.conf with the correct value for the following configuration parameters:

All R12 (not required for 11i) Oracle E-Business suite versions must have the CONTEXT_NAME parameter defined in the stat.conf file. The usual configuration for this value is sid_hostname.

For a complete list of stat.conf configuration, refer to the Stat System Administration Guide, Appendix, stat.conf configuration.

Administration

A separate instance of the agent must be started on the server for each Oracle® E-Business Suite environment. The Stat® Oracle Agent must be started as the Oracle E-Business Suite user (e.g. applmgr) for the environment (not the user created during the installation). Set the <STAT_HOME>, STAT_JAVA_HOME, and PATH in the profile of the Oracle E-Business Suite user on each server. The <STAT_HOME>/bin/statctl.sh utility should be used to control the Stat Oracle Agent.

NOTE: The statctl.sh is a UNIX based utility. MKS is required on Windows platforms to administer the Stat Oracle Agent.

A log of the agent can be found in <STAT_HOME>/log. A separate log file is created for each instance of the agent.

The following command can be used to start an instance of the Stat Oracle Agent for the Dev Oracle E-Business Suite environment

The following command can be used to stop the instance of the Stat® Agent for Ora Apps for the Test Oracle E- Business Suite environment. This command will send a shutdown request to the administration port on the local server. The agent will terminate after all queued events are processed.

If the Stat Central Agent is shut down or disabled, the Stat Agents for Ora Apps are unable to execute any commands or processes. Before re-starting the Stat Central Agent, shut down each Stat Agent for Ora Apps. Then re-start the Stat Central Agent, wait for the startup process to complete (in the server console, you will see the line, “Stat Central Agent is started”), and re-start each Stat Agent for Ora Apps.

The following command can be used to display the status of the Stat Agent for Ora Apps for the Production Oracle E-Business Suite environment.

The following command can be used to abort the Stat Oracle Agent for the Test Oracle E-Business Suite environment. The agent will be terminated immediately. Caution: This could potentially leave events in an unstable state. It may be necessary to re-processes events in-progress or pending when the agent process was aborted. This option should only be used as a last measure for terminating the agent.

The following command can be used to show the Stat Oracle Agent is alive along with the number of queued and in process messages.