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

Serverless runtime environments

Serverless runtime environments

A serverless runtime environment is an advanced serverless deployment solution that doesn't require downloading, installing, configuring, or maintaining a Secure Agent or Secure Agent group. You can use a serverless runtime environment in the same way that you use a runtime environment when you configure a connection or tasks in Data IntegrationData Integration
}
.
A serverless runtime environment is an advanced serverless deployment solution that uses an isolated, single-tenant model, unlike the multi-tenant model on the Hosted Agent.
The single-tenant model provides a dedicated server with virtual machine resources to run tasks for your organization. The serverless runtime environment auto-scales with the size of the workload while your data remains in your cloud environment.
A serverless runtime environment can be hosted on these cloud platforms:
  • Amazon Virtual Private Cloud (VPC). The serverless runtime environment creates an elastic network interface (ENI) to connect to your cloud environment.
  • Azure Virtual Network (VNet)
A serverless runtime environment supports local regions in each geo-location. For example, an AWS cloud platform in the United States (US) supports all US regions and an AWS cloud platform in Asia-Pacific (APAC) supports all APAC regions.
Users who require access to the Serverless Environments configuration page require the PRIVILEGES.VIEW_AGENT_GROUP permission.

Running mappings in advanced mode

When you use a serverless runtime environment to run mappings in advanced mode, the advanced serverless deployment fulfills the prerequisites to create an
advanced cluster
and to run jobs on the cluster.
The serverless runtime environment manages the
advanced cluster
while the cluster adapts to workload changes by provisioning and de-provisioning resources. Worker nodes in the
advanced cluster
are highly available. High availability mitigates job failures and maintains job performance when a worker node crashes.

0 COMMENTS

We’d like to hear from you!
Andre Almar - October 11, 2024

Hi, Is there an API we can use related to this? If so where is the documentation ?

Informatica Documentation Team - October 14, 2024

Hi Andre,

You can use the "job" resource to start or stop a mapping task based on its ID or name. Please see the following topic:

https://docs.informatica.com/cloud-common-services/administrator/current-version/rest-api-reference/platform-rest-api-version-2-resources/jobs.html