Chat now with support
Chat with Support

Stat 6.0 - Install Notes

Installing Stat
Prepare for installation Unpack the 6.0.0 installer Install the Stat database Create a staging database (PeopleSoft Only) Install the Stat Client Configure the Stat database Update the System Maintenance table Install the Stat Central Agent Install the Stat Oracle Agent (Oracle E- Business Suite only) Configure the SYSTEM user account Update the PS Object Mover Instructions (PeopleSoft Only) Implement Stat

Resolving port and firewall conflicts

If the Stat® Central Agent will not run when started, the port assigned to it may already in use by a different program or there are firewalls that need to have ports opened for the Stat Central Agent to communicate with the database or with the Stat Client.

NOTE: Starting with Stat 6.0.0, Stat Central Agent port settings are stored in the following location: <STAT_HOME>\app\standalone\configuration\standalone-full.xml. This is not the same location as previous versions of Stat.

Typical port and firewall conflicts include:

If you have port conflicts, the server will display one or more error messages, such as:

The Stat Central Agent utilizes a set of ports as defined by the values in:

These values are defined for a default port offset of zero which is set in a variable called jboss.socket.binding.port-offset in standalone.conf.bat or standalone.conf file. If there is a conflict situation or a second or third agent is necessary, you may change the jboss.socket.binding.port-offset in standalone.conf.bat or standalone.conf file. The value for offset is added to all the default values.

For example:

HTTP socket binding


HTTPS socket binding (See Note)


Management socket binding


Management socket binding https (See Note)


Transaction sockets



NOTE: Be aware of the following:

When other applications are using the same port as the Stat Central Agent, you need to change the port offset in your standalone.conf.bat or standalone.conf file.

Open <STAT_HOME>\app\bin\standalone.conf.bat with Notepad or other text editor. For Stat Central Agent on Unix, you need to open the <STAT_HOME>/app/bin/standalone.conf file.
Search for the setting: -Djboss.socket.binding.port-offset=0
Change the setting to a proper offset. For example, -Djboss.socket.binding.port-offset=10

The http port is the only port that needs to be opened on existing firewalls.

Other ports used by the Stat Central Agent include the following (the actual port numbers will vary according to your site specifications):

PeopleSoft® databases

The Stat Client will need the same ports opened if there is a firewall between the client and any of the above items.

If there is a natted firewall between the Stat Central Agent and the Stat Oracle Agents, the following options must be configured in the stat.conf file for the Stat Oracle Agents. Older versions of Stat always required the fields to be filled in, but since 5.7.0, the Stat Oracle Agents query the Stat Central Agent for the secure Stat database information. You need only change the stat.db.server: value and indicate the natted ip address. For this scenario, they are not optional.

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/ 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 those files with the wrapper that is provided with the Stat standalone agent using the service.bat command located in the <STAT_HOME>/app/bin/service folder.

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:
(Optional) In <STAT_HOME>/app/bin/service/service.bat, modify the following values if you want the service name to reflect Stat:
Set DESCRIPTION=”Wildfly Application Server”
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.
To start JBoss® AS service, run <STAT_HOME>\app\bin\service>service start.
NOTE: The log files created in the <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 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.

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.
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.
Save the 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.
Save the 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 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:
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating