Chat now with support
Chat with Support

Stat 6.1 - Install Notes

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

Installing multiple servers on one host computer

Stat® currently supports installing up to four Stat Central Agents on the same host computer (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 server, 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 computer:
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 on the host computer 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 and open the standalone.conf.bat file in a text editor. Locate the line:
set "JAVA_OPTS=-Xms64M -Xmx512M -XX:MaxPermSize=256M -Dstat.home="%STAT_HOME%" -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 and open the standalone.conf file in a text editor. Locate the line:
JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Stack=true -Dstat.home=$STAT_HOME -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.

Installing the Stat Central Agent on Oracle WebLogic 11g/12c

As an alternative to the recommended Stat® Standalone platform, the Stat Central Agent can be installed on Weblogic 11g (WebLogic v10.3.3-10.3.6) or Weblogic 12c (v12.1.x-v12.2.x).

To install the Stat Central Agent on Oracle® WebLogic 11g/12c:
1
If you have not already done so, install Oracle WebLogic 11g/12c.
The directory where you install Oracle WebLogic 11g/12c will be referred to in this document as <WL_HOME>. You do not need to set this variable.
2
Create a directory for Stat 6.1.0 in <WL_HOME>/user_projects/domains/.
For a second Stat Central Agent, against a test repository you may create a new folder called <WL_HOME>/user_projects/domains/stat2.
* 
NOTE: If you have port conflicts, see Resolving Port Conflicts (WebLogic).
3
Create a variable named $STAT_HOME and set it to <WL_HOME>/user_projects/domains/stat.
4
Create a variable named $STAT_HOME2 and set it to <WL_HOME>/user_projects/domains/stat2.
5
On the installation media, go to the \stat_server\weblogic folder and unzip the file stat_weblogic.zip to <WL_HOME>/user_projects/domains/stat.
* 
NOTE: For Unix®, use the -a modifier to unzip the file.
6
Edit the startup script, startWebLogic.cmd located in <STAT_HOME> so that it references the correct wlserver folder name and (optionally) a different JDK version.
You will need to modify <WL_HOME>/user_projects/domains/stat/startweblogic.cmd (or startweblogic.sh for Unix) to point <STAT_HOME> to this new location or to the variable described in step 4.
7
Edit startWebLogic.cmd as follows:
a
Locate the wlserver_10x or wlserver_12x folder under <WL_HOME>, and edit the line:
set WL_HOME=%STAT_HOME%\..\..\..\wlserver_10 so that it specifies the exact folder name (e.g., wlserver_10.3).
* 
NOTE: WebLogic names its wlserver folder based on the minor release installed.
b
(Optional) If you want to use a different 1.7.x JDK version, replace the line JAVA_HOME=..\..\..\jdk160_45 with the path for the new version (e.g., JAVA_HOME=C:\j2sdk170_25).
8
If you are using WebLogic 12.2.x and on Windows®, edit <WL_HOME>/user_projects/domains/stat/bin/setDomainEnv.bat.
Locate the lines:
call "%WL_HOME%\common\bin\commEnv.cmd"
@REM For 12.2.x
@REM call "%WL_HOME%\..\oracle_common\common\bin\commEnv.cmd"
and change to:
@REM call "%WL_HOME%\common\bin\commEnv.cmd"
@REM For 12.2.x
call "%WL_HOME%\..\oracle_common\common\bin\commEnv.cmd"
9
If you are using WebLogic 12.2.x and on Unix, edit <WL_HOME>/user_projects/domains/stat/bin/setDomainEnv.sh.
Locate the lines:
. ${WL_HOME}/common/bin/commEnv.sh
# For 12.2.x
# . ${WL_HOME}/../oracle_common/common/bin/commEnv.sh
and change to:
# . ${WL_HOME}/common/bin/commEnv.sh
# For 12.2.x
. ${WL_HOME}/../oracle_common/common/bin/commEnv.sh
10
Locate the files wlclient.jar, wljmsclient.jar, and wlthint3client.jar and copy them to the Stat install folder on each workstation where Stat is installed.
These files are located in <WL_HOME>/wlserver_10.x/server/lib.
* 
NOTE: For Oracle Applications only, wlclient.jar and wljmsclient.jar must also be copied to each Stat Oracle Agent. For more information, see Install the Stat Oracle Agent (Oracle E-Business Suite only).
11
Do one of the following:
•
If on Windows, run the script startWebLogic.cmd.
•
If on Unix, run the script, startweblogic.sh.
The first time you start the WebLogic server, the Stat Connection is not properly defined; therefore the server will start with errors.
12
Configure Oracle WebLogic as follows:
a
Start the WebLogic console from the following url: http://<hostname>:8081/console
b
Login with the following credentials:
•
Username = weblogic
•
Password = irv200038stat
c
Click Services, and then Data Sources on the Domain Structure tree on the left side of the screen.
d
Click StatDataSource on the Configuration tab.
e
Click the Connection Pool tab.
f
Click Lock & Edit on the upper left portion of the screen.
g
Depending on whether your Stat Database is on Oracle or SQL Server®, update the DriverName, Properties and URL.
For Oracle:
•
Update the URL with your Stat Database information :@hostname:port:sid
•
DriverName="oracle.jdbc.driver.OracleDriver"
•
Properties=v$session.program=STAT
•
Set the user name to STAT and set the password for Stat user.
For SQL Server:
•
Update the URL with your Stat Repository information: //hostname:port/databasename.
•
DriverName="net.sourceforge.jtds.jdbc.Driver"
•
Properties="user=STAT
•
appName=”Stat Central Agent on WebLogic"
•
URL="jdbc:jtds:sqlserver://hostname:port/databasename"
h
If your connection needs more properties, such as instance or ssl, append those properties to the Properties value. For example if you are running the Stat Database as an instance, append the instance name to the Properties value:
Properties="appName=Stat Central Agent on WebLogic;instance=instance name"
If you enabled ssl on Stat Database server running SQL Server, append the ssl name to the Properties value:
Properties="appName=Stat Central Agent on WebLogic;ssl=require"
i
Click Save on the Connection Pool tab.
* 
NOTE: If you do not receive a green check mark with the message “Settings Updated Successfully”, edit your savings and try again.
j
Click Activate Changes under Lock & Edit.
You should receive a green check mark with the message “All Changes have been activated. No restarts are necessary”.
k
Log out of the console.
13
Restart the Stat Central Agent.
14
Open a browser and go to http://<hostname>:8081/stat (host name is the name of the machine where weblogic is installed).

Configuring the Stat Central Agent on Oracle WebLogic 11g/12c

Refer to the following sections for information on the number of ways you can configure the Stat® Central Agent on Oracle® WebLogic 11g:

•
Configuring the Stat Central Agent as a Windows Service (WebLogic)
•
Installing DB2 Support for the Stat Central Agent (WebLogic)
•
Resolving Port Conflicts (WebLogic)
•
Deleting Data Sources and Connection Pools (WebLogic)
•
Support IMAP via TLS

Configuring the Stat Central Agent as a Windows Service (WebLogic)

Optionally, you can configure the Stat® Central Agent as a Windows® service. For more information, see the section, “Setting Up a WebLogic Server Instance as a Windows Service,” currently located at the following URL:

http://download.oracle.com/docs/cd/E14571_01/web.1111/e13708/winservice.htm#i1186180

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating