Configuring WebSphere eXtreme Scale to use your previous configuration settings

Using your previous configuration settings that you noted in the WebSphere® Application Server administration console, you must use these settings to associate either an application or an application server to WebSphere eXtreme Scale session management.

• If you want to configure an application so that it is associated with WebSphere eXtreme Scale session management, follow these steps:
  1. Start theWebSphere Application Server administrative console.
  2. In the top menu, click Applications > All applications.
  3. In theWebSphere Enterprise Applications area, select application name.
  4. In the Web Module properties area, click Session management
  5. Click eXtreme Scale session management settings.
  6. If you do not see WebSphere eXtreme Scale, then your WebSphere Application Server profile has not been augmented for WebSphere eXtreme Scale. For more information, see Creating and augmenting profiles for WebSphere eXtreme Scale.
  7. To configure an application for WebSphere eXtreme Scale in a stand-alone environment, follow these steps:
     1. In the Manage session persistence by list, select Remote eXtreme Scale data grid
     2. Select the catalog service domain you had created from the list.
     3. Click Browse to select the grid.
  8. Click Apply or OK and save the configuration.
  9. A new splicer.properties file is created for this application. The location of the splicer.properties file is the value of the a new property {application name},com.ibm.websphere.xs.sessionFilterProps. To locate the custom property, go to System administration> Cell and click Custom properties.
  10. Update the splicer.properties file with the values you obtained in Taking note of previous configuration settings in WebSphere Application Server administrative console.
  11. Restart the application server processes.

  Note: Change the splicer.properties at the Deployment Manager level so that the properties get synchronized to the node agent. If you update the splicer.properties at the node level, then the Deployment Manager will overwrite the splicer.properties file at the next synchronization.

  Note: If you go back to database session management and then return to WebSphere eXtreme Scale session management, the splicer.properties file is recreated so any changes you made will be overridden. For a discussion on the file synchronization process from the Deployment Manager to the Notes and what gets changed, see System Management File Synchronization.
• If you want to configure an application server so that it is associated with WebSphere eXtreme Scale session management, follow these steps:
  1. Start theWebSphere Application Server administrative console.
  2. In the top menu, click Servers > Server Types > WebSphere application servers.
  3. In the Application servers area, select your server name.
  4. In the Container Settings area, click Session management
  5. Click eXtreme Scale session management settings
     Note: If you do not see WebSphere eXtreme Scale, then your WebSphere Application Server profile has not been augmented for WebSphere eXtreme Scale. For more information, see Creating and augmenting profiles for WebSphere eXtreme Scale.
  6. To configure an application server for WebSphere eXtreme Scale in a stand-alone environment, follow these steps:
     1. In the Manage session persistence by list, select Remote eXtreme Scale data grid
     2. Select the catalog service domain you had created from the list.
     3. Click Browse to select the grid.
  7. Click Apply or OK and save the configuration.
  8. A new splicer.properties file is created for this application. The location of the splicer.properties file is the value of the a new property com.ibm.websphere.xs.sessionFilterProps. To locate the custom property, go to Servers > Server Types > WebSphere application servers.
  9. In the Application servers area, select your server name.
  10. In the Server Infrastructure area, select Custom properties.
  11. Update the splicer.properties file with the values you obtained in Taking note of previous configuration settings in WebSphere Application Server administrative console.
  12. Restart the application server processes.

  Note: Change the splicer.properties at the Deployment Manager level so that the properties get synchronized to the node agent. If you update the splicer.properties at the node level, then the Deployment Manager will overwrite the splicer.properties file at the next synchronization.

  Note: If you go back to database session management and then return to WebSphere eXtreme Scale session management, the splicer.properties file is recreated so any changes you made will be overridden.