Sun N1 Advanced Architecture for SAP Solutions 5.2.1 User's Guide

Chapter 5 N1 AA Deployer

This chapter describes the setup and usage of the N1 AA Deployer module.

Overview

The N1 AA Deployer is designed to manage the services in your system landscape. The main functionalities are:

Start and Stop resources. For example, an SAP Central Instance or complete resource groups
Relocate resource groups from one server to another server
Deploy or delete SAP Application Server instances

The N1 AA Deployer is based on the technology of the Sun N1 Service Provisioning System (N1 SPS). The system landscape you manage has to be defined completely within the N1 SPS SAP Plug-in. For more information, see the Sun N1 Service Provisioning System User’s Guide for SAP Plug-In 1.0 on how to setup resources and resource groups.

Customizing

This section describes additional customizing necessary for the N1 AA Deployer.

Note –

The necessary SPS parameterisation should have already been done during the general N1 AA setup. The parameters none.general.sps.* have been specified. For more information, see General Customizing.

SAP RFC Parameter

Purpose: Settings for SAP RFC communication.
Menu: Administration ⇒ Deployer ⇒ Customizing
Tasks for an initial basic setup: Mandatory

While creating or removing SAP Application Instances, the existing Logon and RFC Servers Groups of the SAP System might be modified. The action of creating adds the instance to the SAP Systems Logon or RFC Server Groups. The action of removing deletes the instance from the SAP Systems Logon or RFC Server Groups.

N1 AA uses the RFC parameters to communicate with the SAP system. This is true for all SAP systems in your N1 AA landscape. You have to provide the same user ID and password in every SAP system.

Table 5–1 SAP RFC Parameters


Parameter	Description	Example value
`none.deployment.saprfc.client`	Logon client for RFC communication.	000
`none.deployment.saprfc.password`	Logon password for RFC communication. Password is stored encrypted in the N1 AA database.	n1aapwd
`none.deployment.saprfc.timeout`	Timeout value, in minutes, for RFC communication	2
`none.deployment.saprfc.user`	User for RFC communication. SAP user type `communications (CPI-C)` is sufficient.	n1aauser

Note –

Regarding the previous parameters. You can add additional optional parameters by replacing none with servergroup. For example, servergroup.deployment.saprfc.user, where servergroup is the name of an existing server group. This overwrites the parameter value within the specified server group.

Timeout Parameter

Purpose: Settings the timeout values for Deployer actions
Menu: Administration ⇒ Deployer ⇒ Customizing
Tasks for an initial basic setup: Optional

This is where timeout values for Deployer actions are customized. The naming convention for these parameters is: none.deployment.generaltimeout.resourcetype.action. With:

action = start: Timeout for starting a resource of type resourcetype
action = stop: Timeout for stopping a resource of type resourcetype
action = isonline: Timeout for checking if a resource of type resourcetype is online
action = isoffline: Timeout for checking if a resource of type resourcetype is offline

Note –

You can customize timeouts for a dedicated resource by adding parameters while replacing resourcetype with the dedicated resourcename. For example, none.deployment.generaltimeout.P01CI.start defines the start timeout for the resource P01CI. It overwrites the generic type–specific start timeout for SAP Central Instances none.deployment.generaltimeout.SAPCentralInstance.start.

Table 5–2 Timeout Parameters


Parameter	Description	Example Value
`none.deployment.generaltimeout.GDS.isoffline`	Timeout values, in minutes, for resources of type `GDS`.	1
`none.deployment.generaltimeout.GDS.isonline`		1
`none.deployment.generaltimeout.GDS.start`		5
`none.deployment.generaltimeout.GDS.stop`		5
`none.deployment.generaltimeout.HAStoragePlus.isoffline`	Timeout values, in minutes, for resources of type `HAStoragePlus`.	1
`none.deployment.generaltimeout.HAStoragePlus.isonline`		1
`none.deployment.generaltimeout.HAStoragePlus.start`		10
`none.deployment.generaltimeout.HAStoragePlus.stop`		10
`none.deployment.generaltimeout.LogicalHost.isoffline`	Timeout values, in minutes, for resources of type `LogicalHost`.	1
`none.deployment.generaltimeout.LogicalHost.isonline`		1
`none.deployment.generaltimeout.LogicalHost.start`		5
`none.deployment.generaltimeout.LogicalHost.stop`		5
`none.deployment.generaltimeout.NfsMount.isoffline`	Timeout values, in minutes, for resources of type `NFSMount`.	1
`none.deployment.generaltimeout.NfsMount.isonline`		1
`none.deployment.generaltimeout.NfsMount.start`		5
`none.deployment.generaltimeout.NfsMount.stop`		5
`none.deployment.generaltimeout.NfsShare.isoffline`	Timeout values, in minutes, for resources of type `NFSShare`.	1
`none.deployment.generaltimeout.NfsShare.isonline`		1
`none.deployment.generaltimeout.NfsShare.start`		5
`none.deployment.generaltimeout.NfsShare.stop`		5
`none.deployment.generaltimeout.Oracle.isoffline`	Timeout values, in minutes, for resources of type "`Oracle`".	1
`none.deployment.generaltimeout.Oracle.isonline`		1
`none.deployment.generaltimeout.Oracle.start`		10
`none.deployment.generaltimeout.Oracle.stop`		10
`none.deployment.generaltimeout.SapAppServer.Install`	Timeout values, in minutes, for resources of type `AppServer`.	10
`none.deployment.generaltimeout.SapAppServer.isoffline`		1
`none.deployment.generaltimeout.SapAppServer.isonline`		1
`none.deployment.generaltimeout.SapAppServer.start`		10
`none.deployment.generaltimeout.SapAppServer.stop`		10
`none.deployment.generaltimeout.SapCentralInstance.isoffline`	Timeout values, in minutes, for resources of type `CentralInstance`.	1
`none.deployment.generaltimeout.SapCentralInstance.isonline`		1
`none.deployment.generaltimeout.SapCentralInstance.start`		10
`none.deployment.generaltimeout.SapCentralInstance.stop`		10
`none.deployment.generaltimeout.SapEnqueueServer.isoffline`	Timeout values, in minutes, for resources of type `EnqueueServer`	1
`none.deployment.generaltimeout.SapEnqueueServer.isonline`		1
`none.deployment.generaltimeout.SapEnqueueServer.start`		5
`none.deployment.generaltimeout.SapEnqueueServer.stop`		5
`none.deployment.generaltimeout.SapMessageServer.isoffline`	Timeout values, in minutes, for resources of type `MessageServer`.	1
`none.deployment.generaltimeout.SapMessageServer.isonline`		1
`none.deployment.generaltimeout.SapMessageServer.start`		5
`none.deployment.generaltimeout.SapMessageServer.stop`		5

Note –

Change all *.isonline and *.isoffline parameter values from 1 to 5. This is a absolutely necessary. Make these changes immediately after installation and before you use N1 AA.

If you see messages like ... Got timeoutout from db ..., you might have to adjust the related timeout parameters.

Groups and Resources Management

This chapter explains all functions provided by the N1 AA Deployer to manage resources and resource groups.

Purpose: Management of resources and resource groups. For example, start, stop, and relocate.
Menu: servergroup ⇒ Deployer ⇒ Resource Groups
Use case: Daily business

Go to servergroup ⇒ Deployment ⇒ Resource Groups. You arrive at the first main screen that lists all the available resource groups. This is the access point for all management functions.

Figure 5–1 N1 AA Deployer – Resource Groups

Select one dedicated group and click the View button . This brings you to the second main screen that lists all the available resources belonging to the selected group. This is the access point for all management functions. For example, start and stop the resources.

The following table lists all available functions on resource groups and resources in the N1 AA Deployer.

Caution –

Be careful with the Force option of the Move function. You have to ensure that the resources are really offline. Otherwise, there is the danger that resources will be started twice. On the current host and on the target host.

Table 5–3 Functions


Function	Description	Mode	Input	Output
Resource Groups
View Resource Groups	The initial screen of the Deployer. Shows all Resource Groups defined in N1 SPS.	Online in the foreground (GUI)	None	Resource Name Name of the resource group as defined in N1 SPS. Status Status of the Group on the host. The group status is derived from the status of its resources.
				ONLINE = All resources are online (up and running). OFFLINE = All resources are offline (down). PARTIAL = All resources are partially online. This means that all necessary processes are neither all online nor are they all offline.
				UNKNOWN = No status information for any resource available. UNREACHABLE = Host is unreachable. To be more technically correct, the SPS Remote Agent on this host is not reachable. MIXED = No uniform status of the resources (any mixed mode of statuses.

Table 5–4 Functions (continued)


Function	Description	Mode	Input	Output
Resource Groups
View Resource Groups	The initial screen of the Deployer. Shows all Resource Groups defined in N1 SPS.	Online in the foreground (GUI)	None	Last Update Point in time when the status was last updated. N1 AA is not doing any active monitoring. Instead, the status is only updated when requested. That is: Automatically after start, stop or relocate of resources/groups. If refresh-functions have been performed by the user.
				Host Hostname on that the group is currently mastered as defined in N1 SPS. Environment Type of group as defined in N1 SPS. SPS = Managed directly by SPS SC = Group comes from Sun Cluster ACC = Group comes from SAP Adaptive Computing controller
Start	Start the resource group on the host. N1 AA calls the start plan of the group in N1 SPS. This starts all the resources of the group in the predefined sequence. For more details on the start mechanism, see the Sun N1 Service Provisioning System User’s Guide for SAP Plug-In 1.0.	Job in the background. The GUI reflects the changes as soon as the job is finished and the GUI is refreshed by any user interaction.	Resource Group As selected in the GUI	The joblog shows details of the start: Success = Start of group was successfully executed within SPS. All resources are online. The group status, status of all resources, is set to online. Failed = Start of group was not successfully executed within SPS. At least one resource is not online now. The group status, status of all resources, is set to Unknown. Use the refresh functions to re–evalute the current status of the group.
Stop	Stop the resource group on the host. N1 AA calls the stop plan of the group in N1 SPS. This stops all resources of the group in the predefined sequence. For more details on the stop mechanism, see Sun N1 Service Provisioning System User’s Guide for SAP Plug-In 1.0.	Job in the background. The GUI reflects the changes, as soon as the job is finished and the GUI is refreshed by any user interaction.	Resource Group As selected in the GUI	The joblog shows details of the stop: Success = Stop of group was successfully executed within SPS. All resources are offline now. The group status, status of all resources, is set to Offline. Failed = Stop of group was not successfully executed within SPS. At least one resource is not offline now. The group status, status of all resources, is set to Unknown. Use the refresh functions to reevalute the current status of the group.
Move	Relocate the resource group to a specified target host. This stops the group on the current host and starts the group on the specified target host.	Job in the background. The GUI reflects the changes as soon as the job is finished and the GUI is refreshed by any user interaction.	Resource Group As selected in the GUI Target host Physical hostname Force Option Ignores the fact that the group could not be stopped successfully on the current host and continues to start the group on the target host. This might be needed in special situations. For example, if the current host is down. Caution – Be careful with the Force option. You have to ensure that the resources are really offline. Otherwise, there is the danger that resources will be started twice. On the current host and on the target host.	The joblog shows details of the move: Success = Move of the group was successfully executed within SPS. All resources are online on the target host now. The group status, status of all resources, is set to Online. Failed = Move of the group was not successfully executed within SPS. The group status, status of all resources, is set to Unknown. Use the refresh functions to reevalute the current status of the group.
Refresh	Evaluate the current status of the resource group (every resource) on the host. N1 AA calls the appropriate `isonline` and `isoffline` plans in SPS.	Job in the background. The GUI reflects the changes as soon as the job is finished and the GUI is refreshed by any user interaction.	Resource Group As selected in the GUI	Updates the Status and Last Update information as displayed in the GUI. See the functions View Resource Groups and View Resources.
Resources
View Resources	The screen shows all resources belonging to the specified group as defined in N1 SPS.	Online in the foreground (GUI)	Resource Group As selected in the GUI	Resource Name Name of the resource, as defined in N1 SPS.
				Type Type of the resource, as defined in N1 SPS. There are predefined resource types. For example, IP Address or SAP Central Instance, available with the SAP plug-in.
				Status Status of the resource on the host. ONLINE = Resource is online (up and running). OFFLINE = Resource is offline (down). PARTIAL = All resources are partially online. This means that all necessary processes are neither all online nor are they all offline. UNKNOWN = No status information for the resource is available. UNREACHABLE = Host is unreachable. To be more technically correct, the SPS Remote Agent on this host is not reachable.
				Last update Point in time, the status was last updated. N1 AA is not doing an active monitoring. Instead of that, the status will only be updated when requested. That is: Automatically after start, stop, or relocate of resources or groups. If refresh functions have been performed by the user. Host Hostname, on that the resource is currently mastered as defined in N1 SPS. EnvironmentType of the group, as defined in N1 SPS. SPS = Managed directly by SPS SC = Group comes from Sun Cluster ACC = Group comes from SAP Adaptive Computing controller
Start	Start the resource on the host. N1 AA calls the start plan of the resource in N1 SPS. For more details on the start mechanism, see Sun N1 Service Provisioning System User’s Guide for SAP Plug-In 1.0.	Job in the background. The GUI reflects the changes as soon as the job is finished and the GUI is refreshed by any user interaction.	Resource As selected in the GUI	The joblog shows details of the start: Success = Start of resource was successfully executed within SPS. The resource status is set to Online. Failed = Start of resource was not successfully executed within SPS. The resource status is set to Unknown. Use the refresh functions to reevalute the current status of the resource.
Stop	Stop the resource on the host. N1 AA calls the stop plan of the resource in N1 SPS. For more details on the stop mechanism, see Sun N1 Service Provisioning System User’s Guide for SAP Plug-In 1.0.	Job in the background. The GUI reflects the changes, as soon as the job is finished and the GUI is refreshed by any user interaction.	Resource Group As selected in the GUI	The job log shows details of the stop: Success = Stop of group was successfully executed within SPS. The resource status is set to Offline. Failed = Stop of resource was not successfully executed within SPS. The resource status is set to Unknown. Use the refresh functions to reevalute the current status of the resource.
Refresh	Evaluate the current status of the resource on the host. N1 AA calls the appropriate `isonline` and `isoffline` plans in SPS.	Job in the background. The GUI reflects the changes, as soon as the job is finished and the GUI is refreshed by any user interaction.	Resource Group As selected in the GUI	Updates the `Status` and `Last Update` information as displayed in the GUI. See the functions View Resource Groups and View Resources.
View Details	Shows the technical details of the resource definition.	Online in the foreground (GUI)	Resource As selected in the GUI	Technical details of the resource as defined in N1 SPS.

SAP Application Server Provisioning

N1 AA Deployer supports the provisioning of SAP Application Servers for existing SAP Systems.

Precondition:

The SAP System has to be existing and defined within the N1 SPS SAP Plug-in.
If you want to use a custom exception file for the deployment process, the custom exception file must have been previously created within SPS.

For technical background information on SAP Application Sever provisioning, see Creating, Managing and Installing SAP Application Servers in Sun N1 Service Provisioning System User’s Guide for SAP Plug-In 1.0.

Deploy New SAP Application Server

Purpose: Install a new SAP Application Server for an existing SAP system
Menu: servergroup ⇒ Deployer ⇒ Deploy new SAP Application Server
Use case: Daily business

Description

This function installs a new SAP Application Server for an existing SAP system:
- Creates new SAP Application Server including logical host
- Adjusts the SAP RFC Server Groups and Logon Groups
- Creates appropriate resource group and resources, SAP Application Server and logical host, within the SPS repository
- Starts the new logical host, IP address, and SAP Application Server
Mode

Job in the background. The GUI reflects the changes as soon as the job is finished. The GUI is refreshed by any user interaction.
Input

Necessary input parameters describe the new SAP instance to install.
- SAP System: Select one of the existing SAP systems. Resources of type SAP Central Instance in the server group.
- Instance number: Instance number for the new application server.
- Physical host: Install and start the new instance on this physical host. Select one of the existing hosts in the server group.
- Logical host: IP name for the new application server. Specify any existing but unused IP name.
- Size: Category of memory size, small, medium, or large, for the new instance profile.
- Profile parameter file: Choose an exception file for the deployment process. The exception file defines dedicated parameters to be used for the new Instance Profile of the SAP Application Instance:
  - Choose either the default exception file which is represented by the entry ---------------.
  - Choose a custom exception file that was previously created within SPS
    
    For more information on exception files, see Creating, Managing and Installing SAP Application Servers in Sun N1 Service Provisioning System User’s Guide for SAP Plug-In 1.0.
- SRM Project: (Optional) If you specify an existing SRM project, N1 AA always starts the SAP application server in this SRM project. If you are using N1 AA Analyzer, this is a key requirement. If you do not specify an SRM project, the default project is used.
If N1 SPS is able to connect to the specified SAP system, you see a list of available SAP Logon Groups and RFC Server Groups on the system. Otherwise, you see a warning. You can decide to continue or not continue. Select any of these groups. N1 AA adds the new SAP instance to these groups, if the installation finishes successfully.
Output

The joblog shows details of the actions:
- The installation and starting of the new components (SAP Application Server and logical host).
- The adjustments of the SAP RFC Server Groups and Logon Groups.
- The adjustments within the SPS repository.

Remove SAP Application Server

Purpose: Remove an existing SAP Application Server
Menu: servergroup ⇒ Deployer ⇒ Remove SAP Application Server
Use case: Daily business

Description

This function removes a complete resource group (SAP Application Server and logical host), that has been previously installed by the Deploy new SAP Application Server function of the N1 AA Deployer.
- Stops and deletes all SAP Application Servers and logical hosts in this group, that have been created by the function Deploy new SAP Application Server if not modified manually by the user. This equates to one SAP Application Server and one logical host.
- Removes the deleted SAP Application Servers from all SAP RFC groups or Logon groups.
- Deletes the corresponding resource group and resources within the SPS repository.
Mode

Job in the background. The GUI reflects the changes as soon as the job is finished. The GUI is refreshed by any user interaction.
Input

Necessary input parameters specify the resource group, that should be removed.
- Select one of the existing server groups . The selection is limited to those groups, that have been previously created by the function Deploy New SAP Application Server of the N1 AA Deployer.
Output

The job log shows details of the actions:
- Stopping and deleting the SAP Application Servers and logical hosts.
- The adjustments of the SAP RFC Server Groups and Logon Groups.
- The adjustments within the SPS repository.