Skip to content

Free Tutorial Videos – IIB, WMB, Monitoring

Please check out our free video tutorials on IBM Integration Bus (IIB), WebSphere Message Broker (WMB), TransformaTech MQ Monitor, and Monitoring With MonitorIT:

 

IBM Integration Bus and WebSphere Message Broker Tutorial Videoshttp://www.transformatech.com/videos/integration/

TransformaTech Monitor for MQ and IIBhttp://www.transformatech.com/videos/transformatech-product-videos/

Monitoring WMB with MonitorIT – http://www.transformatech.com/videos/virtualization-and-monitoring/

 

 

Advertisements
Link

WebSphere MQ (WMQ) vs ActiveMQ

Here is a good White Paper doing a comparison of WebSphere MQ (WMQ) and  Apache ActiveMQ.   I also included direct links to a couple YouTube videos that are referenced in document.

White Paperhttp://theedison.com/pdf/Edison_IBM_WebSphere_MQ_vs_ActiveMQ_White_Paper.pdf

ActiveMQ Failover

WMQ Failover 

This White Paper  is a good start of comparing these two products.   I am looking forward to additional releases of this comparison and analysis that goes into more areas of core messaging platform requirements.

TransformaTech

 

IBM Integration Bus V9 – Using New Features (MQService and DatabaseService)

 

Today we are going to be showcasing some of the new features inside IBM Integration Bus version 9. We are going to be using the XML To Cobol flow that we created in one of our other videos. Today, we will focus on some of the new features in IIB9 to help speed up the development process. We will be using an XML to COBOL mapping flow that we created in a previous video to implement these new features.

TransformaTech Monitor: Adding Broker Resources to Monitoring

We are happy to be able to announce a new release of our TransformaTech Monitor. This new version includes some updates to our graphical interface as well as the addition of new features. Be sure to check out our videos at the link for more information. Our Monitor allows you to seamlessly monitor not only your IBM MQ Environment but the Broker as well. Our solution is a multifaceted approach to monitoring by providing alerts and warning on your most critical queues, channels, execution groups and message flows. We can now provide up to the second alerts to events taking place in your environment. Check out our videos on our new Monitor and see for yourself how TransformaTech will continue to transform the way you do business.

Please take a look at videos of our product

TransformaTech

Introduction to TransformaTech Monitor

We at TransformaTech are very happy to be able to showcase our new TransformaTech Monitor. Our Monitor allows you to seamlessly monitor not only your IBM MQ Environment but the Broker as well. Our solution is a multifaceted approach to monitoring by providing alerts and warning on your most critical queues, channels, execution groups and message flows. We can now provide up to the second alerts to events taking place in your environment. Check out our videos on our new Monitor and see for yourself how TransformaTech will continue to transform the way you do business.

Please take a look at videos of our product

TransformaTech

Using WTX Map Node in WebSphere Message Broker

As a follow-up to our blog article (WebSphere Transformation Extender – Simple HIPAA 835X12 5010 to XML Mapping Example) on setting up a simple map in WebSphere Transformation Extender (WTX), we are now going to extend this to leverage WTX for Integration Servers to deploy a message flow to WebSphere Message Broker v8 (WMB).

Products

  • Webshpre Message Broker v8
  • WebSphere Message Broker Toolkit v8.0.0.2
  • WebShere MQ Explorer v7
  • Rfhutil

Pre-reqs

Our scenario depends on the following MQ queues and WebSphere Transformation Extender Map node. Please create these queues In MQ explorer (or using runmqsc from command line) and follow the steps to create your WebSphere Message Broker flow using the WTX Map node.

  • TT.WTX.EXAMPLE.HIPAA8355010.IN – Input queue
  • TT.WTX.EXAMPLE.HIPAA8355010.XML.OUT– Output queue
  • TT_WTX_Example_HIPAA8355010_TO_XML_MAPPING – WTX Map node

Artifacts

Message Flow: TT_WTX_SAMPLE_HIPAA8355010_TO_XML_MSG_FLOW

Input Test Data: 835_5010a1_Test_File.txt

8

Steps of using WTX Map node within a message flow in WMB Toolkit (mapping HIPAA 835 TO XML)

1. Create a WebSphere Message Broker Project

Click File –> New –> Message Broker Project –> Type in (TT_WTX_EXAMPLE_HIPAA835X12_TO_XML_PROJECT)

2. Create a message flow

  • Right click your Message Broker Project –> New –> Message Flow –> Type in (TT_WTX_SAMPLE_HIPAA8355010_TO_XML_MSG_FLOW)

1

  • In the Message Flow editor, add and name the MQ nodes listed in the following image

2

a.      Create WTX Map node

  • Go to your Palette drawers and scroll down until you see WebSphere TX, then drag a WTX Map node from the palette onto the Message Flow Editor.
  • The node initially has no output terminals, and one failure terminal.

4

b.      Configure WTX Map node properties     

  • Navigate to the Properties view, shown in image above.
  • On the Basic tab of the WTX Map node, select the source map and browse to your executable map file that you have already created. (See WTX blog)

5

  • On the Input tab of the WTX Map node, select the map card that receives the input.

6

  • On the Output tab, click add then type in what is shown in the below image.
  • On the Outputs tab, configure properties to describe the format of the output message propagated by the output card:
    • Click Add to add a set of properties. A dialog box will appear.
    • Enter values for Card Number, Message Domain, Coded Char Set Id, Encoding, and then click OK. Message Domain must be one of the supported message domains.

7

c.      Connect the nodes together

9

d.      (Recommended) Perform a clean and rebuild of your projects

10

11

e.     Your flow is now ready to be deployed, and tested.

Following image is what you will suppose to get in “TT.WTX.EXAMPLE.HIPAA8355010.XML.OUT”

Note*: We used the Rfhutil testing tool in this example, but you could use any available testing tools.

12

We look forward to your feedback or comments on this posting.   You can also email us at info@transformatech.com or go to TransformaTech.com for more information. Thanks you,

TransformaTech

WebSphere Transformation Extender (WTX) – Simple HIPAA 835 X12 5010 to XML Mapping Example

OVERVIEW:

This blog post will guide you through the steps to build a simple map in Webshpere Transformation Extender (WTX).  We will be using a HIPAA 835 X12 5010 test message and mapping it to a simple XML document.   This simple example will just do a simple file to file based transformation within WTX Design Studio.   Future blog posts or videos will extend this to leverage WTX for Integration Servers 8.4.1 to deploy a map to one of the supported run-time environments (i.e. WebSphere Message Broker)

ENVIRONMENT DETAILS:

Following is an overview of our environment used for implementing this example:

Products:

WTX Design Studio 8.4.1

WTX HIPAA Pack 4.1.1

Artifacts:

Input Test Data:  835_5010a1_Test_File.txt

XSD for creating output Type Tree:  TT_WTX_EXAMPLE_835_XML_OUT.xsd

Input Type Tree:  hipaa_x12.mtt

STEPS FOR WTX MAPPING (HIPAA 835 TO XML):

1. Create a WebSphere Transformation Extender Project

Click File –> New  –> Extender Project  –> Type in(TT_WTX_EXAMPLE_HIPAAX125010A1_TO_XML)

WTX_Blog_Pic1

2.  Create Type Trees for input and output

Input:

  • Right click on Type Trees –> Import –> File System
  • Import the hipaa_x12.mtt in your workspace by selecting File System.
  • Navigate to the hipaa files directory: <install_dir>\packs\healthcare_v4.4.1
  • Select the hipaa_x12.mtt file and click Finish.

WTX_Blog_Pic2

  • Double click on your file (hipaa_x12.mtt) and analyze it by going to Tree > Analyze > Structure and Logic

WTX_Blog_Pic3

Output:

  • Again, right click on Type Trees > Import > XML Schema
  • Import (TT_WTX_EXAMPLE_835_XML_OUT.xsd) Schema file in your workspace by selecting XML Schema
  • Navigate to your schema file directory
  • Select your schema file (TT_WTX_EXAMPLE_835_XML_OUT.xsd) and click Finish.
  • Double click on your file (TT_WTX_EXAMPLE_835_XML_OUT.mtt) and analyze it by going to Tree > Analyze > Structure and Logic

3.  Create a Map

  • Right click on Map Files -> New -> Map Source
  • Name your map file: (TT_WTX_SAMPLE_Hipaa8355010_To_XML_Mapping.mms) and click Finish.

WTX_Blog_Pic4

  • A dialog box will appear telling us the next step. Click OK

WTX_Blog_Pic15

  • Then click the New Map icon as shown below

WTX_Blog_Pic17

  • A dialog box will appear asking for a name for your map. Type in: HIPAA8355010_TO_XML_MAP

WTX_Blog_Pic18

  • Select OK.

WTX_Blog_Pic23

4.  Configure Input Card:

  • Select Input Cards, then right click it and click on “New”  (*see above image)
  • A new Input Card Dialog box will pop up
  • Type in “input1” in the CardName field
  • Browse to your “hipaa_x12.mtt” file in the Type Tree field
  • Select “Inbound x12” as a root tag in the Type field
  • Browse and select your input test file (835_5010a1_Test_File.txt) in the FilePath field.
  • Click OK

WTX_Blog_Pic6

Following is a screen shot of the input data we are using:

WTX_Blog_Pic21

5.  Configure Output Card:

  • Select Output Cards from the context menu of the map source node, then right click it and click on “New”
  • A new Output Card Dialog box will pop up
  • Type in “output1” in the CardName field
  • Browse to your “TT_WTX_EXAMPLE_835_XML_OUT.xsd” file in the Type Tree field
  • Select “X12EDI835” as a root tag in the Type field
  • Browse and select your output file name (TT_WTX_EXAMPLE_XML_OUT.xml) and location in the FilePath field.
  • Click OK

WTX_Blog_Pic7

6.  Create Mapping Rules

In order to map the input X12 data to the output XML we will need to create mapping rules. To do this we can drag and drop from the input card to the output card.  In this example, we are going to map the repeating X12 Transaction Set (ST-SE segments) to a repeating XML element.   This requires us to build a functional map.

To do this, Expand the input file element until you see the “Transaction #835 Inbound Partner Set V5010X221A1” as shown below:

We want to map the “Transaction #835 Inbound Partner Set V5010X221A1” Group to the “EOB_TRANSACTION” so we’ll drag and drop the input object to the output:

Your map should appear as follows:

WTX_Blog_Pic8

7.  Create Functional Map

The final step is to create the functional map by first using this rule below: =Transaction_ST_Loop_FunctMap(Transaction #835 Inbound Partner Set V5010X221A1:#835<>F5010X221A1<>Inbound Partner Funct’lGroup ANSI:Partner<>input1)

Next we will use the Functional Map Wizard to create the functional map. Click on the icon below to create this:

WTX_Blog_Pic9

The window below appears:

WTX_Blog_Pic10

We have three green “smiley faces” which means WTX recognizes these objects and we can proceed to create the functional map. NOTE: A yellow icon signifies unknown object and a red icon signifies an invalid object was used.

Click create and then Close to complete the functional map wizard. We are taken to the newly created functional map as shown below:

WTX_Blog_Pic11

8.  Mapping

Expand ST Segment on the input side and TRANS_SET_HDR on the output side. We can now drag and drop input elements to output elements (i.e. TSIDCd Element” to “ST01” and “TSCtrl# Element” to “ST02” as shown below):

WTX_Blog_Pic12

We notice that our functional map “Transaction_ST_Loop_FuncMap” has some empty Rule Cells. WTX needs to have a rule in every output cell in order to build. If you build a map and see several errors it may be due to several empty rule cells. To fix this we need to use the “rule =NONE”.

To auto populate several empty rule cells we can use Rules –> Insert NONE if Empty:

WTX_Blog_Pic13

In our example, we have a mapping rule for all of our output fields.

9.  Build Map

We are now ready to build the map to check for errors.  To do this, select the “build
map” icon:

WTX_Blog_Pic22

Our map built successfully so no future information is displayed.  If you would like to see the build results you can look in the Organizer located in the Outline View under the Executable Map.

Once your map is built successfully, Click on the run map icon as shown below:

WTX_Blog_Pic19

If there are no errors in running the map, you should see the following dialog box:

WTX_Blog_Pic14

You can now verify that the TT_WTX_EXAMPLE_XML_OUT.xml file was created.

WTX_Blog_Pic20
We look forward to your feedback or comments on this posting.   You can also email us at info@transformatech.com or go to TransformaTech.com for more information.
Thanks you,

TransformaTech