Migrating Activity Definition

Update existing activities to use the new context rest instead of the deprecated contexts like pemws, mrmws, and mdrws.

Note:

Migration is triggered only if the activity contains old contexts.

  • Identify the API configurations used for PEM Portal and Partner Repository.
  • Update the host and port fields in these API configurations to point them to API Gateway.

For example, a public URL end-point pr.pem.ibmcloud.com configure it to api.pem.ibmcloud.com for PEM cloud.. For more information on creating an API configuration, seeConfiguring API .

To migrate existing APIs, perform the following:

  1. Sign in to the PEM Portal as a System Administrator.
  2. Select Directory > Sponsors.
  3. To edit a sponsor property, go to Actions > Configure Properties > General System Properties and click Edit.
  4. To migrate existing activities to use API Gateway, set the following properties:
    Property Description
    IS_API_GATEWAY_ENABLED True
    ENABLE_API_GATEWAY_ACTIVITY_MIGRATION False
    Note: To disable automatic activity migration, set this property to True. You can choose Skip Migration, if you want your activities to be not migrated or select Migrate, if you want your activities to be compatible with the new API Gateway, during the Save as draft or Mark as final action.
    Note:
    • Before you start migration,ensure you are not in the test mode. In test mode, changes are made to the test mode database and are unavailable in the master database.

    • To migrate your activities, you can either select Save as Draft or Mark as final and in the pop-up window, select OK. The changes made by the migrator are Irreversible. The status of the API migration is available in the Migration Status field. Ensure your API gateway is up and running before you edit the System Configuration.

    • The IS_API_GATEWAY_ENABLED property is false by default for every sponsor unless the system level property is set to True.