Republish Events
Republishes a snooped event on a channel or queue.
Syntax
To republish a snooped event on a channel:
cc exec administration component nodeAlias Universal-Messaging-instanceName
channels publish name=channelName data=eventContent id=originalEventId
user=userName republish=true [tag=eventTag] [ttl=ttlValue]
[persistent={true|false}] [transient={true|false}] [properties=propertiesString]
[pubcount=publishCount] [sendasprotobuf={true|false}]
[protobufdescriptor=protobufDescriptor] [purgeoriginal={true|false}]
To republish a snooped event on a queue:
cc exec administration component nodeAlias Universal-Messaging-instanceName
queues publish name=queueName data=eventContent republish=true [tag=eventTag]
[ttl=ttlValue] [persistent={true|false}]
[properties=propertiesString] [pubcount=publishCount]
[sendasprotobuf=[true|false}] [protobufdescriptor=protobufDescriptor]
Arguments and Options
nodeAlias
Required. The alias name of the installation in which the Universal Messaging server instance is installed.
Universal-Messaging-instanceName
Required. The ID of the Universal Messaging server instance on which you want to republish a snooped event.
name=channelName
Required for republishing an event on a channel. The name of the channel on which you want to republish a snooped event.
name=queueName
Required for republishing an event on a queue. The name of the queue on which you want to republish a snooped event.
data=eventContent
Required. The content of the event.
id=originalEventId
Required when republishing an event on a channel. The ID of the original event.
user=userName
Required when republishing an event on a channel. The username of the user who started snooping on the event on the channel.
republish={true|false}
Required. Whether to republish the snooped event. Values are:
true false (default)
[purgeoriginal={true|false}]
Optional. Whether to purge the original event from the channel. Values are:
true false (default)
[tag=eventTag]
Optional. The tag of the event.
[ttl=ttlValue]
Optional. The time-to-live (TTL) of the event in milliseconds. Defines how long the event remains available on the channel or queue. If you specify a TTL of 0, the event remains on the channel or queue indefinitely.
[persistent={true|false}]
Optional. Whether the event is persistent. Values are:
true false (default)
[transient={true|false}]
Optional. Supported only for channels. Whether the event is transient. Values are:
true false (default)
[properties=propertiesString]
Optional. A string that contains event properties in the following JSON format:
[ { name: "property1_name", type: "property1_type", value: property1_value }, { name: "property2_name", type: "property2_type", value: property2_value }, … ]
where
propertyX_name is the name of the property.
propertyX_type is the type of the property and can have one of the following values:
int,
byte,
long,
short,
float,
double,
boolean,
char,
string,
int[],
byte[],
long[],
short[],
float[],
double[],
boolean[],
char[], and
string[].
propertyX_value is the value of the property.
[pubcount=publishCount]
Optional. The number of times to republish an event. If you omit pubcount, the option defaults to 1.
[sendasprotobuf={true|false}]
Optional. Whether to convert the event content in the data option to a Protobuf event that matches a Protobuf schema specified in the protobufdescriptor option and already uploaded on the channel or queue. Values are:
true false (default)
[protobufdescriptor=protobufDescriptor]
Required for Protobuf events. The Protobuf file descriptor that defines the messaging schema to be used for converting the event content in the data option to a Protobuf event.
Usage Notes
When you use the
properties option, consider the following information:
Include the
-f json option to specify the format of the properties string.
Enclose char and string property values, and values with spaces in double quotes ("). If the value contains double quotes, replace them with a backslash and double quotes (\").
For array values, specify a valid JSON array of the corresponding type.
Before republishing a snooped event on a channel or queue, you must start snooping on the channel or queue and obtain the event ID.
Examples
To republish an event with ID "3", modified event data "CancelledCustomerOrders", and modified event tag "CCOrders", snooped by user "Administrator", on channel "channel2" that is created on the server instance with ID "Universal-Messaging-umserver", installed in the installation with alias name "sag01":
cc exec administration component sag01 Universal-Messaging-umserver channels
publish name=channel2 data=CnacelledCustomerOrders tag=CCOrders
republish=true id=3 user=Administrator