Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. Configuring Metadata Caching

Upgrading from Version 9.7.1

Upgrading from Version 9.7.1

Configure the MDM Identity Services for ActiveVOS

Configure the MDM Identity Services for ActiveVOS

If you use embedded ActiveVOS, ensure that you configure ActiveVOS to use MDM Identity Services. To configure the MDM Identity Services for ActiveVOS, use the ActiveVOS Console to set the Identity Services password to the password of the MDM Hub workflow engine user.
  1. In the ActiveVOS console, select
    Admin
    Configure Services
    Identity Services
    .
  2. In the Provider Configuration section, enable the
    Enable
    check box and select
    MDM
    from the
    Provider Type
    list.
  3. In the Connection tab, enter the password of the MDM Hub user with the user name
    admin
    .
    If you later change the password for the admin user, you must enter the new password in the ActiveVOS identity services settings.
  4. Click
    Update
    .
  5. Test that ActiveVOS can log in to the MDM Hub as the
    admin
    user, and that ActiveVOS can retrieve a list of roles for the user you specify as the
    User for test
    .
    1. Select the
      Test
      tab.
    2. In the
      User for test
      field, enter an MDM Hub user that is assigned to a role.
    3. Click
      Test Settings
      .
      The test fails if an Operational Reference Store is not configured, the user for test does not belong to a role, or the role name contains spaces.

0 COMMENTS

We’d like to hear from you!