| Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter Ensemble 10g Release 3 (10.3.0.1.0) E14114-01 |
|
 Previous |
 Next |
| Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter Ensemble 10g Release 3 (10.3.0.1.0) E14114-01 |
|
Previous |
Next |
This chapter describes how to use Oracle WebCenter Ensemble to create and deploy pagelets. It is organized into the following sections:
About Pagelets, describes what pagelets are.
Registering a Pagelet, describes how you register a pagelet with Oracle WebCenter Ensemble.
Using Lightweight Clipping, describes how to form a pagelet by clipping a portion of a larger web page in a proxied application.
Adding Pagelets to Web Pages, describes how to add pagelets to applications that are proxied and not proxied by Oracle WebCenter Ensemble.
Configuring Pagelet Parameters and Transport Type, describes how to pass parameters to your pagelets.
Configuring Metadata Fields, describes how to configure metadata fields to store additional information about a pagelet.
Configuring Pagelet Consumers, describes how to restrict the resources that can use a pagelet.
Accessing Pagelet Discovery for Developers, describes the Oracle WebCenter Ensemble pagelet discovery UI.
Exposing Oracle WebCenter Analytics Pagelets through Oracle WebCenter Ensemble, describes how to import the Oracle WebCenter Analytics resource migration file and add Oracle WebCenter Analytics and Oracle WebCenter Interaction image server files to Oracle WebCenter Ensemble in order to expose Oracle WebCenter Analytics reports as pagelets through Oracle WebCenter Ensemble.
Exposing BEA AquaLogic Pathways Pagelets through Oracle WebCenter Ensemble, describes how to import the BEA AquaLogic Pathways resource migration file in order to expose BEA AquaLogic Pathways pagelets through Oracle WebCenter Ensemble.
A pagelet is a fragment of HTML that describes a self-contained, reusable UI element. With a portal system, a portlet is a self-contained UI element that can be used in the portal. A pagelet is like a portlet that you can easily insert into any web page proxied by Oracle WebCenter Ensemble.
When writing pagelets, developers can make use of the Oracle WebCenter Interaction Development Kit (IDK) proxy API, the client Scripting Framework and Oracle WebCenter Ensemble Adaptive Tags. Pagelets are hosted on a resource and are consumed by other resources via the pagelet Adaptive Tag.
A pagelet is an application hosted on an Oracle WebCenter Ensemble resource. Before registering a pagelet in Oracle WebCenter Ensemble, you must create a resource and configure it to point to the application server where the pagelets are hosted. For details on creating resources, see Chapter 3, "Proxy Resources."
To register a new pagelet:
Launch the Ensemble Console.
Click the APPLICATIONS tab.
Click the Pagelets sub-tab.
To create a new pagelet, click Create new.
On the General page, type the Name of the pagelet.
Select a parent resource. Next to Parent resource, click select. From the Select a resource picker, select the resource your pagelet is hosted on and click OK.
Type the Library name to associate this pagelet with. This can be any text value. The library setting is a user-defined way of grouping pagelets together within the pagelet documentation. This setting is optional.
Type a Description.
By default, a pagelet is included in the generated pagelet documentation. Clear the Publish documentation check box if the pagelet should not be published.
Select the Add inline refresh to all URLs check box if you want Oracle WebCenter Ensemble to automatically perform inline refresh.
Type the Refresh Interval -- in milliseconds -- at which Oracle WebCenter Ensemble refreshes the pagelet.
Click Save.
On the Location page, perform the following:
Type the URL suffix. The Internal URL prefix (taken from the parent resource) appended to the URL suffix forms the URL to the pagelet.
Choose whether the pagelet returns the whole contents of the source, or a clipped region of the source. For details on using clipping, Using Lightweight Clipping.
Metadata can be used to store additional information about a pagelet. For details, see Configuring Metadata Fields.
Once you save the pagelet, sample code for inserting the pagelet into a web page is available on the General page of the pagelet configuration. For details on adding pagelets to web pages, see Adding Pagelets to Web Pages.
Oracle WebCenter Ensemble can restrict the resources that can insert each pagelet into its web pages. For details, see Configuring Pagelet Consumers.
Parameters can be configured to be passed to the pagelet. For details, see Configuring Pagelet Parameters and Transport Type.
This section provides examples for creating a pagelet in Oracle WebCenter Ensemble, and accessing a pagelet via Oracle WebCenter Ensemble.
This procedure provides an example of creating a pagelet in the Ensemble Console.
Click the APPLICATIONS tab.
Click the Resources sub-tab.
Click Create new.
On the General tab, type a name for the resource.
On the Location tab, provide an internal URL prefix and external URL prefix.
For the internal URL prefix, specify the parent URL of the pagelet. For example, if the pagelet is at http://www.foo.org/bar/pagelet1.html, specify http://www.foo.org/bar/ as the Internal URL.
For the external URL prefix, choose the URL that you will use to call the pagelet.
Save the resource.
You just created the pagelet's producer or parent resource.
Click the APPLICATIONS tab.
Click the Pagelets sub-tab.
Click Create new.
On the General tab, type a name for the pagelet.
Select the parent resource that you just created.
Type a library name for the pagelet.
The library is name that groups pagelets together; it does not exist outside of this context. You can create a unique library name for each pagelet, or share one library name across multiple pagelets. The library name serves only as a logical grouping.
Note the Sample code section.
This example will return to this section when using the pagelet; the contents of the Sample code section are automatically generated when saving the pagelet.
Click the Location tab.
The internal URL prefix is automatically populated because it is inherited from the parent resource.
Add the URL suffix that completes the internal URL of the pagelet.
In the above example, the Internal URL prefix is http://www.foo.org/bar/. For the URL suffix, you would add pagelet1.html.
|
Note: Unlike resources, pagelets are actual file names rather than directory names. |
Click Save.
This procedure provides an example of accessing a pagelet via Oracle WebCenter Ensemble.
To access a pagelet via Oracle WebCenter Ensemble:
Create a consumer resource.
This consumer resource will call the pagelet that you created in Example: Creating a Pagelet in the Ensemble Console. Pagelets are not accessed directly; they are accessed in the context of resources that consume the pagelets.
Click the APPLICATIONS tab.
Click the Resources sub-tab.
Click Create new.
On the General tab, type a name for the resource.
On the Connections tab, type an internal URL prefix.
The internal URL prefix should specify the location of the HTML file that you will create. This HTML file will call the pagelet.
Provide an external URL prefix; visiting this URL will access the consumer page. The consumer page will access the pagelet that you created in Example: Creating a Pagelet in the Ensemble Console.
Click Save.
Create the HTML file that will access the pagelet.
Click the Pagelets sub-tab.
Click the name of the pagelet that you created in Example: Creating a Pagelet in the Ensemble Console.
Click the General tab.
Note the Sample code section.
This section contains the HTML that calls the pagelet when the page containing it is proxied through Oracle WebCenter Ensemble. It is automatically generated for each pagelet, and contains the library name and pagelet name.
Create a web page with some content.
This content can be as simple as the following:
<html><head></head><body></body></html>
Copy the sample code that you noted in the previous step, and paste it into the body of the web page.
Declare the XML namespace by entering the following in front of the sample code:
<div xmlns:pt='http://www.plumtree.com/xmlschemas/ptui/'>
After the sample code, type the following:
</div>
Alternatively, you can simply insert the following into the tag specified in the sample code:
xmlns:pt='http://www.plumtree.com/xmlschemas/ptui/
The following is an example HTML file:
<html> <head> </head> <body> <p> This is a pagelet test page. </p><p> <div xmlns:pt='http://www.plumtree.com/xmlschemas/ptui/'> <pt:ensemble.inject pt:name="Pagelet Library:Pagelet One"> </pt:ensemble.inject> </div> </p> </body>
Save the file in the location specified in the consumer resource's internal URL.
|
Note: If you save the file as index.html, you will not need to access it by filename when clicking the external URL. If you do not save this file as index.html, you will need to access it by Internal_URL/filename.html. |
Access the consuming resource's external URL.
Oracle WebCenter Ensemble: 1) retrieves the HTML from the file that was created at the internal URL location, 2) inserts the pagelet into the HTML file, and 3) presents the entire page to the user's browser.
Lightweight clipping allows you to form a pagelet by clipping a portion of a larger web page in a proxied application. For example, in a news web page there is a box listing the latest headlines. By identifying the containing HTML for that box, you can clip only the headlines and serve that subset of the news web page as an Oracle WebCenter Ensemble pagelet.
In addition to clipping a portion of the body of the web page, the pagelet's <head> element can also be included. This allows CSS, JavaScript, or other declarations that occur in the <head> element to be included with the clipped body portion.
To use lightweight clipping:
Click the APPLICATIONS tab.
Click the Pagelets sub-tab.
Open the Pagelet Editor:
To create a new pagelet, click Create New under the pagelets view.
To edit an existing pagelet, navigate to the pagelet you want to edit. Then click the pagelet name.
Click Location.
Choose from one of the following choices for lightweight clipping:
Select Clip nothing and all content will be returned with this pagelet.
Select Clip a region using Intelligent Matcher and choose the section to be clipped. Next, click Select Intelligent Matcher Clip Region. In the pop-up display, use the mouse to move the red box. Then click when selection you want clipped is outlined. To include the <head> element from the pagelet, select Also include contents of pagelet's <head> tag.
Select Clip a region using tag attributes and specify HTML tag attributes that describe the section to be clipped. Next, type the name of the tag in the Tag type box. For example, div. Then, type an attribute name and value in the Attribute Name and Attribute Value boxes. If more attributes are required, click Add. Alternately, click Select Clip Region and choose the section to be clipped. To include the <head> element from the pagelet, select Also include contents of pagelet's <head> tag.
|
Note: If you are clipping an element where there are multiple identifiable instances (for example, a divs with a class attribute that is the same for a number of divs on the same page,) only one div will be returned. Using Clip a region using tag attributes will return the first occurrence of an element that matches the attribute value. To clip an occurrence other than the first occurrence, you must use Clip a region using Intelligent Matcher. |
Oracle WebCenter Ensemble allows you to inject pagelets into web pages that are proxied, as well as not proxied by Oracle WebCenter Ensemble. You can also use Oracle WebCenter Ensemble as a portlet provider for a portal such as Oracle WebCenter Interaction or Oracle WebLogic Portal.
This section describes the changes that Oracle WebCenter Ensemble makes to HTML code when injecting pagelets into consuming web pages. Note that Oracle WebCenter Ensemble does not make changes to:
HTML that is injected using lightweight clipping.
HTML that is wrapped in an IFrame.
Oracle WebCenter Ensemblee creates fragments out of pagelet HTML, separating the code into <HEAD> and <BODY> sections that can be injected into the necessary code locations of the consuming web page.
In this example, Oracle WebCenter Ensemble injects a pagelet's <HEAD> contents into the <HEAD> section of the consuming page.
Representation of a consumer page's code before injection:
<HTML><HEAD>Consumer page script</HEAD><BODY><pt:ensemble.inject ...></BODY></HTML>
Representation of a pagelet's code before injection:
<HTML><HEAD>Pagelet script</HEAD><BODY>Pagelet body</BODY></HTML>
Representation of the consumer web page's code after injection of the pagelet:
<HTML><HEAD>Consumer page scriptPagelet script</HEAD><BODY><DIV pageletcontainer>Pagelet body</DIV></BODY></HTML>
In this example, Oracle WebCenter Ensemble does not render the <HEAD> contents of the consumer page, because the consumer page is already rendered. Oracle WebCenter Ensemble adds the <HEAD> contents above the <DIV> pagelet container in the pagelet body.
Representation of a consumer page's code before injection:
<HTML><HEAD>Consumer page script</HEAD><BODY><script>injectpagelet(...);</script></BODY></HTML>
Representation of a pagelet's code before injection:
<HTML><HEAD>Pagelet script</HEAD><BODY>Pagelet body</BODY></HTML>
Representation of the consumer web page's code after injection of the pagelet:
<HTML><HEAD>Consumer page script</HEAD><BODY>Pagelet script<DIV pageletcontainer>Pagelet body</DIV></BODY></HTML>
In this example, Oracle WebCenter Ensemble does not need to separate the <HEAD> and <BODY> sections, because the pagelet is being injected into an IFrame, whose code is separated from the surrounding web page. For this reason, Oracle WebCenter Ensemble returns the pagelet as it appears on the server.
Representation of a consumer page's code before injection:
<HTML><HEAD>Consumer page script</HEAD><BODY><script>injectpagelet(..., 'iframe', ...);</script></BODY></HTML>
Representation of a pagelet's code before injection:
<HTML><HEAD>Pagelet script</HEAD><BODY>Pagelet body</BODY></HTML>
Representation of the consumer web page's code after injection of a pagelet:
<HTML><HEAD>Consumer page script</HEAD><BODY>Pagelet script<DIV pageletcontainer><IFRAME SRC=...><HTML><HEAD>Pagelet script</HEAD><BODY>Pagelet body</BODY></HTML></IFRAME></DIV></BODY></HTML>
This section describes how to add a pagelet to any web page that is proxied by Oracle WebCenter Ensemble. Sample code for adding a pagelet to a web page is provided on the General page of the pagelet configuration. The basic format of the code you use to add pagelets to proxied web pages is:
<pt:ensemble.inject pt:name="library:pagelet" />
Library is the library name and pagelet is the pagelet name, as entered in the Oracle WebCenter Ensemble pagelet configuration.
Any data passed to the pagelet is also included in the above. For details on configuring pagelet parameters, see Configuring Pagelet Parameters and Transport Type.
|
Note: You must define the namespace prefix 'pt' in the web page asxmlns:pt='http://www.plumtree.com/xmlschemas/ptui/ |
This section describes how to add pagelets to non-proxied web pages. To do so, you must add special HTML code to the location of the web page where you want to add the pagelet. During runtime, this HTML code calls the injectpagelet javascript function, which adds Oracle WebCenter Ensemble pagelets as widgets into the parent page. Oracle WebCenter Ensemble assigns a unique name to each pagelet instance. If the pagelet requires authentication, a log in screen appears before the pagelet is rendered.
Add the following HTML code to the <HEAD> section of the web page to which you want to add the pagelet:
<script type="text/javascript" src="http://proxy_name:port_number/inject/v2/csapi"> </script>
This HTML code adds a javascript API that provides access to the injectpagelet javascript function:
function injectpagelet(<library>, <name>, <injectmethod>, <payload>, <arguments>)
{
...
}
Parameters of the injectpagelet function are the following:
<library>: The name of the library that includes the pagelet that you want to add to the web page. The value for this parameter must be a string, which can contain spaces. For example: library name.
<name>: The name of the pagelet that you want to add to the web page. The value for this parameter must be a string, which can contain spaces. For example: pagelet name.
<injectmethod>: Specifies whether an iFrame is or is not used to wrap the pagelet. iFrames are most often used with browsers that have security constraints when making HTTP calls in javascript. Possible values are:
" ": This is the default value, and appears as a space character surrounded by quotation marks. Using this value results in an iFrame not wrapping the pagelet.
|
Note: Do not delete the quotation marks from this value. If you delete the quotation marks, the java compiler will mistakenly compile the value of the payload parameter as the value of the injectmethod parameter. |
iframe: Using this value results in an iFrame wrapping the pagelet. You can add the following options to specify the appearance of the iFrame: width, height, frameborder, align, longdesc, marginheight, marginwidth, scrolling, stylem class
<payload>: The XML payload to send with the pagelet request.
<arguments>: The pagelet arguments to send with the pagelet request. These arguments should be in the following format: param1=value1¶m2=value2¶m3=value3.
The values that you supply for the pt:onhttperror parameter of the pt:ensemble.inject tag control Oracle WebCenter Ensemble's pagelet request error handling behavior.
In the following example, the pt:onhttperror's value is set to comment. Oracle WebCenter Ensemble does not display an error to the end user, but instead adds an HTML comment to the resource page that includes error details:
<pt:ensemble.inject pt:name="library:pagelet" pt:onhttperror="comment">
In the following example, the pt:onhttperror's value is set to inline. Oracle WebCenter Ensemble renders the body of the error response (for example, an error message or login form) in the page:
<pt:ensemble.inject pt:name="library:pagelet" pt:onhttperror="inline">
In the following example, the pt:onhttperror's value is set to fullpage. Oracle WebCenter Ensemble returns the error response to the browser, instead of sending the resource response. Oracle WebCenter Ensemble handles the first error that it encounters while transforming a resource page, thus alleviating any chance of subsequent errors.
<pt:ensemble.inject pt:name="library:pagelet" pt:onhttperror="fullpage">
You can use Oracle WebCenter Ensemble to add a non-proxied pagelet to a portal such as Oracle WebCenter Interaction or Oracle WebLogic Portal. Non-proxied pagelets appear as portlets in a portal. To use Oracle WebCenter Ensemble as a portlet provider for a portal, register the following URL as a portlet location in your portal:
http://host:port/inject/v2/portlet/libraryname/pageletname?<instanceid=instance_ID_number>&content-type=html&<payload=xmlpayload>&<param1=value1>&<param2=value2>
This URL contains the call that returns the pagelet to the portal. The following query string arguments define how the pagelet should be returned:
<instanceid>: The instance ID of the pagelet.
<content-type>: Specifies the type of content that is returned to the portal.Values can be the following:
javascript: Returns injectable code to the portal.
html: Returns the pagelet markup with its associated PTPortlet object.
iframe: Returns an IFrame that points back to the inject api, filling the IFrame with the pagelet content, instead of directly inline with the page. The IFrame can be styled by providing a set of query string parameters.
<payload> and <pagelet> parameters: If you want the content of the pagelet to change dynamically, configure the parameters in your portal, then add these parameters to the consumer pagelets. If you want the content to remain static, you can hard code these values.
This section describes how to use pagelet parameters to pass data to pagelets. It is divided into the following sections:
Passing Data with Pagelet Parameters, describes how to use pagelet parameters to pass data to the pagelet.
Passing Data with the Pagelet Payload, describes how to use the pagelet payload to pass data to the pagelet.
Configuring Pagelet Parameter Transport Type, describes how the pagelet parameter transport type allows you to port Oracle WebCenter Interaction portlets to work as pagelets within Oracle WebCenter Ensemble.
Parameters are name/value pairs that provide information to the pagelet code. For example, in a discussions pagelet, parameters could specify which discussions or the number of discussion threads to display. Parameters are viewable in the pagelet documentation.
You configure the pagelet parameters that can be passed to the pagelet in the pagelet configuration in the Ensemble Console. You include pagelet parameter values in the pagelet injection code that is added to a web page.
This section is divided into the following sub-sections:
To configure parameters for a pagelet in the Ensemble Console:
Launch the Ensemble Console.
Click the APPLICATIONS tab.
Click the Pagelets sub-tab.
Click the name of the pagelet you want to configure.
On the Parameters page, type a Name, Description, and Type for the parameter.
|
Note: The Description and Type fields are used for pagelet documentation and are optional. Pagelet documentation is automatically created and can be viewed in the Pagelet Discovery UI. For details on the Pagelet Discovery UI, see Accessing Pagelet Discovery for Developers. |
To make the parameter mandatory, select the check-box under Mandatory.
To add the parameter, click Add.
Click Save.
To delete a parameter, select the checkbox to the left of the parameter and click Delete.
The Pagelet Parameter Transport Type setting is provided for porting Oracle WebCenter Interaction portlets to Oracle WebCenter Ensemble pagelets. For details, see Configuring Pagelet Parameter Transport Type.
You set pagelet parameter values in the pagelet injection code using the parameter names configured in the Ensemble Console. For example:
<pt:ensemble.inject pt:name="library : pagelet" param1="foo" param2="bar" />
In this example, Oracle WebCenter Ensemble passes the pagelet library:pagelet two parameters: param1 with a value of foo, and param2 with a value of bar.
You can send a resource's query string parameters as pagelet parameters. For example:
<pt:ensemble.inject pt:name="library:pagelet"pt:forwardparams="true" param1="foo"param2="bar"/>
In the example above, any query string parameters that are in the request to the resource are sent as pagelet parameters in the request to the pagelet. Pagelet parameters defined in the pt:ensemble.inject tag override identically-named parameters in the resource request.
Any text data can be passed to the pagelet by including it within the <pt:ensemble.inject> tag. For example:
<pt:ensemble.inject pt:name="library:pagelet"> This is the payload. </pt:ensemble.inject>
In this example, Oracle WebCenter Ensemble passes the text This is the payload to the pagelet as the pagelet payload.
The pagelet retrieves the payload through the Oracle WebCenter Interaction Development Kit (IDK) proxy API. In addition to extracting the payload as raw text, the Oracle WebCenter Interaction Development Kit (IDK) proxy API provides methods to extract an XML payload as an XML document.
For more information on the Oracle WebCenter Interaction Development Kit (IDK) proxy API, see the following documentation:
Oracle WebCenter Interaction Development Kit (IDK) proxy API tutorials, located in the Oracle Fusion Middleware Developer's Guide for Oracle WebCenter Ensemble on the Oracle Technology Network at http://www.oracle.com/technology/index.html.
Oracle WebCenter Ensemble allows you to configure a payload schema URL to point to an XML schema that can validate an XML payload. Oracle WebCenter Ensemble only supplies the URL to the pagelet; it is up to the pagelet to use the schema to validate the XML payload.
To configure the payload schema URL:
Launch the Ensemble Console.
Click the APPLICATIONS tab.
Click the Pagelets sub-tab.
Click the name of the pagelet you want to configure.
On the Parameters page, type the schema URL in the Payload schema URL text box.
Pagelet parameter transport type allows you to port Oracle WebCenter Interaction portlets to work as pagelets within Oracle WebCenter Ensemble. Oracle WebCenter Interaction portlets may require Administrator, CommunityPortlet, or Community level preference settings.
For details on portlet settings and preferences, see the developer documentation for Oracle WebCenter Interaction Portlet Settings and Preferences in the Oracle Fusion Middleware Web Service Developer's Guide for Oracle WebCenter Interaction on the Oracle Technology Network at http://www.oracle.com/technology/index.html.
To supply these preferences from Oracle WebCenter Ensemble:
Launch the Ensemble Console.
Click the APPLICATIONS tab.
Click the Pagelets sub-tab.
Click the name of the pagelet you want to configure.
On the Parameters page, select the appropriate Pagelet Parameter Transport Type from the drop-down.
To supply Administrator preferences, select Global - Admin Prefs.
To supply Community preferences, select Realm - Community Prefs.
To supply CommunityPortlet preferences, select Pagelet Realm - Community Pagelet Prefs.
Add parameters, using the same name as the preferences in the portlet. For details on adding parameters, see Configuring Parameters in the Ensemble Console.
Define the parameters in your pagelet injection code. For details on setting parameter values, see Setting Parameter Values in Pagelet Injection Code.
Metadata can be used to store additional information about a pagelet. Metadata fields are viewable in the pagelet documentation.
To configure metadata fields:
Launch the Ensemble Console.
Click the APPLICATIONS tab.
Click the Pagelets sub-tab.
Click the name of the pagelet you want to configure.
On the Metadata page, perform the following:
In the Name box, type the name of the metadata field.
In the Value box, type the mapped value.
To create additional metadata fields, click Add.
To delete metadata fields, select the metadata field and click Delete.
By default, pagelets can be consumed by any Oracle WebCenter Ensemble proxied application. To restrict which resources can consume a pagelet:
Launch the Ensemble Console.
Click the APPLICATIONS tab.
Click the Pagelets sub-tab.
Click the name of the pagelet you want to configure.
Restrict all resources from consuming the pagelet. On the Consumers page, clear the All consumers allowed check box.
Add resources able to consume the pagelet by clicking Add.
Select one or more resources to add.
Click Add selected items.
Click OK.
To remove a resource from the list of consumers, select the resource to remove and click Delete.
Pagelets configured in Oracle WebCenter Ensemble are automatically documented in the Oracle WebCenter Ensemble Pagelet Discovery UI. To access the pagelet discovery UI:
Launch the Ensemble Console.
Click the APPLICATIONS tab.
Click the Pagelet Docs sub-tab.
To expose Oracle WebCenter Analytics reports as pagelets through Oracle WebCenter Ensemble, you perform the following:
Import the Oracle WebCenter Analytics resource migration file that is installed with Oracle WebCenter Ensemble. For details, see Importing the Oracle WebCenter Analytics Migration File.
Add Oracle WebCenter Analytics and Oracle WebCenter Interaction image server files to Oracle WebCenter Ensemble's image server directory. For details, see Adding Oracle WebCenter Analytics and Oracle WebCenter Interaction Image Server Files to Oracle WebCenter Ensemble.
For instructions on configuring Oracle WebCenter Ensemble to send event data to Oracle WebCenter Analytics, see Configuring Oracle WebCenter Ensemble to Send Event Data to Oracle WebCenter Analytics.
To import the Oracle WebCenter Analytics Migration file:
Launch the Ensemble Console.
Click the Administration tab.
Click the Migration sub-tab.
Click the Import tab.
Type the full path to the Oracle WebCenter Analytics resource migration file in the Import this file box:
install_dir/ensembleadminui/version_number/migration/analytics_ensemble_migration.xml
Choose how you want to deal with duplicate resources by selecting Rename imported resource or Overwrite existing resource.
Click Prepare Import.
Enter the URL for the Analytics Console following into the Import Preparation box. For example: http://machine_name:11944/analytics/
Click Import.
On success, the Ensemble Console displays a list of imported objects and any autofixes that were completed during the import process.
Go to Oracle WebCenter Configuration Manager.
Copy the settings found in Ensemble > ALUI Security Database to Analytics > ALUI Security Database, overwriting the original Analytics ALUI Security Database settings.
Restart the Analytics service.
Check the following URL, which should now successfully display Analytics portlets being proxied through Oracle WebCenter Ensemble: http://proxy_machine_hostname:proxy_port/analytics/ui/console.jsf
Oracle WebCenter Analytics reports use Cascading Style Sheets (CSS). These style sheets are delivered with Oracle WebCenter Analytics, in the Oracle WebCenter Analytics image server directory. You must add Oracle WebCenter Analytics image server files to the Oracle WebCenter Ensemble image server directory for Oracle WebCenter Analytics reports to correctly appear.
Additionally -- because Oracle WebCenter Analytics reports include some Oracle WebCenter Interaction images -- you must add Oracle WebCenter InteractionOracle WebCenter Interaction image server files to Oracle WebCenter Ensemble's image server directory for Oracle WebCenter Analytics reports to correctly appear.
To add Oracle WebCenter Analytics and Oracle WebCenter Interaction image server files to Oracle WebCenter Ensemble:
Copy the ptanalytics folder, located in the following location on the Oracle WebCenter Analytics server:
install_dir/ptimages/imageserver/plumtree/ptanalytics
Paste the ptanalytics folder into the plumtree folder, located in the following path on the machine on which you installed Oracle WebCenter Ensemble's Administrative UI and Login Server component:
install_dir/ensembleproxy/version/webapp/ensemblestatic/imageserver/plumtree/...
Copy the common folder, located in the following location on the Oracle WebCenter Interaction server:
install_dir/ptimages/imageserver/plumtree/common
Paste the common folder into the plumtree folder, located in the following path on the machine on which you installed Oracle WebCenter Ensemble's Administrative UI and Login Server component:
install_dir/ensembleproxy/version/webapp/ensemblestatic/imageserver/plumtree/...
Copy the portal folder, located in the following location on the Oracle WebCenter Interaction server:
install_dir/ptimages/imageserver/plumtree/portal
Paste the portal folder into the plumtree folder, located in the following path on the machine on which you installed Oracle WebCenter Ensemble's Administrative UI and Login Server component:
install_dir/ensembleproxy/version/webapp/ensemblestatic/imageserver/plumtree/...
Restart Oracle WebCenter Ensemble.
To expose BEA AquaLogic Pathways pagelets through Oracle WebCenter Ensemble, you import the BEA AquaLogic Pathways resource migration file that is installed with Oracle WebCenter Ensemble, then edit the resource migration file to point to the parent URL of the BEA AquaLogic Pathways pagelets.
To expose BEA AquaLogic Pathways pagelets through Oracle WebCenter Ensemble:
Launch the Ensemble Console.
Click the Administration tab.
Click the Migration sub-tab.
Click the Import tab.
Type the full path to the BEA AquaLogic Pathways resource migration file in the Import this file box:
install_dir/ensembleadminui/version_number/migration/pathways_ensemble_migration.xml
Choose how you want to deal with duplicate resources by selecting Rename imported resource or Overwrite existing resource.
Click Prepare Import.
Enter the parent URL for the BEA AquaLogic Pathways pagelets into the Import Preparation box. For example: http://machine_name:8081/graffiti-webui/
Click Import.
On success, the Ensemble Console displays a list of imported objects and any autofixes that were completed during the import process.
