Using the Embedded Database
Integration Server and Microservices Runtime use Derby, a file-based database, as their embedded database. When you use the embedded database, Integration Server or Microservices Runtime writes IS Internal and Cross Reference data to that database, and writes IS Core Audit Log data to files.
Important:
If one database file gets corrupted, the entire database might become unusable. Software AG therefore recommends backing up the \IntegrationServer\instances\instance_name\db directory for Integration Server or the Software AG_directory \db directory for Microservices Runtime periodically so you will be able to return to the last known good state if necessary.
If you later want to write these types of data to an external RDBMS instead, you will need to create the necessary database components in the RDBMS (see
Database Component Descriptions and
Installation Requirements) and configure
Integration Server or
Microservices Runtime to write to them (see
Connecting Products to Database Components). You must also complete the steps for switching from the embedded database to an external RDBMS (see
webMethods Integration Server Administrator’s Guide).