IBM BPM, V8.0.1, All platforms > Installing, deploying, and undeploying applications in the runtime environment > Deploying service modules
Considerations for deploying service applications on clusters
Deploying a service application on a cluster places additional requirements on you. It is important that you keep these considerations in mind as you deploy any service applications on a cluster.
Clusters can provide many benefits to your processing environment by providing economies of scale to help you balance request workload across servers and provide a level of availability for clients of the applications. Consider the following before deploying an application that contains services on a cluster:
- Will users of the application require the processing power and availability provided by clustering?
If so, clustering is the correct solution. Clustering will increase the availability and capacity of your applications.
- Is the cluster correctly prepared for service applications?
You must configure the cluster correctly before deploying and starting the first application that contains a service. Failure to configure the cluster correctly prevents the applications from processing requests correctly.
- Does the cluster have a backup?
You must deploy the application on the backup cluster also.
Cross-cluster modules
JNDI resources must not be shared across clusters. A cross-cluster module requires that each cluster have different JNDI resources. A scenario matching the following criteria will result in the log file indicating a NameNotFoundException:
- One module has a configured binding that generates JNDI resources.
- Another module is configured to use those generated JNDI resources.
- The modules are deployed in different clusters.
To resolve the problem, modify the module properties so that each module uses the JNDI resources in the same cluster as it.