Oracle Applications connection security is controlled by the following user class rights:
The Oracle Application Connection Maintenance table is displayed in a standard maintenance window. To open this window, select Maintenance | General | Oracle Applications Connect.
After defining an environment in the maintenance table, you can make sure that you have entered all the information correctly by clicking Test Connection. This makes Stat establish a connection to the newly defined environment. If successful, Stat immediately disconnects from the environment and displays a “Connection Successful” message. If Stat is unable to connect, it displays an error message. Test Connect verifies that APPS and SYSTEM passwords. For R12.2 it also verifies the WebLogic password.
You can also test connections to multiple databases simultaneously. To test multiple connections, hold the <Ctrl> or <Shift> keys and select the databases you want to test. Then click Test Selected. Stat attempts to establish a connection to each database and reports its results in the Database Test Connect window
Note that when you test a single environment, Stat does not validate the values specified in the fields Host Name, Service Name, or DB Listener Port. If any of these fields are not configured properly, the Stat Central Agent will log an error when the user attempts to migrate an object to or from the environment. When you test multiple connections, however, Stat does test both client and agent connections, including Host Name, Service Name, DB Listener Port or (in the case of Oracle-based environments) TNS Entry.
A user defined character code which uniquely identifies the server in Stat | |
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). | |
Command run by the Stat Oracle Agent to start Concurrent Manager Service | |
Command run by the Stat Oracle Agent to stop Concurrent Manager Service | |
Command line run by the Stat Oracle Agent to stop Web Service | |
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. | |
This is the STAT_HOME location defined for this Oracle Agent on the Oracle E-Business server. | |
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%% |
• |
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. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center