When a service component invokes another service component synchronously,
you must configure the invoking service component to point to the system running
the target so the target service can communicate results to the invoking service
component.
Before you begin
The task assumes that you have already installed WebSphere® Process Server on the systems
for which you are configuring the communications but have not yet installed
the applications involved. You are using an administrative console that can
examine and change the configuration for both servers involved.
Why and when to perform this task
A service component invoking another service synchronously can communicate
with the target only by configuring the export Java Naming and Directory Interface
(JNDI) name on the target system to a JNDI name on the invoking system.
Note: For the purposes of this task,
the invoking service module resides on system A and the target resides on
system B.
For
the purposes of this task, Figure 1 contains the information to use in the configuration.
Figure 1. Invoking a service
on a different system
Note: For simplicity, only the servers involved in
this communication in each cell is shown and each server resides on a different
physical machine.
Steps for this task
- Install the applications on each server.
- Create a new namespace binding on the invoking system (System A,
in the example) pointing to the export on the target system.
On
the Name Space Bindings pane, l select a scope of Cell
and click Apply. With the changed scope, click New in
the display to create then new binding.
In the wizard, specify the following
(the values are appropriate for the example configuration):
- Binding type is CORBA
- The basic properties are:
When finished, click Next and verify the values
on the Summary page. After verifying, click Finish.
Your system displays your new binding.
- Save your changes by clicking Save.
What to do next
Start the applications. The service component on System A can now
synchronously invoke the service on System B.