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


WebSphere MQ objects for change capture

If you adopt the WebSphere®® MQ publishing option for change messages, you must createWebSphere MQ objects and define them to the Classic data server.

Depending on whether you are setting up an event publishing or replication environment, or whether you are sending changes to local or remote images, you need selected MQ objects:

In an event publishing environment, a send queue transports messages that are associated with publications to consuming applications. Event publishing also requires that you create a publishing map to define the send queue to the data server and specify the message file format.

In a replication environment, a send queue transports messages that are associated with subscriptions to Q Apply.

Related concepts
Mapping data for change capture
Configuring publication to queues or files
Related tasks
Specifying the WebSphere MQ objects to use for change capture
Creating and modifying publishing maps for Classic event publishing to WebSphere MQ
Mapping tables for Classic event publishing
Mapping tables for Classic replication


Feedback

Update icon Last updated: 2007-10-09