This describes how to federate a server in a stand-alone profile
that runs applications that contain business processes or human tasks or both
to a new deployment manager cell.
Before you begin
The
deployment manager is running, and you know its host name and port number.
Business Process Choreographer is configured on the server in a stand-alone
profile. The Business Process Choreographer database in the stand-alone profile
must be remotely accessible from the deployment manager cell. For this reason,
your server cannot be based on the sample Business Process Choreographer configuration
that uses embedded Cloudscape.
Why and when to perform this task
You have one or more applications, which contain business processes
or human tasks, running on a stand-alone server, and you want to federate
this server into a network deployment environment. One of the following applies:
- You want to move an application from a test environment to a production
environment.
- You want to use ND to administer your server and application.
Steps for this task
- If the node includes a large number of applications, increase the
timeout for the administrative connector.
- From the command line, run the addNode command
with the -includeapps and -includebuses options. For details about this command and possible errors that can occur, refer
to the WebSphere Application Server Network Deployment information center, addNode command. For
example, if the deployment manager has a host name of dmgr_host and
uses port dmgr_port, enter the command:
addNode dmgr_host dmgr_port -includeapps -includebuses
For example, if the deployment manager has a host name
of any.hostname.com and uses port 9043,
your profile name is ProcSvr07, your user ID is admin,
and your password is secret, enter the command:addNode any.hostname.com 9043 -profileName ProcSvr07 -username admin
-password secret -includeapps -includebuses
If any of the prerequisites are not met, an error message is displayed.
Otherwise, the server is stopped and the server is federated into a new deployment
manager cell.
- Set the JDBC provider's WebSphere variables on the deployment manager
node. The variable for the path for the JDBC driver that you are
using must be set. That is one of the following:
- DB2UNIVERSAL_JDBC_DRIVER_PATH (for DB2)
- UNIVERSAL_JDBC_DRIVER_PATH (for DB2)
- CONNECTJDBC_JDBC_DRIVER_PATH (for SQL Server)
- ORACLE_JDBC_DRIVER_PATH (for Oracle)
- Start the server to activate the changes.
- If you cannot access the business applications that are running
on the server, use the administrative console on the deployment manager to
make sure that the virtual host and alias definitions for the application
server match the new cell.
Result
Your applications are now running on the same server, but the server
is now in a cell that can be administered using the deployment manager.
What to do next
If required, you can promote the server to a cluster.