Table of Contents

Search

  1. Preface
  2. Runtime environments
  3. Hosted Agent
  4. Secure Agent groups
  5. Secure Agents
  6. Secure Agent installation in a cloud environment
  7. Secure Agent installation in a local environment
  8. Serverless runtime environment setup in AWS
  9. Serverless runtime environments

Runtime Environments

Runtime Environments

Populating the serverlessUserAgentConfig.yml File

Populating the serverlessUserAgentConfig.yml File

Use the following template to create your
serverlessUserAgentConfig.yml
file:
# The Secure Agent is the root element, and configurations are applied to the agent. # Under the agent, there are three levels: #1: apps : Application where you need to apply configurations. #2: event: Event relating to the life cycle of application. #autoDeploy: Configurations that need the agent app to restart. Configurations are applied and minor versions of the app are upgraded. An upgrade event will detect the difference between the configuration that was last applied and the current request and apply only those configuration changes. Note that Administrator does not show notifications during minor version upgrades. #autoApply: Configuration that takes effect immediately, such as copying Swagger files. #3: section: Contains configurations based on connectors. # How do I apply the YML file? # Create a serverlessUserAgentConfig.yml file with these contents in <supplementary_file_location>/serverless_agent_config. # The path in the serverlessUserAgentConfig.yml file is relative to <supplementary_file_location>/serverless_agent_config/. # fileCopy section : Provide the source location of the file that needs to be copied. version: 1 agent: # At the agent level, provide general configurations that are not specific to the application. agentAutoApply: general: # General section for common configurations across applications and connectors. sslStore: # Use this to copy SSL files to the instance machine. You can provide a list of fileCopy. - fileCopy: sourcePath: SSL/RESTV2_JWTpyn.jks # Data Integration Server app dataIntegrationServer: autoApply: # Apply configurations that don't need to upgrade the minor version or a restart of the app. For example, you can copy files. restv2: # Connector section swaggers: # List of Swaggers files to copy to the instance machine. - fileCopy: sourcePath: restv2/<swagger_file_name>.json keystores: # List of keystore files to copy to the instance machine. - fileCopy: sourcePath: restv2/key truststores: # List of truststore files to copy to the instance machine. - fileCopy: sourcePath: restv2/key.ext wsconsumer: wsdls: - fileCopy: sourcePath: s3/ jdbc: drivers: - fileCopy: sourcePath: s3/file autoDeploy: # A change in this event will trigger a minor version upgrade with the new configurations. # In this case, the Data Integration Server app will get a minor version upgrade. general: # General section for Data Integration Server app autoDeploy event. ssls: - fileCopy: sourcePath: SSL/RESTV2_JWTpyn.jks importCerts: certName: cname alias: IICS sap: jcos: # List of jco related files to copy. - fileCopy: sourcePath: sap/jco/libsapjco3.so - fileCopy: sourcePath: sap/jco/sapjco3.jar nwrfcs: # List of nwrfc related files to copy. - fileCopy: sourcePath: sap/nwrfc/libicudata.so.50 - fileCopy: sourcePath: sap/nwrfc/libicudecnumber.so hanas: # List of hana related files to copy. - fileCopy: sourcePath: sap/hana/libicudata.so.50 odbc: # Specify ODBC configurations. # This section can be used to configure multiple drivers. drivers: # Specify drivers to copy. - fileCopy: sourcePath: ODBC/DWdb227.so - fileCopy: sourcePath: ODBC/DWdb227.so dns: # Specify DNS entries. These entries will be updated in odbc.ini file. # If the file is not present, a new odbc.ini file will be created. # Make sure to give a name as a unique entry for the ini file configuration. The file will be read and updated using the name. - name: "SQL server" # Section name in ini file unique key. entries: - key: Driver # Only provide the driver file name without the path. value: DWsqls227.so # Because the file is copied, the path to attach during odbc entry is already known. - 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
For more information about populating connector information in the
serverlessUserAgentConfig.yml
file, see the help for the appropriate connector.

0 COMMENTS

We’d like to hear from you!