To replace an existing trigger with a new trigger, use the following sis-console command, Ant task, or related MBean operations.

Console command

replacetrigger

Command

replacetrigger <ra-entity> <file>
    Replace a previously installed trigger component with new content from a file
Warning This command installs in the SIS the trigger XML file — which must be on the local filesystem of the management client.
Note If a trigger with same identity as that denoted in the file does not exist, this command behaves the same as installtrigger.

Example

To replace an existing trigger with trigger example-trigger.xml from the local filesystem of the management client, into the SIS instance named sis:

$ ./sis-console replacetrigger sis example-trigger.xml
Replaced trigger TriggerID[name=Example,vendor=ABC,version=1.0] from file example-trigger.xml

Ant task

replacetrigger

Task

<replacetrigger file="..."/>

Example

To replace an existing trigger with trigger example-trigger.xml from the local filesystem of the management client:

<sis-in-management>
    <replacetrigger file="example-trigger.xml"/>
</sis-in-management>

or

<sis-sip-management>
    <replacetrigger file="example-trigger.xml"/>
</sis-sip-management>

MBean operations

MBean

replace

Operation

To replace a trigger from a URL:

public TriggerID replace(String url)
    throws NullPointerException, MalformedURLException,
           DeploymentException, ManagementException;
Warning The SIS retrieves the trigger XML file using the specified URL — which must be resolvable from the Rhino node.

replace

Operation

To replace a trigger from a byte array:

public TriggerID replace(byte[] content)
    throws NullPointerException, DeploymentException, ManagementException;
Note The SIS reads the trigger XML data from the specified byte array.
Previous page Next page
SIS Version 3.2