Chat now with support
Chat with Support

Stat 6.0 - Upgrade Notes

Upgrading Stat Upgrade the Stat Central Agent Upgrade the Stat Oracle Agent (Oracle E- Business Suite only) Additional changes Appendix: Upgrade Checklist

Stopping the Stat Central Agent

To stop the Stat Central Agent on either a Windows or a Unix platform, do one of the following:

You can also create a desktop shortcut which sends the appropriate command-line shut down argument to the Stat Central Agent.

If you have modified your port offset from the default value of zero due to conflicts with other systems, etc., then you must supply the modified port information to the shutdown command so that it can find the server to shut it down.

For example, if you modified the port offset to one, you need to edit %STAT_HOME%\app\bin\shutdown.bat and modify it as below:

For Unix installations, you need to edit $STAT_HOME/app/bin/shutdown.sh and modify it as below.

Also, if you running more than one Stat Central Agent on the same host machine, you must specify the port offset. In this case, you must also specify the port number when executing the shutdown command. The port numbers for a port offset of one is 9991 and for a port offset of 100 is 9990+100=10090. Again, these numbers may be modified if they conflict with other applications.

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.

1
Set JAVA_HOME and <STAT_HOME> in standalone.conf.bat to the full physical path.
2
Edit <STAT_HOME>/app/bin/service/service.bat and locate the following lines:
3
(Optional) In <STAT_HOME>/app/bin/service/service.bat, modify the following values if you want the service name to reflect Stat:
Set DISPLAYNAME=”Wildfly”
Set DESCRIPTION=”Wildfly Application Server”
4
Specify one of the following parameters to run service.bat commands: install|uninstall|start|stop|restart.
5
Launch a command-line and from <STAT_HOME>\app\bin\service directory run the following command:
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.
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.
6
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.

2
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.
3
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.
<!--
-->
4
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.
<!--
-->
5
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.
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.

1
Open <STAT_HOME>\app\bin\standalone.conf.bat.
Related Documents