Table of Contents

Search

  1. Preface
  2. Runtime environments
  3. Hosted Agent
  4. Secure Agent groups
  5. Serverless runtime environments
  6. Connectors in a serverless runtime environment
  7. Secure Agents
  8. Secure Agent installation

Runtime Environments

Runtime Environments

Configure VNet for databases or endpoints outside of Azure

Configure VNet for databases or endpoints outside of Azure

You need to perform additional configuration on the VNet if you use Oracle or any database or endpoint hosted on-premises or outside of the Azure ecosystem.
Perform the following tasks:
  • Add trusted IP addresses. If your organization filters based on IP addresses, add the safe Informatica addresses so that they won't get blocked by the firewall. For more information, see Adding trusted Informatica IP addresses.
  • Create a supplementary file location. If your mappings use JAR files and external libraries, set up a location on an Azure storage account with either Gen2 or blob. Use the following format:
    abfs://<file_system>@<account_name>.dfs.core.windows.net/<path>
    For example, to use a JDBC connection, you place the JDBC JAR files in the supplementary file location and then enter this location:
    abfs://discaleqa@serverlessadlsgen2acct.dfs.core.windows.net/serverless
  • Configure TLS to authenticate REST APIs. If you use a REST V3 Connector, you can configure TLS to authenticate REST APIs. For more information, see Configuring TLS to authenticate REST APIs.

0 COMMENTS

We’d like to hear from you!
Remy van der Kleij - October 02, 2024

Is it correct that you have to define a location on Amazon S3, even though the serverless agents are on Azure? I expect that ADLS Gen2 or Azure Blob would be supported for Azure-based serverless agents.

Informatica Documentation Team - October 02, 2024

Hi Remy,

Thanks for reaching out! We're currently checking with our development and QA teams about this and will get back to you shortly.


Informatica Documentation Team - October 02, 2024

Hi Remy,

We've confirmed with our development team that you can't define a location on Amazon S3 when the serverless agent is on Azure. You need to use an Azure storage account with either Azure Data Loake Storage Gen2 or Azure Blob Storage with the following URI format:
abfs://@.dfs.core.windows.net/