After you set up database persistence in your production topology, you must restart the
runtime servers and then run the finalize command.
Before you begin
Decision Server
Insights caches system data in-memory
by default, and does not write to persistent storage. To enable database persistence, you must
complete the configuration of a supported database, a JDBC data source, and the object grid. For
more information, see
Configuring system data
persistence.
About this task
To change the data source configuration of a runtime server, you must stop it, change the
configuration and restart it. You do not need to stop the entire grid if you change a single data
source parameter, such as the connection pool. However, you do need to stop the cluster if you want
to change the location of the data.
You must run the finalize command to enable the persistence change in either
of the following cases:
- You change the default in-memory cache to a database persistence.
- You change the persisted database.
Procedure
- Stop the cluster. You must stop the cluster before you add a data source or change the location of the stored
data. For more information, see Creating,
starting, and stopping servers.
Warning: If you do not stop the cluster before you change the configuration files,
events might not be processed and schedules might be lost.
- Edit the server.xml file of each runtime server to enable persistence or
update the data source configuration.
- Run the server start server_name command
from the <InstallDir>/runtime/wlp/bin directory. After the server restarts, the Insight Server is
in a state of PRELOAD.
- Run the dataLoadManager finalize command. The finalize command activates the
system so that processing can resume with persistence enabled.