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


Mapping tables for Classic event publishing

Use Classic Data Architect to create relational tables and views that map to data sources in supported non-relational database management systems. You use these tables and views as sources for your publications in IBM® WebSphere® Classic Data Event Publisher for z/OS®.

Before you begin

You must perform the following tasks on the data server where the correlation service will run:

About this task

You create the relational tables and views in a project in Classic Data Architect. Then, you promote these objects to a data server.

Procedure

To create tables and views that you can use as sources in Classic event publishing:

  1. Configure Classic Data Architect by creating prerequisite objects, creating connections to data servers, setting preferences, importing reference files, and granting privileges. See Configuring Classic Data Architect.
  2. Create tables and views that you can use as sources in publications. See Mapping data for change capture and Creating views on existing tables.
  3. Optional: Modify your tables or views. See Viewing and modifying objects for Classic event publishing.
  4. Generate and run DDL to promote your tables and views to a data server. See Generating DDL.
  5. Optional: If you choose not to run the DDL from Classic Data Architect but from the metadata utility, export the DDL to a remote z/OS host. See Exporting SQL to remote z/OS hosts.
  6. On the data server where you plan to run the correlation service, run the DDL that is in member CACREPSP in the SCACSAMP data set. This DDL creates the structures that store the definitions of the publishing maps and publications that you create.
    1. Use FTP to copy the DDL in a file with an SQL extension into the directory where your data design project is located. For example, if the name of your project is MyProject, the directory for the project might be (on Windows®) C:\workspace\MyProject.
    2. In Classic Data Architect, right-click the folder for the project that you copied the file into. Select Refresh. The SQL file appears in the SQL Scripts folder in the data design project that you selected.
    3. Right-click the SQL file and select Run.
    4. In the Connection Selection window, select the connection to the data server where you want to run the DDL and click Finish. You can create a new connection to a data server if a connection does not yet exist.
    5. Look in the Data Output view to verify that the DDL ran correctly.
  7. If you adopt WebSphere MQ as your publishing target: Specify a WebSphere MQ manager and a restart queue. See Specifying the WebSphere MQ objects to use for change capture.
  8. If you adopt File Manager as your publishing target: Specify a restart file prefix and a commit interval. See Configuring File Manager for Classic event publishing.
  9. Create at least one publishing map. Publishing maps specify send queues that you want to use for Classic event publishing. If you adopt WebSphere MQ as your publishing target, see Creating and modifying publishing maps for Classic event publishing to WebSphere MQ. If you adopt File Manager as your publishing target, see Configuring File Manager for Classic event publishing.
  10. Create at least one publication. See Creating and modifying publications
Related concepts
Introduction to Classic Data Architect
Populating metadata catalogs
Viewing and modifying objects
WebSphere MQ objects for change capture
Related tasks
Mapping tables for Classic federation
Mapping tables for Classic replication
Adding or replacing columns in tables based on data definition files
Related reference
Column properties
Table properties
View properties


Feedback

Update icon Last updated: 2007-10-09