IBM WebSphere Process Server is a runtime platform for business integration solutions developed using IBM WebSphere Integration Developer.

Many existing business functions for a company's IT infrastructure are written based on Java^TM 2 Enterprise Edition (J2EE) stateless Enterprise Java Beans (EJB). When you design and implement new business process integration applications, it is important that you have the ability to leverage and integrate these functions easily.Overview diagramThe scenario we use in this article is pretty straightforward. It consists of one Service Component Architecture (SCA) module that has a Java component, which uses the imported EJB service.

Software prerequisitesYou need to install:

• WebSphere Integration Developer V6
• WebSphere Process Server V6 test environment

Configuration
In this section, we develop a sample EJB application and an SCA module that utilizes the EJB service.

You can begin by creating the enterprise application, package, and EJB session.

1. Create an enterprise application called Echo (Figure 1) with one EJB module, EchoEJB2. Create a package called com.ibm.issw.poc.invokeejb.

3. Create a stateless EJB session called Bean Echo (Figure 2)
4. Create a simple method called echoSimple, and promote it the remote interface:

   public String echoSimple(String name){
          System.out.println("inside echoSimple");
          return "Hello, " + name;
       }

5. Open the ejb deployment descriptor, and notice the default JNDI name (Figure 3) for the EJB:

   ejb/com/ibm/issw/poc/invokeejb/EchoHome

6. Create an EJB client (Figure 4) project and jar that will be used later in the SCA module.
7. Right-click and select EchoEJB => EJB Client Jar => Create EJB Client Project and enter EchoEJBClient in the name field.
8. Run and test the EJB application (see Figure 5).

Create an EJB component
To integrate the EJB into the WebSphere Process Server SCA component:

1. Create a module called InvokeEcho.
2. From the Dependencies editor (Figure 6), select EchoEJBClient as the dependent Java project and click Add to add EchoEJBCLient as the dependent Java project.

   It is important to add module dependency at this point. When we add the interface later, the wizard will be able to find the remote EJB interface.

3. From the Assembly editor, open the module, InvokeEcho in Assembly editor, add an Import component (Figure 7) on the canvas. Change the name to EchoEJB.
4. Add the interface for the import:
   1.  Click the Add Interface icon.
   2.  In the resulting window, select Show Java.
   3.  Enter echo in the Filter by interface field.
   4.  Select Echo from Matching interfaces . This interface is from project
   /EchoEJBClient/ejbModule (see Figure 8).
   5.  Click Ok and save the module diagram (Figure 9).
   6.  Generate the Session EJB Binding.

1. Right-click the EchoEJB import and select Generate Binding => Stateless Session Bean Binding (Figure 10).
2. Notice how the icon changed in the import (see Figure 11).
3. Select the Properties view and the Binding tab. You can see that the JNDI name field is now populated (see Figure 12).

1. Drag and drop a Java Component onto the assembly canvas and change the name to InvokeEcho (see Figure 13).
2. Create an interface (Figure 14) called InvokeEchoInterface with a one-way operation callEcho and one input parameter:
3. Select the Java component and add an interface for it, InvokeEchoInterface.
4. Wire the InvokeEcho and EchoEJB together (see Figure 15).

   Notice that a reference EchoPartner has been generated. We will use it in the Java Component implementation (see Figure 16).

5. Select and right-click the Java Component and generate the default Java implementation. When the implementation opens, replace the callEcho method with the following code:

       try {
   
         System.out.println("in callEcho");
         // Create an instance of the ServiceManager
         ServiceManager serviceManager = new ServiceManager();
   
         Echo echo= (Echo)serviceManager.locateService("EchoPartner");
   
         String result = echo.echoSimple(name);
         System.out.println("called imported EJB, and response is " + result);
   
       } catch (Exception e) {
         e.printStackTrace();
       }

6. Running and testing the scenarioTo test the scenario:
   1.  Right-click InvokeEcho and select Test Component (Figure 17).
   2.  In the test configuration, remove the emulator for EchoEJB, since we want to invoke the real EJB implementation.
   3.  Enter a value for the name field and click Continue.
   4.  Notice the expected result (Figure 18).

Congratulations, you've successfully imported and invoked the Echo EJB from the SCA component, InvokeEcho. In this scenario, the SCA module and the EJB service are running on the same server.

Conclusion
This article helped you implement a WebSphere Process Server solution that integrates EJB services. As you can see, using EJB services from an SCA component is easy to do. Reusing EJB-based services in this way creates tremendous opportunities for integration products, such as WebSphere Process Server..

(This article was first published on developerWorks WebSphere at http://www.ibm.com/developerWorks/websphere.) This article shows you how to use IBM WebSphere Process Server Version 6 and IBM WebSphere Integration Developer Version 6 to integrate existing J2EE applications without making changes to them.