Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Receive location and remote web service
- This topic has 7 replies, 1 voice, and was last updated 9 years, 10 months ago by
community-content.
-
AuthorPosts
-
-
June 30, 2008 at 4:42 AM #20017
Hi,
So far at work we have only used BizTalk receive locations with web services that have been deployed on the local server (these are web services created using the web services publishing wizard).
I have just tried pointing a receive location at an instance of its web service on a differnet IIS server and it worked.
Does anyone know if there are any downsides to using this model of a “remote” web service for the recieve location?
Cheers
Stu.
-
July 1, 2008 at 2:21 AM #20039
How about the extra license cost to install the Biztalk code on the remote server.
Having a separate deployment operation to install the remote web service
Ensuring the remote server has access to the Biztalk SQL databasesWhat is the upside
-
July 1, 2008 at 3:22 AM #20040
I’m not sure what extra license cost you mean – I was talking about one BizTalk box and one server with IIS on it (both of which exist).
Currently we have our Web Services running on IIS on the BizTalk server, and the receive locations point at the local web services.
The scenario I was curious about is one where you use a seperate IIS server to host the Web Services, and the receive locations point at these “remote” web services.
The IIS does not need access to the BizTalk SQL database, this is handled by the usual BizTalk box.
The reasons for looking at this idea are that we have received some advice from our internal security team that they would prefer a service in the DMZ not communicate directly with the BizTalk server (as they perceive this as a risk). Their suggestion was to intruduce an app server internally to act as an imtermediary between the DMZ initiated contact and the BizTalk web services.
By looking at hosting the web services on the IIS server, it may give them the separation they want without developing or deploying anything extra.
Does that make sense?
Cheers
Stu.
-
July 1, 2008 at 3:50 AM #20041
The web service published by Biztalk is a wrapper around the Microsoft.BizTalk.WebServices.ServerProxy.ServerProxy class. This object takes the received SOAP message, runs the pipeline and publishes the resulting Biztalk message into the MessageBox database. In order to move the published web service to another server you will need to install a subset of the Biztalk dlls, and add various Biztalk registry entries to config the location of the both the BiztalkMgmtDb and BiztalkMsgboxDb. The most reliable way to do this is to install Biztalk on that server – hence the license fee. Even if you manage to parse out the required dlls and config settings, I am not sure what the Microsoft view of this would be in regard to licensing. Not to mention being an unsupported configuration
You will also need to open SQL ports thru your fire wall to enable the IIS process access to these Biztalk databases. I suspect your security guys would not like this.
Alternatives:
1. Write you own web service as an intermediary
2. Use a reverse proxy e.g. ISA, Cisco Xml gateway in the DMZ-
July 1, 2008 at 4:16 AM #20042
Hi Greg,
What you say is about the web service wrapping the biztalk class and having to install the dlls and make registry entries is completely at odds with the process I have tried out here, where the IIS server used is a dedicated IIS server that has never had Biztalk installed on it.
The web service was created on my PC using the wizard (publish schemas as web services), which created the web service in inetpub.
I copied the created directory to the IIS server and added it to the default web site – this web service can now be browsed using IE.
Using Visual Studio I created a receive port and receive location on the BizTalk server, with the location using SOAP and the address settings configured to point at the IIS server and the appropriate virtual directory and asmx page.
This receive location takes the message into the message box, from which point an existing process takes over to send an email.
By using a test application, I can call the web service on the IIS server, the BizTalk receive location receives the message and the email gets sent.
There was no work needed on the IIS server beyond the copy of the directory and adding it to the default web site – how does this tie up with your thoughts on the subject?
Are you thinking of an exposed orchestration (perhaps this behaves differently?) or is there another explanation?
Cheers
Stu.
-
July 1, 2008 at 12:06 PM #20056
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?-
July 3, 2008 at 2:27 AM #20069
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.
-
July 3, 2008 at 3:00 AM #20070
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.
-
-
-
-
-
-
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.