Informatica Cloud - Application Integration (CAI/ICRT)

Other connections, please refer below videos:

JDBC : https://www.youtube.com/watch?v=747EkqZdXGk&list=PLonMTTEC0oeJWJsHqK_DicrzMU-7z3G3W&index=10

SFDC: https://www.youtube.com/watch?v=hwFH74OUVdg&list=PLonMTTEC0oeJWJsHqK_DicrzMU-7z3G3W&index=19

AMQP: https://www.youtube.com/watch?v=qkJVZGXAyYo&list=PLonMTTEC0oeJWJsHqK_DicrzMU-7z3G3W&index=22

Email: https://www.youtube.com/watch?v=1K78GqnKKu4&list=PLonMTTEC0oeJWJsHqK_DicrzMU-7z3G3W&index=25

AWS S3: https://www.youtube.com/watch?v=iYC_VePflxs&list=PLonMTTEC0oeJWJsHqK_DicrzMU-7z3G3W&index=26

• Create the  Process

• Save the Process

• Deploy the Process

• Consume the Process

A process uses the following default HTTP response headers:

• access-control-allow-credentials

• cache-control

• content-encoding

• content-type

• date

• expires

• keep-alive

• status

• strict-transport-security

• transfer-encoding

• vary

• x-frame-options

• x-http-status

• x-instanceid

You cannot override the names and values of the default headers.

• You can configure one of the following tracing levels to determine the type of run-time logging for a process:

  • None

  • Terse

  • Normal

  • Verbose

  The tracing level that you configure in Process Designer maps to the persistence level and logging level in Process Developer as listed in the following:

  
  Tracing-> Logging Level

  ---------------------------

  None   -> None

  Terse  -> Fault

  Normal -> Execution with Service Data

  Verbose-> Final->Execution with Data
  

  Persistence Level

  Regardless of the tracing level that you configure, Process Server uses full persistence in the following situations:

  • When you select the Suspend on Uncaught Fault option

  • When a process includes a timer such as a Wait step, a message event, or a receive event

  • When one process invokes another process to provide subprocess coordination.

  For more information about different persistence levels, see Monitor.
  

  Logging Level

  The Process Server logging level might be lower than the logging level that you set for an individual process. Regardless of the logging level that you set at the process level, the logging will not exceed the maximum process logging level specified for the Process Server. The tracing level table illustrates the mappings between the logging level and the persistence level.

  For more information about different logging levels, see the Administrator online help.

• Pause at a specific time: pause the process at a particular time. For example, set the process to pause at 1:00 am after three days. 1:00 am is the Time and three days is the Delay

• After a wait period: Pause the process for a few Seconds/Minutes/Hours. 

Milestone: Sends Synchronous Response to the consumer.
Milestone is used to make the transaction ASynchronous.

Example: When a consumer does the POST call to API,  it will expect some response from the API, due to that consumer has to wait a few seconds until the transaction is completed from the API. this process is called a Synchronous API call. To make Synchronous to ASynchronous we use milestone. i.e. Fire and forget

When consumers don't require any response from the API, we can add a milestone in the CAI process to give the HTTP 200 response back to the consumer at the very first step of IICS so consumers do not need to wait for the process to be completed. it will save wait time

HTTP Status

Displays the HTTP response status code. The default value is 200 OK. You can edit this value.

HTTP Response Headers

Specifies the HTTP response headers and values that the REST API associated with the process must return after the process runs. For example, you can configure a response header to return the organization ID. You can consume the header value that the process returns in downstream applications.

You can add the values manually or enter a formula. A process uses the following default HTTP response headers:

• access-control-allow-credentials

• cache-control

• content-encoding

• content-type

• date

• expires

• keep-alive

• status

• strict-transport-security

• transfer-encoding

• vary

• x-frame-options

• x-http-status

• x-instanceid

You cannot override the names and values of the default headers.

After the process runs, the API returns the HTTP response headers that you configured. You can view the response headers on the My Processes page in Application Integration or on the Processes page in Application Integration Console.

A Subprocess step embeds one process within another process. When the Subprocess step executes, the embedded process executes.

When you have a process that contains numerous steps, consider splitting the orchestration logic across multiple smaller processes. You can then simplify the design by using the Subprocess step to embed the smaller processes in the parent process. This not only leads to modular design but also helps with faster loading when you open the process for editing.

Service step used in the process to add the connection, subprocess, or system service.

System service includes
   1. Calling CDI mappings task/LTF

   2. Calling Unix/Powershell scripts

The decision step allows a process to take different paths depending on the conditions.

For example, you create a Data Decision step with the following paths:

• Path 1: Field less than or equal to 100.

• Path 2: Field less than or equal to 75.

• Path 3: Field less than or equal to 25.

• Path 4: Otherwise

If the integer field for which the Data Decision step was created has a value of 25, the Data Decision step takes path 1. This is because 25 is less than 100 and path 1 is the first option.

To ensure that the Data Decision step follows the "Field less than or equal to 25" path, re-create the paths with the following criteria:

• Path 1: Integer between 0 and 25

• Path 2: Integer between 26 and 75.

• Path 3: Integer between 76 and 100.

• Path 4: Otherwise

Important

: The process evaluates conditions in a top-down manner. Ensure that the Otherwise branch is the last path.

Jump Path is used to control the flow execution control from one point to another point in the process.
it is mainly used for looping/iteration purposes.

Parallel Path is used in the process of Executing tasks simultaneously, in order to reduce the time it takes to complete an entire suite of operations.

Rules:
1. When you use a Parallel Paths step, all the steps in all the branches will not start at the same time. There will be a time lag in the start time of the steps in all the paths. The execution of branches varies based on the steps used in each branch.
2. When more than one branch is running in sequence, if one branch pauses for a specific time, instead of waiting for the steps to be completed in that branch, the process starts running steps from another branch in parallel.
3. You can add multiple steps to each branch. To add steps to a branch, drag and drop a step from the palette on the left.

4. When you use the Jump step in conjunction with the Parallel Path step, you can only jump to another step on the same Parallel Path branch. Keep in mind the following restrictions when you use the Jump step and the Parallel Path step together:

• If you are in a Parallel Path step, you cannot jump to a step on another branch of the same Parallel Path step.

• If you are in a Parallel Path step, you cannot jump to any step outside the Parallel Path step.

• If you are outside a Parallel Path step, you cannot jump to any step inside the Parallel Path step.

fn:doc('C:\Users\IICS\XQuery\sample.xml') -> Payload

fn:doc-available('C:\Users\IICS\XQuery\sample.xml') -> true/false

fn:unparsed-text('C:\Users\IICS\XQuery\sample.xml') -> Payload

fn:unparsed-text-available(C:\Users\IICS\XQuery\sample.xml') -> true/false

File1:
<root><row><id>1</id><name>John</name><state>TX</state></row><row><id>2</id><name>Martin</name><state>FL</state></row><row><id>3</id><name>Kohl</name><state>NJ</state></row><row><id>4</id><name>Randy</name><state>CA</state></row><row><id>5</id><name>Kyle</name><state>NY</state></row></root>

File2:
<root><row><id>1</id><salary>10000</salary><pay>monthly</pay></row><row><id>2</id><salary>8000</salary><pay>monthly</pay></row><row><id>3</id><salary>12000</salary><pay>monthly</pay></row><row><id>4</id><salary>9000</salary><pay>monthly</pay></row><row><id>5</id><salary>11000</salary><pay>monthly</pay></row></root>

XQuery:
let $x:= fn:doc('C:\Users\IICS\XQuery\sample.xml')

let $y:= fn:doc('C:\Users\IICS\XQuery\details')

return

<root>

{

for $i at $d in $x//row

return

<empoyee>

<id>{$i/id/text()}</id>

<index>{$d}</index>

<name>{$i/name/text()}</name>

<monthly_salary>{$y//row[id=$i/id/text()]/salary/text()}</monthly_salary>

<Address>{$i/state/text()}</Address>

</empoyee>

}

</root>