Bootstrap FreeKB - IBM WebSphere - Update Activation Specification using wsadmin
IBM WebSphere - Update Activation Specification using wsadmin

Updated:   |  IBM WebSphere articles

If you are not familiar with wsadmin.sh (Linux) / wsadmin.bat (Windows), check out my article Getting Started with wsadmin.

An Activation Specification is typically scoped to a cell, node, cluster, or application server. For example, let's say there are Activation Specifications scoped to a cluster. In this scenario, you will first want to use the wsdamin command to get the ID of the cluster

The following wsadmin command can be used to get the name and ID the clusters in your cell using jython.

~]$ /opt/WebSphere/AppServer/profiles/your_profile/bin/wsadmin.sh -lang jython -c "print AdminClusterManagement.listClusters()"
WASX7209I: Connected to process "dmgr" on node your_node using SOAP connector;  The type of process is: DeploymentManager
---------------------------------------------------------------
 AdminClusterManagement: List server clusters
 Usage: AdminClusterManagement.listClusters()
 Return: List of the clusters in the cell.
---------------------------------------------------------------
 
cluster is found: myCluster(cells/your_cell/clusters/myCluster|cluster.xml#ServerCluster_1404931637566
['myCluster(cells/your_cell/clusters/myCluster|cluster.xml#ServerCluster_1404931637566']

 

Using the cluster ID, you can then use listWMQActivationSpecs to list the Activation Specifications in the cluster. In this example, there is one Activiation Specification named foo scoped to myCluster.

AdminTask.listWMQActivationSpecs('myCluster(cells/your_cell/clusters/myCluster|cluster.xml#ServerCluster_1404931637566)')

 

Which should return something like this.

foo(cells/your_cell/clusters/myCluster|resources.xml#J2CActivationSpec_1487618884381)

 

And then use showWMQActivationSpec to display the details of an Activation Specification.

AdminTask.showWMQActivationSpec('foo(cells/your_cell/clusters/your_cluster|resources.xml#J2CActivationSpec_1487618884381)')

 

Which should return something like this.

{
 brokerCCDurSubQueue=SYSTEM.JMS.D.CC.SUBSCRIBER.QUEUE,
 providerVersion=,
 clientID=,
 cleanupInterval=3600000,
 description=foo,
 sparseSubs=FALSE,
 failIfQuiescing=true,
 cleanupLevel=SAFE,
 connectionNameList=mq1.example.com(5201),mq2.example.com(5201),
 jndiName=jms/mq/actspec/foo,
 ccsid=819,
 sslResetCount=0,
 qmgrHostname=mq1.example.com,
 stateRefreshInt=60000,
 compressHeaders=NONE,
 brokerSubQueue=SYSTEM.JMS.ND.SUBSCRIBER.QUEUE,
 destinationType=javax.jms.Queue,
 rescanInterval=5000,
 poolTimeout=300000,
 compressPayload=NONE,
 msgSelection=CLIENT,
 wildcardFormat=Topic,
 brokerCCSubQueue=SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE,
 subStore=MIGRATE,
 subscriptionDurability=Nondurable,
 sslType=SPECIFIC,
 stopEndpointIfDeliveryFails=true,
 qmgrPortNumber=5201,
 qmgrName=MANAGER01,
 brokerVersion=1,
 messageSelector=,
 clonedSubs=DISABLED,
 wmqTransportType=CLIENT,
 sslConfiguration=MQSSL,
 qmgrSvrconnChannel=CHANNEL01,
 startTimeout=10000,
 acknowledgeMode=,
 destinationJndiName=jms/mq/queue/QUEUE001,
 subscriptionName=,
 name=foo,
 useJNDI=true,
 authenticationAlias=john.doe,
 WAS_EndpointInitialState=ACTIVE,
 brokerCtrlQueue=SYSTEM.BROKER.CONTROL.QUEUE,
 maxPoolSize=1,
 failureDeliveryCount=0
}

 

And then use modifyWMQActivationSpec to update the Activation Specification. In this example, the Activation Specification description will be updated from "foo" to "bar".

AdminTask.modifyWMQActivationSpec ('foo(cells/your_cell/clusters/your_cluster|resources.xml#J2CActivationSpec_1487618884381)', ['-description bar'] )

 

And then save the change.

AdminConfig.save()

 

The Activation Specification should also be in the ${WAS_INSTALL_ROOT}/profiles/your_profile/config/cells/your_cell/nodes/your_node/resources.xml file on the server.




Did you find this article helpful?

If so, consider buying me a coffee over at Buy Me A Coffee



Comments


Add a Comment


Please enter c4f8c8 in the box below so that we can be sure you are a human.