サポートと今すぐチャット
サポートとのチャット

Stat 6.2 - Upgrade Notes

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

Modifying connection pool idle time

This feature allows the site to define the length of time before the Stat™ Central Agent connection pool times out database connections. The default is 15 minutes. However, Java® could take up to twice as long to actually disconnect from the environment.

* 
IMPORTANT: Shorter times could adversely affect agent performance.
To modify pool idle time:
1
Open <STAT_HOME>/config/stat.properties.
2
Locate the parameter CONNECTION_IDLE_TIME=15, and modify the time.
3
Stop and restart the agent.

Installing multiple servers on the same host

Stat™ currently supports installing up to four Stat Central Agents on the same host machine (provided there are no port conflicts). Additional Stat Central Agents are installed basically the same way as the first server, except you will need to install the additional servers to separate directories, define separate system variables, modify the startup files, and assign the servers to different port profiles.

If you need to install more than four servers on the same computer, contact Technical Support.

* 
NOTE: You can install only one Stat Central Agent per Stat Repository.
To install an additional Stat Central Agent on the same machine:
1
Unzip the contents of stat_standalone.zip to a location on the host computer that is different from the location where the first Stat Central Agent is installed. This location will be referred to as <STAT_HOME2>.
2
Create an environment system variable called STAT_HOME2 with a value of <STAT_HOME2> from the above step.
3
Do one of the following, depending on your platform:
•
For Windows, go to <STAT_HOME2>\app\bin, open the file standalone.conf.bat in a text editor, and locate the line:
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"
Change the value "%STAT_HOME%" to "%STAT_HOME2%".
Change the value for –Djboss.socket.binding.port-offset from zero to a proper value.
•
For Unix, go to <STAT_HOME2>/app/bin, open the file standalone.conf in a text editor, and locate the line:
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"
Change the value $STAT_HOME to $STAT_HOME2.
Change the value for –Djboss.socket.binding.port-offset from zero to a proper value.
The value for port-offset assigns a new offset of ports to the second Stat Central Agent. See Resolving port and firewall conflicts for information on choosing the proper value for port-offset and resolving port conflicts.
4
Continue installing the second Stat Central Agent the same way you did the first using the Configuration Assistant.
Remember that the URL address for the Configuration Assistant will be different for the second Stat Central Agent. After changing the port-offset, the default URL for the second Stat Central Agent is calculated by adding the port-offset to 8080. For example, if port-offset is set to 1, then the URL is http://localhost:8081/stat-config.

Testing database and server connections

If you have already defined any database and server connections in the Stat® Repository, you can test the connections in the Stat Web Client after installing the Stat Central Agent.

* 
TIP: You can also test connections in the Stat Windows Client. For more information, see the Stat System Administration Guide, Chapter 4, General Maintenance Tables.

You can validate the connections between the Stat Central Agent and all the databases, ftp file servers, email servers, and VCM repositories currently defined in the Stat Repository.

* 
NOTE: To test connections in Stat Web, you must be assigned the user class right, Agent Test Connect.
To test database and server connections:
1
Open your internet browser and go to the URL address for Stat Web.
•
http://localhost:8080/stat
2
Enter your assigned user name and password and click Login or press <Enter>. This logs you into the Stat Web Console.
3
Click Menu in the Stat Web Console menu bar. This opens the Stat Menu window.
4
Click Test Connect.
5
Select the tab for the type of database or server you want to test.
6
Select the checkbox for each database or server you want to test.
7
Click Test Connect.
The Stat Central Agent attempts to connect to each database or server you selected and then reports the results in the Status column. Connection errors are reported with a brief description of the problem.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択