Migrating from WebSphere Business Integration Adapter for Enterprise Java Beans to EJB bindings

This article will help you migrate from WebSphere Business Integration Adapter for Enterprise JavaBeans to the EJB bindings supported by WebSphere Process Server. The Adapter for Enterprise JavaBeans will reach end-of-support in 2014, and integration solutions using it will have to be replaced with the JCA bindings.

Bharathi Manian (bharathi.manian@in.ibm.com), Software Developer, WebSphere Adapters team, IBM

Photo of  Bharathi ManianBharathi Manian is a Software Developer on the WebSphere Adapters team at the IBM India Software Lab in Bangalore, India. She has six years of experience and her areas of expertise include Java, J2EE, and Web technologies. She received a Bachelor's degree in Computer Engineering from Birla Institute of Technology and Science in Pilani, India. You can contact Bharathi at bharathi.manian@in.ibm.com.



19 September 2012

Also available in Portuguese

Introduction

This article will show you how to migrate a business integration solution containing an IBM® WebSphere® Business Integration Adapter for Enterprise JavaBeans (hereafter called a WebSphere EJB Adapter) into an Enterprise JavaBeans binding (hereafter called an EJB binding) in an IBM WebSphere Process Server environment.

The WebSphere EJB Adapter enables the integration broker to exchange business objects with enterprise beans that have been designed using the EJB architecture and deployed on an application server. Similarly, in a WebSphere Process Server environment, EJB bindings enable Service Component Architecture (SCA) components to invoke services provided by EJBs deployed on an application server.

Migration overview

In the existing environment, the WebSphere EJB Adapter receives a business object from the integration broker -- WebSphere InterChange Server. Using the information contained in the business object, the Adapter invokes the EJB deployed on a J2EE application server and returns the response back to the integration broker:

Figure 1. Existing solution using WebSphere EJB Adapter
Existing solution using WebSphere EJB Adapter

Migrating to EJB bindings has several advantages:

  • EJB bindings support import and export bindings, while WebSphere EJB Adapter supports only request processing.
  • EJB bindings support transactions, while WebSphere EJB Adapter does not.
Figure 2. EJB bindings in WebSphere Process Server interacting with an EJB
EJB bindings in WebSphere Process Server interacting with an EJB

Migration in IBM Integration Designer

Using the Migration Wizard in IBM Integration Designer, you can migrate WebSphere InterChange Server artifacts into deployable artifacts and place them in projects within an IBM Integration Designer workspace:

  1. In IBM Integration Designer, open the Import Wizard and select File => Import. Under Business Integration, select WebSphere InterChange Server Repository and then click Next:
    Figure 3. Import Wizard in IBM Integration Designer
    Import Wizard in IBM Integration Designer
  2. In the Import Wizard, browse and select the InterChange Server Repository project:
    Figure 4. Select WebSphere InterChange Server repository
    Select WebSphere InterChange Server repository
  3. In the IBM Integration Designer Library Name field, enter the name of a new designer library or select an existing one and then click Next.
  4. The Configure Connector Migration screen lists the connector files in the InterChange Server repository. For the EJB Connector select EJB binding.
  5. Click Add and browse to choose the EJB JAR file that is referenced by the InterChange Server repository. Click Next:
    Figure 5. Configure connector migration
    Configure connector migration
  6. Choose the recommended options in the Select the Conversion Options screen and then click Next:
    Figure 6. Conversion options in wizard
    Conversion options in wizard
  7. The Migration Summary page is displayed with the options chosen. If you need to change the entries, click Back, otherwise click Finish to close the wizard:
    Figure 7. Migration summary
    Migration summary
  8. The migration is now completed, and the artifacts are generated and placed in different modules:
    Figure 8. Modules in IBM Integration Designer
    Modules in IBM Integration Designer

Testing

You can test the migrated application by implementing the output component in the EJBConnector project.

  1. Deploy the generated modules in WebSphere Process Server and ensure that the required EJB service is deployed and running.
  2. Test the flow by invoking the Test Component from the CustomerRetrieve module and sending the input request. Then you can invoke the service and examine the results:
    Figure 9. Sample request
    Sample request
    Figure 10. Response
    Response

Conclusion

This article showed you how to use the Migration Wizard in IBM Integration Designer V7.5 to migrate from a WebSphere EJB Adapter to an EJB binding.

Resources

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into WebSphere on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=835891
ArticleTitle=Migrating from WebSphere Business Integration Adapter for Enterprise Java Beans to EJB bindings
publish-date=09192012