Enable session handling with the traditional Web Content Viewer

 

+

Search Tips   |   Advanced Search

 

When working with traditional Web Content Viewers installed on remote servers, the default Web content session handling works by initiating a new Web content session for each Web Content Viewer instance on a page. This can cause performance issues if many users access a page containing a large number of remote Web Content Viewers.

Enable session handling to keep track of valid sessions between Web Content Viewer instances on a page.

In the following procedures "Web content server" represents the server where the Web content is stored, and "remote server" represents the server where the remote rendering portlets are installed.

1. If accessing a remote rendering portlet anonymously enable anonymous sessions on the remote server.

   The following procedure enables sessions to be created for anonymous users. Active anonymous sessions will be managed according to the authentication method of the Web Content Viewer as described in steps 2 and 3:

   1. Open administrative console on the remote server.

   2. Go to...
      Resources | Resource Environment Providers | WP_NavigatorService | Custom properties

   3. Add a new property named public.session with a value of true.

2. If you use LTPA authentication, setup single signon on both servers to ensure that only a single session will be active between each instance WebSphere Portal for each user.

   Both servers must be configured to use the same LDAP repository.

   1. Set up Single Signon on the Web content server:

      • Open administrative console on the Web content server.

      • Go to...
        Security | Global security | Authentication mechanisms | LTPA | Single signon (SSO)

      • Ensure enabled is checked and enter the part of the domain name that is common to both servers in the domain name field.

        For example: ilwwcm.au.ibm.com

      • Click OK and save to master configuration.

      • Go back to...
        Security | Global security | Authentication mechanisms | LTPA

      • Enter a password and path for the key file and click Export Keys.

   2. Set up Single Signon on the remote server:

      • Open administrative console on the remote server.

      • Go to...
        Security | Global security | Authentication mechanisms | LTPA | Single signon (SSO)

      • Ensure enabled is checked and enter the part of the domain name that is common to both servers in the domain name field.

        For example: ilwwcm.au.ibm.com

      • Click OK and save to master configuration.

      • Go back to...
        Security | Global security | Authentication mechanisms | LTPA

      • Enter a password and path to the key file you exported from the Web content server and click Import Keys.

   3. Restart both servers.

   4. Verify that single signon is working correctly by logging in to the remote server and then changing the URL in the address bar to access the Web content server.

      If single signon is working you will be shown the authenticated home screen of the Web content server and not asked to login again.

   5. Set up the remote rendering portlet on the remote server:

      • Locate the ilwwcm-remoterenderingportlet.war file. By default, this file is located in...
        PortalServer_root/installableApps

        of the Web content server.

      • Copy the ilwwcm-remoterenderingportlet.war file to the remote server.

      • Install the ilwwcm-remoterenderingportlet.war on the remote server or update the existing ilwwcm-remoterenderingportlet.war if the remote rendering portlet has previously been installed on the remote server.

3. If you use credential vault authentication, enable the session service on the remote server to keep track of valid sessions.

   The service will help ensure that only a single session will be active between each instance WebSphere Portal for each user.

   The service will manage access to the pool of active sessions and queue the requests for sessions that are in the process of being established. It will not stop requests for established sessions to other servers or with different credentials.

   When a request is made for a session with a defined credential vault slot and URL, the WCMSessionService checks to see if this session already exists. If so, this session will be used. If not, a new session will be created.

   1. Set up the remote rendering portlet on the remote server:

      • Locate the ilwwcm-remoterenderingportlet.war file. By default, this file is located in...
        PortalServer_root/installableApps

        of the Web content server.

      • Copy the ilwwcm-remoterenderingportlet.war file to the remote server.

      • Open the ilwwcm-remoterenderingportlet.war file with an appropriate file archive program.

      • Extract the ilwwcm-remoterenderingportlet-service.jar file to
        profile_root/wcm/shared/app

      • Delete the ilwwcm-remoterenderingportlet-service.jar file from the ilwwcm-remoterenderingportlet.war using the archive program and save the WAR file.

      • Install the ilwwcm-remoterenderingportlet.war on the remote server or update the existing ilwwcm-remoterenderingportlet.war if the remote rendering portlet has previously been installed on the remote server.

   2. Setup the shared WCMRemoteLib library on the remote Portal server which is used by the WCMSessionService :

      • Open administrative console on the remote server.

      • Go to...
        Environment | Shared Libraries

      • Create a new library with name WCMRemoteLib and classpath...
        ${WPS_HOME}/wcm/shared/app/ilwwcm-remoterenderingportlet-service.jar

      • Go to...
        Servers | Application servers | WebSphere_Portal | Java and Process Management | Class loader | Classloader_name | Library

      • Add the WCMRemoteLib library.

   3. Setup the WCMSessionService on the remote server. This service is used to obtain the session cookie used to make the request to the Web content server:

      • Edit...
        profile_root/wcm/shared/app/config/services.properties

      • Ensure the following session service line is included:

        # WCM session service com.ibm.workplace.wcm.service.contentServer.AbstractWCMSessionService= com.ibm.workplace.wcm.service.contentServer.WCMSessionService
        

   4. Restart the remote server.

Parent topic:

Display content with Web Content Viewers

---