This preview shows page 330 - 332 out of 568 pages.
# traceSpec =# A string of trace file location.# useful for all other application servers besides WebSphere.# traceFile=# This property should be set if you require sessions to be# accessible across hosts. The value will be the name of the# common domain between the hosts.# cookieDomain=# Set to true if the underlying web container will reuse# session ID’s across requests to different hosts. Default is# false. The value of this should be the same as what is set# in the web container.# reuseSessionId=# A string value of either "true" or "false". The default is# "false". Per the servlet specification, HTTP Sessions cannot# be shared across web applications. An extension to the servlet# specification is provided to allow this sharing.# shareSessionsAcrossWebApps = false# Set to true if you want to enable urlRewriting.Default is# false, which means cookies will be used to store data. The# value of this should reflect what is set in the web container# settings for session management.# useURLEncoding = false318IBM WebSphere eXtreme Scale: Administration Guide April 2012
Configuring the dynamic cache provider for WebSphereeXtreme ScaleInstalling and configuring the dynamic cache provider for eXtreme Scale dependson what your requirements are and the environment you have set up.Before you beginvTo use the dynamic cache provider, WebSphere eXtreme Scale must be installedon top of the WebSphere Application Server node deployments, including thedeployment manager node. See “Installing WebSphere eXtreme Scale orWebSphere eXtreme Scale Client with WebSphere Application Server” on page174 for more information.vGlobal security must be enabled in the WebSphere Application Serveradministrative console, if the catalog servers within your catalog service domainhave Secure Sockets Layer (SSL) enabled or you want to use SSL for a catalogservice domain with SSL supported. You require SSL for a catalog server bysetting the transportType attribute toSSL-Requiredin the Server properties file.For more information about configuring global security, see Global securitysettings.About this taskFor information about using the eXtreme Scale dynamic cache provider with IBMWebSphere Commerce, see the following topics in the IBM WebSphere Commercedocumentation:vEnabling the dynamic cache service and servlet cachingvEnabling WebSphere Commerce data cacheIf you are not specifically directing your caching to a defined Object Cache orServlet Cache instance, then it is likely that the Dynamic Cache API calls are beingserviced by the baseCache. If you want to use the eXtreme Scale dynamic cacheprovider for JSP, Web services or command caching, then you must set thebaseCache instance to use the eXtreme Scale dynamic cache provider. The sameconfiguration properties are used to configure the baseCache instance. Rememberthat these configuration properties need to be set as Java Virtual Machine (JVM)custom properties. This caveat applies to any cache configuration propertydiscussed in this section except for servlet caching. To use eXtreme Scale with the
You've reached the end of your free preview.
Want to read all 568 pages?
Grid Computing, IBM Corporation, Client-server, IBM WebSphere Application Server, IBM WebSphere Application Server Community Edition