Creating and Managing SAP Message Servers

The SAP Message Server is responsible for communication between the application servers. The SAP Message Server passes requests from one application server to another within the system.

The SAP Message Server also contains information about application server groups and the current load balancing within them. The SAP Message Server uses this information to choose an appropriate server when a user logs on to the system.

SAP AC is not supported.

This section describes the following tasks:

• How to Create an SAP Message Server

• How to Delete an SAP Message Server

• How to Start an SAP Message Server

• How to Stop an SAP Message Server

• How to View All SAP Message Server

• How to Check the Online Status of an SAP Message Server

• How to Check the Offline Status of an SAP Message Server

How to Create an SAP Message Server

This task creates an SAP Message Server component in SPS database. The SAP Message Server is created by the user at the OS level outside the SPS plug–in.

This task is a markOnly task.

Steps

1. In the Common Tasks section of the N1 SPS browser interface, click SAP.

2. In the SAP Message Server section of the SAP Tasks page, click Create.

3. Click Run.

4. In the Plan Parameters table, select the variable settings for the Message Server component.

   • If the variable settings have been created for this component, select the appropriate settings from the drop-down menu.

   • If the variable settings are not available from the drop-down menu:

     1. Click Select From List.

        The Select Variable Settings From List window displays.

        • To create a new variable settings set, click Create Set and type a Set Name.

          The following list provides commonly updated variables for the Enqueue Server component. To create a value for the component variable, click the check box in the component variable's row.

          ---

          Note –

          For information about component variables ending in UserExit, see User Exits.

          ---

          groupName

          This is a required field.

          ---

          Note –

          In the Sun Cluster environment, the groupName must equal the Sun Cluster resource group name.

          ---

          groupDescription

          A description of the group.

          resourceName

          Required for default and Sun Cluster environment. The resourceName must equal the Sun Cluster resource name for the Sun Cluster envType.

          envType

          Identifies whether this component will be deployed to a default or Sun Cluster environment. Value can be sc or default. Default value: default.

          createdBy

          Identifies the installer of the component.

          sapSid

          Required for the default and Sun Cluster environment. The SAP system ID consists of three uppercase alphanumeric characters. The first character must be a letter.

          msgLhName

          Required for the default and Sun Cluster environment. Logical host name for the message server.

          instanceName

          Required for the default and Sun Cluster environment. Name of the instance (INSTANCE_NAME in SAP start profile). The name must contain at least three uppercase alpha characters and two numeric characters. For example, ABC01.

          srmProject

          The Solaris Resource Management (SRM) project name. Default value: default.

     2. Click Save.

   • To use component variables from another component, click Import Set.

     For more information about importing variable sets, see How to Run a Plan in Sun N1 Service Provisioning System 5.2 Operation and Provisioning Guide.

5. Select target host or target host set.

6. Click the Run Plan (Includes Preflight) button.

   The Deployment Results page is displayed. If the plan fails, error messages are displayed.

   ---

   Note –

   There is no code verification to enforce the required fields for the Sun Cluster environment when the components are created in the Sun N1 Service Provisioning System.

   ---

How to Delete an SAP Message Server

Plan to delete an SAP Message Server component in the SPS database. The SAP Message Server created by the user at the OS level is not deleted.

This is a markOnly task.

Steps

1. In the Common Tasks section of the N1 SPS browser interface, click SAP.

2. In the SAP Message Server section of the SAP Tasks page, click Delete.

3. Click Run.

4. Select target host or target host set.

5. Provide the plan variable.

   Install path of the message server

   This is a required field. If you do not know the install path, return to the SAP Tasks page and click the View All link.

6. Click the Run Plan (Includes Preflight) button.

   The Deployment Results page is displayed. If the plan fails, error messages are displayed.

How to Start an SAP Message Server

Prior to starting the SAP Message Server, the plug-in does not check any dependencies. After the startup, the plug-in verifies that the main process is running. The main process for the SAP Message Server is the message server process.

Steps

1. In the Common Tasks section of the N1 SPS browser interface, click SAP.

2. In the SAP Message Server section of the SAP Tasks page, click Start.

3. Click Run.

4. Select target host or target host set.

5. Provide the plan variable.

   Install path of the message server component

   This is a required field. If you do not know the install path, return to the SAP Tasks page and click the View All link.

6. Click the Run Plan (Includes Preflight) button.

   The Deployment Results page is displayed. If the plan fails, error messages are displayed.

How to Stop an SAP Message Server

If the SAP component is offline, the plan will complete successfully without any further action. If the SAP component is not offline, the plan stops the SAP component.

If a normal stop fails and you have selected the Force Stop option, the plan will perform a hard stop by “killing” the main process. The plan then verifies that the SAP component is offline. If it is, the plan completes successfully.

If the SAP component is not offline, the plan fails. The process used to determine the status is the message server process.

Steps

1. In the Common Tasks section of the N1 SPS browser interface, click SAP.

2. In the SAP Message Server section of the SAP Tasks page, click Stop.

3. Click Run.

4. Select target host or target host set.

5. Provide the plan variables.

   Install path of the SAP message server component

   This is a required field. If you do not know the install path, return to the SAP Tasks page and click the View All link.

   Force stop SAP Message Server after the graceful stop failed in the default environment

   This option is selected by default.

6. Click the Run Plan (Includes Preflight) button.

   The Deployment Results page is displayed. If the plan fails, error messages are displayed.

How to View All SAP Message Server

Steps

1. In the Common Tasks section of the N1 SPS browser interface, click SAP.

2. In the SAP Message Server section of the SAP Tasks page, click View All.

   The Hosts Where Installed table is displayed.

How to Check the Online Status of an SAP Message Server

If the main processes are present on the system, the resource is considered online. If any of the main processes are not present on the system, the plug-in identifies the resource as offline.

The main process for the SAP Message Server is the message server process.

Steps

1. In the Common Tasks section of the N1 SPS browser interface, click SAP.

2. In the SAP Message Server section of the SAP Tasks page, click Online Status.

3. Click Run.

4. Select a target host or target host set.

5. Provide the plan variable.

   Install path of the SAP message server component

   This is a required field. If you do not know the install path, return to the SAP Tasks page and click the View All link.

6. Click the Run Plan (Includes Preflight) button.

   The Deployment Results page is displayed. If the plan fails, error messages are displayed.

How to Check the Offline Status of an SAP Message Server

If the main processes are present on the system, the resource is considered online. If any of the main processes are not present on the system, the plug-in identifies the resource as offline.

The main process for the SAP Message Server is the message server process.

Steps

1. In the Common Tasks section of the N1 SPS browser interface, click SAP.

2. In the SAP Message Server section of the SAP Tasks page, click Offline Status.

3. Click Run.

4. Select a target host or target host set.

5. Provide the plan variable.

   Install path of the SAP message server component

   This is a required field. If you do not know the install path, return to the SAP Tasks page and click the View All link.

6. Click the Run Plan (Includes Preflight) button.

   The Deployment Results page is displayed. If the plan fails, error messages are displayed.