TIBCO Adapter for COM can be used as a bridge between the TIBCO messaging infrastructure and Microsoft's BizTalk Server. TIBCO messages can flow from the TIBCO messaging transport to BizTalk, and BizTalk messages can flow from BizTalk to the TIBCO messaging transport.
This example is developed to work with Microsoft BizTalk Server 2000 and Microsoft Windows 2000. If you want to run this example using Microsoft BizTalk Server 2004, you will have to write a custom component that will help Microsoft BizTalk Server 2004 interface with the adapter.
To illustrate this functionality, this section provides a simple example of a BizTalk schedule that receives messages from the TIBCO messaging transport and republishes them to the TIBCO messaging transport on a different subject.
![]() |
To keep it simple, the interface/message format for both incoming and outgoing messages are the same, although they can be different.
|
In this example, you will create a TIBCO Adapter for COM interface that defines the format of messages and then set configuration parameters in BizTalk Orchestration Designer and TIBCO Designer.
The tasks are:
Comp
with an interface, IComp
, that satisfies the following IDL:< uuid(44EC00B5-5786-40AB-A26F-6ACAE1EC09B7), version(1.0), helpstring("QComp 1.0 Type Library") > library QCOMPLib { importlib("stdole2.tlb"); interface IComp; < uuid(90C89293-9CE6-44BA-AC1D-8977FB6C4618), helpstring("Comp Class") > coclass Comp { <default> interface IComp; }; < odl, uuid(B72F57AD-9358-404E-BFC6-19EF1EF0818D), helpstring("IComp Interface"), dual, oleautomation > interface IComp : IDispatch { <id(0x00000001), helpstring("method M1")> HRESULT M1( <in> unsigned char vui1, <in> short vi2, <in> unsigned short vui2, <in> long vi4, <in> unsigned long vui4, <in> int vint, <in> unsigned int vuint, <in> VARIANT_BOOL vboolean, <in> single vr4, <in> double vr8, <in> CURRENCY vfixed, <in> DATE vdateTime, <in> BSTR vstring); }; };
To allow messages to pass from the TIBCO messaging transport to BizTalk, you must create an incoming COM component port in BizTalk and then configure the service component of the adapter to write messages into the port.
monikerDisplayName
(case sensitive) with the appropriate value for the BizTalk sked moniker, then click Apply. The syntax for the BizTalk sked moniker is:
monikerDisplayName=sked://
<hostname><!groupmanager>/
<filepath>/
<portname>
For example, in the screen above, the following string extended property was added:
monikerDisplayName=sked:///C:\Program Files\Microsoft BizTalk Server\Tutorial\Schedule\Lab\Buyer1.skx/Port_1
Here filepath is the path to the BizTalk .skx
file that contains the compiled BizTalk schedule, and portname is the name of the incoming port in that schedule. When the service component of the adapter starts, it will use the sked moniker to create a COM interface. Then, when the service component makes a call through a method on that interface, BizTalk will intercept the call, transform the data passed as parameters into a BizTalk message, and hand the message over to the incoming port.
To allow BizTalk messages to pass to TIBCO messaging transport, you must create an outgoing COM component port in BizTalk.
The type information from the parameters of the method is used to define the message format. The Action shape is now connected to the outgoing port.
![]() |
Microsoft BizTalk server 2004(beta) does not support a port implementation directly using a COM component. Therefore, the section on Creating an incoming "COM component" port in BizTalk for passing messages to Microsoft BizTalk is not applicable for the BizTalk Server 2004 (beta) release. Due to this limitation, the adapter cannot directly talk to the BizTalk Server 2004 (beta) release.
|
TIBCO Adapter™ for COM User’s Guide Software Release 5.3, September 2005 Copyright © TIBCO Software Inc. All rights reserved www.tibco.com |