Calling Service Component Architecture services in another cell synchronously

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:

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 cellsThe figure shows the service provider cell and the name space binding between it and consumer cell 1 and consumer cell 2.

Steps for this task

  1. 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).

  2. 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):
    1. Binding type is Indirect
    2. The basic properties are:
      • Binding identifier is a unique string, for example: sca_import_test_sca_cross_simple_custinfo_CustomerInfo
      • Name in Name Space is the JNDI name of the enterprise Java™ bean (EJB) of the service you are invoking in the providing cell, for example, sca/SimpleBOCrsmB/export/test/sca/cros/simple/custinfo/CustomerInfo . This names the export interface in the providing cell.
      • Provider URL is the bootstrap host information of the providing cell you received in step 1. For example corbaname:iiop:9.26.237.144:2810 (corbaname:iiop:9.26.237.150:2810).
      • JNDI name is the JNDI name of the enterprise Java bean (EJB) that represents the service you are invoking on the providing cell, for example, sca/SimpleBOCrsmB/export/test/sca/cros/simple/custinfo/CustomerInfo. This should be the same value as the Name in Name Space.
        Note: Deploying the module on the providing cell creates this name automatically. Contact the providing cell administrator to obtain this name.

      When finished, click Next and verify the values on the Summary page. After verifying, click Finish.

    The administrative console displays your new binding.
  3. 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.
Related tasks
Providing synchronous access to Service Component Architecture services from outside the cell
Providing Service Component Architecture services asynchronously across cells
Using Service Component Architecture services asynchronously across cells

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)