This preview shows page 317 - 319 out of 568 pages.
About this taskIntroducing WebSphere eXtreme Scale into a WebSphere Portal environment can bebeneficial in the following scenarios:Chapter 6. Configuring305
Important:Although the following scenarios introduce benefits, increasedprocessor usage in the WebSphere Portal tier can result from introducingWebSphere eXtreme Scale into the environment.vWhen session persistence is required.For example, if the session data from your custom portlets must stay availableduring a WebSphere Portal Server failure, you can persist the HTTP sessions tothe WebSphere eXtreme Scale data grid. Data replicates among many servers,increasing data availability.vIn a multiple data center topology.If your topology spans multiple data centers across different physical locations,you can persist the WebSphere Portal HTTP sessions to the WebSphere eXtremeScale data grid. The sessions replicate across data grids in the data centers. If adata center fails, the sessions are rolled over to another data center that has acopy of the data grid data.vTo lower memory requirements on the WebSphere Portal Server tier.By offloading session data to a remote tier of container servers, a subset ofsessions are on the WebSphere Portal servers. This offload of data reduces thememory requirements on the WebSphere Portal Server tier.Procedure1.Splice thewpsWebSphere Portal application and any custom portlets to enablethe sessions to be stored in the data grid.You can splice the application by configuring HTTP session management whenyou deploy the application, or you can use custom properties to automaticallysplice your applications. See “Configuring the HTTP session manager withWebSphere Application Server” on page 295 for more information aboutsplicing the application.2.If you are using the remote scenario, where your container servers are outsideof the WebSphere Application Server, explicitly start remote eXtreme Scalecontainers for remote HTTP session persistence scenarios. Start the containerswith theXS/ObjectGrid/session/samples/objectGridStandAlone.xmlandobjectGridDeploymentStandAlone.xmlconfiguration files. For example, youmight use the following command:startOgServer.sh xsContainer1 -catalogServiceEndPoints <host>:<port>-objectgridFile XS/ObjectGrid/session/samples/objectGridStandAlone.xml -deploymentPolicyFileXS/ObjectGrid/session/samples/objectGridDeploymentStandAlone.xmlFor more information about starting container servers, see “Starting containerservers” on page 386. If you are using an embedded scenario, see “Configuringcontainer servers in WebSphere Application Server” on page 267 for moreinformation about configuring and starting container servers.3.Restart the WebSphere Portal servers. See WebSphere Portal Version 7: Startingand stopping servers, deployment managers, and node agents for moreinformation.