Topics

Viewing Screenshots

Place the cursor over this icon to load and view all the screenshots for this tutorial. (Caution: This action loads all screenshots simultaneously, so response time may be slow depending on your Internet connection.)

Note: Alternatively, you can place the cursor over each individual icon in the following steps to load and view only the screenshot associated with that step.

Overview

Oracle WebCenter is an integrated suite of technology designed to deliver a unified, context-aware user experience that integrates structured and unstructured content, business intelligence, business processes, communication, and collaboration services. Oracle WebCenter is part of the Oracle Fusion Middleware product family and is based on an open, standards-based architecture. A key feature of WebCenter is that it removes the boundaries between Web-based portals and enterprise applications, and enables the rapid creation of a new generation of context-centric, composite applications that will change the way people work. The WebCenter Framework is integrated into JDeveloper and allows you to embed portlets, content, and customizable components in your application. Oracle WebCenter Framework portlet integration supports all the production portlet standards including JSR 168 and WSRP 1.0, as well as an early version of WSRP 2.0.

Oracle E-Business Suite Release 12 provides built-in portlets through a WSRP 1.0-compliant framework producer. You can consume these portlets in a WebCenter application.

In this tutorial, you use Oracle JDeveloper as the IDE for building your application.

Have access to or have installed Oracle's E-Business Suite Release 12.

The E-Business Suite Release 12 instance must be configured for WebCenter integration. That means that the Oracle Applications Manager should have:

Updated the list of nodes that have access to Portlet Producer URLs to include the machines where OracleAS 10g WebCenter, Oracle JDeveloper, and the Infrastructure database are installed.
Note: This is requirement is for running the application from JDeveloper and not for clients that access the deployed application.

Implemented Single Sign-On support on the E-Business Suite R12 instance. Users must be common to both the WebCenter application and the E-Business Suite instance that it accesses.

In this topic, you use JDeveloper Studio to create a WebCenter application and a JSF page to display the E-Business Suite portlets. After registering the E-Business Suite portlet producer, you add one of its portlets to the page.

In the Application Navigator, right-click the
ViewController project, and select
New.

Note: Registration is part of consuming a portlet, so you should right-click the ViewController project, not the Portlets project. The Portlets project is for producing portlets—that is, creating, enhancing, and deploying them—whereas the ViewController project is used to create the JavaServer Faces pages for the UI of your application and to consume portlets.

2.

In the New Gallery, expand
Web Tier in the Categories tree, and select
Portlets.

In the Items list, select
WSRP Producer Registration.

Click
OK to launch the Register WSRP Producer Wizard.

3.

Click
Next to leave the Welcome page of the wizard.

4.

Rename the producer
EBSproducer and click
Next.

5.

On the Connection page, enter the Release 12 WSDL URL in the
URL Endpoint field, using the format below:
http://<Release_12_host>:<port>/OA_HTML/portlets/WSRPBaseService?WSDL

For example:
http://myEBSServer.us.oracle.com:8001/OA_HTML/portlets/WSRPBaseService?WSDL

6.

Click
Next. The wizard uses the URL you just entered to connect to the WSRP portlet producer .

Note: Your E-Business Suite instance must be running for this step to succeed.

7.

In the Registration Details page, click
Finish to accept the default timeout value of 30 seconds.

The two remaining wizard pages apply to security and key store location. In this simple example, you have not configured key stores on the E-Business Suite instance or in the OC4J that is running the WebCenter application, so simply click
Finish.

Set JAAS Mode to
doAsPrivileged. Keep the default values for the other settings. Click
Next.

The adfAuthentication resource (the authentication servlet) is already defined by default. You cannot edit or delete this resource, but you can specify the set of roles that may access the resource. To allow any valid user access to the adfAuthentication resource, you need to add a role named ValidUsers.

Note: The ValidUsers role will be mapped by the deployment descriptor to a real role defined in the identify management system. If a role of the same name exists in the identity management system, OC4J will automatically map them. The name "ValidUsers" is a convention used by WebCenter; however, you could choose to use a different name.

6.

To create the ValidUsers role and grant access to it, follow these steps:

a.

Click
Manage Roles.

b.

Click
Add.

c.

Enter
ValidUsers as the name. Click
OK.

Then click
Close.

d.

Click the arrow to move the ValidUsers role to the Selected Roles list .

Running the Application

Now let's run the application and test that the user you just defined is able to access the E-Business Suite portlet producer.

1.

Right-click
EBSportlets.jspx in the Applications Navigator and select
Run from the context menu.

2.

When the login.htm page opens in your browser, enter the user name and password of the authorized user and click
Submit.

After successful authentication, the EBSportlets.jspx page opens. This time, content is displayed in the portlet.

3.

Click any link in the portlet.

4.

When prompted, enter your Single Sign-On user name and password and click
OK.

The relevant Application Navigator for Oracle E-Business Suite is now displayed in your browser.

Note: You may wonder why you were prompted to log in a second time. When two applications use SSO for authentication through the same SSO server (domain), then only a single login is necessary. However, JDeveloper's embedded OC4J does not support SSO. Instead, authentication in your WebCenter application is done by the container using form-based user credential input (that is, login.html) and a local user/credential store (system-jazn-data.xml). So, the first login has no connection to any SSO server. Therefore, when you access the E-Business Suite Web interface, which is protected by SSO, authentication through SSO is required.

In this lesson, you learned how a WebCenter application can consume Oracle E-Business Suite portlets. You also saw how to configure roles and users in a WebCenter application and authorize user access to a page.