< Previous | Next >
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


Module 1: Configuring Classic Data Architect

In Classic Data Architect, you create or import are several components to enable your work.

Workspaces
The projects reside in a folder in your local file system. The folder is referred to as your workspace. Each user who works in Classic Data Architect has a workspace and projects within that workspace.
Data design projects
The type of project that you create in Classic Data Architect is called a data design project. You use the project to design the tables and views that you eventually will promote to the metadata catalog on the data server.
Physical data models
Within a project, you can create one or more models. Models are collections of schemas, which are collections of the tables and views that you create with Classic Data Architect. You can think of a repository of objects that you can promote to one or more metadata catalogs. Rather than create your tables directly in the metadata catalog on the data server and modify them there, you create and modify the tables in the model and then promote the tables to a metadata catalog.
For example, you might have one data server for a test environment and another for a production environment. In a model, you can create a table and then run the DDL to promote the table to the test data server to test it. If you need to modify the table, you can drop it from the metadata catalog in the test data server, modify the table in Classic Data Architect, then promote the table to the metadata catalog and test it again. When you have a version of the table that you want to put into production, you can promote the table to the production data server.
Data definitions
Unless you are using source data from DB2® for z/OS®, when you map source data to relational tables you must specify the structure of your source data and where that data is located. The method you use to specify this information depends on your data source:
For CA-Datacom, CA-IDMS, CICS® VSAM, IMS™, VSAM, and sequential data sources:
You import files of various types, depending on the DBMS in which your source data is located.
For Adabas databases:
You specify an Adabas file or Predict view. Classic Data Architect discovers the information that is required for mapping a table to the file.
Connections
You will need to connect to remote hosts to import data definitions from them and to run SQL DDL on a data server to create your tables, views, and stored procedures in a metadata catalog. you can perform other actions with a connection to a remote host, but they are outside the scope of this tutorial.

Learning objectives

After you complete the lessons in this module, you will be familiar with the Classic Data Architect objects and workspace and know how to do the following tasks:
This module should take approximately 20 minutes to complete.

Prerequisites

Lessons in this module



Feedback

Update icon Last updated: 2006-12-15


< Previous | Next >