Submit Direct

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Submit Direct

Viewing 1 reply thread
  • Author
    Posts
    • November 9, 2006 at 11:22 AM #16380
      community-content

        I have been looking at direct-binding for the operational aspect of a project.  This would allow easier manipulation of initiating function.

        The 'out of process' submitDirect sample is interesting in this regard as it would be more easily integrated into existing processes.  Has anyone figured out how to direct this to a specific, read remote, bts system?  The IBTTransportProxy does not appear to have any remoting or connectionstring properties and I cannot see how to get there from the ExplorerOM  which does take a ConnectionString.

        Doug

      • November 9, 2006 at 6:31 PM #16383
        community-content

          The ExplorerOM classes are used for admin only.

          Using IBTTransportProxy remotely would defeat the loosely coupled nature of Biztalk.

          How about using the SOAP adapter or soon the WCF adapter

          What is that you are trying to do?.

          • November 10, 2006 at 9:37 AM #16386
            community-content

              I am looking at options for integrating BTS into our product line with minimal additional configuration issue.

              It woudl be handy to be able to use a connection string similar to that for SQL to be the target of a message.  Yes, very similar to a SOAP adapter but less setup on the BTS server.  There are lots of ways to do this and I am still trying to figure out the impact of each.

              Doug

               

              • November 12, 2006 at 3:14 PM #16395
                community-content

                  from your previous reply   "integrating BTS into our product line"

                  Are you trying to create a mechanism for users of your product to integrate using Biztalk.

                  One issue is the messaging transport. Receive adapters come in two types – polling and callable.
                  The SQL Server is a polling adapter while the SOAP adapter is called from an external entity

                  It sounds like you wish your product to be the initiator of messages.

                  So you need a mechanism that will import metadata and generate a callable endpoint.

                  One possibility is an application specific adapter. Much like the Oracle/JDEdwards/etc adapters.
                  These adapters allow you to import metadata from the application that defines the messages (creates the Xml schema) and also have a runtime component that handles your own custom messaging transport.

                  Another possibility is a custom wizard like the Web Services publishing wizard that could import the metadata from your product, and create a callable endpoint like a web service, MSMQ or similar.

                  • November 13, 2006 at 8:38 AM #16402
                    community-content

                      Yes, I am willing to accept the preferred method will be web services.  Part of our internal development will be how the schema is controlled, ie whether the generator or consumer will define the schemas.  I am not seeing the need for a vendor-specific transport mechanisms at this time.

                      thanks

                       

            • Author
              Posts
            Viewing 1 reply thread
            • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.