IBM has several solutions for transformation of data. One is the Map Editor in Sterling B2B Integrator. We also have IBM WebSphere Transformation Extender (WTX). WTX is a more powerful tool than the Sterling B2B Mapper, and some times one has maps that has requirements that the Sterling B2B Mapper can’t fulfill. One very simple example is one-to-many, many-to-one or many-to-many maps with more than one input or output, where WTX has a strength over the Sterling B2B Mapper.
What IBM strives for, is to use the best we have in our toolbox, to make the best possible solution. So since we have Sterling B2B Integrator as a very strong B2B Gateway and WTX as a very strong transformation solution, IBM did the only right thing – made WTX for Integration Servers, which is a version of WTX made to be embedded inside e.g. Sterling B2B Integrator. That gives the opportunity to run WTX maps the same way as running native Sterling maps inside Sterling B2B Integrator.
To make this work however, WTX has to be installed on the Sterling B2B Server. And that is what I am going to do in this article. This is however the first time I am doing this myself, so bare with me if something is not by the book. We have Consultants to do it properly…
WebSphere Transformation Extender can’t be “owned” by the root user. So I have to start by creating a new user. I call my new user wtx.
Install WebSphere Transfomration Extender for Integration Servers
I start by unpacking the Installation file i have downloaded. I downloaded WTX for Integration Servers 188.8.131.52 for Linux, which is the current release. I have my Sterling B2B Integrator running on a RedHat Enterprise Linux 7 – 64-bit server. This is a tar-file, and inside there are two new tar-files. One for 32-bit and one for 64-bit.
Start the installation like below. One issue in my case was that I was missing ksh in my Linux Environment. So I had to install ksh (yum install ksh) since the installation file is using ksh.
The Text-based installation Program starts.
Enter through the very long license…
I accept the default value for temporary Directory. And also the default values for everything else. The wtx user I created is used in the installation.
Select what components to install. I choose to install everything.
Then grab a cup of coffee, and let the installation run until it is finished.
When the installation itself is done, there is some post-installation procedures.
The file InstallWTXService.sh must be run to do the setup and linking of WebSphere Transformation Extender and Sterling B2B Integrator. The file is in the folder <installationFolder>/dtx4si/. Before running the file, it has to be edited to match the installation.
The path to the installation folder for both WTX and SB2BI has to be set in the file.
When the file is edited, save the file and run it.
PS: I had one issue when running the file. The InstallWTXService.sh is calling the setupfiles.sh in the SB2BI bin folder. And the setupfiles.sh is calling a file called tmp.sh in the install folder for SB2BI. This file don’t exist, and thus the InstallWTXService.sh ends up with an error. I just did a quick-fix by commenting out the reference to tmp.sh (like the screenshot below), hoping it was not of any importance, and ran the InstallWTXService.sh. I am not sure what this tmp.sh file should be doing, but it seemed to work fine to just comment it out. But it’s probably not IBM Best Practice…:)
When this is done, i edited back the setupfiles.sh to what it should be like, and started Sterling B2B Integrator.
In the GUI, I can now see that I have the possibility to list WTX maps as well as uploading WTX maps, even though I don’t yet know if it will work.
The last part of this is to install the Design Studio to be able to build and compile WTX Maps.
I downloaded WebSphere Transformation Extender Design Studio 184.108.40.206 and installed it on my laptop. The Design Studio is by the way only available for Microsoft Windows. The Design Studio is straight forward to install.
The next thing to do, and here I needed some help from colleagues over seas in the US, is to install WebSphere Transformation Extender for Integration Servers 220.127.116.11 on my laptop. To be honest, I don’t yet really see the logic in that. Since the Design Studio is connecting to a remote server (my Linux box where SB2BI and WTX4IS is residing), I would imagine that the code needed to connect to a remote server and support Sterling B2B Integrator would be packaged together with the Design Studio itself. But it isn’t. Eventually I will understand the logic behind that…:) So I downloaded WebSphere Transformation Extender for Integration Servers 18.104.22.168 for Windows and installed that as well on my Windows Laptop.
Configure WebSphere Transformation Extender Design Studio
The next thing to do is to configure WTX Design Studio to connect to a Sterling B2B Integrator Server.
This is done under Window -> Preferences in Design Studio, and in the Preferences under Transformation Extender -> Map -> Sterling B2B Integrator. Fill in the information to connect to a SB2BI Server, and the Target Platform (the OS SB2BI is running on).
This is what is needed to design a WTX Map, and test it on Sterling B2B Integrator.
Test the configuration
To test if it works, the easiest thing to do is to use the pre-configured examples in the WebSphere Transformation Extender for Integration Servers 22.214.171.124 installed earlier.
I imported the WTX_IVT_Example_For_SIB2B. In my case was to be found in C:\IBM\WebSphere Transformation Extender 126.96.36.199\examples\integrations\SterlingB2B\WTX_IVT_Example_For_SIB2B\WTX_IVT_Example_For_SIB2B.
After importing that project to the Design Studio, I opened the map BasicMap.mms, Right Clicked on the Executable Map and selected Run on Sterling B2B Integrator.
The Map will then, through WebService, run on the Sterling B2B Integrator Server, and the result will come back to the Design Studio, as well as be visible in the Process Log in Sterling B2B Integrator.
This was my first try on installing WebSphere Transformation Extender for Integration Servers. It went mostly OK, but I had some issues with the setupfiles.sh that was pointing to a non-existent file, and the fact that I did not understand that I had to install WebSphere Transformation Extender for Integration Servers both on my server and on my Client Computer. But with some help from the always helpful developers in the US, I managed to get it installed and working.
The next step for me now, is to install the server part on my second Sterling B2B Integrator node, since I have a clustered solution.
Below is a diagram of my current environment after the WTX for Integration Servers install.