Testing Clustered Installation

For testing clustered installation, first test the application installation, test the application for load balancing, and test the application and cache server for failover.

Procedure

  1. Testing the Application Installation
    1. Log in to TIBCO MDM.
    2. Create an enterprise.
    3. Create a repository in the specified enterprise.
    4. Upload data into the repository.
  2. Testing the application for load balancing
    1. Verify that clones are working individually.
    2. Start the web browser and verify the following URLs: 
    • http://NodeB:<port#>/eml/Home
http://NodeC:<port#>/eml/Home
http://NodeB/eml/Home

      (The IBM HTTP Server was installed on this node.)

    • You can now check the load balancing for the TIBCO MDM cluster.
    1. Access TIBCO MDM using the http://NodeB/eml/Home URL from different browsers and with different user accounts.
    2. Observe the details regarding which server receives the request and how both servers are loaded by viewing the http_plugin.log file located on Node B.
  3. Testing the Application for Failover Without Session
    1. Access TIBCO MDM from two different browsers by entering the http://NodeB/eml/Home URL. Both the servers, for example, TIBCO MDM1 and TIBCO MDM2 serve one request each.
    2. On the first browser (assuming this request is being served by TIBCO MDM1), click Add record for master catalog. Enter the product ID, short description, and other information. Stop the TIBCO MDM1 server from Deployment Manager and then click Save. TIBCO MDM2 server’s Login screen is displayed.
    3. Enter your user ID and password to continue working with TIBCO MDM. 
      <UriGroup Name="default_host_veloselcluster_URIs">
		<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/eml/*" /> 
		<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/emlservlet/*" /> 
</UriGroup>
  4. Testing Failover of Cache Server
    1. Set up the Cache server on an external box. For more information on the Cache server, see Configuration of TIBCO MDM with TIBCO ActiveSpaces.
    2. Ensure the Cache server parameters are set in the application server startup scripts.
    3. Add the activity to the list of sleep activities and set the sleep time. You can do this using the Failover Setup category in Configurator.
    4. Add a record through the UI to initiate a workflow.
    5. While the activity is sleeping, shut down the cache server that is running on the external box.
    6. The Elink log shows a Cache server related error.
    7. The Elink log also shows that the activity is retrying according to the parameters configured in the Configurator.
    8. Bring up the Cache server while the activity is retrying. The workflow should be executed successfully.