This section provides a brief description of the WebSphere® Application Server topologies supported by the IBM® Content Manager web services.
Web services is one of the components of IBM Content Manager and supports WebSphere Network Deployment. Therefore, the web service application can be deployed on a remote application server node, which does not need to be on the machine where IBM Content Manager is installed if there is a node (either deployment manager node or application server node federated to the deployment manager) on the machine. The WebSphere Network Deployment management is responsible for transferring the application to the target node that can be on a remote machine. The IBM Content Manager web service application can run depending on local resources only. It does not refer to any information on the machine where IBM Content Manager is installed.
A managed node is an application server node that is already federated to a deployment manager. This node can be local or remote to the machine where the IBM Content Manager is installed. If it is local, it has the same topology as in unmanaged node. If it is remote, the IBM Content Manager installed machine must also have a node (deployment manager node or application server node federated to the deployment manager). The machine where the IBM Content Manager is installed and the machine where the managed node is must be in the same management hierarchy of Network Deployment.
In both topologies, A and B, an application server name must also be supplied for specifying a deployment target besides the node name. Because the web services configuration program does not create a designated server, the server must be already existing at the time when the application is deployed.
A server cluster is a group of application servers on different application server nodes that share the load for particular applications. This topology is similar to the managed node scenario. The difference is that the deployment target consists of multiple application server nodes. These nodes are grouped into a cluster. The cluster name is used as the deployment target. The deployment manager automatically deploys the web services applications onto each member servers in the cluster when the cluster name is used.
You must be able to reach the cluster from the machine where IBM Content Manager is installed. The machine that has IBM Content Manager installed must also have a node (deployment manager node or application server node federated to the deployment manager).
