Table of Contents
Advertisement
The syntax is for stopping the messaging server or bcgserver for the component
servers is:
stopServer <server_name>
Where server_name is bcgmas for stopping the messaging server, and bcgserver
for the component servers.
Starting and stopping the components in a full distributed
mode system
Before you begin, you must know that there are four clusters in full distributed
mode system. They are as follows:
v bcgmasCluster
The messaging cluster that has messaging servers named bcgmas. There must be
at least one messaging server running for the WebSphere Partner Gateway
components to operate.
v bcgconsoleCluster
The WebSphere Partner Gateway Console component cluster that has servers
named bcgconsole.
v bcgreceiverCluster
The WebSphere Partner Gateway Receiver component cluster that has servers
named bcgreceiver.
v bcgdocmgrCluster
The WebSphere Partner Gateway Document Manager component cluster that has
servers named bcgdocmgr.
The names shown here are the installation default names. Be aware that during
installation, the installer might have chosen different names and you must use
these names instead of the default names.
Starting servers in a full distributed mode system
To start your servers in a full distributed mode system, the startup sequence is as
follows:
1. Messaging servers
2. WebSphere Partner Gateway document manager servers
3. WebSphere Partner Gateway receiver servers (or console servers)
4. WebSphere Partner Gateway console servers (or receiver servers)
Note: The receiver and console servers can be started in either order.
Starting all the servers using the Deployment Manager
About this task
1. Select the messaging cluster bcgmasCluster and click Start.
Note: Wait until the cluster has started before starting the WebSphere Partner
Gateway component clusters.
2. Select the bcgdocmgrCluster and click Start.
3. Select the bcgreceiverCluster (or the bcgconsoleCluster) and click Start.
4. Select the bcgconsoleCluster (or the bcgreceiverCluster) and click Start.
Chapter 2. Managing the WebSphere Partner Gateway component applications
11
Advertisement
Table of Contents
