Installed file structure

The following table describes the file structure used by the connector and identifies the installed files.

Notes:

  1. This document uses (\) backslashes as the convention for directory paths. For UNIX installations, substitute slashes (/) for backslashes.

  2. All product path names are relative to the directory where the product is installed on your system.

  3. For Windows, Installer adds an icon for the connector file to the IBM WebSphere Business Integration Adapters menu. For a fast way to start the connector, create a shortcut to this file on the desktop.


Subdirectory of %ProductDir% Description
connectors\Retek\CWRetek.jar Jar file containing connector code (classes of the Retek connector)
connectors\Retek\start_Retek.bat (Windows) start_Retek.sh (UNIX) Startup file for the connector
connectors\Retek\dependencies Directory containing other required files:
  • Retek_RIHeader.out--Retek header business object definition
  • Retek_Generic.out --Retek Generic business object definition
  • Retek_KeyMO --Key metaobject definition
connectors\messages Directory containing the RetekConnector.txt file for error messages
repository\Retek Directory containing the CN_Retek.txt file
connectors\Retek\samples Directory containing samples of connector configuration, business objects, collaboration objects, and metaobjects:
  • MO_DataHandler_RetekXML
    Config.out--configuration
    metaobject for the XML WebSphere MQ Integrator BrokerWebSphere MQ Integrator Broker
  • RDM_ConsumeMO--consume metaobject for RDM
  • Retek_POPhyDesc.out, Retek_VendorDesc.out, Retek_PORef.out, Retek_VendorRef.out, Retek_VendorAddrDesc.out, Retek_VendorAddrRef.out--- business object definitions for purchase orders and vendors
  • RMS_ThreadMO1.out, RMS_ThreadMO1.out--sample thread metaobjects
  • RMS_OrderPhys.out,RMS_Vendor.out--metaobjects for order and vendor message families
  • PassThru_*.out--Pass-through collaborations for the samples

Copyright IBM Corp. 1997, 2003