Configuring servers to invoke services synchronously

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.

About 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.

For the purposes of this task, the invoking service module resides on System A and the target resides on System B. Figure 1 contains the information to use in the configuration.

Note: For simplicity, only the servers involved in this communication in each cell is shown and each server resides on a different physical machine. However, the configuration for cross-cluster asynchronous invocation can apply for the configuration in the same cell too.

1. Install the applications on each server.
2. 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 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 CORBA
   2. The basic properties are:
      • Binding identifier is a unique string, in our example: sca_import_test_sca_cross_simple_custinfo_CustomerInfo
      • Name in Name space is the JNDI name of the enterprise Java bean (EJB) you are invoking on the target system, for example:

        sca/AppB/export/test/sca/cros/simple/custinfo/CustomerInfo

        This names the export interface on the target system.
      • Corbaname URL is the IP address and port number of the naming service on the target system:

        corbaname:iiop:host:port/NameServiceServerRoot#<package.qualified.interface>

        Note: For WebSphere® Business Process Manager, the port is the BOOTSTRAP_ADDRESS.

        For example:

        corbaname:iiop:9.26.237.144:2809/NameServiceServerRoot#sca/
        		AppB/export/test/sca/cros/simple/custinfo/CustomerInfo

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

   Your system displays your new binding.
3. Save your changes by clicking Save.
4. If your cross cell configuration consists of servers on the same host with the same name and you encounter JNDI lookup failures with a NameNotFoundException, then you need to set a system property.

   Follow the directions in the Application access problems under the subheading Two servers with the same name running on the same host are being used to interoperate.