Get Data Moving 1
Results 1 to 3 of 3

Thread: HOW TO: Business Objects Data Integrator and Attunity Thin ODBC checklist

  1. #1
    Adeeb Mass'ad is offline Support Manager
    Join Date
    Aug 2006
    Location
    Jaffa of Nazareth
    Posts
    169
    Rep Power
    14

    HOW TO: Business Objects Data Integrator and Attunity Thin ODBC checklist

    DESCRIPTION

    Installing the Attunity ThinODBC for usage with the Business Objects Data Integrator is very straightforward process, follows is a step by step checklist which the user should follow to ensure proper configuration.

    WINDOWS - CHECKLIST

    Data Integrator on Windows does not support File DSNs therefor the user should install the full Attunity Server Kit for Windows.

    UNIX - CHECKLIST

    1. Download and install the proper Attunity ThinODBC Kit.

    For 64Bit platforms make sure to install the ThinODBC 64Bit Kit.

    2. It is recommended to install the ThinODBC Kit on the same account where Data Integrator is installed.

    Example:

    - Assuming Data Integrator is installed at /usr/bodi, extract the Thin ODBC kit to /usr/bodi/thinodbc.

    The kit should include several files including the product's main modules:
    - thinapi.so
    - libnavshr.so
    - libnvbaseshr.so
    - libodnavshr.so
    3. Edit the local definitions file for the login (.cshrc or.bashrc, etc...) and add the path to the LD_LIBRARY_PATH/SHLIB_PATH/LIBPATH environment variable, for example:
    setenv LD_LIBRARY_PATH /usr/bodi/thinodbc:$LD_LIBRARY_PATH
    4. Decide which odbc.ini will serve your application, you can use the default odbc.ini residing in the Data Integrator's BIN directory:
    $LINK_DIR/bin/odbc.ini
    5. Add an ODBCINI variable to the login profile, and point it to the target ODBC.INI, for example:
    setenv ODBCINI $LINK_DIR/bin/odbc.ini
    Make sure the $LINK_DIR is defined and pointing to the Data Integrator root directory.

    6. Define a DSN in the odbc.ini, make sure to use the same name as the one used in the Data Integrator's Designer, for example:

    [ATT_DBSALES]
    Driver=/usr/bodi/thinodbc/thinapi.so
    Description=Attunity DB2 Driver on the Mainframe
    BindURL=10.0.1.10:2551/Navigator
    OneTdpMode=1
    DefTdpName=DBSALES

    The ATT_DBSALES DSN points to an Attunity Server (IP:PORT 10.0.1.10:2551), where it accesses an Attunity DataSource called DBSALES (it can be any DataSource type which Attunty supports).

    The DataStore configuration on the Data Integrator Designer would be similar to the following screen capture:

    NOTE: The ATT_DBSALES DSN would be an Attunity DSN which points to the DBSALES DataSource defined in the Attunity Server.

    7. If you are using Data Integrator's ODBC Manager (built-in) make sure that the UseDIUnixODBCDriverManager property is set to true in the DSConfig.txt:

    $LINK_DIR/bin/DSConfig.txt

    After finalizing all the setup or modifying any variables in the startup environment, you should restart the DI Job Server usnig the "svrcfg" utility.
    Last edited by Adeeb Mass'ad; 02-20-2008 at 06:10 AM.
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

  2. #2
    Adeeb Mass'ad is offline Support Manager
    Join Date
    Aug 2006
    Location
    Jaffa of Nazareth
    Posts
    169
    Rep Power
    14

    HOW TO: Add debugging to the Attunity DSN on Unix

    DESCRIPTION

    The DataSource defined in the odbc.ini can contain Attunity specific debugging flags. In many cases where there is some failure the user may need to supply Support with the adequate logging in order to analyze the failure.

    All of the debugging flags available from Studio can be set manually in the odbc.ini, for example:

    [ATT_DBSALES]
    Driver=/usr/bodi/thinodbc/thinapi.so
    Description=Attunity DB2 Driver the Mainframe
    BindURL=10.0.1.10:2551/Navigator
    OneTdpMode=1
    DefTdpName=DBSALES
    Debug/logFile=/usr/bodi/thinodbc/odbc_%P.log
    Debug/generalTrace=true
    Debug/apiTrace=true

    This will enable apiTrace which is the ODBC interface APIs level and generalTrace which adds general Attunity debugging information.
    Last edited by Adeeb Mass'ad; 02-19-2008 at 01:44 PM.
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

  3. #3
    Adeeb Mass'ad is offline Support Manager
    Join Date
    Aug 2006
    Location
    Jaffa of Nazareth
    Posts
    169
    Rep Power
    14

    HOW TO: Add ODBC Manager level debugging

    DESCRIPTION

    Most Unix ODBC Managers provide a logging facility which is at a higher level than the target ODBC driver.

    To enable this facility add the Trace options as follows:
    Trace=1
    TraceFile=/usr/bodi/thinodbc/odbctrace.log
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •