Web Service installation and FAQ
Joined: 19 May 2008
Topic: Web Service installation and FAQ
Posted: 08 Sep 2011 at 11:40am
Ecrion’s Web Service FAQ
The Web Service is our WSDL/SOAP interface “API”. For technical specifications of the SOAP API please see the end of this FAQ.
If you installed the service using our setup, it will be accessible at: http://localhost/XFWS/ecrion/services/XFWS.asmx. Then the WSDL will be available at http://localhost/XFWS/ecrion/services/XFWS.asmx?WSDL and you will see the following screen at that location:
Here is the link to view the SOAP API code and parameters:
Make sure you install the Web Service as the administrator: open a command prompt as an user with Administrative rights and run with a command line similar to the following:
msiexec.exe -i setup_name.msi
Installation “interrupted” message with IIS7
The web setup does not install on computers with IIS7 until the IIS6 compatibility layer is installed.
Complete the following steps to install the IIS 6 compatibility layer:
1. Open Control Panel, and then open Programs and Features.
2. Click Turn Windows features on or off.
3. Expand Internet Information Services, expand Web Management Tools, and then expand "IIS 6 Management Compatibility".
4. Select "IIS Metabase and IIS 6 configuration compatibility".
5. Click OK.
Here is an image for the compatibility settings:
Other “Installation interrupted” or “Fatal Error Occurred” during installation suggestions
This page might help you: http://support.microsoft.com/kb/834484
In addition, make sure that the path you are installing to doesn't contain Unicode characters (like German for instance), because this might sometimes confuse installers.
If that doesn’t help, here is the command line for msiexec which will create an installation log. Then, send that log to firstname.lastname@example.org.
404 or 403 Errors:
First, check that the ASP.NET extension is set to “allowed”:
See MS KB articles for more info:
Then, try creating a separate 2.0 .NET application pool:
1. uninstall UWS
2. configure a separate 2.0 .NET application pool
3. reinstall UWS in that app pool
For an example on how to configure a 2.0 application pool: http://blog.crowe.co.nz/archive/2008/07/23/IIS---Event-ID--1062---Server-Application-Unavailable.aspx
If you see this type of parser error, it means that you are using .NET 1.1 and the Web Service requires .NET 2.0:
Just increasing the timeout in IIS should work. This is something that IIS does (it will abort a web application/web page that is taking more time to respond) and is not under our control.
“Error reading socket” or “Operation is not valid due to the current state of the object” error messages
This can mean that the Web Service version you are using is out of sync with the Rendering Server, in which case you may need a new version from the website or support. If you have identical versions, check if an older version of Ecrion.Ultrascale.NET.dll is being picked up from somewhere, like the GAC (global assembly cache).
Here is how to see if any Ecrion dlls are in your GAC:
- Go to Control Panel\ Administrative Tools
- Open Microsoft .NET Framework 2.0 Configuration
- Expand My Computer\Assembly Cache
- Remove any Ecrion*.dll you find there
Testing the Web Service functionality through the command line:
Open a command prompt and try the following:
How do we use the Netlink Load Balancing Add-On with Web Services?
Your Netlink instances can be configured by editing the web.config file:
Does the Web Service work with Tomcat?
The Web Service was written for IIS. We do have a Web Service for Tomcat, written in Java. Contact email@example.com for more information.
The following technical standards are supported:
WS-I Basic Profile 1.1
SOAP 1.1 or higher
SOAP binding style - Document literal
SOAP Attachment - MTOM (http://www.w3.org/TR/soap12-mtom/); WS-I SwaRef can be implemented upon request (for example as an EJB that can be deployed for JBOSS).
Security –HTTPS; WS-Security 1.0 (http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf) is also a possibility.
We can support concurrent web service requests.
We can interface with a WebSphere Process Server.
Edited by radup - 31 Oct 2011 at 9:56am
|Forum Jump||Forum Permissions
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum