QPR Knowledge Base


Hide Navigation Pane


Previous topic Next topic No expanding text in this topic  


Previous topic Next topic JavaScript is required for expanding text Mail us feedback on this topic!  

Comments (...)

QPR Web Services Foundation requires the following configuration to run properly:


Microsoft .NET Framework 3.5 present on the machine
Application (IIS 6 or newer) or a virtual directory (IIS 5 on XP) on the web server (Microsoft IIS). The installation creates an application/virtual directory called QPR81WebServices. Note that .NET Framework 3.5 needs to be installed before the application/virtual directory is created, as otherwise it cannot bind .svc files properly. The .NET Framework is installed during the QPR 8 installation if it is not found on the machine and the QPR Web Services Foundation is selected to be installed. However, the .NET Framework installation requires an active Internet connection.
Access to QPR.WAS.Core.dll and relevant product plugins in ..\Web Application Server folder relative to the WebServices installation folder.
Rights to modify files under <path to All Users profile>\Application Data\QPR Software\QPR 8\QPR 8.1 (C:\ProgramData\QPR Software\QPR 8\QPR 8.1 in Windows Vista and later versions.)
The QPR web Services Foundation has to be running in the same domain as the client (e.g. QPR Add-In for Microsoft Office) accessing it.



Testing the Configuration


The QPR Web Services Foundation installation installs also a test utility with which you can determine that your environment is properly configured for the service. The utility is called servicetester.aspx and it is accessible in the application created for the service, i.e. http://<hostname>/QPR81WebServices/servicetester.aspx. Note that you need to have ASP.NET enabled on the web server in order to use servicetester.aspx.





By default QPR Web Services Foundation uses regular authentication by authentication methods enabled in QPR Configuration Manager. However, if you wish to use Integrated Windows Authentication (IWA), the following additional steps are needed:

Configure the virtual directory to use IWA and allow full access to MainService.svc file.
Make the following modifications to Web.config:
oUncomment "<authentication mode="Windows"/>" and comment "<authentication mode="None"/>"
oUncomment the <security mode="TransportCredentialOnly"> section and comment "<security mode="None">"



Microsoft IIS 7 Configuration


In addition to basic configuration, the following should be noted with Microsoft Internet Information Services 7:

Windows Authentication module needs to be installed for IIS. This can be done in Server Manager -> Roles -> Web Server (IIS) -> Add Role Services.
When using Integrated Windows Authentication, the QPR81WebServices application needs to have both Anonymous Authentication and Windows Authentication enabled.
IIS should be installed before installing the .NET Framework



Using SSL with QPR Web Services Foundation


To enable SSL for QPR Web Services Foundation, the following configurations should be done:

Configure the Microsoft Internet Information Services to use SSL.
Make the following modifications to the bindings in Web.config:
oIn the "<webHttpBinding>" element, comment the "<security mode="None">" and replace it with "<security mode="Transport">"
oIn the "<basicHttpBinding>" element, comment the "<security mode="None">" and replace it with "<security mode="Transport">"
oIn the "<wsHttpBinding>" element, add the following before the "</binding>" tag:

 <security mode="Transport">
 <transport clientCredentialType="None"/>

Note that using SSL for wsHttp (which is the protocol used by QPR Add-In for Microsoft Office) requires that the certificate used in SSL is issued to the same domain the web service resides in. In addition, these configurations need to be reversed in order to be able to use http connection again.




This section provides information on how to resolve common configuration issues related to running QPR Web Services Foundation.


Issue: *.svc files are not properly processed by the web server.

Solution #1: Recreate the virtual directory

Solution #2: Correct the mappings as instructed at http://msdn2.microsoft.com/en-us/library/ms752252.aspx


Issue: Servicetester.aspx doesn't work properly and log displays lots of access denied errors

Solution #1: Give the ASPNET user rights to modify files under <path to All Users profile>\Application Data\QPR Software\QPR 8\QPR 8.1 (C:\ProgramData\QPR Software\QPR 8\QPR 8.1 in Windows Vista and later versions). In Windows Server 2008, give the rights to NetworkServices user instead of ASPNET.



Additional Resources


See http://msdn2.microsoft.com/en-us/library/aa719558.aspx for more information about hosting and configuring WCF services. For additional ASP.NET configuration information, see http://msdn2.microsoft.com/en-us/library/aa719558.aspx.

Comments (...)