5 SOA Best Practices According to IBM

  • Develop architecture with a vision for the future – looking beyond simple connectivity and focusing more on architecture is the most common recurring need for SOA implementations.
  • Foresee linkages from IT to your business processes – implementation of an architecture that transitions IT into the role of a service provider for business functionality.
  • Create an organizational structure to support SOA including culture, skills, training, teaming, organization structure, decision making, reward systems, collaboration and governance.
  • Build a scalable infrastructure – create a baseline for your services performance and scalability using appropriate instruments and measurements.
  • Enable operational visibility – focus on governance and service management.


Web Services from Stateless Session EJB3 with Websphere Integration Developer

How to create a bottoms-up Websphere with Websphere Integration Developer that is deployed to Websphere Application Server V7.

Below is the steps to create an simple Web Service using Websphere Integration Developer:

1. Open up Websphere Integration Developer and create an new EJB Project

Step 2: Click on the ‘New’ button to create a new EAR Membership.

The following 3 files will be created

Step 3: Create a new Stateless Session Bean

Step 4: Complete the following information below (Important to select Remote)

Step 5: Open the Bank interface object and add a method.

Step 6: Open your Stateless Session Bean File and right click and select ‘Override/Implementation Methods’, make sure the @Override notation is added to your code (see in red block)

Step 7: Add code inside your method

Step 8: Verify that there is no error.

Step 9: Add an Application Server to your WID IDE and start the server.

Step 10: Right click on your Application Server and click on ‘Add and Remove Projects’ and Select the BankAccount project

Step 11: Verify that the Application Server has successfully synchronized the new project and no errors occurred.

Step 12: Creating the Web Service is done in the following Steps, right click on your Stateless Session Bean and Select Web Service -> Create Web Service.  Your will see the following screens:

Confirm that the right Server type is selected, being WAS, WPS, WBM or any Application Server

For this example the binding type is HTTP, you can change it to JMS or EJB.

As we only have one method, select the method BankAccount. WS-Security can be added in this step to create a more secure Web Service.

Optional you can deploy your WSDL to the Websphere UDDI for Web Services discovery. Click Finish to complete. Confirm that Web Service creation was successful.

Step 13. Test your new Web Service by opening Web Services Explorer and browsing for the Bank.wsdl

Step 14: Enter the relevant information into the two fields provided and click ‘GO’

Web Service Completed successfully.  This Web Services can now be deployed to Websphere Registry and Repository to be discovered by all other systems in your environment.

Packt Book Review: Application Development for IBM WebSphere Process Server 7 and Enterprise Service Bus 7

Book Review: Application Development for IBM Websphere Process Server 7 and Enterprise Service Bus 7.
Packt Publishing published a market leading book on Websphere Process Server (WPS) V7 and Enterprise Service Bus (WESB) V7 and how to create applications for these two software products. As WPS forms part of your BPM enablement and WESB forms part of your ESB solution in your SOA architecture. This book brings you all the neccessary steps to build an end-to-end BPM and ESB solution. This will help any company or small business enhance or enable their SOA architecture to increase or benefit. By adpopting an SOA approach in BPM it can make your applications:
1. flexible
2. reusable
3. adaptable
This books introduces basic concepts of:
1. Business Integration
2. SOA Fundamentals
3. SOA Programming Models
The first step in the SOA life cylce is Model which includes requirements modeling and analysis. This book assists you to move through all the stages of the SOA lifecycle to create an Order Management application from scratch using WPS and WESB. In my opinion this is a great book for new or existing SOA specialists that would like to improve their current SOA infrastructe with WPS and WESB.

Below is the link to get more information and also buy this book:


Increase business flexibility with the Service Integration Maturity Model

Do you lack flexibility in your organization between business and IT?Identify your organization in one or all of the seven stages of Maturity for each part of your organization.

  1. Silo (data integration)
  2. Integrated (application integration)
  3. Componentized (functional integration)
  4. Simple services (process integration)
  5. Composite services (supply-chain integration)
  6. Virtualized services ( virtual infrastructure)
  7. Dynamically reconfigurable services (eco-system integration)

Map your organization following the CMMI levels for each stage of SIMM.

  1. Incomplete
  2. Performed
  3. Managed
  4. Defined
  5. Quantitatively managed
  6. Optimizing

After SIMM is completed define the scope of your SOA adoption:

To achieve an optimal level of flexibility when architecting a service-oriented infrastructure, it’s wise to adhere to the seven steps of maturity that we’ve discussed. Doing this, combined with attention to the capabilities described in the Capability Maturity Model Integration, will enable you to develop a well-defined and usable architecture.