Creating business model templates with WebSphere Service Registry and Repository V6.1

Document options Document options requiring JavaScript are not displayed Sample code Rate this page Help us improve this content

Level: Intermediate

Ian Shore (ishore@uk.ibm.com), IT Specialist, IBM　
Henry Tonnison, MEng (henry.tonnison@uk.ibm.com), Advisory Software Engineer, IBM

15 Feb 2008
Updated 22 May 2008

You can create new enterprise-specific business models with IBM® WebSphere® Service Registry and Repository to represent your business concepts and relate them to other concepts. You can manage these models using WebSphere Service Registry and Repository's governance capabilities. The default business models demonstrate what you can represent in WebSphere Service Registry and Repository, but how do you create your own models? This article describes how to create, load, update, and use new business models within WebSphere Service Registry and Repository V6.1.

Introduction

Implementing a service oriented architecture requires control and governance of the services that are created and used throughout the organization. These services could have a Web Services Definition Language (WSDL) representation, or they could be generic business concepts which do not have any underlying content or current existing implementation. Using the IBM WebSphere Service Registry and Repository (hereafter called Service Registry) V6.0 you can store, control, govern, and use these generic business concepts as easily as those which have either a WSDL or some other type of document. When you create a generic business concept, it has the default metadata (properties, relationships, and classifications) associated with it; these might define name, namespace, version, description, and so on. However, you can also create a business model template with Service Registry, instantiate it as a generic business concept, and associate specific metadata that is defined in the template.

For example, suppose your organization wants to represent business applications within the Service Registry and to control them from inception to retirement. Using Service Registry business modeling templating, you can create a Business Application template which, upon instantiation, creates properties such as the following:

• costPerInvocation, a numeric double value (for example, 10.43)
• executiveSponsor, a String value or one of five String values (that is, an enumeration)

The template might also define relationships such as:

• designDocumentation to relate at least one WSRR GenericDocument (a loaded design document)
• interfaceDefinition to relate to a WSDL Document
• miscellaneous to relate to any number of other informational documents

Service Registry V6.0 introduced the idea of concept templating where you generate a Service Registry Concept from an XSD template. When instantiated, that template can automatically attach, as metadata, predefined property or relationship names. Service Registry V6 provided a beginning but had limitations which are addressed by Service Registry V6.1. Table 1 describes how V6.1 overcomes these V6 limitations.

Overview

Business model templates within Service Registry 6.1 are defined using the Web Ontology Language (OWL) format. Using OWL to describe the new templates provides a level of flexibility to Service Registry V6.1 business models that was not possiblie with the previous XSD previous XSD document format. However, with flexibility comes some complexity to manually create and understand the OWL files which represent business models. This article shows how to use two alternative mechanisms to generate Service Registry V6.1 business model template OWL files. You can then load them into Service Registry V6.1. These two mechanisms are quick-start routes to help you quickly get up and running with Service Registry V6.1 business modeling. They are:

1. Using a graphical UI business model template OWL creator to load and modify existing business models or generate entirely new ones.
2. Using a text-to-business model template OWL converter to generate a self-contained business model which does not sub-class another business model template.

   After generating a business model template using this text-to-business model template converter, you can change it manually to inherit the attributes of another business model template. You alter the <rdfs:range> element in its Class element to point to the namespace of a super-class template.

Both approaches generate a business model template that can be loaded into Service Registry V6.1, from which you can create instantiations using the WebUI or the API. You see an example of loading and instantiating a business model template using the WebUI later in the Loading business model systems and creating instances from business model templates and Example Service Registry V6.1 business model template sections.

The GUI approach enables you to create, extend, load, and save business model templates. Therefore, using the GUI tool is a more powerful approach to generating business model templates. However, the text converter approach enables you to quickly generate a new business model template without having to navigate a GUI; it is helpful for testing and proof-of-concept purposes.

Using the graphical UI business model template OWL creator

The Service Registry Business Model Creator application (in the download file, WSRRBusinessModelCreator.zip,) requires Java™ 5. (A bug in Sun Java 6 JVM currently prevents you from running this application.)

To determine the version of Java that you are running on your system:

1. Open a Command Prompt window.
2. Enter this command:

   java -version

   
   

   If you do not see IBM in the message, you are running with a Sun JVM. The application must be run with a WebSphere Application Server or IBM JVM of Version 5 or higher.

   java version "1.6.0_03" Java(TM) SE Runtime Environment (build 1.6.0_03-b05) Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode, sharing)

   
   

You can use this tool to easily create business models and to see how your OWL document is laid out.

• Business model system represents the OWL file that contains the details about your model.

  You load this file is loaded into Service Registry into the Configuration perspective. The namespace defined in this document is also the URI of the model system. You can specify a prefix to be prepended to any Restriction names in this document. This document contains models, restrictions, and cardinalities which are discussed below.

• Business model template define the structure of each modelled entity in the business model system.

  You create instances of custom entities from business model templates. The namespace of the business model system combined with the name of the business model template define the business model template's URI. For example, if the business model system namespace is http://ibm.com/namespace and the business model template name is MyFirstBusinessModel, then the URI of the busines model template is http://ibm.com/namespace#MyFirstBusinessModel. The business model template references a series a restrictions. These restrictions define what the business model template will enforce.

• Restrictions capture static integrity constraints for the business model system.

  For example, you can have a property called MyFirstProp that must exist and the value must be an integer. You can also specify that a Concept must have a relationship to another type of object in Service Registry. The name of the property or relationship is the name of the restriction. If you have a prefix defined then the name will be prepended with the prefix; prefix_name.

  • Property restrictions define the name of a property, it's type, and a default value.
  • Relationship restrictions defines the name of the relationship and the target types of the relationship. For example, a relationship must point to a WSDL or XML document.
  • Enumeration restrictions are similar to property restrictions but let you specify that the property values must be one of a desired set. For example, if you were trying to model a contract, you could have a property called hasCustomerAgreed with the possible values of yes or no. Service Registry business model validation enforces that it is one or the other.

• Cardinalities let the user specify additional properties.

  When a business model template references a Restriction it has a cardinality defined for that reference.

  • Property and enumeration restrictions enforce that the value must be set (that is, an empty value is not acceptable), by using a cardinality.
  • Relationship restrictions specifies the type of the targets. However, the cardinality specifies a range for the number of possible targets. For example, we can create a restriction that must have XML documents at the end of a relationship and must have more than 0 and less than 10 targets, using cardinalities.

Using the GUI to create business model systems from scratch

This Service Registry Business Model Creator GUI application is contained within the JAR file BusinessModelCreator.jar within the ZIP file in the Download section. To launch the JAR file, double-click it. Alternatively, if the BusinessModelCreator.jar file is on the Java classpath, you can launch the GUI from the command line using this command:

java -jar BusinessModelCreator.jar

Creating a new business model system

To create a new business model system:

1. Right-click business model systems to bring up a menu.
2. Select Create new model system. You see a window you can use to populate the details about your new business model system.
   
   Figure 1. Creating a new business model system
   
   
   
3. To populate the details of a new business model system, fill in these fields to describe your business model system.
   
   

   Field	Description
   Name	The name of the document for your purposes.
   Namespace	The namespace of your document which is also the URI of the document. A brief description about what this business model system will do. Note: No other documents in Service Registry can share this namespace.
   Prefix	If set, then this will be prepended along with an underscore to the all the restriction names. For example if your restriction is called PropertyRestriction and there is no prefix then a property called PropertyRestriction must exist on the model. However if prefix is set to prefix then the property must be named prefix_PropertyRestriction. Note: This value must be an NC name. See Resources for a link to the definition of a NC name.

   
   
   
   
   Figure 2. Defining details of a new business model system
   
   
   

Business model templates must exist within a business model system. To create a new business model template within a business model system:

1. Right-click on the business model system.
2. Click on Create new model and you see a window to populate a new business model template.
   
   Figure 3. Creating a new business model template within a business model system
   
   
   
3. To populate the details of a new Model, you fill in the details about your business model template using this dialog.
   
   

   Field	Description
   Name	The name of your model. This, along with the containing document namespace, will make up the URI of the model. For this example, the URI is http://ibm.com/namespace#MyModelName. This value has to be a NC name.
   UI Name	For reference purposes, this is displayed in the WebUI.
   Extends	This business model template can extend other models to form a model hierachy.

   
   
   
   
   Figure 4. Populating details of a new Model
   
   
   

Restrictions must exist within a business model system. To create a new property restriction:

1. Right-click on the business model system, and click New property restriction. You see the window shown in Figure 5.
   
   Figure 5. Creating a new property restriction
   
   
   
2. To define the details of a Property Restriction, fill in this dialog. You can enforce certain aspects of properties restrictions with these settings.
   
   

   Field	Description
   Name	The name of a property that a new Concept must have. This must be a NC name.
   Type	The type that the property value must be.
   Default	Use this setting when creating models in the WebUI only. When the business model template is instantiated, this value will be inserted automatically as an initial value.

   
   
   
   
   Figure 6. Populating details of a Property Restriction
   
   
   

To create a new relationship restriction:

1. Right-click on the business model system and click New relationship restriction.
   
   Figure 7. Creating a new Relationship Restriction
   
   
   
2. To populate the details of a Relationship Restriction, fill in the details about your relationship restriction using this dialog. You can enforce certain aspect of relationship restrictions with these settings.
   
   

   Field	Description
   Name	The name of the relationship that a new Concept must have. This must be a NC name.
   Targets	The targets must be other models. If you choose another business model template this will enforce that the target of the relationship is a Concept with that model set on it. See below for details on how to create a relationship restriction to a Service Registry object. You can select as many target types as needed.

   
   
   
   
   Figure 8. Populating details of a Relationship Restriction
   
   
   

To create a new enumeration restriction:

1. Right-click on the business model system and click New enumeration restriction which will present a dialog.
   
   Figure 9. Creating a new enumeration restriction
   
   
   
2. Enumeration restrictions are similar to property restrictions except that there is an added enforcement; the values of the property must be in a certain range. To populate the details of a enumeration restriction, fill in these fields:
   
   

   Field	Description
   Name	The name of the property that a new Concept must have. This must be a NC name.
   Type	The type that the property value must be.
   Value	Insert values for the enumeration. Insert the value in the box and click Add. To remove a value, select it, and then click Remove. To make a selected value the default, click Default.
   Default Value	This is used only when creating models in the WebUI; when the business model template is instantiated, this value will automatically be inserted as an initial value.

   
   
   
   
   Figure 10. Populating details of an enumeration restriction
   
   
   

Figure 11 shows a graphical representation of the example business model template we have defined so far in the GUI. There is one business model system that contains a business model template and three restrictions. However, the class is not yet set up to enforce anything as it does not reference any of the restricitons.

Adding restrictions to a business model template

The defined business model template must reference the restrictions that have been created. To add specific restrictions to a business model template:

1. Right-click on a business model template and click Add/Edit restrictions.
   
   Figure 12. Adding restrictions to a business model template
   
   
   
2. Select the restrictions you want to add to the model from the list that displays.
   
   Figure 13. Select restrictions to be added
   
   
   

   Either select one restriction by clicking it, or multiple items by holding down CTRL and clicking the restrictions.

3. Next, you select the cardinality for the properties. For each property restriction or enumeration restriction you add, you are prompted to decide whether or not to require a value for the property.
   
   Figure 14. Select whether value must be set on the property
   
   
   
4. Finally, select the cardinality for the relationships. For each relationship restriction you add, you are prompted to set the bounds of the relationship restriction. If you need to create a range (that is, restrict between two values; for example, 0 <= x <= 10), then repeat the process of adding a restriction to a model.

   Currently, because instantiating a business model template through the Service Registry 6.1 WebUI results in no targets being set on a generated relationship, the WebUI only supports instantiating a business model template when the minimum cardinality set for any relationship template is 0. Therefore, a higher cardinality minimum setting would fail validation of an instantiated business model against the business model template.

   
   
   Figure 15. Select the bounds for the number of targets of the relationship
   
   
   

Completed business model system

The business model system is now complete. You can see all the restrictions and how they are referenced by the model in the GUI. You can still edit the model by right-clicking on any item and selecting Edit. You can also remove items by right-clicking and selecting Remove.

You can now save the business model system to create files for each business model system that you have defined. The file names will use the namespace of the business model system with all invalid file name characters removed. For this example, the filename will be httpibm.comnamespace.owl.

Next, you choose the directory where you want to save the business model system. Because the filenames are automatically generated, you only need to select the path and directory.

Using the GUI to creating Relationships to Service Registry Objects

The GUI lets you add relationship restrictions that will validate the target of the relationship. The relationship target must be a model. In order to create relationship targets that are Service Registry Objects (WSDLDocument, XMLDocument, and so on), the models that are included with Service Registry must be loaded into the GUI.

1. To load a business model, select File => Load.
   
   Figure 19. Load a business model
   
   
   
2. The registry objects file, registryobjects.owl, defines the mapping of Service Registry objects to models. This file is loaded by default into your Service Registry system, so you do not need to re-load it.
   
   Figure 20. Load the registryobjects.owl
   
   
   

   The registry objects are now loaded. The GUI now shows many more models. These models are the Service Registry objects.

   
   
   Figure 21. The registryobjects.owl after loading
   
   
   
3. Next, select a Service Registry object. If you followed the steps in the Using the GUI to create business model systems from scratch section to create a relationship restriction, you see that there are many more models to choose from. The new models represent the Service Registry object heirarchy. If you edit one of these models you see which business model template class it extends.
   
   Figure 22. Select a Service Registry object
   
   
   

Loading business model systems and creating instances from business model templates

After creating a business model system, you can load it into Service Registry. You load and administer business model systems using Service Registry's Configuration perspective. After loading the business model system, you will be able to see all the available business model templates.

To creating a new instance and then to create a Concept with this business model template applied:

1. First, in the Configuration perspective, load the business model system. After it is loaded you will be able to administer it from the Service Registry WebUI.
   
   Figure 23. Load the business model system
   
   
   
2. To create a new instance of the business model template, in the Administrator/User perspective, expand the Business Metadata tab and then select business model templates. Here you can view all the available business model templates.
3. Select one of the business model templates and click Create New Instance to create a new Concept using that business model template.
   
   Figure 24. Create a new instance of the business model template
   
   
   
4. Now you can populate the details of the new instance.

   After the instance of the business model template has been created, you can specify the details of the new Concept. You see the properties that the business model template enforces and the default values are already populated. You will not see the relationship restrictions at this point.

   
   
   Figure 25. Populate the details of the new instance
   
   
   
5. To view the new Concept with the business model template applied, click the Concepts menu item.
   
   Figure 26. View the new created concept
   
   
   
6. To view the relationship, browse the Custom Relationships of the Concept. You see that the WebUI has created a relationship with zero targets. Here you can add in your targets.
   
   Figure 27. View the relationship
   
   
   

Back to top

Using the text-to-business model template OWL converter

Creating OWLs and SACLs A previous developerWorks article, Creating customized classification systems with WebSphere Service Registry and Repository V6.0.0.1 and higher, describes how you can use a similar text parsing technique to generate Service Registry classification systems and lifecycles. You can use this capability to quickly understand the Service Registry concepts using your own terminology.

To create a business model template you need to decide:

1. How it will be identified within Service Registry.
2. What comments should appear within the generated business model template OWL.
3. What property names, types, and constraints should be defined.
4. What relationship names, target types, and cardinalities should be defined.
5. Whether to define a classification hierarchy for your Service Registry.

If you have not already done so, download the sample ZIP file and extract the BusinessModelCreator.jar from it. The classes to perform the parsing of your textual input file are in this file.

1. Define its identity

Key aspects of any new business model template to define are its:

• Name. A user-friendly name to display in the Web-UI.
• Namespace. The ID used for referring to this business model template by the primary type property of its instantiated business models and by other business model template sub-classes.
• Prefix. The property and relationship name prefix. Predefined property and relationship names in instantiated business model templates are prefixed with this prefix identifier. So, for example, if the prefix is newBM and the predefined property name is newString then the generated property name will be newBM_newString.

You specify the name, namespace, and prefix in the input text file by including the following tags,respectively:

• BUSINESS_MODEL:{business model template name}

  If no BUSINESS_MODEL name is specified, then the default name, SampleBusinessModel, is used.

• BUSINESS_MODEL_NS:{Namespace URI to identify this BM}

  If no BUSINESS_MODEL_NS is specified, then a namespace URI representing the name of the business model template output file specified is used. For example, file:///c:/temp/NewBusModel.owl

• BUSINESS_MODEL_PREFIX:{prefix to use}

  If no BUSINESS_MODEL_PREFIX is specified, then five random alphabetic characters will be used; for example, fwxpa.

2. Add comments

To enable comments to be inserted into the generated business model template, insert lines starting with a # (hash/pound) character. These lines will be placed together as one comment block (using XML's comment mechanism; <!-- ... -->).

3. Define template properties

To define a new property for the business model template use this syntax:

PROP:name:type:values:default:haveValue

Where:

• name is the name that will follow the specified prefix which will be added in the instantiated business model template

• type is the type of the property value. The expected values for this field are:
  • string
  • anyURI
  • bool or boolean
  • int or integer
  • short
  • long
  • float
  • double

  If none of these values are used, then the string type is assumed.

• values is an enumerated list of values for the new property. Separate the values using the | character; for example, Red|Amber|Green . Values can only be string types for Service Registry V6.1.
  Tip: To indicate that any value can be used for this property, specify the space character, as shown in the second line in Listing 1.

• default is the default value for this property.
  Tip: If a default value is not required, then specify the space character, as shown in the third line in Listing 1.

• haveValue indicates whether or not a value must be supplied for this property. Valid values are true or false. If there are enumeration values specified then haveValue will be ignored but set to true; otherwise, the default value is false.

PROP:status:string:Red|Amber|Green:Red:true
PROP:department:string: :HR:false
PROP:priority:int: : :true
      

In this example, if the prefix specified is xmpl, a business model template is created, which when instantiated, would include three properties:

1. xmpl_status, with a value of Red, Amber, or Green.
2. xmpl_department, a string which defaults to HR but does not have to be set.
3. xmpl_priority, set to an integer value.

4. Define template relationships

To define a new relationship for the business model template use the REL element with this syntax:

REL:name:relTarget:cardinalities

Where:

• name is the name that will follow the specified prefix added in the instantiated business model template.
• relTarget is the type of Service Registry entity that can exist as a target of the relationship. To allow any object to be set as the target of this relationship, specify BaseObject. If the target specified is not recognized, then BaseObject is assumed. Listing 3 represents the hierarchy of values that you can use. BaseObject is the top-most type in this hierarchy, so you would use it to allow any entity to be the target of the relationship.
• cardinalities represent the number of targets that can exist on this relationship, represented as a non-negative integer range with the minus character separating the numbers; for example, 0-3.

REL:designDoc:Document:0-1
REL:interfaces:WSDLDocument:0-3

In this example, if the prefix specified is xmpl, a business model template will be created which, upon instantiation, would create two relationships:

1. xmpl_designDoc; which can have 0 or 1 targets that must be Document entities, such as: ExportDocument, GenericDocument, ImportDocument, ModuleDocument, PolicyDocument, WSDLDocument, XMLDocument, or XSDDocument.
2. xmpl_interfaces; which can have at most three WSDLDocument entities as targets of the relationship.

BaseObject
    LogicalObject
        AttributeDeclaration
        ElementDeclaration
        Export
        ExportBinding
            JMSExportBinding
            SCAExportBinding
            WebServiceExportBinding
        ExtensionLogicalObject
        Import
        ImportBinding
            JMSImportBinding
            SCAImportBinding
            SLSBImportBinding
            WebServiceImportBinding
        Interface
            SCAWSDLPortType
        LocalAttribute
        Module
        PolicyAttachment
        PolicyExpression
        SOAPAddress
        SOAPBinding
        WSDLBinding
        WSDLFault
        WSDLInput
        WSDLMessage
        WSDLOperation
        WSDLOutput
        WSDLPart
        WSDLPort
        WSDLPortType
        WSDLService
        XSDType
            ComplexTypeDefinition
            SimpleTypeDefinition
    OriginalObject
        Document
            ExportDocument
            GenericDocument
            ImportDocument
            ModuleDocument
            PolicyDocument
            WSDLDocument
            XMLDocument
            XSDDocument
        GenericObject
        QueryObject
            GraphQuery
            PropertyQuery
        SCAModule
      

5. Create classification hierarchies

Similar to the technique described in Creating customized classification systems with WebSphere Service Registry and Repository V6.0.0.1 and higher, you can create a classification hierarchy while creating the business model template.

You use the name and namespace tags:

• ONTOLOGY:{hierarchy name}.

  If the ONTOLOGY hierarchy name is not specified then the top-level hierarchy name will be used. For example, if in Figure 2 the ONTOLOGY tag was not present then the label would be Corporate Applications.

• ONTOLOGY_NS:{hierarchy namespace URI}.

  If the ONTOLOGY_NS is not specified then a namespace URI representing the name of the Classification OWL output file specified will be used; for example, file:///c:/temp/NewClassification.owl.

ONTOLOGY:Corp Application Hierarchy
ONTOLOGY_NS:http://www.bt.com/hierarchy/applications
Corporate Applications
  Platform
    Windows
    zOS
    AIX
  Application
    Web-Service
    EJB
  Language
    Java
    C
    C++
    C#
      

Invoking the business model template quick-start utility

If the BusinessModelCreator.jar file is on the Java classpath, then you can invoke the utility using the following command with these parameters:

java com.ibm.serviceregistry.quickstart.CreateBusModel
    -in <input filename>
    [-pre <prefix>]
    [-ns <namespace>]
    <-bm <filename>>
    [-c <filename>]
      

Where:

• -in specifies the text input file to generate the Service Registry V6.1 business model template
• -pre is optional and is used to override any business model template prefix specified within the input file
• -ns is optional and is used to override any business model template namespace URI specified within the input file
• -bm is the name of the output file for the new Service Registry V6.1 business model template
• -c is the name of the output file for the classification hierarchy that can be defined in the same input file.

Example Service Registry V6.1 business model template

Listing 7 shows the command used to generate a business model template bm4QS.owl OWL file from the input file shown in Listing 6.

BUSINESS_MODEL:Quickstart test
BUSINESS_MODEL_NS:http://www.ibm.com/quickstart/bm
BUSINESS_MODEL_PREFIX:myBM

# PROP:name:type:values:default:haveValue
PROP:status:string:Red|Amber|Green:Red:true
PROP:department:string: :HR:false
PROP:priority:int: : :true

# REL:name:relTarget:cardinalities
REL:designDoc:Document:0-1
REL:interface:WSDLDocument:0-3
      

java com.ibm.serviceregistry.quickstart.CreateBusModel
    -in resources\createBM2.txt
    -bm bm4QS.owl

After loading the business model template generated by Listing 7, the Configuration perspective displays a new Quickstart test entry in the business model systems view, as shown in Listing 8.

Figure29 shows the Service Registry detail view when creating a new instance of the Quickstart test business model template, which includes the three properties as defined in the example input file (see Listing 6):

• The myBM_status value must be Red, Amber or Green.
• The myBM_priority must be set to an integer.
• The myBM_department can have the HR value removed.

If you click either Apply or OK and any of the above are not correctly set, then Service Registry V6.1 will display a message indicating what was invalid.

The targets of the two relationships defined in the same example input file are set up after the instance has been created (in the WebUI). Therefore, defining business model templates for instantiation using the WebUI requires the minimum cardinality of the relationships to be 0. However, if you create an instance of a business model template using the API then you can have higher minimum cardinalities.

Back to top

Conclusion

This article provided an overview of Service Registry 6.1 business modeling functionality and described two methods for generating a business model template It showed how to load these templates into Service Registry 6.1 and how a new business model can be instantiated from a business model template. Both approaches described in this article have advantages and disadvantages. If you prefer a GUI interaction which allows business models to be loaded and extended to create new business models, then use the Business Model Creator application. If you need to quickly generate individual business model templates for testing or proof-of-concepts, then use the text-to-business model template converter. Using either of these tools will assist you in creating a Service Registry 6.1 business model template input file and is preferable to error-prone manual editing of an OWL file using a text editor.

Back to top

Download

	Information about download methods

Resources

• "Web Ontology Language (OWL)" is designed for use by applications that need to process the content of information instead of just presenting information to humans.
  
  
• See the WebSphere Service Registry and Repository Version 6.1 Information Center for more information about how to manage and govern your services and business processes.
  
  
• XML Schema Part 2: Datatypes Second Edition defines NC name as well as other XML schema attributes, types, and elements.
  
  
• In the Creating customized classification systems with Service Registry V6.0.0.1 and higher describes how you can use a text parsing technique to generate Service Registry classification systems and lifecycles.
  
  
• Get a brief overview of the new Business modeling feature.
  
  
• The product information page describes features, benefits, system requirements and provides links to more information about WebSphere Service Registry and Repository.
  
  
• WebSphere business integration zone provides a wide variety of technical resources to help you levearge WebSphere Service Registry and Repository and other products that integrate data, applications, processes, and people across and beyond the enterprise.
  
  
• WebSphere business process management zone provides technical resources to help you use learn to use tool that model, assemble, deploy, and manage business processes.

• The WebSphere Service Registry and Repository Wiki offers a variety of related technical resources and lets you comment on them.
  
  
• Check out developerWorks blogs and get involved in the developerWorks community.
  
  

About the authors

		Ian Shore is a Senior IT Specialist in the Application and Integration Middleware Software division of the IBM Software Group. He is a lead developer in the WebSphere Service Registry and Repository development team at IBM Hursley Laboratories, UK. His previous roles have included supporting customers as a Lab Services consultant for WebSphere Commerce and working with numerous new and traditional technologies.

		Henry Tonnison is a Software Engineer in the IBM Software Group. Currently in Level 3 support for Websphere Service Registry and Repository, with previous roles within Test.

Rate this page

Please take a moment to complete this form to help us better serve you. Did the information help you to achieve your goal? Yes No Don't know   Please provide us with comments to help improve this page:   How useful is the information? 1 2 3 4 5 Not useful Extremely useful

Share this.... Digg this story del.icio.us Slashdot it!

Back to top