Deploying and Testing iFlows

Deploy Your iFlow PurchaseOrder.

1. Navigate to your package and the created artifacts in the Artifacts tab.

   

2. Deploy the PO_Slack iFlow by choosing Actions → Deploy.

   You will receive a confirmation of your request and its success (or failure).

   

3. Deploy the PurchaseOrder iFlow by choosing Actions → Deploy.

   You will receive another confirmation of your request and its success (or failure).

   

Perform a preparation step: replace the Timer element by a Start Message element.

1. Open the iFlow PO_Slack.

2. Replace the Timer element by a Start Message element

3. Connect the Sender PurchaseOrder to Start Message

4. As Adapter choose Process Direct.

5. In the Connection tab, as address enter/PO_scenario/PO_Slack as address.

6. Re-deploy both iFlows PO_Slack and PurchaseOrder.

Monitor the iFlow.

1. Navigate to the Monitor section on the left menu bar. You are now able to see your integration content, how messages were processed, manage security, stores and locks. While ideally no errors are presented, if so, they are directly visible in the Failed Messages section.

   

2. Choose the Manage Stores - Data Stores tile to view the SOAP message that was saved to the data store. The status Waiting indicates that the entry has been successfully written into the data store (and is waiting to be consumed by another integration flow). You can choose Download to view the message.

   

3. Return to the Monitor overview. Choose Monitor Message Processing → All Integration Flows - Messages to view the deployed iFlow and the SOAP message that is being persisted within the data store. Click around the page to get familiar with the setup. You will notice that only an overview is provided – the message payloads, for example, are not available. CI offers different Log Levels that can be separately activated (prior to redeploying an iFlow) to gather additional information. The default level is Info.

   

Explore the Process Steps.

1. From the Overview, choose Manage all integration content → All. Select your iFlow. Set Trace as the log level.

   

2. Redeploy your iFlow and go back to Monitor Message Processing → All Integration Flows - Messages.

3. Select the PurchaseOrder artifact and then on the Trace log level.

   

4. You will now be able to explore each process step and the message payloads in detail.

   Note

   By clicking on a particular process step, you are viewing the payload before the process step is executed.

   Example

   

   Make use of the Debug and Trace log levels to pinpoint any errors you might have within the integration flow. The provided error messages will give you insight into the problem at hand. We also suggest going back to the individual lessons and re-reading the instructions carefully.

   You can also import the solution package (to be found in the "provided_integration_content" folder as a zip file) directly into your Design tab on your own tenant to compare. In this case, be sure to configure the iFlow to use your own APIkey as shown in Unit 3 before deploying the artifacts.