Opening Decision Center on the sample server

The sample server runs samples and tutorials that demonstrate Decision Center features.

To use the samples and tutorials, you must have Decision Center and the sample server installed on your computer. The sample server includes predefined databases for Decision Center. The databases contain sample decision services in American English (en_US). Make sure that you start the sample server in the en_US locale.

To work with the samples and tutorials in Decision Center:
  1. Start the sample server with one of these methods on :
    • Windows:
      • Windows 10: Start > All Programs > <ODM> > Start Sample Server
      • Windows 11: Start > All apps > <ODM> > Start Sample Server

      The variable <ODM> refers to the package group specified in IBM® Installation Manager during installation. The default package group is Operational Decision Manager V8.12.0.

    • In the Samples Console, click the Start the sample server icon (see Starting and stopping the sample server).

    Note: If you are using Mac OS or UNIX, you can find an executable file in the <InstallDir>/shared/bin directory.
  2. Use one of these methods to open the Decision Center consoles:
    • From the Start menu:
      • Windows 10: Start > All Programs > <ODM> > <console>
      • Windows 11: Start > All apps > <ODM> > > <console>
      Click one of the following for the console:
      • Decision Center Business console
      • Decision Center API console

    • For a web browser, enter the URL for a console as follows:

      • Business console: http://localhost:<PORT>/decisioncenter/
      • API console: http://localhost:<PORT>/decisioncenter-api/
      The port number can be 9090. It might differ on your computer.
    • Samples Console - In the Samples Console perspective, in the Sample Server view, click one of the following links:
      • Decision Center Business console
      • Decision Center REST API tool
  3. Log in by entering an existing username and password combination. The sample server comes preconfigured with the following user credentials in the basic registry of the Liberty profile, in <wlp_home>/usr/servers/odmXXX/server.xml:
    Users for the samples and tutorials:
    • Administrator rights:
      • Paul as username and password.
    • Standard rights:
      • Bea as username and password.
      • rmtUser as username and password.
    Additional users mapped to the Decision Center roles
    Username and password Role
    odmAdmin rtsAdministrator, rtsInstaller. Also has resAdministrator rights to access the Rule Execution Server console.
    rtsAdmin rtsAdministrator, rtsInstaller
    rtsConfig rtsConfigManager
    rtsUser1 rtsUser

    These users can be used to test configuration issues (see Step 2: Configuring user access to Decision Center).

    Users that can log in to the Decision Center consoles are generally uploaded to the Decision Center database and associated to a group of users. This allows them to receive a permissions profiles for use with the Decision Center branch security feature. To be uploaded to the database in the sample server, these users are declared in the file <InstallDir>/shared/samplesServer/wlp/userConfiguration.xml. The build.xml file in the same directory has a declareUsersIfNeeded target that calls the configuration file. The file contains the following group and user declarations:
    <dc-usermanagement>
  <group name="rmtUserGroup" roles="rtsUser"/>
  <group name="AdminGroup" roles="rtsAdministrator"/>
  <group name="UserGroup" roles="rtsUser"/>

  <user name="Paul" groups="AdminGroup"/>
  <user name="Bea" groups="UserGroup"/>
  <user name="rmtUser" groups="rmtUserGroup"/>
</dc-usermanagement>

    The users rtsUser1, rtsConfig, rtsAdmin, and odmAdmin are not included in this file. These users can log in to the consoles because they are declared in the basic registry, but they are not available as participants in the decision governance framework or visible in the Administration tab of the Business console for mapping users to security groups (see Decision Center groups of users).

To run the samples, see Running samples from the Samples Console.

Note:

Single sign-on (SSO) authentication is activated for the sample server. With SSO, users can log in once and gain access to all applications without being prompted to log in again for each of them. If you use different sign-on credentials for the applications on the sample server, for example when performing certain samples and tutorials, you get an error message when you attempt to sign in to the second application.

To avoid this issue, you must sign out of the first console and then sign in to the second console. Alternatively, you can sign in to all of the applications on the server by using the credentials that you entered at installation time.