5 Configuring database and Topics credentials

This chapter includes the following topics:

• Creating the Topics service user (optional)

• Storing database and Topics credentials

• Setting up permissions for the credential store

Creating the Topics service user (optional)

If you plan to use the Topics feature, perform the following steps.

1. Type the URL for the Weblogic Administration Console, and log in.

2. In Domain Structure pane to the left, select Security Realms.

   The Summary of Security Realms page appears.

3. In the Realms table, click the myRealm link.

   The Settings for myrealm page appears.

4. Select the User and Groups tab.

5. In the Users table, click New.

   The Create a New User page appears.

6. Type a name and a password for the Topics service user. For example, you might choose the username topicsService.

   
   

   Note: Remember this information. This information is stored in the credential store.

   
   

7. Click OK.

   The topic service user is created.

Storing database and Topics credentials

1. In an internet browser, enter the URL for the Oracle Enterprise Manager, such as the following::

   https://<server_name>:7002/em

2. Type the WebLogic administrator credentials, and click Login.

   The Oracle Enterprise Manager appears.

3. On the left, expand WebLogic Domain, and select empirica.

4. Expand the WebLogic Domain menu, located below the empirica page title, and select Security > Credentials.

   The Credentials page appears.

5. Create a map for credentials for the Empirica Signal application:

   1. In the Credentials table, click Create Map.

      The Create Map dialog box appears.

   2. Type the following map name:

      oracle.hsgbu.empirica

   3. Click OK.

6. Create a key for the credentials for the Empirica Signal database account:

   1. In the Credentials table, click Create Key.

   2. Fill in the following fields. Text fields are case-sensitive.

      • Select Map—Select the map you just created.

      • Key—Type the following value:

        DatabaseCredentials

      • Type—Select Password.

      • User Name, Password, Confirm Password—Type the login information for the Empirica Signal database schema. The default user name is webvdme.

      • Description—Type the following value:

        Signal schema username and password

   3. Click OK.

7. If you are using the Topics feature, create a key for the Topics service credentials:

   1. In the Credentials table, click Create Key.

   2. Fill in the following fields. Text fields are case-sensitive.

      • Select Map—Select the map you just created.

      • Key—Type the following value:

        TopicsService

      • Type—Select Password.

      • User Name, Password, Confirm Password—Type the login information for the Topics service user created in the WebLogic Administration Console. For example, the user name might be topicsService.

      • Description—Type the following value:

        Username and password for Signal communicating with the Topics Service.

   3. Click OK.

      The Credentials page appears. The credential store keys are now set up.

8. If you are configuring the Empirica Signal application for use with LDAP, create a key for the LDAP credentials.

   
   

   Note: Skip this step if you are configuring anonymous LDAP login.

   
   

   1. In the Credentials table, click Create Key.

   2. Fill in the following fields. Text fields are case-sensitive.

      • Select Map—Select the map you just created.

      • Key—Type the following value:

        LdapCredentials

      • Type—Select Password.

      • User Name, Password, Confirm Password—Type the login information for the LDAP user.

      • Description—Type the following value:

        LDAP username and password

   3. Click OK.

9. To see the keys you created, expand the map in the Credentials table.

Setting up permissions for the credential store

You must set up permissions for the Empirica Signal application to access the credential store. Otherwise, the Empirica Signal application cannot start, users cannot login, and the Topics Web Service is unavailable.

1. In the Oracle Enterprise Manager, on the left, expand WebLogic Domain, and select empirica.

2. Expand the WebLogic Domain menu, located below the empirica page title, and select Security > System Policies.

   The System Policies page appears.

3. In the System Policies table, click Create.

   The System Policies > Create System Grant page appears.

4. In the Codebase field, type the case-sensitive codebase, such as:

   file:${oracle.deployed.app.dir}/Signal${oracle.deployed.app.ext}

   
   

   Note: Use the codebase value as is unless you plan to use a context root value other than the default value of Signal. For more information, see Creating the Empirica Signal deployment in WebLogic.

   
   

5. Add a permission:

   1. Click Add.

      The Add Permission page appears.

   2. Select the Select here to enter details for a new permission check box, located at the bottom of the page.

   3. Type the following values for the fields below the check box:

      • Permission Class—oracle.security.jps.service.credstore.CredentialAccessPermission

      • Resource Name—context=SYSTEM,mapName=oracle.hsgbu.empirica,keyName=*

      • Permission Actions—read

   4. Click OK.

      The System Policies > Create System Grant page appears.

6. Click OK.

   The permission is saved. The System Policies page appears.

7. Search for the permission you just created:

   1. From the Name drop-down list, select Includes.

   2. In the field after the Name field, type Signal or the intended application context root. For more information, see Creating the Empirica Signal deployment in WebLogic.

   3. Click the Search button.

      The newly created permission appears in the table.

8. Create a permission based on the permission:

   1. Select the permission in the table, and click Create Like.

      The System Policies > Create System Grant page appears.

   2. Type a codebase value, such as the following value:

      file:${domain.home}/servers/${weblogic.Name}/stage/Signal/Signal${oracle.deployed.app.ext}

      
      

      Note: Use the codebase value as is unless you plan to use a context root value other than the default value of Signal. For more information, see Creating the Empirica Signal deployment in WebLogic.

      
      

   3. Click OK.

      The permission is added.

9. Search for the permission you just created:

   1. From the Name drop-down list, select Includes.

   2. In the field after the Name field, type Signal or the intended application context root. For more information, see Creating the Empirica Signal deployment in WebLogic.

   3. Click the Search button.

      The newly created permissions appear in the table.

10. Create a permission based on the permission:

    1. Select a permission in the table, and click Create Like.

       The System Policies > Create System Grant page appears.

    2. Type a codebase value, such as the following value:

       file:${wls.home}/../../patch_wls1036/patch_jars/-

       
       

       Note: This directory should reflect the directory where you installed the patch for WebLogic.

       
       

    3. Click OK.

       The permission is added.