Forum Replies Created
-
AuthorPosts
-
December 3, 2009 at 2:22 AM in reply to: Publishing webservice with callback (or other way to do an asynchronous service) #23842
Sorry I posted this in the wrong subforum. It should be in BT 2006, not R2 as I have posted.
BR
Johan
December 3, 2009 at 2:02 AM in reply to: how to debug orchestration using health and activity tracking? #23840Put a break Point in the Orchestration Instance
process the message
Right click the orchestration instance
open orchestration debugger
do attach from the top debug menu
control comes to the break point
you can view the messages and other variables in variable window
press continue to go to the next break point
Hi Siva,
You cannot expose an Orchestration as an ASP page, that is technically not possible. You can only expose it as an XML web service with an ASMX endpoint or as a WCF service in BizTalk 2006 R2 version. I suggest you expose it as a WCF service for forward compatibility and in your ASP page, use Javascript code to make a call to the XML HTTP Request object to consume that service.
Daniel.
Thanks Man for yours answers,….
The Objetive is to Catch the Exception that occurs inside EDI Disassembler into Pipeline. And Save the Error into Event Log with the format some like this
<Log> <Message>original txt Edi Message<Message> <ErrorDescription>Error Description</ErrorDescription> </Log>
The EDITxtMessage comes from a IBM MQ Series.
Already I subscribed and Orch direct to the MessageBox that pick up suspended message from the receive port. Until this time I have access to Error and Original XML EDI Message but still I need the TXT, so I created a component (already tested with values from DB) to access the BD to get it…
The issue is that I dont know what is the right Message Property to send to my component to pick up this txt… I tried with BTS.MessageID but doesnt work…anyone knows what it is?
In FTP Receive adapter you have to specify Temp folder. The FTP file will be transfer to temp folder, once it is completed it will be copied to your target FTP received folder.
When completed the file in Temp and target folder will be removed.
This error is generated from the SQL adapter, it means it is getting a dataset response instead of Xml.
Had this exact problem yesterday, someone had “temporarily” commented out the FOR XML in the stored procedure so they could view the result in tabular format. They forgot to remove the comment and reinstate the FOR XML.
Greg – thanks for your help – it is very much appreciated….
As it turned out, the access denied errors were for the registry keys indicated in the initial posting. However, these were not being seen in RegMon because the wrong process was being monitored. The correct process was w3wp.exe, which I understand to be for the application pool.
In addition, granting access to the registry keys did not resolve the problem. This did resolve the messages in the Application log however.
The real problem, which I did not clearly state was that no data was being moved from the BizTalkMessageBoxDb to the BAMPrimaryImport database. I incorrectly assumed that access to the registy was the problem, but it was not. We were able to figure out that the probelm was configuration related.
We needed to create a w3wp.exe.config file. This file contains configuration information for .Net applications running in an application pool. Placing the following text into this file resolved the issue and data is now flowing into BAMPrimaryImport as expected:
<appSettings>
<!– These settings must be made available to the BizTalkRuntime. –>
<!– This can be accomplished in two ways: –>
<!– 1. Add the contents of this appSettings node to %SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\config\machine.config –>
<!– 2. Add the contents of this appSettings node to: –>
<!– A. %SYSTEMROOT%\system32\inetsrv\w3wp.exe.config –>
<!– B. %PROGRAMFILES%\Microsoft BizTalk Server 2006\BTSNTSVC.EXE.config –>
<!– Note: If a config file does not have a appSettings node, add one. –>
<!– Otherwise, add the contents of this appSettings node to the existing appSettings node –>
<!– This connection string is used by the BAM Observers –>
<!– It MUST point to the BAM Primary Import Database –>
<add key=”BAMDatabaseConnectionString” value=”Server=<SERVERNAME\INSTANC-ENAME>;Database=BAMPrimaryImport;Trusted_Connection=True;” />
<!– These keys enable the eHub BAM Observers –>
<!– Notice that the value of these keys reference the strong name of each observer. –>
<!– The strong name includes the observer assembly version number. –>
<!– These strong names/version numbers must be adjusted in accordance with changes made to eHub’s code base (new version numbers) –>
<add key=”eHubObserver01″ value=”eHub.Hub.ObservationModel.ReceivePublicationMessageBAMObserver, eHub.Hub.ObservationModel, Version=3.2.0.0, Culture=Neutral, PublicKeyToken=95e40461a5ba22b5″ />
<add key=”eHubObserver02″ value=”eHub.Hub.ObservationModel.ReceiveSubscriptionResponseBAMObserver, eHub.Hub.ObservationModel, Version=3.2.0.0, Culture=Neutral, PublicKeyToken=95e40461a5ba22b5″ />
<add key=”eHubObserver03″ value=”eHub.Hub.ObservationModel.SendPublicationResponseBAMObserver, eHub.Hub.ObservationModel, Version=3.2.0.0, Culture=Neutral, PublicKeyToken=95e40461a5ba22b5″ />
<add key=”eHubObserver04″ value=”eHub.Hub.ObservationModel.SendSubscriptionMessageBAMObserver, eHub.Hub.ObservationModel, Version=3.2.0.0, Culture=Neutral, PublicKeyToken=95e40461a5ba22b5″ />
<add key=”eHubObserver05″ value=”eHub.Hub.ObservationModel.ErrorProcessingBAMObserver, eHub.Hub.ObservationModel, Version=3.2.0.0, Culture=Neutral, PublicKeyToken=95e40461a5ba22b5″ />
</appSettings>
Thank you Greg,
So I guess I have to write an asp page to post message on HTTP Receive port or directly to orchestration soft-receive port. Is it possible to directly post to orchestration from asp page? In this case, i dont need to use BTSHTTPReceive.dll.
No, The BTSHTTPReceive.dll is an ISAPI extension. You might be able to change it name and reregister it, but you cannot use a .asp file suffix as this would clash with any asp.net applications
I would go use a SOAP/HTTP interface – use the SOAP or preferably the WCF adapter on BizTalk and the equivalent on JCAPS.
The WCF adapter supports most of the WS-* protocols. Also using an open standard puts you on the high moral ground with both teams
lol 🙂 – thx greg – probably both, (if you knew of a connector to get the teams working together that would be brilliant !!) but more importantly can the products work together ? – I think you may have answered this as Yes – but if you have any more thoughts please let me know…Thx..
Both JCaps and BizTalk are integration platforms for connecting various disparate applications. Both come with a range of connector technologies to accomplish this. There is considerable overlap in these connector technologies, so there should be no technical reason preventing integration.
The best option would probably be an open standard interface like Web Services (SOAP or REST).“we really want to know if they can integrate and work together..” – are you talking about the products or the teams?
Is your tracking host running?
Jack,
Same problem what components were out of date?
-
AuthorPosts