2
Post-Installation Configuration

After you have installed the Management Pack for Oracle Applications, you need to configure the following software:

• Intelligent Agent on the managed nodes (for example, Internal Concurrent Manager node and Applications Database node)

• Oracle Management Server

• Oracle Enterprise Manager console

  Note: All the configuration tasks listed in this chapter are required to bring the Management Pack for Oracle Applications online. A checklist is provided at the end of this chapter to help you ensure that each step has been performed correctly.

The following sections provide detailed information about each of these configuration tasks.

Intelligent Agent on the Managed Node

On the managed node you must:

Apply Oracle Applications patch for bug #1302931 or bug #1371501, depending on the version of your Oracle Applications instance

Configure Windows NT security for the Enterprise Manager job system (for Windows NT targets only)

Enable disk statistics collection for Capacity Planner and Performance Manager on Windows NT (for Windows NT only)

Configure Oracle Applications Sign-On Auditing profile

Start the Intelligent Agent on the managed node

Note: If you are running the Concurrent Processing Server in Parallel Concurrent Processing mode (that is, distributed across several host computers), configure as a managed node only the host which runs the Internal Concurrent Manager. In this configuration, the Applications Disk Free event will only report on the disk space on this node.

Applying Oracle Applications Patch for Bug #1302931 or Bug #1371501

The patch for bug #1302931 or bug #1371501 must be applied to the Oracle Applications instance for it to be managed by the Management Pack for Oracle Applications. The patch for bug #1302931 applies to release 10.7 of Oracle Applications and the patch for bug #1371501 applies to releases 11.0 and higher of Oracle Applications. These patches must be applied to the $APPL_TOP directory of each of the Concurrent Processing Servers.

Note: The fix for bug #1302931 is a server-side patch, which applies identically to 10.7 SC (Smart Client), 10.7 NCA (Network Computing Architecture), and 10.7 character mode deployments.

Please use your normal channels for pulling patches for Oracle Applications. The patch for bug #1302931 or bug #1371501 is a prerequisite for using the Management Pack for Oracle Applications.

Configuring Windows NT Security for the Enterprise Manager Job System

You can use the Oracle Intelligent Agent to perform a variety of jobs on the managed node, such as starting or stopping the Concurrent Manager, or running fix-it jobs to correct problems detected by Advanced Event Tests.

To use this feature against a Concurrent Processing Server on Windows NT, you must grant the Log on as a batch job privilege to the Windows NT user whose account will be used to run these jobs. If you know what user accounts you will be using for this purpose, configure them now. If not, perform this step later when you enter preferred node credentials to be used on this node by Oracle Enterprise Manager.

Note: On Windows NT, the Internal Concurrent Manager is created as a service. Only users belonging to the Administrators group are allowed to start and stop services.

To grant a Windows NT user the Log on as a batch job privilege, do the following:

1. Select Start=>Programs=>Administrative Tools=>User Manager.

2. Highlight the user to be granted the privilege.

3. Choose Policies=>User Rights.

4. Check the Show Advanced User Rights box.

5. In the Right field, select the Log on as a batch job right.

6. Click Add.

Jobs submitted using user names without the Log on as a batch job privilege fail with the status of VNI Authentication Error. Refer to the Oracle Intelligent Agent User's Guide for information regarding the Logon as a batch job privilege.

Enabling Disk Statistics Collection for Capacity Planner and Performance Manager on Windows NT

To collect disk statistics on Windows NT, type the following at the DOS prompt:

diskperf  -Y 

Disk statistics will be enabled the next time the system is restarted.

Note: If you want to view CPU usage of your concurrent programs using Performance Manager, the Applications database must have the timed_statistics parameter, located in the init.ora file, turned on. See your database documentation for details. Activating this parameter may have a performance impact on your database.

Configuring Oracle Applications Sign-On Auditing

To monitor Applications form sessions with the Management Pack for Oracle Applications, you must set the Oracle Applications "Sign-On: Audit Level" profile to FORM, using your normal Applications administration tools. Oracle suggests that you periodically run the Purge Sign-on Audit Data concurrent program to purge unwanted historical data from your FND tables.

Starting the Intelligent Agent on the Managed Node

To start the Intelligent Agent on the managed node, see the appropriate sections that follow:

• "Managing the Intelligent Agent on UNIX"

• "Managing the Intelligent Agent on Windows NT"

• "Managing the Intelligent Agent from the Windows NT Command Prompt"

Managing the Intelligent Agent on UNIX

On UNIX, Oracle Enterprise Manager uses the agentctl command to start and stop the Intelligent Agent. The relevant agentctl commands to control the UNIX Intelligent Agent are listed in the following table.

Note: Verify that your Oracle home environment variable is set to the Intelligent Agent's Oracle home before running agentctl. Also, Oracle suggests you perform the following steps: Construct an environment file for use with this agent separate from the environment files you use for other Oracle Applications on this node. Ensure that the PATH variable includes the $ORACLE_HOME/bin directory. This directory must be at the beginning of the list of directories. Do not set any values for the ORA_NLS and ORA_NLS33 environment variables. You will run into trouble if these are set to the directories Oracle Applications uses for these variables.

If you want to...	Enter the command...
Start the agent on UNIX platforms	agentctl start agent
Stop the agent on the UNIX platform	agentctl stop agent
Verify status of the agent	agentctl status agent or ps -ef | grep dbsnmp
Turn on debugging for data collection	1) setenv VP_DEBUG 1 2) agentctl start agent Collection activity is logged into dbsnmp.nohup.

Managing the Intelligent Agent on Windows NT

On Windows NT, the Intelligent Agent runs as a Windows NT service. The steps to control the Intelligent Agent are listed in the following table.

If you want to...	Do the following...
Start Intelligent Agent	Start=>Settings=>Control Panel=>Services=>Oracle<name of Oracle home>Agent=>Start
Stop Intelligent Agent	Start=>Settings=>Control Panel=>Services=>Oracle<name of Oracle home>Agent=>Stop
Verify status of Intelligent Agent	Start=>Settings=>Control Panel=>Services=>Oracle<name of Oracle home>Agent=>look at Status column or View the Windows NT Task Manager to see the dbsnmp.exe process information

Managing the Intelligent Agent from the Windows NT Command Prompt

To start or stop the Intelligent Agent from the command prompt, enter the appropriate command. From the command prompt, you can also verify that the service is running.

If you want to...	Enter the following command
Start the Intelligent Agent from the prompt	net start <agent service>
Stop the Intelligent Agent from the prompt	net stop <agent service>
Verify status of the Intelligent Agent from the prompt	net start

The <agent service> is composed of the word Oracle, followed by the name of the Oracle home (for example, ORCLHome), and concluded with the word Agent. OracleORCLHomeAgent, is an example of an agent service.

Note: Do not use the agentctl command to start the Intelligent Agent for Windows NT.

Oracle Management Server (OMS)

After you install the Oracle Management Server for the Management Pack for Oracle Applications, you must:

Create the Oracle Management Server repository, if not already created

Start the Oracle Management Server

(Optional) Run the Management Pack for Oracle Applications through a web browser

Creating the Oracle Management Server Repository

When you create your Oracle Management Server, you must provide the repository address in the <host:port:sid> format, rather than using an Oracle Net service name or leaving the name field blank to indicate a local default database. The host portion should be a fully qualified DNS name, for example, myhost.us.acme.com. Otherwise, Capacity Planner and Performance Manager clients from other DNS domains (for example, uk.acme.com) will not be able to connect to the server. This step ensures that all Enterprise Manager applications can connect to the Oracle Management Server repository when needed.

If you are using a previously created repository, use the Enterprise Manager Configuration Assistant to verify that the Oracle Management Server is using the <host:port:sid> syntax for its repository address, and modify it to use this syntax if needed. To do this task, start the Configuration Assistant, as follows:

• To start the Configuration Assistant on Windows NT, select Start=>Programs=><Enterprise Manager Home>=>Enterprise Manager=>Configuration Assistant

• To start the Configuration Assistant on UNIX, run <Enterprise Manager Oracle Home>/bin/emca

  Select the Edit Configuration Parameters option and click Next.

The existing Oracle Management Server connection parameters are now displayed. The bottom parameter ("Service") indicates the repository service. If this is already in the <host:port:SID> syntax, nothing further needs to be done, and you can exit the tool.

If this line instead contains a name (for example, omsdb or omsdb.acme.com) or is blank, you need to do the following:

1. Change the line to contain the fully-qualified host name on which the Oracle Management Server repository database is run. Insert a colon after the host name.

2. Type the port number that the TNS listener for this database is using. Insert a colon after the port number.

3. Type the SID of this database. The resulting line looks like:

   omhost.acme.com:1521:ORCL
   
   

4. Click Next.

5. Click Finish to save the changes.

Starting the Oracle Management Server

To start the Oracle Management Server, see the appropriate section that follows:

• "Managing the Oracle Management Server on UNIX"

• "Managing the Oracle Management Server on Windows NT"

  Note: If you have problems starting the Oracle Management Server, see the Oracle Enterprise Manager Configuration Guide for information.

Managing the Oracle Management Server on UNIX

On UNIX, Oracle Enterprise Manager uses the oemctl command to start and stop the Oracle Management Server. The relevant oemctl commands to control the UNIX Oracle Management Server are listed in the following table. In all cases, the command string is case-sensitive and must be entered with lowercase characters.

If you want to...	Enter the command...
Start Oracle Management Server	oemctl start oms
Stop Oracle Management Server	oemctl stop oms <EMAdministratorName>/<EmPassword> where EMAdministratorName is your Oracle Enterprise Manager super administrator name (for example, sysman). EmPassword in your Oracle Enterprise Manager super administrator password (for example, oem_temp). EmPassword is case-sensitive and must be entered in the same case as it was originally entered.
Verify status of Oracle Management Server	oemctl status oms <EMAdministratorName>/<EmPassword>[@<hostname>] where EMAdministratorName is your Oracle Enterprise Manager super administrator name (for example, sysman). EmPassword is your Oracle Enterprise Manager super administrator password (for example, oem_temp). EmPassword is case-sensitive and must be entered in the same case as it was originally created. hostname is the machine where your Oracle Management Server is running. You do not need to enter the host name if the Oracle Management Server is running locally.

Note: If the need arises, you can reset the superuser password by running the vduResetSysman.sql script from the Enterprise Manager master account. The script is located in the ORACLE_HOME/sysman/admin directory.

Managing the Oracle Management Server on Windows NT

On Windows NT, the Oracle Management Server runs as a Windows NT service. The steps to control the Oracle Management Server are listed in the following table.

If you want to...	Do the following...
Start Oracle Management Server	Start=>Settings=>Control Panel=>Services=>Oracle<name of Oracle home>ManagementServer=>Start
Stop Oracle Management Server	Start=>Settings=>Control Panel=>Services=>Oracle<name of Oracle home>ManagementServer=>Stop NOTE: You must have the Windows NT operating system administrator privilege to stop the Oracle Management Server.
Verify status of Oracle Management Server	Start=>Settings=>Control Panel=>Services=>Oracle<name of Oracle home>Management Server=>look at Status column or oemctl status oms

The status information of the Oracle Management Server includes the following:

• Overall status of the Oracle Management Server

• Time period the Oracle Management Server has been up and available

• Statistics regarding the performance of the Oracle Management Server

Using CPTA Through the Oracle Management Server

When launching CPTA in standalone mode, you have the option of using CPTA through the Oracle Management Server. To use the Concurrent Processing Tuning Assistant through the Oracle Management Server, you must have an entry defined in the tnsnames.ora file where the Oracle Management Server resides.

If you do not have such an entry in the tnsnames.ora file, you must add a connection to the Oracle Management Server using the Add Connection option available from the toolbar.

Running the Management Pack for Oracle Applications through a Web Browser

Windows NT clients can run the Oracle Enterprise Manager console, along with all Management Pack for Oracle Applications tools, through a web browser without installing any software on the client node. The only exception is Capacity Planner, which can only run as a client install.

To run in this mode of operation, some special setup steps must be taken to make the Enterprise Manager software available from a Web server. Refer to the Web browser information in the Oracle Enterprise Manager Configuration Guide for a complete description of how to set up and run Oracle Enterprise Manager in this configuration.

Oracle Enterprise Manager Console

After you install the client software for the Management Pack for Oracle Applications, you must:

1. Start the Oracle Enterprise Manager console.

2. Discover nodes and services to manage in the console.

3. Configure the oapps.ora file on the concurrent manager node.

4. Discover concurrent managers in the console.

5. Set preferred credentials.

6. Start the applications delivered with the Management Pack for Oracle Applications.

The following sections describe these tasks in detail.

Starting the Oracle Enterprise Manager Console

1. Start the Oracle Enterprise Manager console.
   • On Windows NT, start the console from the Windows Start menu under the appropriate Oracle home.

   • On UNIX, start the console from the command line by typing:

     oemapp console
     

     The command string is case-sensitive and must be entered with lowercase characters.

2. If you are connecting to the Oracle Management Server for the first time, at the first login dialog, type in the default credentials for the super administrator account.

   Administrator = sysman

   Password = oem_temp

   Note: Should you forget the Enterprise Manager password after you set it, run the vduResetSysman.sql script to reset the password.

3. From the Oracle Management Server pull-down list, select an Oracle Management Server which is configured for Oracle Applications management.

   If the name of the Oracle Management Server you want to use does not appear, do the following:

   1. Click the Management Servers button. The Management Servers dialog is displayed.

   2. Click the Add button. The Add Management Server dialog is displayed.

   3. Type in the host name of the computer on which the Oracle Management Server you want to add is running, and click OK.

   4. Select the Oracle Management Server from the pull-down list.

4. After the initial login, a security login dialog is displayed where you can change your password. Change your password immediately.

   Note: Passwords cannot have more than 8 characters.

Discovering Nodes and Services

During the start up of the Oracle Management Server, the manageable services on the machine where the Oracle Management Server is running are automatically discovered. The Console Navigator shows all these discovered services.

To discover additional nodes:

1. Select Discover Nodes from the Console's Navigator menu.

2. Enter the host name of the node in the text window of the Discover Nodes dialog. You can discover multiple services at one time by entering each node you want to discover on a new line within the text window.

3. Click OK to continue.

If a node cannot be discovered, it may be because the node is down or the node is not running an Intelligent Agent. Also note that you must be using the TCP/IP network protocol.

Configuring the oapps.ora File on the Concurrent Manager Node

There are several manual steps you must perform before discovering an Oracle Applications instance. These steps are:

1. In the Enterprise Manager Console, discover the node where the Oracle Applications database resides, as described in "Discovering Nodes and Services".

2. Make a note of the fully qualified database name as it appears in the Enterprise Manager console, for example, Production_DB.acme.com. You will need this information later.

3. Go to the Concurrent Processing Server node and locate the Oracle home of the Intelligent Agent. For the Intelligent Agent to discover the Concurrent Processing Server, you must edit the oapps.ora file. The oapps.ora file is installed into the following directory in the Intelligent Agent's Oracle home:

   $ORACLE_HOME/network/agent/config
   
   

   The oapps.ora file is an input file used to associate Oracle Applications instances with information about the instances.

   The file format is:

   <type> <WS> <dbname> <WS> <envfile> <WS> <startup information> <NL>
   

   Variable	Definition
   <type>	Entry type. Currently only cmanager is recognized; cmanager denotes Concurrent Manager Server.
   <WS>	White space (one or more blanks or tabs).
   <dbname>	Applications database name. This name is also used as the Applications instance name. This must be exactly the same (fully qualified) name as the database name that appears in the Enterprise Manager console.
   <envfile>	Fully qualified path and file name of the Applications environment file. This file must set up the entire Applications environment, including all required database environment variables, and all variables from the Applications environment file located in the APPL_TOP directory. Note: For the Windows NT 10.7 instance, which does not have the Applications environment file, type a dummy file name. This file name can reference an empty file or a non-existing file.
   <startup information>	For Windows NT. Name of the ICM service in the NT Services panel. For UNIX. Fully qualified path to the ICM startup script. Typically this is the oemstart.sh script in the $FND_TOP/bin directory, installed when you apply the patch for bug #1302931 or bug #1371501.
   <NL>	New line, that is, one line per entry. Note: You can have multiple entries in a single oapps.ora file.

   Lines starting with a pound sign (#) as the first non-WS character are comments and are ignored.

   An example of an entry for Windows NT is:

   # entry for discovering the headquarters production applications instance
   cmanager hqprod.world C:\home\admin\appsenvfile ICMprod
   
   

   An example of an entry for UNIX is:

   # entry for discovering the headquarters production applications instance
   cmanager hqprod.world /appltop/APPSORA.env /appltop/fnd/11.0/bin/oemstart.sh
   
   

4. Stop and start the Intelligent Agent as described earlier in this chapter. This will force the Intelligent Agent to read the oapps.ora file and recognize the existence of the Concurrent Manager on this node.

5. After starting the Intelligent Agent, verify that the Intelligent Agent successfully discovered the concurrent manager by inspecting the Intelligent Agent's $ORACLE_HOME/network/agent/services.ora file. This file should contain an entry of the form:

   <applications instance name> = (oracle_sysman_cmanager, <hostname>, 
   <environment file name>, <startup information>)
   
   

   If such a line does not appear in the services.ora file, refer to Appendix A, "Troubleshooting", or the Oracle Intelligent Agent User's Guide for additional information.

   Note: It is possible to name the concurrent manager instance using a name that is different from the name of its corresponding database. To do this, you must define a tnsnames.ora entry for the Oracle Applications database with the name you want to use for the concurrent manager in the Console. Use this name in the oapps.ora file and verify that every oracle home (for example, Enterprise Manager Console, OMS, and Agent) has this tns alias defined in its tnsnames.ora file.

Discovering Concurrent Managers in the Console

After configuring the oapps.ora file, return to the Enterprise Manager console. Right mouse click on the node where the Concurrent Processing Server resides and select Refresh Node. Upon completion, you will see a new Concurrent Manager appear in the console.

Setting Preferred Credentials

You must enter preferred credentials for both the concurrent manager and the managed node. The Intelligent Agent uses these credentials when running jobs on the managed node.

To enter preferred credentials, select System=>Preferences=>Preferred Credentials on the Oracle Enterprise Manager console main window. To manage Concurrent Manager Servers, you must add preferred credentials for each concurrent manager discovered, and you must add node credentials for the host computer on which they run. All the fields are mandatory. Refer to the Oracle Enterprise Manager console help and the Oracle Enterprise Manager Configuration Guide for information about setting preferred credentials.

Note: Node credentials for Windows NT nodes must be for users who are granted the Windows NT Log on as a batch job privilege. See "Configuring Windows NT Security for the Enterprise Manager Job System" for details on configuring this privilege.

Starting Applications in the Management Pack for Oracle Applications

After starting the Oracle Enterprise Manager console, you can now start the applications in the Management Pack for Oracle Applications. The following table lists these applications and where to find the appropriate information.

Step	Where to Find the Information
Starting Oracle Performance Manager	See "Starting Oracle Performance Manager".
Starting Oracle Capacity Planner	See "Introduction to Oracle Capacity Planner".
Starting Concurrent Processing Tuning Assistant	See "Concurrent Processing Tuning Assistant".
Using Advanced Events	See "Oracle Applications Advanced Event Tests".

Configuration Checklist

The following table provides a checklist of steps to perform when configuring the Management Pack for Oracle Applications.

Table 2-1 Configuration Checklist  

Intelligent Agent on the Managed Node (Concurrent Manager Node)

Install software on the managed node See the Oracle9i Installation Guide Release 9.0.1 for your particular platform for instructions on installing the Oracle Intelligent Agent.

Apply Oracle Applications patch for bug #1302931 or bug #1371501 See "Applying Oracle Applications Patch for Bug #1302931 or Bug #1371501".

Configure Windows NT security See "Configuring Windows NT Security for the Enterprise Manager Job System".

Enable disk statistics collection (Windows NT only) See "Enabling Disk Statistics Collection for Capacity Planner and Performance Manager on Windows NT".

Start the Intelligent Agent in the newly installed Oracle Home See "Starting the Intelligent Agent on the Managed Node" and information in the file itself.

Oracle Management Server

Install software Skip this step if Oracle Management Server Release 9.0.1 is already running.

Create an Oracle Management Server repository Skip this step if Oracle Management Server Release 9.0.1 is already running. The installation will guide you through these steps. See "Creating the Oracle Management Server Repository" or refer to the Oracle Enterprise Manager documentation for additional details.

Start the Oracle Management Server See "Starting the Oracle Management Server".

(Optional) Run the Management Pack for Oracle Applications through a web browser See "Running the Management Pack for Oracle Applications through a Web Browser".

Oracle Enterprise Manager Console

Install software

Start the Oracle Enterprise Manager Console See "Starting the Oracle Enterprise Manager Console".

Discover managed nodes (Oracle Applications Database Node) See "Discovering Nodes and Services".

Configure the oapps.ora file on the Concurrent Manager node See "Configuring the oapps.ora File on the Concurrent Manager Node" .

Discover concurrent managers in the console See "Discovering Concurrent Managers in the Console".

Set preferred credentials See "Setting Preferred Credentials".

Start and use the Management Pack for Oracle Applications tools See "Starting Applications in the Management Pack for Oracle Applications".