adt config

Configuration Guide 2.1

Advantage Data Transformer

This documentation and related computer software program (hereinafter referred to as the Documentation) is for the end users informational purposes only and is subject to change or withdrawal by Computer Associates International, Inc. (CA) at any time.

This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies.

This right to print copies is limited to the period during which the license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the users responsibility to return to CA the reproduced copies or to certify to CA that same have been destroyed.

To the extent permitted by applicable law, CA provides this documentation as is without warranty of any kind, including without limitation, any implied warranties of merchantability, fitness for a particular purpose or noninfringement. In no event will CA be liable to the end user or any third party for any loss or damage, direct or indirect, from the use of this documentation, including without limitation, lost profits, business interruption, goodwill, or lost data, even if CA is expressly advised of such loss or damage.

The use of any product referenced in this documentation and this documentation is governed by the end users applicable license agreement.

The manufacturer of this documentation is Computer Associates International, Inc.

Provided with Restricted Rights as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.

2003 Computer Associates International, Inc. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Contents i

Contents Chapter 1: An Overview of Advantage Data Transformer Configuration 3

Overview of the Advantage Data Transformer Components..................................................................3 How the Advantage DT Server Works .......................................................................................................7

Chapter 2: Configuring the Server and Internal Database 9 Advantage Data Transformer Server Overview........................................................................................9

Preliminary Configuration Tasks .....................................................................................................9 Configuring Advantage Data Transformer ..............................................................................................10

Selecting a New Idb and a Server in the Idb .................................................................................11 Selecting the ODBC Data Source ....................................................................................................11 Selecting the ODBC Driver..............................................................................................................11

Chapter 3: Configuring the Client 19 Client Components ......................................................................................................................................19

Configuring the Script Manager .....................................................................................................19 Configuring the Mapper ..................................................................................................................20 Configuring the Normalizer............................................................................................................21 Configuring the Listener..................................................................................................................21 Configuring the Listener for Advantage Data Transformer Enterprise Metadata Edition ....21 Configure the Listener for Advantage Data Transformer...........................................................22 Configuring the Workflow Administrator ....................................................................................22 Configuring an Extra Data Source Name......................................................................................22

Chapter 4: Configuring the Target Agent 25 About the Target Agent...............................................................................................................................25

How the Target Agent Works .........................................................................................................26 Target Agent Requirements........................................................................................................................26

Where the Target Agent is Configured..........................................................................................27 Configuring the Target Agent on a UNIX Database Server...................................................................27

Copying and Extracting Target Agent Files..................................................................................28 Copying, Extracting, and Configuring Enterprise Communicator Files...................................28 Configuring the Target Agent for UNIX .......................................................................................30 Starting the Target Agent Daemon.................................................................................................35

Configuring the Target Agent on a Windows Database Server ...........................................................35 Installing Target Agent and Enterprise Communicator..............................................................36

ii Configuration Guide

Configuring the Target Agent for Windows.................................................................................36 Installing the Target Agent as a Windows Service.......................................................................39

Verifying the Target Agent Installation ....................................................................................................40

Chapter 5: Optional Configuration Activities 41 A Summary of Optional Configuration Activities ..................................................................................41 Configuring the Advantage Data Transformer Mapper for Use With Data Shopper ........................41 Configuring Mapper Programs to Use the Target Agent.......................................................................42

Troubleshooting................................................................................................................................44 SAP R/3 Setup..............................................................................................................................................44

Scan Metadata into the Advantage Repository ............................................................................46 Server Utility Tasks......................................................................................................................................46

The Utilities........................................................................................................................................47 Dumping an Idb ...........................................................................................................................................47

Running the Script Dump Utility ...................................................................................................47 Naming the Dump File ....................................................................................................................48 Contents of the Dump File...............................................................................................................48

Loading an Idb .............................................................................................................................................49 Restoring a Corrupted Idb...............................................................................................................49 What is Loaded .................................................................................................................................49 Running the Script Load Utility......................................................................................................50

Synchronizing Interfaces.............................................................................................................................51 Running the Script Interface Synchronizer ...................................................................................51

Configuring an Additional Oracle Idb......................................................................................................52 Defining Additional Users for an Idb........................................................................................................53 Using Microsoft Access for the Idb............................................................................................................55 Loading Standard System Transformations.............................................................................................56

Index 59

An Overview of Advantage Data Transformer Configuration 3

Chapter 1: An Overview of Advantage Data Transformer Configuration

This guide addresses configuration tasks that are required after Advantage Data Transformer is installed. The following chapters cover all major Advantage Data Transformer configuration tasks. The following is an overview of the information addressed in each chapter.

Configuring the Server and Internal Database - After the Advantage DT Server component is installed, perform the required configuration tasks to use the Advantage DT Server.

Configuring the Client - After the Advantage DT Server is installed, follow the tasks outline in this chapter to configure each client machine.

Configuring the Target Agent - If you have elected to use the Target Agent component for Oracle or DB2, then you must perform the tasks described in this chapter to configure the Target Agent.

Note: The Target Agent was automatically installed by default on any machines that have the Advantage DT Server components installed. The standalone Target Agent must be installed on any additional machines that do not have the server components installed, but which contain a target database server to be used with the Target Agent.

Important! The Target Agent must be enabled and configured before being used by Advantage Data Transformer to move data to the database.

Overview of the Advantage Data Transformer Components The following table contains a complete list of Advantage Data Transformer components. Some of these components require configuration.

Overview of the Advantage Data Transformer Components

4 Configuration Guide

Component Description Advantage DT Server Servers are used for data movement and consist of several sub

components and is started by invoking the Server icon in the task bar Start, Programs, Computer Associates, Advantage, Data Transformer. The Server icon invokes the infopump.exe. that can also be started from a command line.

When you start the Advantage DT Server, the following programs automatically run:

The local Server Console (ipcons.exe) The Scheduler (ipsched.exe) The Logger (iplogger.exe) which writes start and stop times for

requests and messages from executing requests to the System Log. For each request, meaning scripts or data transfers, the Advantage DT Server starts a session of the script interpreter (iprun.exe). Because the Advantage DT Server can execute multiple requests concurrently, multiple instances of the interpreter can be running at the same time.

Server Console The console is used to connect to the Advantage DT Server's scheduler interface. You can start or shut down the Advantage DT Server, manage requests, or view messages about request executions. The console can be started independently to connect to a Scheduler that is currently running.

In addition to the local console, you can install remote consoles to control a Advantage DT Server from other machines.

Scheduler The major component of the Advantage DT Server (ipsched.exe), which checks the execution queue in the Idb for requests, and initiates the script interpreter process to run the requests. When the scheduler starts, the logger (iplogger.exe) starts automatically, if it is not already running. The scheduler can be started directly by running ipsched.exe from a command line causing a Advantage DT Server session to run without a console, meaning that only ipsched.exe and iplogger.exe are running.



Component Description System Log A file (system.log) listing:

Start and stop times for requests Messages produced by executing requests The status of various Data Movement Services components

(processes) as they runfor example, the Scheduler and the script interpreter

Errors and messages produced by Enterprise Communicator as Advantage DT Server components work with it.

Internal Database (Idb) The Idb includes scripts, data transfers, code fragments, profiles, the execution queue, and various logs that can be viewed from the script manager.

The Idb is used to register servers and interfaces defined with Advantage Data Transformer.

You can define more then one Idb.

If you are using Advantage Data Transformer (not the Enterprise Metadata Edition), the Idb is also used to store the metadata used by the Advantage DT Mapper.

Interfaces Allow the Advantage DT Server to communicate with the source and target databases and files specified in requests.

An interface implements the following communication handlers: CONNECT, DISCONNECT, SEND, LOAD, STORE.

Script Dump Utility ipdump.exe is used to dump the contents of an Idb for backup or migration to a different Idb.

Script Load Utility ipload.exe is used to load a dump file, created by the Script Dump Utility, into an Idb.

Script Interface Synchronizer

ipsync.exe is used to define licensed database interfaces into an Idb.

Target Agent (Optional) A database utility that performs rapid, bulk loading of data into a target database table. This component is optional and is available only for the Oracle and DB2 interfaces.

Script Manager Controls and administers the Internal Database (Idb). The Script Manager also provides a development environment for creating and modifying data movement requests and allows the monitoring of logs for data movement.



Component Description Mapper The main component of Advantage Data Transformer and Advantage

Data Transformer Enterprise Metadata Edition and is used to access metadata and define programs for script generation and execution by the Advantage DT Server.

Listener Runs as a Windows service and tracks information about script modifications in the manager and script execution by the Advantage DT Server. This information is relayed by the Listener to the metadata store for access by the Mapper

Normalizer (Optional) An application used in conjunction with the Mapper that puts COBOL copybook data, which has been scanned into a repository, into a relational-like table format for use in Mapper programs. This component is only available with the Advantage Data Transformer Enterprise Metadata Edition.

SAP R/3 Interface Setup (Optional)

The SAP R/3 Interface Setup is used to define ABAP information into a SAP R/3 system for use by the Mapper and SAP R/3 database interface. This component is only available with the Advantage Data Transformer Enterprise Metadata Edition.

SAP R/3 Installation Verification (Optional)

The SAP R/3 Installation Verification is used to confirm that the Interface Setup has successfully put the right information into the SAP R/3 system. This component is only available with the Advantage Data Transformer Enterprise Metadata Edition.

How the Advantage DT Server Works


How the Advantage DT Server Works The following graphic shows how the Advantage DT Server works with other Advantage DT components to execute data movement requests:

Configuring the Server and Internal Database 9

Chapter 2: Configuring the Server and Internal Database

The Advantage DT Server component must be properly configured before use. Follow the tasks outlined in this chapter to configure the Advantage DT Server and internal database (Idb). Optional tasks to configure the Script Manager and Listener are also covered.

Advantage Data Transformer Server Overview The Advantage DT Server is the main data movement component for Advantage DT and can execute multiple requests simultaneously. For each executed request, the Advantage DT Server logs start and stop times, errors, messages, and the results of the request execution, such as tables or rows that are created, modified, or deleted in the target databases.

You can configure the Advantage DT to have more than one server, each on a different machine.

Preliminary Configuration Tasks

Before you configure the Advantage DT Server and the Idb, you must create a database to store the Idb. This database contains all the structures required for the Idb. The procedure for creating the database depends upon your choice of RDBMS to be used for the Idb. You may use Microsoft SQL Server, Sybase, Oracle, DB2, Advantage Ingres, or Microsoft Access for the Idb database. Sample files and instructions for each database type, except Microsoft Access, can be found in the Advantage DT installation folder idbsetup. By default the location is c:\Program Files\CA\Advantage Data Transformer\idbsetup directory.

Note: No setup instructions are supplied for creating a Microsoft Access database because an empty database is provided with Advantage DT. Also, it is not necessary to have Microsoft Access installed on the machine.

The following is an overview of the basic configuration tasks required to create a database in which to place the Idb:

Create a user ID called infopump, which is required, and groups (or roles) for users and administrators.

Create the Idb database.

Create an ODBC system data source to access the Idb.

Configuring Advantage Data Transformer


Note: The creation of the ODBC system data source can be postponed and performed during Advantage DT Server configuration. The Advantage DT Sever configuration launches the appropriate dialogs to create a new data source, or allows you to select a pre-existing ODBC data source. If you plan on using an existing data source, ensure it is created using the required drivers and parameters as noted in the following configuration tasks.

You must use the Advantage DT Server configuration to register the ODBC DSN to the registry. If the ODBC DSN is renamed, you must run the configuration utility to register the new name.

Configuring Advantage Data Transformer To configure Advantage Data Transformer, perform these steps:

1. From the Start menu, choose Programs, Computer Associates, Advantage, Data Transformer, and click the Configuration icon.

The Advantage Data Transformer Server Configuration dialog displays.

2. To configure the Advantage DT Server component, check the Server check

box.

Note: Checking the An extra data source name check box allows you to create additional client data sources after initial configuration. Do not select the An extra data source name check box during a Server configuration process.

3. Check the Script Manager box.



The Script Manager runs on the machine where the Advantage DT Server is installed. Typically, a Script Manager is installed on the server machine, as well as client machines.

4. Optionally check the Target Agent or Listener check boxes.

These are optional components and the Target Agent only needs to be configured if it will run on this machine.

Note: If you do not select to install and configure the Script Manager, the Target Agent, and Listener components now, you can configure these optional components at any time.

5. Click Next to display the Advantage Data Transformer Server Configuration dialog.

6. Click Next to display the New Installation screen.

Selecting a New Idb and a Server in the Idb 1. Select Both a new Idb and a server in the Idb in the New Installation screen.

2. Click Next.

Note: The option labeled A new server into an existing Idb is used if you want to install an additional server into an existing Idb.

Selecting the ODBC Data Source

In the next dialog, select the ODBC data source.

1. Select Add new data source, or, if you wish to use a pre-existing data source, select that data source now.

Be sure it adheres to the requirements noted below.

2. Click Next.

Selecting the ODBC Driver

In the Add Data Source dialog,

1. Select the appropriate ODBC driver for the database type.

2. Click Next.

The Add Data Source dialog displays.

To configure a specific ODBC system data source, proceed to the appropriate section:

Configure an Oracle data source



Configure a Microsoft SQL Server data source

Configure a Sybase data source

Configure a Microsoft Access data source

Configure an Advantage Ingres data source

Configure a DB2 data source

Once an ODBC data source has been configured for your specific database driver, proceed to the section Select or Verify the Server Name.

Configuring an Oracle Data Source

To configure an Oracle data source, follow these steps:

1. Enter the Data Source Name appropriate for your site then click Next.

The default data source name is Idb.

2. Select the General tab, then enter the name of the appropriate Oracle server in the Server Name field.

This is the Oracle alias defined in the tnsnames.ora file used to connect to the Oracle server containing the Idb database. The data source name you defined in the previous step is automatically entered in the Data Source Name field.

3. In the Advanced Tab, accept the default values, as no changes should be made, then click OK.

4. Enter the name of the schema that contains the Idb, then click Next.

5. Enter the names of the Idb tablespace and index tablespace.

These names were chosen by your database administrator during setup of the Idb database.

6. Click Next.

7. Enter the schema's password to log into the new data source, then click Next.

Configuring a Microsoft SQL Server Data Source

To configure a Microsoft SQL Server data source, follow these steps:

1. Enter the Data Source Name appropriate for your site and click Next.


2. From the drop-down list select the SQL Server where the Idb is located. The data source name you defined in the previous step is automatically entered in the Data Source Name field.

3. Click Next.

4. Select With SQL Server authentication using a login ID and password entered by the user.



5. Enter the infopump user ID and password as defined by your database administrator during creation of the empty Idb database.

6. Click Next.

7. Change the default database to the name of the Idb database established by your database administrator.

8. Clear the Use ANSI, nulls, paddings, and warnings check box. Do not select any other options.

WARNING: If you do not clear the Use ANSI nulls, paddings, and warnings check box, an unusable Idb is created.

9. Click Next.

10. Accept the default values and click Finish.

11. To verify the connection to the Idb, click the Test Data Source button.

12. Click OK.

13. Enter the password to log into the new data source, then click Next.

Configuring a Sybase Data Source

To configure a Sybase data source, follow these steps:

1. Enter the Data Source Name appropriate for your site, then click Next.


2. Select the General tab. The data source name defined in the previous step is automatically entered in the Data Source Name field.

3. Enter the name of the Sybase server in the Server Name field.

4. Enter the name of the empty Idb database created by your database administrator in the Database Name field.

5. Select the Performance tab and set the parameters to the following:

Set the Prepare Method field to 2 Full.

Set the Fetch Array Size field to 50.

Set the Select Method field to 1 Direct.

Set the Packet Size field to 0.

Set the Connection Cache to 1.

6. Accepted the default values on the other tabs, as nothing should be changed.

7. Click OK.

8. Enter the password to log into the new data source.

9. Click Next.



Configuring a Microsoft Access Data Source

To configure a Microsoft Access data source, follow these steps:

1. In the Data Source Name field, enter the appropriate name for your site, then click Next.


2. The data source name defined in the previous step is automatically entered in the Data Source Name field.

3. Click Select to locate the Access Idb database.

By default the location is c:\Program Files\CA\Advantage Data Transformer\bin directory.

4. Select the Database Name Idb.mdb, which is the empty Access Idb installed with Advantage Data Transformer.

Note: Do not choose EmptyIdb.mdb. This is a template for an empty Idb that can be copied to reset the Idb.mdb back to its original empty state.

5. Click OK to exit the Select Database dialog.

6. Click OK to exit the ODBC Microsoft Access Setup dialog.

7. In the Data directory field on the Data Directory for Microsoft Access dialog, enter the full path of your Advantage DT installation with data appended to it.

For example, c:\Program Files\CA\Advantage Data Transformer\bin\data

Or

You can use the Browse button, which selects the c:\Program Files\CA\Advantage Data Transformer\bin directory. This alternative method displays the Set Access Data Directory dialog.

In the Set Access Data Directory dialog:

a. Enter the file name data, then click Open.

b. Click Yes to create the file name, and return to the Data Directory for Microsoft Access dialogue.

The Data Directory for Microsoft Access dialog then displays with the appropriate location defined.

8. Click Next to proceed from the Data Directory for Microsoft Access to the ODBC Login dialog.

9. Click Next in the ODBC Login dialog.

Note: No password is needed for logging into the Access data source.



Configuring an Advantage Ingres Data Source

To configure an Advantage Ingres data source, follow these steps:

1. Enter the Data Source Name appropriate for your site and click Next.


2. In the Ingres ODBC Administrator dialog, select the Data Source tab. The Data Source Name field is automatically set to the name you entered in the previous step.

3. In the Server group box:

a. Select the appropriate Vnode from the Vnode drop-down list.

b. Select INGRES from the Type drop-down list.

c. Select your database from the Database drop-down list.

4. In the Connect Options section, select the Prompt User ID and Password To Override VNODE Login check box, then click OK.

5. In the Ingres Schema dialog, enter infopump, then click Next.

6. In the ODBC Login dialog, enter the password to access the new data source, then click Next.

Configuring a DB2 Data Source

To configure a DB2 data source, follow these steps:

1. Enter the Data Source Name appropriate for your site, then click Next.


2. Enter the data source name from the previous step, then select the database alias for the Idb.

3. Click OK.

4. Enter the password to log into the new data source, then click Next.

Note: Before attempting to use a DB2 Idb, the ODBC data source must be modified. See the section Additional Modifications for a DB2 ODBC Data Source.

Additional Modification for a DB2 ODBC Data Source

Before attempting to use a DB2 Idb, the ODBC data source must be modified.

In the Windows ODBC Data Source Administrator, follow these steps:

1. Select the DB2 Data source that was created during installation found under the System DSN tab.

2. Click the Configure button.



3. When prompted to connect to the data source, enter infopump as the user ID, then click the Advanced button.

4. Select the Data Type tab, then select the Long object binary treatment parameter.

5. Select the As LONGVAR data radio button, then click OK to accept the change.

6. To exit the CLI/ODBC Settings dialog, click OK.

Note: This setting is required to handle large scripts in the Idb.

Selecting or Verifying the Server Name

Once you have created your Idb database ODBC data source, the Advantage Data Transformer Server dialog displays. The Advantage DT Server name is automatically set to the name of the ODBC data source with _Server appended.

To keep the default name, click Next.

To change the name, enter a different name, and then click Next.

Loading an Idb from a Dump File

The Load Idb from Dump File dialog displays. Loading an Idb from a dump file created from a different Idb is optional.

Note: If this is a new installation, an Idb dump file may not exist.

To skip this step, do not check the Load Idb now check box. Click Next.

To load an Idb from a dump file, check the Load Idb now check box and click the Browse button to locate the appropriate dump file. Click Next.

Installing the Server as a Windows Service

The Install the Server as a Windows Service dialog displays. Installing the Advantage DT Server as a Windows Service is optional.

To skip this step, do not check the Configure Data Transformer as a Windows Service check box, then click Next.

To install the Advantage DT Server as a Windows service, follow these steps:

1. Select the Configure Data Transformer as a Windows Service check box.

2. Select a Startup Type for the Windows service.

The default type is automatic.

3. Enter a user ID and password that has Log on as service as part of the operating system security policy.



4. Click Next, then click Yes to confirm the new service name or No to modify the service name.

5. From the Windows Service Startup Parameters dialog, enter the appropriate restart parameters or accept the defaults. For additional information, see the chapter "Using the Server Console" in the Server User Guide.

6. Click Next.

Viewing Registration Output

A summary of your configuration choices displays, followed by notification that the database interfaces you have purchased are being registered. When the Output from Registering the Interfaces displays, review the output and click Close.

Configuring the Script Manager

If this is a new installation, the Script Manager should be configured. Follow the steps below to configure the Script Manager.

1. If you checked the Script Manager box in the initial Advantage Data Transformer Server Configuration dialog, the Advantage DT Script Manager Configuration dialog displays.

2. Click Next.

The ODBC data source created during Advantage DT Server configuration is used for the script manager. However, if you did not configure the Advantage DT Server during this configuration session, a dialog displays requiring you to select or create a data source.

3. Select a data source or create a data source.

4. Click Next.

Configuring the Target Agent (Optional)

The Target Agent must run on the machine where the target DBMS (Oracle or DB2) is located. If the Advantage DT Server is located on the same machine as the target DBMS, the Configuration utility can be used to set up the Target Agent as a Windows service.

If you checked the Target Agent check box in the initial Advantage Data Transformer Server Configuration dialog, a dialog displays to allow you to set up the Target Agent as a Windows service. The service name and path location for the Target Agent executable (tgtdaem.exe) will be automatically entered in the appropriate fields in the dialog.

1. Click the Set up Target Agent as a service button.

2. Click Next to proceed to the Summary dialog.



Configuring the Listener (Optional)

If you choose to use the Listener service, you should configure the Listener on every machine that is running an Advantage DT Server. Also, you should configure the Listener on client machines running the Advantage DT Mapper and Script Manager components.

Note: A Listener can only be configured to communicate with one repository.

Configuring the Listener for Advantage Data Transformer Enterprise Metadata Edition

To configure the Listener for Advantage Data Transformer Enterprise Metadata Edition, follow these steps:

1. If you are using the Advantage Data Transformer Enterprise Metadata Edition product, the Advantage Data Transformer Listener Setup dialog displays.

2. Select the name of the repository that the Listener will connect to the Select Metadata Store field.

The Select Metadata Store list displays the Advantage Repository connections that were defined through the Repository/OEE Configuration Facility, which is part of the Advantage Repository for Distributed Systems. One or more repository connections was defined when the Advantage Repository product was installed.

3. Enter the login name and password used to connect to the repository.

4. Click Next.

Configuring the Listener for Advantage Data Transformer

To configure the Listener for Advantage DT, follow these steps:

1. If you are using the Advantage DT product, the Advantage Data Transformer Listener Setup dialog displays.

2. The Select Metadata Store default for Advantage DT is Internal Metadata Store because the Idb is used as the metadata store.

3. From the Select Metadata Store drop-down list, select Internal Metadata Store.

4. From the Specify the IDB DSN drop-down list, select the ODBC data source name used to connect to the Idb.

5. Enter the login name and password used to connect to the Idb, then click Next.

Configuring the Client 19

Chapter 3: Configuring the Client You can install and configure Advantage DT client machines separately from machines where servers are installed. To do this, install and configure client components, such as the Mapper and the Script Manager, on a Windows server or workstation.

Client Components The following table lists the available client components for both the Advantage Data Transformer product and the Advantage Data Transformer Enterprise Metadata Edition. These components can be configured on client machines.

Advantage Data Transformer Advantage Data Transformer Enterprise Metadata Edition Mapper Mapper

Script Manager Script Manager

Listener Listener

Workflow Administrator Workflow Administrator

Workflow Executor Workflow Executor

Script Runner Script Runner

Server Console (For remote console access to the Server to perform data movement)

Server Console (For remote console access to the Server to perform data movement)

Target Agent Target Agent

Normalizer

SAP

Configuring the Script Manager

To configure the Script Manager, follow these steps:

1. Choose Start, Programs, Computer Associates, Advantage, Data Transformer, then click Configuration.

2. Click the Script Manager box, the click Next.

The Advantage Data Transformer Script Manager Configuration dialog displays.

3. Select the appropriate file, then click Next.

Client Components


4. Either select Add new data source or select an existing data source, then click Next.

If adding a new data source, Advantage DT lists only the supported ODBC data source types for the Idb you are using, for example, Oracle, Microsoft SQL Server, Sybase, Microsoft Access, Advantage Ingres, or DB2. For more information, see the section Select the ODBC Data Source in the chapter Configure the Server and Internal Database.

Important! The ODBC data source name used by the Mapper and Script Manager must have the same name on each machine that will be communicating to a common Idb. This is required for the Listener to correctly track Script Manager changes to program scripts or server script execution information in the metadata store. We recommend that all client machines use the ODBC data source name that was specified during server installation.

When the data source selection and configuration is complete, the ODBC Login dialog displays.

5. Enter the password to log into the data source, then click Next.

6. Click Finish when the Summary window displays.

The following message is displayed:

Operation completed successfully

Configuring the Mapper

The Mapper is not configured using the Configuration icon on the Advantage Data Transformer menu.

Important! If you are using Advantage Data Transformer Enterprise Metadata Edition, the Advantage Repository client components must have been installed and a Repository connection alias must have been defined using the Repository Configuration Facility. This alias is required for the Mapper to successfully connect to an Advantage Repository. If you are not using the Advantage Data Transformer Enterprise Metadata Edition, the Mapper uses the ODBC data source defined for the Script Manager to connect to the Idb. The Mapper also requires that the database client software for the IDB or Repository is installed before a connection can be made to the Advantage Repository. In addition, if you are using the Advantage Data Transformer Enterprise Metadata Edition, the Advantage Repository Security Manager must be used to grant the DecisionBase User right to each user ID that will be used by Mapper users.

Client Components


Configuring the Normalizer

The Normalizer is not configured using the Configuration icon on the Advantage Data Transformer menu. However, the Advantage Repository client components must have been installed and a Repository connection alias must have been defined using the Repository Configuration Facility. This alias is required for the Normalizer to successfully connect to an Advantage Repository.

Configuring the Listener

If the Listener service has been configured for use on other machines, then the Listener should be configured on every client machine running the Mapper and Script Manager components. Follow these steps to configure the Listener for either Advantage Data Transformer or Advantage Data Transformer Enterprise Metadata Edition.

Note: A Listener can only be configured to communicate with one metadata store.

To configure the Listener, follow these steps:

1. From the Start menu, choose Programs, Computer Associates, Advantage, Data Transformer, then click Configuration.

2. Click the Listener box, then click Next.

To continue, proceed to the section that is most appropriate for your site, which is dependent upon whether you are using Advantage Data Transformer or Advantage Data Transformer Enterprise Metadata Edition.

Configuring the Listener for Advantage Data Transformer Enterprise Metadata Edition

To configure the Listener for Advantage Data Transformer Enterprise Metadata Edition, follow these steps:

1. If you are using the Advantage Data Transformer Enterprise Metadata Edition product, the Advantage Data Transformer Listener Setup dialog displays.

2. Select the name of the repository that the Listener will connect to the Select Metadata Store field.

The Select Metadata Store list displays the Advantage Repository connections that were defined through the Repository/OEE Configuration Facility, which is part of the Advantage Repository for Distributed Systems. One or more repository connections was defined when the Advantage Repository product was installed.

Client Components


3. Enter the login name and password used to connect to the repository.

4. Click Next.

Configure the Listener for Advantage Data Transformer

To configure the Listener for Advantage Data Transformer, follow these steps:

1. If you are using the Advantage Data Transformer product, The Advantage Data Transformer Listener Setup dialog displays.

2. From the Select Metadata Store drop-down list, select Internal Metadata Store list.

3. Select the Idb from the Specify the IDB DSN, which contains the ODBC data source name used to connect to the Idb.

4. Enter the login name and password used to connect to the Idb, then click Next.

Configuring the Workflow Administrator

The Workflow Administrator configures the Advantage DT Program Types that will be scanned into a metadata store for use in Workflow applications.

We recommend that you dedicate a single machine to Workflow administration tasks to ensure that Program Type configuration, reconfiguration, and scanning into the metadata store are consistent. If Workflow administration tasks are performed from more than one machine, inconsistent Workflow configurations can be scanned into the metadata store and overwrite valid Workflow configurations.

Configuring an Extra Data Source Name

In addition to the ODBC data source configuration that is performed during Script Manager configuration, you may need to configure additional ODBC data sources on a client machine. For example, if you have more than one Idb that the Script Manager or Mapper is using, you will need to define additional data sources.

Important! To create additional data sources on a client machine, you must use the Advantage Data Transformer Configuration utility, rather than another facility, such as the Windows ODBC Data Source Administrator. This must be done to ensure that the appropriate Advantage Data Transformer registry entries are set up during the creation of the data source.

Client Components


To create an additional data source, follow these steps:

1. From the Start menu, choose Programs, Computer Associates, Advantage, Data Transformer, then click Configuration.

2. Check the An extra data source name check box.

3. Click Next, then select the appropriate driver.

When adding a new data source, only the supported ODBC data source types are listed. For details about how to configure the particular data source, see the section Select the ODBC Data Source in the chapter Configure the Server and Internal Database.

Important! The ODBC data source name used by the Mapper and Script Manager must have the same name on each machine that will be communicating to a common Idb. This is required for the Listener to correctly track server or Script Manager changes to program scripts in the metadata store. We recommend that all client machines use the ODBC data source name that was specified during Advantage DT Server installation.

Configuring the Target Agent 25

Chapter 4: Configuring the Target Agent If you elect to use the optional Target Agent component for fast bulk loading of data to Oracle or DB2, then you must perform the tasks described in this chapter. The Target Agent component must be installed and configured on each Oracle or DB2 server machine. The Target Agent can only be used for the fast inserting of data into the target database and not does not support updates or deletes of target data. The configuration is the same for both Advantage Data Transformer and Advantage Data Transformer Enterprise Metadata Edition.

Important! The Target Agent must be enabled and configured before Advantage Data Transformer can use it to move data to the database.

About the Target Agent The Target Agent accepts data retrieved from source databases by Advantage Data Transformer components and performs a rapid load of that data into a database table. The Target Agent uses the Computer Associates Enterprise Communicator (PEC) to communicate with other Advantage Data Transformer components.

The Target Agent must be enabled and configured before Advantage Data Transformer can move data to the database. For more information about enabling the Target Agent, see the section Configuring Mapper Programs to Use the Target Agent in the chapter Optional Configuration Activities.

The following four components comprise the Advantage Data Transformer Target Agent:

Enterprise Communicator RT Server - Establishes a connection between the Advantage DT Server script interpreter process, and the Target Agent Daemon.

Target Agent Daemon (tgtdaem executable) - An agent that runs on the target database server that communicates with the Advantage DT Server. This invokes the appropriate Target Agent database client component to perform data movement.

Target Agent Database Client - An application invoked by the Target Agent Daemon to perform data movement at the request of the Advantage DT Server. The Target Agent database client (oraclient executable for Oracle and db2client executable for DB2) accepts data from the Advantage DT Server script interpreter, processes the data, and then passes it to the Oracle or DB2 fast load utility.

Target Agent Requirements


RDBMS Load Utility - The database facility provided by the RDBMS vendor to perform a fast load into the target database. Oracle's load utility is SQLLDR executable and DB2's load utility is the Load command.

How the Target Agent Works

The following is the basic process of how the Target Agent loads data into a database.

1. The Advantage Data Transformer Script Manager or a Workflow schedules a script to be executed by the Advantage DT Server.

2. The Server script interpreter retrieves data from the source database.

3. The Server script interpreter uses Enterprise Communicator to connect to and pass the retrieved data to the Target Agent.

4. The Target Agent passes the retrieved data to the RDBMS load utility that loads the data into the target table.

Target Agent Requirements The following components must be in place before running scripts that use the Target Agent:

Server Required Components Machine where Advantage DT Server resides Connectivity to the Idb and source and

target databases

Advantage DT Server Enterprise Communicator

Machine where the Oracle or DB2 database resides. This may be a remote machine or the same machine where the Advantage DT Server resides, if the Advantage DT Server is run on the same machine as the target Oracle or DB2 database.

Target Agent Enterprise Communicator Target database (Oracle or DB2) RDBMS load utility (Oracle SQLLDR or DB2

Load)

Configuring the Target Agent on a UNIX Database Server


Where the Target Agent is Configured

Place the Target Agent on each Oracle or DB2 target database server for which the Target Agent fast bulk loading capability is desired.

For a local server:

During installation, if the target database server is running on the same Windows machine where the Advantage DT Server is run, select the Target Agent component along with the Advantage DT Server components. If there is no target Oracle or DB2 database on the machine where the Advantage DT Server is located, it is not necessary to select the Target Agent component on that machine.

For a remote target database:

The Target Agent component must be placed on each remote Windows or UNIX database server to which you will be moving data. The Target Agent can load data into Oracle or DB2 tables on the following platforms:

AIX

HP-UX

Sun Solaris

Microsoft Windows

Note: Multi-node DB2 EEE versions are not supported due to an IBM API limitation.

Configuring the Target Agent on a UNIX Database Server On the Advantage Data Transformer CD there is a folder named TargetAgent_UNIX that contains all the required files for the UNIX platforms. This folder contains two types of files:

The following compressed Enterprise Communicator UNIX tar files:

Platform Compressed Enterprise Communicator Tar File HP-UX pec100_hp700_hpux_tar.Z (for HP-UX 10 versions)

pec110_hp700_hpux11.tar.Z (for HP-UX 11 versions)

Sun Solaris pec25_sun4_solaris_tar.Z

AIX pec41_rs6000_aix_tar.Z



The following Target Agent UNIX tar files:

Platform Target Agent Tar File HP-UX adt21_ta_hp7us5.tar

Sun Solaris adt21_ta_su4us5.tar

AIX adt21_ta_rs4us5.tar

Copying and Extracting Target Agent Files

To place the Target Agent on a remote UNIX database server, follow these steps:

1. On the UNIX machine, create a new directory under the home directory of the user ID that will be used for the Target Agent component.

For example the directory could be named //CA/AdvantageDataTransformer/targetagent

2. In binary mode, use FTP or other means to copy the appropriate platform-specific Enterprise Communicator compressed tar file from the Advantage Data Transformer CD TargetAgent_UNIX directory to the directory you created in step 1.

The platform-specific tar files are:

Platform Target Agent Tar File HP-UX adt21_ta_hp7us5.tar

Sun Solaris adt21_ta_su4us5.tar

AIX adt21_ta_rs4us5.tar

3. Extract the Target Agent files from the tar file by using the following xvf parameter of the tar command: tar -xvf tarfilename.tar

Copying, Extracting, and Configuring Enterprise Communicator Files

To place the Enterprise Communicator on a remote UNIX database server, follow these steps:

1. On the UNIX machine, create a new subdirectory named pec below the directory you created for the Target Agent files.



2. In binary mode, use FTP or other means to copy the appropriate platform-specific Enterprise Communicator compressed tar file from the Advantage Data Transformer CD TargetAgent_UNIX directory to the pec directory on the UNIX machine where the remote database server is located.

Platform Compressed Enterprise Communicator Tar File HP-UX pec100_hp700_hpux_tar.Z (for HP-UX 10 versions)

pec110_hp700_hpux11.tar.Z (for HP-UX 11 versions)

Sun Solaris pec25_sun4_solaris.tar.Z

AIX pec41_rs6000_aix.tar.Z

3. From the pec directory, enter the following command to uncompress the Enterprise Communicator tar file: uncompress tarfilename.tar.Z

Uncompressing the file produces a tar file with the same name as the compressed file, but removes the .Z extension.

4. Extract the Enterprise Communicator file from the tar file by using the following xvf parameter of the tar command: tar -xvf tarfilename.tar

where tarfilename.tar is the name of the tar file produced from the uncompress step.

This creates the Enterprise Communicator directory tree in the pec directory.

5. Within the pec directory, locate the bin directory, then locate the rtinit shell script files:

rtinit.sh for Korn shell

rtinit.csh for C shell

6. Edit the file that is appropriate for your environment as follows:

For the rtinit.sh file, locate the following lines: # Must do this first! RTHOME=/home/rtworks

Change the path value for RTHOME to the appropriate pec directory path value. For example, //CA/AdvantageDataTransformer/targetagent/pec.

For the rtinit.csh file, locate the following lines: # Must do this first! setenv RTHOME /home/rtworks



Change the path value for RTHOME to the appropriate pec directory path value. For example, //CA/AdvantageDataTransformer/targetagent/pec.

7. For the user ID running the Target Agent, the user profile can either be set up to automatically execute the rtinit shell script when you log on or the script can be run manually.

If the shell script is executed automatically through the user profile, ensure to include the full Target Agent pec/bin path to locate the rtinit.sh or rtinit.csh shell script.

To manually execute the shell script, perform the following:

a. From the pec/bin directory, located under the Target Agent directory, enter the following:

. ./rtinit.sh for Korn shell

source ./rtinit.csh for C shell

The automatic or manual execution of the rtinit shell script establishes the Enterprise Communicator $RHOME in preparation for the Target Agent to utilize Enterprise Communicator.

8. Under the pec directory, locate the standard directory, then add the following line to the rtclient.cm file: setopt server_name tcp:rtserver_machine_name

where rtserver_machine_name is the IP address or name of the machine that will be running Enterprise Communicator Rtserver. Typically the Rtserver runs on the Windows machine where the Advantage DT Server is running. Therefore, the Target Agent and Enterprise Communicator components installed on a remote UNIX database machine would be communicating to an Rtserver and Advantage DT Server on a Windows machine.

Important! The Target Agent and Advantage DT Server must communicate with the same Enterprise Communicator Rtserver.

Configuring the Target Agent for UNIX

Next, the Target Agent must be configured to communicate with Advantage DT and the Oracle and/or DB2 server. Set the appropriate environment variables for path, library path, and other RDBMS-specific variables in the dbewhse.cm file regardless of whether you might also have the variables set externally. This file is located in the UNIX Target Agent directory.

The dbewhse.cm is as follows:

setopt ORCL "oraclient"



/*setopt ORCL_env "ORACLE_HOME=< >*ORACLE_SID=< >*=$ORACLE_HOME/lib:/usr/lib:$RTHOME/lib/*PATH=$ORACLE_HOME/bin:$RTHOME/bin:/usr/bin:."*/

/* Sample for Solaris (modify RTHOME in rtinit.sh/rtinit.csh to point to the installed PEC location and run . rtinit.sh/source rtinit.csh) */

/*setopt ORCL_env "ORACLE_HOME=/usr/vendor/oracle/8.1.7*ORACLE_SID=SU81*LD_LIBRARY_PATH=$ORACLE_HOME/lib:/usr/lib:$RTHOME/lib/sun4_solaris*PATH=$ORACLE_HOME/bin:$RTHOME/bin:/usr/bin:."*/

/* Sample for AIX (modify RTHOME in rtinit.sh/rtinit.csh to point to the installed PEC location and run . rtinit.sh/source rtinit.csh) */

/*setopt ORCL_env "ORACLE_HOME=/usr/vendor/oracle/9i/9.0.1*ORACLE_SID=AIX90*LIBPATH=$ORACLE_HOME/lib32:/usr/lib:$RTHOME/lib/rs6000_aix*PATH=$ORACLE_HOME/bin:$RTHOME/bin:/usr/bin:."*/

/* Sample for HP-UX (modify RTHOME in rtinit.sh/rtinit.csh to point to the installed PEC location and run . rtinit.sh/source rtinit.csh) */

/*setopt ORCL_env "ORACLE_HOME=/usr/vendor/oracle/9i/9.0.1*ORACLE_SID=HP90*SHLIB_PATH=$ORACLE_HOME/lib32:/usr/lib:$RTHOME/lib/hp700_hpux11*PATH=$ORACLE_HOME/bin:$RTHOME/bin:/usr/bin:."*/

setopt DB2 "db2client"

/*setopt DB2_env "DB2HOME=< >*DB2INSTANCE=< >*=$DB2HOME/sqllib/lib:/usr/lib:$RTHOME/lib/*PATH=$DB2HOME/sqllib/bin:$RTHOME/bin:/usr/bin:."*/

/* Sample for Solaris (modify RTHOME in rtinit.sh/rtinit.csh to point to the installed PEC location and run . rtinit.sh/source rtinit.csh) */

/*setopt DB2_env "DB2HOME=/usr/vendor/db2/db271*DB2INSTANCE=db271*LD_LIBRARY_PATH=$DB2HOME/sqllib/lib:/usr/lib:$RTHOME/lib/sun4_solaris*PATH=$DB2HOME/sqllib/bin:$RTHOME/bin:/usr/bin:."*/

/* Sample for AIX (modify RTHOME in rtinit.sh/rtinit.csh to point to the installed PEC location and run . rtinit.sh/source rtinit.csh) */

/*setopt DB2_env "DB2HOME=/usr/vendor/db2/db271*DB2INSTANCE=db271*LIBPATH=$DB2HOME/sqllib/lib:/usr/lib:$RTHOME/lib/rs6000_aix*PATH=$DB2HOME/sqllib/bin:$RTHOME/bin:/usr/bin:."*/

/* Sample for HP-UX (modify RTHOME in rtinit.sh/rtinit.csh to point to the installed PEC location and run . rtinit.sh/source rtinit.csh) */

/*setopt DB2_env "DB2HOME=/usr/vendor/db2/db272*DB2INSTANCE=db272*SHLIB_PATH=$DB2HOME/sqllib/lib:/usr/lib:$RTHOME/lib/hp700_hpux11*PATH=$DB2HOME/sqllib/bin:$RTHOME/bin:/usr/bin:."*/

setopt PING "db2client"

setopt debug No



To modify the dbewhse.cm to establish environment information internally within the file:

1. Log on to the UNIX server where the Target Agent remote component is installed.

2. Using the text editor of your choice, open the dbewhse.cm file on that machine and make the changes outlined in the section called Oracle on UNIX Considerations or the section called DB2 UDB on UNIX Considerations.

Changes can be made by un-commenting the appropriate setopt line, and then editing it.

3. Save dbewhse.cm and exit the editor.

Oracle on UNIX Considerations

The dbewhse.cm file provided for UNIX systems supplies the following setopt commands for defining environmental information for use with an Oracle target database:

setopt ORCL "oraclient" ORCL is the target name. This name can be changed here and in the other setopt parameters, however, it must correspond to the name used in the #TARGET parameter in the STORE statement of the Target Agent script for data movement. Do not change the oraclient name.

setopt ORCL_env "Oracle environment variables" Specify the Oracle environment variables. These variables include ORACLE_HOME, ORACLE_SID, PATH, and library path.

For the setopt ORCL_env "Oracle environment variables", perform the following steps:

1. Remove the starting and ending comment characters /* and */ from the setopt ORCL_env line and specify the appropriate values for the ORACLE_HOME and ORACLE_SID by replacing the < > placeholders with the values.

2. Substitute the appropriate library path environment variable name for the parameter. Library path environment variable name varies by UNIX platform AIX uses LIBPATH, Solaris uses LD_LIBRARY_PATH, HP-UX uses SHLIB_PATH.

3. Substitute the appropriate Enterprise Communicator lib name for the parameter AIX uses rs600_aix, Solaris uses sun4_solaris, HP-UX 10 uses hp700_hpux, HP-UX 11 uses hp700_hpux11.

4. Be sure to remove the < > placeholder brackets when you are setting the above values. Do not change the names or order of any of these environment variables. The * between each of the variables must remain. The entire string following the setopt ORCL_env must be in double quotes.



Note: The setopt ORCL name used in the dbewhse.cm can be any appropriate name and does not have to be a name of an Oracle instance. This name has conventionally been set to ORCL, which is the default name for an Oracle instance. Information can be specified for more than one Oracle instance if the Target Agent on this machine must connect to an Oracle server that has multiple instances.

The following is an example of entries in a dbewhse.cm file used to communicate to two Oracle instances, one named ORCL and one named ORCL2. For the ORCL2 instance, the name TEST is used following the setopt rather than ORCL2 to illustrate that the setopt name does not have to be the same as the instance name, however, the ORACLE_SID parameter does have to be the same as the instance name.

setopt ORCL "oraclient"

setopt ORCL_env "ORACLE_HOME=/usr/vendor/oracle/9i/9.0.1*ORACLE_SID=ORCL*LIBPATH=$ORACLE_HOME/lib32:/usr/lib:$RTHOME/lib/rs6000_aix*PATH=$ORACLE_HOME/bin:$RTHOME/bin:/usr/bin:."

setopt TEST "oraclient"

setopt TEST_env "ORACLE_HOME=/usr/vendor/oracle/9i/9.0.1*ORACLE_SID=ORCL2*LIBPATH=$ORACLE_HOME/lib32:/usr/lib:$RTHOME/lib/rs6000_aix*PATH=$ORACLE_HOME/bin:$RTHOME/bin:/usr/bin:."

Note: Examples for Solaris, AIX, and HP-UX are provided in the dbewhse.cm

The following is a list of special configuration requirements based on your environment:

If you are using Oracle 9i on a 64 bit UNIX machine, the library path specified in the dbewhse.cm file must be set to point to the $ORACLE_HOME lib32 directory instead of the Oracle lib directory.

If you are using Oracle 8.1.7 or later on Solaris or Oracle 9i or later on HP-UX, a symbolic link must be created. You must be in the UNIX Target Agent directory to create the symbolic link as follows.

If you are using Solaris and Oracle Version 8.1.7 or later, create a symbolic link named libclntsh.so.1.0 pointing to Oracles libclntsh.so using this syntax: ln s /lib/libclntsh.so libclntsh.so.1.0

For example, if your Oracle home directory is /usr/vendor/oracle/8.1.7: ln -s /usr/vendor/oracle/8.1.7/lib/libclntsh.so libclntsh.so.1.0

If you are using HP-UX and Oracle Version 9i or later, create a symbolic link named libclntsh.sl.8.0 pointing to Oracles libclntsh.sl using this syntax: ln s /lib/libclntsh.sl libclntsh.sl.8.0

For example, if your Oracle home directory is /usr/vendor/oracle/9i/9.0.1: ln -s /usr/vendor/oracle/9i/9.0.1/lib/libclntsh.sl libclntsh.sl.8.0



If you are using Oracle 9i on a 64 bit Solaris or HP-UX machine, you must use Oracles lib32 directory instead of lib in the symbolic link creation.

If it is necessary to create a symbolic link in the UNIX Target Agent directory, then the full path name for the UNIX Target Agent directory must be added to the library path specified in your dbewhse.cm file, so that the symbolic link is found as part of the Target Agent library path search.

DB2 UDB on UNIX Considerations

The dbewhse.cm file for UNIX systems supplies the following commands for defining environmental information for use with a DB2 UDB target database:

setopt DB2 db2client DB2 is the target name. This name can be changed here and in the other setopt parameters, however, it must correspond to the name used in the #TARGET parameter in the STORE statement of the Target Agent script for data movement. Do not change the db2client name.

setopt DB2_env "DB2 environment variables Specify the DB2 environment variables. These variables include DB2_HOME, DB2INSTANCE, PATH, and library path.

For the setopt DB2_env "DB2 environment variables", perform the following steps:

1. Remove the starting and ending comment characters /* and */ from the setopt DB2_env line and specify the appropriate values for the DB2_HOME and DB2INSTANCE by replacing the < > placeholders with the values.

2. Substitute the appropriate library path environment variable name for the parameter. Library path environment variable name varies by UNIX platform AIX uses LIBPATH, Solaris uses LD_LIBRARY_PATH, HP-UX uses SHLIB_PATH.

3. Substitute the appropriate Enterprise Communicator lib name for the parameter AIX uses rs600_aix, Solaris uses sun4_solaris, HP-UX 10 uses hp700_hpux, HP-UX 11 uses hp700_hpux11.

4. Be sure to remove the < > placeholder brackets when you are setting the above values. Do not change the names or order of any of these environment variables. The * between each of the variables must remain. The entire string following the setopt DB2_env must be in double quotes.

Note: Examples for Solaris, AIX and HP-UX are provided in the dbewhse.cm

The database alias name that you define in your DB2 client on Windows must be the same name as the DB2 database to which the data movement script and Target Agent will connect. This database alias name is specified in the Select server box on the Server/Database tab of the scripts profile in Script Manager. Use of a DB2 client database alias name that is not the same name as the DB2 database will result in the Target Agent being unable to find the database.

Configuring the Target Agent on a Windows Database Server


Additional dbewhse.cm File Considerations for UNIX

The setopt PING parameter can be set to either oraclient or db2client, depending on what is appropriate for your site. This parameter is used by the tgtping test, which verifies that the Target Agent is operational and accessible. The setopt PING tells the Target Agent which client to load if the tgtping test does not specify a parameter such as ORCL or DB2.

The setopt debug parameter can be set to either yes or no. If set to yes, it will provide debugging files in the Target Agent directory for debugging Target Agent problems. The debug files will have a name in the format of DBEnnnn, where nnnn is a process id number associated with that Target Agent session.

Starting the Target Agent Daemon

The Target Agent daemon is a background process that communicates with the Advantage DT Server. The Target Agent daemon must be running when the data movement scripts that utilize the Target Agent are executed or when using the tgtping command to test Target Agent connectivity.

To start the Target daemon on the UNIX server:

1. From the command line of the Target Agent directory on the UNIX machine where the target database server is located, enter the following command: ./tgtdaem

The UNIX command prompt redisplays and the Target Agent begins running as a background process.

Note: To stop the Target Agent daemon, you must kill the background process.

2. When you are satisfied that the Target Agent is running, proceed to the section Verifying the Target Agent Installation.

Configuring the Target Agent on a Windows Database Server The Advantage Data Transformer CD provides the means for placing the Target Agent component on a local server along with other Advantage DT components, such as the data movement Server, or on a remote Windows server where only the target database server resides.

Note: The Target Agent must be located on the machine that contains the target database server.



Installing Target Agent and Enterprise Communicator

To install Enterprise Communicator and Target Agent files on a Windows database server from the Advantage Data Transformer CD, follow these steps:

During installation, select either Complete or Custom install.

Complete installation - Installs all Advantage Data Transformer components.

Custom installation - Allows you to select which components you want installed on each machine.

Note: For a remote database server, which only requires the Target Agent component, select Custom installation, then select only the Target Agent component.

Target Agent requires the Computer Associates Enterprise Communicator (PEC) product, which is automatically installed during the Advantage Data Transformer installation.

Configuring the Target Agent for Windows

When the Target Agent is installed, the Target Agent executables and configuration file are located on the target database server in the Advantage Data Transformer installation bin directory. By default the location is c:\Program Files\CA\Advantage Data Transformer\bin. The next task is to configure the Target Agent so it can communicate with Advantage Data Transformer.

To configure the Target Agent, review, and, if necessary, edit the dbewhse.cm file shown here.

setopt ORCL "oraclient" setopt ORCLpath "d:\\ORANT" setopt ORCLsid "ORCL" setopt ORCLloader sqlldr setopt ORCL_env "ORACLE_HOME=D:\\ORANT" setopt DB2 "db2client" setopt PING "oraclient" setopt debug no

1. Using the text editor of your choice, open the dbewhse.cm file, then make the changes outlined in the sections Oracle on Windows Considerations or DB2 UDB on Windows Considerations.

2. Save dbewhse.cm, then exit.

If you have installed the Target Agent component on a remote Windows database server, you must configure the Enterprise Communicator client on that machine to point to the Enterprise Communicator Rtserver that is running on the Windows machine where the data movement Server is running.



Note: The following steps are not necessary if you are running the Target Agent component on the same local machine as the data movement Server.

To configure the Enterprise Communicator on a remote Windows database server, follow these steps:

1. Locate the Enterprise Communicator rtclient.cm file found in the c:\Program Files\CA\SharedComponents\pec\standard directory on the remote database server machine. Using the text editor of your choice, add the following line to the rtclient.cm file: setopt server_names tcp:rtserver_machine_name

where rtserver_machine_name is the IP address or name of the machine that will be running Enterprise Communicator Rtserver.

2. Save the rtclient.cm, then exit.

Important! It is critical that the Target Agent and Advantage DT Server both communicate to the same Enterprise Communicator RTserver.

Oracle on Windows Considerations

The dbewhse.cm file for Windows provides the values for an Oracle instance installed on a Windows machine with the default settings. If you must edit the file, use a text editor to change any of these lines.

setopt Line Description setopt ORCL "oraclient" ORCL is the target name. This name can be changed here and in the

other setopt parameters, however, it must correspond to the name used in the #TARGET parameter in the STORE statement of the Target Agent script for data movement.

WARNING! Do not change the oraclient name.

setopt ORCLpath D:\\ORANT" The string in quotes contains the appropriate Oracle path for your environment. This path should point to, but not include, the Oracle bin directory.

Note: Path names must use double backslashes.

setopt ORCLsid "ORCL" The string in quotes is the name of the Oracle SID.

setopt ORCLloader "sqlldr" The string in quotes is the name of the SQL*Loader executable for the version of Oracle you are using.

setopt ORCL_env

"ORACLE_HOME=D:\\ORANT"

The string in quotes contains environment variables for Oracle. In addition to ORACLE_HOME you may specify other variables as needed. Separate variables with an asterisk (*).

Note: Path names must use double backslashes.



You can change the ORCL value used in the dbewhse.cm file to any appropriate name. By convention, the default value is ORCL, which is the default name for an Oracle instance. You can change this name to any appropriate name, even something other than an Oracle instance name. You can specify information for more than one Oracle instance if the Target Agent on this machine needs to connect to an Oracle server that has multiple instances.

Following is an example of entries in a dbewhse.cm file that will be used to communicate to two Oracle instances, one named ORCL and one named ORCL2. For the ORCL2 instance, a name TEST is used following the setopt, rather than ORCL2. This illustrates that the setopt name does not have to be the same as the instance name, however, the ORACLE_SID parameter does have to be the same as the instance name.

setopt ORCL "oraclient" setopt ORCLpath d:\\Oracle\\Ora81 setopt ORCLsid ORCL setopt ORCLloader sqlldr setopt ORCL_env "ORACLE_HOME=d:\\Oracle\\Ora81 setopt TEST "oraclient" setopt TESTpath d:\\Oracle\\Ora81 setopt TESTsid ORCL2 setopt TESTloader sqlldr setopt TEST_env "ORACLE_HOME=d:\\Oracle\\Ora81

DB2 UDB on Windows Considerations

The dbewhse.cm file for Windows provides the following required option line for a DB2 UDB database: setopt DB2 db2client.

DB2 is the target name. This name can be changed, however, it must correspond to the name used in the #TARGET parameter in the STORE statement of the Target Agent script for data movement. Do not change the db2client name.

dbewhse.cm File Considerations for Windows

You can set the setopt PING parameter to either oraclient or db2client, depending on what is appropriate for your site. This parameter is used by the tgtping test that verifies the Target Agent is operational and accessible. The setopt PING tells the Target Agent which client to load if the tgtping test does not specify a parameter such as ORCL or DB2.

You can set the setopt debug parameter to either yes or no. If set to yes, setopt provides debugging files in the Target Agent directory for debugging Target Agent problems. The debugging files are named in the format of DBEnnnn, where nnnn is a process id number associated with that Target Agent session.



Installing the Target Agent as a Windows Service

The Target Agent daemon is a process that communicates with the Advantage DT Server. The Target Agent daemon must be running when data movement scripts that utilizes Target Agent are executed, or when using the tgtping command to test Target Agent connectivity. The Target Agent service to run this daemon is installed and operated as follows:

1. If the Target Agent is placed on a remote database server, with no other Advantage Data Transformer components, perform the following steps to install the Target Agent service on that machine:

a. From a command line window locate the Advantage Data Transformer installation bin directory, then enter the following command:

tgtdaem -install

The Target Agent daemon service is installed, and the service is named Advantage Data Transformer Target Agent.

2. If the Target Agent is placed on a machine where the Advantage Data Movement Server components are also installed, perform the following steps:

a. From Start, Programs, Computer Associates, Advantage Data Transformer, select Configuration.

b. Select Target Agent, then click Next.

c. Select the Set up Data Transformer Target Agent as a service radio button, then click Next.

d. Click Finish.

The Target Agent daemon service is installed, and the service is named Advantage Data Transformer Target Agent.

3. After the service is installed on the Windows machine, use the Windows Control Panel Services Manager to start and stop the Target Agent service, and to define if you want the service to run as either a manually or automatically started service.

4. If you do not wish to run the Target Agent daemon as a Windows Service, you can manually start the daemon from a command line window by navigating to the Advantage Data Transformer installation bin directory, then entering the following command: tgtdaem -debug

The tgtdaem starts in the command line window and remains running until it is stopped. Another command prompt is not displayed while the Target Agent daemon is running. If you want to stop the Target Agent daemon, press Ctrl-C in the command line window where the Target Agent daemon is running.

Verifying the Target Agent Installation


5. When Target Agent is running, proceed to the section Verifying the Target Agent Installation.

Verifying the Target Agent Installation To verify that the Target Agent components have been correctly installed and are working properly, run the tgtping.exe program from the machine where Advantage DT Server is installed.

1. From a command line window, navigate to the Advantage Data Transformer installation bin directory, then enter the following command: tgtping

is the name of the UNIX or Windows machine on which the target database server resides, and where the Target Agent is running. is the name used in the setopt command in the dbewhse.cm file, for example ORCL or DB2 that points to the Oracle or DB2 information contained therein.

For example, tgtping ptisun28 ORCL

This attempts to connect to the Target Agent running on the ptisun28 machine and tell it to load the oraclient pointed to by the setopt ORCL parameter to test the connectivity.

If the Advantage Data Transformer server machine where tgtping is invoked is able to access the Target Agent machine, the following message displays:

Connected successfully to client

Target Agent data movement scripts should now be able to successfully connect to the Target Agent.

If the server machine is not able to access the target machine, the following message displays:

Error connecting to client

This error occurs when the Target Agent setup and configuration is incorrect, or network access to the Target Agent machine fails. Verify your steps to ensure the procedure was followed.

Note: If the tgtping command is run with just the machinename parameter specified and no target parameter specified, the setopt PING parameter in the dbewhse.cm file determines which target agent client executable, oraclient or db2client, is loaded by the tgtping test.

Optional Configuration Activities 41

Chapter 5: Optional Configuration Activities

This chapter describes optional configuration activities that may need to be performed depending on your installed components.

A Summary of Optional Configuration Activities The following are optional configuration tasks you may be required to complete:

Configuring the Advantage Data Transformer Mapper for use with Data Shopper

Configuring Mapper Programs to Use the Target Agent

SAP R/3 Setup

Server Utility Tasks

Setting up an Additional Oracle Idb

Using Microsoft Access for the Idb

Defining Additional Users for an Idb

Loading Standard System Transformations

Configuring the Advantage Data Transformer Mapper for Use With Data Shopper

To configure the Advantage DT Mapper for use with the Advantage Repository Data Shopper, perform the following steps:

1. From the Mapper, select View, Preferences.

The Preferences dialog displays.

2. Click the Data Shopper tab.

Note: The default machine name and virtual directory that is displayed is http://localhost/DataShopper2.1/metadata.asp. The default machine name, localhost, indicates that the Mapper will look for the Data Shopper on the local machine where the Mapper is running. The default virtual directory name is DataShopper 2.1. You many need to change these defaults if they are not appropriate for your site.



3. Specify the machine name of the Advantage DT Server where the Data Shopper is running and the IIS virtual directory on that Advantage DT Server.

Important! If you chose to use an IIS virtual directory name other than the default name of DataShopper2.1 during Advantage Repository installation and configuration of Data Shopper components, ensure that this name is changed in the Mapper as well.

WARNING! Do not change the name of the file metadata.asp.

4. Confirm the name of the IIS virtual directory that is being used by running the Microsoft Internet Information Server Internet Service Manager on the machine where Data Shopper is installed. In the Console Root folder, open the Internet Information Server. Under the default website is a list of all virtual IIS directories on that machine.

Configuring Mapper Programs to Use the Target Agent To utilize the Target Agent fast loading capability with scripts generated from your Mapper programs, certain steps must be performed to set up each program that will use this capability. In addition to the tasks described in the chapter Configuring the Target Agent, perform the following steps to use the Advantage DT Mapper to enable the Target Agent:

1. From the Advantage Data Transformer Mapper, open an Advantage Data Transformer program that will load data onto an Oracle or DB2 UDB target table.

2. Right-click the blue title bar of the Oracle or UDB target table. The pop-up menu displays.

3. Choose Properties. The Table Properties dialog displays.

4. Select the Store Processing tab.

5. Click the Insert button then click the Target Agent check box.

6. Enter information in the Host Machine and Target Type fields as follows:



Target Database Syntax Example DB2 UDB Host MachineEnter the name of the machine on which the

DB2 UDB target database resides. This is the machine where the Target Agent component is installed. This name must be a machine name, not an IP address. Ensure that you can ping the specified machine name from the machine where the Advantage DT Server for data movement will be running scripts.

The value specified for Host Machine will become the value used in the #HOST parameter of the generated script STORE statement.

db2serv1

DB2 UDB Target TypeEnter the DB2 target name that is found in the dbewhse.cm file that was installed with the Target Agent components on the DB2 UDB target machine. The target name is the value following the setopt parameter in the setopt DB2 db2client string.

The value specified for Target Type will become the value used in the #TARGET parameter of the generated script STORE statement

DB2

Oracle Host MachineEnter the name of the machine on which the Oracle target database resides. This is the machine where the Target Agent component is installed. This name must be a machine name, not an IP address. Ensure that you can ping the specified machine name from the machine where the Advantage DT Server for data movement will be running scripts.

The value specified for Host Machine will become the value used in the #HOST parameter of the generated script STORE statement.

oraserv1

Oracle Target TypeEnter the Oracle target name that is found in the dbewhse.cm file that was installed with the Target Agent components on the Oracle target machine. The target name is the value following the setopt parameter in the setopt ORCL oraclient string.

The value specified for Target Type will become the value used in the #TARGET parameter of the generated script STORE statement.

ORCL

SAP R/3 Setup


Troubleshooting

If problems occur when running the Target Agent, you can use the debug option in the dbewhse.cm file. Enter the following command:

setopt debug yes

This tracks and records processes in the Target Agent and provides information that is used by Computer Associates Technical Support.

SAP R/3 Setup If you are running Advantage Data Transformer Enterprise Metadata Edition, and using a SAP R/3 system as a Mapper and data movement database source, you must configure SAP R/3 for access by Advantage DT. This only needs to be done once from a single machine. It is recommended that that you use the machine where the Advantage DT Server is installed to perform this task. Ensure that SAP R/3 client software is in place on this machine.

SAP R/3 Setup


To configure SAP R/3 for access by Advantage DT, follow these steps:

1. From the Start menu, choose Programs, Computer Associates, Advantage, Data Transformer, and click the SAP R3 Interface Setup icon. The Advantage Data Transformer SAP R/3 Interface Setup dialog displays.

2. Enter the appropriate SAP R/3 parameters.

3. Click OK to verify that the SAP R/3 configuration was successful.

You should now run an SAP R/3 installation verification.

Server Utility Tasks


4. From the Start menu, choose Programs, Computer Associates, Advantage, Data Transformer location. The Advantage Data Transformer SAP R/3 Test dialog displays.

5. Enter the appropriate SAP R/3 parameters.

6. Click Run Test.

Scan Metadata into the Advantage Repository

Metadata stored in the Advantage Repository is used to define what SAP R/3 data you want to move. Refer to the Advantage Repository SAP R/3 Interface User Guide for instructions.

Server Utility Tasks The Advantage DT Server component includes utilities to backup and restore the contents of an internal database (Idb), to synchronize (register) database interfaces, and to schedule data movement scripts from programs outside the Script Manager.

Dumping an Idb


The Utilities

You can run most of the Advantage DT Server utilities from the Advantage Data Transformer program group or by running them from a command prompt.

Note: PTIDBRUN does not have a program group icon and must be run from a command prompt or from an executable program.

The following Advantage DT Server utilities are located in the Advantage Data Transformer bin subdirectory. By default the location is c:\Program Files\CA\Advantage Data Transformer\bin subdirectory:

Utility Function ipdump.exe Script Dump Utility. Backup an Idb

ipload.exe Script Load Utility. Restore or load a copy of an Idb

ipsync.exe Script Interface Synchronizer. Synchronize (register) Server database interfaces

PTIDBRUN Executes an Advantage Data Tran

adt config

Documents