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. Hierarchies Upgrade
  13. ActiveVOS Post-Installation Tasks for the Application Server
  14. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  15. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  16. Appendix A: Troubleshooting the Upgrade Process
  17. Appendix B: Frequently Asked Questions
  18. Appendix C: Processing Existing ActiveVOS Tasks
  19. Appendix D: Configuring Metadata Caching

Upgrading from Version 10.1, 10.2, 10.3, or 10.4

Upgrading from Version 10.1, 10.2, 10.3, or 10.4

Create the ActiveVOS Console Administrative User

Create the ActiveVOS Console Administrative User

If you want to use ActiveVOS, create the ActiveVOS Console administrative user with the
abAdmin
role in the application server container.
If you want to use ActiveVOS, create the ActiveVOS Console administrative user with the
abAdmin
role.
If you do not create an administrative user, the Hub Server deployment fails. Use the ActiveVOS Console administrative user name and password when the Hub Server installer prompts you to enter the administrative user credentials for the ActiveVOS Console.
  1. Change to the following directory:
    <
    JBoss installation directory
    >/bin
  2. To run the add-user utility, use the following script:
    On UNIX.
    add-user.sh
    On Windows.
    add-user.bat
  3. Answer the prompts that appear.
    The following table describes the values to specify for each prompt:
    Prompt
    Value to Specify
    What type of user do you wish to add? a) Management User or b) Application User
    To select Application User, enter
    b
    .
    Realm (ApplicationRealm)
    Realm name. Enter the realm name that you specified in the
    login-module
    that you added to the
    standalone-full.xml
    file.
    Username
    ActiveVOS Console administrator name.
    Password
    Password that complies with the JBoss password standard.
    What roles do you want this user to belong to?
    abAdmin
    .
    About to add user <user name> for realm <realm name>. Is this correct?
    To add the user, enter
    yes
    .
    Is this new user going to be used for one AS process to connect to another AS process?
    yes
    .
  4. Log in to the WebSphere console, and create the ActiveVOS Console administrative user.
    The ActiveVOS console user is mapped to the
    abAdmin
    role when you run the
    postInstallSetup
    or the
    patchInstallSetup
    script during the post-installation or post-upgrade process.
  5. Log in to the WebLogic console.
  6. Create the
    abAdmin
    role.
  7. Create the ActiveVOS Console administrative user.
  8. Assign the administrative user to the
    abAdmin
    role

0 COMMENTS

We’d like to hear from you!