N1 Grid Service Provisioning System User's Guide and Release Notes for the Oracle App Server 10g Plug-In 1.0

Chapter 3 Installing and Configuring the Oracle App Server 10g Plug-In

This chapter explains how to install and configure the Oracle App Server 10g plug-in. The chapter contains the following information:

Acquiring the Oracle App Server 10g Plug-In

The Oracle App Server 10g solution is packaged as a plug-in to the N1 Grid Service Provisioning System (N1 Grid SPS) software. Plug-ins are packaged in JavaTM Archive (JAR) files. The plug-in files for the Oracle App Server 10g solution are available from the N1 Grid Service Provisioning System Supplement CD or from the Sun Download Center.

Adding the Oracle App Server 10g Plug-In to the N1 Grid SPS Environment

To make a given plug-in known to the N1 Grid SPS product, you need to import the plug-in. To import a plug-in, follow these steps as explained in detail in Chapter 5, Plug-In Administration, in N1 Grid Service Provisioning System 5.0 System Administration Guide.

  1. In the Administrative section of the main window, click Plug-ins.

  2. In the Action column of the Plug-ins page, click Import.

  3. Browse to the location where you downloaded the com.sun.oracle10g_AS_1.0.jar file.

  4. Click the Continue to Import button.

When the import completes successfully, a plug-in details page appears that shows you the objects that the plug-in provides.

You can also import a plug-in archive file from the command line. Use the following command:


% cr-cli -cmd plg.p.add -path com.sun.oracle10g_AS_1.0.jar -u username -p password

Customizing the Solution for Your Environment

Before you install and run this plug-in, you must make changes to your Oracle Application Server and N1 Grid SPS Master Server.

ProcedureHow to Configure the Oracle Application Server

Steps
  1. Modify the /etc/system file.

    Add the following lines to your /etc/system file and reboot:

    * included for Oracle 
    set semsys:seminfo_semmap=80 
    set semsys:seminfo_semmni=2200
    set semsys:seminfo_semmns=2200 
    set semsys:seminfo_semmnu=2000 
    set semsys:seminfo_semmsl=256 
    set semsys:seminfo_semopm=210 
    set semsys:seminfo_semume=600 
    set shmsys:shminfo_shmmax=4294967295 
    set shmsys:shminfo_shmmin=100 
    set shmsys:shminfo_shmmni=100 
    set shmsys:shminfo_shmseg=100
  2. Add an Oracle database group to the /etc/group file.

    Edit the /etc/group file on the system on which you intend to install the Oracle Application Server product and add the following line:

    dba::120:
  3. Add an Oracle user to the /etc/passwd file.

    Edit the /etc/passwd file on the system on which you intend to install the Oracle Application Server product and add the following line:

    oracle:x:500:120::/export/home/oracle:/bin/csh 
  4. Synchronize the /etc/shadow file.

    Use the following command: pwconv

  5. Activate the Oracle user account.

    Use the passwd oraclecommand and provide a password for the Oracle user.

  6. If your system is in NIS and an Oracle account or dba group is already in the NIS maps, verify the configuration of the /etc/nsswitch.conf file.

    Make sure that files appears before nis in the passwd entry in the /etc/nsswitch.conf file.


    Note –

    Use the same definition of Oracle and dba in all systems.


Master Server Timeout Settings

Some of the plans that are provided with this plug-in require significant time to execute. As a result, you should verify that the timeout values for the Master Server are long enough to allow the plans to run.

Edit the provisioning system config.properties file on the Master Server. By default, the file is in the /opt/SUNWn1sps/N1_Grid_Service_Provisioning_System_5.0/server/config/config.properties directory. Set the following timeout values:

pe.nonPlanExecNativeTimeout=1800
pe.defaultPlanTimeout=18000
userdb.sessionTimeout=10800000

Note –

You must restart the Master Server for the timeout changes to occur.


Remote Agent User and Group

When you install the Remote Agent, set root as the user and group that own the installation. Also select yes when asked if you want to allow the setuid functionality.

Remote Shell for Cluster Functionality

To enable the use of clustering functionality in the Oracle environment, systems that are part of a cluster must be able to communicate remotely with each other through a remote shell (rsh command). To enable remote functionality, create the rhosts file in the home directory of the oracle account and add the line + oracle to it.