In Classic event publishing, a publication associates a source table or view with a WebSphere® MQ message queue or—if you adopt the File Manager option as your publishing target—a change filename prefix.
Before you begin
About this task
The publication service places messages that describe changes to source data on the message queue or writes the messages directly to the change file. Applications that need to be aware of the changes can read the messages for later processing.
The source table or view maps to a data source such as Adabas, CA-IDMS, CICS® VSAM, IMS™, or native VSAM. When a change occurs to the data that is mapped to the source table or view, Classic event publishing captures the change, converts it to a message, and writes the message to a change file or puts the message on a message queue, called a send queue.
The publishing map that you select determines whether the messages for the publication are in XML, XML with a Java™ Message Service (JMS) topic, or Delimited format.
Publications are used only in Classic event publishing. They are not used in Classic replication.
Procedure
If you want to change the properties of the publication, right-click the publication and select Update.