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


Configuring File Manager for Classic event publishing

To publish changed data to data sets, set up File Manager as your publishing target and create one or more publishing maps.

Before you begin

About this task

Configure File Manager options in Classic Data Architect by using the Configure Publishing Target wizard and the New Publishing Map wizard.

The publishing target specifies the following information as a one-time server setup:

  • A restart filename prefix for the files that store restart points for recovery processing
  • A commit interval that specifies how long the data server waits before committing change messages to a permanent file

A publishing map specifies the following information:

  • The publishing map name that you will use later when you create publications
  • The change filename prefix for the files that store change messages for this map
  • The file format for change messages that use this map

You can create multiple publishing maps for a given File Manager. You link your publishing map with a mapped table later when you create a publication.

Procedure

To configure File Manager for Classic event publishing:

  1. Run the New Publishing Target wizard by right clicking on the database connection in the Database Explorer and choosing Configure Publishing Target.
    Tip: Alternatively, you can right-click on the Publications folder or the Subscriptions folder.

    When you run the wizard for the first time: The Specify Publishing Target page appears. Complete this step.

    When you run the wizard again: The Configure Publishing Target page appears. Skip to the next step.

    1. Choose the File Manager option.
    2. Click Next.

    The Configure Publishing Target page appears.

  2. Supply a restart file prefix.
    1. Enter the full path, starting with the root directory.
    2. Include the file prefix at the end of the path string.

      The restart file prefix is case sensitive.

  3. Specify a unit of time and a value for the commit interval.

    You can specify milliseconds, seconds, minutes, or hours. The default value is 30 minutes, and the maximum value is 24 hours.

  4. Click Finish to save your changes and close the wizard.

    If you want to change the publishing target or the settings, run the New Publishing Target wizard again.

  5. Run the New Publishing Map wizard by right clicking the Publishing Maps folder and choosing New Publishing Map.

    The Publishing Map Attributes page appears.

  6. Specify a name for your publishing map.
  7. Specify a change file prefix.

    The change file prefix is case sensitive.

  8. Choose a message file format for change messages.

    Choose XML, Delimited, or Raw. File Manager does not support XML with a Java™ Messaging Service (JMS) header, because that format is specific to WebSphere® MQ.

  9. Specify whether the map publishes messages for each row-level change or for each transaction.
  10. If you choose to publish messages for each transaction, specify in kilobytes the maximum size for a message related to this publishing map.

    An XML or Delimited message that is larger than the maximum size is split into two or more smaller messages.

  11. Optional: Enter a description of your publishing map.
  12. Click Finish to save your changes and close the wizard.

    To add another publishing map, run the New Publishing Map wizard again. To change the settings for your publishing map, right-click the publishing map in the Database Explorer and choose Update.

You must restart the data server or data servers that host the correlation service, distribution service, and publication service before your configuration changes take effect. You can view your settings in two locations:

  • Publishing target: on the Publishing Target tab in the Properties view for the database connection.
  • Publishing maps: on the General tab in the Properties view for the map.
Related concepts
XML messages for Classic event publishing
Related tasks
Specifying the WebSphere MQ objects to use for change capture
Creating and modifying publishing maps for Classic event publishing to WebSphere MQ
Creating and modifying publications
Related reference
Format of delimited messages


Feedback

Update icon Last updated: 2007-10-09