Policy Manager/Community Manager Feature Matrix

This document provides information on features that were previously only available in Policy Manager and are now available within the Community Manager developer portal.

Note: Functionality available in the Community Manager developer portal corresponds to functionality available in Policy Manager at the tenant level and below. Any activities at a higher level than tenant level must be done in Policy Manager.

Functions available in both Policy Manager and Community Manager

The tables below list functions that were (and are) available in Policy Manager but are also available in the Community Manager developer portal. Each table has a legend below it with more detailed information on navigation, and links to more information in most cases.

Functions are grouped as follows:

Managing setup and configuration

Feature PM CM Notes
Configure Network Director Setup_01_PM Setup_01_CM

Generally, the ND is installed and configured as part of installation.

In the Community Manager developer portal, ND instances are registered under the tenant root organization or sub-organization.

There is no visibility from CM to NDs created outside the tenant. If the ND is created within the context of a specific organization, there is no visibility outside that organization. In PM it appears in the hierarchy as follows: Tenant > Container or Tenant > Organization > Container.
Create Network Director Cluster Setup_02_PM Setup_02_CM

ND clusters configured in the Community Manager developer portal are created under the tenant root organization or sub-organization.

A cluster must include at least one container.
Modify container listener Setup_03_PM Setup_03_CM In CM, you can modify a container listener for the tenant root organization or sub-organization.

The list below gives navigation and additional information for the numbered tasks listed in the table above.

Managing organizations

Feature PM CM Notes
Create organization; add, view, modify, delete, create child organizations, manage hierarchy org_01_PM org_01_CM Organizations created in Policy Manager are not visible in the Community Manager developer portal.
Create user roles, modify user roles, assign users to roles org_02_PM org_02_CM  
Add processes to an organization org_03_PM org_03_CM  
Create scripts, add scripts to an organization org_04_PM org_04_CM  
View monitoring data for all APIs in an organization org_05_PM org_05_CM*

PM provides monitoring alerts and logs at the tenant, container, or registry level, depending on permissions.

CM provides different metrics for top APIs when viewing metrics for an API, but does not display all organizational usage/response data for the tenant organization.
Create an anonymous contract for an organization org_06_PM org_06_CM* *For CM, not available at the Organization level, only the API Implementation level.
Move APIs between organizations org_07_PM org_07_CM  
Add and manage policies for an organization: Operational Policy, Operational Script Policy, or QoS Policy org_08_PM org_08_CM  
Export Metric Data through UI (for an organization) org_09_PM org_09_CM  

The list below gives navigation and additional information for the numbered tasks listed in the table above.

  • Create organization; add, view, modify, delete, create child organizations, manage hierarchy:
    • org_01_PM: In Policy Manager: Tenant > Add Organization. See Add Organization.

      Note: If you add an organization in PM, it isn't visible in CM.

    • org_01_CM: In Community Manager: Organizations > Add. See Organizations
  • Manage organization security:
    • org_02_PM: In Policy Manager: choose Security > Users (see User Administration) and Security > User Groups (see User Group Administration). This sets users and groups at the registry level. You can also do it at the tenant level and at the organization level.
    • org_02_CM: In Community Manager: Organizations > choose organization > Security. See Business Security.
  • Add and edit processes in the context of an organization:
  • Add and edit scripts in the context of an organization:
  • View monitoring data for all APIs in an organization:
  • Create an anonymous contract for an organization:
    • org_06_PM: In Policy Manager: Organization > Contracts (Consumed or Provided) > Offer Contract. Under Access Control, choose Allow consumer (application or organization) users that do not have a contract specifically assigned.
    • org_06_CM Not available at Organization level. For an API implementation: API > Implementation > Edit > Allow Anonymous Access.
  • Move APIs between organizations:
    • org_07_PM: In Policy Manager: Organization > Services > choose specific service. On the right, in the Actions section, choose Change Organization. Choose the organization to move it to.
    • org_07_CM: In Community Manager: Organizations > choose organization > choose API > Edit. Change Parent Organization Name. See How do I move an API from one organization to another?
  • Add and manage policies for an organization:
    • org_08_PM: In Policy Manager: Organization > In the center pane, in the Policy Attachments section, add, change, and delete the policies. See Managing Policies.
    • org_08_CM: In Community Manager: Organizations > choose organization > Policies. See Business Policies
  • Export metric data through UI for an organization:
    • org_09_PM: In Policy Manager: choose organization > Monitoring > Logs, click Export Usage Records.
    • org_09_CM: In Community Manager: Organizations > choose organization > Actions > Export. See How do I export organization information?

Managing APIs

Feature PM CM Notes
Create API API_01_PM API_01_CM

In PM you can add APIs in the Services folder for the organization.

In CM, when you add an API, it shows up in PM under the tenant organization. APIs and other assets, such as organizations, are listed together, and are distinguished by a unique icon for each asset type.
Add and edit processes in the context of an API API_02_PM API_02_CM  
Assign scripts to an API API_03_PM API_03_CM  
Attach policies to an API API_04_PM API_04_CM  
Modify physical endpoint for an API API_05_PM API_05_CM  
Monitor analytics for an API API_06_PM API_06_CM  
Export metric data for an API (through UI) API_07_PM API_07_CM  
Export API API_08_PM API_08_CM  
Create anonymous contract for an API API_09_PM API_09_CM  
Configure propagated headers on a virtual API API_10_PM N/A  

Manage Identities support on virtual API:

Use virtual service identity for outbound HTTPS

 API_11_PM N/A  
Modify listener API_12_PM API_12_CM  

The list below gives navigation and additional information for the numbered tasks listed in the table above.

  • Create an API:
    • API_01_PM: In Policy Manager: Under the tenant organization, Services > Create Physical Service or Create Virtual Service. See Registering an API.
    • API_01_CM: In Community Manager: Plus icon > Add API. See Adding an API.
  • Add and edit processes in the context of an API:
  • Add and edit scripts in the context of an API:
  • Attach policies to an API:
    • API_04_PM: In Policy Manager: Choose service > Policies. On the right, click the tab for the policy type. Click Add Policy. See Managing Policies.
    • API_04_CM: In Community Manager: API > choose implementation > choose resource > Edit Process. Choose scripting. See Managing Policies for an API Implementation.
  • Modify physical endpoint for an API:
    • API_05_PM: In Policy Manager: Services > choose physical service. On the right, click Access Points tab. Choose Actions > Modify Access Point. In the Modify Access Point wizard, page 2, on the Specify HTTP Details page, in the Location field, modify the endpoint.
    • API_05_CM: In Community Manager: API > choose implementation > choose resource > Edit Process. See How do I add or modify a target endpoint for an implementation?
  • Monitor analytics for an API:
    • API_06_PM: In Policy Manager: Choose virtual service > Monitoring tab > Logs / Real-Time Charts / Historical Charts.
    • API_06_CM: In Community Manager: API > Analytics. Choose scripting. See Monitoring API Analytics.
  • Export metric data for an API (through UI):
    • API_07_PM: In Policy Manager: Choose virtual service > Monitoring tab > Logs. Choose Export Usage Records to schedule; choose Manage Exports to download. Also: Monitoring tab > Historical Charts. Choose data range, and click Export to download.
    • API_07_CM: In Community Manager: API > Analytics > Overview. See Monitoring API Analytics.
  • Export API:
    • API_08_PM: In Policy Manager: Choose service > Details tab > in right pane, under Actions, choose Export Service.
    • API_08_CM: In Community Manager: API > Details > Export. See How do I export an API?
  • Create anonymous contract for an API:
    • API_09_PM: In Policy Manager: Choose service > Details tab > in right pane, under Actions, choose Offer Contract. On the Specify Contract Details page, choose Allow Consumer (application or organization) users that do not have a contract explicitly assigned. The contract is created in the Contracts folder for the organization that the API is in, under Provided Contracts. Click Manage Contract Scopes and modify scope as needed. Then, activate the contract. Can also be done at the Organization level: Organization > Contracts folder. On right, under Provided Services Contracts, click Offer Contract.
    • API_09_CM: In Community Manager: API > Implementation > Edit > check Allow Anonymous Access box.
  • Configure propagated headers on a virtual API:
    • API_10_PM: In Policy Manager: API virtual service > Details tab. In right pane, under Actions, click Configure Message Processing. Choose Preserve Transport Headers.

      Note: Propagation of headers might be further limited by security settings restricting the propagation of specific headers: see Header Propagation in Network Director (Platform Hardening doc).

    • Configuration of propagated headers is not currently available in Community Manager.
  • Manage Identities support on virtual API:
    • API_11_PM: In Policy Manager: API > Details tab > in Actions, Manage Outbound Identities.
    • API_11_CM Not currently supported. Expected in an upcoming release.
  • Modify listener:

Managing apps

Note: An Organization Identity in PM is the equivalent to an App in CM, but they are not interchangeable. Apps created in PM must be continually managed in PM, so the certificate needs to be added in PM. For new resources, we recommend creating Apps in CM. The table below includes instructions for managing legacy Organization Identity objects in PM as well as apps in CM.

PM Feature PM CM Feature CM
Create an organization Identity in PM app_01_PM Create an app in CM app_01_CM
Upload certificate to an Organization Identity app_02_PM Upload certificate to an app app_02_CM
Create Access (contract) between Organization Identity and API in PM app_03_PM Create Access (contract) between App and API in CM app_03_CM
View monitoring data for an API an Organization Identity is contracted with: app_04_PM View monitoring data for an API an app is contracted with app_04_CM
Export metric data through UI (for an Organization Identity): app_05_PM Export metric data through UI (for an app): app_05_CM
  • Create an Organization Identity in PM:
    • app_01_PM: Workbench > organization > Details tab. On the right, in the Actions section, choose Add Organization Identity.
  • Create an app in CM:
  • Upload certificate to an Organization Identity:
    • app_02_PM: Workbench > organization > In center pane, choose organization identity. In the Actions drop-down, choose Manage PKI Keys.
  • Upload certificate to an app:
  • Create Access (contract) between Organization Identity and API in PM:
    • app_03_PM: Workbench > organization > Contracts > Provided Contracts. On the right, in the Actions section, choose Offer Contract.
  • Create Access (contract) between App and API in CM:
  • View monitoring data for an API an Organization Identity is contracted with:
    • app_04_PM: Choose virtual service > Monitoring tab > Logs / Real-Time Charts / Historical Charts.
  • View monitoring data for an API an app is contracted with:
  • Export metric data through UI (for an Organization Identity):
    • app_05_PM: In Policy Manager: choose organization > Monitoring > Logs, click Export Usage Records.
  • Export metric data through UI (for an app):

Functions that are available only in Community Manager and cannot be done in Policy Manager

Currently, it isn't possible to modify an OAuth Provider domain or OpenID Connect domain in Policy Manager. These changes must be made in Community Manager.