You can configure a Derby event database at the server or cluster scope on a Linux®, UNIX®, or Windows® system.
There are two types of Derby databases that you can use for the event database: Derby Embedded and Derby Network. Both types are shipped with WebSphere® Application Server, but they have limited functionality that is not suitable for a production environment. You should, therefore, use Derby as the event database only for purposes such as development or testing. For more information on the Derby databases, see the WebSphere Application Server documentation (linked to at the bottom of this page).
Derby Embedded can only be used with a stand-alone server. Consequently, if you ever federate your stand-alone server to a cluster or ND environment, then you will need to completely re-configure your event data source with another database product. It will automatically start when you start the server.
Derby Network can be used in a clustered or ND environment, although it should still be avoided in use with actual production systems. You need to manually start the database to use it with the server.
To configure a Derby event database:
The administrative command creates the required data source at the specified scope; if you specified true for the createDB parameter, the command also runs the generated database configuration script to create the database.
The generated database configuration scripts are stored by default in the profile_root/databases/event/node/server/dbscripts/derby directory. (In a Network Deployment environment, these scripts are stored under the deployment manager profile directory.) If you specified a value for the optional outputScriptDir parameter, the scripts are stored in that location instead. You can use these scripts to manually configure the event database at any time.