Click here to ask a question or provide feedback on this topic Bookmark this topic Print this topic    Previous Next

WebService Wizard - Step 1

The "IntraWeb Studio WebService Regitration Wizard" gets started during the server setup and can also be run later by manually selecting it from the start menu. Usually this wizard needs to run only once. It will create a new WebService entry where the IWS clients will connect to. If there should be IWS server updates, then this wizard does not need to be run again - the WebServices are hosted on IIS, and will survive IWS Server installation updates.

Note:

This WebService wizard is intended to be run on the server that will host the IWS Repository only. It has not to be executed on the web server(s) where the web pages will get deployed to.

Step 1

In the first step you have to configure three items:

Website

This combobox lists all available websites on your IIS server. Select the one you want the IWS service to be added to. The website needs to be accessible for all users that will access IWS. IntraWeb Studio Server Location

This is the physical location for a new virtual directory that will be created on the selected website. The wizard will copy several assemblies and an empty database file to that directory.

Please note that if you selected the embedded Firebird option in step three, this might cause a permission issue on Windows 2003; in particular, the embedded engine needs read/write access to the database file (for example c:\inetpub\wwwroot\IWS\database\IWStudio.fdb). The wizard registers the IWS WebService to run under the default application pool in Windows 2003. It is assumed that this account is a member of the Windows group "Users". This assumption will fail on localized Windows versions or on servers where permissions have been modified.

After the wizard finished, you need to check the account that runs the default application pool, making sure that it has read/write permissions on that FDB file above.

Client URL

For the Click-Once installation of the IntraWeb Client, you need to enter the valid URL to the Website + IWS directory as entered in the dialog above. This is the URL that will be written to the Click-Once configuration, and will be used when a Click-Once IntraWeb client checks for the current version. 

Compression

The wizard tries to enable compression for the web service on your IIS server, which may improve the overall performace of the connected IWS clients. Every request of an IWS client and the answer of the IWS server will be wrapped into a SOAP package, which is text based and typically can be compressed by a factor of 10.

To manually enable compression for your IWS web service, you need to do the following: 

  • enable compression for the virtual directory where your IWS web service is installed or the whole website
  • add the asmx extension to the list of compressible script extensions. .Restarting/recycling the website/app-pool might be required.

Note:

Out of the box, compression works with IIS6 only. For IIS5 you will need a compression plugin for IIS, which is offered by several 3rd party vendors.



Feedback? Bookmark this topic    Previous Next

We use the ABCpdf .NET PDF component for HTML to PDF conversion...