Chat now with support
Chat with Support

Stat 6.1 - Upgrade Notes

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

Refer to the following sections for information on the number of ways you can configure the Stat® Central Agent on Oracle® WebLogic 11g/12c:

Configuring the Stat Central Agent as a Windows service (WebLogic)

Optionally, you can configure the Stat® Central Agent as a Windows® service. For more information, see the section, Setting Up a WebLogic Server Instance as a Windows Service, currently located at the following URL: http://download.oracle.com/docs/cd/E14571_01/web.1111/e13708/winservice.htm#i1186180.

Installing DB2 support for the Stat Central Agent (WebLogic)

The requirements have changed since 5.6.3. The DB2® Client connect does not need to be installed on the Stat™ Central Agent machine, however the agent does need the jdbc drivers provided in DB2 connect.

The Stat Central agent will now use the IBM® JDBC type 4 driver. The required files can be found in C:\Program Files\IBM\SQLLIB\java of the DB2 client installation. Note that Stat requires a 32 bit version of these files.

Copy db2jcc.jar and db2jcc_license_%%.jar from C:\Program Files\IBM\SQLLIB\java to <STAT_HOME>\lib. The location of required drivers may vary on your site due to DB2 installation preferences.

Also note that in the Stat Central agent needs 3 columns filled in for connection to a PeopleSoft database that were not required before.

Host Name — The IP address or server name where the database resides
Service Name— The UDB/DB2 database name. This is database name as defined during installation, not an alias.
DB Listener Port — The port that is listening for requests against the UDB/DB2 database.

Additionally, the Other Database Parameters field is now case sensitive for UDB/DB2 databases. The correct format is:

Resolving port conflicts (WebLogic)

On many server installations, standard ports are often already occupied by various systems. By default, the Stat® Central Agent uses port number 8081. If you have port conflicts, the server will display one or more error messages, such as java.net.BindException or Address already in use. To resolve this conflict you may need to change the default service port, 8081.

2
Open file config.xml.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating