IDMC Cloud Data Integration Job Log Capture > Using the IDMC CDI Job Log Capture recipe > Step 4. Configure the Taskflow and Processing
  

Step 4. Configure the Taskflow and Processing

The CDI Job Logs Taskflow calls an Application Integration process that extracts CDI Job Log information from a specified organization and writes it to a staging file location. By default, this staging location is set to /tmp on the machine where the Secure Agent is running. If job log records are extracted, a mapping task subsequently runs to transfer the data from the staging location to the target cloud storage. The taskflow is designed to either run once per day to retrieve the previous day’s data.
  1. 1Open the Get CDI Job Log process in Application Integration.
    1. aOn the Start tab of the Start step, select the Secure Agent from the Run On list.
    2. bOn the Temp Fields tab of the Start step, enter the target organization's base URL in the temp_baseOrgUrl field. For example, if you have logged in using https://dm-us.informaticacloud.com/identity-service/home, set this field value to https://dm-us.informatica.cloud.com/saas.
    3. cSave and publish the process.
  2. 2Open the Load Cloud Storage CDI Job Log Mapping mapping in Data Integration.
    1. aOn the Source tab of the srcReadJobLogStage step, select the flat file connection that points to your staging directory and the object as shown in the following image:
      2. The flat file connection and the object selected in the Source tab of the srcReadJobLogStage step.
    2. bOn the Target tab of the tgtCloudStorage step, select the cloud storage connection that points to your cloud storage location as shown in the following image:
      3. The cloud storage connection selected on the Target tab of the tgtCloudStorage step.
    3. cSave the mapping.
  3. 3Open the Load CDI Job Logs Mapping Task mapping task in Data Integration.
    1. aClick Edit.
    2. bFrom the Runtime Environment list, select the Secure Agent.
    3. cSave the mapping task.
  4. 4Open the CDI Job Log Taskflow taskflow in Data Integration.
    1. aOn the Start tab of the Start step, enter a valid user ID and/or group for the organization in the Allowed Users and/or Allowed Groups fields.
    2. bOn the IntegrationOps Task tab of the Get Job Logs step, reselect the Get CDI Job Log process and click Save.
    3. cOn the Input Fields tab of the Get Job Logs step, add all the input fields and assign field values as shown in the following image:
      4. The input fields configured for the Get Job Logs step in the CDI Job Log Taskflow taskflow.
    4. dSave and publish the taskflow.
    5. eTest the CDI job log using the Run Using option in Data Integration or with Postman.
      6. To test with the Run Using option, perform the following steps:
      1. aOn the Actions menu, click Run Using.
      2. bProvide inputs using the following JSON format:
        3. {
        "username": "<user name for org to get log files>",
        "password": "<password for org to get log files>",
        "startDateTime": "",
        "in_tgtPath": "<full path to cloud storage, including file name>"}
        Note:
        You can get the log files from a different organization than where you installed the package.
      3. cSave and run the taskflow.
      To test using Postman, perform the following steps:
      1. aOn the Actions menu, click Properties Details > Copy Service URL.
      2. bOpen Postman.
      3. cSelect the HTTP verb as POST and specify the generated REST service URL.
      4. dOn the Authorization tab, select Basic Auth and enter the user account details same as provided in the taskflow.
      5. eOn the Body tab, select the body type as raw and provide the following JSON snippet for the HTTPS request:
        6. {
        "username": "<user name for org to get log files>",
        "password": "<password for org to get log files>",
        "startDateTime": "",
        "in_tgtPath": "<full path to cloud storage, including file name>"}
      6. fSend the POST request.
        7. You will receive the taskflow run ID as a response.