By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,424 Members | 1,375 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,424 IT Pros & Developers. It's quick & easy.

Hardware to web service

P: n/a
I'm developing a piece of Hardware that I wish to have utilize a web service
on a Windows 2003 server. I send an XML file to the server over port 80 but,
it doesn't work. Whatis required to make this connection?
Jun 27 '08 #1
Share this Question
Share on Google+
5 Replies


P: n/a
On Jun 26, 10:27*am, "Dave" <D...@newsgroup.nospamwrote:
I'm developing a piece of Hardware that I wish to have utilize a web service
on a Windows 2003 server. I send an XML file to the server over port 80 but,
it doesn't work. Whatis required to make this connection?
hardware?

you need to be more especific
Jun 27 '08 #2

P: n/a
Let me tell what does work and maybe that will explain it. I wrote a program
that runs on a windows xp computer and it transmits over the internet to a
web service on the server. This works fine. I want to replace the client
computer with an embeded controller. I have the controler send the xml file
the web service is expecting. I have verfied that it is sending the XML file
correctly . The hardware device connects by way of a socket over the
internet. This is not working, I assume because of some comunication is
going on between the orignal app and the web service that I'm not expecting.
Does a web service just receive an XML file?
"Ignacio Machin ( .NET/ C# MVP )" <ig************@gmail.comwrote in
message
news:58**********************************@i36g2000 prf.googlegroups.com...
On Jun 26, 10:27 am, "Dave" <D...@newsgroup.nospamwrote:
I'm developing a piece of Hardware that I wish to have utilize a web
service
on a Windows 2003 server. I send an XML file to the server over port 80
but,
it doesn't work. Whatis required to make this connection?
hardware?

you need to be more especific
Jun 27 '08 #3

P: n/a
Hi Dave,

As for webservice itself, it is rely on XML SOAP message transfering over
http protocol(most cases), and since http is simply over Tcp, you can
surely send webservice request via raw TCP socket programming. IMO, as
long as the network connection is correct, the most important part is the
XML data(in http request) you send, matches the data/request format the
webservice server-side expect.

So currently, for your scenario, would you let me know the following things:

1. What's your client-side (tcp socket ...)'s programming language?

2. What's the server-side webservice's programming platform and what's the
webserver(IIS or other..). Also, how the webservice is deployed also
matters, for example whether the services has turn on some authentication
...

For general troubleshooting (when you send webservice via one client work
while anothe not work), you can use some network trace tool(tcp or http
trace) to capture the request content (sent by the different client) and
compare the content (message header and body) to see whether there is any
difference.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: "Dave" <DW**@newsgroup.nospam>
References: <uA**************@TK2MSFTNGP04.phx.gbl>
<58**********************************@i36g2000prf. googlegroups.com>
>Subject: Re: Hardware to web service
Date: Thu, 26 Jun 2008 16:11:09 -0400
>

"Ignacio Machin ( .NET/ C# MVP )" <ig************@gmail.comwrote in
message
news:58**********************************@i36g200 0prf.googlegroups.com...
On Jun 26, 10:27 am, "Dave" <D...@newsgroup.nospamwrote:
>I'm developing a piece of Hardware that I wish to have utilize a web
service
on a Windows 2003 server. I send an XML file to the server over port 80
but,
it doesn't work. Whatis required to make this connection?

hardware?

you need to be more especific
Jun 27 '08 #4

P: n/a
I used a sniffer to see what the difference was. The computer running from
the computer, c# program, POST to the web service. EX. POST address\webapp
(192.168.1.1\sitetemp)

Where address if the address of the web server, and web app is the relative
path and name of the app.

The hardware device just setup a socket to a web address. You can't specifiy
a relative path or the web app name. That was the problem.
"Steven Cheng [MSFT]" <st*****@online.microsoft.comwrote in message
news:Oc**************@TK2MSFTNGHUB02.phx.gbl...
Hi Dave,

As for webservice itself, it is rely on XML SOAP message transfering over
http protocol(most cases), and since http is simply over Tcp, you can
surely send webservice request via raw TCP socket programming. IMO, as
long as the network connection is correct, the most important part is the
XML data(in http request) you send, matches the data/request format the
webservice server-side expect.

So currently, for your scenario, would you let me know the following
things:

1. What's your client-side (tcp socket ...)'s programming language?

2. What's the server-side webservice's programming platform and what's the
webserver(IIS or other..). Also, how the webservice is deployed also
matters, for example whether the services has turn on some authentication
..

For general troubleshooting (when you send webservice via one client work
while anothe not work), you can use some network trace tool(tcp or http
trace) to capture the request content (sent by the different client) and
compare the content (message header and body) to see whether there is any
difference.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
>>From: "Dave" <DW**@newsgroup.nospam>
References: <uA**************@TK2MSFTNGP04.phx.gbl>
<58**********************************@i36g2000prf. googlegroups.com>
>>Subject: Re: Hardware to web service
Date: Thu, 26 Jun 2008 16:11:09 -0400
>>

"Ignacio Machin ( .NET/ C# MVP )" <ig************@gmail.comwrote in
message
news:58**********************************@i36g20 00prf.googlegroups.com...
On Jun 26, 10:27 am, "Dave" <D...@newsgroup.nospamwrote:
>>I'm developing a piece of Hardware that I wish to have utilize a web
service
on a Windows 2003 server. I send an XML file to the server over port 80
but,
it doesn't work. Whatis required to make this connection?

hardware?

you need to be more especific

Jun 27 '08 #5

P: n/a
Thanks for your reply Dave,

If the hardware side is really restricted and have limited programming
interface, would you consider some changes at the webservice side? Is the
service side controllable by you? If so, you can change it to a simple http
handler which just expect some simple http post message or even just use a
Tcp server ? Actually, for your scenario, I don't think the webservice/SOAP
(xml based structure is necessary) as you just need to do some
communication or send some command text, correct?

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: "Dave" <DW**@newsgroup.nospam>
References: <uA**************@TK2MSFTNGP04.phx.gbl>
<58**********************************@i36g2000prf. googlegroups.com>
<e0*************@TK2MSFTNGP06.phx.gbl>
<Oc**************@TK2MSFTNGHUB02.phx.gbl>
>Subject: Re: Hardware to web service
Date: Fri, 27 Jun 2008 16:58:47 -0400
>
I used a sniffer to see what the difference was. The computer running from
the computer, c# program, POST to the web service. EX. POST address\webapp
(192.168.1.1\sitetemp)

Where address if the address of the web server, and web app is the
relative
>path and name of the app.

The hardware device just setup a socket to a web address. You can't
specifiy
>a relative path or the web app name. That was the problem.
"Steven Cheng [MSFT]" <st*****@online.microsoft.comwrote in message
news:Oc**************@TK2MSFTNGHUB02.phx.gbl...
>Hi Dave,

As for webservice itself, it is rely on XML SOAP message transfering over
http protocol(most cases), and since http is simply over Tcp, you can
surely send webservice request via raw TCP socket programming. IMO, as
long as the network connection is correct, the most important part is the
XML data(in http request) you send, matches the data/request format the
webservice server-side expect.

So currently, for your scenario, would you let me know the following
Jun 30 '08 #6

This discussion thread is closed

Replies have been disabled for this discussion.