![[V5.0.8 or later]](../buildfiles/icon_v508.jpg)
How to export Portal Delegated User Registry user information
From IBM® API Connect Version 5.0.8.7 onwards, if your Developer Portal uses Portal Delegated User Registry, you can export the user information that is stored in the Developer Portal local database.
Before you begin
You must have administrator access to complete this task.
Note: The ability to migrate Portal Delegated User Information is available
only from IBM API
Connect Version 5.0.8.7 onwards. If your deployment is at an earlier version, you
must upgrade to Version 5.0.8.7 or later before migrating. See Upgrading your API Connect cloud for information about
upgrading in Version 5.
About this task
When Portal Delegated User Registry (PDUR) is selected for a Catalog, the user management is delegated from the management server to the Developer Portal. In this instance, if you want to migrate users from an IBM API Connect Version 5 Developer Portal, to an IBM API Connect Version 2018 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.
The following two methods can be used for exporting the PDUR user information:
- You can use the Developer Portal UI to export the PDUR user information on a per site basis into a .json user-mapping file. If you have more than one site, before the user information can be used by the migration tooling you must manually combine the .json files into one compressed pdurexport.tgz file.
- You can use a Developer Portal CLI command to export the PDUR user information for all of the sites on a Developer Portal server into a pdurexport.tgz file. This compressed file will contain all of the .json user-mapping files for that server.
Note: User-mapping files
must not be edited, or the migration may not complete successfully.