| Oracle® Fusion Middleware Developer's Guide for Oracle WebCenter 11g Release 1 (11.1.1) Part Number E10148-09 |
|
|
View PDF |
| Oracle® Fusion Middleware Developer's Guide for Oracle WebCenter 11g Release 1 (11.1.1) Part Number E10148-09 |
|
|
View PDF |
This chapter describes how you can integrate other Oracle applications with your WebCenter Portal application.
This chapter contains the following sections:
This section describes how to integrate a Siebel Web service in a WebCenter Portal application. It also describes how to integrate Siebel objects using the Siebel Web Engine (SWE).
This section contains the following subsections:
Section 52.1.1, "Integrating Siebel Applications as Web Services"
Section 52.1.2, "Integrating Siebel Applications Using the Siebel Web Engine"
This section describes how to integrate Siebel applications as Web services in a WebCenter Portal application.
This section contains the following subsections:
This section describes how to create an inbound Web service, set up operations for the inbound service, and generate a WSDL.
This section contains the following subsections:
To create an inbound Web service:
Log into the Siebel application.
Navigate to the Administration - Web Services page.
Click Inbound Web Services.
The Inbound WebServices 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:
Namespace: http://siebel.com.fmw
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.
In the Address field, set the URL to your Siebel instance. For example:
http://example.com/eai_enu/start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&UserName=SADMIN&Password=SADMIN
From the Menu drop-down list, select Save Record.
To add operations to the inbound Web service and then create a WSDL file, perform the following 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 relogin 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.
This section describes how to consume Siebel applications that have been set up as Web services in a WebCenter Portal 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:
Section 52.1.1.2.1, "Creating a Data Control Based on a Siebel Web Service"
Section 52.1.1.2.3, "Adding Pages and Navigation to the Page Flow Diagram"
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:
Open your WebCenter Portal application or create a new WebCenter Portal application in JDeveloper.
In the Applications Navigator, right-click the Model node and select New from the context menu.
In the New Gallery, select All Technologies from the Filter By drop-down list.
Select Business Tier | Web Services as the category, select the Web Service Data Control item, and click OK.
In the Create Web Service Data Control wizard, click Next to leave the Welcome page.
In Step 1, enter the Web service name in the Name field.
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.
Click Next.
Step 2 shows all the operations available from the selected Web service.
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.
Click the Save All icon to save your changes.
-
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:
In the Applications Navigator, right-click the ViewController node and select New from the context menu.
In the New Gallery, expand the Web Tier node and select JSF.
In the Items pane, select JSF Page Flow & Configuration (faces-config.xml) and click OK.
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.
Click the Save All icon to save your changes.
This section describes how to add pages and navigation to the page flow diagram.
To add pages to the page flow diagram:
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.
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).
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.
Modify the default label (success) by clicking it and entering an apporpriate name (for example, toResult).
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 cklicking the Source tab) the <from-view-id> tag identifies the source page, and the <to-view-id> tag identifies the destination page.
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.
Modify the default label by clicking it and entering an appropraite name (for example, toQuery).
Click the Save All icon to save the diagram.
This section describes how to create and set up navigation for the query page.
To create the query page:
On the Page Flow diagram, double-click the source page icon (QueryById) to launch the Create JSF JSP Wizard.
Click Next to leave the Welcome page.
In Step 1 of the wizard, select JSP Document (*.jspx) and click Next.
In Step 2, make sure Do Not Automatically Expose UI Components in a Managed Bean is selected and click Next.
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
Click Finish to create the page.
An empty JSF page opens in the Design tab of the editor.
In the Customizable Components Core component palette, click ShowDetailFrame.
The ShowDetailFrame appears in the page.
Note:
Oracle WebCenter 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.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.
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.
In the popup menu, select Create | Parameters | ADF Parameter Form.
In the Edit Form Fields, click OK.
Select the AccountQueryById button generated in the page and in the Property Inspector pane, change the following properties:
Text Submit Action toResult
Select the input field corresponding to the input value, and in the Property Inspector, change the Label property to Account ID:
Click the Save All icon to save your work.
This section describes how to create and add navigation for the results page.
To create the results page:
Click the faces-config.xml tab to return to the Page Flow diagram and double-click the ShowResult icon to launch the page wizard.
Click Next to skip the Welcome page.
In Step 1 of the wizard, select JSP Document (*.jspx) and click Next.
In Step 2, make sure Do Not Automatically Expose UI Components in a Managed Bean is selected and click Next.
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
Click Finish to create the page.
An empty JSF page opens in the Design tab of the editor.
In the Customizable Components Core component palette, click ShowDetailFrame.
The ShowDetailFrame appears in the page.
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.
In the Data Control palette, expand AccountQueryById | Return | SiebelMessage | ListofAccountInterface, select the Account node and drop it on the page on the ShowDetailFrame.
In the popup menu, select Create | Forms | ADF Read-only Form.
In the Edit Form Fields, delete all fields except for the following:
AccountID AccountStatus NumberOfEmployees CurrencyCode Location MainPhoneNumber Name Type
Check the Include Submit Button checkbox and click OK.
In the Action Binding Editor, click OK.
Click Submit and in the Property Inspector change the title to Back to Query, and in the Action field select toQuery from the list.
Click the Save All icon to save your work.
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:
Log into Siebel Call Center, providing the appropriate user ID and password.
Navigate to the Accounts List using Site Map.
Click Accounts, then Accounts List.
From the returned list, highlight the account you want to query.
From the Help menu, select About Record.
Find the ID value in the Row # field and make a note of it.
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.
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.
As well as integrating Siebel applications using Web Services, you can also integrate Siebel applications in a WebCenter Portal 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 WebCenter Portal application.
For instructions on how to use SWE within a WebCenter Portal 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 "System Requirements and Supported Platforms" guide for Siebel that is available on OTN from http://download.oracle.com/docs/cd/E11886_01/srsphomepage.html)
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.
This section describes how to integrate E-Business Suite applications in WebCenter Portal applications and in WebCenter Spaces.
This section contains the following subsections:
Section 52.2.1, "Introduction to Integrating EBS Applications"
Section 52.2.2, "Integrating EBS Applications in a WebCenter Portal Application"
Section 52.2.3, "Integrating EBS Applications in WebCenter Spaces"
This section describes the integration points and requirements integrating Oracle E-Business Suite portlets in WebCenter Portal applications, and WebCenter Spaces.
This section inlcudes the following subsections:
Out-of-the-box Oracle E-Business Suite OA Framework-based portlets, such as Applications Navigator, Favorites, and Worklist are WSRP/JSR168-compliant. That means that you can access these Oracle E-Business Suite portlets from WSRP-compliant portal servers such as WebCenter Portal applications or WebCenter Spaces, by simply adding the portlet onto an application page. You can also create new E-Business Suite portlets that are WSRP/JSR168-compliant and that can similarly be added to a WebCenter Portal application or WebCenter Spaces.
The following requirements apply for integrating Oracle E-Business Suite portals into WebCenter Portal applications and WebCenter Spaces:
Regions to be exposed as portlets must be created using Oracle E-Business Suite OA Framework Release 12 as previous versions are not WSRP/JSR168-compliant.
Oracle E-Business Suite should be configured to 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 application access to the E-Business Suite Portlet Producer and added and configured the appropriate users.
This section inlcudes the following subsections:
Section 52.2.2.1, "Preparing the EBS Application for Remote Access"
Section 52.2.2.2, "Registering the EBS WSRP Producer in the WebCenter Portal Application"
Section 52.2.2.3, "Creating a JSF Page to Consume the Remote Producer"
Section 52.2.2.4, "Testing the WebCenter Portal Application"
Prepare the standalone regions to be portletized as described the section on "Basic Implementation" under "Portlets" in Chapter 4: "Implementing Specific UI Features" in the Oracle Application Framework Developer's Guide, available from My Oracle Support at:
https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1107973.1
The Oracle E-Business Suite OA Framework lets you expose any standalone regions (except pageLayout regions) as portlets.
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, see the section on "Portlet Generator" in Chapter 4: "Developer Tools" in the Oracle Application Framework Developer's Guide.
After creating the portlets, grant access to your new UI Function by adding it to a menu and associating the menu with a responsibility. For more information, see the section on "Page Security" under "Portlets" in Chapter 4: "Implementing Specific UI Features" in the Oracle Application Framework Developer's Guide.
Before adding the portlets in WebCenter, be sure to bounce the Apache listener as the menu and function definitions are cached.
Follow the instructions below to create or open an existing WebCenter Portal application, and register the EBS WSRP producer.
Create a new WebCenter Portal application or open an existing one in which you would like to consume the remote (WSRP) EBS portlet.
Under Application Resources, right-click Connection and select WSRP Producer.
Page 1 (Specify Producer Name) of the Register WSRP Portlet Producer wizard displays.
Enter a name for the WSRP producer and click Next.
The Specify Connection Details page displays.
Paste the WSDL for the EBS producer into the WSDL URL field.
Click Next and then Finish.
The WSRP producer should now appear under Connections.
Continue by creating a JSF page to consume the WSRP producer as described in Section 52.2.2.3, "Creating a JSF Page to Consume the Remote Producer."
Use the following procedure to add or use an exising JSF page to consume the EBS remote producer in your WebCenter Portal application.
To create a JSF page:
In the application's Navigation panel, right-click on the application name and select New.
The New Gallery dialog displays.
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.
From this list, select JSF Page and click OK.
The Create JSF Page dialog displays.
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.
Click OK.
The newly created JSF page displays.
Under connections, expand the newly created WSRP producer and drag the portlet for the EBS page onto the JSF page.
In the Portlet Property Inspector, set the RenderPortletInIFrame property to True.
Add any other components that you need onto the page, and save the application.
Continue by running the page and testing that modifications made in the WebCenter application appear in the EBS application as described in Section 52.2.2.4, "Testing the WebCenter Portal Application."
Use this procedure to test the WebCenter application by modifying content on the JSF page in the WebCenter Portal application and checking that the modification shows up in the EBS application.
Run the .jspx page that you created.
In the running page, 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.
This section contains the following subsections:
Section 52.2.3.1, "Preparing the EBS Portlet for Remote Access"
Section 52.2.3.2, "Registering the EBS WSRP Producer in WebCenter Spaces"
Section 52.2.3.3, "Adding the EBS Portlet to a WebCenter Spaces Page"
Section 52.2.3.4, "Testing the WebCenter Spaces Portlet Connection"
Prepare the standalone regions to be portletized as described the section on "Basic Implementation" under "Portlets" in Chapter 4: "Implementing Specific UI Features" in the Oracle Application Framework Developer's Guide, available from My Oracle Support at:
https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1107973.1
The Oracle E-Business Suite OA Framework lets you expose any standalone regions (except pageLayout regions) as portlets.
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, see the section on "Portlet Generator" in Chapter 4: "Developer Tools" in the Oracle Application Framework Developer's Guide.
After creating the portlets, grant access to your new UI Function by adding it to a menu and associating the menu with a responsibility. For more information, see the section on "Page Security" under "Portlets" in Chapter 4: "Implementing Specific UI Features" in the Oracle Application Framework Developer's Guide.
Before adding the portlets in WebCenter, be sure to bounce the Apache listener as the menu and function definitions are cached.
You can register the EBS WSRP producer directly in WebCenter Spaces, as described in the section on "Registering Portlet Producers" in Oracle Fusion Middleware User's Guide for Oracle WebCenter 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:
Prepare the EBS page that you want to consume in WebCenter spaces for remote access as described in Section 52.2.3.1, "Preparing the EBS Portlet for Remote Access."
Log into Fusion Middleware Control for the WebCenter Spaces domain.
Expand WebCenter Spaces in the Navigation bar and from the WebCenter menu, 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 WebCenter Spaces page as described in Section 52.2.3.3, "Adding the EBS Portlet to a WebCenter Spaces Page."
Use the following procedure to consume the EBS remote producer in WebCenter Spaces.
Log into WebCenter Spaces.
Go to the page, or create a new page, where you want to add the EBS portal.
Click Add Content to open Composer.
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 Spaces.
Click the portlet you added in Fusion Middleware Control.
Click Add for the EBS portlet you want to add to your WebCenter Spaces page.
Click Close to close Composer.
On the WebCenter Spaces page, click the Edit (pencil) icon.
Open the Display Options tab and set the Render Portlet in IFrame option to True and click OK.
Continue by checking the portlet connection as described in Section 52.2.3.4, "Testing the WebCenter Spaces Portlet Connection."
Use this procedure to test the WebCenter Spaces portlet connection by modifying content and checking that the modification shows up in the EBS application.
On the WebCenter Spaces page that you added the EBS portlet to, 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.
This section describes how to integrate JD Edwards applications into WebCenter Portal applications and WebCenter Spaces.
This section contains the following subsections:
Section 52.3.1, "Integrating JD Edwards Applications in a WebCenter Portal Application"
Section 52.3.2, "Integrating JD Edwards Applications in WebCenter Spaces"
This section inlcudes the following subsections:
Section 52.3.1.1, "Preparing the JD Edwards Application for Remote Access"
Section 52.3.1.2, "Registering the JD Edwards WSRP Producer in the WebCenter Portal Application"
Section 52.3.1.3, "Creating the JSF Page to Consume the Remote Porducer"
Section 52.3.1.4, "Testing the WebCenter Portal Application"
Prepare the standalone regions to be portletized by making them available externally, as portlets and then generating a WSDL.
Follow the instructions below to create or open an existing WebCenter Portal application, and register the JD Edwards WSRP producer.
Create a new WebCenter Portal application or open an existing one in which you would like to consume the remote (WSRP) JD Edwards portlet.
Under Application Resources, right-click Connection and select WSRP Producer.
Page 1 (Specify Producer Name) of the Register WSRP Portlet Producer wizard displays.
Enter a name for the WSRP producer and click Next.
The Specify Connection Details page displays.
Paste the WSDL for the JD Edwards producer into the WSDL URL field.
Click Next and then Finish.
The WSRP producer should now appear under Connections.
Continue by creating a JSF page to consume the WSRP producer as described in Section 52.3.1.3, "Creating the JSF Page to Consume the Remote Porducer."
Use the following procedure to add or use an exising JSF page to consume the JD Edwards remote producer in your WebCenter Portal application.
To create a JSF page:
In the application's Navigation panel, right-click on the application name and select New.
The New Gallery dialog displays.
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.
From this list, select JSF Page and click OK.
The Create JSF Page dialog displays.
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.
Click OK.
The newly created JSF page displays.
Under connections, expand the newly created WSRP producer and drag the portlet for the JD Edwards page onto the JSF page.
In the Portlet Property Inspector, set the RenderPortletInIFrame property to True.
Add any other components that you need onto the page, and save the application.
Continue by running the page and testing that modifications made in the WebCenter application appear in the JD Edwards application as described in Section 52.3.1.4, "Testing the WebCenter Portal Application."
Use this procedure to test the WebCenter Portal application by modifying content on the JSF page in the WebCenter Portal application and checking that the modification shows up in the JD Edwards application.
Run the .jspx page that you created.
In the running page, 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.
This section contains the following subsections:
Section 52.3.2.2, "Adding the JD Edwards Portlet to a WebCenter Spaces Page"
Section 52.3.2.3, "Testing the WebCenter Spaces Portlet Connection"
You can register the JD Edwards WSRP producer directly in WebCenter Spaces, as described in the section on "Registering Portlet Producers" in Oracle Fusion Middleware User's Guide for Oracle WebCenter 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:
Prepare the JD Edwards page that you want to consume in WebCenter Spaces for remote access as described in Section 52.3.1.1, "Preparing the JD Edwards Application for Remote Access."
Log into Fusion Middleware Control for the WebCenter Spaces domain.
Expand WebCenter Spaces in the Navigation bar and from the WebCenter menu, 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 WebCenter Spaces page as described in Section 52.3.2.2, "Adding the JD Edwards Portlet to a WebCenter Spaces Page."
Use the following procedure to consume the JD Edwards remote producer in WebCenter Spaces.
Log into WebCenter Spaces.
Go to the page, or create a new page, where you want to add the JD Edwards portal.
Click Add Content to open Composer.
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 Spaces.
Click the portlet you added in Fusion Middleware Control.
Click Add for the EBS portlet you want to add to your WebCenter Spaces page.
Click Close to close Composer.
On the WebCenter Spaces page, click the Edit (pencil) icon.
Open the Display Options tab and set the Render Portlet in IFrame option to True and click OK.
Continue by checking the portlet connection as described in Section 52.3.2.3, "Testing the WebCenter Spaces Portlet Connection."
Use this procedure to test the WebCenter Spaces portlet connection by modifying content and checking that the modification shows up in the JD Edwards application.
On the WebCenter 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.
Save your changes and confirm that the changes also appear in the JD Edwards application.
This section describes how to integrate PeopleSoft applications in a WebCenter Portal application and in WebCenter Spaces.
This section contains the following subsections:
Section 52.4.1, "Integrating PeopleSoft Applications in a WebCenter Portal Application"
Section 52.4.2, "Integrating PeopleSoft Applications in WebCenter Spaces"
This section describes how to create or modify a WebCenter Portal application that integrates with PeopleSoft Applications.
This section includes the following subsections:
Section 52.4.1.1, "Preparing the PeopleSoft Application for Remote Access"
Section 52.4.1.2, "Registering the PeopleSoft WSRP Producer in the WebCenter Portal Application"
Section 52.4.1.3, "Creating the JSF Page to Consume the Remote (WSRP) Producer"
Section 52.4.1.4, "Testing the WebCenter Portal Application"
This section describes how to prepare the PeopleSoft application so that it can be consumed by a WebCenter Portal application or WebCenter Spaces.
To prepare the PeopleSoft application:
Log into PeopleSoft as an administrator.
Select PeopleTools from the main menu.
From the People Tools main menu, expand Employee Self-Service, and then Portal.
Select Structure and Content.
Navigate to the folder containing the page that you want to consume in WebCenter and click Edit to open it.
The Content Ref Administration page displays.
On the General tab, select the WSRP Producible checkbox.
Save the page.
From the main menu, select WSRP Production.
The Producer Offered Portlets page displays.
Verify that the page 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 creating or modifying a WebCenter Portal application that can access the PeopleSoft remote (WSRP) producer as described in Section 52.4.1.2, "Registering the PeopleSoft WSRP Producer in the WebCenter Portal Application."
Follow the instructions below to create or open an existing WebCenter Portal application, and register the PeopleSoft WSRP producer.
Create a new WebCenter Portal application or open an existing one in which you would like to consume the remote (WSRP) PeopleSoft portlet.
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 52-1).
Enter a name for the WSRP producer and click Next.
The Specify Connection Details page displays (see Figure 52-2).
Paste the WSDL (the URL you copied earlier) into the WSDL URL field.
Click Next and then Finish.
The WSRP producer should now appear under Connections.
Continue by creating a JSF page to consume the WSRP producer as described in Section 52.4.1.3, "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:
In the application's Navigation panel, right-click on the application name and select New.
The New Gallery dialog displays.
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.
From this list, select JSF Page and click OK.
The Create JSF Page dialog displays.
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.
Click OK.
The newly created JSF page displays.
Under connections, expand the newly created WSRP producer and drag the portlet for the PeopleSoft page onto the JSF page.
In the Portlet Property Inspector, set the RenderPortletInIFrame property to True.
Add any other components that you need onto the page, and save the application.
Continue by running the page and testing that modifications made in the WebCenter application appear in the PeopleSoft application as described in Section 52.4.1.4, "Testing the WebCenter Portal Application."
Use this procedure to test the WebCenter application by modifying content on the JSF page in the WebCenter Portal application and checking that the modification shows up in the PeopleSoft application.
Run the .jspx page that you created.
In the running page, 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.
This section describes how to integrate a PeopleSoft application in WebCenter Spaces.
This section contains the following subsections:
Section 52.4.2.2, "Adding the PeopleSoft Portlet to a WebCenter Spaces Page"
Section 52.4.2.3, "Testing the WebCenter Spaces Portlet Connection"
You can register the PeopleSoft WSRP producer directly in WebCenter Spaces, as described in the section on "Registering Portlet Producers" in Oracle Fusion Middleware User's Guide for Oracle WebCenter 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:
Prepare the PeopleSoft page that you want to consume in WebCenter spaces for remote access as described in Section 52.4.1.1, "Preparing the PeopleSoft Application for Remote Access."
Log into Fusion Middleware Control for the WebCenter Spaces domain.
Expand WebCenter Spaces in the Navigation bar and from the WebCenter menu, 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 WebCenter spaces page as described in Section 52.4.2.2, "Adding the PeopleSoft Portlet to a WebCenter Spaces Page."
Follow the steps below to add the PeopleSoft portlet to a WebCenter Spaces page.
Log into WebCenter spaces.
Go to the page, or create a new page, where you want to add the PeopleSoft portal.
Click Add Content to open Composer.
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 Spaces.
Click the portlet you added in Fusion Middleware Control.
Click Add for the PeopleSoft page you want to add to your WebCenter Spaces page.
Click Close to close Composer.
On the WebCenter spaces page, click the Edit (pencil) icon.
Open the Display Options tab and set the Render Portlet in IFrame option to True and click OK.
Continue by checking the portlet connection as described in Section 52.4.2.3, "Testing the WebCenter Spaces Portlet Connection."
Use this procedure to test the WebCenter Spaces portlet connection by modifying content and checking that the modification shows up in the PeopleSoft application.
On the WebCenter Spaces 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.
This section explains how to use JDeveloper to create and configure a WebCenter application that integrates with the Oracle Business Intelligence Presentation Services catalog. At runtime, users can add business intelligence objects to their WebCenter Portal application or webCenter Spaces pages.
This section includes the following subsections:
Section 52.5.1, "Introduction to Integrating Oracle Business Intelligence Presentation Services"
Section 52.5.3, "Integrating Oracle Business Intelligence Objects in WebCenter Spaces"
This section explains how you use JDeveloper to create a WebCenter Portal application, or configure WebCenter Spaces to integrate with the Oracle Business Intelligence Presentation Services catalog. For more information about adding Oracle Business Intelligence objects to WebCenter 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:
Section 52.5.1.1, "Understanding Oracle Business Intelligence Presentation Services Integration"
Section 52.5.1.2, "Requirements for Integrating Oracle Business Intelligence Presentation Services"
You can use JDeveloper to create WebCenter Portal applications that integrate with Oracle Business Intelligence Presentation Services. At runtime, these applications include the Presentation Services catalog in the WebCenter 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 WebCenter Portal application pages. Any filters, prompts, and actions links included in the Business Intelligence objects will work within the WebCenter Portal application or WebCenter Spaces pages.
At runtime, WebCenter 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 WebCenter Portal application pages.
To create a WebCenter Portal application that integrates with Oracle Business Intelligence Presentation Services, you must have installed Oracle JDeveloper 11g Release 1 (11.1.1.4) and the required Oracle BI EE and WebCenter extensions. To properly create the WebCenter application, you must configure the library settings, update the web.xml and default-catalog.xml files, and have properly configured security.
For WebCenter Portal applications and WebCenter Spaces, you must also set up a connection to the BI application as well as configuring security. For more information about configuring security and setting up a connection, see "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.
This section describes how to install the required BI extensions, and create or modify a WebCenter Portal application that integrates with Oracle Business Intelligence Presentation Services.
This section includes the following subsections:
Section 52.5.2.1, "Installing the Required Business Intelligence Extensions"
Section 52.5.2.3, "Testing the WebCenter Portal Application"
Section 52.5.2.4, "Post-Deployment Connection Configuration"
Section 52.5.2.5, "Securing Oracle BI EE Objects Included in a WebCenter Application"
Use this procedure to install the required Business Intelligence extensions:
From the JDeveloper Help menu, select Check for Updates.
Follow the steps in the wizard to locate, download, and install the Oracle BI EE extensions.
Use the following procedures to create or modify an Oracle WebCenter application that can access the Oracle Business Intelligence Presentation Services catalog at runtime.
This section includes the following subsections:
Section 52.5.2.2.1, "Creating the WebCenter Portal Application and JSF Page"
Section 52.5.2.2.2, "Configuring the Application to Display the Oracle BI EE Presentation Catalog"
Section 52.5.2.2.3, "Enabling the BI ADF Task Flow Permission"
Use the following procedure to create a WebCenter application and add a JSF page.
To create a WebCenter Portal application and JSF page:
In Oracle JDeveloper, create a new WebCenter Portal application or open an existing one.
In the Navigation panel, right-click on the application name and select New.
The New Gallery dialog displays.
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.
From this list, select JSF Page and click OK.
The Create JSF Page dialog displays.
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.
Click OK.
The newly created JSPX page displays.
In the Component Palette pane, select Oracle Composer.
The field updates to display the corresponding components, layouts, and operations.
From the Common Components category, select Change Mode Link and drag and drop it onto your page.
From the Common Components category, select Page Customizable.
Save the application.
Use this procedure to add the Presentation Catalog to the WebCenter Portal application's folder list. At runtime, the catalog displays in the WebCenter Resource Catalog where the users can browse to business intelligence objects and add them to their WebCenter Portal application page.
To display the Presentation Catalog in the WebCenter application's folder list:
In the WebCenter application that you created with Oracle JDeveloper, click the Application menu and select Project Properties.
The Project Properties dialog displays.
In the available properties pane, select Technology Scope and from the Available field, select BI ADF 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.
In the available properties pane, select Libraries and Classpath, and click the Add (+) icon.
The Add Library dialog displays.
Add the following libraries to the project, and click OK.
BI ADF
BI ADF Taskflow
BI SOAP Connection Runtime
BI View Object Runtime
Save the application.
Locate and open the following default resource catalog file that was created when you saved the WebCenter Portal application:
<your_application_home>\mds\oracle\adf\rc\metadata\default-catalog.xml
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"/>
In the application's Project pane, locate and open the web.xml file.
Update the file to include the BIRegionServlet definition:
<servlet>
<servlet-name>biregionservlet</servlet-name>
<servlet-class>oracle.bi.presentation.servlet.
BIRegionServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>biregionservlet</servlet-name>
<url-pattern>/BIProxy/*</url-pattern>
</servlet-mapping>
Make sure that the filter mapping of BIRegionFilter displays before the filter-mapping definition. For example:
<filter-mapping>
<filter-name>BIRegionFilter</filter-name>
<servlet-name>Faces Servlet</servlet-name>
<dispatcher>FORWARD</dispatcher>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>adfBindings</filter-name>
<servlet-name>Faces Servlet</servlet-name>
<dispatcher>FORWARD</dispatcher>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
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:
Locate and open the jazn-data.xml file in the following location:
<your_application_root>\src\META-INF\jazn-data.xml
Add the following element to this file:
<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>
This section describes how to test the WebCenter Portal 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:
Section 52.5.2.3.1, "Adding Oracle BI Objects to the Resource Catalog"
Section 52.5.2.3.2, "Adding Business Intelligence Content at Runtime"
Section 52.5.2.3.3, "Modifying a Business Intelligence Object's Prompt Values"
Section 52.5.2.3.4, "Modifying a Business Intelligence Task Flow's Initialization Parameters"
Before you can add Oracle BI content to a WebCenter Portal application page, you must add objects stored in the Oracle BI Presentation Catalog to the WebCenter Resource Catalog.
Run the application in a browser.
Log into the WebCenter Portal application as an administrator.
Click Administration.
The WebCenter Portal Administration Console displays.
Open the Resources tab.
Click Resources Catalogs.
In the Name field, enter the name of the catalog you are creating. Complete the other fields on this dialog, as necessary.
Click the Edit menu and then choose Edit.
From the Add menu, choose Add From Library....
Double-click Connections.
The BI Presentation Services folder displays in the right frame. Open this folder to display the Oracle BI objects.
Browse to and select the objects that you want to add.
Click Add to add the selected objects to the catalog.
Use this procedure to test the WebCenter application by adding business intelligence content to the WebCenter application.
Run the .jspx page that you created.
In the running page, click the Edit link to enter the edit mode.
Click Add Content.
The WebCenter Resource Catalog displays.
Browse to and open the Oracle BI folder.
Click the host machine to which you want to connect.
The contents of the catalog display.
Browse to and click the Add link for the object that you want to add to the .jspx page.
Confirm that the application correctly added the object.
Use this procedure to test the WebCenter application by changing an analysis or dashboard's filter or prompt values.
Run the .jspx page that you created.
In the running page, click the Edit link to enter the edit mode.
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 52.5.2.3.2, "Adding Business Intelligence Content at Runtime."
Click Configure.
The Editing Page dialog displays.
Modify the values and click Save.
Confirm that the application correctly applied the modified prompt values.
Use the following procedure to test the business intelligence task flow's initialization parameters.
Run the .jspx page that you created.
In the running page, click the Edit link to enter the edit mode.
Add a business intelligence object.
For more information about adding business intelligence content to the .jspx page, see Section 52.5.2.3.2, "Adding Business Intelligence Content at Runtime."
Locate the business intelligence object and click Edit.
The Component Properties dialog displays.
Open the Parameters tab, modify the object's parameters, and click OK.
Confirm that the application correctly applied the modified prompt values.
After an application has been deployed, you can use Fusion Middleware Control to add a new Oracle BI EE Presentation Services connection to the application, or to modify the application's existing Oracle BI EE Presentation Services connection.
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.
Impersonate User lets you secure a WebCenter Portal 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.
Use the following procedures to test the WebCenter Spaces integration with the BI objects. Note that before you can begin integrating BI objects in WebCenter Spaces, you must first configure a connection from spaces to the BI server. For information about creating and 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.
Section 52.5.3.1, "Adding Oracle BI Objects to the WebCenter Spaces Resource Catalog"
Section 52.5.3.3, "Modifying a Business Intelligence Object's Prompt Values"
Section 52.5.3.4, "Modifying a Business Intelligence Task Flow's Initialization Parameters"
Before you can add Oracle BI content to a Spaces page, you must add objects stored in the Oracle BI Presentation Catalog to the WebCenter Spaces Resource Catalog.
Log into WebCenter Spaces as an administrator.
In WebCenter Spaces, click Administration.
The WebCenter Spaces Administration pages displays.
Open the Resources tab.
Click Resources Catalogs.
In the Name field, enter the name of the catalog you are creating. Complete the other fields on this dialog, as necessary.
From the Edit menu, choose Edit.
Select the Add menu and then choose 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.
Use this procedure to create a WebCenter Spaces page and add Oracle BI objects to it. Before you perform this procedure, you must have added Oracle BI objects to the WebCenter Spaces resource catalog.
Log into WebCenter Spaces and create a new Space or access an existing Space.
Create a new page.
In the page, click Add Content.
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.
Click Close to exit the Add Content dialog.
Use this procedure to test the WebCenter Spaces 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 Section 52.5.3.2, "Adding Oracle BI Content at Runtime."
Save the WebCenter Spaces page.
In the WebCenter Spaces page, modify the prompt values and click OK.
Confirm that the application correctly applied the prompt values.
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 Section 52.5.3.2, "Adding Oracle BI Content at Runtime."
Save the WebCenter Spaces page.
On the WebCenter Spaces page, open the Parameters tab and modify the object's parameters and click OK.
Confirm that the application correctly applied the modified parameter values.
|
 Copyright © 2007, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|