Transaction interoperability is implemented based on the OTS specification. The object mentioned here is the CORBA Object, which is affected by the transaction.

When using OTS, an interceptor (a listener type) which can process transactions is added to CORBA. This additional interceptor handles the transaction related part of the IIOP protocol header. Through this, JEUS, which plays a role of a client or server, supports transaction propagation between different remote systems such as WAS or JEUS.

CSIv2 specification guarantees security interoperability. If this CSI is used, like the OTS, an interceptor that can process security is added to ORB, and this interceptor handles the header and other security related parts.

Security interoperability starts by attaching security information for CSI to Interoperable Object Reference (IOR) of EJB reference. If IOR is registered to a naming service, the client side ORB that is trying to used it and the JEUS MS handles negotiation on the security level of the IIOP protocol. JEUS MS acts as a client when it needs CSI Services to call another EJB bean.

Besides the basic JNDI Naming Service provided by MS, the COS Naming Service for CORBA objects can also be added. An EJB reference (stub) exposed to RMI-IIOP is saved in the COS Naming Service, and an EJB client looks up the reference and uses it.

The COS Naming Service operates in the JEUS Manager JVM and uses BASEPORT + 4 (e.g. 9,740) as the service port.

In order to use interoperability needed for RMI-IIOP clients and servers, interoperability property must be activated. This must be done to initialize the ORB.

In order to activate the property, click [Servers] and then select a server from the search list. In Advanced Options of the Server page, enable the 'Enable Interop' option.

[Figure 5.1] Configuring interoperability Activation

For more information about CSlvs, refer to "5.2.3. Configuring the CSIv2 Security Interoperability".

In order to perform CSIv2 protocol, use the information from two additional security environment files and JEUS Security Manager. The two additional security environment files are keystore and truststore.

he paths and necessary information of these two files can be configured through the WebAdmin or system property.

CSIv2 related settings are specified in the Interop Ssl Config of the Enable Interop.

[Figure 5.2] Configuring CSIv2 Security Interoperability - Interop Ssl Config

Besides WebAdmin, the setting can also be configured through the system property of the execution script. However, WebAdmin configurations have higher priority.

The following are options for this setting. Set this value by using -D option.

Authentication and authorization may not be needed between trusted nodes.

By setting the IP address to jeus.ejb.csi.trusthosts, you can prevent any unnecessary security checks between trusted nodes. JEUS Security Manager uses the guest user, which represents an anonymous principal for anonymous user access.

In order to expose EJB to RMI-IIOP, configure the <export-iiop> option for each EJB in jeus-ejb-dd.xml. If the <export-iiop> option is set, EJB Home Reference is registered to a COS Naming Service using the given <export-name>. This way, EJB Reference can be fetched and used through the COS Naming Service.

The following is an example of the jeus-ejb-dd.xml file in which EJB RMI-IIOP is configured.

...
<jeus-bean>
   <ejb-name>CalcEJB</ejb-bean>
   <export-name>ejb/Calc</export-name>
  <export-iiop>
     <only-iiop>true</only-iiop>
  </export-iiop>
</jeus-bean>
...

The following table explains the configuration tag.

The following is the method for calling RMI-IIOP EJB on JEUS or another vendor's WAS from applications running on a JEUS MS.

First, COS Naming Server looks up EJB Home Reference (Stub). The Naming Server can get it directly by using the JNDI APIs corbaname URL as follows:

    InitialContext ctx = new InitialContext();
    Object obj = ctx.lookup("corbaname:iiop:1.2@192.168.11.22:9740#ejb/Calc");

    CalcHome home = (CalcHome)PortableRemoteObject.narrow(obj, CalcHome.class);
    Calc calcRef = home.create();

URL has the form of "corbaname:iiop:1.2@<host>:<port>#<name>", and <host> and <port> are the address of the COS Naming Server. Also, by directly specifying the COS Naming Server as the PROVIDER URL, you can get and use the InitialContext.

Since there are multiple methods to specify the PROVIDER URL, you should specify one to use as in the following example.

    Hashtable env = new Hashtable();
    env.put(Context.PROVIDER_URL, "iiop://192.168.11.22:9740");
//  env.put(Context.PROVIDER_URL, "iiopname://192.168.11.22:9740");
//  env.put(Context.PROVIDER_URL, "corbaname:iiop:1.2@192.168.11.22:9740");
//  env.put(Context.PROVIDER_URL, "corbaloc:iiop:1.2@192.168.11.22:9740");

    InitialContext ctx = new InitialContext(env);
    Object obj = ctx.lookup("ejb/Calc");

    CalcHome home = (CalcHome)PortableRemoteObject.narrow(obj, CalcHome.class);
    Calc calcRef = home.create();

For clients using dependency injection or a logical JNDI name in the form of "java:comp/env/", the <export-name> option should be mapped to the previous corbaname URL in the JEUS application DD file, such as the jeus-web-dd.xml file.

@EJB(name="ejb/Calc")
private CalcHome calcHome;

<ejb-ref>
    <jndi-info>
        <ref-name>ejb/Calc</ref-name>
        <export-name>corbaname:iiop:1.2@192.168.11.22:9740#ejb/Calc</export-name>
    </jndi-info>
</ejb-ref>

The method to call RMI-IIOP EJB of JEUS from applications running on another vendor's WAS is similar to the method described in "5.3.1. JEUS Managed Servers (MSs)" .

In this case, check whether ORB configuration is needed like in JEUS, and configure it if necessary. For more information, refer to the relevant product documentation.

Since ORB runtime and related settings are not configured for standalone clients, you need to add the jclient.jar client library, as well as the omgapi.jar and peorb.jar files to the class path. You must also add the jeus.client.interop=true system property.

The method to obtain the EJB Home Reference (Stub) is similar to that in "5.3.1. JEUS Managed Servers (MSs)". However, you should also configure the JNDI provider from JEUS.

    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY, "jeus.jndi.JNSContextFactory"); 
    env.put(Context.PROVIDER_URL, "iiop://192.168.11.22:9740");

    InitialContext ctx = new InitialContext(env);
    Object obj = ctx.lookup("ejb/Calc");

    CalcHome home = (CalcHome)PortableRemoteObject.narrow(obj, CalcHome.class);
    Calc calcRef = home.create();