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

Stat 7.0 - Install Notes

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

Stopping the Stat Central Agent

To stop the Stat Central Agent on either a Windows or a Unix platform, do one of the following:

•
For Windows, go to <installation location>\app\bin and run shutdown.bat in a command line editor.
•
For Unix, go to <installation location>/app/bin and run shutdown.sh in a command line editor.

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:

jboss-cli.bat --connect controller=localhost:9991 command=:shutdown

For Unix installations, you need to edit $STAT_HOME/app/bin/shutdown.sh and modify it as below.

./jboss-cli.sh --connect controller=localhost:9991 command=:shutdown

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 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 run.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
Locate the following line in /app/bin/service/service.bat and change its value to standalone-full-https.xml if you are using Stat Central Agent in HTTPS mode
•
set CONFIG=standalone-full.xml
5
Specify one of the following parameters to run service.bat commands: install|uninstall|start|stop|restart
6
Launch a command-line and from <STAT_HOME>\app\bin\service directory run the following command:
service install /controller localhost:9990 /jbossuser jboss /jbosspass 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.
7
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.
8
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.

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=%JAVA_OPTS% -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 -Djava.security.properties=%STAT_HOME%\app\standalone\configuration\stat.java.security.properties"
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=%JAVA_OPTS% -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 -Djava.security.properties=%STAT_HOME%\app\standalone\configuration\stat.java.security.properties -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="$JAVA_OPTS -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 -Djava.security.properties=$STAT_HOME/app/standalone/configuration/stat.java.security.properties"
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="$JAVA_OPTS -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 -Djava.security.properties=$STAT_HOME/app/standalone/configuration/stat.java.security.properties -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
* 
NOTE: JDK 9 and above offers strong cryptographic algorithms by default. You can skip the following steps if you are using JDK 9 or later.

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

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation