When you invoke a Service Component Architecture (SCA) module in
a different cell synchronously you must add a name space binding to
bind the remote SCA service.
Before you begin
The task assumes that:
- You have received bootstrap host information for the cell that is running
the service your cell wants to invoke.
- You are at the administrative console for the consuming cell.
- You have already installed the SCA modules consuming the target service.
Why and when to perform this task
To communicate synchronously with a SCA service in another cell you
need to configure your JNDI name space to find the service. You perform this
task to configure your JNDI name space.
Note: For the purposes of this task,
the consuming service module runs on cell A and the providing service module
runs on cell B.
For
the purposes of this task, Figure 2 contains
the IP information to use in the configuration.
Figure 1. A synchronous environment across cells
Steps for this task
- Obtain the bootstrap host information from
the administrator of the providing cell.
Assuming that the bootstrap
port is 2810 in Figure 2,
this information would look like corbaname:iiop:9.26.237.144:2810 (corbaname:iiop:9.26.237.150:2810).
- Create a new namespace binding on the invoking cell (Cell A, in
the example) pointing to the export in the providing cell.
On
the Environment > Naming > Name Space Bindings panel,
select a scope of Cell and click Apply.
With the changed scope, click New in the display to
create the new binding.
In the wizard, specify the following (the values
are appropriate for the example configuration):
- Binding type is Indirect
- The basic properties are:
When finished, click Next and verify the values
on the Summary page. After verifying, click Finish.
The administrative console displays your new binding.
- Save your changes by clicking Save.
What to do next
Start the application. The SCA module on Cell A can now synchronously
invoke the SCA module on Cell B.
Last updated: Wed 01 Nov 2006 07:47:12
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)