test

Sun N1 Service Provisioning System User's Guide for SAP Plug-In 1.0

The GDS Component

The following plans are necessary for operating the Generic Data Service (GDS) component at the group level through the Sun N1 Advanced Architecture for SAP Solutions software.

Caution – Caution –

The naming convention for the plans must follow the examples. If they do not, the plan will fail.

ProcedureHow to Create a GDS Component Using the GDSResourceType

Steps

  1. In the Application Deployment section of the N1 SPS browser interface, click Components.

  2. Change the folder to /com/sun/n1aa/GDS.

  3. Click on create link for creating the component.

  4. Enter the name of the component.

  5. Select the type as untyped.

  6. Insert the following text before the ending component element, </component>:

    <extends>
    <type name="com.sun.sap#GDSResourceType"></type>
</extends>

<installList>
    <installSteps name="createDependency" access="PROTECTED">
    <paramList>
	       <param name="grpInstallPath"/>
    </paramList>
    <try>
        <block>
        <!-- Replace dependency name, RunLevel1, with your desired run-level. -->
        <!-- Following are the pre-defined dependency names -->
            <createDependency name="RunLevel1">
                <installedComponent name="Group" path="/com/sun/sap/resourcetypes" 
                     installPath=":[grpInstallPath]"></installedComponent>
            </createDependency>
        </block>
        <catch>
            <raise message="Error in creating dependency: :[grpInstallPath]"/>
        </catch>
    </try>
    </installSteps>
</installList>

  7. Change the dependency name on line containing <createDependency> element.

    Valid dependency names are:

      RunLevel1 through RunLevel5


      NFSMount2Group


      RunLevel7 through RunLevel11


      HAStoragePlus2Group


      RunLevel13 through RunLevel17


      LogicalHost2Group


      RunLevel19 through RunLevel23


      Oracle2Group


      RunLevel25 through RunLevel29


      CentralInstance2Group


      RunLevel31 through RunLevel35


      EnqueueServer2Group


      RunLevel37 through RunLevel41


      MessageServer2Group


      RunLevel43 through RunLevel47


      AppServerWithExceptionFile2Group


      RunLevel49 through RunLevel53


      AppServer2Group


      RunLevel55 through RunLevel59


      NFSShare2Group


      RunLevel61 through RunLevel65


  8. Click Check In.

  9. Click Continue to Check In.

ProcedureHow to Generate a Create Plan for a GDS Resource

This is a markOnly task.

Note –

This plan does not have any plan parameters.

Steps

  1. In the Application Deployment section of the N1 SPS browser interface, click Components.

  2. Change the folder to /com/sun/n1aa/GDS.

  3. Click on the details link of the created GDS component.

  4. Select the check box for the install:default procedure.

    You can also select the check box for the install:markOnly procedure.

    Note –

    Both default and markOnly installs are the same unless you overwrite the installSteps in the GDS component ?

  5. Click the Generate Plan With Checked Procedures link.

  6. Type the name of the plan as Creategds-component-namePlan.

    Where gds-component-name is the name of the component created in the task How to Create a GDS Component Using the GDSResourceType.

  7. In the XML text, in <executionPlan> element, change the name of the attribute to Creategds-component-namePlan.

  8. Click Check In.

  9. Click Continue to Check In.

ProcedureHow to Generate a Delete Plan for a GDS Resource

This is a markOnly task.

Note –

The installPath is the only plan parameter.

Steps

  1. In the Application Deployment section of the N1 SPS browser interface, click Components.

  2. Change the folder to /com/sun/n1aa/GDS.

  3. Click on the details link of the created GDS component.

  4. Select the check box for the uninstall:default procedure.

    You can also select the check box for the uninstall:markOnly procedure.

  5. Click on the Generate Plan With Checked Procedures link.

  6. Enter the name of the plan as Deletegds-component-namePlan.

    Where gds-component-name is the name of the component created in section How to Create a GDS Component Using the GDSResourceType.

  7. In the XML text <executionPlan> element, change the name of the attribute to Deletegds-component-namePlan.

  8. Before the <simpleSteps> element, add the installPath as the plan parameter.

    For example, include the following text to insert the plan parameter:

    <paramList>
        <param name="installPath" default="" prompt="Install path of the GDS component"></param>
     </paramList>

  9. Add the installPath=':[installPath]' attribute to the <installedComponent> element in the XML text.

    For example:

    Before adding the installPath.

    <uninstall blockName='default'>
    <installedComponent name='gds' versionOp='=' version='1.0' 
        path='/com/sun/n1aa/GDS'></installedComponent>
</uninstall>

    After adding the installPath.

    <uninstall blockName='default'>
    <installedComponent name='gds' versionOp='=' version='1.0' 
    path='/com/sun/n1aa/GDS' installPath=':[installPath]'></installedComponent>
</uninstall>

  10. Click Check In.

  11. Click Continue to Check In.

ProcedureHow to Generate a Start Plan for a GDS Resource

Note –

The installPath is the only plan parameter.

Steps

  1. In the Application Deployment section of the N1 SPS browser interface, click Components.

  2. Change the folder to /com/sun/n1aa/GDS.

  3. Click on the details link of the created GDS component.

  4. Select the check box for the start procedure.

  5. Click on the Generate Plan With Checked Procedures link.

  6. Enter the name of the plan as Startgds-component-namePlan.

    Where gds-component-name is the name of the component created in section How to Create a GDS Component Using the GDSResourceType.

  7. In the XML text, in the <executionPlan> element, change the name of the attribute to Startgds-component-namePlan.

  8. Before the <simpleSteps> element, delete the <paramList> entry containing forceStart parameter.

  9. Before the <simpleSteps> element, add the installPath as the plan parameter.

    For example, include the following text to insert the plan parameter:

    <paramList>
    <param name="installPath" default="" 
        prompt="Install path of the GDS component"></param>
</paramList>

  10. Delete arguments to start control, by deleting the <argList> line after <call blockName='start'>.

  11. Add the installPath=':[installPath]' attribute to the <installedComponent> element in the XML text.

    For example, before adding the installPath.

    <call blockName='start'>
    <installedComponent name='gds' versionOp='=' version='1.0' 
        path='/com/sun/n1aa/GDS'></installedComponent>
</call>

    After added the installPath.

    <call blockName='start'>
    <installedComponent name='gds' versionOp='=' version='1.0' 
        path='/com/sun/n1aa/GDS' installPath=':[installPath]'></installedComponent>
</call>

  12. Click Check In.

  13. Click Continue to Check In.

ProcedureHow to Generate a Stop Plan for a GDS Resource

Note –

The installPath is the only plan parameter.

Steps

  1. In the Application Deployment section of the N1 SPS browser interface, click Components.

  2. Change the folder to /com/sun/n1aa/GDS.

  3. Click on the details link of the created GDS component.

  4. Select the check box for the stop procedure.

  5. Click the Generate Plan With Checked Procedures link.

  6. Enter the name of the plan as Stopgds-component-namePlan.

    Where gds-component-name is the name of the component created in section How to Create a GDS Component Using the GDSResourceType.

  7. In the XML text, in the <executionPlan> element, change the name of the attribute to Stopgds-component-namePlan.

  8. Before the <simpleSteps> element, delete the paramList element containing the shutdownMode and forceStop parameters.

  9. Before the <simpleSteps> element, add the installPath as the plan parameter.

    For example, include the following text to insert the plan parameter:

    <paramList>
    <param name="installPath" default="" 
        prompt="Install path of the GDS component"></param>
</paramList>

  10. Delete arguments to stop control, by deleting the <argList> line after <call blockName='stop'>.

  11. Add the installPath=':[installPath]' attribute to the <installedComponent> element in the XML text.

    For example,

    Before adding the installPath.

    <call blockName='stop'>
     <installedComponent name='gds' versionOp='=' version='1.0' 
          path='/com/sun/n1aa/GDS'></installedComponent>
</call>

    After adding the installPath.

    <call blockName='stop'>
    <installedComponent name='gds' versionOp='=' version='1.0' 
        path='/com/sun/n1aa/GDS' installPath=':[installPath]'></installedComponent>
</call>

  12. Click Check In.

  13. Click Continue to Check In.

ProcedureHow to Generate an isOnline Plan for a GDS Resource

Note –

The installPath is the only plan parameter.

Steps

  1. In the Application Deployment section of the N1 SPS browser interface, click Components.

  2. Change the folder to /com/sun/n1aa/GDS.

  3. Click on the details link of the created GDS component.

  4. Select the check box for the isOnline procedure.

  5. Click on the Generate Plan With Checked Procedures link.

  6. Enter the name of the plan as Isgds-component-nameOnlinePlan.

    Where gds-component-name is the name of the component created in section How to Create a GDS Component Using the GDSResourceType.

  7. In the XML text, in the <executionPlan> element, change the name of the attribute to Isgds-component-nameOnlinePlan.

  8. Before the <simpleSteps> element, add the installPath as the plan parameter.

    For example, include the following text to insert the plan parameter:

    <paramList>
    <param name="installPath" default="" 
        prompt="Install path of the GDS component"></param>
</paramList>

  9. Add the installPath=':[installPath]' attribute to the <installedComponent> element in the XML text.

    For example, before adding the installPath.

    <call blockName='isOnline'>
    <installedComponent name='gds' versionOp='=' version='1.0' 
        path='/com/sun/n1aa/GDS'></installedComponent>
</call>

    After adding the installPath.

    <call blockName='isOnline'>
    <installedComponent name='gds' versionOp='=' version='1.0' 
        path='/com/sun/n1aa/GDS' installPath=':[installPath]'></installedComponent>
</call>

  10. Click Check In.

  11. Click Continue to Check In.

ProcedureHow to Generate an isOffline Plan for a GDS Resource

Note –

The installPath is the only plan parameter.

Steps

  1. In the Application Deployment section of the N1 SPS browser interface, click Components.

  2. Change the folder to /com/sun/n1aa/GDS.

  3. Click on the details link of the created GDS component.

  4. Select the check box for the isOffline procedure.

  5. Click on the Generate Plan With Checked Procedures link.

  6. Enter the name of the plan as Isgds-component-nameOfflinePlan.

    Where gds-component-name is the name of the component created in section How to Create a GDS Component Using the GDSResourceType.

  7. In the XML text, in the <executionPlan> element, change the name of the attribute to Isgds-component-nameOfflinePlan.

  8. Before the <simpleSteps> element, add the installPath as the plan parameter.

    For example, include the following text to insert the plan parameter:

    <paramList>
    <param name="installPath" default="" 
        prompt="Install path of the GDS component"></param>
</paramList>

  9. Add the installPath=':[installPath]' attribute to the <installedComponent> element in the XML text.

    For example, before adding the installPath:

    <call blockName='isOffline'>
    <installedComponent name='gds' versionOp='=' version='1.0' 
        path='/com/sun/n1aa/GDS'></installedComponent>
</call>

    After adding the installPath:

    <call blockName='isOffline'>
    <installedComponent name='gds' versionOp='=' version='1.0' 
        path='/com/sun/n1aa/GDS' installPath=':[installPath]'></installedComponent>
</call>

  10. Click Check In.

  11. Click Continue to Check In.