SOA / Web Services / Java

A Technology Blog

Archive for the ‘SOA Governance’ Category

Determining Complexity of Service in SOA

Posted by Vivek on May 13, 2012

Every unit of logic in a SOA is treated as a service. Before embarking on the SOA journey, it is important to go through a service identification process. Once services are identified, they are categorized as per the level of complexity. Determining the complexity is a key step in providing estimation. The following guidelines can be used to gauge the complexity of a service:

Simple Service:

· Exposed using a standard based interface and no adapters are required.
· There is minimal (simple) or no data validation required.
· There is minimal (simple) or no data transformation required.
· Does not require any security implementation. (Mostly public services)
· Simple logging framework. Does not require a separate error handling mechanism.
· Can be easily searched in UDDI. Taxonomies clearly defined. Simple end-point look.
· Does not require WS-* Standards like WS-RM, WS-A etc.
· Does not require any guaranteed delivery messaging mechanism to be in place
· Mostly utility services with simple read/ update operations.

Medium Service:

· Exposed using a standard based interface.
· There is simple/ medium data validation required.
· There is simple/ medium data transformation required.
· Simple logging framework. Requires a separate simple error handling mechanism.
· Require simple security implementation. Eg WS-security for authentication/ authorization, tool based encryption and decryption, SSL etc
· Can be easily searched in UDDI. Taxonomies clearly defined. Simple end-point look.
· Can include simple WS-* standards such as WS-Addressing, WS-reliable messaging.
· Requires some guaranteed delivery messaging mechanism to be in place
· Services returning/ adding medium to large amount of information and interacting with 1 application or system.

Complex Service:

· Exposed using a standard based interface.
· There is complex data validation required. (eg, data & timezone validation etc)
· There is complex data transformation required. (eg. One message standard to another)
· Complex logging framework. Implementation of Correlation sets. Requires a separate complex error handling mechanism with retry/ reprocessing logic and fault notification.
· Require medium to complex security implementation. Eg Digital Signature, encryption & decryption, SAML etc
· Multiple versions exist in UDDI. Standards such as WS-Policy, WS-trust need to be enforced.
· Can include WS-* standards such as WS-Coordination etc.
· Requires guaranteed delivery messaging mechanism to be in place
· Services adding/ updating and returning large and complex information and interacting with multiple systems.


Posted in integration, Java/J2EE, Miscellaneous, SOA, SOA Governance, Web Services | Tagged: , | 1 Comment »

WSRR Installation Issues

Posted by Vivek on March 6, 2009

WSRR or Websphere Service Registry and Repository is IBM’s answer to a robust SOA Governance solution framework. Every complex product brings some issues along with it and when its an IBM product, it is obvious.

If you are installing WSRR 6.1, make sure you have followed the below mentioned steps:

1. Installed Websphere Application Server (WAS) or later.  If not, first install Update Installer in WAS Installation Directory.

2. Install Websphere Application Server fix pack using Update Installer on top of existing Websphere Application Server installation.

3. Install IBM SDK SR6 using Update Installer from here

4. Install Oracle or DB2 database and create database schema.

5. Install Websphere Service Registry Repository

6. Deploy WSRR on WAS using “deploywizard” or “installall” batch/shell scripts (Located under WSRR_HOME/install directory).

To download Update Installer, interim fix and Fix Packs 13 for windows, Click Here

Note: Web Service feature pack is not required for WSRR. If you have already installed Web Services feature pack, please install interim fix and Fix Pack for Web Services feature pack before following step 3. (Not Recommended)

Chances are that deployment of WSRR ear on WAS may fail. In such cases, make sure that

1. you have correctly specified server and profile details of WAS on one of the deployement details screens.

2. If you are on database details screen, choose “Preload the database” option rather than “Reuse an existing database” option. If not, you may end up getting only configuration perpective of WSRR. Administrator and User perspective may not be visible. Though, you can go to Configuration –> Manage Configuration Profile –> Configuration Profiles from your WSRR Homepage, Select Load Configuration Profile, Browse to $REGISTRY_HOME/samples, select, select OK and Restart server.

3. If you have opted for Oracle database, make sure you have set Oracle_JDBC_Driver_Path. If not, go to WAS Administrative Console –> Environment –> Websphere variables. Set the value for Oracle_JDBC_Driver_Path and restart server.

Posted in SOA Governance | Tagged: , | Leave a Comment »

Best UDDI Registries

Posted by Vivek on January 27, 2009

UDDI service registry is of paramount importance when it comes to providing a SOA Governance solution. A service registry stores metadata that is related to the particular asset you have interest in, without actually containing those assets.  It is essentially an online directory of services that enables the service providers to advertise their offerings and allowing service consumers to find services that match their criteria. It provides a foundation for the governance and lifecycle management of Business Services. It provides with what is needed to obtain enterprise-wide insight, control and economic leverage of organization’s business and service artifacts. The registry also supports metadata like classifications, categorizations, relationships and properties. These metadata are then used to define taxonomies, describe how service artifacts are related to each other and associate generic as well as object specific characteristics for service artifacts.

Here are some UDDI registries that are widely used in organizations:

1. Systinet Registry (now HP SOA Systinet Registry)  

2. Oracle Service Registry : It is a modified version of Systinet Registry. Remodeled according to Oracle needs.

3. Aqualogic Service Registry: Again a modified version of Systinet Registry.

4. IBM Web Services Registry Repository

5. TIBCO ActiveMatrix: Again a modified version of Systinet Registry.

Posted in SOA Governance | Tagged: , , , , | Leave a Comment »

Managing registry without a repository?

Posted by Vivek on October 27, 2008

When it comes to SOA Governance practice, the first thing advocated is having a registry-repository. In almost all the cases, the registry and repository are two seperate entities. They are integrated using some utility to serve the purpose of a good SOA Governance solution.  When Oracle acquired BEA, it knew that with this acquisition it will get some powerful tools of SOA that are classified under Aqualogic series.

AquaLogic Enterprise Repository or ALER is now going to be rebranded as Oracle Enterprise Repository. What about Aqualogic Service registry (ALSR) ? Well, ALSR is nothing but an OEM version of Systinet registry (now acquired by HP). So when BEA was rebranding Sytinet registry, Oracle was also doing the same. Oracle rebranded systinet registry as Oracle Service Registry (OSR). Most of the people will now think that Oracle has redundant registry but it is not completely true. Aqualogic was not supposed to support oc4j servers whereas all products belonging to Oracle breed should support oc4j server. Though Oracle is now looking to come out of this thought process. Replacing embedded oc4j server with weblogic server in jdeveloper is one such example. But how did Oracle manage to have a registry without a repository? The answer is Oracle never had a full SOA governance solution in place because the governance process has to be automated. One cannot claim that he can manage the lifecyle of an asset without synchronizing the changes, that a service is undergoing, across the organization.

To avoid the changes that can occur while moving the assets to a new location, the importance of having a repository in place cannot be undermined. Moving one step further, the repository can have a workspace to facilitate accelerated development of artifacts.

Posted in SOA Governance | Tagged: , , , | Leave a Comment »

SOA Governance

Posted by Vivek on August 23, 2008

Any organization willing to implement SOA should already have a plan for its governance. Most people think that SOA Governance is optional and it’s not true. Without SOA Governance it is impossible to reap the true benefits of a full-fledged SOA. Some benefits that are directly related to success of any organization.

With the widespread adoption of SOA, the challenges associated with SOA projects are emerging. SOA governance isnt optional its imperative. Without it, return on investment will be low and every SOA project out of pilot phase will be at risk.
                                                        Paolo Malinverno
                                                           Gartner, Inc.1

Failure to provide effective SOA governance exposes your organization to serious risks:
• Insufficient knowledge of available services
• General failure to reuse services
• Unnecessary, uncontrolled service duplication
• Resources wasted on services that can’t be reused
• Service sprawl across siloed SOAs
• Ineffective communication of best practices.


A good blog on SOA Governance:

Posted in SOA Governance | Tagged: , | Leave a Comment »