modifyWMQActivationSpec command

Use the modifyWMQActivationSpec command to change certain parameters of a WebSphere® MQ messaging provider activation specification.

Para executar o comando, use o objeto AdminTask do cliente de script wsadmin.

[IBM i]O cliente de script wsadmin é executado no Qshell. Para obter informações adicionais, consulte o tópico "Configurar o Qshell para Executar Scripts do WebSphere Application Server".

Esse comando é válido apenas quando for usado com o WebSphere Application Server Versão 7 e servidores de aplicativos posteriores. Não o utilize com versões anteriores.

Para obter uma lista de comandos administrativos do provedor de sistemas de mensagens existentes do IBM MQ, além de uma breve descrição de cada comando, insira o seguinte comando no prompt wsadmin:

print AdminTask.help('WMQAdminCommands')

Para obter ajuda de visão geral sobre um determinado comando, digite o seguinte comando no prompt wsadmin:

print AdminTask.help('command_name')

Depois de utilizar o comando, salve suas alterações na configuração principal. Por exemplo, utilize o seguinte comando:

AdminConfig.save()

Purpose

Use the modifyWMQActivationSpec command to modify a WebSphere MQ messaging provider activation specification defined at the scope at which the command is issued.

Note: You cannot change the type of an activation specification. For example, you cannot create an activation specification where you enter all the configuration information manually and then modify it to use a CCDT.
For a CCDT-based activation specification, you cannot modify of the following parameters:
  • qmgrName
  • qmgrHostname
  • qmgrPortNumber
  • qmgrSrvconnChannel
  • transportChain
  • wmqTransportType
For a generic activation specification, you cannot modify any of the following parameters:
  • ccdtUrl
  • ccdtQmgrName

Target object

A WebSphere MQ messaging provider activation specification at the specific scope.

Required parameters

The parameters for this command are identical to those used to create a WebSphere MQ messaging provider activation specification.

Optional parameters

The parameters for this command are identical to those used to create a WebSphere MQ messaging provider activation specification.

Note: If either the -qmgrHostname or -qmgrPortNumber parameters are specified without the -connectionNameList parameter being specified, then it is assumed that a connection name list should no longer be used to connect to WebSphere MQ and that the specified host name and port number information should be used instead. As a result of this the -connectionNameList parameter is set to blank.

Note the behavior of this command on the -customProperties parameter.

-customProperties
This parameter specifies custom properties to be passed to the WebSphere MQ messaging provider activation specification implementation. Typically, custom properties are used to set attributes of the activation specification which are not directly supported through the WebSphere administration interfaces.
Cada propriedade customizada é especificada usando os parâmetros de etapa de tabela nome e valor. Como são etapas de tabela, a ordem dos dois parâmetros é fixa, de modo que você deve especificar sempre primeiro o nome e depois o valor:
  • No Jython: [name value]
  • No Jacl: {name value}

For example, -WAS_EndpointInitialState is a custom property that can be used with the -customProperties parameter. The value of -WAS_EndpointInitialState must be ACTIVE or INACTIVE. -WAS_EndpointInitialState determines whether the endpoint is activated when the endpoint is registered. If the parameter is set to active, message consumption begins from the JMS destination as soon as the activation specification is used for a message-driven bean to connect with the destination.

This parameter should be ignored for subsequent activation or deactivation via the J2CMessageEndpoint MBean.

New name/value pairs are added to the existing set of custom properties using the following rules:
  • If the existing set of properties does not contain a property with the same name as that supplied as part of a modify command, the supplied property is added to the set of custom properties, unless the custom property has no value specified, when it is disregarded.
  • If the existing set of properties contains a property with the same name as that supplied as part of a modify command, and the modify command also specifies a value for the property, the existing value is replaced by the supplied value.
  • If the existing set of properties contains a property with the same name as that supplied as part of a modify command, but the modify command does not specify a value for the property, the property with the same name is deleted from the existing set of custom properties.

Example

  • Using Jython:
    wsadmin>AdminConfig.getid("/Node:9994GKCNode01")
    9994GKCNode01(cells/9994GKCNode01Cell/nodes/9994GKCNode01|node.xml#Node_1)
    
    wsadmin>AdminTask.listWMQActivationSpecs("9994GKCNode01(cells/9994GKCNode01Cell/
    nodes/9994GKCNode01|node.xml#Node_1)")
    spec1(cells/9994GKCNode01Cell/nodes/9994GKCNode01|resources.xml#
    J2CActivationSpec_1098737234986)
    
    
    wsadmin>AdminTask.modifyWMQActivationSpec("spec1(cells/9994GKCNode01Cell/
    nodes/9994GKCNode01|resources.xml#J2CActivationSpec_1098737234986)", 
    ["-destinationJndiName jms/topics/t5 -destinationType javax.jms.Topic"]) 
    spec1(cells/9994GKCNode01Cell/nodes/9994GKCNode01|resources.xml#
    J2CActivationSpec_1098737234986)
  • Using Jacl:
    wsadmin>$AdminConfig getid /Node:9994GKCNode01
    9994GKCNode01(cells/9994GKCNode01Cell/nodes/9994GKCNode01|node.xml#Node_1)
    
    wsadmin>$AdminTask listWMQActivationSpecs
    9994GKCNode01(cells/9994GKCNode01Cell/nodes/9994GKCNode01|node.xml#Node_1)
    spec1(cells/9994GKCNode01Cell/nodes/9994GKCNode01|resources.xml#
    J2CActivationSpec_1098737234986)
    
    
    wsadmin>$AdminTask modifyWMQActivationSpec
    spec1(cells/9994GKCNode01Cell/nodes/9994GKCNode01|resources.xml#
    J2CActivationSpec_1098737234986) 
    {-destinationJndiName jms/topics/t5 -destinationType javax.jms.Topic} 
    spec1(cells/9994GKCNode01Cell/nodes/9994GKCNode01|resources.xml#
    J2CActivationSpec_1098737234986)
  • The following example modifies an activation specification by activating the WAS_EndpointInitialState custom property, using Jython:
    wsadmin>AdminConfig.getid("/Node:myNode01")
    'myNode01(cells/myCell01/nodes/myNode01|node.xml#Node_1)'
    wsadmin>wsadmin>AdminTask.listWMQActivationSpecs("myNode01(cells/myCell01/nodes/myNode01|node.xml#Node_1)")
    'newas(cells/myCell01/nodes/myNode01|resources.xml#J2CActivationSpec_1298546034140)'
    wsadmin>AdminTask.modifyWMQActivationSpec("newas(cells/myCell01/nodes/myNode01|resources.xml
    #J2CActivationSpec_1298546034140)", '-customProperties [[WAS_EndpointInitialState ACTIVE]]')

Ícone que indica o tipo de tópico Tópico de Referência



Ícone de registro de data e hora Última atualização: July 9, 2016 7:52
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=rmj_wmq_jmsas_modify
Nome do arquivo: rmj_wmq_jmsas_modify.html