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 your system.
About this task
The backbone of
WebSphere Application Server
Community Edition ,
the kernel, relies on outward modules, referred to as GBeans, to provide
function and capabilities.
Procedure
- Distribute the GBeans.
- Navigate to the extremeScale_root/wasce/bin directory.
- Run the addToCeRepository script for the system that
you are running.
![[Linux]](./icons/nglinux.gif)
addToRepository.sh ceRoot
addToRepository.bat ceRoot
- 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.
- Navigate to the WasCeRoot/var/config directory.
- Open the config.xml file in a plain
text editor.
- Find the following line in the config.xml file:
<module name="org.apache.geronimo.plugins/mconsole-ds/2.1.1/car"/>
</attributes>
- 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
- Specifies a server name that must be unique for every WebSphere Application Server
Community Edition and eXtreme Scale server instance
- catalogServiceEndPoints -
- Specifies the host and port of the eventual catalog server.
- replicationDisabled -
- Specifies if replication of session state is enabled.
- traceSpecification -
- Specifies a string for trace of the eXtreme Scale container within
the Java™ virtual machine (JVM).
- 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,
you must 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 Starting the catalog service in a stand-alone environment 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, you must open the ceRoot/var/config/config-substitutions.properties file
and change the NamingPort key to a value other than 1099.
- Start WebSphere Application Server
Community Edition to
test the bootstrap.
- Navigate to the WasCeRoot/bin directory.
- Set the JAVA_HOME environment variable.
![[Unix]](./icons/ngunix.gif)
export JAVA_HOME=javaHome
set JAVA_HOME=javaHome
- Run the start command.
![[Unix]](./icons/ngunix.gif)
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.