10 Integrating Other Oracle Applications

Integrate other Oracle applications, such as Siebel, E-Business Suite, JD Edwards, PeopleSoft, and Oracle Business Intelligence, with WebCenter Portal.

Permissions:

To perform the tasks in this chapter, you must be granted the WebLogic Server Admin role through the Oracle WebLogic Server Administration Console and the Administrator role granted through WebCenter Portal Administration. Aside from these permissions for WebCenter Portal, you may also need additional permissions for the other Oracle applications being integrated.

For more information about roles and permissions, see Understanding Administrative Operations, Roles, and Tools.

Topics:

10.1 About Integrating Other Oracle Applications

Oracle WebCenter Portal is an integrated suite of technology designed to deliver a unified, context-aware user experience. WebCenter Portal integrates structured and unstructured content, business intelligence, business processes, communication, and collaboration services, and removes the boundaries between enterprise applications. By integrating other applications available within the enterprise with WebCenter Portal, you can create context-centric, composite applications that leverage the capabilities of these applications, extending WebCenter Portal and changing the way people work.

WebCenter Portal uses industry-standard technologies to integrate (primarily as WSRP portlets) other application components. Figure 10-1 shows the technologies involved in WebCenter Portal integration with other Oracle applications.

Figure 10-1 WebCenter Portal Integration

Description of "Figure 10-1 WebCenter Portal Integration"

Although not all applications support the same integration mechanisms, the integration process is generally quite simple, consisting of exposing the application object to be integrated as a portlet, registering the portlet with WebCenter Portal, adding the portlet to a page, and then running and testing the results.

In Figure 10-1 we show the applications that can be integrated as Siebel, E-Business Suite, JD Edwards, PeopleSoft, and Oracle Business Intelligence. These Oracle applications are fully supported and documented within this chapter. However, you can integrate virtually any application that can expose objects as WSRP portlets. The process for integrating them is the same as for the Oracle applications documented here: expose the object as a portlet, register the portlet in WebCenter Portal, and add the portlet to a page. Refer to the documentation for one of the supported Oracle applications for a description of how to consume an exposed portlet in WebCenter Portal.

10.2 Integrating Siebel Applications

This section describes how to integrate a Siebel Web service in WebCenter Portal. Siebel and WebCenter can work together to include Siebel's CRM capabilities as portlets within WebCenter Portal.

How to Integrate Siebel Applications as Web Services

10.2.1 How to Integrate Siebel Applications as Web Services

This section describes how to integrate Siebel applications as Web services in WebCenter Portal.

To be able to add a Siebel Web service data control or a task flow containing a data control to a portal page you must first have configured WS-Security for WebCenter Portal. For more information about configuring WS-Security, see Configuring Web Services Security login credentials in Oracle Fusion Middleware Administering Oracle WebCenter Portal. For more information about Web service data controls, see Creating Data Controls and Web Service Data Controls in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.

This section contains the following subsections:

10.2.1.1 How to Prepare the Siebel Application

This section describes how to create an inbound Web service, set up operations for the inbound service, and generate a WSDL that you will later use to create a data control in WebCenter Portal.

This section contains the following subsections:

10.2.1.1.1 How to Create an Inbound Web Service

To create an inbound Web service:

Log into the Siebel application as an administrator.
Navigate to the Administration - Web Services page.
Click Inbound Web Services.

The Inbound Web Services page shows the out-of-the-box Web services and any other Web services that are currently exposed.
Click Menu and select New Record from the drop-down list.
Enter the values for Namespace, Name, Status and Comment as appropriate for the Web service you want to set up. For example:

Field Name Value

Namespace

http://xmlns.oracle.com

Name

Siebel Customer Account

Status

Active

Comment

For Fusion Middleware
Scroll to the Service Ports pane and select New Record from the Menu drop-down list.
Enter CustAccount as the Name and click Type.
In the Inbound Web Service Port Type pick applet, open the New tab.
Select Business Service as the Implementation Type.
From the Service Name list, select Siebel Account.
In the Inbound Web Service Port Type pick applet, click OK to create the inbound Web service.
From the Service Ports dialog's Transport drop-down list, select HTTP.

Field Name	Value
Namespace	`http://xmlns.oracle.com`
Name	`Siebel Customer Account`
Status	`Active`
Comment	`For Fusion Middleware`

In the Address field, set the URL to your Siebel instance. For example:

http://xmlns.oracle.com/eai_enu/start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&UserName=SADMIN&Password=SADMIN

From the Menu drop-down list, select Save Record.

10.2.1.1.2 How to Create Operations for the Inbound Web Service

After creating the inbound Web service, continue by adding operations to the inbound Web service and then create a WSDL file, follow these steps:

Scroll to the Operations section and select New from the Menu drop-down list.
In the Operation Name field, enter AccountInsert.
Click Method Display Name to open the Business Service Method dialog.
Select Insert as the Method, and click OK.

From the Authentication Type drop-down list, select an appropriate authentication type:

Authentication Type	Session Type	Description
None	None	A single request is sent with an anonymous user login, and the session is closed after the response is sent out. In order for the anonymous session to be identified by the SWSE Plug-in, UsernameToken and PasswordText must be excluded in the SOAP headers.
Username and password	None	A single request is sent with the username and password used to log in, and the session is closed after the response is sent out.
Username and password	Stateless	The initial request to log in establishes a session that is to remain open and available for subsequent requests. Username/password are used to log in and a session token is returned in a SOAP header included in the outbound response. The session remains open.
Session token (stateless)	Stateless	Request to reconnect to an established session, using the information contained in the session token. If the session has been closed, automatic re-login occurs. The Siebel servers include the session token in the SOAP header of the response. The session remains open.
Session token (stateless)	None	When a SOAP header carries a session token and has the session type set to None, then the Session Manager on the SWSE closes (logs out) of this session, and invalidates the session token. The session token is not used after the session is invalidated.

Click New to create a new operation.
In the Operation Name field, enter a name for the new operation (for example, AccountQueryByExample).
Click Method Display Name for the new operation.
In the Business Service Method dialog, select the query method (for example, Query By Example) and click OK.
Continue by adding any additional operations you may need as described in steps 6 to 9 above.
In the Service Ports pane, select Save Record from the Menu drop-down list.
In the Inbound Web Services pane, select Save Record from the Menu drop-down list.
Select Clear Cache from the Menu drop-down list.
Click the Generate WSDL.
On the File Download dialog, click Open.
Select File --> Save As...
Locate the directory where you want to save the WSDL file, enter a name for the file and click Save.

10.2.1.2 How to Consume a Siebel Web Service Data Control

This section describes how you can create a Web Service data control and add it to a portal page. The steps in this section assume that you have prepared the application and generated a WSDL as described in How to Prepare the Siebel Application.

Note:

Before you can add a data control or task flow containing a data control to a portal page you must first have configured WS-Security for WebCenter Portal. For more information about configuring WS-Security, see Configuring Web Services Security login credentials in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

To create a Web service data control:

In WebCenter Portal or the portal in which you want to create the data control, go to either the Shared Assets or Assets page.
Select Data Controls and click Create.

The Create New Data Control dialog displays.

Figure 10-2 Create New Data Control Dialog

Description of "Figure 10-2 Create New Data Control Dialog"
In the Create New Data Control dialog, enter a Name and Description for the data control, select Web Service as the Data Control Type, and then click Continue.
Enter the WSDL URL that you generated earlier and other details for the data control and click Continue.
Click Show Methods.
Select the method(s) to make available and click Next.
Enter the parameter default values, if any, and click Create.
To make the data control available, from the Shared Assets or Assets page, select Task Flows. The Create New Task Flow dialog displays.

Figure 10-3 Create New Task Flow Dialog

Description of "Figure 10-3 Create New Task Flow Dialog"
Enter the task flow Name and Description, select the Mashup Style to use, and then click Create to create the task flow.
Select the task flow and click the Edit icon.
Add the data control (with parameter form) as a table onto the task flow and verify the data.
To make the task flow available, navigate to Administration > Business Role Pages.
Select Business Role Page and click the Create icon.
Edit the page and save the changes.
Drop the task flow onto the page and verify the data.

10.3 Integrating E-Business Suite Applications

This section describes how to integrate E-Business Suite applications in WebCenter Portal.

This section contains the following subsections:

10.3.1 About Integrating EBS Applications

This section describes the integration points and requirements integrating Oracle E-Business Suite portlets in WebCenter Portal.

This section includes the following subsections:

10.3.1.1 Understanding EBS Integration

Out of the box, Oracle E-Business Suite OA Framework-based portlets, such as Applications Navigator, and Favorites are WSRP and JSR 168-compliant. That means that you can access these Oracle E-Business Suite portlets from WSRP-compliant portal servers, such as WebCenter Portal, by simply adding the portlet onto a page. Follow the instructions in How to Add the EBS Portlet to a Portal Page to add them to a WebCenter Portal or portal page.

You can also create new E-Business Suite portlets that are WSRP and JSR 168-compliant that can similarly be added to WebCenter Portal. Creating and consuming WSRP and JSR 168 compliant portals in WebCenter Portal is described in How to Integrate EBS Applications.

10.3.1.2 Requirements for Integrating EBS Applications

The following requirements apply for integrating Oracle E-Business Suite portals in WebCenter Portal:

Regions to be exposed as portlets must be created using Oracle E-Business Suite OA Framework Release 12 as previous versions are not WSRP/JSR 168-compliant.
Oracle E-Business Suite can be configured to use Oracle Internet Directory (OID) and one of following single sign-on solutions:

Caution:

Both WebCenter Portal and Oracle E-Business Suite must share the same OID instance and user IDs.
- Oracle Single Sign-On (OSSO)
- Oracle Access Manager (OAM)
If you are using OSSO, follow the steps in My Oracle Support document 376811.1 to integrate E-Business Suite Release 12 with OID and OSSO.

If you are using OAM, follow the steps in My Oracle Support document 975182.1 to integrate E-Business Suite Release 12 with OAM.

E-Business Suite can also be configured to OID without OAM or OSSO. For more information, see How to Prepare OID for Use Without Single Sign-On.

Note:

Although Oracle E-Business Suite can be configured to use Oracle Internet Directory (OID) without single sign-on, this is not a recommended approach as users will be prompted for credentials each time they move to or from the integrated portal or data control.
You must have granted WebCenter Portal access to the E-Business Suite Portlet Producer and added and configured the appropriate users.

Note:

To complete some steps, you may need system administrator permissions.

10.3.2 Required Configurations for Integrating EBS

This section contains configurations that should be undertaken prior to attempting to integrate portal or data controls in WebCenter Portal.

This section contains the following subsections:

10.3.2.1 How to Prepare OID for Use Without Single Sign-On

This section describes the steps to configure OID as an optional standalone environment without using either OAM or OSSO. Note that this is not a recommended approach as users will be prompted for credentials each time they move to or from an integrated portal or data control. If you have installed an SSO solution, continue with How to Create a User in EBS and Assign a Responsibility.

Caution:

Both WebCenter Portal and Oracle E-Business Suite must share the same OID instance and the same user IDs.

Run the following command:

$FND_TOP/bin/txkrun.pl -script=SetSSOReg -registerinstance=yes

Supply the required information at the following prompts:

Enter the host name where the Oracle iAS Infrastructure database is installed ? <Enter the OID Host>
Enter the LDAP Port of the Oracle Internet Directory server ? <Enter the LDAP Port>
Enter SSL LDAP Port of the Oracle Internet Directory server ? <Enter the LDAP SSL Port>
Enter the Oracle Internet Directory Administrator (orcladmin) Bind password ? <Password>
Enter Oracle E-Business apps database user password ? <Password>

Restart all the services by navigating to $ADMIN_SCRIPTS_HOME and running:

./adstpall.sh apps/<apps to stop>

and then:

./adstrtal.sh apps/<apps to start>

Run the following command:

$FND_TOP/bin/txkrun.pl -script=SetSSOReg -registeroid=yes

Supply the required information at the following prompts:

Enter LDAP Host name ? <Enter the OID Host>
Enter the LDAP Port on Oracle Internet Directory server ? <Enter the LDAP Port>
Enter the Oracle Internet Directory Administrator (orcladmin) Bind password ? <Password>
Enter the instance password that you would like to register this application instance with ? <Password>
Enter Oracle E-Business apps database user password ? <Password>

Restart all the services by navigating to $ADMIN_SCRIPTS_HOME and running:

./adstpall.sh apps/<apps to stop>

and then:

./adstrtal.sh apps/<apps to start>

10.3.2.2 How to Create a User in EBS and Assign a Responsibility

For integration with EBS to work, WebCenter Portal and EBS must have a common OID identity store. With a common OID, you can either create a new user in EBS, or use an existing user in OID, and then assign a responsibility to that user. This will ensure that the user has access to the portlets in WebCenter Portal.

To create a new user and assign a responsibility:

Log into EBS as a system administrator if not already logged in.
In the Navigation pane, expand the System Administrator node, expand Security, expand User, and then click Define.

The Users window displays.

Figure 10-4 Users Window

Description of "Figure 10-4 Users Window"
Enter the User Name, and Password. The Password Expiration options should be set to None.
Open the Direct Responsibilities tab, and search for the Responsibility to add and assign the Application to associate with it (for example, search for Preferences SSWA and assign Oracle iProcurement to it), and then click Save.

Figure 10-5 Users Window Showing the Direct Responsibilities Tab

Description of "Figure 10-5 Users Window Showing the Direct Responsibilities Tab"
To confirm, log in with the newly created user and check that the application associated with the Responsibility is listed.

10.3.2.3 How to Configure the EBS Applications Profile Options

This section describes how to configure EBS Applications Profile Options and is a requirement for both SSO and non-SSO configurations.

To configure the EBS profile options:

Log into EBS as a system administrator.
In the Navigation pane, expand the System Administrator node, and then click Define Profile Options.
Close the Profiles window.
In the Navigator, select Profile System Values and click Open.

The Find System Profile Values window displays.

Figure 10-6 Find System Profile Values Window

Description of "Figure 10-6 Find System Profile Values Window"
Enter the Profile name to update and click Find.

The System Profile Values window displays.

Figure 10-7 System Profile Values Window

Description of "Figure 10-7 System Profile Values Window"

Update the values for the following profiles, saving your entries after each update:

Applications SSO Enable OID Identity Add Event =Enabled

Applications SSO Login Types =Both

Application SSO LDAP Synchronization =Enabled

Applications SSO Type =SSWA w/ SSO

Link Applications user with OID user with same username =Enabled
Restart all the services by navigating to $ADMIN_SCRIPTS_HOME and running:

./adstpall.sh apps/<apps to stop>

and then:

./adstrtal.sh apps/<apps to start>

10.3.2.4 How to Add the WebCenter Host as a Trusted Portal Using AutoConfig

The EBS WSDL is protected and before you can access it you must first add an entry for the consuming WebCenter Portal instance's host using the EBS AutoConfig tool. Note that without this configuration step you will get a "403 Forbidden" error if you try to access the WSDL.

To add the WebCenter Portal host as a trusted portal:

Log into EBS as a system administrator if you are not already logged in.
In the Navigation pane, expand the System Administrator node, expand Oracle Applications Manager, and then click Workflow.
Open the Sitemap tab and click AutoConfig.
In the Edit Parameter column, click the Edit icon in the Applications Tier row.
Open the System tab and expand the oa_web_server node.
In the list of nodes, look for any that have access to Portlet Producer URLs, add the WebCenter Host and click Save. If you need to add multiple host name, add them separated by space.
Run the autoconfig script entering apps as the password when prompted:

cd $ADMIN_SCRIPTS_HOME

./adautocfg.sh
Restart all the services by running the following commands from $ADMIN_SCRIPTS_HOME:

./adstpall.sh apps/<apps to stop>

and then:

./adstrtal.sh apps/<apps to start>

10.3.3 How to Integrate EBS Applications as WSRP Portlets

This section describes how to integrate EBS regions as WSRP portlets in WebCenter Portal. To start, you'll need to generate the portlet for the region using the Portlet Generator, and then continue by registering the producer and integrating it in WebCenter Portal.

This section contains the following subsections:

10.3.3.1 How to Prepare the EBS Portlet for Remote Access

Oracle E-Business Suite provides a tool called Portlet Generator to convert existing standalone Oracle Application Framework regions into portlets. To be available for portletization, a region must have the following properties.

Regions must have an Application Module (AM) defined and must have its standalone property set to true.
Inline regions must have an AM defined and have its standalone property set to true.
Content regions must have an AM defined (content regions do not have a standalone property)

To expose EBS functionality as a portlet using Portlet Generator:

Log into EBS as a system administrator.
In the Navigation pane, expand the Functional Administrator node, and then click Home.

The Application Administration page displays (see Figure 10-8).

Figure 10-8 Application Administration Page

Description of "Figure 10-8 Application Administration Page"
Open the Portletization tab and click the Search icon for the Application Short Name field (or enter the Application Short Name if you know it).

Figure 10-9 Application Short Name Search Dialog

Description of "Figure 10-9 Application Short Name Search Dialog"
Select the Search By criteria (for example, select Application Name and enter Oracle iProcurement) and search for the functionality to portletize.
Select the row returned in the search results and click Select.
Click Go to list the EBS functionality that can be portletized.
Click the Portletize icon for the functionality you want to expose (for example, AdvisoryWarningRN ).

The Create Portlet dialog displays (see Figure 10-10).

Figure 10-10 Create Portlet Dialog

Description of "Figure 10-10 Create Portlet Dialog"
Enter the Responsibility to associate the region with (for example, Preferences SSWA) or use the Search function.
Click Apply.
Continue by registering the EBS producer and integrating it in a portal (see How to Integrate EBS Applications).

10.3.3.2 How to Integrate EBS Applications

This section contains the following subsections:

10.3.3.2.1 How to Prepare the EBS Portlet for Remote Access

Prepare the standalone regions to be portletized as described in the section on How to Prepare the EBS Portlet for Remote Access.

Before adding the portlets in WebCenter Portal, be sure to bounce the Apache listener as the menu and function definitions are cached.

10.3.3.2.2 How to Register the EBS WSRP Producer in WebCenter Portal

You can register the EBS WSRP producer directly in WebCenter Portal using Fusion Middleware Control.

To register the EBS WSRP producer using Fusion Middleware Control:

Prepare the EBS page that you want to consume in WebCenter Portal for remote access as described in How to Prepare the EBS Portlet for Remote Access.
Log in to Fusion Middleware Control for the WebCenter Portal domain (WC_Domain by default).
Expand WebCenter Portal in the Navigation bar and from the WebCenter Portal menu, and select Register Producer.

The Add Portlet Producer page displays.
Enter a Connection Name, set the Producer Type to WSRP Producer, and paste the WSDL endpoint URL that you copied in step 1 into the URL End Point field.
Click OK and verify that the producer connection was created successfully.
Continue by adding the portlet to a portal page as described in How to Add the EBS Portlet to a Portal Page.

10.3.3.2.3 How to Add the EBS Portlet to a Portal Page

Follow the steps below to consume the EBS remote producer in a WebCenter Portal page:

Log into WebCenter Portal and, optionally, open the target portal.
Go to the page, or create a new page, where you want to add the EBS portal.
Click Add Content and in the resource catalog, select UI Components and then Portlets.

Note that if you've created a custom resource catalog, Portlets may not appear. In this case, you will need to add it to the resource catalog. For information about managing resource catalogs, see Working with Resource Catalogs in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.
Click the portlet you added in Fusion Middleware Control.
Click Add for the EBS portlet you want to add to your portal page.
On the portal page, click the portlet’s View Actions menu, and select Display Options.
In the Display Options dialog, set Render Portlet in IFrameto True and click OK.
Continue by checking the portlet connection as described in How to Test the Portlet Connection.

10.3.3.2.4 How to Test the Portlet Connection

Follow these steps to test the portlet connection by modifying content and checking that the modification shows up in the EBS application.

On the WebCenter Portal or portal page to which you added the EBS portlet, modify some information that you can verify the changes for in the EBS application.
Save your changes and confirm that the changes also appear in the EBS application.

10.3.4 How to Integrate EBS Applications as Data Controls

This section describes how to add EBS applications as Web service data controls on a WebCenter Portal page.

This section contains the following topics:

10.3.4.1 How to Generate the WSDL

This section describes how to create the WSDL.

Log into E-Business Suite as the SYSADMIN user.
In the Navigation pane, expand the Integrated SOA Gateway node and under the Integrated SOA Gateway sub-node click Integration Repository.
From the Integration Repository tab, navigate to the part of the EBS application to expose. For example, for the price request interface, you would go to Order Management Suite > Advanced Pricing > Price List, and then selecting Price Request from the list of integration points.
Click Generate WSDL to expose the integration point (for our example, a PL/SQL API integration point) as a Web service.
Right-click the View WSDL link and open the link in a new tab or new window (be sure to keep the tab or window open as you'll need it later).
On the Integration Repository page under Procedures and Functions (see Figure 10-11), check the box for the object to grant access to, and then click Grant Access.

Figure 10-11 Integration Repository - Price Request Example

Description of "Figure 10-11 Integration Repository - Price Request Example"
Select the Grantee Type and Grantee Name (the user you want to grant access to the exposed object), or use the Search tool. For our example, we will grant access to ASADMIN.

Figure 10-12 Integration Repository - Create Grants Page

Description of "Figure 10-12 Integration Repository - Create Grants Page"

10.3.4.2 How to Add a Web Service Data Control to a Portal Page

Once you have the WSDL, you can continue by using it to create a web service data control.

Note:

Before you can add a data control or task flow containing a data control to a portal page you must first have configured WS-security for WebCenter Portal. For more information about configuring WS-security, see Configuring Web Services Security.

For more information about creating a web service data control, see Creating a Web Service Data Control in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal. For information about web service data controls, see About Web Services Data Controls in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.

To create a web service data control:

In WebCenter Portal or the portal in which you want to create the data control, go to either the Shared Assets or Assets page.
Select Data Controls and click Create.

The Create New Data Control dialog displays (see Figure 10-31).

Figure 10-13 Create New Data Control Dialog

Description of "Figure 10-13 Create New Data Control Dialog"
In the Create New Data Control dialog, enter a Name and Description for the data control, select Web Service as the Data Control Type, and then click Continue.
Enter the WSDL URL that you generated in How to Generate the WSDL and other details for the data control and click Continue.
Click Show Methods.
Select the method(s) to make available and click Next.
Enter the parameter default values, if any, and click Create.
To make the data control available, from the Shared Assets or Assets page, select Task Flows. The Create New Task Flow dialog displays (see Figure 10-33).

Figure 10-14 Create New Task Flow Dialog

Description of "Figure 10-14 Create New Task Flow Dialog"
Enter the task flow Name and Description, select the Mashup Style to use click Create to create the task flow.
Select the task flow and click the Edit icon.
Add the data control (with parameter form) as a table onto the task flow and verify the data.
To make the task flow available, navigate to Administration > Business Role Pages.
Select Business Role Page and click the Create icon.
Edit the page and save the changes.
Drop the task flow onto the page and verify the data.

10.4 Integrating JD Edwards Applications

This section describes how to integrate JD Edwards applications into WebCenter Portal.

This section contains the following subsections:

10.4.1 How to Prepare the JD Edwards Application for Remote Access

Before you can add JD Edwards standalone regions to WebCenter Portal, you must first prepare them to be portletized within JD Edwards by making them available externally as portlets and locating the pre-configured WSDL in the webclient.war/wsdl directory. The WSDL URL is needed so that you can register the JD Edwards WSRP producer and consume it from a WebCenter Portal or portal page. To view the XML content of the JDE WSDL in the browser, open the Page source of the page in the browser. For more information, see Administering WSRP with Oracle WebCenter.

10.4.2 How to Register the Producer

You can register the JD Edwards WSRP producer directly in WebCenter Portal, as described in the Registering Portlet Producers in Oracle Fusion Middleware Administering Oracle WebCenter Portal. You can also register the JD Edwards WSRP producer using Fusion Middleware Control as described in the steps below.

To register the JD Edwards WSRP producer using Fusion Middleware Control:

Prepare the JD Edwards page that you want to consume in WebCenter Portal for remote access.
Log into Fusion Middleware Control for the WebCenter Portal domain (WC_Domain by default).
Expand WebCenter Portal in the Navigation bar and from the WebCenter Portal menu, and select Register Producer.

The Add Portlet Producer page displays.
Enter JDE as the Connection Name, set the Producer Type to WSRP Producer, and paste the WSDL endpoint URL that you copied in step 1 into the URL End Point field.
Click OK and verify that the producer connection was created successfully.
Continue by adding the portlet to a portal page as described in How to Add the JD Edwards Portlet to a WebCenter Portal Page.

10.4.3 How to Add the JD Edwards Portlet to a WebCenter Portal Page

Follow the steps below to consume the JD Edwards remote producer in WebCenter Portal:

Log into WebCenter Portal.
Go to the page, or create a new page, where you want to add the JD Edwards portal.
Click Add Content and in the resource catalog, select UI Components and then Portlets.

Note that if you've created a custom catalog, Portlets may not appear. In this case, you will need to add it to the resource catalog. For information about managing resource catalogs, see Working with Resource Catalogs in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.
Click the portlet you added in Fusion Middleware Control.
Click Add for the JD Edwards portlet you want to add to your portal page.
On the portal page, click the portlet’sView Actions menu, and select Display Options.
In the Display Options dialog, setRender Portlet in IFrame to True and click OK.
Continue by checking the portlet connection as described in How to Test the Portlet Connection.

10.4.4 How to Test the Portlet Connection

Follow these steps to test the portlet connection by modifying content and checking that the modification shows up in the JD Edwards application.

On the WebCenter Portal or portal page that you added the JD Edwards portlet to, modify some information that you can verify the changes for in the JD Edwards application.
Save your changes and confirm that the changes also appear in the JD Edwards application.

10.5 Integrating PeopleSoft Applications

This section describes how to integrate PeopleSoft applications in WebCenter Portal.

This section contains the following subsections:

10.5.1 About Integrating PeopleSoft Applications

This section describes the benefits and methods involved in integrating PeopleSoft applications in WebCenter Portal.

This section includes the following subsections:

10.5.1.1 Understanding PeopleSoft Integration

PeopleTools 8.51 and later lets you expose PeopleSoft applications as WSRP portlets in remote applications such as WebCenter Portal. This allows people who only need access to a small portion of PeopleSoft's functionality to access it through WebCenter Portal without needing to open or learn the entire PeopleSoft application.

10.5.1.2 Requirements for Integrating PeopleSoft Applications

This section the prerequisites for integrating PeopleSoft objects in WebCenter Portal.

PeopleSoft 9.0 or later.
PeopleTools 8.51 or later.
When using WS-Security for automatic sign on to PeopleSoft, in order for the SAML assertion to be valid, the date/time on the PeopleSoft and Oracle WebCenter Portal servers must be synchronized. If this is problematic, then the PeopleSoft web server's time may be set to be slightly ahead of the Oracle WebCenter Portal server.
For PeopleTools 8.51, you may need to create and configure a custom OWSM policy in order to fully support WS-Security. For more information, see How to Configure WS-Security for PeopleTools 8.51.
For PeopleTools 8.51, only upper case subject names are supported, requiring that only fully upper case user IDs can be used in WebCenter for the integration to work.

10.5.2 How to Integrate PeopleSoft Applications as WSRP Portlets

This section describes how to expose PeopleSoft applications as WSRP portlets in WebCenter Portal.

This section includes the following subsections:

10.5.2.1 How to Prepare the PeopleSoft Application for Remote Access

This section describes how to prepare the PeopleSoft application so that it can be consumed by WebCenter Portal.

To prepare the PeopleSoft application:

Log into PeopleSoft as an administrator.
Select PeopleTools from the main menu.
From the People Tools main menu, expand Portal.
Select Structure and Content.

The Structure and Content page displays a list of folders containing PeopleSoft objects that could be exposed as a WSRP Portlet (see Figure 10-15).

Figure 10-15 Structure and Content Page

Description of "Figure 10-15 Structure and Content Page"
Navigate to the folder and subfolder (if required) containing the service that you want to expose as portlet in WebCenter Portal and click Edit to open it. For example, you could select Self Service, Personal Information, and then Personal Information Summary.

The Content Ref Administration page displays (see Figure 10-16).

Figure 10-16 Content Ref Administration Page

Description of "Figure 10-16 Content Ref Administration Page"
On the General tab, select the WSRP Producible checkbox.
Save the page.
In the PeopleSoft Application Designer, open the component object to the Request Details page that gets displayed in PeopleSoft, and in the Component Properties section, check the WSRP Compliant check box.
From the main menu, expand PeopleTools and then Portal and select WSRP Production.

The Producer Offered Portlets page displays (see Figure 10-17).

Figure 10-17 Producer Offered Portals Page

Description of "Figure 10-17 Producer Offered Portals Page"
Verify that the service is exposed, and then expand Web Service Endpoint URL and copy the URL (the WSDL).
Open a new tab in your browser, and paste the copied URL into the Navigation Bar to access the WSDL page.
Copy the URL to the clipboard.
Continue by integrating the PeopleSoft WSRP producer in WebCenter Portal as described in How to Integrate PeopleSoft Applications in WebCenter Portal.

10.5.2.2 How to Configure WS-Security for PeopleTools 8.52 and Later

This section describes how to create a keystore for both WebCenter Portal and PeopleSoft, and exchange the private key between them. This step is required prior to adding WS-Security policies for WebCenter Portal.

First, we will create the WebCenter keystore as webcenter.jks with orakey as the private key, and PeopleSoft's public key rootCA and the certificate that PeopleSoft will use as the WS-Security recipient using the following keytool commands:

./keytool -genkeypair -keyalg RSA -dname "cn=orakey,dc=us,dc=oracle,dc=com" -alias orakey -keypass password -keystore webcenter.jks -storepass password -validity 720
 
./keytool -exportcert -v -alias orakey -keystore webcenter.jks -storepass password -rfc -file orakey.cer
 
./keytool -importcert -trustcacerts -alias orakey -file orakey.cer -keystore peoplesoft.jks -storepass password

Next, we will create PeopleSoft keystore as peoplesoft.jks with rootCA as the private key and WebCenter's public key orakey and the certificate that WebCenter will use as the WS-Security recipient.

./keytool -genkeypair -keyalg RSA -dname "cn=rootCA,dc=us,dc=oracle,dc=com" -alias rootCA -keypass password -keystore peoplesoft.jks -storepass password -validity 720
 
./keytool -exportcert -v -alias rootCA -keystore peoplesoft.jks -storepass password -rfc -file rootca.cer
 
./keytool -importcert -trustcacerts -alias rootCA -file rootca.cer -keystore webcenter.jks -storepass password

After creating the key stores for WebCenter Portal and PeopleSoft, copy the peoplesoft.jks to the PeopleSoft host and webcenter.jks to the WebCenter host:
- Copy peoplesoft.jks to <Domain_Home>/config/fmwconfig/
- Copy webcenter.jks to /home/psadm2/psft/pt/8.52/webserv/<Domain_Name>/applications/peoplesoft/pspc.war/WEB-INF/classes
Install the certificate in PeopleSoft as shown below:
1. Log into PeopleSoft as an administrator and navigate to PeopleTools > Security > Security Objects > Digital Certificate.
  
  The Digital Certificates page displays (see Figure 10-18).
  
  Figure 10-18 Digital Certificates Page
  
  Description of "Figure 10-18 Digital Certificates Page"
2. Click +to add a new entry.
  
  We need to add digital certificates for Remote and RootCA as shown in Figure 10-19.
  
  Figure 10-19 Digital Certificates Page
  
  Description of "Figure 10-19 Digital Certificates Page"
3. Enter the Type as RootCA, Alias as orakey, Issuer Allias as orakey, and then click the Search icon (magnifying glass).
4. Click Import and in the popup, enter the entire text of orakey.cer created earlier and click OK.
5. Click +to add another new entry, and enter the Type as Remote, Alias as orakey, Issuer Allias as orakey and then click the Search icon.
6. Click Import and in the popup, enter the entire text of orakey.cer created earlier and click OK.
Update the WSS.properties file under /home/psadm2/psft/pt/8.52/webserv/<Domain_Name>/applications/peoplesoft/pspc.war/WEB-INF/classes to reference the peoplesoft.jks file.
Use PSCipher.sh to create an Encrypted Password and update the KeyStore password as shown in Figure 10-20.

Figure 10-20 PSCipher.sh

Description of "Figure 10-20 PSCipher.sh"
Check the local node definition in PeopleSoft:
1. Navigate to Peopletools > Portals > Node Definitions.
  
  The Nodes page displays.
2. Click Search and click PSFT-HR.
  
  Figure 10-21 Node Definitions Page
  
  Description of "Figure 10-21 Node Definitions Page"
3. Select Password from the Authentication Option drop-down list and click Save.
Continue by adding a WS-Security policy to WebCenter Portal as described in How to Attach a WS-Security Policy to WebCenter Portal.

10.5.2.3 How to Attach a WS-Security Policy to WebCenter Portal

This section describes how to attach a WS-Security policy to WebCenter Portal.

Note:

Before continuing with the steps below you must have configured the WebCenter and PeopleSoft key stores as described in How to Configure WS-Security for PeopleTools 8.52 and Later.

10.5.2.3.1 How to Configure WSS 1.0 SAML Token with Message Integrity

Follow the steps below to configure the WSS1.0 SAML Token with Message Integrity policy for WebCenter Portal:

Navigate to the following directory on the PeopleSoft server:

/home/psadm2/psft/pt/8.53/webserv/peoplesoft/piabin

and run the following command:

./redeployWSRP.sh 6

This will update the PeopleSoft WSRP security options to use WSRPBaseService with SAMLToken Full Security.
In PeopleSoft, navigate to PeopleTools > Security > SAML Administration Setup > SAML Inbound Setup.

The SAML Inbound Setup page displays (see Figure 10-22).

Figure 10-22 SAML Inbound Setup Page

Description of "Figure 10-22 SAML Inbound Setup Page"
Open the Add a New Value tab and map the WebCenter Portal user with the PeopleSoft user if they use a different OID (example settings are shown below), and then click Save.

Example:
- Certificate Alias - orakey
- Issuer - WWW.ORACLE.COM
- SubjectName - pat
- QualifierName - WWW.ORACLE.COM
- Mapping PeopleSoft UserID - PS
Continue by registering the WSRP producer and adding the portlet to a portal page as shown in How to Integrate PeopleSoft Applications in WebCenter Portal.

10.5.2.3.2 How to Configure WSS 1.0 Username Token Without Password

Follow the steps below to attach a WSS 1.0 Username Token without Password policy to WebCenter Portal.

Create a WebCenter user in PeopleSoft:
1. In PeopleSoft, navigate to PeopleTools > Security > User Profiles > Copy User Profiles.
  
  The Copy User Profiles page displays (see Figure 10-23).
  
  Figure 10-23 Copy User Profiles Page - Search Criteria
  
  Description of "Figure 10-23 Copy User Profiles Page - Search Criteria"
2. Search for the user to add (PS, for example).
  
  The search results display (see Figure 10-24).
  
  Figure 10-24 Copy User Profiles Page - Search Results
  
  Description of "Figure 10-24 Copy User Profiles Page - Search Results"
3. Enter the New User ID (for example, Pat), a Description, the New Password, check the Copy ID Type Information option and click Save.
Log into Fusion Middleware Control, select the domain and navigate to Security > Security Provider Configuration.

The Security Provider Configuration page displays.
Open the Keystore section and click Configure.

The Keystore Configuration page displays.
Enter ./webcenter.jks for the KeyStore Path, orakey for the Key Alias, orakey for the Crypt Alias. Enter the associated passwords and click OK.

Note that you must restart the entire domain for the configuration changes to take effect.
Navigate to /home/psadm2/psft/pt/8.53/webserv/peoplesoft/piabin and run the following command:

./redeployWSRP.sh 8

This will update the PeopleSoft WSRP security options to use WSRPBaseService with UsernameToken, No Password Full Security Option With WSS Response.
Continue by registering the WSRP producer and adding the portlet to a WebCenter Portal or portal page as shown in How to Integrate PeopleSoft Applications in WebCenter Portal.

10.5.2.3.3 How to Configure WSS 1.0 SAML Token with Message Protection

Follow the steps below to attach the WSS1.0 SAML Token with Message Protection policy to WebCenter Portal.

Navigate to /home/psadm2/psft/pt/8.53/webserv/peoplesoft/piabin and run the following command:

./redeployWSRP.sh 10

This will update the PeopleSoft WSRP security options to use WSRPBaseService with SAMLToken Full Security Option With WSS Response.
Continue by registering the WSRP producer and adding the portlet to a portal page as shown in How to Integrate PeopleSoft Applications in WebCenter Portal.

10.5.2.3.4 How to Configure WSS 1.0 Username Token with Password

Follow the steps below to attach the WSS1.0 SAML Token with Message Protection policy to WebCenter Portal.

Navigate to /home/psadm2/psft/pt/8.53/webserv/peoplesoft/piabin and run the following command:

./redeployWSRP.sh 7

This will update the PeopleSoft WSRP security options to use WSRPBaseService with UsernameToken Full Security Option With WSS Response.
Continue by registering the WSRP producer and adding the portlet to a WebCenter Portal or portal page as shown in How to Integrate PeopleSoft Applications in WebCenter Portal.

10.5.2.4 How to Integrate PeopleSoft Applications in WebCenter Portal

This section describes how to integrate a PeopleSoft application in WebCenter Portal.

This section contains the following subsections:

10.5.2.4.1 How to Register the PeopleSoft WSRP Producer for WebCenter Portal

You can register the PeopleSoft WSRP producer directly in WebCenter Portal, as described in Registering Portlet Producers in Oracle Fusion Middleware Administering Oracle WebCenter Portal. You can also register the PeopleSoft WSRP producer using Fusion Middleware Control as described in the steps below.

To register the PeopleSoft WSRP producer using Fusion Middleware Control:

Prepare the PeopleSoft page that you want to consume in WebCenter Portal for remote access as described in How to Prepare the PeopleSoft Application for Remote Access.
Log into Fusion Middleware Control for the WebCenter Portal domain (WC_Domain by default).
Expand WebCenter Portal in the Navigation bar and from the WebCenter Portal menu, select Register Producer.

The Add Portlet Producer page displays.
Set the Producer Type to WSRP Producer, enter a Connection Name, and paste the WSDL endpoint URL that you copied in step 1 into the URL End Point field.
If required, configure WS-Security in WebCenter Portal as described in How to Configure WS-Security for PeopleTools 8.51.
Click OK and verify that the producer connection was created successfully.
Continue by adding the portlet to a WebCenter Portal or portal page as described in How to Add the PeopleSoft Portlet to a WebCenter Portal Page.

10.5.2.4.2 How to Add the PeopleSoft Portlet to a WebCenter Portal Page

Follow the steps below to add the PeopleSoft portlet to a WebCenter Portal or portal page:

Log into WebCenter Portal.

If you configured WS-Security, be sure to use the user account that was used in the SAML Inbound Setup page in PeopleSoft (see How to Attach a WS-Security Policy to WebCenter Portal).
Go to the page, or create a new page, where you want to add the PeopleSoft portal.
Click Add Content and in the resource catalog, select UI Components and then Portlets.

Note that if you've created a custom catalog, Portlets may not appear. In this case, you will need to add it to the resource catalog. For information about managing resource catalogs, see Working with Resource Catalog Components on a Page in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.
Click the portlet you added in Fusion Middleware Control.
Click Add for the PeopleSoft page you want to add to your portal page.
On the portal page, click the portlet’s View Actions menu, and select Display Options.
In the Display Options dialog, set Render Portlet in IFrame to True and click OK.
Continue by checking the portlet connection as described in How to Test the Portal Portlet Connection.

10.5.2.4.3 How to Test the Portal Portlet Connection

Follow these steps to test the portlet connection by modifying content and checking that the modification shows up in the PeopleSoft application.

On the WebCenter Portal or portal page that you added the PeopleSoft portlet to, modify some information that you can verify the changes for in the PeopleSoft application.
Save your changes and confirm that the changes also appear in the PeopleSoft application.

10.5.2.5 How to Configure WS-Security for PeopleTools 8.51

This section describes the supported OWSM policies for PeopleTools 8.51. It is important to note that PeopleTools release 8.51 does not support outgoing WS-Security headers in its messages. However, some out-of-the-box Oracle WebCenter Portal/OWSM policies require that both outgoing and incoming messages be secured. To bridge this gap you may need to create custom OWSM policies. The different integration scenarios that would require you to create custom WS-Security policies, and the steps required on the WebCenter Portal side to configure them are also described in this section.

For integration scenarios with PeopleTools 8.51, you can use WSS10 SAML Token with Message Integrity, WSS10 SAML Token with Message Protection, or WSS10 Username Token with Password as the OWSM policy.

This section includes the following subsections:

10.5.2.5.1 How to Configure WS-Security for WSS10 SAML Token with Message Integrity

(PeopleSoft policy: WSRPBaseService with SAMLToken Full Security Option (timestamp) )

This section describes how to configure WS-Security for the WSS10 SAML Token with Message Integrity (oracle/wss10_saml_token_with_message_integrity_client_policy) policy.

To configure WS-Security:

Configure the Oracle WebCenter Portal/OWSM keystore as described in Configuring Web Services Security.
Generate a certificate containing the public key of the Oracle WebCenter Portal domain and send it to the PeopleTools administrator so it can be imported in the PeopleTools configuration.
When you register the producer, choose wss10_saml_token_with_message_integrity_client_policy.
Continue by adding the WSRP portlet to WebCenter Portal.

10.5.2.5.2 How to Configure WS-Security for WSS10 SAML Token with Message Protection

(PeopleSoft policy: WSRPBaseService with SAMLToken Full Security Option (timestamp) With WSS Response)

The default WSS10 SAML Token with Message Protection (oracle/wss10_saml_token_with_message_protection_client_policy) policy that ships with OWSM requires that response also be signed and encrypted. However, PeopleTools release 8.51 and earlier cannot send WS-Security headers in response (only the initial cookie/get portlet handle call contains security headers; subsequent calls do not) and we therefore need to create and attach a custom policy based on the oracle/wss10_saml_token_with_message_protection_client_policy policy.

To create a custom policy:

Log into Fusion Middleware Control and navigate to the Oracle WebCenter Portal domain (WC_Domain by default).
From the WebLogic Domain menu, select Web Services > Policies.
Select the wss10_saml_token_with_message_protection_client_policy and click Create Like.
Give the policy a new name (for example, oracle/wss10_saml_token_with_message_protection_plaintext_response_client_policy).
Open the Response tab, uncheck the Include Entire Body check boxes under Message Signing Setting and Message Encrypt Setting, and save the policy.
Check that the public certificate of the PeopleSoft keystore is imported into the keystore used in the WebCenter Portal domain.
Use WLST to register the producer using the newly created policy as shown in the following example:
```
registerWSRPProducer('webcenter', 'wc-pt851-saml_msg-protection', 'http://xmlns.oracle.com/pspc/pswsdl/ps/EMPLOYEE', timeout=100, tokenType='oracle/wss10_saml_token_with_message_protection_plaintext_response_client_policy', 
enforcePolicyURI='false', issuer='www.oracle.com', sigKeyAlias='webcenter',sigKeyPswd='welcome1', encKeyAlias='webcenter', encKeyPswd='welcome1', recptAlias='peopleTools_public')
```
Use the alias for the imported peoplesft public key as the value for the recptAlias parameter.

Note:

You must use WLST to register the producer. Fusion Middleware Control can only accept fixed policy names and therefore you must register the producer with this policy using WLST by passing in enforcePolicyURI='false'.

10.5.2.5.3 How to Configure WS-Security for WSS10 Username Token with Password

(PeopleSoft policy: WSRPBaseService with UsernameToken Full Security Option With WSS Response)

The default WSS10 Username Token with Password (oracle/wss10_username_token_with_message_protection_client_policy) policy that ships with OWSM requires that response also be signed and encrypted. However, PeopleTools release 8.51 and earlier cannot send WS-Security headers in response (only the initial cookie/get portlet handle call contains security headers; subsequent calls do not) and we therefore need to create and attach a custom policy based on the oracle/wss10_username_token_with_message_protection_client_policy policy.

To create a custom policy:

Log into Fusion Middleware Control and navigate to the WebCenter Portal domain (WC_Domain by default).
From the WebLogic Domain menu, select Web Services > Policies.
Select the wss10_username_token_with_message_protection_client_policy and click Create Like.
Give the policy a new name (for example, oracle/wss10_username_token_with_message_protection_plaintext_response_client_policy).
Open the Response tab, uncheck the Include Entire Body check boxes under Message Signing Setting and Message Encrypt Setting, and save the policy.
Check that the public certificate of the PeopleSoft keystore is imported into the keystore used in the Oracle WebCenter Portal domain.
Use WLST to register the producer using the newly created policy as shown in the following example:
```
registerWSRPProducer('webcenter', '<Producer_Name>', '<URL>', timeout=100,
tokenType='oracle/wss10_username_token_with_message_protection_plaintext_response_client_policy', extApp='<Ext_App_Name>',
enforcePolicyURI='false', issuer='www.oracle.com',
sigKeyAlias='webcenter',sigKeyPswd='welcome1', encKeyAlias='webcenter',
encKeyPswd='welcome1', recptAlias='peopleTools_public') 
```
Use the alias for the imported peoplesft public key as the value for the recptAlias parameter.

Note:

You must use WLST to register the producer. Fusion Middleware Control can only accept fixed policy names and therefore you must register the producer with this policy using WLST by passing in enforcePolicyURI='false'.

10.5.3 How to Integrate PeopleSoft Applications as Data Controls in WebCenter Portal

This section describes how to add PeopleSoft applications as Web service data controls in WebCenter Portal.

This section includes the following subsections:

10.5.3.1 How to Prepare the WSDL

Follow the steps below to prepare a the WSDL.

Log into the PeopleSoft Console as an administrator.
Navigate to PeopleTools > Web Profile > Web Profile Configuration.
Click Search and select DEV from the results list.

Figure 10-25 WebProfile Configuration Page

Description of "Figure 10-25 WebProfile Configuration Page"
Open the General tab and enter the Authentication Domain for your host.

For example, if your host name is ps.example.com, enter .example.com in the Authentication Domain field.
Save your changes and close the application.
Open the C:\Windows\System32\drivers\etc\hosts file for editing.
On a new line enter the IP address and the full host name with the authentication domain.

For example:

193.128.1.113 ps.example.com
Save the file and reboot the server.
Log into the PeopleSoft application using the following URL:

http://<host_name>:8000/ps/signon.html

For example:

http://ps.example.com:8000/ps/signon.html
From the Main Menu, navigate to PeopleTools > Integration Broker > Configuration > Gateways.
Search for the GatewayID LOCAL. The Local Gateway URL is set to

http://<host_name>:8000/PSIGW/PeopleSoftListeningConnector
Using the Local Gateway URL, ping the gateway to make sure it's active.
Open the Gateway Setup Properties and log in as an administrator.
On the PeopleSoft Node Configuration page, check that the node being used is PSFT_HR.
Ping the node
From the Main Menu, navigate to PeopleTools > Integration Broker > Configuration > Service Configuration.
Open Setup Target Locations and check that the Target Location is set to <Local Gateway URL>/PSFT_HR.
From the Main Menu, navigate to PeopleTools > Integration Broker > Integration Setup > Nodes.
Click Search.
Click the Default Local Node PSFT_HR.
On the Nodes tab, check that the Default UserID is set correctly as in the example in Figure 10-26.

Figure 10-26 Nodes Page - Node Definitions

Description of "Figure 10-26 Nodes Page - Node Definitions"
Click Return to Search.
Click the ANONYMOUS node.
Change the Default UserID to the PeopleSoft Login ID (for example, PS) as in the example in Figure 10-27.

Figure 10-27 Nodes Page - Nodes Definitions

Description of "Figure 10-27 Nodes Page - Nodes Definitions"
Save the changes and navigate to Main Menu > PeopleTools > Integration Broker > Web Services > CI-Based Services.
Search for and select the Component Interface Name (for example, CURRENCY) as in the example in Figure 10-28.

Figure 10-28 CI-Based Services Page - Select Component Interfaces

Description of "Figure 10-28 CI-Based Services Page - Select Component Interfaces"
Click Review CI Status.

The CI-Based Services - Review Status page displays (see Figure 10-29).

Figure 10-29 Review CI-Based Status - Review Status Page

Description of "Figure 10-29 Review CI-Based Status - Review Status Page"
Select the available methods (Get and Find, in this case) and click Display Selected Actions.
On the Confirm Actions dialog, click Perform Selected actions.
Click View Service Definition.
Click Provide Web Service.

The Select Service Operations page displays (see Figure 10-30).

Figure 10-30 Select Service Operations Page

Description of "Figure 10-30 Select Service Operations Page"
Select the Select All check box and click Next until you reach the last page.
Click Finish to generate the WSDL.

You should now be able to access the WSDL URL. For this example, the URL would be:

http://ps.example.com:8000/PSIGW/PeopleSoftServiceListeningConnector/PSFT_HR/CI_CURRENCY.1.wsdl\\\\
Continue by creating w Web service data control as shown in How to Create a Web Service Data Control.

10.5.3.2 How to Create a Web Service Data Control

Once you have the WSDL, you can continue by using it to create a Web service data control. In this section we'll continue with the example we started in How to Prepare the WSDL.

Note:

Before you can add a data control or task flow containing a data control to a portal page you must first have configured WS-Security for WebCenter Portal. For more information about configuring WS-Security, see Configuring Web Services Security in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

For more information about creating a Web service data control, see Creating a Web Service Data Control in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal. For information about Web service data controls, see also Web Service Data Controls in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.

To create a Web service data control:

In WebCenter Portal or the portal in which you want to create the data control, go to either the Shared Assets or Assets page.
Select Data Controls and click Create.

The Create New Data Control dialog displays (see Figure 10-31).

Figure 10-31 Create New Data Control Dialog

Description of "Figure 10-31 Create New Data Control Dialog"
In the Create New Data Control dialog, enter a Name and Description for the data control, select Web Service as the Data Control Type, and then click Continue.
Enter the WSDL URL and other details for the data control and click Continue. For our example, the URL would be:

http://ps.example.com:8000/PSIGW/PeopleSoftServiceListeningConnector/PSFT_HR/CI_CURRENCY.1.wsdl
For our example, enter the Default Value for CURRENCY_CD as USD and click Create (see Figure 10-32).

Figure 10-32 Create New Data Control Dialog - CI_Currency_G Method Parameters

Description of "Figure 10-32 Create New Data Control Dialog - CI_Currency_G Method Parameters"
To make the data control available, from the Shared Assets or Assets page, select Task Flows. The Create New Task Flow dialog displays (see Figure 10-33).

Figure 10-33 Create New Task Flow Dialog

Description of "Figure 10-33 Create New Task Flow Dialog"
Click Create to create the task flow.
Select the task flow and click the Edit icon.
Add the data control (with parameter form) as a table onto the task flow and verify the data.
To make the task flow available, navigate to Administration > Business Role Pages.
Select Business Role Page and click the Create icon.
Edit the page. and save the changes.
Drop the task flow onto the page and verify the data.

10.6 Integrating Oracle Business Intelligence Presentation Services

This section explains how to configure WebCenter Portal to integrate with the Oracle Business Intelligence Presentation Services catalog. At runtime, users can add business intelligence objects to their WebCenter Portal pages.

This section includes the following subsections:

10.6.1 About Integrating Oracle Business Intelligence Presentation Services

This section explains how to configure WebCenter Portal to integrate with the Oracle Business Intelligence Presentation Services catalog.

This section includes the following subsections:

10.6.1.1 Understanding Oracle Business Intelligence Presentation Services Integration

Oracle WebCenter Portal users can expand and browse the Presentation Services catalog's folders to view an analysis' views. The following view types display in the Presentation Services catalog: table, pivot table, chart, funnel chart, gauge, narrative, ticker and title. The following view types do not display in the Presentation Services catalog: view selector, column selector, logical SQL, and no-results view.

Users can also browse the dashboard folder for the pages associated with the dashboard; however, users cannot browse within the dashboard pages to see their components (for example, any analyses embedded in the dashboard).

10.6.1.2 Requirements for Integrating Oracle Business Intelligence Presentation Services

You must also set up a connection to the BI application as well as configuring security as described in Creating an Oracle BI EE Presentation Services Connection in Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition. You will also need to specify the credentials for the connection, as described in How to Configure Credentials for Connecting to the Oracle BI Presentation Catalog.

The following prerequisites apply:

Oracle WebCenter Portal

The WC_Portal server has been installed and configured, including the database connection, Content Server connection, and Fusion Middleware Control

OBIEE

Oracle Business Intelligence Applications
OBI Enterprise Edition version 12.2.1.1
OBIEE is already installed, configured, and up and running (Database –OBI Enterprise Edition)
OBI Applications is installed and set up and all content is available from the OBIEE environment (Optional)

Security

The OBIEE integration requires that the identity store user name population be the same across WebCenter and OBIEE. This can be done by either:

Having WebCenter and OBIEE share the same identity store (recommended)
Maintaining identical user names across separate WC and OBIEE identity stores

10.6.1.3 Advanced Integration Options

As well as the approaches to adding resources described in the subsections in Integrating Oracle Business Intelligence Presentation Services, such as adding business intelligence analyses, dashboards, and scorecard components that can be easily dropped onto a page, there are also options for using Web services and BI EE Logical SQL view objects to embed business intelligence data into an application. For more information about using Web services, see Introduction to Oracle Business Intelligence Web Services in Oracle Fusion Middleware Integrator's Guide for Oracle Business Intelligence Enterprise Edition. For more information about using the BI EE Logical SQL view object, see Using the Oracle BI EE Logical SQL View Object in Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition.

10.6.2 How to Configure Credentials for Connecting to the Oracle BI Presentation Catalog

At design time, you need to specify credentials to connect to the Oracle BI Presentation Catalog. These credentials are used to retrieve the list of business intelligence objects (for example, analyses, dashboards, and scorecard components) from the Oracle BI Presentation Catalog.

This process ensures that the login to the Presentation Server is the same as the current user of the application and any access checks are performed as the current user, and data is fetched as the current user. If the ADF page contains business intelligence objects to which the user does not have access, the ADF page returns a message stating that the user does not have the proper permissions to access these objects.

Note that the Perform impersonation parameter should be set to true when security is enabled.

This section contains the following subsections:

10.6.2.1 How to Check for the BIImpersonateUser

Use the following steps to check if a BIImpersonateUser user already exists, and that the roles assigned to it are correct:

Open WLS Administration Console for your Oracle BI EE instance using an Administrator account.
Locate the Domain Structure pane and select Security Realm.

The Realms pane displays.
In the Realms pane, select <myrealm>.

The Settings dialog displays.
In the Settings dialog, open the Users and Groups tab.
Check that BIImpersonateUser appears in the list of users.

If the BIImpersonateUser does not appear in the list, continue by creating the BIImpersonateUser as shown in How to Create the BIImpersonateUser.
Log into Fusion Middleware Control with an administrator account.
From the Weblogic Domain menu, select Security > Application Policies.
On the Application Policies page under Search, choose obi from the Application Stripe dropdown list.
From the Principal Type drop down list, select User.
In the Name field, enter BIImpersonateUser and start the search (Figure 10-34).

Figure 10-34 Application Policies Pane - bifoundation_domain

Description of "Figure 10-34 Application Policies Pane - bifoundation_domain"
If found, check that:
- Resource Name =*
- Resource Type =oracle.bi.user
- Permission Actions = impersonate
- Permission Class =oracle.security.jps.ResourcePermission
If the BIImpersonateUser is not found, continue by adding permissions for the BIImpersonateUser as shown in How to Grant Permissions to BIImpersonateUser.

10.6.2.2 How to Create the BIImpersonateUser

Use the following procedures to create a BIImpersonateUser user to secure an application that uses an Oracle BI EE Presentation Services connection and includes Oracle BI EE objects. ADF security must be enabled for your application before you can apply the impersonator user credentials to the Oracle BI EE Presentation Services connection.

The Impersonate User feature secures applications that contain Oracle BI EE objects when Oracle BI EE and ADF are not sharing an Oracle Internet Directory (OID). Before you begin the process of creating and using Impersonate User, you must confirm that this capability is configured in your environment.

Before you perform this procedure, make sure that either you or the Administrator have created users in the WebLogic Server's Oracle BI EE realm and assigned the BIConsumer group to each user in this realm. For more information, see How to Create and Use Impersonate User in Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition.

Follow the steps below to create the BIImpersonateUser user:

Open WLS Administration Console for your Oracle BI EE instance using an Administrator account.
Locate the Domain Structure pane and select Security Realm.

The Realms pane displays.
In the Realms pane, select <myrealm>.

The Settings dialog displays.
In the Settings dialog, open the Users and Groups tab.
Confirm that the Users tab is displaying and click New.
Enter BIImpersonateUser for the user name and enter a password.
Click OK.

10.6.2.3 How to Grant Permissions to BIImpersonateUser

Follow the steps below to use Fusion Middleware Control to grant permissions to BIImpersonateUser:

From the WebLogic Domain drop down, select Security > Application Policies.

The Search pane displays.
On the Application Policies page under Search, choose obi from the Application Stripe dropdown list. Set the Principle Type as User
Click Create.

The Create Application Grant pane displays (Figure 10-35).

Figure 10-35 Create Application Grant Pane

Description of "Figure 10-35 Create Application Grant Pane"
Under Permissions, click Add a new permission and perform the following actions in the Add Permission pane.

The Add Permission dialog displays (Figure 10-36).

Figure 10-36 Add Permission Dialog

Description of "Figure 10-36 Add Permission Dialog"
1. In the Permission Class list, select oracle.security.jps.ResourcePermission.
2. Select Resource Types.
3. In the Resource Type list, select oracle.bi.user, and click Continue.
4. In the Resource Name field, to impersonate all users, enter *.
5. For Permissions Actions, select impersonate, and then click Select.
Clicking Select will take you back to the Create Application Grant pane.
Under Grantee, click Add users and perform the following actions in The Add Principal pane:
1. In the Type list, User.
2. Click Search Roles.
3. Select BIImpersonateUser, and click OK to return to the Create Application Grant pane.
In the Create Application Grant page, click OK to compete the creation of the security grant.
If the changes that you made do not display, stop and restart the following servers:
- Oracle BI EE Server
- Oracle BI EE Presentation Server
- WebLogic Server

10.6.3 How to Integrate Oracle Business Intelligence Objects in WebCenter Portal

Use the following procedures to configure portal integration with the BI objects.

10.6.3.1 How to Add or Modify a Presentation Services Connection After Deployment

Before you can begin integrating BI objects in WebCenter Portal, you must first configure a connection from WebCenter Portal to the BI server. Oracle BI EE provides an ADF MBean that lets you add a new connection to a deployed portal or BI ADF application. You can also modify a deployed application's existing connection. MBeans are deployed with the application and can be accessed post-deployment using Fusion Middleware Control.

Prior to following the steps below, you should already have followed the steps in How to Configure Credentials for Connecting to the Oracle BI Presentation Catalogto specify credentials to connect to the Oracle BI Presentation Catalog.

Note:

If the portal and the Oracle Business Intelligence application do not share the same identity store, you must create the relevant users in both systems.

Follow the steps below to configure the connection after the application was deployed.

Log into the FMW Control Enterprise Manager of the instance where WebCenter Portal is installed and click on the WebLogic domain drop down menu.
From the list, select System MBean Browser.

The System MBean Browser pane displays.
In the System MBean Browser pane, navigate to the ADF Connections tree node by following the below path:
1. Select the Application Defined MBeans tree node.
2. Select the oracle.adf.share.connections tree node.
3. Select the Server: <my server name> tree node.
  
  For example, Server:DefaultServer or WC_Portal.
4. Select the Application:<your application's name> tree node.
  
  For example, Application:Application2 or webcenter.
5. Open the ADF Connections tree node.
6. Open the child ADF Connections tree node.
  
  The corresponding MBean information displays in the Application Defined MBean pane.
In the Application Defined MBean pane, open the Operations tab and then click createConnection to create a Presentation Services connection.

The Operation:createConnection dialog displays.
Specify the required values for the connection.

In the Connection Type value field, enter BISoapConnection, in the Connection Name value filed, enter for example, biserver and click Invoke to create the connection.
In the System MBean Browser pane, click Refresh to refresh the tree so that the new connection displays.
Continue to expand the tree ADF Connections > BISoapConnection. You should see the biserver connection that was created

The connection's information displays in the Application Defined MBean pane.
Navigate to the Attributes tab.

Enter the BISoap connection information as shown below, and then click Apply to apply your changes.

context = analytics
host = The host name where the BI Server is running
IsStaticResourcesLocationAutomatic = true
Port = 9502(default Analytics port)
protocol = http
StaticResourcesLocation = http://machine.domain:port (This is the default URL for the Analytics port.)   
username =BIImpersonatorUser
password = BIImpersonatorUser user password

Keep the defaults for the rest of the fields and click Apply .
Click on the ADFConnections folder in the Navigation pane, open the Operations tab, and then click Save to save the connection.
When you click Invoke, you should get the following message:

"Confirmation Operation executed successfully."

10.6.3.2 How to Add Oracle BI Objects to a WebCenter Portal Resource Catalog

Before you can add Oracle BI content to a portal page, you must add objects stored in the Oracle BI Presentation Catalog to a WebCenter Portal resource catalog:

Log into WebCenter Portal as an administrator or application specialist.
In the portal browser, click the Administration tile.
Click Shared Assets , then Resource Catalogs.
Click Create.
In the Name field, enter the name of the resource catalog you are creating. Complete the other fields, as necessary.
Make the resource catalog available by selecting its Available check box.
Select the new resource catalog and click Edit.
From the Add menu, select Add From Library.
Double-click Connections.

The BI Presentation Services folder displays.
Open this folder to display the Oracle BI objects and browse to and select the objects that you want to add.
Click Add to add the selected objects to the catalog.

For more information about managing resource catalogs at runtime, see Working with Resource Catalogs in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.

10.6.3.3 How to Add Oracle BI Content at Runtime

Use this procedure to create a portal page and add Oracle BI objects to it. Before you perform this procedure, you must have added Oracle BI objects to a WebCenter Portal resource catalog (see How to Add Oracle BI Objects to a WebCenter Portal Resource Catalog.

Log into WebCenter Portal and create a new portal or access an existing portal.
Make the resource catalog containing the Oracle BI objects the default resource catalog for portal pages. See Choosing Default Resource Catalogs
In the portal editor, create a new page.
In the page editor, click Add Content to open the resource catalog, and browse to the folder containing the Oracle BI objects.
Select an analysis or dashboard and click Add.

The object that you selected is added to the page.

10.6.3.4 How to Modify a Business Intelligence Object's Prompt Values

Use this procedure to test the portal page by changing an analysis or dashboard's filter or prompt values.

Open the page that you created.
In the running page, click Page Actions and then click the Edit link to enter edit mode.
Add an analysis or dashboard that contains a filter or prompt. For more information about adding Oracle BI objects to the page, see How to Add Oracle BI Content at Runtime.
Without exiting the edit mode of the page, save the portal page.
In the portal page, modify the prompt values and click OK.
Exit edit mode, save the page and confirm that the application correctly applied the prompt values.

10.6.3.5 How to Modify a Business Intelligence Task Flow's Initialization Parameters

Use the following procedure to test the business intelligence task flow's initialization parameters.

Open the page that you created.
In the running page, click Page Actions and then click the Edit link to enter the edit mode.
Add an analysis or dashboard that is part of a task flow. For more information about adding business intelligence content to the .jspx page, see How to Add Oracle BI Content at Runtime.
Without exiting the edit mode for the page, save the portal page.
Locate the business intelligence object and click the Edit (wrench) icon.

The Component Properties dialog displays.
On the portal page, open the Parameters tab and modify the object's parameters and click OK.
Open the Parameters tab, modify the object's parameters, and click OK.
Exit edit mode, save the page and confirm that the application correctly applied the modified parameter values.

10.7 Integrating with Oracle Content and Experience Cloud

This section describes how to integrate Oracle Content and Experience Cloud with WebCenter Portal.

It contains the following topics:

10.7.1 About Oracle Content and Experience Cloud Integration

The Oracle DOCS Content Manager task flow enables users to integrate Oracle WebCenter Portal with Oracle Content and Experience Cloud and quickly access documents in Oracle Content and Experience Cloud. You can add, view, manage, and share documents and collaborate in cloud server with robust security from WebCenter Portal.

The Oracle DOCS Content Manager task flow:

Provides easy and secure access to Oracle Content and Experience Cloud from WebCenter Portal
Allows easy collaboration with other people

10.7.2 Integrating Oracle Content and Experience Cloud with WebCenter Portal

To integrate Oracle Content and Experience Cloud with WebCenter Portal:

Add the WebCenter domain in Oracle Content and Experience Cloud to allow the display of embedded content from Oracle Content and Experience Cloud within WebCenter Portal.

Note:

Log in to Oracle Content and Experience Cloud as an administrator. From the user menu, select Administration, then Documents. On the Documents page, enable the Embedded Content option. In the Allowed Domains field, provide portal host name and port number.

For example: hostname:port

For more information, see Embedding Content in Other Domains in Administering Oracle Content and Experience Cloud.
Register Oracle Content and Experience Cloud with WebCenter Portal. For more information, see Creating a Default Oracle Content and Experience Cloud Connection Using WLST.
Add the Oracle DOCS Content Manager task flow to a portal page. For more information, see Adding the Oracle DOCS Content Manager Task Flow to a Page in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.
(Optional) Customize the Oracle Content and Experience Cloud connection. For more information, see Customizing the Oracle Content and Experience Cloud URL Connection in Oracle Fusion Middleware Building Portals with Oracle WebCenter Portal.

Note:
You can customize the Oracle Content and Experience Cloud connection to change the default URL connection to a different connection.

10.7.3 Creating a Default Oracle Content and Experience Cloud Connection Using WLST

Create a default Oracle Content and Experience Cloud URL Connection in Oracle WebCenter Portal using WLST, use WLST command adf_createHttpURLConnection.

The following is the syntax for the WLST command:

adf_createHttpURLConnection(appName=<application name>, name=<connection name>, url='http://<host>:<port>/documents')

where,

appName is the application name, for example webcenter.
name is the default URL connection. Set the name as WCP-DCS.
<host>:<port> is the host and the port of the of your Oracle Content and Experience Cloud.

Example:

 adf_createHttpURLConnection(appName='webcenter', name='WCP-DCS', url='http://<host>:<port>/documents')

For more information on WLST, see Oracle WebLogic Scripting Tool (WLST).

You can list the created connection and also delete the connection using the following WLST commands

To list the connections created, use the following WLST command:

adf_listURLConnection(appName=<application name>)

For example:

adf_listURLConnection(appName='webcenter')

To delete the connection use

deleteConnection(appName=<application name>, name='connection name')

For example:

deleteConnection(appName='webcenter', name='WCP-DCS')