API Connect

Expand all | Collapse all

Portal analytics in APIC V10 for Portal delegated User registry

  • 1.  Portal analytics in APIC V10 for Portal delegated User registry

    Posted 28 days ago


    We are currently having a fer portal in APIC v5 which use portal delegated user registry. As of now, using PDUR does not support viewing portal analytics in developer portal. 

    I would like to know whether this would feature to view analytics be supported if we migrate APIC v10.

    Also if anyone knows how the capability can be enabled in V5.0.8.7 or higher, then please share that too.


    Vaibhav Mehra

  • 2.  RE: Portal analytics in APIC V10 for Portal delegated User registry

    Posted 26 days ago
    Edited by Nick Cawood 26 days ago


    In APIC v10 Consumer Analytics for APIs are visible within the Portal either at an App or Consumer Organization level.
    Knowledge Center is helpful here: https://www.ibm.com/support/knowledgecenter/en/SSMNED_v10/com.ibm.apic.devportal.doc/capim_portal_analyticsparent.html

    In APIC v10 the concept of PDUR no longer exists so during migration from v5 an extract of the PDUR data is required and the API Connect Migration Utility (AMU) can migrate that data into APIC v10.

    Knowledge Center  explains this in more detail: https://www.ibm.com/support/knowledgecenter/en/SSMNED_v10/com.ibm.apic.install.doc/migration_pdur.html

    "In IBM API Connect Version 5, when Portal Delegated User Registry (PDUR) was selected for a Catalog, the user management was delegated from the management server to the Developer Portal. The site administrator within the Portal site then performed the configuration. The management server recorded that the delegation had taken place, and stored a record of the users which existed in the catalog. However, the management service maintained no information about the configuration of the specific registries or how users mapped to them.

    PDUR in IBM API Connect v5 was highly configurable. A single Portal site (catalog) could be configured to use multiple different registry types or different registries of the same type. Details of this configuration, and which users map to which registry, is all stored in the Portal.

    However, IBM API Connect Version 10 and later supports new registries, and no longer needs the PDUR. Instead, functionally equivalent registries can be configured in v10 and used. To migrate the PDUR user registries and users from v5 to v10, we must gather configuration information from both the management server and the Portal node.

    PDUR supported 4 different types of user registries. The following table shows the mapping of these types to the v10 equivalents:

    Table 1. Mapping of Registry types
    v5 PDUR Registry v10 Equivalent Registry
    HybridAuth OIDC
    Local User Registry (LUR) Local User Registry (LUR)

    In this scenario, if you want to migrate users from an IBM API Connect V5 Developer Portal to an IBM API Connect v10 Developer Portal, you must export the user information that is stored in the Developer Portal local database. This information can then be used by the migration tooling to migrate the PDUR user registry. You complete this action after you have exported the v5 configuration database for the management server."

    I will leave others to comment on your question regarding v5.0.8.7.

    Best Regards,


    Nick Cawood
    Software Consultant