A custom exception file enables you to create a unique set of variables by which to deploy an application server.
This section describes the following tasks:
The custom exception file enables you to provide and check in a custom exception file to SPS. You can then use the custom exception file to deploy the application server instead of the default exception file which is provided by the plug–in.
The custom exception file must be available on the machine where the custom exception file component is created.
Create the custom exception file.
For more information, see Exception File Example
In the Common Task ssection of the N1 SPS browser interface, click SAP.
In the Application Server With Custom Exception File section of the SAP Tasks page, click Create Component.
Provide the component information.
This is a required field. This is the component name.
Leave this value as com.sun.sap#AppServerWithExceptionFile.
Select a specific platform or leave the default value of system#any.
Short description of the component.
A description of the component.
Import Exception File from host.
Select additional options if desired.
force check in when items have not changed
remember the user that owns this item
remember the group that owns this item
path of the resource descriptor file
For more information about the resource descriptor file, see Using a Resource Descriptor File in Sun N1 Service Provisioning System 5.2 XML Schema Reference Guide.
Click the Check In Selected Item button.
The Check In window is displayed.
Specify the component name.
You can change the component name if you wish. For example, MyCustomExceptionFileComponent.
Click the Change Folder link.
Change to the /com/sun/n1aa/exceptionfiles directory.
For more information, see Chapter 6, Setting Up Folders, in Sun N1 Service Provisioning System 5.2 System Administration Guide.
Click the Change To Selected Folder button.
Click the Continue to Check In button.
The Components table is displayed.
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the Application Server With Custom Exception File section of the SAP Tasks page, click View All Components.
Click the View Current Component Check-Ins button.
The Default Exception File and any previously checked in Custom Exception files are displayed.
If you do not see the components you checked in, click on the Change Folder link and change the folder to the one in which you created the components.
This task creates an SAP Application Server component in the SPS database. This SAP Application Server is used by the Sun N1 Advanced Architecture for SAP Solutions to deploy and create a new SAP Application Server at the OS level.
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the Application Server With Custom Exception File section of the SAP Tasks page, click Create Component.
Populate the component information.
For information about component variables ending in UserExit, see User Exits.
This is a required field. This is the component name. The format of the component name is ASWithcustom-exception-filename, where custom-exception-filename is the previously created component.
For example, ASWithMyCustomExceptionFile. This component needs to be in the /com/sun/n1aa/exceptionfiles directory.
Leave this value as com.sun.sap#AppServerWithExceptionFile.
Select a specific platform or leave the default value of system#any.
A short description.
An description of the component.
Click the Reference Existing link for the Exception File component.
Select the exception file.
Click the Reference Checked Components button.
The Add Component Variables table appears.
This table will be empty if there are no component variables
Click the Continue to Reference Components button.
Populate the Component Variables.
Required for the Sun Cluster environment.
This is a required field.
In the Sun Cluster environment, the groupName must equal the Sun Cluster resource group name.
Install location.
Required for the default environment installation. Central instance logical host.
Required for the default environment. Application server logical host.
Required for the default environment. SAP system ID (3 upper case alphanumeric.) The first character must be an alphabetic letter.
Required for the default environment. Application Server instance number.
This is a required field. Central Instance number. Generated from variable input.
Application Server instance size. Default value: medium.
Identifies if this component will be deployed to a Default, Sun Cluster, or SAP AC environment. Value can be ac, sc, or default. Default value: default.
Required for the SAP AC environment. SAP AC service ID.
The Solaris Resource Management (SRM) project name. Default value: default.
This is a required field. TRUE means the central scripts are user to start and stop the application server. FALSE means instance specific start and stop scripts from the SAP user home directory will be used to start and stop the application server. Default value: TRUE
Identifies the installer of the component.
Click Check In.
Click Continue to Check In.
You have completed the creation of the application server with custom exception file component.
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the Application Server With Custom Exception File section of the SAP Tasks page, click View All Components.
The components table is displayed.
Select the Application Server with Custom Exception File component.
Perform one of the following options to begin the plan creation task:
If you are in the Components Details window.
Select default: install
If you enter from the Common Tasks page.
In the Common Tasks section of the N1 SPS browser interface, click SAP.
In the Application Server With Custom Exception File section of the SAP Tasks page, click View All Components.
Select the appropriate application server with custom exception file component.
Select the default:install procedure from the component procedures table.
Click Generate Plan With Checked Procedures.
The plans details advanced edit page appears.
Type the plan name
The format of the plan name is Installcomponent-namePlan. For example, InstallASWithMyCustomExceptionFilePlan.
Edit the plan definition.
Click the Check In button.
The Plans Details Edit Check In window appears.
The following warning might appear and can be ignored.
warning – plan names and/or paths differ |
Click the Continue To Check In button.
The Plans Details window appears.
Click Done.
The Plans table is displayed.