Server-Side Troubleshooting
The table below lists Server Side block troubleshooting situations and steps to remedy.
| Situation | Block | Steps to Troubleshoot |
| I entered the Service URL but getting a pop-up with Check the Web Service URL | Web Service Block | Verify that the WSDL definition is accessible in a web browser.
Check the Composer logs for possible errors in fetching the WSDL. Location: <workspace>\.metadata Check that the WSDL definition is accessible and test with the Web Services Explorer utility as described in the Troubleshooting section. |
| I entered the Service URL and I can choose the SOAP operations, but the parameters do not show up in the dialogs | Web Service Block | Verify that the WSDL definition is accessible in a web browser.
Check the Composer logs for possible errors in fetching the WSDL. More details can be found in the logs in the following location: <workspace>\.metadata\.plugins\com.genesyslab.studio.model folder Check that the WSDL definition is accessible and test with the Web Services Explorer utility as described in the Troubleshooting section. |
| Using the Web Services Explorer utility | Web Service Block | The Web Services Explorer is a JSP Web application hosted on the Apache Tomcat servlet engine contained within Eclipse. The Web Services Explorer is provided with Composer and allows you to explore, import, and test WSDL documents.
Check that the WSDL definition is accessible and test with the Web Services Explorer utility as described in the Troubleshooting section. |
| Errors during runtime | Web Service Block | Check the Composer logs for possible errors in fetching the WSDL.
Check the backend logs. For ASP.NET projects, check the IIS logs For Java Projects, check the Tomcat standard logs. Check that the WSDL definition is accessible and test with the Web Services Explorer utility as described in the Troubleshooting section. |
| I copied my callflow/workflow from one project to another but my Backend block does not work Backend block
|
Backend Block | Check that any custom backend libraries or applications have also been copied to the new project.
|
Logs:
- Java Composer Projects Server Side Backend logging can be controlled using the log4j.xml file present in the $ComposerInstalledLocation\tomcat\lib folder.
- For DotNetComposer Projects web.config file can be used to control the Server Side logging.
- Java Composer Projects exported as WAR files will have the log4j.xml bundled inside the WEB-INF\lib folder. If the log4j.xml configuration format is not working, you can add a log4j.properties in the tomcat/webapps/<application name>/WEB-INF/classes folder.
Notes:
- Service URL has to end with wsdl or WSDL
- Cannot use - or other reserved characters in the Entry block for a variable value. Enter the value directly in the input parameters dialog by typing the value in the Expression column as a string; example: 'atm near 37.771008, -122.41175'