Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Pre-Installation Tasks
  4. Hub Store Installation
  5. Hub Server Installation
  6. Hub Server Post-Installation Tasks
  7. Process Server Installation
  8. Process Server Post-Installation Tasks
  9. ActiveVOS Post-Installation Tasks for the Application Server
  10. ActiveVOS Post-Installation Tasks for the Business Entity Adapter
  11. Customize ActiveVOS
  12. Troubleshooting the MDM Hub
  13. Uninstallation

Installation Guide for Microsoft SQL Server with Red Hat JBoss

Installation Guide for Microsoft SQL Server with Red Hat JBoss

Create a Trusted User in JBoss Environments

Create a Trusted User in JBoss Environments

To use the ActiveVOS workflow engine, create a trusted user assigned with the role of abTrust, abServiceConsumer, and abTaskClient in the application server. MDM Hub and ActiveVOS trust the trusted user. For secure communication .
The trusted user is the same user as the ActiveVOS workflow adapter user in the Hub Console, but its username must differ from the application server's administrative user. To set up the trusted user, complete the following steps:
  1. From the command prompt, run the Add User script:
    • On UNIX:
      <JBoss install directory>/bin/add-user.sh
    • On Windows:
      <JBoss install directory>\bin\add-user.bat
  2. Respond to the prompts that appear. The prompt displays the default value in brackets.
    1. Select
      Enter
      to use the default value and to move to the next prompt.
    2. When prompted about the type of user, select b for the Application User.
    3. For the Realm, enter the realm name that matches the one specified in the login module you configured in the
      standalone-full.xml
      file.
    4. Enter the user name of the trusted user.
    5. Enter a password that complies with the JBoss password standards.
    6. Specify the roles with the following entries:
      abTrust
      ,
      abServiceConsumer
      ,
      abTaskClient
      .
    7. Confirm the addition of the user by entering yes when prompted.
    8. If asked whether this user will be used for one AS process to connect to another, enter yes.
  3. To apply the necessary changes, restart the Application Server.

0 COMMENTS

We’d like to hear from you!