Troubleshooting external applications
There is no check for the consistency of the external application configuration when it is set up. If there are problems, these will first be seen when the application is executed. Below are some tips to aid with troubleshooting issues with external applications.
- Information is presented to a user if an external application fails. In a CLC Workbench, summary information will be shown in a dialog, and this may help to identify the issue. If the summary information does not help, try opening the Advanced tab, where an extended error message should be visible.
- Configure the external application to import standard out and standard error as text. This makes it possible to check error messages posted by the external application. See figure 12.23.
Figure 12.23: Standard error and standard out from the command line application can be collected and imported as text so it can be reviewed. - If your external application was previously working and then stops working, you can check to see if the configuration was recently changed. Each time a change is made the version number of the external application is updated. You can see the name of the user who made the most recent change in the listing under the External application tab, and also under the Management tab of the editor when you open an individual external application.
- Check the third party application:
- Is the application being found? Check the path, and if you have not tried this already, give the full path to it.
- Is the application executable?
- If there is a wrapper script calling the third party application, does it contain the correct path to the application? Is the wrapper script executable?
- Check the import/export directory directory configuration
For certain setups, import/export directories must be configured. Please refer to section 12.1.6 for more details on this.
- Check for conflicts in the naming of the external application
If your users will only access external applications via a CLC Workbench, then you do not have to worry about what name you choose when setting up the configuration. However, if they plan to use the CLC Server Command Line Tools, to interact with your CLC Server, then please ensure that you do not use the same name as any of the CLC Server internal commands. You can get a list of these by running the
clcservercommand, with your CLC Server details and no tool specified. I.e. a command of the form:clcserver -S <host> -P <port> -U <username> -W <password or token>