Configuration

The majority of the configuration for Platform's Message Queueing system is stored in the same Oracle database as the rest of your business models. The following outlines where each configuration lives:

• The following data and metadata related to Messages are stored in Oracle database tables as regular Platform Models.

  • All Message information except the payload (the actual content of the message is stored on a shared file system)

  • MessageQueue definitions (including queue name, owning enterprise if relevant, whether paused, etc.)

  • MessageSources and MessageSourcePolls, describing where to go to fetch files to be enqueued into MessageQueues, and how often to do so

  • MessageRoutes and MessageDestinations, describing where to route outbound Messages

  • MessageTransforms, describing transformations to be invoked when enqueuing/dequeuing

  • MessageQueueDependencies, describing relationships between queues

• To reduce the I/O load on the relational database, the payloads for Messages are stored in a separate MessageStorageService, which is typically bound to a shared filesystem. It is expected to have backup/failover characteristics similar to the database. All nodes in a platform instance must share the same MessageStorageService.

• Inbound & Outbound Interface definitions are provided in Process Types, whether at the MPT, SPT, or EPT level.

• Each node in a cluster of Platform servers may configure whether it participates in the dequeuing of messages. Furthermore, it can optionally narrow this to specific Queues it wants to dequeue, and how many threads for each. This is done in dvce-app-config.xml