PingIntelligence

Adding the PingIntelligence policy components

Add the PingIntelligence policy components to your API.

Before you begin

Make sure to:

  1. Download the PingIntelligence policy from the Ping Identity Downloads site.

  2. Extract the policy by using the following command:

    # tar –zxvf  <<file name>>

    For example:

    # tar –zxvf pi-api-ibm-policy-4.1.0.tar.gz

About this task

To add the PingIntelligence policy components:

Steps

  1. Sign on to IBM API Manger.

    A screen capture of the IBM API Connect API Manager sign-on page.

  2. To open the navigation pane, click the Menu bgq1582013473323 icon on the top-left corner.

    A screen capture of the left navigation menu icon with a red arrow pointing to it.

  3. Click Drafts in the navigation pane.

    A screen capture of the Drafts link selected in the left navigation with a red box around it.

  4. Click the APIs tab.

    A screen capture of the APIs tab with a red box around it.

  5. Click on your API under TITLE list or enter the API name in the Search APIs dialog box and select the API.

    A screen capture of the APIs tab with a red arrow pointing to the Search APIs field and a red box around the API Title list.

  6. Click the Source tab to edit your API definition.

    A screen capture of the Source tab with a red box around it.

  7. Copy and paste the contents of the PingIntelligence policy into the Assembly block of your API definition at three places:

    1. Open the pi_policy.yaml file, copy the contents of the set-variable: block with the ASE Config component and paste it in the next line after the execute: block in your API.

      A screen capture of the source editor with a red arrow pointing to set-variable.

    2. Next, copy the contents of the gateway script: block containing the ASE Request component from the pi_policy.yaml file and paste it after the last line of the ASE Config component.

      A screen capture of the source editor with a red arrow pointing to the value.

    3. Copy the contents of the gateway script: block containing the ASE Response component from the pi_policy.yaml file and paste it as the last component of your API.

      A screen capture of the source editor with a red arrow pointing to title.

      The assembly component ASE Reponse should always be the last component of your policy assembly.

  8. Click the Validate hmn1582038060999 icon to validate your changes, and then click the Save qsf1582074751032 icon after completing the validation.

  9. Click the Assemble tab to open the Assemble view. Verify the sequence of the components ASE Config, ASE Request, and ASE Response in the Policy Assembly.

    The order must match as highlighted in the red boxes in the following image.

    A screen capture of the Assemble page with red boxes around ASE Config, ASE Request, and ASE Response.