This topic provides information about how to start IBM® Lotus® Expeditor services in the proper order for a network deployment environment. IBM Lotus Expeditor services are dependent on other services, such as the WebSphere® Application Server node agent. You must start the prerequisites services first and then start the IBM Lotus Expeditor services.
In a Network Deployment environment, Lotus Expeditor Servers are installed on nodes managed by a Deployment Manager node. While servers may be started on the individual managed nodes, all nodes might be managed using the Deployment Manager console. The Deployment Manager console provides a central administration point for starting and stopping servers for the entire Network Deployment environment. The following instruction describe how to use the Deployment Manager console to startup the Network Deployment environment.
To start Lotus Expeditor Server:
- Start the database server and database clients running on the nodes in the cell.
- Start your LDAP server.
- If you are using an external Web server or load balancer, start it.
- Start the Deployment Manager. Run the following command on the deployment manager system from dmgr_home/bin:
- Start the node agent on each node that is managed by the Deployment Manager. Run the following command on the node system from was_profile/bin:
- Go to http://dmgr_host:port/ibm/console and log in, where dmgr_host is the fully-qualified host name of the Deployment Manager and port is the Deployment Manager administration port.
- Under Servers, select Application Servers. A list of all application servers in the cell is displayed.
- Start the DB2 Everyplace servers. Go to Servers -> Clusters, select IBMDB2eServerCluster, and click the Start button to start all servers in the cluster. Wait until the IBMDB2eServerCluster is started before you proceed.
- Start the Client Management servers. Go to Servers > Clusters, select clientMgmtServicesCluster, and then click Start to start all servers in the cluster. Wait until the clientMgmtServicesCluster is started before you proceed.
Alternatively you can start and stop the servers using the WebSphere Application Server startServer and stopServer command line tools, although using the Deployment Manager console is the preferred method. See Starting and stopping on a single system
for information on running these commands.
The scripts are not cluster-aware and only affect cluster members on that node. Also, you must manually start and stop the node agent if the node has been clustered. Make sure to start the node agent before starting any IBM Lotus Expeditor services.
To verify the servers are started correctly, go to http://dmgr_host:port/ibm/console
and log in. Where dmgr_host
is the fully-qualified host name of the Deployment Manager and port
is the Deployment Manager administration port. Under Servers
, select Application Servers
and ensure all the clientMgmtServices and IBMDB2eServer application servers show a status of started. In addition, you can test access to the service as follows:
- Verify DB2® Everyplace® is started.
Open a Web browser and go to the following URL: http://access_host : access_port/db2e/db2erdb where access_host and access_port is the host name and port used to gain access to the servers in the cluster. This is typically the host name of the external Web server or load balancer. If prompted for user ID and password, enter your IBM Lotus Expeditor administrator user ID and password. You should see a message similar to this with the current date and time: DB2e SyncServer (Mon Jun 26 15:31:16 EDT 2006).
- Verify Client Management is started.
Open a Web browser and go to the following URL: http://access_host : access_port/ManageClients/webservices where access_host and access_port is the host name and port used to gain access to the servers in the cluster. This is typically the host name of the external Web server or load balancer.
Parent topic: Starting and stopping the servers: XPD622