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

Step 4. Create a serverless runtime environment

Step 4. Create a serverless runtime environment

When you use Azure Native ISV Services, you create and maintain your serverless runtime environments in the Azure portal instead of in
Informatica Intelligent Cloud Services
.
The System Disk and Proxy Servers features are currently not supported in Azure serverless runtime environments.
  1. On your organization's resource page in the Azure portal, click
    Serverless Runtime Environment
    .
    Right now, the list is empty since you have no serverless runtime environments.
  2. Click
    Create New Serverless Environment
    .
    The configuration is divided across four tabs:
    Basics
    ,
    Platform details
    ,
    Runtime configuration
    , and
    Tags
    .
  3. On the
    Basics
    tab, enter the following information:
    Field
    Description
    Name
    Name of the serverless runtime environment.
    Description
    Description of the serverless runtime environment.
    Task type
    Type of tasks that run in the serverless runtime environment:
    • Select
      Data Integration
      to run mappings outside of advanced mode.
    • Select
      Advanced Data Integration
      to run mappings in advanced mode.
    Maximum computer units per task
    Maximum number of serverless compute units corresponding to machine resources that a task can use.
    Task time out (Minutes)
    By default, the timeout is 2880 minutes (48 hours). You can set the timeout to a value that is less than 2880 minutes.
  4. On the
    Platform Detail
    tab, enter the following information:
    Field
    Description
    Region
    Select the region where the serverless runtime environment is hosted.
    Virtual network
    Select a virtual network to use.
    Subnet
    Select a subnet within the virtual network to use.
    Be sure you've completed Step 2. Configure the subnet .
    Supplementary file location
    ADLS Gen2 location of any supplementary files. 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
    If you intend to run command tasks within the Azure serverless runtime environment, create a folder named
    command_scripts
    within supplementary file location.
    For example, you would create the folder here:
    abfs://discaleqa@serverlessadlsgen2acct.dfs.core.windows.net/serverless/command_scripts
    For more information about command tasks, see "Command task steps" in
    Taskflows
    .
    Ensure that there are no extra spaces or special characters in the supplementary file location, because this might cause the deployment to fail.
    Data disks
    Access files in an NFS file system. Configuring a data disk in your serverless runtime environment allows you to access files in NFS directories. For more information about configuring data disks, see Working with data disks.
    Configure the following properties to configure a data disk:
    • Type. Only NFS directories are currently supported.
    • Server host/IP. The hostname or IP address of the NFS server.
    • Source mount. File system path to be mounted in the serverless runtime environment.
    • Target mount. File system to be mounted on the Secure Agent.
    • Mount options. If mount options are required, enter them in a comma-separated list in the following format:
      <key1>=<value1>
      ,
      <key2>=<value2>
    Custom properties
    Specific properties required for accessing the supplementary file location.
    Add the following custom properties and their appropriate values:
    • ServicePrincipalId
    • ServicePrincipalSecret. Check for accuracy, as the secret is masked once the configuration is saved.
    Informatica Global Customer Support
    might direct you to add other custom properties.
    If you clone an Azure serverless runtime environment, you need to re-enter the ServicePrincipalSecret because the original value is replaced by a masked string.
    You can't change the supplementary file location and custom properties once the configuration is saved. If you need to make corrections, clone the configuration. For more information about cloning, see Manage the serverless runtime environment.
  5. On the
    Runtime Configuration
    tab, enter properties that determine how the serverless runtime environment behaves.
    Don't make any changes to this tab unless directed by
    Informatica Global Customer Support
    .
  6. On the
    Tags
    page, create tags that help you categorize Azure resources and view consolidated billing.
    Enter as many tags as necessary as name-value pairs.
  7. On the
    Review+Create
    page, verify that all entries are correct and then click
    Create
    .
    If you need to go back to make corrections, click
    Previous
    to return to the appropriate tab.
    For more information on using and managing serverless runtime environments, see Serverless Runtime Environments on the Informatica Documentation Portal.

0 COMMENTS

We’d like to hear from you!