How can I install a Web Service ?

[anyweb]

In this example we will install Maik Kosters excellent web services (7.2) on our SCCM server (which is already running IIS).

 

 

Installing the Web Service

 

Step 1. Download the files from this codeplex site

 

Step 2. Extract the content of the zip file into a folder on your Webserver

 

 

Step 3. Copy the contents to your webserver root, rename the folder to something like NEWWebservice

 

 

Step 4. Add the folder as a new Application to IIS (Step by Step Guide IIS 6 | Step by Step Guide IIS 7), Start IIS manager, expand Sites, right click on Default Web Site and choose Add Application.

 

 

Step 5. Specify an "Alias" (the name you would like to use to access the Webservice, lets call it NewWebService) and the physical path to the extracted content of the webservice eg: c:\inetpub\wwwroot\NEWWebService

 

 

At this point the webservice is accesible (in internet explorer http://sccm/newwebservice/sccm.asmx ) but you cannot do anything with it (as it doesn’t know how to communicate with your SCCM site…) until you’ve done some final configuration…

[anyweb]

Step 6. Refresh Default Web Site

 

Right click on Default Web Site, click Refresh (if you don’t do this the New web Service will still appear as a folder in IIS instead of as an Application.

 

 

Step 7. Add Application Pool

 

In IIS Manager, locate Application Pools, right click and choose Add Application Pool,

 

 

give it a name such as New Web Service and click ok

 

 

Step 8. Configure Application Pool

 

Now you can configure this Application Pool to use a Different User Account for running your Webservice. To do this Open IIS Manager, expand your Webserver Node and click on Application Pools. Right click your Application Pool on the right side and choose Advanced Settings... In the Process Model area click in the Identity field and then click on the ... Button

 

 

Choose Custom account and click on Set...

 

 

 

Step 9. Configure the Webservice to use the application Pool

 

Open IIS Manager, expand your Webserver node and Sites node, expand your Default Web Site node, Right click on the NewWebService folder and choose Manage Application - Advanced Settings...

 

 

In the General area click into the Application Pool field and then click on the ... Button

 

 

choose the appropiate Application Pool (called New Web Service) click OK, OK

 

[anyweb]

Step 10. Configure Application Settings

Next we need to configure the application settings (Step by Step Guide) , failure to do so will mean the webservice cannot do anything.

Open IIS Manager, expand the Webserver Node, expand the Sites Node, expand your Default Web Site, click on the Deployment Webservice Folder/Application (NewWebService) and then double click on the Application Settings Icon on the right side.



And enter the appropriate details…



The following are configurable:-

By default, the webservice will use the configured application pool user for authentication. It requires only a couple of Application Settings to be set:

RootServer - The SCCM Root Server
SLPServer - One SCCM Server with the SLP Role
RootSiteCode - The Root site code

For Access to the MDT Database you need to configure at least

MDTDBServer - The MDT Database server (with Instance if necessary)
MDTDBName - The MDT Database name
MDTDBIntegratedSecurity - Set to "True" if you want to use the application pool account for authentication. If set to "False" you need to supply the following two settings
MDTDBUser - Username to access the MDT Database
MDTDBPassword - Password to access the MDT Database

For Active Directory access, you can optionally configure the following Application Settings. This is only necessary, if the application pool user account does not have enough permissions to do execute the required functions, and/or if you need to access a different domain as the application pool User is member of:

ADDomain - Domain to query (use either "domain.com" or "DC=Domain,DC=COM" format)
ADUsername - Username for authentication
ADPassword - Password for authentication

You will note i didn't configure any of the MDTDB settings as I'm not using them currently in my environment.



Step 11. Test the New Web Service

You should now be able to use the Webservice. To test the functionality just open your favourite Browser and point it to

http://sccm/NewWebService/ad.asmx- For Active Directory related functions
http://sccm/NewWebService/mdt.asmx- For MDT related functions
http://sccm/NewWebService/sccm.asmx- for SCCM related functions.

 

Troubleshooting

 

To troubleshoot when things are not working, browse to the LOGS folder of where you installed the Web Service, and you should see Trace, Debug and Info logs, open them in CMTrace to review.

[wmmayms]

What permissions did you assign to your Application Pool identity? WMI permissions?

 

When i did the installation I had to use local system account to be able to make queries.

[ogeccut]

How come on the step 10 i do not have "Application Settings"

 

Is there a way for me to insert an image here?

[anyweb]

are you clicking on NewWebservice in IIS ? yes you can post images here using the Image icon when you post

[ogeccut]

Yes, i think i have everything correct. I have been trying for a while and always got stock at this step.

When i try to post a pic, i need to point to URL? sorry for the questions, but dont know where/how i can upload a pic.

[ogeccut]

One more try.

I have an image here "https://picasaweb.google.com/113087378504038044691/September14201102#5652292298134978066"

for some reason not able to post this link.

[ogeccut]

I tried installing and configuring webservice one more time with the same result.

What am i missing?

 

Thanks for the help....

https://picasaweb.google.com/113087378504038044691/September14201102#5652292298134978066

[ogeccut]

I dont see ASP.NET view....and not sure where to change this setting????

[ogeccut]

I got it. Sorry for multiple post. If anyone else is havign same issue here is the fix:

If you don't see the expected version of ASP.NET listed under "Web Service Extensions", it's typically because IIS was installed after .NET. You can run the aspnet_regiis.exe utility to remedy this:

• 
  Get to a command prompt, e.g. Start>Run "cmd".
  
• 
  Enter "CD /D C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322" or "CD /D C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727" depending on which version of ASP.NET.
  
• 
  Enter "aspnet_regiis.exe -i".
  
• 
  Wait for the finished message; "Start installing ASP.NET (1.1.4322.0)" or "Start installing ASP.NET (2.0.50727.0)" depending on which version of ASP.NET.
  
• 
  Follow the previous set of steps to enabled ASP.NET in Web Service Extensions.