This sections contains the following:
The AJAXTableContainerProvider is available, by default, on the Portal Server Enterprise sample with a fresh install of this relase of the Portal Server software. The container provider is added to the top level organization of the portal server and will be available in all the sub-organizations created under the top level organization. However, the AJAXTableContainerProvider will not be installed with other samples because other samples do not need the AJAXTableContainerProvider to function. However, AJAXTableContainerProvider can be easily added to the display profile to allow usage on any other custom portal.
Set up configuration information.
To set up configuration information:
Create a temporary directory to store the configuration files.
Copy the input.properties.template file from PortalServer-BaseDir/samples/portals/shared/ directory to the temporary directory as input.properties file.
Edit the input.properties file (in the temporary directory) and replace all the tokens that begin and end with % with the appropriate portal settings.
Set up password information.
Copy the password.properties.template file from PortalServer-BaseDir/samples/portals/shared/ directory to the temporary directory (created in Step 1,a) as password.properties file.
Edit the password.properties file in the temporary directory and replace all the tokens that begin and end with % with the appropriate portal settings.
Deploy the AJAXTableContainerProvider.
To deploy, type Ant-Home/bin/ant -buildfile PortalServer-BaseDir/samples/portals/build.xml install_ajax. This command will install just the container provider and make it available at the global level DP for use in any portal. This will not deploy the static files to the webapp.
To deploy the static files, type PortalServer-BaseDir/bin/psadmin redeploy -u amadmin -w amadmin-password -p portal-ID. Now, the portal webapp will be redeployed and AJAXTableContainerProvider will be made available.
Log in to Portal Server management console as amadmin.
Navigate to the Manage Channels and Containers section of the organization
Select the container under which you want to add the AJAX container.
Typically this is a tab container or a single page container.
On the right frame, click on New Channel or Container.
Go through the wizard and select the steps to add a new container.
Ensure that you select AJAXTableContainerProvider as the container provider
After adding the new container, customize the container title and description properties, and add channels to the container by clicking on the Show or Hide Channels and Containers on Portal Desktop link.
The AJAXTableContainerProvider defines the following new display profile properties:
A collection of boolean properties used to determine whether a channel will display it's edit content inline. If set to TRUE, inline editing is enabled for the channel or portlet. If set to FALSE or missing, edit pages will be displayed using JSPSinglePageContainer.
A string property, it specifies the name of the style to be used by the container. The provider ships three styles out of the box: orange, gray and blue.
A string property, it specifies the relative path for the styles directory in the portal webapp. The default value is /desktop/ajaxcontainers/styles/.
A collection, it lists styles that can be used by the container. The provider ships three styles out of the box: orange, gray and blue.
A collection, it lists channel names that must be displayed under the My Channels category.
The AJAXTableContainerProvider allows customization of the styles. You can add a new style by copying an existing style directory and modifying the contents of that style. For more information on the structure of a style directory, see AJAXTableContainerProvider CSS. The JavaScript that is shipped with the AJAXTableContainerProvider is compressed for performance optimization. Hence the JavaScript cannot be customized easily using a script editor.