Contribute in GitHub: |

System Store

The System Store addresses the various needs of IBM® Security Verify Directory Integrator for persistent storage and by default uses the Apache Derby RDBMS (previously known as IBM Cloudscape) as its underlying storage technology.

Other relational databases, like IBM DB2®, can be used to hold the System Store. The System Store can be shared by multiple instances of IBM® Security Verify Directory Integrator servers if the Derby database runs in networked mode, or if a multiuser relational database system is used. If Derby runs embedded in an IBM® Security Verify Directory Integrator server, it cannot be shared simultaneously with other servers.

The System Store implements three types of persistent stores for IBM® Security Verify Directory Integrator components:

Each store offers its own set of features and built-in behavior, as well as a callable interface that users can access from their scripts, for example, to persist their own data and state information.

You can configure the System Store settings for a project by selecting the project in the IBM® Security Verify Directory Integrator Navigator, and select Solution Logging and Settings. Then select the System Store tab.

You can set up a JDBC Connector to directly access any of the tables in the System Store, although changing data in these tables must be avoided, as this can cause your solution to malfunction.

Attention: If you are running

Derby embedded in IBM® Security Verify Directory Integrator as opposed to running it in networked mode as a server, then be sure to Close the database again before trying to test or run your Config. Because the Config Editor starts up a separate instance of the server, running in its own JVM, the System Store is not available to this server. Closing the System Store Details window also closes your connection to the database.

Note: Although the Sandbox feature also uses the System Store technology, you specify a new database directory for each AssemblyLine.