Chatta subito con l'assistenza
Chat con il supporto

Stat 6.3 - Install Notes

Installing Stat
Prepare for installation Unpack the 6.3.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

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 Central Agent using the service.bat command located in the <STAT_HOME>/app/bin/service folder.

To configure the Stat Central Agent as a Windows service:
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:
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.
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
5
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 Wildfy 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.
6
To start Wildfly 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.
7
To modify the service.bat file, you need to stop the service, uninstall it, make the changes you want, and 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
* 
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.

Installing DB2 Support for the Stat Central Agent

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.

To install DB2 support for the Stat Central Agent:
1
Make sure Stat Central Agent is shut down.
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.
Resources section before edit:
<module xmlns="urn:jboss:module:1.1" name="com.ibm.db2.jcc">
<resources>
<!--
<resource-root path="db2jcc4.jar"/>
<resource-root path="db2jcc_license_cisuz.jar"/>
<resource-root path="db2jcc_license_cu.jar"/>
-->
<!-- Insert resources here -->
</resources> …
Resources section after edit:
<module xmlns="urn:jboss:module:1.1" name="com.ibm.db2.jcc">
<resources>
<resource-root path="db2jcc4.jar"/>
<resource-root path="db2jcc_license_cisuz.jar"/>
<resource-root path="db2jcc_license_cu.jar"/>
<!-- Insert resources here -->
</resources> …
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.
Datasources subsystem section before edit:
<subsystem xmlns="urn:jboss:domain:datasources:2.0">
<datasources>
<drivers>
<driver name="OracleJDBCDriver" module="oracle.jdbc"/>
<driver name="jtdsJDBCDriver" module="net.sourceforge.jtds">
<driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
</driver>
<!--
<driver name="ibmJDBCDriver" module="com.ibm.db2.jcc">
<driver-class>com.ibm.db2.jcc.DB2Driver</driver-class>
</driver>
-->
</drivers>
</datasources>
</subsystem>
Datasources subsystem section before edit:
<subsystem xmlns="urn:jboss:domain:datasources:2.0">
<datasources>
<drivers>
<driver name="OracleJDBCDriver" module="oracle.jdbc"/>
<driver name="jtdsJDBCDriver" module="net.sourceforge.jtds">
<driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
</driver>
<driver name="ibmJDBCDriver" module="com.ibm.db2.jcc">
<driver-class>com.ibm.db2.jcc.DB2Driver</driver-class>
</driver>
</drivers>
</datasources>
</subsystem>
6
Save the standalone-full.xml file (or for https, the standalone-full-https.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.
7
Restart the Stat Central Agent.
Also note that in the PeopleSoft Environment Connection Maintenance table, 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:
•
currentSQLID=The implicit qualifier of all table, view, alias, and index names specified in dynamic SQL statements (Mainframe).
or
•
currentSchema=Specifies the default schema name that is used to qualify unqualified database objects in dynamically prepared SQL statements-also case sensitive (Aix).

Configure 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®:
1
Open <STAT_HOME>\app\bin\standalone.conf.bat.
2
Locate the following:
set "JAVA_OPTS=-Xms64M -Xmx512M -XX:MaxPermSize=256M -Dstat.home="%STAT_HOME%" -Dstat.server.config.file=%SERVER_CONFIG% -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"
3
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:
set "JAVA_OPTS=-Xms64M -Xmx512M -XX:MaxPermSize=256M -Dstat.home="%STAT_HOME%" -Dstat.server.config.file=%SERVER_CONFIG% -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 -Dweb.charset=UTF-8"
4
Restart the Stat Central Agent.
If the Stat Central Agent is running on UNIX®:
1
Open <STAT_HOME>/app/bin/standalone.conf.
2
Locate the following:
JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Stack=true -Dstat.home=$STAT_HOME -Dstat.server.config.file=$SERVER_CONFIG -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"
3
At the end of the line and included inside the final quote mark, add:
Add -Dweb.charset=UTF-8
The final edit will look like this:
JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Stack=true -Dstat.home=$STAT_HOME -Dstat.server.config.file=$SERVER_CONFIG -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 -Dweb.charset=UTF-8"
4
Restart the Stat Central Agent.

Setting up support for AES256 Ciphers for SFTP

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:

•
Blowfish
•
Triple DES
•
AES128
•
AES192
•
AES256

To configure J2SE 1.8 to support AES256, you need to download and apply the Java® Cryptography Extension (JCE). To do this:

1
Go to the following url: http://www.oracle.com/technetwork/java/javase/downloads/index.html
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
Browse to the JAVA_HOME/jre/lib/security directory under your installation of JAVA_HOME.
4
Rename local_policy.jar to local_policy.jar.strong.
5
Rename US_export_policy.jar to US_export_policy.jar.strong.
6
Go to the temp folder where you unzipped the jce_policy file and copy local_policy.jar and US_export_policy.jar.
7
Paste both files into the JAVA_HOME/jre/lib/security folder.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione