Dynamic Apps Platform : Administering My webMethods Server : My webMethods Server Clustering : How a My webMethods Server Cluster Works : Component Deployment in a My webMethods Server Cluster
Component Deployment in a My webMethods Server Cluster
A My webMethods Server cluster uses an asymmetrical mode of deploying components such as portlets or deployable packages.
In Asymmetrical component deployment mode, a component deployed to a node is not automatically deployed to other nodes in the cluster. In Asymmetrical deployment mode, you need to manually deploy a component locally to each node where it is needed. In this mode it is possible to have different versions of a component running at the same time on different nodes of a cluster. Because component registration is centralized in the My webMethods Server database, the registration is performed only once by the first node on which the component is deployed. Because of this dependency, changes made to a component that can affect component registration or My webMethods Server taxonomy can potentially break other versions of the component residing on a different node. Some examples of changes to a component that can cause changes to the My webMethods Server database schema are:
*Adding or removing a portlet preference.
*Adding, removing, or changing a field in a DBO (Dynamic Business Object) table.
*Adding, removing, or changing a field in a task type business data.
*Adding, removing, or updating My webMethods Server taxonomy
Asymmetrical component deployment mode enables you to deploy and test a modified component on one or more nodes before deploying it to the entire cluster.
Copyright © 2017 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback