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.
About this task
The steps in this procedure are for Version 8.5 of the
WebSphere Application Server administrative console.
This information may vary slightly depending on the version of
WebSphere Application Server you are using.
Note: WebSphere eXtreme Scale Client Version 8.6 is not supported on versions of WebSphere Application Server prior to Version 7.0.
Procedure
- If you want to configure an application so that it is associated
with WebSphere eXtreme Scale session management,
follow these steps:
- Start theWebSphere Application Server administrative
console.
- In the top menu, click Applications > All applications.
- In theWebSphere Enterprise Applications area, select application name.
- In the Web Module properties area, click Session management
- Click eXtreme Scale session management settings.
- 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 .
- To configure an application for WebSphere eXtreme Scale Client, follow these steps:
- In the Manage session persistence by list,
select IBM WebSphere DataPower XC10 Appliance
- Specify the IP or host name of the catalog service domain you
had created from the list.
- Specify a user name and password and test the connection.
- Specify a new data grid or select an existing one.
- Click Apply or OK and save the configuration.
- 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.
- Update the splicer.properties file with the
values you obtained in Taking note of previous configuration settings in WebSphere Application Server administrative console.
- 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:
- Start theWebSphere Application Server administrative
console.
- In the top menu, click Servers > Server Types > WebSphere
application servers.
- In the Application servers area, select your server name.
- In the Container Settings area, click Session management
- 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 .
- To configure an application for WebSphere eXtreme Scale Client, follow these steps:
- In the Manage session persistence by list,
select IBM WebSphere DataPower XC10 Appliance
- Specify the IP or host name of the catalog service domain you
had created from the list.
- Specify a user name and password and test the connection.
- Specify a new data grid or select an existing one.
- Click Apply or OK and save the configuration.
- 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.
- In the Application servers area, select your server name.
- In the Server Infrastructure area, select Custom properties.
- Update the splicer.properties file with the
values you obtained in Taking note of previous configuration settings in WebSphere Application Server administrative console.
- 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.
Results
You have now changed your previous configuration settings
for either a memory-to-memory or database session management with
WebSphere eXtreme Scale session management.