Stat 6.2 - System Administration Guide

Testing Environment Connections

Oracle Applications Connection Maintenance

The Oracle Applications Connections Maintenance table defines the Oracle Applications environments and servers that Stat can connect to. These are the environments available for selection on CSRs and the various object wizards. Within the definition for each environment is the information Stat needs to connect to it.

Oracle Applications connection security is controlled by the following user class rights:

•

Oracle Connection - Add

•

Oracle Connection - Edit

The Oracle Application Connection Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | General | Oracle Applications Connect.


Value	Description
Active	If selected, indicates that this environment is active in Stat
Environment Cd (Key Value)	A 1-10 character code which uniquely identifies the environment. This is the code that must be used in the Stat Oracle Agent configuration file.
Description (Required Value)	A 1-35 character description of the environment
OraApps Version (Required Value)	The version number of the Oracle Applications environment. Options include 11i and R12.
Data Obj Version	The Oracle Applications version number, as defined in the Data Objects Maintenance table. Select a value in this field only if you plan on using Stat to manage data objects within this environment.
Req. Mgr. Approval	If selected, indicates that archive sets cannot be migrated to the environment without approval
Req. Patch Approval	If selected, indicates that patches cannot be applied to the environment without approval
DBMS (Required Value)	The Oracle database management system that the environment is running on
Database Name	TNSNAMES.ORA entry on all Stat users’ workstations. Used by Stat Client for Oracle Net connections to the Oracle Applications database.
APPS User	Name of the APPS database account holder
APPLSYS User	Name of the APPLSYS database account holder
SYSTEM Pwd	SYSTEM database account password
APPS Pwd	APPS database account password
Host Name	Name of the machine hosting the database. Used by the Stat Central Agent and the Stat Oracle Agent for JDBC connections to the Oracle Applications database. Required value for the Stat Central Agent.
Service Name	For Oracle, the listener service of the database. Used by the Stat Central Agent and the Stat Oracle Agent to establish JDBC connections to the Oracle database. IMPORTANT: Required value for the Stat Central Agent, even when Tns values are specified.
DB Listener Port	Port number for the database listener. Used by the Stat Central Agent and the Stat Oracle Agent for JDBC connections to the Oracle Applications database. Required value for the Stat Central Agent.
Use Tns	For RAC Oracle databases, configures Stat to invoke TNS
Tns Entry	The full description as it appears in the tnsnames.ora file with no line breaks or carriage returns
Other Database Parameters	Additional environment-specific parameters, if needed
Last Update (Read Only)	The date and time this record was last updated
Update By (Read Only)	The user who last updated this record

Defining Oracle Applications Servers

In the Oracle Apps Environment Servers table, you define one or more servers that host the four service partitions required for each Oracle Applications environment. These service partitions include Web Service, Forms Service, Concurrent Manager Service, and Admin Service. To open the table, select the environment you want and click Servers.


Value	Description
Active	If selected, indicates that the server is active
Server Name (Required Value)	A user defined character code which uniquely identifies the server in Stat
Server Host (Required Value)	The physical hostname (as opposed to the value in the Server Name field, which is user defined). This must be the server’s exact name (i.e., the value returned by hostname).
Platform (Required Value)	The server’s operating system
Working Directory (Required Value)	The location where the Stat Oracle Agent temporarily unzips patch files. A patch file is only stored in the directory while Stat is applying the patch with AutoPatch. After the patch has been applied, the patch file is removed.
Autobatch Size	Batch size parameter for AutoPatch
Autoparallel Workers	The number of parallel workers used by autopatch
Web Srv	Indicates if the server hosts a Web Service
Forms Srv	Indicates if the server hosts a Forms Service
Concurrent Srv	Indicates if the server hosts a Concurrent Manager Service
Admin Srv	Indicates if the server hosts the Database Service, also known as the “Administration Server” in Oracle documentation
Start Concurrent Cmd	Command run by the Stat Oracle Agent to start Concurrent Manager Service
Stop Concurrent Cmd	Command run by the Stat Oracle Agent to stop Concurrent Manager Service
Start Forms Cmd	Command run by the Stat Oracle Agent to start Forms Service
Stop Forms Cmd	Command run by the Stat Oracle Agent to stop Forms Service
Start Web Cmd	Command run by the Stat Oracle Agent to start Web Service
Stop Web Cmd	Command line run by the Stat Oracle Agent to stop Web Service
Ping Multiplier	The rate in 30 second increments at which the Oracle Agent updates the MEC_WAKE table and reports its status in Oracle Agent Status window (opened from the Tools menu). The default value is 1, meaning every 30 seconds. To increase the time amount, enter a higher value, e.g., meaning 120 seconds (4x30=120 seconds). The default value is 1. If the value is set to 0, the agent does not report its status and will always be shown as 'Not Responding'. NOTE: You must stop and re-start the Oracle Agent if the value of the ping multiplier is modified.
Server Code	If you want to start/stop the Oracle Agent associated with this server from the Window's Client, you must first define a Server entry for this agent in the Maintenance \| General \| Object Types \| File Servers window. This entry must be defined with an SFTP protocol, and SSH must be running on the server running the Oracle Agent. Generally, the applmgr user should be used for the Username and Password or Key exchange authentication for logging into the Oracle Agent server. Once the Server entry is created, you may associate the Server Code with this Oracle Agent entry. NOTE: In order to source the environment when SSH logs in, you might be required to add the “./.ssh/rc” command to Post login cmd on the File Servers tab of the Object Type Maintenance window. In this case make sure that the rc file sources your Oracle E-business environment and sets your STAT_JAVA_HOME.
OA Stat Home	This is the STAT_HOME location defined for this Oracle Agent on the Oracle E-Business server.
OA Config File	If you override the default location for the OA config file with a “-s” switch, you must enter it here.
OA Stat Java Home	If you override the default STAT_JAVA_HOME of the Oracle Agent with a “-j” switch, you must enter it here.
Update Date (Read Only)	The date and time this record was last updated
Updated By (Read Only)	The user who last updated this record

When defining servers for an Oracle Applications environment, be aware of the following:

•

When specifying commands that start and stop any of the Oracle Apps services, you can use the appsusername and appspwd parameters to pass the user name and password values specified in the Apps User and Apps Pwd columns in the Oracle Applications Environment Connection Maintenance table. For example, to start a Concurrent Manager in R12, you would specify:
$INST_TOP/admin/scripts %%appsusername%%/%%appspwd%%

•

Each of the four service partitions must be hosted on at least one active server. For a shared APPL_TOP, all four service partitions can be configured on one server.

•

For each active server, at least one of the service partition check boxes must be checked.

•

Only one active server can host the Database Service partition.

Start/Stop Oracle Applications Agents

After you install the Oracle Application Agent on each defined server, you may start/stop the agent, edit the stat.conf file, retrieve OA Agent logs, or change OA Agent log mode from the server list.

•

Oracle Agent Configuration - You may use this button to retrieve your stat.conf file from the OA Agent conf directory. At this point, you may view or edit the content of the file before saving it back to the server.

•

Start/Stop Oracle Agent - You may use this button to start/stop the OA Agent for the selected server. Once the OA agent is started, the Status column for the server will display Started along with a green check mark. Once the OA agent is stopped, the Status column for the server will display Stopped along with a red X.

•

Oracle Agent Logs - You may use this button to retrieve a list of logs from the OA Agent log directory. Once the list is retrieved, you may view the content of the log or export it.

•

Oracle Agent Log Mode - The current log mode defined for the Oracle Agent is displayed in the drop-down and can be changed while the agent is running. Select the desired mode from the drop-down and click the button beside it.

•

Refresh Oracle Agent Status - Once you attempt to start or stop the Oracle Agent, you may use this button to refresh the current status of the OA agent.

•

Show SSH logs - SSH protocol is used to run the Start/Stop commands on the Oracle Agent server. For troubleshooting purposes, you may need to view the SSH logs generated by the commands that are run on the server. Make sure to select this check box before executing the Start or Stop command.

Inactivating Oracle Applications Environments

To inactivate an environment, de-select Active. Stat displays a warning message if the environment is currently part of a migration path.


	CAUTION: Be careful inactivating environments that are part of migration paths. Objects in inactive environments cannot be archived or migrated.

Seleccione su producto:

Con el fin de ofrecerle un mejor servicio, complete el campo Motivo del chat:

Soluciones recomendadas para su problema

Stat 6.2 - System Administration Guide

Testing Environment Connections

Defining Oracle Applications Servers

Start/Stop Oracle Applications Agents

Inactivating Oracle Applications Environments