Use the deployEventServiceMdb command to deploy the event service message driven bean onto your server.
Purpose
The deployEventServiceMdb command is a Common Event Infrastructure administrative command is available for the AdminTask object. Use this command to deploy the event service MDB to a server or cluster. For more information about the AdminTask object, see the WebSphere Application Server documentation.
Note: The product uses a Jython
version that does not support Microsoft Windows 2003, Windows Vista, or Windows 7 operating systems.Parameters
- - nodeName
- The name of the node where the event service MDB should be deployed. If this parameter is specified, then the serverName parameter must be specified. You must not specify this parameter if the clusterName parameter is specified.
- - serverName
- The name of the server where the event service MDB should be deployed. You must specify this parameter if the nodeName parameter is specified. You must not specify this parameter if the clusterName parameter is specified.
- - clusterName
- The name of the cluster where the event service MDB should be deployed. You must not specify this parameter if the nodeName and serverName parameters are specified.
- - applicationName
- The name of the event service MDB application to be deployed on a server or cluster.
- - listenerPort
- The name of the listener port where the event service MDB should publish the events. The listener port must already be created. You must not specify this parameter if the activationSpec parameter is specified.
- - activationSpec
- The JNDI name of activation specification where the event service MDB should publish the events. The activation specification must already be created. You must not specify this parameter if the listenerPort parameter is specified.
- - qcfJndiName
- The JNDI name of the JMS queue connection factory object to be used by the event service MDB. You must specify this parameter if the activationSpec parameter is specified.
Sample
Batch mode example usage:
- Using Jacl:
$AdminTask deployEventServiceMdb {-applicationName appname -nodeName nodename -serverName servername -listenerPort lpname}$AdminTask deployEventServiceMdb {-applicationName appname -clusterName clustername -activationSpec asjndiname -qcfJndiName qcfjndiname} - Using Jython string:
AdminTask.deployEventServiceMdb('[-applicationName appname -nodeName nodename -serverName servername -listenerPort lpname]')AdminTask.deployEventServiceMdb ('[-applicationName appname -clusterName clustername -activationSpec asjndiname -qcfJndiName qcfjndiname]') - Using Jython list:
AdminTask.deployEventServiceMdb(['-applicationName', 'appname', '-nodeName', 'nodename', '-serverName', '-servername', ' -listenerPort', 'lpname']) AdminTask.deployEventServiceMdb(['-applicationName', 'appname', '-clusterName', 'clustername', '-activationSpec', 'asjndiname', '-qcfJndiName', 'qcfjndiname'])
Interactive mode example usage:
- Using Jacl:
$AdminTask deployEventServiceMdb {-interactive} - Using Jython string:
AdminTask.deployEventServiceMdb('[-interactive]') - Using Jython list:
AdminTask.deployEventServiceMdb(['-interactive'])
