Home

---

Start the environment At this point, you have configured the whole environment and have validated that the catalog servers and eXtreme Scale grid are working correctly. Now you need to validate that the Commerce application servers are correctly using the eXtreme Scale dynamic cache provider and validate that the whole environment works. Figure 6-5 shows an operational overview of the environment. This illustrates the components you need to start and validate. Start order: The order in which the application server components are started is important. Ensure you start the components in the following order: 1. The catalog server components; namely the deployment manager and node agent(s) 2. The eXtreme Scale application server cluster 3. The Commerce application server cluster The order is important merely because the Commerce cluster must be started before the eXtreme Scale grid, and both clusters must be started before the catalog servers. Once started, the environment is flexible concerning the starting and stopping of components. For example, the environment will be resilient if a single application server or catalog server fails. After the catalog server components (deployment manager and node agent(s)) and eXtreme Scale are started, start the Commerce application server cluster. You can verify that it is using eXtreme Scale by looking in the SystemOut.log file for the Commerce application server as shown in Example 6-12. Example 6-12 SystemOut.log showing eXtreme Scale as the Commerce dynamic cache provider [10/25/10 8:46:08:538 CDT] 00000000 CacheProvider I CWOBJ4500I: WebSphere eXtreme Scale Dynamic Cache provider is successfully initialized. [10/25/10 8:46:09:913 CDT] 00000000 ObjectGridImp I CWOBJ4700I: The map name IBM_DC_PARTITIONED_baseCache matched the regular expression of template map IBM_DC_PARTITIONED_.*. The IBM_DC_PARTITIONED_baseCache map has been created for ObjectGrid DYNACACHE_REMOTE. [10/25/10 8:46:09:991 CDT] 00000000 CacheProvider I CWOBJ4508I: The WebSphere eXtreme Scale provider has created a Dynamic Cache instance with name baseCache using topology remote.

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.