WebSphere eXtreme Scale Administration Guide > Configure WebSphere eXtreme Scale > Cache integration > HTTP session management

Configure the HTTP session manager with WebSphere Application Server Community Edition

WebSphere Application Server Community Edition can share session state, but not in an efficient, scalable manner. WebSphere eXtreme Scale provides a high performance, distributed persistence layer that can be used to replicate state, but does not readily integrate with any application server outside of WebSphere Application Server. You can integrate these two products to provide a scalable session-management solution. You can use the WebSphere Application Server Community Edition modular infrastructure, GBeans, to embed WebSphere eXtreme Scale as the session-state persistence mechanism.

Before you begin

You must unzip or install Geronimo or WebSphere Application Server Community Edition and WebSphere eXtreme Scale on the system.

The backbone of WebSphere Application Server Community Edition , the kernel, relies on outward modules, referred to as GBeans, to provide function and capabilities.

Procedure

1. Distribute the GBeans.

   1. Navigate to the extremeScale_root/wasce/bin directory.

   2. Run the addToCeRepository script for the system that you are running.

      • addToRepository.sh ceRoot

      • addToRepository.bat ceRoot

2. Edit the configuration file. Now that the GBean is distributed, configure WebSphere Application Server Community Edition to know that it should be launched at server startup. You can register the GBean and supply it with configurable arguments that can be used at runtime with the config.xml file.

   1. Navigate to the WasCeRoot/var/config directory.

   2. Open the config.xml file in a plain text editor.

   3. Find the following line in the config.xml file:

      <module name="org.apache.geronimo.plugins/mconsole-ds/2.1.1/car"/>
      
      </attributes>
      

   4. Append the following excerpt before the </attributes> tag.

      <module name="com.ibm.websphere.objectgrid/gbean/1.0/car">
        
      <gbean name="objectgrid/BringupPlugin">
        
      <attribute name="objectgridHome">c:\objectgrid</attribute>
        
      <attribute name="geronimoHome">C:\websphereCE</attribute>
        
      <attribute name="serverName">server1</attribute>
        
      <attribute name="catalogServiceEndPoints">host:port</attribute>
        
      <attribute name="replicationDisabled">false</attribute>
        
      <attribute name="traceSpecification">*=all=disabled</attribute>
        
      </gbean>
      </module>
      

      The values for the GBean parameters in the previous excerpt are examples. You can configure these values.

      objectgridHome

      Specifies the installation directory of objectgridRoot.

      geronimoHome -

      Specifies the installation directory of WebSphere Application Server Community Edition or Apache Geronimo.

      serverName

      Server name that must be unique for every WebSphere Application Server Community Edition and eXtreme Scale server instance

      catalogServiceEndPoints -

      Host and port of the eventual catalog server.

      replicationDisabled -

      Specifies if replication of session state is enabled.

      traceSpecification -

      String for trace of the eXtreme Scale container within the Java™ virtual machine (JVM).

3. Start a catalog server. Your WebSphere Application Server Community Edition image can successfully be able to launch an eXtreme Scale server within its JVM at server startup. For an eXtreme Scale to bootstrap, however, first start a catalog server. The catalog server is analogous to a deployment manager within a WebSphere Application Server topology and must be started before WebSphere Application Server Community Edition starts. After the catalog server is started, enter the hostname and port for the catalog server in the config.xml file within the GBean entry. See Start a stand-alone catalog service for more information. Be sure to read the section on binding the ORB port to a particular hostname and port. You need to specify those endpoints within the GBean configuration. If you have a port conflict on server startup, open the ceRoot/var/config/config-substitutions.properties file and change the NamingPort key to a value other than 1099.

4. Start WebSphere Application Server Community Edition to test the bootstrap.

   1. Navigate to the WasCeRoot/bin directory.

   2. Set the JAVA_HOME environment variable.

      • export JAVA_HOME=javaHome

      • set JAVA_HOME=javaHome

   3. Run the start command.

      • geronimo.sh run

      • geronimo.bat run

   The server should now start up and begin to initialize its components or GBeans. The eXtreme Scale plug-in is the last plug-in to load and outputs the necessary startup trace and information statements.

• Use WebSphere eXtreme Scale for replication of session state in WebSphere Application Server Community Edition
  Every Web application that is deployed to WebSphere Application Server Community Edition requires compliance with the Java Platform, Enterprise Edition specification, along with the geronimo-web.xml descriptor file. This file contains access and dependency information specific to the runtime environment for WebSphere Application Server Community Edition. To allow a Java EE Web application to use the session replication feature of WebSphere eXtreme Scale, the Web application must supply data about the eXtreme Scale plug-in as and session-specific attributes.

Parent topic

HTTP session management

Related concepts

HTTP session management

Related tasks

Configure the HTTP session manager with WebSphere Application Server

Related reference

Servlet context initialization parameters

+

Search Tips   |   Advanced Search