WAS v8.5 > Develop applications > Develop SCA composites > Specify bindings in an SCA environment

Configure EJB bindings in SCA applications

Use this task to learn how to use EJB bindings in SCA applications.

Support is provided for EJB bindings in 2.x and 3.x-style beans, for service and reference.

The EJB bindings do not support interface.wsdl files.

The following is an example of an composite definition that has a service exposed over an EJB 3.x binding: 

<?xml version="1.0" encoding="UTF-8"?> <composite xmlns="http://www.osoa.org/xmlns/sca/1.0" targetNamespace="http://neworder/sca/jdbc" 
name="NewOrderComposite"> 
<component name="NewOrderEJB3ServiceComponent"> <implementation.java class="neworder.sca.jdbc.NewOrderServiceImpl" requires="managedTransaction.local"/> <service name="NewOrderService" requires="suspendsTransaction"> <interface.java interface="neworder.sca.jdbc.NewOrderService"/> <binding.ejb ejb-version="EJB3"/> </service> </component> </composite>

A client that wants to invoke the resultant enterprise bean would treat it like any other enterprise bean and not like a regular SCA service. CompositeContext.getService is not supported for a non-SCA binding, therefore, a getService() on the CompositeContext would not work here. The following is the client code for the previous example: 

InitialContext ctxt = new InitialContext();
  Object remoteObj = ctxt.lookup("ejb/sca/ejbbinding/NewOrderEJB3ServiceComponent/NewOrderService#neworder.sca.jdbc.NewOrderServiceRemote");
  NewOrderServiceRemote newOrderRemote = (NewOrderServiceRemote) PortableRemoteObject.narrow(remoteObj, NewOrderServiceRemote.class);

The following is an example of an composite definition containing references to both EJB 2.x and EJB 3.x bindings: 

<?xml version="1.0" encoding="UTF-8"?> <composite xmlns="http://www.osoa.org/xmlns/sca/1.0"
targetNamespace="http://erww.workload" name="ConvertComposite"> 
<component name="ConvertInputOutputServiceComponent"> <implementation.java class="convert.inputoutput.sca.ConvertInputOutputServiceImpl"

<reference name="priceQuoteSessionReference"> <interface.java interface="priceQuoteSession.PriceQuoteSession"/> <binding.ejb uri="corbaname:iiop:localhost:2809/NameServiceServerRoot#ejb/session/PriceQuoteSessionFacadeBean"/> </reference> </component> </composite>

Different binding.ejb attributes can be used for service side EJB bindings or reference side EJB bindings. The following information explains how the default value is calculated for each side:


Service side

The service side EJB binding applies only to JAR-packaged SCA applications.

EJB 2.0-level beans

URI is the JNDI name for the home; it can be calculated with the default short name in the following form:

    /sca/ejbbinding/component_name/service_name

Therefore, the URI can be calculated as:

    corbaname:iiop:localhost:2812/NameServiceServerRoot#ejb/sca/ejbbinding/component_name/service_name
We can use it to look up home.

EJB 3.x-level beans

The URI contains the component-id, therefore, it is calculated the same as the EJB 2.0 beans as follows:

    sca/ejbbinding/component_name/service_name

The URI can be calculated as: 

corbaname:iiop:localhost:2812/NameServiceServerRoot#ejb/sca/ejbbinding/component_name/service_name#package.qualified.interface of 
SCA Java interface with prefix of Remote or Local to the class name
We can use it directly to get the business interface.

The following code example displays as if it were a session bean:

    <session name="ServiceNameBean" component-id="sca/ejbbinding/component_name/service_name"/>

When an SCA service is exposed through an EJB service binding, the service is exposed through an enterprise bean. During deployment, the SCA runtime generates a session bean for the service exposed through the EJB binding. The caller of the composite service can invoke this service by accessing the generated enterprise bean as if they are invoking any enterprise bean.

The generated enterprise bean for the composite service is in the profile_root/installedApps/cell_name/sca.composite.nameApp.ear/ directory. Callers need to include the client required classes, such as remote or home, of the generated bean in the classpath or bundle the classes in the JAR file. In addition, if the caller application is running on a non-WebSphere application server, a "Bare" Java Standard Edition (SE), or a version of WAS previous to version 7.0 without the Feature Pack for EJB 3.0, then run the createEJBStubs command for the generated EJB module to generate client-side stubs and include the generated subs at the client application. The createEJBStubs command is under the profile_root/installedApps/cell_name/sca.composite.nameApp.ear/ directory. See the topic on the create stubs command.


Reference side

The reference side EJB binding applies to both JAR-packaged applications and web application archive (WAR)-packaged applications, if not otherwise stated.

A lookup issue for EJB 3.x reference bindings might occur when the URI follows the corbaname:iiop:host:port/NameServiceServerRoot##ejb3_binding_longform pattern This problem exists only for EJB 3.x reference bindings. When the EJB 3.x reference binding URI follows the corbaname:iiop:host:port/NameServiceServerRoot##ejb3_binding_longform pattern, where ejb_binding_longform is ejb/<component-id#<package.qualified.interface>, and if more than one enterprise bean that is implementing the same interface is deployed on that server, lookup may not be directed to the correct EJB with corresponding component ID. An example of a URI where this problem can occur is as follows: 

uri="corbaname:iiop:host:port/NameServiceServerRoot#ejb/EJB3CounterSample/EJB3Beans.jar
/StatelessCounterBean#com.ibm.websphere.ejb3sample.counter.RemoteCounter

There are two enterprise beans implementing the com.ibm.websphere.ejb3sample.counter.RemoteCounter interface. To avoid this issue:

To resolve this problem, follow these guidelines:

Different patterns of the SCA EJB reference binding URI are based on the user setup and configurations. If the SCA EJB reference binding is accessing a stateless session bean on the same server, the EJB reference binding URI can be designated as the JNDI name, uri="ejb/com/app/resumebank/ResumeBankHome". If the SCA EJB reference binding is referencing another SCA service with an EJB binding in the same server, the URI can be designated as the JNDI name, uri="ejb/com/app/resumebank/ResumeBankHome".

If the EJB reference binding is accessing a stateless session bean that is deployed in the same cell, the URI can be based on cluster/node/server setup, for example: 

uri="cell/clusters/cluster2/ejb/com/app/resumebank/ResumeBankHome" 
uri="cell/nodes/node_name/servers/server_name/ejb/com/app/resumebank/ResumeBankHome"

If the EJB reference binding is accessing a stateless session bean on a different cell (cross cell) or a mixed cell, create a namespace binding, either an enterprise bean or Corba type, in the dmgr console and use the name in namespace binding in EJB reference binding URI such as, uri="cell/persistent/name_in_namespace_binding". For example, uri="cell/persistent/neworder" where neworder is name in the namespace binding.


Subtopics


Related concepts:

EJB 3.0 and EJB 3.1 application bindings overview
Unsupported SCA specification sections


Reference:

Create stubs command


+

Search Tips   |   Advanced Search