Design

Back Next

Updating field values for processes

You can use the update resource to update the values for the following fields for existing processes:

Allowed Users/Allowed Groups/Allow anonymous access

HTTP authorization requests from the API Gateway

Run On

Tracing Level

You can update fields for a single process or multiple processes. To update the processes using the update resource, you must be assigned the Admin, Deployer, Designer, or Operator role.

You can add the process and fields that you want to update as input data in a REST client such as Postman. The input data consists of the Global Identifier/Global Unique Identifier (GUID) of the process and a key-value pair of deployments to be updated. For more information about GUID, see the lookup resource and finding assets resource in

REST API Reference

in the Data Integration help.

To update the field values, use the following URL:

<Informatica Intelligent Cloud Services URL>/active-bpel/asset/v1/update?assetType=Process

You can add the input data as shown in the following sample:

PUT <baseApiUrl>/active-bpel/asset/v1/update?assetType=Process
Content-Type: application/json
Accept: application/json
INFA-SESSION-ID: <Infa-Session-ID>
{
  "processes": [
   {
      "guid": {
        "$t": "<guidvalue>"
      },
      "deployment": [
        {
          "key": {
            "$t": "Allow Anonymous Access"
          },
          "value": {
            "$t": "true"
          }
        },
        {
          "key": {
            "$t": "Run On"
          },
          "value": {
            "$t": "cloud server"
          }
        },
        {
          "key": {
            "$t": "Tracing Level"
          },
          "value": {
            "$t": "normal"
          }
        }
      ]       
    }
  ]
}

You can use the login resource to get the

INFA-SESSION-ID

. For more information about the login resource, see

REST API Reference

in the Data Integration help.

If the fields are successfully updated, you receive the following response:

{
    "status": {
      "$t": "SUCCESS"
    }
}

If you enter an invalid Secure Agent, you receive the following response:

{
  "status": {
    "$t": "FAILED"
  },
  "errorDetails": {
    "error": {
      "$t": "Update failed for assets"
    },
    "failedAssets": {
      "updateAssetFaultInfo": {
        "xmlns": "https://com.informatica.icrt/2021/08/updateAssets.xsd",
        "xmlns$aetgt": "https://com.informatica.icrt/2021/08/updateAssets.xsd",
        "name": {},
        "GUID": {
          "$t": "<Incorrect guid value>"
        },
        "fault": {
          "$t": "The Secure Agent is not valid. Specify a valid Secure Agent."
        }
      }
    }
  }
}

Rules and guidelines for updating fields in a process

Consider the following rules and guidelines when you use the update resource to update the fields in a process:

You must set either the Allowed Users/Allowed Groups or Allow anonymous access field at a time. Otherwise, an error occurs.

You must set either the HTTP authorization request from the API Gateway or the Allow anonymous access field at a time. Otherwise, an error occurs.

In the HTTP authorization request from the API Gateway and Allow anonymous access field, you must specify the value as true or false. If you specify any other value such as yes or no, an error occurs.

In the Tracing Level field, you must specify one of the following values: None, Terse, Normal, or Verbose. Otherwise, an error occurs.

If you set the HTTP authorization request from the API Gateway value to true, you must specify the value for the Run On (runtime environment) field as Cloud Server. If you specify the run on value as Secure Agent, an error occurs.

If you want to update the runtime environment value for a published process, you must first unpublish the process.

Setting Process Properties

Download Guide

Watch

Comments

Cloud Application Integration Homepage