Use the serverless runtime environment

• •Add the ODBC drivers in the Amazon S3 bucket or Azure container in your AWS or Azure account.
• •Configure the .yml serverless configuration file.

Add the ODBC drivers in the Amazon S3 bucket or Azure container in your AWS or Azure account

Perform the following steps to use a serverless runtime environment in an ODBC connection:

1. 1Create the following structure for the serverless agent configuration in AWS or Azure: <Supplementary file location>/serverless_agent_config
2. 2Add the ODBC drivers in the Amazon S3 bucket or Azure container in the following location in your AWS or Azure account: <Supplementary file location>/serverless_agent_config/ODBC

Configure the .yml serverless configuration file

Perform the following steps to configure the .yml serverless configuration file in the serverless runtime environment:

1. 1Copy the following code snippet to a text editor and specify the driver file names and DSN entries:
version: 1
agent:
dataIntegrationServer:
autoDeploy:
odbc:
drivers:
- fileCopy:
sourcePath: ODBC/<Driver_file name>
- fileCopy:
sourcePath: ODBC/<Driver_file name>
dsns:
- name: "<Name of the ODBC database>"
entries:
- key: Driver
value: <Driver_file name>
- key: Description
value: "<Description of the driver>"


where the source path is the directory path of the ODBC drivers in AWS or Azure.
Note: The DSN entries vary based on the driver you want to add to the serverless runtime location.
The following example shows the DNS entries for the Microsoft SQL Server driver:
version: 1
agent:
dataIntegrationServer:
autoDeploy:
odbc:
drivers:
- fileCopy:
sourcePath: ODBC/DWdb227.so
- fileCopy:
sourcePath: ODBC/DWdb227.so
dsns:
- name: "<SQL server>"
entries:
- key: Driver
value: DWsqls227.so
- key: Description
value: "SQL Server 2014 Connection for ODL"
- key: HostName
value: INVW16SQL19
- key: PortNumber
value: 1433
- key: Database
value: adapter_semantic
- key: QuotedId
value: No
- key: AnsiNPW
value: Yes

2. 2Ensure that the syntax and indentations are valid, and then save the file as serverlessUserAgentConfig.yml in the following AWS or Azure location: <Supplementary file location>/serverless_agent_config
When the .yml file runs, the ODBC drivers are copied from the AWS or Azure location to the serverless agent directory and the DNS entries are updated in the odbc.ini file.