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 Central Agent using the service.bat command located in the <STAT_HOME>/app/bin/service folder.
1 |
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 SHORTNAME=Wildfly |
• |
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 |
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 |
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 |
NOTE: If you experience issues when stopping the service, you need to edit <STAT_HOME>\app\bin\jboss-cli.bat and uncomment and set the JAVA_HOME location. |
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 4.0 type 4 driver (db2jcc4.jar). 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 db2jcc4.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. |
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 |
Save the module.xml file. |
5 |
Edit <STAT_HOME>\app\standalone\configuration\standalone-full.xml (or for https, <STAT_HOME>\app\standalone\configuration\standalone-full-https.xml) in a text editor and locate the datasources:2.0 subsystem. You need to uncomment the driver for ibmJDBCDriver. |
6 |
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. |
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. |
1 |
Open <STAT_HOME>/app/bin/standalone.conf. |
The configuration of your SSH server determines which ciphers are used when connecting to the Stat® Central Agent. The Stat Central Agent currently supports the following cipher configurations:
• |
• |
• |
• |
2 |
Download the Java Cryptography Extension (JCE), which is contained in the appropriate zip file (jce_policy-8.zip) to a temp folder and unzip the file. |
3 |
4 |
5 |
6 |
Go to the temp folder where you unzipped the jce_policy file and copy local_policy.jar and US_export_policy.jar. |
7 |
© ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center