Remove Namespaces from XML

<xsl:stylesheet version="1.0" xmlns:xsl="">
  <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
 <!-- keep comments -->
 <xsl:template match="comment()">

  <xsl:template match="*">
    <!-- remove element prefix -->
    <xsl:element name="{local-name()}">
      <!-- process attributes -->
      <xsl:for-each select="@*">
        <!-- remove attribute prefix -->
        <xsl:attribute name="{local-name()}">
          <xsl:value-of select="."/>

Remove Empty XML elements

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0"
    <xsl:output indent="yes"/>
    <xsl:strip-space elements="*"/>
    <xsl:template match="node()|@*">
            <xsl:apply-templates select="node()|@*"/>
    <xsl:template match="*[not(@*|*|comment()|processing-instruction()) and normalize-space()='']"/>

Sidebar using simple CSS properties

Sometimes we want to show/hide a view to avoid cluttering the screen. Here is an example of how it can be done in Vaadin.

.sidebar {
  position: fixed;
  top: 0;
  right: -200px;
  width: 200px;
  height: 100%;
  background-color: #f1f1f1;
  transition: 0.5s;
  padding-left: 10px;

.show {
  right: 0;
public HelloWorldView() {


        VerticalLayout sidebar = new VerticalLayout();

        Button toggleButton = new Button("Click", event -> {
            if (sidebar.getClassNames().contains("show")) {
            } else {


        add(toggleButton, sidebar);

You can see here how the sideview is getting shown/hidden when user clicks on the Button

ACE Explorer

If you’re like us working on WMB since v6.1, we all know how much the product has changed so far. We’re working on the latest version ACEv12 for a migration project which is to migrate from IIBv10 to ACEv12. The client is using a custom application for all administrative tasks and is completely built using IBM Integration JAVA API.

As the product architecture has changed dramatically in ACE, IIB v10 APIs are deprecated so the current custom application won’t work AS IS. So, it has be re-written from scratch and today we’re able to get the ActivityLog working.

Here is the screenprint showing all message flows and one of the flow’s activity log.

ACE Explorer

Activity Log

The current version ACE12.0.3 doesn’t support deploying a bar file with a overriding property file. But, we added this feature to simplify the life of both developers/administrators. All, you’ve to do is, choose the Integration server in which you’d like to deploy, drag the bar file and properties file then click the Deploy Bar button located at the bottom.


If you’re using IIBv10 Integration API and looking for any assistance, please contact us at

Also, we’d like to know the features you’re expecting in the Web UI. You can put them in the comments section. We’ll try our best to get them into ACE Buddy. Those who provide good suggestions would get ACE Buddy free license for ONE year.

Mastering ESQL In One Day

Can someone master ESQL in just one day? YES, ESQL is not like any other programming language which has lot of statements and libraries to know. It is the most simplest language that I’ve ever seen.

The statements are limited, syntax is simple and learning is super easy. As an ACE/IIB developer, what do you do most of the time? Writing ESQL code right? Then, are you harvesting the real power of ESQL?

This one day training program is going to show you the real power of ESQL. It is going to explain you from the basics to advanced statements with examples

Here is what we’re going to cover in the course.

  1. Introduction
  2. Data Types
    1. Boolean
      1. TRUE
      2. FALSE
      3. UNKNOWN
    2. DateTime
    3. NULL
    4. Numeric
      1. DECIMAL
      2. FLOAT
      3. INTEGER
    5. Reference
    6. String
      1. BIT
      2. BLOB
      3. CHARACTER
  3. Correlation Names
    1. Root
    2. FirstChild
    3. LastChild
    4. FirstSibling
    5. NextSibling
    6. PreviousSibling
    7. LastSibling
  4. Message Components
    1. Properties
    2. Message Domain
    3. Environment
    4. Local Environment
    5. Exception List
  5. Variables
    1. Declaration
    2. Normal
    3. External
    4. Shared
    5. Scope
  6. Operators
    1. Simple Comparison 
      1. >, >=, <, <=, <> & =
    2. Complex Comparison
      1. BETWEEN
      2. EXISTS
      3. IN
      4. IS
      5. LIKE
      6. SINGULAR
    3. Logical
      1. AND
      2. OR
      3. NOT
    4. Numeric
    5. String
  7. Field References
  8. Field Types
    1. NAME
    2. TYPE
  9. Conditional Statements
    1. IF….ELSEIF…..ELSE
    2. CASE
      1. Simple
      2. Searched
  10. Looping Statements
    2. WHILE
    3. FOR
    5. ITERATE
    6. LEAVE
    7. RETURN
  11. Error Handling
    1. THROW
  12. Modules
    1. Procedures
    2. Functions
    3. CALL
    4. MOVE
  13. Handling NULL values
  14. Propagating Multiple Messages
  15. List Functions
    2. EXISTS
    4. THE
    5. ITEM
  16. Complex Functions
    1. CAST
    2. FORMAT
    3. SELECT
      1. Simple
      2. Complex
    4. ROW
    5. LIST
    6. ROW & LIST Combined
  17. Working with Database
    1. INSERT
    2. SELECT
    3. UPDATE
    4. DELETE
    6. Stored Procedures
  18. Manipulating repeating fields
  19. Calling Java methods
  20. String Functions
    3. LEFT
    4. LENGTH
    5. LOWER
    6. LTRIM
    7. OVERLAY
    9. REPLACE
    11. RIGHT
    12. RTRIM
    13. SPACE
    17. TRIM
    18. UPPER
  21. Miscellaneous
    1. ATTACH
    2. DETACH
    3. PATH
    5. DECLARE
    8. COALESCE 
    9. SLEEP
    12. EXTRACT

As the trainer has more than 15+ years of experience in ESQL, you can ask him any questions related to ESQL. If you’ve complex requirement, ask him how to resolve it during the training. So, why wait ?

Enroll into the training program and become a Master in ESQL in One Day.

Event Address: Online
Contact us at (612) 305-8684 or

Course Fee: USD : 75$/ INR 5000

To register the training, click here :

Alternative Link :

ACE Buddy

One tool for all your ACE needs like MQ testing, Kafka Testing, String manipulations, Proprty file generator and KafKa Editor.

If you’ve any suggestions or questions, feel free to ask in the comments. We’ll try to include those as well in our next release.

Message Set to DFDL Automatic Conversion


Recently we’ve started working on migrating stuffs from WMBv7 to ACEv12. The biggest challenge we’ve encountered is so far is, converting the message sets to DFDLs. Please note I’m talking about Custom Wire Formats not Cobol copy books.

I’d say it is one of the most difficult task I’ve encountered so far because the messages sets are all EDIFACT ( IBM 500 ) messages with different initiators, separators and terminators along with various padding characters and justification configuration.

So, thought of finding some automatic solution in Google but no luck. There are 100+ models need to be converted in next couple of months. All I can do so far is, write a java program to read the MXSD files and clean up the unnecessary stuffs. Also, tried to have the group indicators/terminators and delimiters converted into DFDL annotations.

This is not a 100% working solution but definitely helping a lot to quickly have the DFDL created. If you’ve any better solution, please feel free to add in the comments.

import java.nio.charset.StandardCharsets;
import java.nio.file.Files;
import java.nio.file.Path;
import java.nio.file.Paths;
import java.util.ArrayList;
import java.util.List;

import javax.swing.JFileChooser;
import javax.swing.JOptionPane;
import javax.swing.filechooser.FileSystemView;

import org.apache.commons.lang3.StringUtils;

public class TDSCleaner {

	 * @param args
	 * @throws IOException 
	public static void main(String[] args) throws IOException {
		// TODO Auto-generated method stub
		JFileChooser jfc = new JFileChooser(FileSystemView.getFileSystemView().getHomeDirectory());

        int returnValue = jfc.showOpenDialog(null);

        if (returnValue == JFileChooser.APPROVE_OPTION) {
            File selectedFile = jfc.getSelectedFile();
            Path path = Paths.get(selectedFile.getAbsolutePath());
            List&lt;String> lines = Files.readAllLines(path, StandardCharsets.UTF_8);
            List&lt;String> newLine = new ArrayList&lt;>();
            /*String rootElm = JOptionPane.showInputDialog("Enter the root element name");
            if (rootElm != null) {
				rootElm = "       01  "+FilenameUtils.getBaseName(selectedFile.getAbsolutePath())+".";
            String rootElm =  "       01  "+FilenameUtils.getBaseName(selectedFile.getAbsolutePath())+".";
            String delimiter,groupTerminator,groupIndicator;
            delimiter = null;
    		groupTerminator = null;
    		groupIndicator = null;
            for (String line : lines) {
            	if (!StringUtils.containsAny(line, "annotation","appinfo",
            			"MRMessage","MRMessage","MRComplexType","tdsElemRep"))  {
            		if (line.contains("tdsStructRep")) {
            			line = StringUtils.replace(line, "&amp;lt;U+001D&amp;gt;", "%GS;");
            			line = StringUtils.replace(line, "&amp;lt;U+001C&amp;gt;", "%FS;");
            			if (line.contains("groupIndicator")) {
							groupIndicator = "dfdl:initiator="+StringUtils.substringBetween(line, "groupIndicator=", " ");
            			if (line.contains("groupTerminator")) {
            				groupTerminator = "dfdl:terminator="+StringUtils.substringBetween(line, "groupTerminator=", " ");
            			if (line.contains("delimiter")) {
            				delimiter = "dfdl:separator="+StringUtils.substringBetween(line, "delimiter=", " ");
            		if (line.contains("&lt;xsd:sequence")) {
            			if (delimiter != null) {
            				line = StringUtils.replace(line, ">", " ")+delimiter+">";
            			if (groupIndicator != null) {
            				line = StringUtils.replace(line, ">", " ")+groupIndicator+">";
            			if (groupTerminator != null) {
            				line = StringUtils.replace(line, ">", " ")+groupTerminator+">";
            		delimiter = null;
            		groupTerminator = null;
            		groupIndicator = null;
            if (!lines.isEmpty()) {
            	String cpyFileName = FilenameUtils.getFullPath(selectedFile.getAbsolutePath())
            	FileUtils.writeLines(new File(cpyFileName), newLine);
            	JOptionPane.showMessageDialog(null, "File created successfully");
			} else {
				JOptionPane.showMessageDialog(null, "Lines are empty check your source file");




Some of the notes we’ve taken while working on a migration project from IIB to ACE. If you see anything has changed or provided incorrectly, feel free put those in the comments and we’d update this post with your comments.

  1. App Connect Enterprise v11 (first released 2018):
    1. Onpremise + Cloud
    1. IIB + App Connect Professional
    1. Local -> Toolkit ; Cloud -> Designer
  2. Integration Node is optional
  3. Integration Servers can run independently
  4. Configurable services are replaced with Policy files
  5. Local queue manager is required if Collector, Timer and Aggregate nodes are used.
  6. One Web UI can show any number of Integration Servers & Nodes
  7. Not all features available in v10 Web UI are available in ACE V11 but soon they will be available
  8. Flow and Resource Statistics are turned on by default
  9. Some mqsi commands are not available like mqsiformatlog, mqsireadlog, mqsimigratecomponents, mqsideleteconfigurableservice
  10. IIB End of Support is announced as Apr 2022
  11. ACE can run in on-premise and cloud
  12. Use TransformationAdvisor for the migration plan and impact
  13. App Connect Standard is effectively IIB standard with the addition of the Salesforce Request node whereas App Connect Enterprise is the official successor to IIB and includes the ACE V11 software, App Connect Professional V7.5.2 as well as the IBM App Connect on Cloud Service.
  14. A new administrative REST APIv2 for configuring App Connect Enterprise servers
  15. All Runtime node properties can be modified using server.conf.yml file
  16. IBM App Connect professional has 100+ connectors
  17. If there is any project created in older versions like WMB v6/v7 or anything as integration project, those would be deployed into a default Application project.
  18. Integration projects are no longer encouraged. Any attempt to subsequent redeploy independent resources will replace the entire content of the default application of an integration server with the new BAR file’s independent resources.
  19. New REST API testing utility in admin Web UI
  20. Migration
    1. Parallel Migration
      1. Install your ACEv11 environment,
      1. Configure the environment manually from scratch or reuse command scripts from IIBv10
      1. Take a branch in version control and then deploy your BAR files to the new environment
    1. Parallel Migration using extraction to help
      1. Install your ACEv11 environment
      1. Use mqsiextractcomponents to configure the v11 environment (this will help to create policies for you from config services for example) to help ensure you don’t forget configuration from your v10 system. Discard the run directory contents, because instead you are going to deploy items to the new system one by one as the next action
      1. Take a branch in version control and then deploy your BAR files to the new environment.
    1. Big Bang using extraction
      1. Install your ACEv11 environment
      1. Use mqsiextractcomponents to configure the v11 environment (this will help to create policies for you from config services for example) to help ensure you don’t forget configuration from your v10 system. Don’t discard the run directory contents
      1. Restart the integration node.
  21. There is no change in the project types. It is same as v10.
    1. Application (same as v10)
    1. Library (same as v10)
    1. Shared Library (same as v10)

How do I capture the messages on the fly in IIB?

IBM has provided lot of ways to capture the messages flowing through our message flows. In this post, we are going to discuss about one of them and it is also one of the most unnoticed.

IIB allows you to capture the messages by enabling monitoring profile or by writing custom subflows or using trace nodes.

The most frequently used one is subflows and now a days people use monitoring profile too a lot. There are companies which do not have logs at all ( don’t know how they survive).

Have you ever used Record & Replay? If not, just google to get some basic idea on how that works.

This post is also utilizing the same Record & Replay concept but it does on the fly. I do not have any database setup to store the messages permanently. Just going with built-in capacity of the Integration node.

Let me put here the sequence of steps to achieve this

  1. Enable recording
  2. Enable Injection
  3. Retrieve Recorded Message

Let me put here the Java APIs used here

public void enableRecording(ExecutionGroupProxy proxy, boolean status) throws ConfigManagerProxyLoggedException, ConfigManagerProxyPropertyNotInitializedException {
		if (status) {
		}else {
			// clear recorded data and reset server to turn off recording and injection
		enableInjection(proxy, status);
	public void enableInjection(ExecutionGroupProxy proxy, boolean status) throws ConfigManagerProxyLoggedException, ConfigManagerProxyPropertyNotInitializedException {
		if (status) {
		}else {
			// clear recorded data and reset server to turn off recording and injection
public List<RecordedTestData> retreiveRecordedMessage(MessageFlowProxy mf) throws ConfigManagerProxyPropertyNotInitializedException, ConfigManagerProxyLoggedException {
		Properties filterProps = new Properties();
		String name = getApplication(mf).getName();
//		System.out.println(name);
		if (name != null) {
		}else {
			name = getLibraryProxy(mf).getName();
			if (name != null) {
//		System.out.println(mf.getName());
//		ExecutionGroupProxy egProxy = mf.getExecutionGroup();
//		List<RecordedTestData> dataList = egProxy.getRecordedTestData(filterProps);
		return mf.getExecutionGroup().getRecordedTestData(filterProps);

That’s it. Once you enable recording, the message flow automatically turns into like this

The recorded message is here (I’ve a UI to make this easier to read)

Here is the local environment message

<localEnvironment xmlns:iib="" iib:parser="MQROOT" iib:injectable="true">
         <Retained iib:valueType="BOOLEAN">FALSE</Retained>
         <QualityOfService iib:valueType="INTEGER">0</QualityOfService>
         <Topic iib:valueType="CHARACTER">IBM/IntegrationBus/default/Monitoring/Hello</Topic>
         <Duplicate iib:valueType="BOOLEAN">FALSE</Duplicate>

And here is the payload

<message xmlns:iib="" iib:parser="GENERICROOT" iib:injectable="true">
   <Properties iib:parser="GENERICPROPERTYPARSER">
      <MessageSet iib:valueType="CHARACTER" iib:elementType="0x03000000"></MessageSet>
      <MessageType iib:valueType="CHARACTER" iib:elementType="0x03000000"></MessageType>
      <MessageFormat iib:valueType="CHARACTER" iib:elementType="0x03000000"></MessageFormat>
      <Encoding iib:valueType="INTEGER">546</Encoding>
      <CodedCharSetId iib:valueType="INTEGER">5348</CodedCharSetId>
      <Transactional iib:valueType="BOOLEAN">TRUE</Transactional>
      <Persistence iib:valueType="BOOLEAN">FALSE</Persistence>
      <CreationTime iib:valueType="GMTTIMESTAMP">2021-04-13 16:54:58.451</CreationTime>
      <ExpirationTime iib:valueType="INTEGER">-1</ExpirationTime>
      <Priority iib:valueType="INTEGER">0</Priority>
      <ReplyIdentifier iib:valueType="BLOB"></ReplyIdentifier>
      <ReplyProtocol iib:valueType="CHARACTER">UNKNOWN</ReplyProtocol>
      <Topic iib:elementType="0x03000000"/>
      <ContentType iib:valueType="CHARACTER" iib:elementType="0x03000000"></ContentType>
      <IdentitySourceType iib:valueType="CHARACTER" iib:elementType="0x03000000"></IdentitySourceType>
      <IdentitySourceToken iib:valueType="CHARACTER" iib:elementType="0x03000000"></IdentitySourceToken>
      <IdentitySourcePassword iib:valueType="CHARACTER" iib:elementType="0x03000000"></IdentitySourcePassword>
      <IdentitySourceIssuedBy iib:valueType="CHARACTER" iib:elementType="0x03000000"></IdentitySourceIssuedBy>
      <IdentityMappedType iib:valueType="CHARACTER" iib:elementType="0x03000000"></IdentityMappedType>
      <IdentityMappedToken iib:valueType="CHARACTER" iib:elementType="0x03000000"></IdentityMappedToken>
      <IdentityMappedPassword iib:valueType="CHARACTER" iib:elementType="0x03000000"></IdentityMappedPassword>
      <IdentityMappedIssuedBy iib:valueType="CHARACTER" iib:elementType="0x03000000"></IdentityMappedIssuedBy>
   <XMLNSC iib:parser="xmlnsc">
      <wmb:event xmlns:wmb="">
               <wmb:productVersion iib:valueType="CHARACTER" iib:elementType="0x03000100">100011</wmb:productVersion>
               <wmb:eventSchemaVersion iib:valueType="CHARACTER" iib:elementType="0x03000100"></wmb:eventSchemaVersion>
               <wmb:eventSourceAddress iib:valueType="CHARACTER" iib:elementType="0x03000100">MQ Input.transaction.Start</wmb:eventSourceAddress>
                  <wmb:eventName iib:valueType="CHARACTER" iib:elementType="0x03000100">OrderReceived</wmb:eventName>
                  <wmb:creationTime iib:valueType="CHARACTER" iib:elementType="0x03000100">2020-06-01T02:02:32.402892Z</wmb:creationTime>
                  <wmb:counter iib:valueType="CHARACTER" iib:elementType="0x03000100">1</wmb:counter>
                  <wmb:localTransactionId iib:valueType="CHARACTER" iib:elementType="0x03000100">f8a1af6d-013b-4420-9c1b-baf23d5e10a4-5</wmb:localTransactionId>
                  <wmb:parentTransactionId iib:valueType="CHARACTER" iib:elementType="0x03000100"></wmb:parentTransactionId>
                  <wmb:globalTransactionId iib:valueType="CHARACTER" iib:elementType="0x03000100"></wmb:globalTransactionId>
                  <wmb:name iib:valueType="CHARACTER" iib:elementType="0x03000100">IB10NODE</wmb:name>
                  <wmb:UUID iib:valueType="CHARACTER" iib:elementType="0x03000100">b7d2e6dd-0b36-4728-9015-818133dbeb14</wmb:UUID>
                  <wmb:name iib:valueType="CHARACTER" iib:elementType="0x03000100">default</wmb:name>
                  <wmb:UUID iib:valueType="CHARACTER" iib:elementType="0x03000100">61704de3-b47c-4b23-b95f-0ffd934fdcb1</wmb:UUID>
                  <wmb:uniqueFlowName iib:valueType="CHARACTER" iib:elementType="0x03000100">IB10NODE.default.TestMon.TestMon</wmb:uniqueFlowName>
                  <wmb:name iib:valueType="CHARACTER" iib:elementType="0x03000100">TestMon</wmb:name>
                  <wmb:UUID iib:valueType="CHARACTER" iib:elementType="0x03000100">429ff9ef-1c8d-48c1-bf42-99ac3bd247fb</wmb:UUID>
                  <wmb:threadId iib:valueType="CHARACTER" iib:elementType="0x03000100">21980</wmb:threadId>
                  <wmb:nodeLabel iib:valueType="CHARACTER" iib:elementType="0x03000100">MQ Input</wmb:nodeLabel>
                  <wmb:nodeType iib:valueType="CHARACTER" iib:elementType="0x03000100">ComIbmMQInputNode</wmb:nodeType>
                  <wmb:detail iib:valueType="CHARACTER" iib:elementType="0x03000100">IN.Q</wmb:detail>
         <wmb:applicationData xmlns="">
               <wmb:elementName iib:valueType="CHARACTER" iib:elementType="0x03000100">MQMD</wmb:elementName>
                  <SourceQueue iib:valueType="CHARACTER">IN.Q</SourceQueue>
                  <Transactional iib:valueType="CHARACTER">true</Transactional>
                  <Encoding iib:valueType="CHARACTER">273</Encoding>
                  <CodedCharSetId iib:valueType="CHARACTER">1208</CodedCharSetId>
                  <Format iib:valueType="CHARACTER">MQSTR   </Format>
                  <Version iib:valueType="CHARACTER">2</Version>
                  <Report iib:valueType="CHARACTER">0</Report>
                  <MsgType iib:valueType="CHARACTER">8</MsgType>
                  <Expiry iib:valueType="CHARACTER">-1</Expiry>
                  <Feedback iib:valueType="CHARACTER">0</Feedback>
                  <Priority iib:valueType="CHARACTER">0</Priority>
                  <Persistence iib:valueType="CHARACTER">0</Persistence>
                  <MsgId iib:valueType="CHARACTER">414d5120494942763130514d475220204064d15e10000105</MsgId>
                  <CorrelId iib:valueType="CHARACTER">000000000000000000000000000000000000000000000000</CorrelId>
                  <BackoutCount iib:valueType="CHARACTER">0</BackoutCount>
                  <ReplyToQ iib:valueType="CHARACTER">                                                </ReplyToQ>
                  <ReplyToQMgr iib:valueType="CHARACTER">IIBv10QMGR                                      </ReplyToQMgr>
                  <UserIdentifier iib:valueType="CHARACTER">vaithu      </UserIdentifier>
                  <AccountingToken iib:valueType="CHARACTER">160105150000002d74cc5dfa721e73431607412b32030000000000000000000b</AccountingToken>
                  <ApplIdentityData iib:valueType="CHARACTER">                                </ApplIdentityData>
                  <PutApplType iib:valueType="CHARACTER">28</PutApplType>
                  <PutApplName iib:valueType="CHARACTER">vaithu</PutApplName>
                  <PutDate iib:valueType="CHARACTER">2020-06-01</PutDate>
                  <PutTime iib:valueType="CHARACTER">02:02:32.480</PutTime>
                  <ApplOriginData iib:valueType="CHARACTER">    </ApplOriginData>
                  <GroupId iib:valueType="CHARACTER">000000000000000000000000000000000000000000000000</GroupId>
                  <MsgSeqNumber iib:valueType="CHARACTER">1</MsgSeqNumber>
                  <Offset iib:valueType="CHARACTER">0</Offset>
                  <MsgFlags iib:valueType="CHARACTER">0</MsgFlags>
                  <OriginalLength iib:valueType="CHARACTER">-1</OriginalLength>

By this way, if you’ve a need to immediately see what is flowing through your messages, simply implement this solution and see the messages on the fly. Once done, clear up the recordings.

If you’re interested to know more about this solution, feel free to contact us at WhatsApp +1 6123058684.