Stat 6.1 - Upgrade Notes

Chat now with support

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 Configuring the Stat Central Agent character map Setting up support for AES256 ciphers for SFTP Configuring the Web Client to use HTTPS Modifying connection pool idle time Installing multiple servers on the same host

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

Configuring the Stat Central Agent as a Windows service (WebLogic) Installing DB2 support for the Stat Central Agent (WebLogic) Resolving port conflicts (WebLogic) Deleting data sources and connection pools (WebLogic) Support IMAP via TLS

Testing database and server connections

Upgrade the Stat Oracle Agent (Oracle E- Business Suite only) Additional Changes

Assign user class rights

Appendix: Upgrade Checklist

Configuring the Stat Central Agent as a Windows service

If you previously used Wrapper.conf and other associated files to run the Stat® Central Agent functionality of the Stat Central Agent as a Windows service, you must replace them with the wrapper that is provided with the Stat standalone agent. Use the service.bat command located in the <STAT_HOME>/app/bin/service folder.

To configure the Stat Central Agent as a Windows® service:

Set JAVA_HOME and <STAT_HOME> in standalone.conf.bat to the full physical path.

Edit <STAT_HOME>/app/bin/service/service.bat and locate the following lines:

REM Uncomment and set your JAVA_HOME here

REM set JAVA_HOME=<>

REM set PATH=%JAVA_HOME%/bin;%PATH%

Enter the full path for your JAVA_HOME variable.

(Optional) In <STAT_HOME>/app/bin/service/service.bat, modify the following values if you want the service name to reflect Stat:

•

Set SHORTNAME=Wildfly

•

Set DISPLAYNAME=”Wildfly”

•

Set DESCRIPTION=”Wildfly Application Server”

Specify one of the following parameters to run service.bat commands: install|uninstall|start|stop|restart.

Launch a command-line and from <STAT_HOME>\app\bin\service directory run the following command:

service install /controller localhost:9990 /user jboss /password irv200038stat+

This installs JBoss AS as a Windows service by creating a manual service called Wildfly (unless you changed the name in step 2). Now JBoss AS should be enlisted in the Windows Service List, which is found in the Control Panel.

The install process creates 3 log files in the <STAT_HOME>\app\standalone\log directory. Any subsequent service command calls will write to these 3 log files.

Now you can use either the Windows service applet or the service.bat command to start the service.

NOTE: You may use the actual hostname instead of localhost above. Also note that port 9990 is used when your default post-offset is zero. If you have changed the port-offset, you need to use the corresponding management socket binding port.

To start JBoss AS service, run <STAT_HOME>\app\bin\service>service start.

NOTE: The log files created in <STAT_HOME>\app\standalone\log directory by service.bat are persistent. You should monitor the size of this file while running as a service.

To modify the service.bat file, you need to stop the service, uninstall it, make the changes you want, and then reinstall the service.

•

To stop the service, run <STAT_HOME>\app\bin\service>service stop.

•

To remove the service, run <STAT_HOME>\app\bin\service>service uninstall.

Installing DB2 support for the Stat Central Agent

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

To install DB2 support:

Make sure Stat Central Agent is shut down.

Copy db2jcc.jar and db2jcc_license_%%.jar from C:\Program Files\IBM\SQLLIB\java to <STAT_HOME>\app\modules\com\ibm\db2\jcc\main directory. The location of required drivers may vary on your site due to DB2 installation preferences.

NOTE: The db2jcc_license_cisuz.jar file has been removed from certain products in DB2 client installations. Depending on the DB2 configuration, it may or may not be needed.

Edit <STAT_HOME>\app\modules\com\ibm\db2\jcc\main \module.xml in a text editor and uncomment the 3 jar files in the resources section.

Resources section before edit:

<!--

<resource-root path="db2jcc.jar"/>

<resource-root path="db2jcc_license_cisuz.jar"/>

<resource-root path="db2jcc_license_cu.jar"/>

-->

</resources> …

Resources section after edit:

<resource-root path="db2jcc.jar"/>

<resource-root path="db2jcc_license_cisuz.jar"/>

<resource-root path="db2jcc_license_cu.jar"/>

</resources> …

Save module.xml file.

Edit <STAT_HOME>\app\standalone\configuration\standalone-full.xml in a text editor and locate the datasources:2.0 subsystem. You need to uncomment the driver for ibmJDBCDriver.

Datasources subsystem section before edit:

<driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>

</driver>

<!--

<driver-class>com.ibm.db2.jcc.DB2Driver</driver-class>

-->

Datasources subsystem section after edit:

<driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>

</driver>

<driver-class>com.ibm.db2.jcc.DB2Driver</driver-class>

Save standalone-full.xml file.

NOTE: When you modify an .xml file, be sure that there is only one copy of it in the directory when you are finished. Do not rename the old copy and leave it in that directory.

Restart the Stat Central Agent.

The Stat Central Agent requires 3 columns filled in to connect to a PeopleSoft® database:

•

Host — The IP address or Server name where the database resides

•

Service — The UDB/DB2 database name as defined during installation, not an alias.

•

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:

•

currentSQLID= The implicit qualifier of all table, view, alias, and index names specified in dynamic SQL statements (Mainframe).

•

currentSchema= Specifies the default schema name that is used to qualify unqualified database objects in dynamically prepared SQL statements-also case sensitive (AIX®).

Configuring the Stat Central Agent character map

The Stat® Central Agent defaults to a character map of ISO-8859-1, which is compatible with sites that are upgrading from older versions of Stat. If desirable, the agent can be configured to use UTF-8.

If the Stat Central Agent is running on Windows:

Open <STAT_HOME>\app\bin\standalone.conf.bat.

Locate the following:

set "JAVA_OPTS=-Xms64M -Xmx512M -XX:MaxPermSize=256M -Dstat.home="%STAT_HOME%" -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"

At the end of the line and included inside the final quote mark, add:

-Dweb.charset=UTF-8

The final edit will look like this:

Restart the Stat Central Agent.

If the Stat Central Agent is running on Unix®:

Open <STAT_HOME>/app/bin/standalone.conf.

Locate the following:

JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Stack=true -Dstat.home=$STAT_HOME -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"