In a network deployment environment it may be convenient to remotely
install WebSphere Adapter applications on nodes which reside closer to the
EIS (e.g., on the same machine as the EIS) than the node which contains the
consuming application (e.g., an application which contains a BPEL process).
The best practice for such remote deployment is described herein.
Before you begin
To perform this task you must have a WebSphere Adapter embedded in
an application. You must also be working in a network deployment environment
with an operating Deployment Manager, and have sufficient privileges to install
the application on a remote machine.
Why and when to perform this task
This task is appropriate when you have a consuming application, such
as a BPEL process application, which requires communication with an EIS mediated
by a WebSphere Adapter application in a network deployment environment.
Steps for this task
- Install the consuming application on any node of the cell.
- Remotely install the WebSphere Adapter application on a node situated
in close proximity to the EIS with which it interacts.
Result
The consuming process can access the information in the EIS via the
WebSphere Adapter application, without the need for installation of the adapter
on every node in the cell.
A BPEL process application requiring communication with an EIS, mediated
by a WebSphere Adapter application is a situation where remote deployment
of the WebSphere Adapter application is ideal. The WebSphere Adapter application
can reside on a node in the cell which is conveniently close to the EIS with
which it interacts. The BPEL process application need not reside on the same
node. A WebSphere Process Server Network Deployment environment following
best practice guidelines would have an architecture similar to that shown
in figure 1.
Figure 1. The cell architecture of a remote deployment of a
WebSphere Adapter application in a network deployment environment.