Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Migrating the access control configuration

To complete access control migration, perform manual steps to migrate permissions on specific users and groups, and credential vault data. Also, when migrating from version 5.0.2.2 or 5.0.2.3, you need to migrate permissions of administrative resources.

• Migrating permissions on All Authenticated Users and All Portal User Groups
  On the current WebSphere Portal Express system, there are three ways to assign the principals to roles on the appropriate user groups: the User and Group Permissions portlet, the Resource Permissions portlet, and the XML configuration interface.
• Migrating permissions on administrative resources
  If you are migrating from WebSphere Portal Express V5.0.2.2 or V5.0.2.3, you need to note the access control settings for your previous version and then recreate them in the current version.
• Migrating credential vault data using the XML configuration interface
  When you migrated the configuration, credential vault slots and segments were also migrated. To complete the process, you need to migrate existing credential secrets by exporting them from the earlier version and importing them into the current version. If you do not migrate existing credential vault secrets, users must provide their credential information the first time a Version 6.1 portlets attempts to use the data.
• Migrating credential vault data using SQL and direct database operations
  Migrating the credential secrets involves moving two tables, VAULT_DATA and VAULT_RESOURCES, from the earlier version database to the current database. The table definition has not changed in WebSphere Portal Express Version 6.1, so the data does not need to be changed. However, because the database is now split into different database domains, the data also has to be split. Use an import and export utility that is provided by the database server.