Building A Messaging Framework Connector

After you have installed the Messaging Framework extension on your copy of Microsoft Visual Studio and you have run the TIBCO Scribe® Connector Wizard, you are ready to begin editing the sample code. The project files need to be modified to meet your needs:

To build a useful Messaging Framework Connector you must know the following: 

  • How the message is generated
  • What the message contains

Typically, there are sample messages available in a third-party API or you can create one by using the third-party application.  The sample message is used to customize the item.cs. By default you are given the following in the item.cs:

Message configuration is the key to successfully getting a Connector to process the data correctly. There are four basic message structures that can be configured in the Messaging Framework.

Two concepts to keep in mind are:

There are many variations and much complexity that can be added into the function that converts the message type into the entity to return to TIBCO Scribe®. The things to keep in mind are the type of the entire message and including any types it is composed of. The Messaging Framework uses this information to deserialize the message into an instance of that type. You must consider the type you want TIBCO Scribe® to use. It may be the same as the message type, contained within the message type of a custom type constructed from the message type. Then, you must create a function that uses C# to get from the message to the entity type, unless it is either of the first two types where the message type is what is returned.

See

Fast Connector Framework (FCF)

Complex Message Configuration Scenarios

Include Container Values In A Custom Type

Custom XML Listener