Complete Installation and Upgrade Information for webMethods and IBO Products : Installing webMethods and Intelligent Business Operations Products : Creating and Dropping Database Components : Data Storage : Integration Server Data Storage : Embedded Database versus External RDBMS : Using the External RDBMS
Using the External RDBMS
When you use an external RDBMS, you must create the ISCoreAudit, ISInternal, and DistributedLocking database components in the RDBMS. You must create the ISInternal and DistributedLocking database components in the same schema (Oracle) or database (DB2 or SQL Server). You will also create other database components as needed. For example, if you are using publish-and-subscribe solutions and exactly-once processing, you will need the CrossReference and DocumentHistory database components; if you are running business processes, you will need the ProcessAudit and ProcessEngine database components. For complete information about the database components you will need to create, see Product Database Component Descriptions and Installation Requirements.
When you choose to use an external RDBMS, the installer asks you to supply the database connection. From this information, the installer creates a JDBC connection pool and configures Integration Server to write IS Internal, IS Core Audit Log, Cross Reference, Distributed Locking, Document History, Process Audit Log, and Process Engine data to the external RDBMS using that pool.
Note:  
This auto-configuration of Integration Server is for ease of use only. You need not create all the corresponding database components; only create those you will actually use. Also, in a production environment, you might want to create additional JDBC connection pools and reconfigure Integration Server to write different types of data using different pools. Connect Products to Database Components provides instructions.
If you are clustering Integration Servers, create an ISCoreAudit database component, an ISInternal database component, and a DistributedLocking database component in the same schema (Oracle) or database (DB2 or SQL Server) for the cluster to share. Also create a CrossReference database component and a DocumentHistory database component for the cluster to share.
If you are not clustering Integration Servers, create an ISInternal database component and a Distributed Locking database component in the same schema (Oracle) or database (DB2 or SQL Server) for all Integration Servers to share. Also create the ISCoreAudit, CrossReference, and DocumentHistory database components; you can create a single instance of each of those database components for all Integration Servers to share, or you can create a separate instance of each of those database components for each Integration Server.
Copyright © 2007-2015 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback