Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Service Development Help | Working with Document Types | Working with Publishable Document Types | About the Encoding Type for a Publishable Document Type
 
About the Encoding Type for a Publishable Document Type
 
Using Protocol Buffers as the Encoding Type
Encoding Documents as Protocol Buffers during Document Publishing
Decoding Protocol Buffers
Setting the Encoding Type for a Publishable Document Type
The encoding type indicates how Integration Server encodes and decodes published instances of the document type. For a publishable document type that uses Universal Messaging as the messaging provider, you can specify an encoding type. You can specify one of the following encoding types:
*IData, the universal container in Integration Server for sending and receiving data. When a document type uses IData as the encoding type, Integration Server encodes published instances of the document type as a serialized IData object.
*Protocol buffers, a format for serializing structured data developed by Google and implemented by Integration Server. When a document type uses protocol buffers as the encoding type, Integration Server encodes the published instances of the document type as protocol buffer.
Note:
When a publishable document type uses Broker as the messaging provider, Integration Server always encodes published documents as a Broker Event. Integration Server encodes locally published documents as IData.
The encoding type for a publishable document type also determines the scope of the message to which Universal Messaging applies a provider filter. In turn, this affects the provider filters that you can build for the webMethods Messaging Triggers that subscribe to the document type.
*When IData is the encoding type, Universal Messaging can filter on the custom header fields added via _properties only. The provider filter created by a webMethods Messaging Trigger can include _properties header fields only.
*When protocol buffers is the encoding type, Universal Messaging can filter on the body of the document only. However, when creating the published document, Integration Server includes the _properties headers in the body of the document as well. The provider filter created by a webMethods Messaging Trigger can include body and _properties header fields.
For more information about creating filters for use with Universal Messaging, see Creating a webMethods Messaging Trigger .
Note:
You can only specify an encoding type for a publishable document type in Integration Server and Designer versions 9.7 or later. Additionally, the publishable document type must use Universal Messaging version 9.7 or later as the messaging provider.