Using the adapter with WMQIB or WBIMB

When using either WebSphere MQ Integrator Broker (WMQIB) or WebSphere Business Integration Message Broker (WBIMB) as your integration broker, you must make some modifications to this adapter. The modifications enable the broker to successfully process the default wbieuAsset business object, which is recursively defined by default. The changes you make must be made to the wbieuAsset business object and XSL translations that use the wbieuAsset business object.

Changing business object definitions

Perform the following steps to make the changes to the wbieuAsset business object:

  1. Open the Business Object Designer. For information on launching and using the Business Object Designer, see IBM WebSphere Business Integration Adapters Business Object Development Guide.
  2. Open the wbieuAsset business object.
  3. Save a copy of the wbieuAsset business object under a different name, for example, subAsset.
  4. Change the type of the subAsset attribute in the original wbieuAsset business object. The new type must be the type created in step 3.
  5. Refresh all business objects that depend on the wbieuAsset business object (by default, wbieuWorkOrder and wbieuWorkTask business objects).
  6. Redeploy all three business objects.

After completing these changes to the business object, you must make some XSL translation changes.

Changing XSL translations

This section explains how to make changes to the XSL translations that use the wbieuAsset business object.

  1. Open the following convert.xsl XSL translations which reside in the translations directory:
    Note:
    Before you begin, save backup copies to another directory or with a different file extension.

    xslt/Indus/cw/Equipment

    xslt/Indus/cw/Schedule

    xslt/Indus/cw/UniqueTrackedCmmdty

    xslt/Indus/cw/WorkOrder

  2. For each translation, search for the text "subAsset". This text should appear in the Attribute elements and the text "subAsset" should appear as the name attribute of the XML element.
  3. For each instance of the subAsset attribute, change the XML attribute named class from wbieuAsset to reflect the new business object created in step 3 in Changing business object definitions.
  4. Save all new translations.

The following examples show the business object definition before the changes are made and what the business object definition looks like after the changes are made. In this example, assume the subAsset attribute has been changed from wbieuAsset to type newAsset in the Business Object Designer:

Before:

<xsl:element name="Attribute">
     <xsl:attribute name="class">wbieuAsset</xsl:attribute> 
     <xsl:attribute name="name">subAsset</xsl:attribute> 
     <xsl:attribute name="type">SINGLECARDSTRING</xsl:attribute> 
     <xsl:element name="BusinessObject">
     <xsl:attribute name="class">wbieuAsset</xsl:attribute> 
     <xsl:attribute name="type">SINGLECARDSTRING</xsl:attribute> 
     <xsl:element name="Attribute">
   

Becomes the following:

<xsl:element name="Attribute">
     <xsl:attribute name="class">newAsset</xsl:attribute> 
     <xsl:attribute name="name">subAsset</xsl:attribute> 
     <xsl:attribute name="type">SINGLECARDSTRING</xsl:attribute> 
     <xsl:element name="BusinessObject">
     <xsl:attribute name="class">newAsset</xsl:attribute> 
     <xsl:attribute name="type">SINGLECARDSTRING</xsl:attribute> 
     <xsl:element name="Attribute">
    
   

Copyright IBM Corp. 1997, 2003