Skip Headers

Oracle® Student Learning Installation and Deployment Guide Release 3.1.3 Part Number E20664-04 |
Home | Book List | Contents | Contact Us

Previous | Next
| PDF · Mobi · ePub

# 8 Configuring WebLogic Server

This chapter describes the configuration steps in WebLogic Server before OSL deployment.

## 8.1 Installing ADF Runtime Libraries

To install ADF 11g Runtime libraries in the existing WLS instance, see Section 35.6.1, "How to Install the ADF Runtime into an Existing WebLogic Server Using the Oracle Fusion Middleware Application Developer Installer" in the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework 11g Release 1 (11.1.1.5.0) at:

`http://download.oracle.com/docs/cd/E21764_01/web.1111/b31974/toc.htm">>http://download.oracle.com/docs/cd/E21764_01/web.1111/b31974/toc.htm`.

## 8.2 Configuring ADF Domain with Oracle Enterprise Manager

To create a domain or extend the existing domain in the WLS instance for ADF applications, see Section 35.7, "Creating and Extending WebLogic Domains" in the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework 11g Release 1 (11.1.1.5.0) at

`http://download.oracle.com/docs/cd/E21764_01/web.1111/b31974/toc.htm">>http://download.oracle.com/docs/cd/E21764_01/web.1111/b31974/toc.htm`.

When you generate or extend a domain, ensure that the domain is configured to support Oracle Enterprise Manager, Oracle JRF, and Oracle WSM Policy Manager.

Note:

For Oracle WSM Policy Manager, the schema DEV_MDS must exist in the Learning Tool database. Run the Oracle Fusion Middleware Repository Creation Utility 11g against the Learning Tool database. Ensure that Metadata Service under AS Common Schemas is selected.

## 8.3 Configuring OSL LT Data Source

To configure the OSL Learning Tool data source:

1. Open the WLS Administration Console:

   ```http://<WLS host name>:7001/console`

2. Log in to the WLS console using an administrator user name and password.

3. Select JDBC > Data Sources > New.

4. Edit the properties as specified in Table 8-1, "Data Source Properties".

   Table 8-1 Data Source Properties

   Attribute | Value | Meaning
   --- | --- | ---
   Name | `oslDS` | Name of the data source
   JNDI Name | `oslDS` | JNDI name of the data source
   Database Type | `Oracle` |
   Database Driver | `Oracle Driver (Thin XA) for Instance Connections; Versions:9.0.1,9.2.0,10,11` | JDBC driver used to connect to the database
   Database Name | `<SID>` | Oracle database SID or service name
   Host Name | `<Database Hostname>` |
   Port | `<Default: 1521>` | Database port
   Database User Name | `<enter username>` | OSL database schema name
   Password | `<password>` | Password for OSL schema
   Confirm Password | `<password>` |

5. Select Next.

6. Select Test Configuration to verify that the database connection parameters are set correctly.

7. Select the server targets for the data source from the list of available servers in the WLS domain on which to deploy the OSL LT Admin and OSL LT applications.

8. Click Finish.

## 8.4 Storing Credentials in OSL Credential Store

The OSL credential map contains credentials for servers to which the OSL Learning Tool must authenticate. The servers include the remote JMS server for the Event publishing service (if remote Resources are used) and custom Content Integration. This section describes how to create the OSL credential map and store credentials in the OSL credential map.

### 8.4.1 Creating a Credential Map

To create a credential map:

1. Open the Oracle Enterprise Manager 11 g Fusion Middleware Control.

2. From the navigation pane, expand WebLogic Domain.

3. Right-click the domain and click Security > Credentials.

4. On the Credentials page, click Create Map and name it OSL.

5. Click OK.

Figure 8-1 Creating a Credential Map

### 8.4.2 Storing Credentials for Content Integration

If you are using the default content integration with the default proxy type (Internal), ignore this section.

If you chose the WS proxy type or you are using a custom content integration, the OSL Learning Tool must pass authentication information to the content integration web service. You must specify the credentials of the JMS server in the OSL credential map.

#### 8.4.2.1 Creating the JMS Server Credential Key

To create a credential key:

1. Click the OSL Map created in Section 8.4.1, "Creating a Credential Map".

2. Click Create Key.

3. Enter the following details:

   - Map: OSL

   - Key: osl.content.credentials

   - Type: Password

   - Username: name of the user that can invoke the content integration web service. In the default content integration, this user is named contentintegration (as specified in Section 5.4, "Assigning Content Integration User").

   - Password: password of the above user

#### 8.4.2.2 Granting Codebase Permission to the Credential Store

The OSL Learning Tool codebase requires permission to access the credential map mentioned in Section 8.4.2.1, "Creating the JMS Server Credential Key".

Perform the steps in Section 8.4.2.2, "Granting Codebase Permission to the Credential Store".

## 8.5 Configuring OID as Security Provider

Configure the OID instance as the security provider for the WLS instance on which OSL is deployed so that OID users can access OSL.

To define a security provider for WLS:

1. Open the WLS Administration Console:

   `http://<WLSHostName>:port/console`

2. Log in to the console using an administrator user name and password.

3. Select Security Realms > myrealm (default) > Providers (tab).

4. In the Authentication Providers table, select New.

5. Enter a name for the authentication provider in the Name field, for example `OSL_OID`.

6. Choose OracleInternetDirectoryAuthenticator as from the Type list.

7. Click OK.

8. Select the new authentication provider instance on the Providers tab to navigate to its configuration page.

9. Select the Provider Specific tab under the Configuration tab.

10. Edit the properties in the Provider Specific configuration as described in Table 8-2, "Provider Specific Properties".

    Table 8-2 Provider Specific Properties

    Attribute | Value | Meaning
    --- | --- | ---
    Host | `<OID hostname>` |
    Port | `3060` | Default non-SSL OID port.
    Principal | `cn`=`orcladmin` | Administrator account to connect to OID.
    Credential | <`orcladmin` `password`> | Password for OID administrator account.
    Confirm Credential | <`orcladmin` `password`> |
    User Base DN | <`OID User Search Base`> | Value of the User Search Base attribute in OID. You can find this value on the OID administration page. The format of the value is: `cn=users`, `dc=...`
    Use Retrieved User Name as Principal | `Check` | Specifies whether the user name retrieved from OID use as the Principal in the Subject.
    Group Base DN | <`OID Group Search Base`> | Value of the Group Search Base attribute in OID. You can find this value on the OID administration page. The format of the value is: `cn=Groups`, `dc=…`
    Propagate Cause for Login Exception | `Check` | Propagates OID exceptions to WLS to show in the console and logs.

11. Click Save.

12. Restart the WLS instance.

13. Log in to the WLS console and select Security Realms > myrealm (default) > Users and Groups (tab).

    Ensure that the OID users and groups are listed under Users and Groups.

14. Change the Control Flag attribute of the security provider so that OSL users must authenticate only against OID:

    1. Select Security Realms > myrealm (default) > Providers (tab) > [name of the security provider] > Configuration (tab) > Common (tab).

    2. Set Control Flag to Sufficient.

15. Reorder the security provider to be the first authentication provider.

16. Restart the WLS instance.