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 is a two-step process. First you must add the package file that contains the Oracle App Server 10g plug-in JAR file to your system. then you must import the Oracle App Server 10g plug-in JAR file.
The Oracle App Server 10g solution is packaged as a plug-in to the Sun N1 Service Provisioning System (N1 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 Sun N1 Service Provisioning System Supplement CD or from the Sun Download Center.
Once the package file is added to your system, theOracle App Server 10g Plug-In is available for import from two different JAR files. Choose the correct file depending on your situation.
The Oracle App Server 10g plug-in is available for import from two different JAR files. Choose the correct file depending upon your situation.
If you are importing the Oracle App Server 10g plug-in for the first time, use the com.sun.oracle10g_AS_2.0.jar file.
If you have already imported the previous version of the Oracle App Server 10g plug-in, use the com.sun.oracle10g_AS_1.0_2.0.jar file.
Add the package containing the JAR file.
Import the JAR file – Importing the Oracle App Server 10g Plug-In to the N1 SPS Environment
The Oracle App Server 10g plug-in is contained in the SUNWspsoas package.
In a terminal window, become superuser.
Move to the directory containing the plug–in package.
Type the following command and press Return.
# pkgadd -d . SUNWspsoas
The standalone JAR file is in the /opt/SUNWn1sps/plugins/com.sun.oracle10g_AS/ directory. The upgrade JAR file is in the /opt/SUNWn1sps/plugins/com.sun.oracle10g_AS/Upgrade directory.
The Oracle App Server 10g plug-in is contained in the sun-spsoas-2.0-1.noarch.rpm file.
In a terminal window, become superuser.
Move to the directory containing the sun-spsoas-2.0-1.noarch.rpm file.
Type the following command and press Return.
# rpm –i sun-spsoas-2.0-1.noarch.rpm
The standalone JAR file is in the /opt/sun/N1_Service_Provisioning_System/plugins/com.sun.oracle10g_AS/ directory. The upgrade JAR file is in the /opt/sun/N1_Service_Provisioning_System/plugins/com.sun.oracle10g_AS/Upgrade directory.
The Oracle App Server 10g plug-in is contained in the sun-spsoas-2.0.msi file.
Move to the directory containing the sun-spsoas-2.0.msi file.
Double-click the sun-spsoas-2.0.msi file.
The Installer GUI start. The JAR file is copies to the C:\Program Files\N1 Service Provisioning System\plugins\com.sun.oracle10g_AS directory.
To make a given plug-in known to the N1 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 Sun N1 Service Provisioning System 5.2 System Administration Guide.
In the Administrative section of the N1 SPS browser interface main window, click Plug-ins.
In the Action column of the Plug-ins page, click Import.
Browse to the location where you downloaded the JAR file.
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.
If you have not previously used the OS provisioning plug-in, use the following command to import the plug-in:
% cr-cli -cmd plg.p.add -path com.sun.oracle10g_AS_2.0.jar -u username -p password |
If you already have an older version of the OS provisioning plug-in, use the following command to import the plug-in:
% cr-cli -cmd plg.p.add -path com.sun.oracle10g_AS_1.0_2.0.jar -u username -p password |
When you upgrade to a new version of a plug-in, the Common Tasks page for the plug-in is updated to provide links to components that are installed with the new plug-in version. This feature enables you to easily view components that contain the most current features and improvements. Components that rely on old functionality are not linked to from the Common Tasks page.
If you have trouble finding a component that you previously installed, the component was likely created from the previous version of the plug-in. Follow these steps to view or work with a previous version of the component:
Click the appropriate component procedure on the Common Tasks page.
The Component Detail page appears.
On the Component Details page, click Version History.
A list of components and versions appears.
Click the appropriate link.
Before you install and run this plug-in, you must make changes to your Oracle Application Server and N1 SPS Master Server.
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
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:
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
Synchronize the /etc/shadow file.
Use the following command: pwconv
Activate the Oracle user account.
Use the passwd oraclecommand and provide a password for the Oracle user.
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.
Use the same definition of Oracle and dba in all systems.
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_Service_Provisioning_System_5.2/server/config/config.properties directory. Set the following timeout values:
pe.nonPlanExecNativeTimeout=1800 pe.defaultPlanTimeout=18000 userdb.sessionTimeout=10800000
You must restart the Master Server for the timeout changes to occur.
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.
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.
Check the SunSolve site for available patches for the Oracle App Server 10g plug-in. To apply the patch, follow the instructions in the patch README file.