Page Component Portlets - describes how to display a page component as a portlet in a portal page
Navigation in Pages - describes how to customize the navigation that displays in Pages
The Pages Launcher Portlet
The Pages Launcher Portlet displays links to the Dashboard, available LiveSpaces, and available DataSpaces. This portlet is created in the Pages Objects folder when you import the Pages migration package (as described in the Installation Guide for AquaLogic Pages).
Note:
Only LiveSpaces and DataSpaces to which the user has access appear in the portlet.
To provide access to Pages, add this portlet to a community page, tell users to add the portlet to their My Pages, or make the portlet mandatory for some groups so that it automatically shows up on the users' My Pages. You must have at least Select access to a portlet to add it to a My Page or community page. By default users in the Pages Users and Pages Administrators groups have Select access to the Pages Launcher Portlet.
Note:
For information on changing access privileges, making a portlet mandatory, or adding a portlet to a My Page or community page, refer to the portal online help.
LiveSpaces and DataSpaces Menus in Portal Navigation
You can add menus (just like the My Communities menu) to display available LiveSpaces and DataSpaces in the portal navigation.
Note:
Only LiveSpaces and DataSpaces to which the user has access appear in the menus.
You must perform the following steps to display the LiveSpaces and DataSpaces menus:
Add the LiveSpaces and DataSpaces navigation tags to a custom header. There is a sample header code file installed with Pages: install_dir\pages\1.0\header_with_pagestags.html (for example, C:\bea\alui\pages\1.0\samples\header_with_pagestags.html). For information on creating your own custom header using the Pages navigation tags, see the AquaLogic User Interaction Development DocumentationAdaptive Tags: Pages.
Create a remote portlet web service that points to the custom header you created. For instructions on creating a remote portlet web service, see the Administrator Guide for AquaLogic Interaction and the portal online help.
Create a portlet based on the remote portlet web service. For instructions on creating a portlet, see the Administrator Guide for AquaLogic Interaction and the portal online help.
Create an experience definition that uses the custom header portlet. For instructions on creating an experience definition, see the Administrator Guide for AquaLogic Interaction and the portal online help.
Create an experience rule that displays the experience definition. For instructions on creating an experience rule, see the Administrator Guide for AquaLogic Interaction and the portal online help.
Note:
You probably want experience rule to apply to the following groups: DataSpace Creators, LiveSpace Creators, Pages Administrators, and Pages Users. Also, if there are any other experience rules defined, you might need to move the experience rule you just created up in the list so that the rule will apply. For information on how experience rules are applied, see the portal online help.
Verify that the LiveSpaces and DataSpaces menus are displaying properly. Log off and log back in as a user that should see the LiveSpaces and DataSpaces menus.
Note:
The LiveSpaces menu should always display because the Dashboard is a LiveSpace. However, the DataSpaces menu will only display after you have created at least one DataSpace in Pages.
Troubleshooting LiveSpaces and DataSpaces Menus
If the LiveSpaces or DataSpaces menus are not showing up, perform the following steps:
Start AquaLogic Interaction Logging Spy and confirm that logging is enabled.
Log out of the portal.
Clear the AquaLogic Interaction Logging Spy log.
Log back in to the portal.
Note:
If you just refresh the page without logging out and logging back in, the page will use cached data, and any errors that occur when the navigation tags execute the request to the Pages server will not display in AquaLogic Interaction Logging Spy.
Look in the log under Portal application for any errors from the PagesIntegration component.
If there are no errors from the PagesIntegration component, check the settings described in Verifying Navigation Settings. (You will probably see two other tag errors regarding not being able to find data tags, this is due to the Pages tags not functioning properly.)
If there are errors from the PagesIntegration component, refer to Typical Errors.
Verifying Navigation Settings
If your LiveSpaces and DataSpaces menus are not displaying in the portal navigation and AquaLogic Interaction Logging Spy does not display any PagesIntegration component errors:
Verify that you are really logged in as a user that views the Tag Navigation Experience Definition. You should see a blue banner. If you see a white banner with the AquaLogic liquid image, you are logged in as a user that views the Pluggable Navigation. Review the Experience Definition Rules to ensure that the Tag Navigation Experience Definition is being used for the user you used to log in.
Verify that the Pages navigation tags were added to your custom header. Open your custom header file and search for pt:pages.livespacesdata and pt:pages.dataspacesdata.
If you do find these entries, continue with the next step.
If you do not find these entries, the Pages navigation tags were not added to your custom header. See the AquaLogic User Interaction Development DocumentationAdaptive Tags: Pages.
Verify that the experience definition you are viewing uses header.html. Add some random text to the top of header.html, save the file, and reload the portal page.
If you see the random text at the top of the page, remove the random text from header.html, save the file, and continue with the next step.
If you do not see the random text, the experience definition you are viewing is not using header.html as its header portlet. Verify that there is not a higher priority experience definition that is being used for the user. If there is a higher priority experience definition, move the rule that uses the Tag Navigation Experience Definition higher up in the rules list. If there is not a higher priority experience definition, continue with the next step.
Verify that the Pages tags are being transformed. View the source for the portal page, and search for pt:pages.livespacesdata and pt:pages.dataspacesdata.
If you do not find these entries, the Pages tags are being transformed. Skip to step l.
If you do find these entries, the Pages custom tags were not properly deployed to the portal. Verify that the Pages Portal Extensions component was installed on the portal. If it was installed, continue with the next step. If it was not installed on the portal, refer to the Installation Guide for AquaLogic Pages for instructions.
Verify that the custom tag libraries are properly deployed.
On a Java portal, look for taglibPages.jar in install_dir/ptportal/6.1/lib/java and look for the WEB-INF/lib folder reference in install_dir/ptportal/6.1/webapp/portal.war. Use WinZip or WinRAR to view the contents of the .war file. If you run the portal on BEA WebLogic, you also need to open portal.ear and verify the content of portal.war inside the .ear file. With portal on WebLogic server, ensure that you updated the portal deployment after installing the Portal extensions.
On a .NET portal, look for taglibPages.dll in install_dir/ptportal/6.1/bin/assemblies and install_dir/ ptportal/6.1/webapp/portal/web/bin.
Verify that the Pages tag library is defined as a custom tag library. Open install_dir/settings/portal/CustomTags.xml. Verify that it contains the following entry:
<libfile name="taglibPages"/>
Typical Errors
Typical errors include:
Portlet exceptions: These are usually due to the Pages server being unavailable. Verify that the BEA AquaLogic Pages service is running.
IDK exceptions: These are usually due to the ALI API service not running or not being configured correctly in the portal. Verify that the BEA ALI API service is running. To verify that it is configured correctly in the portal:
Log in to portal as an administrator.
Click Administration.
In the Select Utilities menu, click Portal Settings.
In the Portal Settings Editor, on the left, under Edit Utility Settings, click Portal URL Manager.
Copy the Soap Server URL value and paste it into a web browser. The page that appears should be titled QueryInterfaceAPI. If this is not the case, correct the URL in the Portal Settings Editor.
OpenKernel exceptions: These are usually due to the adaptive tags not being able to find a setting in install_dir/settings/configuration.xml. Verify that the Configuration Manager was installed properly and that the configuration.xml file exists.
ObjectManager exceptions: These are usually due to problems with the Pages objects that were imported into the portal from the migration package. To correct the problems:
Log in to the portal as an administrator.
Click Administration.
Open the Pages Objects folder. If it does not exist, refer to the Installation Guide for AquaLogic Pages for instructions on importing the migration package.
Expand the web services, and open the Pages LiveSpaces Web Service.
In the Web Service Editor, on the left, under Edit Standard Setting, click Properties and Names, and write down the UUID.
Open the Pages DataSpaces Web Service and write down its UUID.
Open install_dir/settings/configuration.xml in a text editor.
Search for LiveSpacesListWebServiceUUID and verify that the value matches the Pages LiveSpace Web Service UUID you wrote down. If it does not match, correct the value in the file and save the file.
Search for DataSpacesListWebServiceUUID and verify that the value matches the Pages DataSpace Web Service UUID you wrote down. If it does not match, correct the value in the file and save the file.
Page Component Portlets
You can create a portlet from an existing page component, allowing you to display content from a page component in a portal page.
Notes:
Only users who have permission to see the page component will be able to see the content in the portlet. Users must have at least the Guest role on the associated LiveSpace.
Rich text components and image components will not display correctly.
If the page component is deleted, the portlet will display an error.
Click Administration.
Open the administrative folder in which you want to create the portlet.
Click Create Object Portlet.
In the Choose Template or Web Service dialog box, select Pages Components Selector and click OK.
Next to Configure this Portlet, click Edit.
In the Portlet Wizard:
Select the LiveSpace which includes the page component you want to use.
Note:
You can only choose from LiveSpaces you have permission to see.
Select the page component you want to use.
Click Finish.
In the Portlet Editor, click Finish.
In the Save Object dialog box, type a name for the portlet and click Save.
In the Object Saved dialog box, click Close.
You can now add the portlet to a portal page.
Navigation in Pages
By default, Pages uses the same navigation as the portal though Pages displays only a portion of that navigation. Pages displays only the horizontal drop-down menus (not the links at the top of the page or the banner). If you use a left vertical navigation scheme or custom navigation with a header portlet that does not display horizontal navigation, you must customize the navigation for Pages. If you want Pages to display different navigation than the portal, you also need to customize the navigation.
To use a different standard navigation scheme for Pages:
Create an experience definition that uses a supported navigation scheme. In the Experience Definition Editor, on the Edit Navigation Options page, select the navigation scheme to use for Pages. The following standard navigation schemes are supported in Pages: Horizontal Combo Box Drop-Down Navigation, Mandatory Links Only, No Navigation, and Horizontal Drop-Down Navigation.
Create an experience rule for Pages that uses the experience definition you created. Add a URL condition with the following value: *Pages_host:Pages_port/pages* (for example, *pages.company.com:11990/pages*).
To customize the navigation for Pages using a header portlet:
Create a header portlet that displays horizontal navigation. For information on creating a custom header portlet, see the AquaLogic User Interaction Development Documentation Adaptive Tags: Implementing Custom Navigation.
Note:
Left vertical navigation schemes are not supported in Pages. The top bar and banner sections of header portlets are not displayed in Pages.
Create an experience definition that uses the header portlet you created. In the Experience Definition Editor, on the Choose Header, Footer & Style page, select the header portlet you created. On the Edit Navigation Options page, select Portlet-Ready Navigation.
Create an experience rule for Pages that uses the experience definition you created. Add a URL condition with the following value: *Pages_host:Pages_port/pages* (for example, *pages.company.com:11990/pages*).
For information on creating experience definitions or experience rules, see the Administrator Guide for AquaLogic Interaction or the portal online help.
Note:
Experience definition rules applied to a community do not apply to Pages, even if the user navigates to Pages from that community.
Portlet.
