Sun Cluster Data Service for Sun Java System Application Server Guide for Solaris OS

ProcedureHow to Verify the Installation and Configuration of the Node Agents Configured as a Failover Data Service

In this procedure, a two-node cluster is used, where the nodes are identified as Node1 and Node2. The following actions were performed in How to Configure and Activate Network Resources.

Steps
  1. On Node1, start the Node Agent manually using the asadmin command.

    This step starts the Node Agent and all the server instances that are configured for this Node Agent.


    Note –

    The Node Agent and the server instances are configured to listen on the failover logical host that is configured in the failover resource group NA-resource-group.


  2. Connect to the server instances from a browser.


    http://logical-hostname:instance1-port
    

    http://logical-hostname:instance2-port
    
  3. Ensure that you can connect to any application deployed on the server instance.

  4. If you are not able to connect to an application deployed on the server instance, perform the following steps.

  5. On Node1, stop the Node Agent using the asadmin command.

    This step stops all the server instances that are configured for this Node Agent.

  6. Switch the Node Agent resource group from Node1 to Node2.


    # scswitch -z -g NA-resource-group -h Node2
    

    This steps takes the resource group offline from Node1 and brings the same resource group online on Node2. The resource group includes the logical host logical-hostname.

  7. On Node2, start the Node Agent manually using the asadmin command.

    This step starts the Node Agent and all the server instances that are configured for this Node Agent.

  8. Connect to the server instances from a browser.


    http://logical-hostname:instance1-port
    

    http://logical-hostname:instance2-port
    
  9. If you are not able to connect to the server instance from the browser, perform the following steps.

  10. After successfully verifying the configuration, stop the Node Agent and all the server instances on Node2 using the asadmin command.