Taking note of previous configuration settings in WebSphere Application Server administrative console

As part of migration to a WebSphere® eXtreme Scale session, you should take note of your previous configuration settings in WebSphere Application Server administrative console. When migrating to a WebSphere eXtreme Scale session, the configuration settings have to reflect what you already had configured for your database or memory-to-memory session.

1. Start theWebSphere Application Server administrative console.
   • If you have previously configured settings at the server level, then go to:
     1. Servers > Server Types > WebSphere application servers
     2. In the Application servers area, select your server name
     3. In the Container Settings area, click Session management
   • If you have previously configured settings at the application level, then go to:
     1. Applications > All applications.
     2. In the Application servers area, select your application name.
     3. In the Web Module Properties area, click Session management
2. In the General Properties, select the Allow Overflow check box.
3. In the General Properties area, take note of the WebSphere Application Server settings.
   You will need these values later to update the properties in the splicer.properties file.

   Table 1. Configuration settings to update the splicer.properties file

   Settings in the WebSphere Application Server administration console	Properties to update in the splicer.properties file
   Enable cookies	useCookies
   Enable URL rewriting	useURLEncoding
   Maximum in-memory session count	sessionTableSize

4. In the General Properties area, if the Enable cookies check box is selected, then click it and take note of the WebSphere Application Server settings.
   You will need these values later to update the properties in the splicer.properties file.

   Table 2. Configuration settings for the properties in the splicer.properties file

   Settings in the WebSphere Application Server administration console	Properties to update in the splicer.properties file
   Cookie domain	cookieDomain
   Cookie path	cookiePath

5. Click Session management and in the Additional Properties area, click Distributed environment settings.
6. In the Distributed Sessions area, change your previous database or memory-to-memory replication configuration to None.
7. Click Custom Tuning Properties and take note of the WebSphere Application Server settings.
   You will need these values later to update the properties in the splicer.properties file

   Table 3. Configuration settings for the properties in the splicer.properties file

   Settings in the WebSphere Application Server administration console	Properties to update in the splicer.properties file
   Write frequency	replicationInterval
   Write contents	fragmentedSession