Stat 6.2 - Install Notes

Chat now with support

Update the System Maintenance table Install the Stat Central Agent

Installing the Stat Central Agent Configuring the Stat Central Agent

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 Configure the Stat Central Agent character map Setting up support for AES256 Ciphers for SFTP Configure Web Client to use HTTPS Connection pool idle time Installing multiple servers on one host computer

Testing Database and Server Connections

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

Configuration Administration Dynamically changing log level Stat Oracle Agent version Custom products and file locations Object compare support for form library files Base directory codes Verifying the Stat Oracle Agent

Configure the SYSTEM user account Update the PS Object Mover Instructions (PeopleSoft Only) Implement Stat

Installing multiple servers on one host computer

Stat® currently supports installing up to four Stat Central Agents on the same host computer (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 server, contact Technical Support.

NOTE: You can install only one Stat Central Agent per Stat Repository.

To install an additional Stat Central Agent on the same computer:

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 on the host computer 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 and open the standalone.conf.bat file in a text editor. 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 and open the standalone.conf file in a text editor. 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.

Click Menu in the Stat Web Console menu bar.

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.

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.

To Install the Stat Oracle Agent:

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

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. This directory is referred to below as STAT_HOME.

Set the <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 the STAT_JAVA_HOME to the JVM on the Stat Central Agent 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 on the Stat Central Agent if one is not already available.

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.

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 the database server's sqlnet.ora.

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:

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

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

(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

export TNS_ADMIN

•

Replace with the following:

#TNS_ADMIN=$ORACLE_HOME/network/admin

#export TNS_ADMIN

TNS_ADMIN=${TNS_ADMIN:-$ORACLE_HOME/network/admin}

export TNS_ADMIN

(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:

•

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

TNS_ADMIN=$ORACLE_HOME/network/admin

export TNS_ADMIN

•

Replace with the following:

#TNS_ADMIN=$ORACLE_HOME/network/admin

#export TNS_ADMIN

TNS_ADMIN=${TNS_ADMIN:-$ORACLE_HOME/network/admin}

export TNS_ADMIN

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

Remove xmlparserv2.jar from <STAT_HOME>/lib/oracle directory.

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

•

Parameters prefixed with stat apply to all instances of an agent and should only be defined once in the configuration file.

•

Parameters prefixed with <ENV> refer to an instance of the Stat Oracle Agent for a particular Oracle E-Business Suite environment. The <ENV> must be replaced with the environment code used to define that Oracle E-Business Suite environment in Stat.

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:

stat.central_agent.server:<stat agent server name/ip>

stat.central_agent.name_port:8080

java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory

#stat.central_agent.protocol:https

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.

<env>.env.CONTEXT_NAME:<sid_hostname>

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