Contact Us 1-800-596-4880
  1. Homepage
  2. Exchange
  3. Publish Assets

  4. Add Policy Implementation Files to Published Custom Policy

Add Policy Implementation Files to Published Policy Definition

When a policy definition asset is published in Exchange, the asset details page displays a Pending flag next to Implementations in the left navigation bar. The flag indicates that the policy implementation has not been added. Add the policy implementation files to the policy definition to enable the policy to be available in runtime. The required implementation files are a binary file such as a WebAssembly (WASM) file for Flex Gateway or JAR for Mule 4 runtime and a YAML metadata file.

Before adding the policy implementation files, ensure that the policy definition asset is in the Stable state.

To add the policy implementation files:

  1. In Exchange, select the policy asset to open the asset details page.

  2. Click Implementations in the left navigation bar.

  3. Click Add implementation.

  4. Enter the name for the implementation.

  5. Click Choose file to select the JAR or WebAssembly file.

  6. Click Choose file to select the YAML file.

  7. To edit the GroupId, AssetId, Version, and API version, click Advanced.

    Exchange generates the group ID, asset ID, and version. You can change these values. You can also change an API asset’s version and API version separately. The advanced settings are most often used to change the asset version.

  8. Click Add implementation.

    The implementation displays in the Manage implementations table. From this table, manage the implementation versions of a policy asset. See Manage Versions for more information.