Scripting Websphere 6.1 configurations, Part 8


Part 2

Setting up the SIBus (Service Integration Bus) is fairly trivial. For this activity that needs to be performed first, below are the examples.

def create(self):
params = WASConfigParams();
params.add(“bus”, self.busName);
params.add(“busSecurity”, “false”);

After the SIBus has been created. You create a Bus Member. There are probably good reasons why this is a separate exercise but I haven’t stumbled upon the reason.

def addServerMember(self):
params = WASConfigParams();
params.add(“bus”, self.busName);
params.add(“node”, self.wasDef.nodeName);
params.add(“server”, self.wasDef.serverName);
params.add(“fileStore”, “”);
params.add(“logSize”, 10);
params.add(“minPermanentStoreSize”, 10);
params.add(“maxPermanentStoreSize”, 500);
params.add(“minTemporaryStoreSize”, 10);
params.add(“maxTemporaryStoreSize”, 500);

This third task, albeit optional, is necessary if you wish to connect to your queues using third party tools for monitoring and debugging. I recommend it.

Note: The qmName HAS to follow the below naming convention. Don’t ask why.

def createMQClientLink(self):
msgEngine = self.getMessagingEngine();
params = WASConfigParams();
params.add(‘name’, self.mqClientLinkName);
params.add(‘channelName’, “WAS.JMS.SVRCONN”);
params.add(“qmName”, “WAS_” + self.wasDef.nodeName + “_” + self.wasDef.serverName);
params.add(“defaultQM”, “true”);
params.add(“heartBeat”, “300”);
AdminConfig.create(‘SIBMQClientLink’, msgEngine, params.asList());

The few posts will finish off with examples of creating SIQueues and tying them to JMS Queue’s and a Queue Connection Factory. Then I will show examples of creating Activation Specs.