SIB Configuration Migration script

The script demonstrates how to migrate a single messaging engine configuration from classic WAS to Liberty. script

If a user needs to create a messaging engine configuration in liberty server similar to that of existing classic WAS configuration manually, the steps to be performed are -

1. Add the wasJmsServer feature to enable the messaging engine and wasJmsClient feature if you need to talk from same server or from different server.


2. Add an entry for each destination based on the properties which are defined in WAS classic and mapping them according to the table provided in the blog post. Example -

             <queue id="testQueue"  maxMessageDepth = "20" maintainStrictOrder = "true" >

3. start the server

The automates the above mentioned steps and when run against WAS Classic environment it would generate a configuration for liberty. The end result is a representation of single messaging engine on the liberty server with the destination configuration of WAS Classic.

This sample can be installed onto runtime version ${bvt.prop.appliesto.minimum.version}.


Optional parameters

<output_xml_file> Creates a xml file and stores the output

Sample use and resulting messages

>> wsadmin Output.xml

Assuming that the classic WAS SIB configuration consists of 4 user created destinations say, testQueue, CustomExceptionDestination, TopicSpace1 and aliasQ. The generated output will look like -

>> <server>


  <messagingEngine id="defaultME">

   <queue id="testQueue"  exceptionDestination = "CustomExceptionDestination" maxMessageDepth = "20" receiveAllowed = "false" forceReliability = "BestEffortNonPersistent" maxRedeliveryCount = "2" maintainStrictOrder = "true" >

   <queue id="CustomExceptionDestination"  >

   <topicSpace id="TopicSpace1"  maxMessageDepth = "1000" receiveAllowed = "false" >

   <alias id="aliasQ"  targetDestination = "testQueue" >



The xml so generated can be included in the server.xml as <include location="Output.xml"/>.

Sample Structure

  • Copyright.txt
  • readme.html