A publishable document type is an IS document type with specified publication properties such as storage type, time-to-live, and a message connection alias. In an integration solution that uses the publish-and-subscribe model, services publish instances of publishable document types, and triggers subscribe to publishable document types. A trigger specifies a service that the Integration Server invokes to process the document.

For example, you might create a publishable document type named EmpRec that describes the layout of an employee record. You might create a trigger that specifies that Integration Server should invoke the addEmployeeRecord service when instances of the EmpRec are received. When a service or adapter notification publishes a document of type EmpRec, that document would be queued for the subscribers of document type EmpRec. Integration Server would pass the document to the subscribing trigger and invoke the addEmployeeRecord service.

In a business process, a published document can start or join a process.

In a publication environment that includes Broker or Universal Messaging, each publishable document type is associated with a messaging provider. You create an association between a publishable document type and messaging provider by assigning a messaging connection alias to the document type. A messaging connection alias specifies the configuration information necessary to create a connection to the messaging provider. The messaging connection alias assigned to a publishable document type determines the messaging provider that will receive and route published documents

The messaging connection alias is used by:

Once you assign a messaging connection alias to a publishable document type, the messaging provider creates a provider definition, that corresponds to the publishable document type. On Broker, the corresponding provider definition is a Broker document type. On Universal Messaging, the corresponding provider definition is a channel. A publishable document type and its corresponding provider definition must remain in sync. Designer provides tools that you can use to synchronize a publishable document type with its provider definition.

If the publishable document type uses Universal Messaging as the messaging provider, you can specify an encoding type of IData or protocol buffers for instances of the publishable document type. Integration Server uses the encoding type to serialize and deserialize published and received documents. The encoding type you select determines the filtering that the Universal Messaging can preform prior to enqueuing a message for subscribers. For more information, see About the Encoding Type for a Publishable Document Type.

When you build an integration solution that uses publication and subscription, you need to create the publishable document types before you create triggers, services that process documents, and services that publish documents.