The RepublishEventsFromOfflineFile Tool
The RepublishEventsFromOfflineFile tool is a command-line recovery tool that imports events into a Universal Messaging realm server store (channel or queue) from any of the following sources:
An XML file
Importing can be done from an XML file produced by the ExportEventsFromOfflineMemFile tool. The XML file is a copy of the store's persistent memory file (or multiple memory files for a multi-file store). Selector based event filtering can be applied while importing with the tool. Republishing is done as transaction event publishing.
Input files
Importing can be done from offline memory files of the store taken from the parent realm's data directory. The offline memory files have the filetype *.mem. When importing multi-file stores, you specify the folder that contains the *.mem files. When importing a mixed/persistent store, you specify a single .mem file.
When you invoke the tool, you can specify either a mem file (or mem folder name), or an XML file, but not a combination of these options.
The -protobufdescriptor input parameter
Filtering based on protobuf event data will be performed starting from v10.3 and not performed in earlier versions.
Import from the mem file of a protobuf store
If the import is performed from a protobuf store's mem file and the protobufdescriptor parameter specified is the same as for the "source" channel, and the "republish" channel has the protocol buffer file descriptor set, events will be republished as protobuf events.
If the import is performed from a protobuf store's mem file and the protobufdescriptor parameter specified is the same as for the "source" channel, but the "republish" channel has another protocol buffer file descriptor or is not a protobuf channel, then event republishing will not be done.
If the import is performed from a protobuf store's mem file but the protobufdescriptor parameter is not specified, events will be republished as non-protobuf events to a non-protobuf store and as protobuf events to a store with the protocol buffer file descriptor set.
Import from mem file of non-protobuf store
If the import is performed from a non-protobuf store's mem file and the protobufdescriptor parameter is not specified, events will be republished as non-protobuf events to any channel.
If the import is performed from a non-protobuf store's mem file and the protobufdescriptor parameter is specified and coincides with the descriptor of the "republish" channel, events will be republished as non-protobuf events.
But if the import is performed from a non-protobuf store's mem file and the protobufdescriptor parameter is specified and does not coincide with the descriptor of the "republish" channel, events will not be republished.
Import from an XML file
If the source file belongs to (was exported from) a protobuf channel's mem file, events will be republished as protobuf events to a store with the protobuf descriptor and as non-protobuf events to other channels.
If the protobufdescriptor parameter is specified, the tool will validate if the "republish" channel has the same protocol buffer file descriptor set.
The -batchsize input parameter
This parameter can be optionally specified when running the tool. It defines the number of events which will be read/loaded to the memory/ from the mem/XML file, filtered and then published to the "destination" store as a single batch.
The default batch size is 100.