WebSphere logo Classic Federation Server for z/OS, Version 9.1
WebSphere logo Classic Replication Server for z/OS, Version 9.1
WebSphere logo Classic Data Event Publisher for z/OS, Version 9.1
WebSphere logo Data Integration Classic Connector for z/OS, Version 9.1


Creating and modifying publishing maps for Classic event publishing to WebSphere MQ

A publishing map provides information about the target to which the publication service writes change messages. The information presented here describes creating publishing maps for WebSphere® MQ.

Before you begin

The information contained in a publishing map differs, depending on whether you adopt the WebSphere MQ option or the File Manager option as your publishing target. If you adopt the WebSphere MQ option, a publishing map identifies a send queue that is used to transport change messages to applications.

If you adopt the File Manager option, a publishing map provides information about the data sets that store change messages for later processing by applications. See the topic about configuring File Manager for information about how to create a publishing map for that publishing target.

When you create a publishing map for WebSphere MQ, you specify the send queue and the values of parameters for the send queue.

You must have $VSAM authority or SYSADM authority on the data server where you will store the information about the publication.

About this task

After you create at least one publishing map, you can create one or more publications. The data server publishes all messages based on the format that you specify in the publishing map.

Procedure

To create a publishing map:

  1. Open the New Publishing Map wizard. In the Database Explorer, right-click the Publishing Maps folder for a data server and select New Publishing Map.
  2. Specify these attributes of the publishing map:
    • The name of the publishing map.
    • The WebSphere MQ name of the send queue.
    • Whether to use the publishing map for publishing messages in XML, XML with a Java™ Messaging Service (JMS) topic, Delimited format, Delimited format with a JMS topic, or Raw format.
    • Whether to use the publishing map to publish messages for each row-level change or for each transaction.
    • If you choose to publish messages for each transaction, specify the maximum size for a message that is related to this publishing map. Any message that is larger than the maximum size is split into two or more smaller messages.

      If you are publishing messages that are in Delimited format, subsequent messages follow in order and have no header information.

    • A description of the publishing map.
    • The type of activation.
      • Deferred: The publication is activated when you restart the correlation service
      • Immediate: The publication is activated when you create it
      • None: The publication is not activated automatically, and you must activate it manually
The publishing map appears in the Publishing Maps folder and is active.

If you want to modify the properties of the publishing map, right-click it and select Update.

Related concepts
WebSphere MQ objects for change capture
Related tasks
Specifying the WebSphere MQ objects to use for change capture
Configuring File Manager for Classic event publishing
Related reference
Publishing map properties


Feedback

Update icon Last updated: 2007-10-09