Installing and clustering WebSphere Process Server V7 in non-GUI mode, Part 2: Using the command line to create a cluster

Creating the Golden topology

This section details the steps to set up a Golden topology using the deployment environment commands.

Preparing the environment

The administration tasks will require considerable time using the wsadmin scripts. Therefore, the SOAP timeout has to be adjusted accordingly for the deployment manager to avoid SOAP timeout errors. To adjust the timeout, set com.ibm.SOAP.requestTimeout to 2700 from the default value in the file <dmgr_profile_path>/properties/soap.client.props.

Note: It is a good practice to back up the system configuration before and after a deployment environment is generated.

Back to top

Running the commands

1. Start the deployment manager and the nodeagent in the dWCustom01profile:

   ../profiles/dWDmgr/bin>./startManager.sh ../profiles/dWCustom01/bin>./startNode.sh

   
   
2. Connect to the wsadmin scripting environment from the dWDmgr/bin directory:

   ./wsadmin.sh –lang jython –user <administrative user> -password <administrative user password> -connType SOAP

   
   
3. The following is the command to create a new deployment environment definition. This command creates a deployment environment with a name of dWDepEnv. The topology pattern is specified here as well as the runtime type, which is either WPS or WESB.

   AdminTask.createDeploymentEnvDef (‘[ -topologyName dWDepEnv -topologyPattern RemoteMessagingAndSupport –topologyRuntime WPS ]’)

   
   
4. Add the dWCustom01 node to dWDepEnv. Also configure the clusters and add a single member in each of the clusters.

   AdminTask.addNodeToDeploymentEnvDef (‘[ -topologyName dwDepEnv -topologyRole ADT,Messaging,Support -nodeRuntime WPS –nodeName dWNode02 -serverCount 1 ]’)

   
   
5. Validate the deployment environment. Show the current status. Save the changes. To learn more about the status of the deployment environment, refer to this Information Center topic, Displaying deployment environment status using the command line.

   AdminTask.validateDeploymentEnvDef (‘[ -topologyName dWDepEnv ]’) AdminTask.showDeploymentEnvStatus (‘[ '-topologyName dWDepEnv ]’) AdminConfig.save()

   
   
6. Generate the deployment environment. Ensure that the nodeagent is running before this command is issued.

   This task configures the clusters and servers for the deployment environment first. It then proceeds to create the data sources, authentication aliases, and JMS resources. As part of this task, the SCA and BPC containers are configured in the application clusters, messaging engines are configured in the messaging cluster, CEI, Business Space, business rules, and other support applications are configured in the Support cluster.

   Depending on the size of the topology, the command may take a while to complete the execution. The command took around ten minutes to complete on the Linux server.

   AdminTask.generateDeploymentEnv (‘[ -topologyName dWDepEnv ]’) AdminTask.showDeploymentEnvStatus (‘[ '-topologyName dWDepEnv ]’) AdminConfig.save()

   
   
7. Ensure that the deferred tasks are completed before you issue the next command.

   Navigate to Servers > Deployment Environments > dWDepEnv > Configuration tab > Additional properties > Deferred Configurations. You will see instructions to complete the deferred tasks as shown in Figure 2. Complete the deferred configuration tasks for the Business Space component. Open the administrative console.

   
   
   Figure 2. Deferred configuration steps page in the Administrative console
   
   
   
   1. Business Space database: The page also displays the location where the database scripts for Business Space are created. Note the location details and execute the database scripts. Failure to complete this task results in error while the application cluster is launched.
   2. CEI database: Complete the CEI database configuration. The CEI database is created after the generation of the deployment environment and the script locations will be indicated. Note the location and execute the scripts to complete the CEI database configuration.
8. Upon successful configuration, return to this page and click the Configuration Done button as shown in Figure 3.
   
   Figure 3. Completed deferred configuration steps
   
   
   
9. Start the deployment environment. This command starts all the clusters in the environment. Verify that all the servers or clusters have started successfully.

   AdminTask.startDeploymentEnv (‘[ -topologyName dWDepEnv ]’) AdminTask.showDeploymentEnvStatus (‘[ '-topologyName dWDepEnv ]’)

   
   
10. Stop the deployment environment.

    AdminTask.stopDeploymentEnv (‘[ -topologyName dWDepEnv ]’) AdminTask.showDeploymentEnvStatus (‘[ '-topologyName dWDepEnv ]’)

    
    

    The deployment environment is now complete. Figure 4 shows the cluster topology screen from the administrative console.

    
    
    Figure 4. Cluster topology view from the administrative console
    
    
    

Back to top

Verifying the environment

The deployment environment approach hides considerable configuration data from the administrator, performing these tasks in the background. Now that the environment is generated, it is worthwhile to check to see if the configured resources are functioning as designed before using the deployment environment.

Figure 5 shows the various resources configured as part of the deployment environment creation task.

A detailed checklist for verification is available in IBM Redbook: WebSphere Business Process Management V7 Production Topologies (Section 5.5: Post-creation configuration and verification). Table 3 shows the verification list.

Back to top

Modifying the environment

Certain commands are available for modifying the already configured deployment environments. Documentation on these commands is available in the Information Center topic, Administering deployment environments. Note that these commands will not be effective over an already generated deployment environment.

No other modifications are possible via the deployment environment scripts. You will need to manually make the required configuration changes to the environment if the need arises.

Note: If you need to expand the deployment environment to add additional clusters, there are no commands provided in the pre-defined reference patterns. This option is available only on a Custom topology pattern. For expanding deployment environments created using pre-defined patterns, manual configuration is required. For best practices and patterns on expanding clustered topologies, see Expanding clustered topologies for WebSphere Process Server and WebSphere Enterprise Service Bus.

Back to top

Recovering from failures

If you encounter failure while generating a deployment environment, it is not necessary to remove the deployment environment configuration. You can correct the error, clean up the resources, and reattempt the deployment environment generation. In case you accidentally saved an incorrect configuration, use the deleteDeploymentEnvDef command to remove the configuration:

AdminTask. deleteDeploymentEnvDef (‘[ -topologyName dWDepEnv]’)

This command deletes the deployment environment definition from a deployment manager.

Note: This command does not remove the node, cluster, or server configurations created for the deployment environment. Regenerating the deployment environment after using the above command may not work. We strongly recommend that you manually delete the node, cluster, or server configurations and start the task from scratch. If you are using a topology pattern with webserver, ensure that the corresponding profile or servers and the webserver plug-in configuration are also deleted before the re-attempt. We recommend that you restart the deployment manager after the cleanup. Ensure that the managed nodes are resynchronized with the deployment manager before the deployment environment is rerun.

For a comprehensive list of known issues and defect fixes in this area, see the Support Portal.

For debug information, you can enable wsadmin trace by navigating to the file <dmgr_profile_path>/properties/wsadmin.properties. Uncomment the line #com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled. <dmgr_profile_path>/logs/dmgr/wsadmin.traceout will generate trace information as the commands execute. You can use this trace to troubleshoot any errors you may face while running the commands.

Refer to <dmgr_profile_path>/logs/dmgr/SystemOut.log when you encounter errors while the Process Servicer components are being configured by the commands. For debug information, you can use additional trace specifications for the deployment manager.

5 of 10 | Previous | Next

Comments

Back to top

Table of contents

• Introduction
• Introduction to the commands
• Introduction to the topology
• Creating profiles using the manageprofiles command
• Creating the Golden topology
• Reusing the deployment environment design
• Conclusion
• Download
• Resources
• About the authors

---

5 of 10 | Previous | Next

Dig deeper into WebSphere on developerWorks

IBM SmartCloud trial. No charge.

Unleash the power of hybrid cloud computing today!

---

Public and private solutions in one trial.

Special offers