traceSpec A string of trace file location useful for all other application

Tracespec a string of trace file location useful for

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 = false 318 IBM WebSphere eXtreme Scale: Administration Guide April 2012
Image of page 330
Configuring the dynamic cache provider for WebSphere eXtreme Scale Installing and configuring the dynamic cache provider for eXtreme Scale depends on what your requirements are and the environment you have set up. Before you begin v To use the dynamic cache provider, WebSphere eXtreme Scale must be installed on top of the WebSphere Application Server node deployments, including the deployment manager node. See “Installing WebSphere eXtreme Scale or WebSphere eXtreme Scale Client with WebSphere Application Server” on page 174 for more information. v Global security must be enabled in the WebSphere Application Server administrative console, if the catalog servers within your catalog service domain have Secure Sockets Layer (SSL) enabled or you want to use SSL for a catalog service domain with SSL supported. You require SSL for a catalog server by setting the transportType attribute to SSL-Required in the Server properties file. For more information about configuring global security, see Global security settings. About this task For information about using the eXtreme Scale dynamic cache provider with IBM WebSphere Commerce, see the following topics in the IBM WebSphere Commerce documentation: v Enabling the dynamic cache service and servlet caching v Enabling WebSphere Commerce data cache If you are not specifically directing your caching to a defined Object Cache or Servlet Cache instance, then it is likely that the Dynamic Cache API calls are being serviced by the baseCache. If you want to use the eXtreme Scale dynamic cache provider for JSP, Web services or command caching, then you must set the baseCache instance to use the eXtreme Scale dynamic cache provider. The same configuration properties are used to configure the baseCache instance. Remember that these configuration properties need to be set as Java Virtual Machine (JVM) custom properties. This caveat applies to any cache configuration property discussed in this section except for servlet caching. To use eXtreme Scale with the
Image of page 331
Image of page 332

You've reached the end of your free preview.

Want to read all 568 pages?

  • Fall '19
  • Grid Computing, IBM Corporation, Client-server, IBM WebSphere Application Server, IBM WebSphere Application Server Community Edition

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture