This chapter explains how to install and configure the SAP plug-in. This chapter discusses the following topics:
The general tasks you need to do before installing the SAP plug-in are:
Install the SPS Master Server (MS), Remote Agent (RA), and Command Line Interface (CLI) on the Master Server host.
For more information, see the Sun N1 Service Provisioning System 5.2 Installation Guide.
Install the SPS Remote Agent (RA) on all SAP machines and prepare them.
For more information, see Non-Interactive Installation of a Remote Agent on Linux and UNIX Systems in Sun N1 Service Provisioning System 5.2 Installation Guide.
Install all SAP central instances and Oracle databases.
Make sure they are virtualized.
For more information, see the SAP HA Switchover Document for an overview of virtualization and How to Enable Failover SAP Instances to Run in a Cluster in Sun Cluster Data Service for SAP Guide for Solaris OS.
For instances that are under the control of Sun Cluster, perform the following steps:
Ensure that the clusters are installed and set up correctly.
Ensure that all Sun Cluster data services are installed.
Ensure that all Sun Cluster resource groups and resources are set up correctly.
For more information, see Sun Cluster Software Installation Guide for Solaris OS.
For instances that are under the control of SAP AC, make sure the server is installed and set up correctly.
Although the following items can be managed locally on the file system, they should be managed by NIS, NIS+, or LDAP.
Update all SAP machines' /etc/services file with port information for all SAP instances.
Ensure that all SAP users, (sidadm) are present on the system. Users are defined locally in /etc/password.
Ensure that all logical host names are present on the system. Logical host are defined in /etc/hosts.
Group information must be maintained. Groups are defined in /etc/group.
An appropriate project must be created for each resource. See the project(4) man page for more details on the project file and related information on creating a project.
Directories for SAP must be present on the servers. You can create these directories in one of the following methods:
Use the plug-in nfsshare or nfsmount components
Mount manually through NFS
Create the directories manually on each target servers
Use automounter
Management of the automounter map is required.
Acquiring the SAP plug-in is a two-step process. First, you must add the package file that contains the SAP plug-in JAR file to your system. Then you must import the SAP plug-in JAR file.
The SAP plug-in is packaged as a plug-in to the Sun N1 Service Provisioning System software. The plug-in files for the SAP plug-in are available from the Sun N1 Service Provisioning System 5.2 Supplement CD or from the Sun Download Center.
Add the file containing the JAR file:
Import the JAR file - Importing the SAP Plug-In.
The SAP plug-in is contained in the SUNWspssap package.
Log in to Master Server.
Become superuser.
Move to the directory containing the plug-in package.
Type the following command and press Return.
# pkgadd -d package_directory SUNWspssap
The JAR file is in the /opt/SUNWn1sps/plugins/com.sun.sap/ directory.
To make a given plug-in known to the Sun N1 Service Provisioning System 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 browser interface main window, click Plug-ins.
In the Action Column of the Plug-ins page, click Import.
Click the Browse button and navigate to the location of the JAR file.
Select the JAR file and click Open.
Click the Continue to Import button.
When the import completes successfully, a plug-in details page appears and shows you the objects that the plug-in provides.
You can also import a plug-in archive file by using the command line.
To import a plug-in file from the CLI, type:
% cr_cli -cmd plg.p.add -path plugin-filename -u username -p password |
After the plug-in is imported, perform the following steps:
These steps should be performed prior to importing the SAP plug-in.
Review the ReadMe.txt file to make sure that all configuration tasks have been completed.
Create session variables.
These variables are used when maintaining SAP instances in the SAP AC environment and creating SAP users or logical hosts in LDAP.
SAP_DEFAULT_AC_ADMIN_PASSWORD
SAP_DEFAULT_AC_ADMIN_USER
SAP_DEFAULT_AC_PORT
SAP_DEFAULT_AC_SERVER
AUTHENTICATE_ACC_SERVER_CERT
For more information about session variables, see How to Create Session Variables.
Create a virtual host with the Master Server as its parent.
This is created for the purpose of running the SPS CLI.
If virtual host cliHost exists and its host type is com.sun.was#cliHT, do not create another cliHost.
For more information, see Virtual Hosts in Sun N1 Service Provisioning System 5.2 System Administration Guide.
In the Host Setup section of the browser interface main window, click Hosts.
Type cliHost in the Host field.
Select the com.sun.sap#cliHT host type.
Click Create.
Select the Virtual Host option.
Modify the cliLoc attribute to the fully qualified path of the CLI.
For example, /SPS–INSTALL–PATH/cli/bin/cr_cli.
Set the Master Server as the Virtual Host parent.
Click Save.
Add the following lines to the /SPS–INSTALL–PATH//server/config/config.properties file:
config.allowSessionIDOnHosts=masterserver pe.defaultPlanTimeout=6000 pe.nonPlanExecNativeTimeout=2400 |
The config.allowSessionIDOnHosts line lets the plug-in communicate with the Master Server through the Sun N1 Service Provisioning System Remote Agent/CLI interface.
The pe.defaultPlanTimeout line is in seconds. Add this line if your site needs to increase the default plan from its 30 minute, 1800 second, value.
The pe.nonPlanExecNativeTimeout line is in seconds. Add this line if your site needs to increase the time for execNative time outs.
The config.properties file is in the SPS–INSTALL–PATH/server/config directory.
Restart the Master Server after the changes have been made to the config.properties file.
Repeat this procedure for each session variable that you create.
Session variables need to be set only if you have an SAP AC environment and you intend to administer components by using this plug-in.
From the Common Tasks page, click the Session Variables link.
Click the Create link.
Create the session variable.
Click Save.
After you have installed the SAP plug-in, perform the tasks in this section.
In the Common Tasks section of the N1 SPS browser interface, click Hosts.
Click Create.
Type the host name.
Set the Host Type to com.sun.sap#SAPHT.
Type a comma-delimited list of the environment types that can exist on this Remote Agent in the envType field.
(Optional) Type the SAPS value.
Select the Include Remote Agent on This Physical Host check box.
Select a connection type.
Type the IP address or name.
Type a port number.
Click Save.
For more information, see Chapter 2, Managing Hosts, Host Types, Host Sets, and Host Searches, in Sun N1 Service Provisioning System 5.2 System Administration Guide.
The following should be performed to establish the environment for the SAP plug-in:
Create SAP Hosts. For more information, see How To Create SAP Hosts.
Prepare the Master Server and Remote Agents.
For more information, see How to Prepare a Physical Host in Sun N1 Service Provisioning System 5.2 System Administration Guide.
Perform any of the Utilities for SAP group tasks, as necessary.
Create a group component.
Other components set dependency on the group component.
For more information, see Creating and Managing Groups.
Add a logical host component to the group.
For more information, see Creating and Managing Logical Hosts
Add a storage management component to the group for groups that also contain an SAP Central Instance or database components.
For more information, see Creating and Managing HA Storage Devices.
Add an NFS share component to the group for groups that also contain an SAP Central Instance or database components.
For more information, see Sharing and Managing Network File Systems.
Add a Central Instance or Oracle component to the group.
For more information, see Creating and Managing SAP Central Instances or Creating and Managing Oracle Databases.
Add an NFS Mount component for groups that also contain SAP Application Server.
This section describes how to delete a plug-in from the Sun N1 Service Provisioning System. For more information, see Deleting Plug-Ins in Sun N1 Service Provisioning System 5.2 System Administration Guide.
Delete all objects created by all versions of the plug-in.
These objects include the system services that are installed automatically when a host is prepared.
In the Common Tasks section of the N1 SPS browser interface, click Plans.
Navigate to the RemoveSAPSystemServicePlan plan.
Click the Details link.
Click Run.
Select target host or target host set.
Click the Run Plan (Includes Preflight) button.
From the CLI directory, type the following command.
./cr_cli -cmd plg.p.del -ID plugin-ID -u admin -p password |
For example, ./cr_cli -cmd plg.p.del -ID 010011242111-1146106455699-00215-1170512625 -u admin -p admin
Check the SunSolve site for available patches for the SAP plug-in. To apply a patch, follow the instructions in the patch README file.