Installer 10.15 | Complete Installation and Upgrade Information for Software AG Products | Installing Software AG Products On Premises | Preparing for Database Component Creation | Database Component Descriptions and Installation Requirements | Integration Server or Microservices Runtime Database Components
 
Integration Server or Microservices Runtime Database Components
 
External RDBMS versus Embedded Database
Archiving the ISCoreAudit Database Component
The table below describes the types of data Integration Server or Microservices Runtime can persist.
Database Component
Types of Data
When Data is Written
ISInternal
Service results, scheduled tasks, client certificate mappings, run-time data for pub.storage services, guaranteed delivery transactions, trigger joins, active OpenID requests, WS-ReliableMessaging runtime data, and configuration and runtime data for OAuth and Account Locking.
You are using the features listed in the Types of Data column
ISCoreAudit
*Error, guaranteed delivery, service, security, and session audit data.
The audit logger for the type of data is enabled
*Documents that are in doubt, have failed, or have exhausted trigger retries.
You are using triggers
CrossReference
Cross-referencing data for publish-and-subscribe solutions.
You are using publish-and-subscribe solutions
DocumentHistory
Document history data for exactly-once processing in publish-and-subscribe solutions. Integration Server uses the data to detect and reject duplicate documents.
You are using exactly-once processing
DistributedLocking
Information that coordinates access to resources across distributed servers and processes.
Executing services in the pub.storage folder.