Enable session handling

 

+
Search Tips   |   Advanced Search

 

The default IWWCM session handling works by initiating a new WCM session for each WCM portlet instance that is on a page. This can cause performance issues if many users access a page containing a large number of WCM portlets.

The following procedures enables a service that is used to keep track of valid sessions. The service will help ensure that only a single session will be active between the instance of IBM WebSphere Portal and WCM 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, but not stop requests for established sessions to other servers or with different credentials.

 

Enable WCM session handling

  1. Remove the service jar from the ilwwcm-remoterenderingportlet.war

    The ilwwcm-remoterenderingportlet.war file contains a jar (ilwwcm-remoterenderingportlet-service.jar). This must be removed if the service is to be used. The jar is added to the class loader instead. It is important it does not appear in both places if the service is to be used.

    1. Open...

      portal_server_root/installableApps/ilwwcm-remoterenderingportlet.war

      ...with an appropriate file archive program.

    2. Extract the ilwwcm-remoterenderingportlet-service.jar file to...

      portal_server_root/wcm/shared/app

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

  2. Create a new shared library

    1. Log in to the administrative console for WebSphere Application Server.

    2. Go to...

      Environment | Shared Library

    3. Create a new shared library called WCMRemoteLib.

  3. Add the library to the portal server

    WebSphere Administration console | Application Servers | WebSphere Portal | classloader | class_loader | libraries | WCMRemotelib | Apply | OK | Save

  4. Edit the Services.Properties file

    1. Open...

      ..\PortalServer\shared\app\config\services.properties

    2. Ensure the following WCM session service line is included:

      # ValidationService 
      com.ibm.wps.services.validation.ValidationService = com.ibm.wps.services.validation.ValidationServiceImpl 
      # WCM session service 
      com.ibm.workplace.wcm.service.contentServer.AbstractWCMSessionService = com.ibm.workplace.wcm.service.contentServer.WCMSessionService 
      # Transcoding Portal Support 

  5. Restart WebSphere Portal

  6. Review...

    portal_server_root/log/SystemOut.log

    ...to ensure the new service is running.

 

How WCM session handling works

When a request is made for a session with WCM for 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.

 

Parent Topic

Display content in a rendering portlet