Thanks for the replies,

In German-speaking countries, they always use the surname first, terribly 
polite but quite confusing when you have a first name as a surname. So please 
call me Andy. :)

The calls are pretty small, using e.g. collection membership lookups, 
add/remove to collection or add new computer to sccm and the most seem to run 
ok. The one I had a problem with was a method that looked up all coll 
memberships for a computer and had no built in timeout handling. When more 
requests ran concurrently then the timeout of the query exceeded the default 
timeout of the asp/http. We have now built in a custom timeout in the method so 
that we can handle this.

All the web methods call sdk methods.
All virtual servers.
Server generally runs well and I don't see any performance issues.
I'd said we will have a few thousand web service calls per day.

I am mitigating this perceived risk, by making sure web services run on a 
custom website and not the default website. I don't really want to have a 
separate server for everything. I have tested moving the webservices to another 
server and that works ok but then I need to run the apppool as a service 
account with admin rights on the remote smsprov. And I don't encrypt any data 
between webservice and smsprov as it was local hosted.

My impression is that using a dedicated server is heavy handed. Your answers 
are really helpful to formulate my concept and risk docs.

Thanks
Andy

Von: [email protected] [mailto:[email protected]] Im 
Auftrag von Trevor Sullivan
Gesendet: Montag, 24. Juni 2013 20:42
An: [email protected]
Betreff: RE: [mssms] ConfigMgr Web Services

Craig,

It depends on exactly what code is running inside of each of the web service 
calls. Consider these questions:


*         What functionality did you expose via the web service?

*         Are they long-running operations? Short-running operations?

*         What services does the web service method rely upon?

o   Which services hosted locally vs. remotely?

*         What kind of hardware does the server have?

*         How heavy is the current load on the server without the web service?

*         How many web service calls are being created per second?

Cheers,
Trevor Sullivan
[cid:[email protected]]<http://trevorsullivan.net/>   
[cid:[email protected]] <http://twitter.com/pcgeek86>    
[cid:[email protected]] <http://facebook.com/trevor.sullivan>     
[cid:[email protected]] 
<https://plus.google.com/106658223083457664096>

From: [email protected] [mailto:[email protected]] On 
Behalf Of Craig Andrew (OIZ)
Sent: Monday, June 24, 2013 10:25 AM
To: [email protected]
Subject: [mssms] ConfigMgr Web Services

Hi All,

Just wondering if anyone can help me out with some good practises for web 
services that supplement configMgr.
I am using web service functions more and more especially in OSD. Main points 
are whether it is sensible to use a separate dedicated server for this to avoid 
having too much http traffic on the smsprov server or if having it co-hosted 
impacts the performance either positively, negatively or not at all. I'm 
working just now on a site with around 10,000 Clients, deploying about 100 OS 
per day in rollout phase. (ConfigMgr 2012 SP1)

Any thoughts very welcome

Andy





<<inline: image001.gif>>

<<inline: image002.gif>>

<<inline: image003.gif>>

<<inline: image004.gif>>

Reply via email to