search cancel

How to install Federation Adapters and ADT as a component of CMDB on Win2008 with an Oracle MDB


Article ID: 50133


Updated On:


Advantage Data Transformer



After installing Service Desk Manager and CMDB, there's an option to install and configure Advantage Data Transformer and then Federation Adapters. A patch is required for ADT to run on Win2008. Also, installing ADT on any drive other than C will require a modification of an installation file. Below are instructions for installing ADT and Federation Adapters on Win2008 with Oracle hosting the MDB, and, optionally, installing ADT on a non-C drive.


  1. Before installing ADT, there needs to be an Oracle client installed on the computer hosting ADT.
    A database client for the database server that hosts your Idb needs to be installed on the ADT host computer whether the database server resides on this or another computer. The client should be a version that is the same or higher than the database server.

  2. Select INSTALL ADT from the Service Desk Manager install disk/image menu.

    1. Select Express install OR

    2. Select Custom install and de-select Normalizer, Target Agent, and Demo.

      The install will get errors because a fresh copy of ADT 2.2 doesn't know how to locate some system files in Win2008. Expect an error such launchwin.c can't find scdct.c. Ignore the errors. This problem is corrected by the following patch (ADT #21.)

  3. Install ADT patch #21.
    This patch is published at CA Support Online under CMDB patch number RO15654.

    This certification upgrade is available to CMDB customers to enable ADT to work going forward under 32-bit or 64-bit operating systems Windows 2008 or Windows 2003. The patch modifies ADT files, so if ADT is uninstalled and re-installed, it would be back to the original ADT and need the patch reinstalled.

    This patch also adds ADT support for an Idb hosted by SQL2008 32- or 64-bit and Oracle 11g 32-bit only.

  4. Install the latest version of PEC.
    Download PEC 4.7.4 from CA Support as CMDB patch RO18415. "PEC" is the CA Enterprise Communicator Service, and the Communicator executable is rtserver.exe.

    The PEC that is installed with ADT 2.2 is an older version. The newer PEC may be installed before or after ADT. If it's installed first, ADT will see you already have a newer PEC and ask you to confirm not replacing it. If you install PEC 4.7.4 after ADT, the installer will update (replace) the old PEC.

    Follow the instructions that come in RO18415 for starting the PEC installer. During the PEC install:

    • Let it use the default location on C, no matter what drive the CA products are installed on.

    • Be sure to select to have PEC run on THIS computer.

    • No need to name any failover servers. Just NEXT that page.

  5. Create infopump user in the Database Server.
    Have a 'system' or DBA-privileged Oracle user execute the CA-provided script to create the infopump user and issue grants in Oracle. See \CA\Advantage Data Transformer\idbsetup\oracle_mdb.sql.

  6. Pre-configuration Notes:

    1. Check that you have the latest CA ODBC driver for Oracle before going to Step 7.

      • Run C:\WINDOWS\SYSWOW64\odbcAd32.exe to access the ODBC Administrator of 32-bit DataSources.

      • Select the Drivers tab and check for CAI/PT Oracle8.

      • Scroll to the right and confirm the date is March, 2007.

      • If it is earlier, please contact CA Technical Support for ADT.

  7. If ADT is not installed on the C: drive, see Note I at the bottom of this document about modifying a Perl file, before going to Step 8.

  • Configure ADT.
    Go to the ADT Start/Programs icons and run Configuration.

    1. Select only Server and Script Manager to configure.

    2. Confirm the path to the ADT executables.

    3. Select "A new Server in an existing Idb." An "Idb" is ADT's name for its tables, its Internal Data Base. The "existing Idb" you are selecting refers to the set of ADT tables that are pre-defined in the MDB.

    4. Select <a new datasource>

      This pops you out of ADT Configuration and into the ODBC Administrator to create a 32-bit System DSN for ADT to connect to the Idb.

      • Configure the Oracle DataSource using the CAI/PT Oracle 8 driver.

      • The usual name for this DataSource is IDB, but you can give it any name.

      • Enter the Server name.

      Then you are put back into the ADT Configurator.

    5. The ADT Configurator now wants to test the DSN. Provide the infopump login credentials.

    6. The internal name of the server defaults to <yourAdtIdbDsnName>_Server, e.g. IDB_Server.

    7. No changes on this page; Do not select to do an Idb load.

    8. No changes on this page; Do not select to create a Windows Service. If you want ADT Server to start automatically, you can run the ADT Configuration Utility at a later time to create the Service. It's best to keep the initial configuration uncluttered.

    9. Review the summary listing and click next or finish.

    10. It will run the Script Interface Synchronizer. This checks what database clients are installed and registers interfaces. Check the last line of the output to confirm it completed successfully. This output also goes to your Advantage Data Transformer\bin\log\system.log.

    11. Now that the ADT Server configuration is complete, the Configurator will bring up the "Script Manager Configuration" to register your Idb DSN for the ADT Client pieces, Mapper and Script Manager.

    12. Another Summary screen, then Finish.

  • Installing Federation Adapters
    This imports and loads metadata and sample programs related to Federation Adapters into ADT.

    It is recommended that this program be executed directly rather than by using the menu item on the on the install disk. Go to Windows Explorer and double-click on x:\Program Files (x86)\CA\Service Desk Manager\cmdb\data\federationAdapters\install_federation_adapters.exe or run install_federation_adapaters.exe from a command window at that directory. If Service Desk Manager and ADT are not installed on the same computer, copy the folder x:\Program Files (x86)\CA\Service Desk Manager\cmdb and its contents to the computer hosting ADT.

    The installation of Federation Adapters begins and shows you a progress window.

    • It imports several dozen files that contain the XML metadata that will be used to format your output XML files that will be used as input to GRLoader.

    • It imports some sample ADT programs into ADT Mapper.

    • It loads three sample profiles into ADT Script Manager. These are cmdb_profile_mdb, cmdb_profile_xls, and cmdb_profile_xml.
  • Notes

    1. If ADT is not installed on C or if you get RC=100 during the installation of Federation Adapters, the FA install program is unable to find ADT. This is usually because ADT is not installed on the C: drive, so the install program needs to be told the ADT path. Go to ...:\Program Files (x86)\CA\Service Desk Manager\cmdb\data\federationAdapters\ and locate the file

      1. Open it with Notepad and turn off word-wrap.

      2. Locate the following text (usually line 126) my $adtbin = "$ENV{ADT_INSTALLDIR}/BIN";

      3. Copy that line, then remark one of them by putting a pound-sign (#) in front of it. This will save the original line as a backup.

      4. Edit the other copy of the line so that it points to the actual location of your ADT executables folder. If you use Windows Explorer to copy/paste the path, be sure to switch the backslashes to forward slashes. The 2 lines will look like this:

        # my $adtbin = "$ENV{ADT_INSTALLDIR}/BIN";
        my $adtbin = "D:/Program Files (x86)/CA/Advantage Data Transformer/BIN";

      5. Save the edited file -- no recompile is required.

      6. You are now ready for Step 8.

    2. See TEC553610 for installing ADT and Federation Adapters when the MDB is hosted by SQL Server.

    3. If you have any difficulty, please call CA Support for Advantage Data Transformer at 1-800-225-5524.


Component: DWM