Skip Headers
Oracle® Fusion Middleware Developer's Guide for Oracle WebCenter Portal
11g Release 1 (11.1.1.7.0)

Part Number E10148-20
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

54 Integrating Other Oracle Applications

This chapter describes how you can integrate other Oracle applications with your WebCenter Portal application.

This chapter contains the following sections:

54.1 Integrating Oracle and Other Applications in WebCenter Portal

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 and JPDK portlets) other application components. Figure 54-1 shows the technologies involved in WebCenter Portal integration with other Oracle applications.

Figure 54-1 WebCenter Portal Integration

Description of Figure 54-1 follows
Description of "Figure 54-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 54-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 or JPDK 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.

54.2 Integrating Siebel Applications

This section describes how to integrate a Siebel Web service in a Framework application. It also describes how to integrate Siebel objects using the Siebel Web Engine (SWE). Siebel and WebCenter Portal can work together to include Siebel's CRM capabilities as portlets within your Framework application. You can integrate Siebel applications as Web services, or using the Siebel Web Engine (SWE) as described in the following subsections:

54.2.1 Integrating Siebel Applications as Web Services

This section describes how to integrate Siebel applications as Web services in a Framework application.

This section contains the following subsections:

54.2.1.1 Preparing 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 to your Framework application.

This section contains the following subsections:

54.2.1.1.1 Creating an Inbound Web Service

To create an inbound Web service:

  1. Log into the Siebel application.

  2. Navigate to the Administration - Web Services page.

  3. 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.

  4. Click Menu and select New Record from the drop-down list.

  5. 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


  6. Scroll to the Service Ports pane and select New Record from the Menu drop-down list.

  7. Enter CustAccount as the Name and click Type.

  8. In the Inbound Web Service Port Type pick applet, open the New tab.

  9. Select Business Service as the Implementation Type.

  10. From the Service Name list, select Siebel Account.

  11. In the Inbound Web Service Port Type pick applet, click OK to create the inbound Web service.

  12. From the Service Ports dialog's Transport drop-down list, select HTTP.

  13. 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
    
  14. From the Menu drop-down list, select Save Record.

54.2.1.1.2 Creating Operations for the Inbound Web Service

To add operations to the inbound Web service and then create a WSDL file, perform the following steps:

  1. Scroll to the Operations section and select New from the Menu drop-down list.

  2. In the Operation Name field, enter AccountInsert.

  3. Click Method Display Name to open the Business Service Method dialog.

  4. Select Insert as the Method, and click OK.

  5. 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.


  6. Click New to create a new operation.

  7. In the Operation Name field, enter a name for the new operation (for example, AccountQueryByExample).

  8. Click Method Display Name for the new operation.

  9. In the Business Service Method dialog, select the query method (for example, Query By Example) and click OK.

  10. Continue by adding any additional operations you may need as described in steps 6 to 9 above.

  11. In the Service Ports pane, select Save Record from the Menu drop-down list.

  12. In the Inbound Web Services pane, select Save Record from the Menu drop-down list.

  13. Select Clear Cache from the Menu drop-down list.

  14. Click the Generate WSDL.

  15. On the File Download dialog, click Open.

  16. Select File --> Save As...

  17. Locate the directory where you want to save the WSDL file, enter a name for the file and click Save.

54.2.1.2 Consuming a Siebel Web Service in a Framework Application

This section describes how to consume Siebel applications that have been set up as Web services in a Framework application, including how to set up a WSDL-based data control and, how to use JDeveloper's JSF Navigation Modeler to diagrammatically create your application's pages and the navigation between them.

This section contains the following subsections:

54.2.1.2.1 Creating a Data Control Based on a Siebel Web Service

This section describes how to create a WSDL-based data control based on a Web service created from a Siebel application.

To create a WSDL-based data control:

  1. Open your Framework application or create a new Framework application in JDeveloper.

  2. In the Applications Navigator, right-click the Model node and select New from the context menu.

  3. In the New Gallery, select All Technologies from the Filter By drop-down list.

  4. Select Business Tier | Web Services as the category, select the Web Service Data Control item, and click OK.

  5. In the Create Web Service Data Control wizard, click Next to leave the Welcome page.

  6. In Step 1, enter the Web service name in the Name field.

  7. Click Browse for the URL field, locate the directory where you downloaded the WSDL file, select the file and click Open.

    In the wizard, note the URL generated in the Service field.

  8. Click Next.

    Step 2 shows all the operations available from the selected Web service.

  9. Using the Add button, shuttle the operations you want to the Selected pane., and then click Next.

    When you expand the Model node in the Applications Navigator, you should see nodes for the entries that you have created.

  10. Click the Save All icon to save your changes.

54.2.1.2.2 Creating a Page Flow Diagram

-

This section describes how to create the page flow diagram to which you can your add source and query pages.

To create a page flow diagram:

  1. In the Applications Navigator, right-click the ViewController node and select New from the context menu.

  2. In the New Gallery, expand the Web Tier node and select JSF.

  3. In the Items pane, select JSF Page Flow & Configuration (faces-config.xml) and click OK.

  4. In the Create JSF Configuration File dialog, click OK to accept default values.

    An empty page flow diagram opens with a Component Palette and Data Control Palette to the right of the diagram editor. You use this to create components for the JSF Navigation Model.

  5. Click the Save All icon to save your changes.

54.2.1.2.3 Adding Pages and Navigation to the Page Flow Diagram

This section describes how to add pages and navigation to the page flow diagram.

To add pages to the page flow diagram:

  1. In the JSF Navigation Diagram Component Palette, create a source page by selecting JSF Page, clicking the diagram and naming the page appropriately (for example, QueryByID). Typically, you will have at least a source and query page.

  2. To create the query page, click and drag another JSF Page from the Component Palette and drop it next to the previous one, renaming it appropriately (for example, ShowResult).

  3. Select JSF Navigation Case in the JSF Navigation Diagram Component Palette. Click the icon for the source JSF page, and then click the icon for the destination JSF page for the navigation case.

  4. Modify the default label (success) by clicking it and entering an appropriate name (for example, toResult).

  5. Open the Overview tab and click Navigation Rules.

    The rule you just created in the diagram should be listed in the table.

    JDeveloper gives you three views of the faces-config.xml file: The same information that is presented in the diagram is also accessible through a declarative dialog and directly from the source. If you open the source view (by clicking the Source tab) the <from-view-id> tag identifies the source page, and the <to-view-id> tag identifies the destination page.

  6. From the diagram view, select JSF Navigation Case in the Component Palette. Click the icon for the source JSF page, and then click the icon for the destination JSF page for the navigation case.

  7. Modify the default label by clicking it and entering an appropriate name (for example, toQuery).

  8. Click the Save All icon to save the diagram.

54.2.1.2.4 Creating the Query Page

This section describes how to create and set up navigation for the query page.

To create the query page:

  1. On the Page Flow diagram, double-click the source page icon (QueryById) to launch the Create JSF JSP Wizard.

  2. Click Next to leave the Welcome page.

  3. In Step 1 of the wizard, select JSP Document (*.jspx) and click Next.

  4. In Step 2, make sure Do Not Automatically Expose UI Components in a Managed Bean is selected and click Next.

  5. In Step 3, make sure the following libraries are selected:

    ADF Faces Components 10_1_3_2_0 
    ADF Faces HTML 10_1_3_2_0
    JSF Core 1.0 
    Cusomizable Components Core 10_1_3_2_0 
    
  6. Click Finish to create the page.

    An empty JSF page opens in the Design tab of the editor.

  7. In the Customizable Components Core component palette, click ShowDetailFrame.

    The ShowDetailFrame appears in the page.

    Note:

    Oracle WebCenter Portal provides two customizable components: PanelCustomizable and ShowDetailFrame. These two components make it very easy to organize the content of your Web application, treating different panels as if they are almost stand-alone, portlet-like objects that can be minimized, rearranged, have their own drop-down menus, and so on.

  8. With the ShowDetailFrame selected, modify the Text property in the Properties Inspector to Query By ID. Press [Enter] to update the page in the Visual Editor.

  9. Open the Data Control palette and expand the Siebel Web services node. Drag and drop the AccountQueryById(String) node onto the ShowDetailFrame on the page.

  10. In the popup menu, select Create | Parameters | ADF Parameter Form.

  11. In the Edit Form Fields, click OK.

  12. Select the AccountQueryById button generated in the page and in the Property Inspector pane, change the following properties:

    Text     Submit
    Action        toResult
    
  13. Select the input field corresponding to the input value, and in the Property Inspector, change the Label property to Account ID:

  14. Click the Save All icon to save your work.

54.2.1.2.5 Creating the Results Page

This section describes how to create and add navigation for the results page.

To create the results page:

  1. Click the faces-config.xml tab to return to the Page Flow diagram and double-click the ShowResult icon to launch the page wizard.

  2. Click Next to skip the Welcome page.

  3. In Step 1 of the wizard, select JSP Document (*.jspx) and click Next.

  4. In Step 2, make sure Do Not Automatically Expose UI Components in a Managed Bean is selected and click Next.

  5. In Step 3, make sure the following libraries are selected:

    ADF Faces Components 10_1_3_2_0 
    ADF Faces HTML 10_1_3_2_0
    JSF Core 1.0 
    
  6. Click Finish to create the page.

    An empty JSF page opens in the Design tab of the editor.

  7. In the Customizable Components Core component palette, click ShowDetailFrame.

    The ShowDetailFrame appears in the page.

  8. With the ShowDetailFrame selected, modify the Text property in the Properties Inspector to Query Results. Press [Enter] to update the page in the Visual Editor.

  9. In the Data Control palette, expand AccountQueryById | Return | SiebelMessage | ListofAccountInterface, select the Account node and drop it on the page on the ShowDetailFrame.

  10. In the popup menu, select Create | Forms | ADF Read-only Form.

  11. In the Edit Form Fields, delete all fields except for the following:

    AccountID 
    AccountStatus 
    NumberOfEmployees 
    CurrencyCode 
    Location 
    MainPhoneNumber 
    Name 
    Type
    
  12. Check the Include Submit Button checkbox and click OK.

  13. In the Action Binding Editor, click OK.

  14. Click Submit and in the Property Inspector change the title to Back to Query, and in the Action field select toQuery from the list.

  15. Click the Save All icon to save your work.

54.2.1.2.6 Testing the Application

This section describes how to test the application's JSF pages in JDeveloper. Before you can query a Siebel Account using an ID, you need to determine the IDs that are available in your Siebel instance. To perform the following steps you must have access to Siebel Call Center.

To determine the IDS and test your JSF pages:

  1. Log into Siebel Call Center, providing the appropriate user ID and password.

  2. Navigate to the Accounts List using Site Map.

  3. Click Accounts, then Accounts List.

  4. From the returned list, highlight the account you want to query.

  5. From the Help menu, select About Record.

  6. Find the ID value in the Row # field and make a note of it.

  7. Return to the page flow diagram and right-click the QueryById page icon and select Run from the context menu.

    The page is loaded in your default browser.

  8. In the ID field, enter the value you previously noted in the the Row # field and click Submit.

    The Details page displays the detail information for the corresponding account.

54.2.2 Integrating Siebel Applications Using the Siebel Web Engine

As well as integrating Siebel applications using Web Services, you can also integrate Siebel applications in a Framework application using the Siebel Web Engine (SWE).

Siebel Web Engine (SWE) is responsible for rendering the Siebel User Interface. Siebel Web Templates provide this HTML layout information (markup information) to the Siebel Web Engine when rendering Siebel objects in the repository definition of the application. The markup that SWE returns can also be XML for rendering within XML-aware applications or WML (wireless markup language) for rendering on wireless devices. This lets you request the SWE to return a Siebel View as XML, parse the data elements, and display the result in a Framework application.

For instructions on how to use SWE within a Framework application, follow the tutorial Using the Siebel Web Engine (SWE) to View Data in a WebCenter Application.

To complete the tutorial, you will need the following:

  • Have access to or have installed Oracle JDeveloper Studio Edition

  • Have access to or have installed Oracle's Siebel eBusiness Applications.

  • Have access to a supported version of Windows Internet Explorer (IE) (see the System Requirements and Supported Platforms Guide for Siebel that is available on OTN).

Also refer to the Siebel Bookshelf Guides: Siebel Portal Framework Guide (specifically, the section on delivering content to external Web applications), and Configuring Siebel Business Applications Guide for details on SWE and Web Templates.

54.3 Integrating E-Business Suite Applications

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

This section contains the following subsections:

54.3.1 Introduction to Integrating EBS Applications

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

This section includes the following subsections:

54.3.1.1 Understanding EBS Integration

Out-of-the-box, Oracle E-Business Suite OA Framework-based portlets, such as Applications Navigator, Favorites, and Worklist 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: Framework applications or WebCenter Portal: Spaces, by simply adding the portlet onto an application page. Follow the instructions in Section 54.3.2.3, "Creating a JSF Page to Consume the Remote Producer" to add them to a Framework application page, or Section 54.3.3.3, "Adding the EBS Portlet to a Spaces Page" to add them to a Spaces page.

You can also create new E-Business Suite portlets that are WSRP and JSR 168-compliant that can similarly be added to a Framework application. Creating and consuming WSRP and JSR 168 compliant portals in WebCenter Portal is described in Section 54.3.2, "Integrating EBS Applications in a Framework Application" and Section 54.3.3, "Integrating EBS Applications in Spaces."

54.3.1.2 Requirements for Integrating EBS Applications

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

  • 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 should be configured to use Oracle Internet Directory (OID) and one of following single sign-on solutions:

    • 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.

  • You must have granted the WebCenter Portal application 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.

54.3.2 Integrating EBS Applications in a Framework Application

This section includes the following subsections:

54.3.2.1 Preparing the EBS Portlet for Remote Access

The Oracle E-Business Suite OA Framework lets you expose any standalone regions (except pageLayout regions) as portlets. Page layout regions cannot be exposed as portlets because portlets are always rendered inside an HTML table cell and page layout regions contain HTML constructs that cannot be rendered within a table cell.

Note:

The Oracle Application Framework Provider handles the form submission using HTTP GET as per the Java Portlet Specification. (Refer to PLT.16.3 The Include Method - "Servlets and JSPs included from portlets must be handled as HTTP GET requests."). Due to this limitation, any regions requiring data entry (like search criteria regions, LOVs, text inputs, etc.) should not be exposed as portlets.

Tip:

You can also use an Oracle E-Business Suite tool called Portlet Generator to convert existing standalone Oracle Application Framework regions into portlets. For more information about Portlet Generator, see the Oracle E-Business Suite System Administrator's Guide - Configuration.

To expose your region as a portlet:

  1. Create a UI Function to register your region as a portlet. See Tabs/Navigation for more information regarding the creation of UI Functions.

  2. Set the following properties within your new UI Function:

    • Function Type = Web Provider Portlet (internal value is WEBPORTLET).

      In order to define a WSRP/JSR168-compliant portlet, a user needs to add an extra parameter to the portlet function definition. # Parameters = OA_JSR168_PORTLET=Y

    • HTML call = OA.jsp?region=<your region Reference>

      For example: OA.jsp?region=/oracle/apps/fnd/wf/worklist/webui/WorklistPrtletRG

      If your portlet includes a drill-down page, append a parameter to the above URI specifying the target of the drill down using a page reference or a function name. For example:

      1. &detailPage=<target page>

        For example:

        OA.jsp?region=/oracle/apps/fnd/wf/worklist/webui/WorklistPrtletRG
        &detailPage=/oracle/apps/fnd/wf/worklist/webui/AdvancWorklistPG
        
      2. &detailFunction=<Form Function name>

        For example:

        OA.jsp?region=/oracle/apps/fnd/wf/worklist/webui/WorklistPrtletRG
        &detailFunction=WF_WORKLIST_DRILL_FUNC
        
  3. Optionally disable portlet personalization.

    By default, all portlets rendered using the OA Framework Web Provider include a Customize link in the title bar. Clicking on the link displays a customization page that lets you change the portlet title and responsibility. With this page you can customize the portlet title and assign a responsibility to it. Customizing the responsibility is useful when a portlet content is dependent on the responsibility context, and is associated with multiple responsibilities.

    To disable portlet customization, append &dispRespCustPg=N to the HTML call URI.

    For example:OA.jsp?region=/oracle/apps/fnd/wf/worklist/webui/WorklistPrtletRG&dispRespCustPg=N
    
  4. Associate help text defined using Oracle online Help with your portlet.

    When you associate help text with your portlet, the OA Framework Web Provider renders a help text icon (?) in the portlet title bar. Clicking the icon displays the help text.To associate help text with your portlet, append &oawpHelpTarget=<Oracle online Help reference> to the HTML call URI.

    For example:OA.jsp?region=/oracle/apps/fnd/wf/worklist/webui/WorklistPrtletRG&oawpHelpTarget=worklistHelp
    

After creating the portlets, grant access to your new UI Function by adding it to a menu and associating the menu with a responsibility. Before adding the portlets in WebCenter Portal, be sure to bounce the Apache listener as the menu and function definitions are cached. Note that you'll need system administrator permissions to do this.

54.3.2.2 Registering the EBS WSRP Producer in the Framework Application

Follow the instructions below to create or open an existing Framework application, and register the EBS WSRP producer.

  1. Create a new Framework application or open an existing one in which you would like to consume the remote (WSRP) EBS portlet.

  2. Under Application Resources, right-click Connection and select WSRP Producer.

    Page 1 (Specify Producer Name) of the Register WSRP Portlet Producer wizard displays.

  3. Enter a name for the WSRP producer and click Next.

    The Specify Connection Details page displays.

  4. Enter the WSDL for the EBS producer in the WSDL URL field as shown below:

    WSDL URL: http://[Release_12_host]:[port]/OA_HTML/portlets/WSRPBaseService?WSDL
    

    For example:

    http://myEBSServer.example.com:8001/OA_HTML/portlets/WSRPBaseService?WSDL
    
  5. Click Next and then Finish.

    The WSRP producer should now appear under Connections.

  6. Continue by creating a JSF page to consume the WSRP producer as described in Section 54.3.2.3, "Creating a JSF Page to Consume the Remote Producer."

54.3.2.3 Creating a JSF Page to Consume the Remote Producer

Use the following procedure to add or use an existing JSF page to consume the EBS remote producer in your Framework application.

To create a JSF page:

  1. In the application's Navigation panel, right-click on the application name and select New.

    The New Gallery dialog displays.

  2. In the Categories field's tree structure, locate and expand the Web Tier.

    A list with the descriptions of the available options display in the Items field.

  3. From this list, select JSF Page and click OK.

    The Create JSF Page dialog displays.

  4. Create the JSF page, making sure that the Create an XML Document (*.jspx) field is selected. For more information about setting up the JSF page, click the Help button to access the online help.

  5. Click OK.

    The newly created JSF page displays.

  6. Under connections, expand the newly created WSRP producer and drag the portlet for the EBS page onto the JSF page.

  7. In the Portlet Property Inspector, set the RenderPortletInIFrame property to True.

  8. Add any other components that you need onto the page, and save the application.

  9. Continue by running the page and testing that modifications made in the Framework application appear in the EBS application as described in Section 54.3.2.4, "Testing the Framework Application."

54.3.2.4 Testing the Framework Application

Use this procedure to test the Framework application by modifying content on the JSF page in the Framework application and checking that the modification shows up in the EBS application.

  1. Run the .jspx page that you created.

  2. In the running page, modify some information that you can verify the changes for in the EBS application.

  3. Save your changes and confirm that the changes also appear in the EBS application.

54.3.3 Integrating EBS Applications in Spaces

This section contains the following subsections:

54.3.3.1 Preparing the EBS Portlet for Remote Access

Prepare the standalone regions to be portletized as described the section on Section 54.3.2.1, "Preparing the EBS Portlet for Remote Access."

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

54.3.3.2 Registering the EBS WSRP Producer in Spaces

You can register the EBS WSRP producer directly in Spaces, as described in the section on "Registering Portlet Producers" in Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces. You can also register the EBS WSRP producer using Fusion Middleware Control as described in the steps below.

To register the EBS WSRP producer using Fusion Middleware Control:

  1. Prepare the EBS page that you want to consume in Spaces for remote access as described in Section 54.3.3.1, "Preparing the EBS Portlet for Remote Access."

  2. Log into Fusion Middleware Control for the Spaces domain.

  3. Expand Spaces in the Navigation bar and from the WebCenter Portal menu, and select Register Producer.

    The Add Portlet Producer page displays.

  4. 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.

  5. Click OK and verify that the producer connection was created successfully.

  6. Continue by adding the portlet to a Spaces page as described in Section 54.3.3.3, "Adding the EBS Portlet to a Spaces Page."

54.3.3.3 Adding the EBS Portlet to a Spaces Page

Use the following procedure to consume the EBS remote producer in Spaces.

  1. Log into Spaces.

  2. Go to the page, or create a new page, where you want to add the EBS portal.

  3. Click Add Content to open Composer.

  4. From the Resource Catalog, select Portlets.

    Note that if you've created a custom catalog, Portlets may not appear, in which case you will need to add it to the Resource Catalog. For information about managing Resource Catalogs, see the chapter "Working with Resource Catalogs" in the Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces.

  5. Click the portlet you added in Fusion Middleware Control.

  6. Click Add for the EBS portlet you want to add to your Spaces page.

  7. Click Close to close Composer.

  8. On the Spaces page, click the Edit (pencil) icon.

  9. Open the Display Options tab and set the Render Portlet in IFrame option to True and click OK.

  10. Continue by checking the portlet connection as described in Section 54.3.3.4, "Testing the Spaces Portlet Connection."

54.3.3.4 Testing the Spaces Portlet Connection

Use this procedure to test the Spaces portlet connection by modifying content and checking that the modification shows up in the EBS application.

  1. On the Spaces page that you added the EBS portlet to, modify some information that you can verify the changes for in the EBS application.

  2. Save your changes and confirm that the changes also appear in the EBS application.

54.4 Integrating JD Edwards Applications

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

This section contains the following subsections:

54.4.1 Integrating JD Edwards Applications in a Framework Application

This section includes the following subsections:

54.4.1.1 Preparing the JD Edwards Application for Remote Access

Before you can add JD Edwards standalone regions to Framework applications, 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 Framework application page.

54.4.1.2 Registering the JD Edwards WSRP Producer in the Framework Application

Follow the instructions below to create or open an existing Framework application, and register the JD Edwards WSRP producer.

  1. Create a new Framework application or open an existing one in which you would like to consume the remote (WSRP) JD Edwards portlet.

  2. Under Application Resources, right-click Connection and select WSRP Producer.

    Page 1 (Specify Producer Name) of the Register WSRP Portlet Producer wizard displays.

  3. Enter a name for the WSRP producer and click Next.

    The Specify Connection Details page displays.

  4. Paste the WSDL URL for the JD Edwards producer into the WSDL URL field.

  5. Click Next and then Finish.

    The WSRP producer should now appear under Connections.

  6. Continue by creating a JSF page to consume the WSRP producer as described in Section 54.4.1.3, "Creating the JSF Page to Consume the Remote Producer."

54.4.1.3 Creating the JSF Page to Consume the Remote Producer

Use the following procedure to add or use an existing JSF page to consume the JD Edwards remote producer in your Framework application.

To create a JSF page:

  1. In the application's Navigation panel, right-click on the application name and select New.

    The New Gallery dialog displays.

  2. In the Categories field's tree structure, locate and expand the Web Tier.

    A list with the descriptions of the available options display in the Items field.

  3. From this list, select JSF Page and click OK.

    The Create JSF Page dialog displays.

  4. Create the JSF page, making sure that the Create an XML Document (*.jspx) field is selected. For more information about setting up the JSF page, click the Help button to access the online help.

  5. Click OK.

    The newly created JSF page displays.

  6. Under connections, expand the newly created WSRP producer and drag the portlet for the JD Edwards page onto the JSF page.

  7. In the Portlet Property Inspector, set the RenderPortletInIFrame property to True.

  8. Add any other components that you need onto the page, and save the application.

  9. Continue by running the page and testing that modifications made in the Framework application appear in the JD Edwards application as described in Section 54.4.1.4, "Testing the Framework Application."

54.4.1.4 Testing the Framework Application

Use this procedure to test the Framework application by modifying content on the JSF page in the Framework application and checking that the modification shows up in the JD Edwards application.

  1. Run the .jspx page that you created.

  2. In the running page, modify some information that you can verify the changes for in the JD Edwards application.

  3. Save your changes and confirm that the changes also appear in the JD Edwards application.

54.4.2 Integrating JD Edwards Applications in Spaces

This section contains the following subsections:

54.4.2.1 Registering the Producer

You can register the JD Edwards WSRP producer directly in Spaces, as described in the section on "Registering Portlet Producers" in Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces. 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:

  1. Prepare the JD Edwards page that you want to consume in Spaces for remote access as described in Section 54.4.1.1, "Preparing the JD Edwards Application for Remote Access."

  2. Log into Fusion Middleware Control for the Spaces domain.

  3. Expand Spaces in the Navigation bar and from the WebCenter Portal menu, and select Register Producer.

    The Add Portlet Producer page displays.

  4. 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.

  5. Click OK and verify that the producer connection was created successfully.

  6. Continue by adding the portlet to a Spaces page as described in Section 54.4.2.2, "Adding the JD Edwards Portlet to a Spaces Page."

54.4.2.2 Adding the JD Edwards Portlet to a Spaces Page

Use the following procedure to consume the JD Edwards remote producer in Spaces.

  1. Log into Spaces.

  2. Go to the page, or create a new page, where you want to add the JD Edwards portal.

  3. Click Add Content to open Composer.

  4. From the Resource Catalog, select Portlets.

    Note that if you've created a custom catalog, Portlets may not appear, in which case you will need to add it to the Resource Catalog. For information about managing Resource Catalogs, see the chapter "Working with Resource Catalogs" in the Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces.

  5. Click the portlet you added in Fusion Middleware Control.

  6. Click Add for the JD Edwards portlet you want to add to your Spaces page.

  7. Click Close to close Composer.

  8. On the Spaces page, click the Edit (pencil) icon.

  9. Open the Display Options tab and set the Render Portlet in IFrame option to True and click OK.

  10. Continue by checking the portlet connection as described in Section 54.4.2.3, "Testing the Spaces Portlet Connection."

54.4.2.3 Testing the Spaces Portlet Connection

Use this procedure to test the Spaces portlet connection by modifying content and checking that the modification shows up in the JD Edwards application.

  1. On the Spaces page that you added the JD Edwards portlet to, modify some information that you can verify the changes for in the JD Edwards application.

  2. Save your changes and confirm that the changes also appear in the JD Edwards application.

54.5 Integrating PeopleSoft Applications

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

This section contains the following subsections:

54.5.1 Introduction to Integrating PeopleSoft Applications

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

This section includes the following subsections:

54.5.1.1 Understanding PeopleSoft Integration

PeopleTools 8.48 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 a WebCenter Portal application without needing to open or learn the entire PeopleSoft application.

54.5.1.2 Requirements for Integrating PeopleSoft Applications

This section the prerequisites for integrating PeopleSoft objects in Framework applications, and Spaces.

  • PeopleTools 8.48 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 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 WebCenter Portal server.

  • For PeopleTools 8.5.1 and earlier, you may need to create and configure a custom OWSM policy in order to fully support WS-Security. For more information, see Section 54.5.5, "Setting up WS-Security for PeopleTools."

54.5.2 Preparing the PeopleSoft Application for Remote Access

This section describes how to prepare the PeopleSoft application so that it can be consumed by Spaces or a Framework application.

To prepare the PeopleSoft application:

  1. Log into PeopleSoft as an administrator.

  2. Select PeopleTools from the main menu.

  3. From the People Tools main menu, expand Employee Self-Service, and then Portal.

  4. Select Structure and Content.

  5. Navigate to the folder containing the page that you want to consume in WebCenter Portal and click Edit to open it.

    The Content Ref Administration page displays.

  6. On the General tab, select the WSRP Producible checkbox.

  7. Save the page.

  8. From the main menu, select WSRP Production.

    The Producer Offered Portlets page displays.

  9. Verify that the page is exposed, and then expand Web Service Endpoint URL and copy the URL (the WSDL).

  10. Open a new tab in your browser, and paste the copied URL into the Navigation Bar to access the WSDL page.

  11. Copy the URL to the clipboard.

  12. Continue by integrating the PeopleSoft WSRP producer in Spaces or Framework application as described in Section 54.5.3, "Integrating PeopleSoft Applications in a Framework Application" and Section 54.5.4, "Integrating PeopleSoft Applications in Spaces."

54.5.3 Integrating PeopleSoft Applications in a Framework Application

This section describes how to create or modify a Framework application that integrates with PeopleSoft Applications.

This section includes the following subsections:

54.5.3.1 Registering the PeopleSoft WSRP Producer in the Framework Application

Follow the instructions below to create or open an existing Framework application, and register the PeopleSoft WSRP producer.

  1. Create a new Framework application or open an existing one in which you would like to consume the remote (WSRP) PeopleSoft portlet.

  2. Under Application Resources, right-click Connection and select WSRP Producer.

    Page 1 (Specify Producer Name) of the Register WSRP Portlet Producer wizard displays (see Figure 54-2).

    Figure 54-2 Specify Producer Name

    Description of Figure 54-2 follows
    Description of "Figure 54-2 Specify Producer Name"

  3. Enter a name for the WSRP producer and click Next.

    The Specify Connection Details page displays (see Figure 54-3).

    Figure 54-3 Specify Connection Details

    Description of Figure 54-3 follows
    Description of "Figure 54-3 Specify Connection Details"

  4. Paste the WSDL (the URL you copied earlier) into the WSDL URL field and click Next.

  5. If you need to configure WS-Security, click Next.

    For more information about configuring WS-Security, refer to Section 54.5.5, "Setting up WS-Security for PeopleTools."

  6. Click Finish.

    The WSRP producer should now appear under Connections.

  7. Continue by creating a JSF page to consume the WSRP producer as described in Section 54.5.3.2, "Creating the JSF Page to Consume the Remote (WSRP) Producer."

Note:

Compression must be turned off in WLS to expose WSRP Portlets. Compression is enabled by default in the Producer Web Server running with Weblogic 10.3.2 and must be disabled in the Server Manager setting for compression available for each instance.

54.5.3.2 Creating the JSF Page to Consume the Remote (WSRP) Producer

Use the following procedure to add a JSF page to consume the PeopleSoft remote producer.

To create a JSF page:

  1. In the application's Navigation panel, right-click on the application name and select New.

    The New Gallery dialog displays.

  2. In the Categories field's tree structure, locate and expand the Web Tier.

    A list with the descriptions of the available options display in the Items field.

  3. From this list, select JSF Page and click OK.

    The Create JSF Page dialog displays.

  4. Create the JSF page, making sure that the Create an XML Document (*.jspx) field is selected. For more information about setting up the JSF page, click the Help button to access the online help.

  5. Click OK.

    The newly created JSF page displays.

  6. Under connections, expand the newly created WSRP producer and drag the portlet for the PeopleSoft page onto the JSF page.

  7. In the Portlet Property Inspector, set the RenderPortletInIFrame property to True.

  8. Add any other components that you need onto the page, and save the application.

  9. Continue by running the page and testing that modifications made in the Framework application appear in the PeopleSoft application as described in Section 54.5.3.3, "Testing the Framework Application."

54.5.3.3 Testing the Framework Application

Use this procedure to test the Framework application by modifying content on the JSF page in the Framework application and checking that the modification shows up in the PeopleSoft application.

  1. Run the .jspx page that you created.

  2. In the running page, modify some information that you can verify the changes for in the PeopleSoft application.

  3. Save your changes and confirm that the changes also appear in the PeopleSoft application.

54.5.4 Integrating PeopleSoft Applications in Spaces

This section describes how to integrate a PeopleSoft application in Spaces.

This section contains the following subsections:

54.5.4.1 Registering the PeopeSoft WSRP Producer for Spaces

You can register the PeopleSoft WSRP producer directly in Spaces, as described in the section on "Registering Portlet Producers" in Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces. 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:

  1. Prepare the PeopleSoft page that you want to consume in Spaces for remote access as described in Section 54.5.2, "Preparing the PeopleSoft Application for Remote Access."

  2. Log into Fusion Middleware Control for the Spaces domain.

  3. Expand Spaces in the Navigation bar and from the WebCenter Portal menu, select Register Producer.

    The Add Portlet Producer page displays.

  4. 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.

  5. If required, configure WS-Security in WebCenter Portal as described in Section 54.5.5, "Setting up WS-Security for PeopleTools."

  6. Click OK and verify that the producer connection was created successfully.

  7. Continue by adding the portlet to a Spaces page as described in Section 54.5.4.2, "Adding the PeopleSoft Portlet to a Spaces Page."

54.5.4.2 Adding the PeopleSoft Portlet to a Spaces Page

Follow the steps below to add the PeopleSoft portlet to a Spaces page.

  1. Log into Spaces.

  2. Go to the page, or create a new page, where you want to add the PeopleSoft portal.

  3. Click Add Content to open Composer.

  4. From the Resource Catalog, select Portlets.

    Note that if you've created a custom catalog, Portlets may not appear, in which case you will need to add it to the Resource Catalog. For information about managing Resource Catalogs, see the chapter "Working with Resource Catalogs" in the Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces.

  5. Click the portlet you added in Fusion Middleware Control.

  6. Click Add for the PeopleSoft page you want to add to your Spaces page.

  7. Click Close to close Composer.

  8. On the Spaces page, click the Edit (pencil) icon.

  9. Open the Display Options tab and set the Render Portlet in IFrame option to True and click OK.

  10. Continue by checking the portlet connection as described in Section 54.5.4.3, "Testing the Spaces Portlet Connection."

54.5.4.3 Testing the Spaces Portlet Connection

Use this procedure to test the Spaces portlet connection by modifying content and checking that the modification shows up in the PeopleSoft application.

  1. On the Spaces page that you added the PeopleSoft portlet to, modify some information that you can verify the changes for in the PeopleSoft application.

  2. Save your changes and confirm that the changes also appear in the PeopleSoft application.

54.5.5 Setting up WS-Security for PeopleTools

This section describes the supported OWSM policies for PeopleTools releases. It is important to note that PeopleTools release 8.5.1 (and earlier) does not support outgoing WS-Security headers in its messages. However, some out-of-the-box 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.

Note that:

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

  • For integration scenarios with PeopleTools 8.5.2, only WSS10 SAML Token with Message Integrity or Configuring WS-Security for WSS10 Username Token without Password should be used.

This section includes the following subsections:

54.5.5.1 Configuring 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:

  1. Configure the WebCenter Portal/OWSM keystore as shown in the chapter "Configuring WS-Security" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.

  2. Generate a certificate containing the public key of the WebCenter Portal domain and send it to the PeopleTools administrator so it can be imported in the PeopleTools configuration.

  3. When you register the producer, choose wss10_saml_token_with_message_integrity_client_policy.

  4. Continue by adding the WSRP portlet to a WebCenter Portal page.

54.5.5.2 Configuring 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.5.1 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:

  1. Log into Fusion Middleware Control and navigate to the WebCenter Portal domain (wc_domain by default).

  2. From the WebLogic Domain menu, select Web Services > Policies.

  3. Select the wss10_saml_token_with_message_protection_client_policy and click Create Like.

  4. Give the policy a new name (for example, oracle/wss10_saml_token_with_message_protection_plaintext_response_client_policy).

  5. Open the Response tab, uncheck the Include Entire Body checkboxes under Message Signing Setting and Message Encrypt Setting , and save the policy.

  6. Check that the public certificate of the PeopleSoft keystore is imported into the keystore used in the WebCenter domain.

  7. 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'.

54.5.5.3 Configuring 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.5.1 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:

  1. Log into Fusion Middleware Control and navigate to the WebCenter Portal domain (wc_domain by default).

  2. From the WebLogic Domain menu, select Web Services > Policies.

  3. Select the wss10_username_token_with_message_protection_client_policy and click Create Like.

  4. Give the policy a new name (for example, oracle/wss10_username_token_with_message_protection_plaintext_response_client_policy).

  5. Open the Response tab, uncheck the Include Entire Body checkboxes under Message Signing Setting and Message Encrypt Setting , and save the policy.

  6. Check that the public certificate of the PeopleSoft keystore is imported into the keystore used in the WebCenter domain.

  7. 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'.

54.5.5.4 Configuring WS-Security for WSS10 Username Token Without Password

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

This section describes how to configure WS-Security for the WSS10 Username Token without Password (oracle/wss10_username_id_propagation_with_msg_protection_client_policy) policy for PeopleTools release 8.5.2:

  1. Configure the WebCenter Portal/OWSM keystore as described in the chapter on "Configuring WS-Security" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.

  2. Generate a certificate containing the public key of the WebCenter Portal domain and send it to the PeopleTools administrator so it can be imported in the PeopleTools configuration.

  3. Check that the public certificate of the PeopleSoft keystore is imported into the keystore used in the WebCenter domain. Use the alias for the imported peoplesft public key as the value for the recptAlias parameter when you register the PeopleSoft WSRP producer.

  4. When you register the producer, choose wss10_username_id_propagation_with_msg_protection_client_policy.

  5. Continue by adding the WSRP portlet to a WebCenter Portal page.

54.6 Integrating Oracle Business Intelligence Presentation Services

This section explains how to use JDeveloper to create and configure a WebCenter Portal application that integrates with the Oracle Business Intelligence Presentation Services catalog. At runtime, users can add business intelligence objects to their Framework application or Spaces pages.

This section includes the following subsections:

54.6.1 Introduction to Integrating Oracle Business Intelligence Presentation Services

This section explains how you use JDeveloper to create a Framework application, or configure Spaces to integrate with the Oracle Business Intelligence Presentation Services catalog. For more information about adding Oracle Business Intelligence objects to Framework applications, see "Embedding Business Intelligence Objects in ADF Applications" in the Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition.

This section includes the following subsections:

54.6.1.1 Understanding Oracle Business Intelligence Presentation Services Integration

You can use JDeveloper to create Framework applications that integrate with Oracle Business Intelligence Presentation Services. At runtime, these applications include the Presentation Services catalog in the WebCenter Portal - Resource catalog. Users can then browse for and add business intelligence analyses, dashboard pages, dashboards, or scorecard components (strategy maps, strategy trees, KPI watchlists, cause and effect maps, and custom views) to their Framework application pages. Any filters, prompts, and actions links included in the Business Intelligence objects will work within the Framework application or Spaces pages.

At runtime, 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). Users cannot include entire Scorecards (only a Scorecard's components) in their Framework application pages.

54.6.1.2 Requirements for Integrating Oracle Business Intelligence Presentation Services

To create a Framework application that integrates with Oracle Business Intelligence Presentation Services, you must have installed Oracle JDeveloper 11g Release 1 (11.1.1.6) or later and the required Oracle BI EE and WebCenter Portal extensions.

To properly create the Framework application, you must configure the library settings, update the weblogic.xml and weblogic-application.xml files, and have properly configured security.

For both Framework applications and Spaces, 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 the 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 Section 54.6.2, "Configuring Credentials for Connecting to the Oracle BI Presentation Catalog."

54.6.2 Configuring 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:

54.6.2.1 Creating 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 impersonate 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 role to each user in this realm. For more information, see "How to Create and Use Impersonate User" in the Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition.

Follow the steps below to create the BIImpersonateUser user:

  1. Open WebLogic Server for your Oracle BI EE instance.

  2. Locate the Domain Structure pane and select Security Realm.

    The Realms pane displays.

  3. In the Realms pane, select <myrealm>.

    The Settings dialog displays.

  4. In the Settings dialog, open the Users and Groups tab.

  5. Confirm that the Users tab is displaying and click New.

  6. Enter BIImpersonateUser for the user name and enter a password.

  7. Click OK.

54.6.2.2 Granting Permissions to BIImpersonateUser

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

  1. Open Fusion Middleware Control for your Oracle BI EE instance.

  2. Locate and select bifoundation_domain.

    The bifoundation_domain pane displays.

  3. In the bifoundation_domain pane, click the WebLogic Domain list, highlight Security, and select Application Policies.

    The Search pane displays.

  4. In the Select Application Name to Search field's list, select obi.

  5. Click Create.

    The Add Permission dialog displays.

  6. In the Permission Class field, select oracle.security.jps.ResourcePermission. In the Resource Name field, select oracle.bi.server.impersonateUser.

  7. Click OK.

  8. In the Grantees pane, click Add User.

    The Add User dialog displays.

  9. In the Available Users list, select BIImpersonateUser and click Move to move it to the Selected Users list.

  10. Click OK.

  11. In the bifoundation_domain pane, click OK.

  12. 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

54.6.3 Integrating Oracle Business Intelligence Presentation Services in Framework Applications

This section describes how to install the required BI extensions, and create or modify a Framework application that integrates with Oracle Business Intelligence Presentation Services.

This section includes the following subsections:

54.6.3.1 Installing the Required Business Intelligence Extensions

Use this procedure to install the required Business Intelligence extensions:

  1. From the JDeveloper Help menu, select Check for Updates.

  2. Follow the steps in the wizard to locate, download, and install the Oracle BI EE extensions. Be sure to install the bundles in the following order:

    • bi-soap-cn_bundle

    • bi-vo_bundle

    • bi-adf_bundle

    • bi-adf-taskflow-extension_bundle

  3. Also use the wizard to download and install the Oracle Webcenter Framework Extension bundle (oracle.webcenter.framework_bundle.zip).

54.6.3.2 Creating a Framework Application that Integrates with Oracle BI Presentation Services

Use the following procedures to create or modify a Framework application that can access the Oracle Business Intelligence Presentation Services catalog at runtime. Before following these steps you should already have created the BIImpersonateUser, as described in Section 54.6.2, "Configuring Credentials for Connecting to the Oracle BI Presentation Catalog."

This section includes the following subsections:

54.6.3.2.1 Creating the Framework Application and JSF Page

Use the following procedure to create a Framework application and add a JSF page.

To create a Framework application and JSF page:

  1. In Oracle JDeveloper, create a new WebCenter Portal - Framework application (be sure to check the checkbox for Configure the Application with Standard Portal Features).

    The user name/password in this case should be BIImpersonateUser/<password>, where <password> is the password that you set when you created the user.

  2. Create a connection to the BI application as described in the section "How to Configure SSL and Create an Oracle BI EE Presentation Services Connection" in the Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition.

    When you create the connection, be sure to set Perform impersonation when security is enabled the to true and change the username and password to the Impersonate User credentials (BIImpersonateUser/<password>) as described above.

  3. In the Navigation panel, right-click on the Portal project and select New.

    The New Gallery dialog displays.

  4. In the Categories field's tree structure, locate and expand the Web Tier.

    A list with the descriptions of the available options display in the Items field.

  5. From this list, select JSF Page and click OK.

    The Create JSF Page dialog displays.

  6. Create the JSF page, making sure that the Create an XML Document (*.jspx) field is selected. For more information about setting up the JSF page, click the Help button to access the online help.

  7. Click OK.

    The newly created JSPX page displays.

  8. In the Component Palette pane, select Composer.

    The field updates to display the corresponding components, layouts, and operations.

  9. From the Common Components category, select Change Mode Link and drag and drop it onto your page.

  10. From the Common Components category, select Page Customizable.

  11. Save the application.

  12. Right-click the page in Design view and choose Edit Authorization.

  13. Navigate to Granted to > Select authenticated-users and under Actions grant authenticated users Customize, Grant, Personalize, and View privileges.

54.6.3.2.2 Configuring the Application to Display the Oracle BI EE Presentation Catalog

Use this procedure to add the Presentation Catalog to the Framework application's folder list. At runtime, the catalog displays in the WebCenter Portal - Resource Catalog where the users can browse to business intelligence objects and add them to their Framework application page.

To display the Presentation Catalog in the Framework application's folder list:

  1. In the Framework application that you created with Oracle JDeveloper, from the Application menu, right-click Portal Project and select Project Properties.

    The Project Properties dialog displays.

  2. In the available properties pane, select Technology Scope and from the Available field, select Business Intelligence ADF View Components, and click the Add (>) icon to add it to the project's technology scope. Note that you can also add the BI technology libraries when you create a new application.

  3. In the available properties pane, select Libraries and Classpath, and click Add Library.

    The Add Library dialog displays.

  4. Add the following libraries to the project, and click OK.

    • BI ADF Runtime

    • BI ADF Taskflow

    • BI SOAP Connection Runtime

    • BI View Object Runtime

  5. Save the application.

  6. In JDeveloper, open the default resource catalog file (default-catalog.xml) located in Portal > Web Content > Oracle > webcenter > portalapp > catalogs.

  7. Add the following <customFolder> entry under the <catalogDefinition> - ><contents> folder:

    <customFolder id="oracleBIContent"
        name="Oracle BI"
        description="Oracle BI Presentation Services Content"
        factoryClass="oracle.bi.presentation.rescat.
          BICatalogInitialContextFactory"/>
    
  8. Edit Weblogic.xml and add references to oracle.bi.adf.view.slib and oracle.bi.adf.webcenter.slib as shown below:

    <library-ref>
          <library-name>oracle.bi.adf.view.slib</library-name>
       </library-ref>
       <library-ref>
          <library-name>oracle.bi.adf.webcenter.slib</library-name>
       </library-ref>
    </weblogic-web-app>
    
  9. Edit weblogic-application.xml and add a reference to oracle.bi.adf.model.slib as shown below:

       library-ref>
         <library-name>oracle.bi.adf.model.slib</library-name>
       </library-ref>
    </weblogic-application>
    
54.6.3.2.3 Enabling the BI ADF Task Flow Permission

Use the following procedure to enable the BI ADF task flow permissions in your application's security settings.

To enable the BI ADF task flow permissions:

  1. Open the jazn-data.xml file from Application Resources Pane > META-INF > jazn-data.xml.

  2. Locate the following code in the file:

    <grantee>
        <principals>
            <principal>
                <class>
                  oracle.security.jps.internal.core.principals.JpsAnonymousRoleImpl
                 </class>
                <name>anonymous-role</name>
            </principal>
        </principals>
    </grantee>
    
  3. Add the following element:

    <permission>
        <class>oracle.adf.controller.security.TaskFlowPermission</class>
        <name>/WEB-INF/oracle/bi/presentation/taskflow/
    
         task-flow-definition.xml#task-flow-definition</name>
        <actions>customize,personalize,view</actions>
    </permission>
    

    For example:

    <grant>
       <grantee>
          <principals>
             <principal>
                <class>oracle.security.jps.internal.core.principals
    
                .JpsAnonymousRoleImpl</class>
                <name>anonymous-role</name>
             </principal>
          </principals>
       </grantee>
    <permissions>
       <permission>
           <class>oracle.adf.controller.security.TaskFlowPermission</class>
           <name>/WEB-INF/oracle/bi/presentation/taskflow/
    
            task-flow-definition.xml#task-flow-definition</name>
           <actions>customize,personalize,view</actions>
       </permission>
    

54.6.3.3 Testing the Framework Application

This section describes how to test the Framework application by performing the following procedures:

  • Adding Oracle BI Presentation Services catalog content and modifying a report or dashboard's prompt values

  • Confirming and modifying a business intelligence object's initialization parameters.

This section includes the following subsections:

54.6.3.3.1 Adding Oracle BI Objects to the Resource Catalog

Before you can add Oracle BI content to a Framework application page, you must add objects stored in the Oracle BI Presentation Catalog to the WebCenter Portal - Resource Catalog.

  1. Run the application in a browser.

  2. Log into the Framework application as an administrator.

  3. Click Administration.

    The WebCenter Portal Administration Console displays.

  4. Open the Resources tab.

  5. Click Resources Catalogs.

  6. Click Create a Resource Catalog.

  7. In the Name field, enter the name of the catalog you are creating. Complete the other fields on this dialog, as necessary.

  8. Click Edit > Show for the resource catalog.

  9. Click the Edit menu and then choose Edit.

  10. From the Add menu, choose Add From Library....

  11. Double-click Connections.

    The BI Presentation Services folder displays in the right frame. Open this folder to display the Oracle BI objects.

  12. Browse to and select the objects that you want to add.

  13. Click Add to add the selected objects to the catalog.

  14. Open the Configuration tab and select the resource catalog you just created as the Default Resource Catalog.

54.6.3.3.2 Adding Business Intelligence Content at Runtime

Use this procedure to test the Framework application by adding business intelligence content to the Framework application.

  1. Run the .jspx page that you created.

  2. In the running page, click the Edit link to enter the edit mode.

  3. Click Add Content.

    The WebCenter Portal - Resource Catalog displays.

  4. Browse to and open the Oracle BI folder.

  5. Click the BI connection or host machine to which you want to connect.

    The contents of the catalog display.

  6. Browse to and click the Add link for the object that you want to add to the .jspx page.

  7. Confirm that the application correctly added the object.

54.6.3.3.3 Modifying a Business Intelligence Object's Prompt Values

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

  1. Run the .jspx page that you created.

  2. In the running page, click the Edit link to enter the edit mode.

  3. Add an analysis or dashboard that contains a filter or prompt.

    For more information about adding business intelligence content to the .jspx page, see Section 54.6.3.3.2, "Adding Business Intelligence Content at Runtime."

  4. Click Parameters.

    The Editing Page dialog displays.

  5. Modify the values and click Save.

  6. Confirm that the application correctly applied the modified prompt values.

54.6.3.3.4 Modifying a Business Intelligence Task Flow's Initialization Parameters

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

  1. Run the .jspx page that you created.

  2. In the running page, click the Edit link to enter the edit mode.

  3. Add a business intelligence object.

    For more information about adding business intelligence content to the .jspx page, see Section 54.6.3.3.2, "Adding Business Intelligence Content at Runtime."

  4. Locate the business intelligence object and click the Edit (wrench) icon.

    The Component Properties dialog displays.

  5. Open the Parameters tab, modify the object's parameters, and click OK.

  6. Confirm that the application correctly applied the modified prompt values.

54.6.3.4 Post-Deployment Connection Configuration

After an application has been deployed, use Fusion Middleware Control to add a new Oracle BI EE Presentation Services connection to the application, or modify the application's existing Oracle BI EE Presentation Services connection with the user name and password for BIImpersonateUser.

For more information about modifying these connections, see "Adding or Modifying a Presentation Services Connection After Deployment" in the Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition.

Note:

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

54.6.3.5 Securing Oracle BI EE Objects Included in a Framework Application

Impersonate User lets you secure a Framework application that integrates with Oracle BI EE Presentation Services. For more information about Impersonate User and how to implement it to secure your application, see "How to Create and Use Impersonate User" in the Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition.

54.6.4 Integrating Oracle Business Intelligence Objects in WebCenter Portal: Spaces

Use the following procedures to test the WebCenter Portal: Spaces integration with the BI objects.

54.6.4.1 Adding or Modifying a Presentation Services Connection After Deployment

Before you can begin integrating BI objects in Spaces, you must first configure a connection from Spaces to the BI server. Oracle BI EE provides an ADF MBean that allows you to add a new connection to a deployed BI ADF or WebCenter Portal: Spaces 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 Section 54.6.2, "Configuring Credentials for Connecting to the Oracle BI Presentation Catalog" to specify credentials to connect to the Oracle BI Presentation Catalog.

Note:

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

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

  1. Open Fusion Middleware Control and select your WebLogic domain by doing one of the following:

    • If your application is deployed in the BI ADF domain, select the Application Deployments <your domain> tree node.

    • If your application is deployed in the Spaces domain, select the WebCenter tree node, and then the Spaces tree node, and then the webcenter(11.1.1.4.0) (WC_Spaces) tree node. Note that the WC_Spaces server must be running in order to perform this step.

  2. From the list, select System MBean Browser.

    The System MBean Browser pane displays.

  3. 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 Server:WC_Spaces.

    4. Select the Application:<your application's name> tree node.

      For example, Application:Application2 or Application: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.

  4. In the Application Defined MBean pane, open the Operations tab and then click createConnection/findOrCreateConnection to create a Presentation Services connection.

    The Operation:createConnection dialog displays.

  5. Specify the required values for the connection.

    In the connection type Value field, enter BISoapConnection, enter a name in the connection name Value field and click Invoke to create the connection.

  6. In the System MBean Browser pane, click Refresh to refresh the tree so that the new connection displays.

  7. To modify the connection, locate it in the System MBean Browser pane and click it.

    The connection's information displays in the Application Defined MBean pane.

  8. Navigate to ADF Connections from the System MBean Browser pane and open the Attributes tab.

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

    • From the OBIEE URLto the login page you need:

      context = analytics
      host = <host name>
      port = 7001 or the local value
      protocol = HTTP
      
    • From BIImpersonateUser you need:

      username = BIImpersonateUser
      password = <password>
      
  10. Click on the ADFConnections folder in the Navigation pane, open the Operations tab, and then click Save to save the connection.

  11. When you click Invoke, you should get the following message "Confirmation Operation executed successfully."

54.6.4.2 Adding Oracle BI Objects to the Spaces Resource Catalog

Before you can add Oracle BI content to a Spaces page, you must add objects stored in the Oracle BI Presentation Catalog to the Spaces Resource Catalog.

  1. Log into Spaces as an administrator.

  2. In Spaces, click Administration.

    The Spaces Administration pages displays.

  3. Open the Resources tab.

  4. Click Resources Catalogs.

  5. Click Create a Resource Catalog.

  6. In the Name field, enter the name of the catalog you are creating. Complete the other fields on this dialog, as necessary.

  7. Make the Resource Catalog available by choosing Edit > Show.

  8. From the Edit menu, choose Edit.

  9. Select the Add menu and then choose Add From Library.....

  10. Double-click Connections.

    The BI Presentation Services folder displays.

  11. Open this folder to display the Oracle BI objects and browse to and select the objects that you want to add.

  12. Click Add to add the selected objects to the catalog.

    Continue by adding the object to a space or Framework application. For more information about managing Resource Catalogs at runtime, see "Working with Resource Catalogs" in Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces. For information about managing Resource Catalogs in JDeveloper, see Chapter 15, "Creating and Managing Resource Catalogs."

54.6.4.3 Adding Oracle BI Content at Runtime

Use this procedure to create a WebCenter Portal: Spaces page and add Oracle BI objects to it. Before you perform this procedure, you must have added Oracle BI objects to the WebCenter Portal: Spaces resource catalog.

  1. Log into Spaces and create a new space or access an existing space.

  2. Make the Resource Catalog the default catalog for the space.

    1. Navigate to Space Settings > General and select the catalog created in Section 54.6.4.2, "Adding Oracle BI Objects to the Spaces Resource Catalog" as the default catalog for Resource Catalog for Pages.

    2. Click Apply.

    3. Click Back to Space.

  3. Create a new page.

  4. In the page, click Add Content.

  5. Browse to the folder containing the Oracle BI objects.

  6. Select an analysis or dashboard and click Add.

    The object that you selected is added to the page.

  7. Click Close to exit the Add Content dialog.

54.6.4.4 Modifying a Business Intelligence Object's Prompt Values

Use this procedure to test the WebCenter Portal: Spaces page by changing an analysis or dashboard's filter or prompt values.

  1. Open the page that you created.

  2. In the running page, click Page Actions and then click the Edit link to enter edit mode.

  3. Add an analysis or dashboard that contains a filter or prompt. For more information about adding Oracle BI objects to the page, see Section 54.6.4.3, "Adding Oracle BI Content at Runtime."

  4. Without exiting the edit mode of the page, save the Spaces page.

  5. In the Spaces page, modify the prompt values and click OK.

  6. Exit edit mode, save the page and confirm that the application correctly applied the prompt values.

54.6.4.5 Modifying a Business Intelligence Task Flow's Initialization Parameters

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

  1. Open the page that you created.

  2. In the running page, click Page Actions and then click the Edit link to enter the edit mode.

  3. 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 Section 54.6.4.3, "Adding Oracle BI Content at Runtime."

  4. Without exiting the edit mode for the page, save the Spaces page.

  5. Locate the business intelligence object and click the Edit (wrench) icon.

    The Component Properties dialog displays.

  6. On the Spaces page, open the Parameters tab and modify the object's parameters and click OK.

  7. Open the Parameters tab, modify the object's parameters, and click OK.

  8. Exit edit mode, save the page and confirm that the application correctly applied the modified parameter values.