Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Introduction to ODBC Connector
  3. Connections for ODBC
  4. Synchronization tasks with ODBC Connector
  5. Mappings and mapping tasks with ODBC Connector
  6. SQL ELT optimization
  7. Data type reference

ODBC Connector

ODBC Connector

Configure the elastic runtime environment

Configure the elastic runtime environment

You can use an elastic runtime environment hosted on AWS to connect to ODBC-compliant databases.
Before you configure an ODBC connection using the elastic runtime environment, make sure to complete certain prerequisites.
Perform the following steps in the AWS infrastructure:
  1. Deploy the elastic runtime environment on AWS to make the Kubernetes cluster available to process data from Informatica Intelligent Cloud Services.
    For more information about deploying an elastic runtime environment, see Deploy an elastic runtime environment.
  2. Create a data disk in the same AWS environment that hosts the elastic runtime environment to store custom binary files.
  3. On the master node, create a directory and mount the data disk to that directory.
  4. Place the custom binaries on the mounted disk and copy the exact path to the binary files.
    This path is used later in POST API calls.
Perform the following steps within Informatica Intelligent Cloud Services:
  1. Ensure that the elastic agent is up and running and enable the required connectors.
    To enable connectors to use the elastic agent, perform the following steps:
    1. In Administrator, select
      Runtime Environments
      .
    2. Right-click the Secure Agent group and select
      Enable or Disable Services and Connectors
      .
      A dialog box listing all the services and connectors for the Secure Agent group is displayed.
    3. On the
      Connectors
      tab, enable the required connectors.
    4. Click
      OK
      .
  2. Obtain the session ID and runtime environment ID from your organization.
  3. To register the binary files, make a POST call to the REST API, passing the session ID, runtime environment ID, and the binary file path. You can add multiple DSN drivers in the same POST call.
    For more about information about making the POST calls, see Supplementary files in the REST API Reference guide.
    The following is an example of the POST request:
    POST <base URL>/api/v3/RuntimeEnvironment/<runtime environment ID>/ElasticConfig Content-Type: application/json Accept: application/json INFA-SESSION-ID: <SessionId> { "rteId": "rte-12345", "specification": { "agent": { "dataIntegrationServer": { "odbc": { "drivers": [ { "sourcePath": "/<path of driver in data disk>/DWsqls18.so" } ], "dsns": [ { "name": "ODBC_SQLServer", "entries": [ { "key": "Driver", "value": "DWsqls18.so" }, { "key": "Description", "value": "Test Connection" }, { "key": "HostName", "value": "<>" }, { "key": "PortNumber", "value": "1234" }, { "key": "Database", "value": "cloud_DB" }, { "key": "QuotedId", "value": "No" }, { "key": "AnsiNPW", "value": "Yes" } ] }
    Ensure that the key-value pairs are same as the key-value pairs in the odbc.ini file.
    The POST call triggers a restart of the Data Integration Server.
  4. Verify that the elastic runtime environment is up and running by checking the status of the Data Integration Server in Administrator.
  5. Test a connection or run a mapping to confirm that the elastic runtime environment can access and use the custom binary files.
For more information about how to configure and use the elastic runtime environment, see
Elastic Runtime Environments
in the Administrator help.

0 COMMENTS

We’d like to hear from you!