In a network deployment environment it might be convenient to remotely
install WebSphere Adapter applications on nodes that reside closer to the
Enterprise Information System (EIS) rather than the node which contains the
consuming application.
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 a running deployment manager, and have sufficient privileges to install
the application on a remote machine.
Why and when to perform this task
You might want to deploy a WebSphere Adapter application remotely;
for example, on the same machine as the EIS rather than the node which contains
the consuming application (for example, a service application with a mediation
module that uses the WebSphere Adapter application to communicate with the
EIS.
To deploy a WebSphere Adapter application remotely, use the administrative
console to complete the following steps:
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 application can access the information in the EIS through
the WebSphere Adapter application, without the need for installation of the
adapter on every node in the cell.
Example
A service application (SCA mediation module) requiring communication
with an EIS, through a WebSphere Adapter is a scenario 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 service application need not reside on the same node.
A network deployment environment following best practice guidelines would
have an architecture similar to that shown in the figure
Figure 1.
Figure 1. The cell architecture of
a remote deployment of a WebSphere Adapter application in a network deployment
environment.