Scripting Websphere 6.1 configurations, Part 9


Part 3

Your service integration bus needs “destinations” (see: Queues). Adding the destinations is easy, but what you do with them later could be more complicated. I am going to assume you want to connect them with JMS Queues (which is also easy).

def addQueue(self, qname):
params = WASConfigParams();
params.add(“bus”, busName);
params.add(“node”, nodeName);
params.add(“server”, serverName);
params.add(“name”, qname);
params.add(“type”, “Queue”);
params.add(“reliability”, “BEST_EFFORT_NONPERSISTENT”);
q = AdminTask.createSIBDestination(params.asString());

Now that your queues have been added, you will have to add a client queue alias. An alias queue is not a queue, but an object that you can use to access another queue.


def addMQClientQueueAlias(self, targetQueName):
mqClientAliasName = self.makeMQClientAliasName(targetQueName);
log = Log(“SIBusConfig.addMQClientQueueAlias”, mqClientAliasName);
params = WASConfigParams();
params.add(“bus”, busName);
params.add(“aliasBus”, busName);
params.add(“targetBus”, busName);
params.add(“name”, mqClientAliasName);
params.add(“type”, “ALIAS”);
params.add(“targetName”, targetQueName);
qa = AdminTask.createSIBDestination(params.asString());

The next step in completing your messaging application is to create a standard JMS queue connection factory, then create your JMS queues, and tie them to your SIB Destinations. I will show you how to do that in my next post.

One thought on “Scripting Websphere 6.1 configurations, Part 9

Comments are closed.