Forum Replies Created
-
AuthorPosts
-
Thanks. Confirm: It is correct and it works.
July 4, 2008 at 11:29 AM in reply to: Error while calling web service using SOAP Adapter in BizTalk 2006 #20074At first i thought this is a too simple solution for this problem. But it’s exactly what happens when this message occurs. Try check the values in the XML source file.
I think that’s right. Here’s a trick I use to test HTTP receive locations: Open up a web browser and type this into the URL:
http://xxx.xxx.xx.xxx:5080/ABC/BTSHTTPReceive.dll?<Message>Hello!</Message>
Press Enter, and you should see a page with some XML I think containing a message ID or something. You should now see a message received into BizTalk: <Message>Hello!</Message>. I know this is XML and you are using EDI, but it should reveal whether the receive location is working. You may have a no-subscribers-found error unless something is subscribing to the send port. You may need to set up a test send port to subscribe to the receive location to get this to work.
No problem, Stu. Travelled the same path myself.
I quite like the ISA Server, which can proxy on output and reverse proxy input. You can add your own filters to increase security if you wish. http://msdn.microsoft.com/en-us/library/ms977256.aspx
On my last project project we used an ISA server so there was no direct path into the internal network, and used WS-FederatedSecurity with the WCF adapter with message level security (the only SSL was on the Security Token Service, that issued our SAML tokens)
We have a Cisco Xml Gateway on my current project, powerful device, but costs a small fortune and it is consuming the life of the guy thats implementing it.
Hi Greg – thanks for the continued input.
I have now re-visited my test and confirm that you are right – it doesn’t work [:$]
The web service (created as discussed earlier and copied to the IIS server) runs and can be browsed from PCs and servers on the network with no problems. Allowing you to look at the WSDL and browse the availble methods.
However, in my haste to re-test I had not re-pointed the test application at this url, hence making that test false.
Changing this to point at the correct url on the IIS server sees the application submit the request okay, but the receive location does not see the request, and no BizTalk process is started.
We alreday use a self authored intermediary web service for outgoing comms, so I think I’ll be looking into this or ISA for this incoming process!
Thanks for the patience.
Stu.
Yes the Authors node is correct
July 2, 2008 at 8:08 AM in reply to: Making a BT2006/R2 orch published as .asmx backward comaptible with BT2004 #20064By moving the web service files, I mean moving the whole C# solution from the old server to the new server. You will probably need to manually recreate the virtual directory in IIS on the new server. Then you can just move over the receive ports by exporting bidings.
July 2, 2008 at 7:54 AM in reply to: Making a BT2006/R2 orch published as .asmx backward comaptible with BT2004 #200631) Can you just move the web service files from the BizTalk 2004 box to the BizTalk 2006 box, instead of re-publishing it? I would try this first.
Not sure what you mean here. You mean just overlay the BT2006 WSDL with the BT2004 WSDL?
2) If there are any orchestration/port name discrepencies, it should be fairly simple to open the web service files and update the web update them with the correct names.
Ah, I keep forgetting that .asmx create a C# solution and source code (where as WCF publish does not). I’ll take a look there.
Thanks,
NealI haven’t got it right yet. Please see below whether it is what you are expecting ?
I haven’t got it right yet. Please see below whether it is what you are expecting ?
i/p
<ns0:Record>
<ns0:Title>ABC</ns0:Title>
<ns0:Author>JOHN</ns0:Author>
<ns0:ISBN>123234123123</ns0:ISBN>
<ns0:CheckOutDate>CheckOutDate_0</ns0:CheckOutDate>
</ns0:Record>
<ns0:Record>
<ns0:Title>XYZ</ns0:Title>
<ns0:Author>JOHN</ns0:Author>
<ns0:ISBN>5435345123</ns0:ISBN>
<ns0:CheckOutDate>CheckOutDate_0</ns0:CheckOutDate>
</ns0:Record>o/p expected
<ns0:Authors>
<ns0:Author name=”john” code=”code_0″>
<ns0:Author name=”Bob” code=”code_1″></ns0:Authors>
July 1, 2008 at 3:22 PM in reply to: Making a BT2006/R2 orch published as .asmx backward comaptible with BT2004 #20061If there are any orchestration/port name discrepencies, it should be fairly simple to open the web service files and update the web update them with the correct names.
July 1, 2008 at 3:18 PM in reply to: Making a BT2006/R2 orch published as .asmx backward comaptible with BT2004 #20060Can you just move the web service files from the BizTalk 2004 box to the BizTalk 2006 box, instead of re-publishing it? I would try this first.
July 1, 2008 at 3:14 PM in reply to: Making a BT2006/R2 orch published as .asmx backward comaptible with BT2004 #20059Here’s one quick clarification: otpLoanDataPull was my interanal PortName, which I can change to ImagingInterfaceLoanDataPull. But BT2006/R2 seems to prefix it with the full namespace TMAC_Adfitech etc… Is there way not to prefix it with the namespace?
Neal
Unless you’re prepared to shell out a small fortune for the Attunity adapter, I would suggest you go for the ODBC adapter. I have used it briefly with Informix and it works reasonably well.
If you go for the IBM .Net provider, I would suggest developing a custom adapter rather than invoking the provider via a helper class in an orchestration – its not best practice and can cause headaches.
Cheers, Nick.
Not sure exactly what is happening here, but check out the .asmx.cs file produced in the App-Code directory of the web service:
Should look like this:public sealed class WebService1 : Microsoft.BizTalk.WebServices.ServerProxy.ServerProxy
This won’t even compile without Biztalk being installed on the server hosting the web service.
Have you tried browsing to this web service on the IIS Server
Are you sure your test application is pointing to the right Url?Good, I’ve always had the impression that a loadbalanced configuration is whats best for us.
Since we don’t have cluster services I guess we could try to make our own watchdog etc. to switch hosts…
Thanks Greg!
-
AuthorPosts