Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Stat 6.3 - Upgrade Notes

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

To install DB2 support:
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.
* 
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.
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> …
Save module.xml file.
4
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 after 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>
5
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.
6
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).
OR
•
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:
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 download and apply the Java Cryptography Extension (JCE):
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.

Configuring the Web Client to use HTTPS

To configure the Web Client to use HTTPS:
8
Ensure the agent is shut down.
9
Delete <STAT_HOME>/app/standalone/tmp and <STAT_HOME>/app/standalone/data if one exists.
10
Obtain a keystore with a self-signed certificate from your security group or build it yourself, if authorized.
You need to know the keystore file name and the password that opens it.
11
Once you have the keystore, move it to <STAT_HOME>/ app/standalone/configuration.
12
Go to <STAT_HOME>/ app/ standalone/standalone-full-https.xml to point to your keystore.
Look for this block in the file:
<security-realm name="SslRealm">
<server-identities>
<ssl>
<keystore path="keystore.jks"
relative-to="jboss.server.config.dir"
keystore-password="changeme"/>
</ssl>
</server-identities>
</security-realm>
13
Modify the keystore.jks with the name of your keystore and modify the keystore-password with the password for your keystore.
14
Go to the <STAT_HOME>/app/bin directory and locate the standalone.conf.bat (for Unix, standalone.sh) file.
a
Uncomment the JAVA_HOME statement and point it to your Java Home location.
b
Uncomment the STAT_HOME statement and point it to your Stat Home.
c
Locate the SERVER_CONFIG variable and uncomment one of the following 2 lines:
•
For http, uncomment the line: SERVER_CONFIG=standalone-full.xml. Make sure the line SERVER_CONFIG=standalone-full-https.xml is commented out.
•
For https, uncomment the line: SERVER_CONFIG=standalone-full-https.xml. Make sure the line SERVER_CONFIG=standalone-full.xml is commented out.
15
Keep in mind that if you had already configured a datasource for the agent using http configuration, you need to define the database again for the https configuration file. In this case, when you start the agent, you may receive some errors, but you are still able to enter the datasource information using the https://<agent_hostname>:port/stat-config URL. Once the datasource is saved, you need to restart the agent again.
16
At this point users can login as https://servername:8443 if the port from the agent is zero.
Additional Steps for Oracle EBusiness customers:

After configuring the Stat Central agent to run in https mode, http protocol is completely removed from the Wildfly configuration file. This means that the messaging protocol used between the Stat Central agent and all Stat Oracle Agents must use secure messaging over https. This means that the certificate stored in your keystore file must be imported into the JAVA_HOME installation of your Stat Oracle Agents.

1
On your Oracle Ebusiness machine, go to the <STAT_JAVA_HOME>/jre/lib/security directory.
2
Import your certificate into your jssecacerts file. (If file does not exist, you can create it.) One way to do this is by using the java keytool command.
keytool -import -keystore jssecacerts -file mycert.cert -alias stat_https_client –trustcacerts
3
Finally you need to tell the Stat Oracle Agent to use https protocol for its communications. Edit the <STAT_HOME>/conf/stat.conf file and uncomment the following property:
stat.central_agent.protocol:https
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation