Sun Cluster Data Service for N1 Grid Service Provisioning System for Solaris OS

Registering and Configuring Sun Cluster HA for N1 Service Provisioning System

This section contains the procedures you need to configure the Master Server, the Remote Agent, or the Local Distributor of Sun Cluster HA for N1 Service Provisioning System.

How to Register and Configure Sun Cluster HA for N1 Service Provisioning System Master Server as a failover data service

This procedure assumes that you installed the data service packages.

If you did not install the Sun Cluster HA for N1 Service Provisioning System packages, go to Installing the Sun Cluster HA for N1 Grid Service Provisioning System Packages.

  1. Become superuser on one of the nodes in the cluster that will host N1 Grid Service Provisioning System Master Server.

  2. Register the SUNW.gds resource type.


    # scrgadm -a -t SUNW.gds
    
  3. Prepare the parameter file, which is required by the Sun Cluster HA for N1 Service Provisioning System Master Server.


    Caution – Caution –

    The parameter files need to be available on every node that can host the N1 Grid Service Provisioning System Master Server data service. For a failover configuration store them on the shared storage. The parameter files cannot differ for a specific instance of N1 Grid Service Provisioning System Master Server on the various nodes.



    # cd /opt/SUNWscsps/master/bin
    # cp pfile desired place
    

    Choose a location on the shared storage for the pfile. Edit the parameter file pfile and follow the comments within that file. For example:


    #!/usr/bin/ksh
    #
    # Copyright 2003 Sun Microsystems, Inc.  All rights reserved.
    # Use is subject to license terms.
    #
    # Set theN1 Grid Service Provisioning System Master Server specific environment variables which the start, stop
    # and check fuctions will use
    #
    # User          Centerrun User
    # Basepath      Absolute path to Centerrun Basedir directory
    # Host          Hostname to test Apache Tomcat
    # Tport         Port where the N1 Service Prosioning Systems Apache Tomcat instance
    #               is configured to listen
    # TestCmd       Apache Tomcat test command
    # ReturnString  Use one of the strings below faccording to your Sun One Provisoning
    #               Server Version.
    #               Version 4.1 = SSL|Service
    # Startwait     Sleeping $Startwait seconds after completion of the
    #               start command
    User=
    Basepath=
    Host=
    Tport=
    TestCmd="
    ReturnString=
    Startwait=

    The following is an example for a N1 Grid Service Provisioning System 4.1 Master Server.


    User=sps
    Basepath=/global/sps/N1_Service_Provisioning_System_4.1
    Host=N1spsma-lh
    Tport=8080
    TestCmd="get /index.jsp"
    ReturnString="SSL|Service"
    Startwait=20
    

    This example is from an N1 Grid Service Provisioning System 4.1 Master Server. The Apache Tomcat is configured to listen on Port 8080. The default start page contains the string Service, or the string SSL if you configured it to respond on the SSL Port.

  4. Configure the registration scripts for each required N1 Grid Service Provisioning System Master Server instance.


    # cd /opt/SUNWscsps/master/util
    # cp spsma_config desired place
    # cp spsma_register desired place
    

    Edit the spsma_config file and follow the comments within that file. For example:


    # These parameters can be customized in (key=value) form
    #
    # Copyright 2003 Sun Microsystems, Inc.  All rights reserved.
    # Use is subject to license terms.
    #
    # This file will be sourced in by spsma_register and the parameters
    # listed below will be used.
    #
    # These parameters can be customized in (key=value) form
    #
    #        RS - name of the resource for the application
    #        RG - name of the resource group containing RS
    #      PORT - name of the port number to satisfy GDS registration
    #        LH - name of the LogicalHostname SC resource
    #     PFILE - name of the parameter file for additional variables
    #    HAS_RS - name of the HAStoragePlus SC resource
    #
    
    RS=
    RG=
    PORT=
    LH=
    PFILE=
    HAS_RS=

    The following is an example for the Sun Cluster HA for N1 Service Provisioning System Master Server.


    RS=N1spsma-res
    RG=N1spsma-rg
    PORT=8080
    LH=N1spsma-lh
    PFILE=/global/mnt1/N1spsma-pfile
    HAS_RS=N1spsma-hastplus-res
    

    The PORT variable is needed to satisfy the requirements of the generic data service.

  5. After editing spsma_config register the resource.


    # ./spsma_register
    Registration of resource N1spsma-rs succeeded
    Validate resource N1spsma-rs in resourcegroup spsma-rg
    Validation of resource spsma-rs succeeded
    &#
  6. Enable each N1 Grid Service Provisioning System Master Server resource.


    # scstat -g
    

    # scswitch -e -j N1spsma-resource
    

Repeat Step 3 to Step 6 for each N1 Grid Service Provisioning System Master Server instance you need.

How to Register and Configure Sun Cluster HA for N1 Service Provisioning System Remote Agent as a failover data service

This procedure assumes that you installed the data service packages.

If you did not install the Sun Cluster HA for N1 Service Provisioning System packages, go to Installing the Sun Cluster HA for N1 Grid Service Provisioning System Packages.

  1. Become superuser on one of the nodes in the cluster that will host N1 Grid Service Provisioning System Remote Agent.

  2. Register the SUNW.gds resource type.


    # scrgadm -a -t SUNW.gds
    
  3. Configure the registration scripts for each required N1 Grid Service Provisioning System Remote Agents instance.


    # cd /opt/SUNWscsps/remoteagent/util
    # cp spsra_config desired place
    # cp spsra_register desired place
    

    Edit the spsra_config file and follow the comments within that file. For example:


    #
    # Copyright 2003 Sun Microsystems, Inc.  All rights reserved.
    # Use is subject to license terms.
    #
    # This file will be sourced in by spsra_register and the parameters
    # listed below will be used.
    #
    # These parameters can be customized in (key=value) form
    #
    #        RS - name of the resource for the application
    #        RG - name of the resource group containing RS
    #      PORT - name of the port number to satisfy GDS registration
    #        LH - name of the LogicalHostname SC resource
    #      USER - name of the owner of the remote agent
    #      BASE - name of the direcotry where the N1 Service Provisioning Server
    #             is installed
    #    HAS_RS - name of the HAStoragePlus SC resource
    #
    
    RS=
    RG=
    PORT=
    LH=
    USER=
    BASE=
    HAS_RS=

    The following is an example for the N1 Grid Service Provisioning System 4.1 Remote Agent.


    RS=N1spsra-res
    RG=N1spsra-rg
    PORT=22
    LH=N1spsra-lh
    USER=sps
    BASE=/global/sps/N1_Service_Provisioning_System
    HAS_RS=N1spsra-hastplus-res
    

    The PORT variable is needed to satisfy the requirements of the generic data service.

  4. After editing spsra_config register the resource.


    # ./spsra_register
    Registration of resource N1spsra-rs succeeded
    Validate resource N1spsra-rs in resourcegroup N1spsra-rg
    Validation of resource N1spsra-rs succeeded
  5. Enable each N1 Grid Service Provisioning System Remote Agent resource.


    # scstat -g
    

    # scswitch -e -j N1spsra-resource
    

Repeat Step 3 to Step 6 for each N1 Grid Service Provisioning System Remote Agent instance you need.

How to Register and Configure Sun Cluster HA for N1 Service Provisioning System Local Distributor as a failover data service

This procedure assumes that you installed the data service packages.

If you did not install the Sun Cluster HA for N1 Service Provisioning System packages, go to Installing the Sun Cluster HA for N1 Grid Service Provisioning System Packages.

  1. Become superuser on one of the nodes in the cluster that will host N1 Grid Service Provisioning System Local Distributor.

  2. Register the SUNW.gds resource type.


    # scrgadm -a -t SUNW.gds
    
  3. Configure the registration scripts for each required N1 Grid Service Provisioning System Local Distributor instance.


    # cd /opt/SUNWscsps/localdist/util
    # cp spsld_config desired place
    # cp spsld_register desired place
    

    Edit the spsld_config file and follow the comments within that file. For example:


    #
    # Copyright 2003 Sun Microsystems, Inc.  All rights reserved.
    # Use is subject to license terms.
    #
    # This file will be sourced in by spsld_register and the parameters
    # listed below will be used.
    #
    # These parameters can be customized in (key=value) form
    #
    #        RS - name of the resource for the application
    #        RG - name of the resource group containing RS
    #      PORT - name of the port number to satisfy GDS registration
    #        LH - name of the LogicalHostname SC resource
    #      USER - name of the owner of the local distributor
    #      BASE - name of the directory where the N1 Service Provisioning Server
    #             is installed
    #    HAS_RS - name of the HAStoragePlus SC resource
    #
    
    RS=
    RG=
    PORT=22
    LH=
    USER=
    BASE=
    HAS_RS=

    The following is an example for N1 Grid Service Provisioning System 4.1 Local Distributor.


    RS=N1spsld-res
    RG=N1spsld-rg
    PORT=22
    LH=N1spsld-lh
    USER=sps
    BASE=/global/sps/N1_Service_Provisioning_System_4.1
    HAS_RS=N1spsld-hastplus-res
    

    The PORT variable is needed to satisfy the requirements of the generic data service.

  4. After editing spsld_config register the resource.


    # ./spsld_register
    Registration of resource N1spsld-rs succeeded
    Validate resource N1spsld-rs in resourcegroup N1spsld-rg
    Validation of resource N1spsld-rs succeeded
  5. Enable each N1 Grid Service Provisioning System Local Distributor resource.


    # scstat -g
    

    # scswitch -e -j N1spsra-resource
    

Repeat Step 3 to Step 5 for each N1 Grid Service Provisioning System Local Distributor instance you need.