Deploy the portal.war file on the Apache server by copying the portal.war file to your CATALINA_HOME\webapps\ directory. The portal.war file is located in Ensemble_Install_dir\ensembleproxy\version\integration\alisso\.

For example,

to C:\Program Files\Apache Software Foundation\Tomcat5.5\webapps\

Note: Although you can use various brands of Web servers to host the Oracle WebCenter Interaction portal, you must use Apache Tomcat to host the portal.war file.

Open Services and restart the Apache Tomcat service if it is already running. If it is not running, start the service.

Note: You can also use Tomcat Manager to deploy the portal.war.

On the machine on which Oracle WebCenter Interaction is installed, navigate to WCI_Install_Dir\settings\portal\. For examle,

C:\bea\alui\settings\portal.

Edit portalconfig.xml and set the AllowAutoConnect node to 1.

Restart the Oracle WebCenter Interaction services. (To restart everything you would restart BEA AL Notification Service, BEA ALI API Service, BEA ALI Automation Service, BEA ALI Content Upload Service, BEA ALI Document Repository Service, BEA ALI LDAP Directory, BEA ALI Logger, BEA ALI Remote Portlet Service, BEA ALI Search Cluster Manager, BEA ALI Search.)

Note: Before performing these steps, determine the security impact that enabling Remember Me cookies might have on your portal environment.

Open Configuration Manager by clicking Start > Programs > Oracle > Configuration Manager and log in using your administrator username and password. For example, administrator/admin. In the left navigation pane, expand Ensemble. Here you see a list of links for changing Ensemble settings.

Click ALUI Directory and ensure Authentication provider is set to ALI and all the Connection Information settings are correct. If you change anything click Save, otherwise continue with the next step.

Before you perform the next step you need to find a value from a database table. Connect to your Oracle WebCenter Interaction database. For example, Start - Programs - Oracle Database 10g Express Edition - Go to Database Home Page. And log in as the WebCenter Interaction user, for example, owidbuser/admin.

View the ptserverconfig table and find the row where the Name equals login token root key. Make a note of the number in the Value column. This may be a negative number, if so, note the negative sign as you will need to enter this in Configuration Manager in the next step.

Note: The number in your table may differ from what you see in the screenshot above.

Back in the WebCenter Configuration Manager, click ALUI Security Login Tokens and ensure Default token type is set to ALUI.

Click Change value to enter the Message authentication code seed value. Enter the value from the ptserverconfig table in the previous step twice and click Ok. Back on the ALUI Security Login Tokens page, click Save.

Click SSO Login and select Enabled to enable portal cookie replication.

For the Portal Cookie Replication URL enter the location to which you deployed the portal.war file on Apache Tomcat in an earlier step, for example, http://win2k3ent.us.oracle.com:8088/portal/PortalIntegrationServlet.

If you wish, you can change Timeout which is the frequency, in milliseconds, at which Oracle WebCenter Ensemble checks for portal cookies. You can also change Access Level which is the access level assigned to the user when Oracle WebCenter Ensemble detects a valid portal session cookie. Valid values are between 1 and 10. The defaults are shown in the screenshot.

Click Save and log out of Configuration Manager.

Go to the Ensemble Administration Console URL, for example, http://win2k3ent:20070/ensembleadminui and log in with the Administrator's username and password, for example administrator/admin.

Click the APPLICATIONS tab. This will take you to the Resources page by default.

On the Resources page, click Create new. On the General page that appears, enter a Name,for example WC Services.

Click the Connections tab. For Internal URL prefix enter the hostname and port of the base URL of the service producer. For example, http://producer_svr:8891/.

For External URL prefixes enter any name that is unique within Ensemble, for example /webcenter/. This is the URL, relative to the Ensemble proxy, where the application will be running.

Click Save.

Set security on your new resource by navigating to POLICIES, selecting your resource, for example WC Services, and clicking Policies. For example, select and delete the Administrator user to allow anonymous access. Click Save.

Return to APPLICATIONS and click the Pagelets tab, then Create new.

On the General tab, name the pagelet, for example wc_mail_portlet.

For Parent resource, select the resource you created in the previous step, for example WC Services.

Supply a Library name for example, Services. The Library name is a mandatory grouping name for pagelets.

Click the Location tab and you see the Internal URL prefix is already populated from the parent resource.

For URL suffix enter the suffix that completes the pagelet producer end point URL for the mail task flow. For example, servicesproducer/services?id=Mail&width=500px&height=300px. Click Save.

Repeat these steps to create another pagelet for the Documents task flow and name it, for example, wc_docs_portlet. Use the same Parent Resource (WC Services) and the same Library name (Services) as you used previously. On the Location tab enter the suffix that completes the pagelet producer end point URL for the documents task flow. For example, servicesproducer/services?id=DocManager&width=500px&height=300px.

WebCenter Interaction will use an Ensemble REST API to retrieve portlet content. The REST API runs as an intrinsic resource in Ensemble and is named aluiinjectorresource. This resource must accept the WebCenter Interaction portal login token as a valid form of authentication.

Navigate to POLICIES and click aluiinjectorresource.

Click the Authentication Level tab and select Allow Portal Login Token. Click Save.

Note: These settings control access to the REST API itself, not to the pagelet content. You can require authentication for pagelets even if the REST API is publicly accessible.

Go to the Oracle WebCenter Interaction URL, for example, http://win2k3ent:7001/portal/server.pt. Log in with the Administrator's username and password (or a user with the appropriate permissions to create these objects), for example, administrator/admin.

Click Administration and navigate to the administrative folder where you wish to store the objects, for example, Portal Resources.

From the Create Object drop-down, select Remote Server.

On the Create Remote Server Main Settings page, for Base URL enter the URL for the Ensemble proxy, for example http://win2k3ent:20050/. Click Finish.

On the Save In page, enter a name for the Remote Server, for example, WebCenter Remote Server and click Save.

On the Object Saved page, click Create new Portlet Web Service.

On the Create Web Service - Remote Portlet Main Settings page, the Portlet URL points to the REST API for the pagelet. This should be in the form:

inject/v2/portlet/<pagelet_library>/<pagelet_name>?csapi=true&content-type=iframe.

For example, for the mail portlet:

inject/v2/portlet/Services/wc_mail_portlet?csapi=true&content-type=iframe

The WebCenter Remote Server you created has already been selected. If you closed the Save dialog in the previous sub-step, to get to this page, select Web Service - Remote Portlet from the Create Object drop down then Browse to select the Remote Server.

Note: ADF-based pages must be injected into WebCenter Interaction using iFrames. Also note that for WebCenter Interaction only, the API uses portlet and not pagelet in the Portlet URL. Pagelet is used in all other cases.

You may wish to increase the Portlet Timeout if there is slow performance in displaying the portlet.

Click the HTTP Configuration link on the left of the page. On the HTTP Configuration page click Add Gateway Prefix.

Click the Advanced Settings link on the left of the page. On the Advanced Settings page check Send Login token to Portlets. The aluiinjectorresource is expecting a portal login token and this ensures it is sent. Click Finish.

On the Save In page, enter a name for the Web Service, for example, WebCenter Mail Web Service and click Save.

On the Object Saved page, click Create new Portlet.

On the Create Portlet Main Settings page, select the Portlet Type/Size, for example Wide. Click Finish.

The WebCenter Web Service you created has already been selected. If you closed the Save dialog in the previous sub-step, to get to this page, select Portlet from the Create Object drop down.

On the Save In page, enter a name for the portlet, for example, WebCenter Mail and click Save.

On the Object Saved page, click Close.

Note: In this scenario, everything is done as Administrator so you don't need to edit security. In a realworld situation you should edit security on the portlet to allow your users to select it for their My Pages or Community pages.

Repeat the steps above to create a Portlet Web Service for the Document Library portlet using the appropriate Portlet URL, for example, inject/v2/portlet/Services/wc_docs_portlet?csapi=true&content-type=iframe. Save it as WebCenter Docs Web Service.

Then follow the steps above to create a portlet based on this Web Service and call it WebCenter Docs.

Navigate to the page you want to place the portlets on, for example, the Services page of the Sales community and edit the page to add the WebCenter Services portlets, WebCenter Docs and WebCenter Mail.