plugin: Troubleshooting
Many of the same tactics outlined in the main Troubleshooting Wiki page can be applied to the plug-in. To replicate these strategies, you first need to identify the Ant command being run by the plug-in step. Within all DataPower step output logs, the DataPower Configuration Manager (DCM) command is displayed. This same command can be run manually in a terminal or via an IBM UrbanCode Deploy Shell step. The command in question is always preceded by the command: marker.
In the above screenshot, line 31 contains the full DataPower command that is being run by the plug-in. You may notice that command is very long due to the Agent's folder paths. To simplify the command, feel free to modify the runtime location in your terminal. This may make it easier to reconfigure.
Note: The single quotes surrounding some of the arguments are placed by IBM UrbanCode Deploy to simulate how the terminal is reading the command. This is important as spaces may make some commands ambiguous to a developer. In some terminals, these single quotes should be removed.
As mentioned before, these commands can run on the terminal or a Shell step. If having issues, it's frequently recommend to try and first successfully run the command manually. This will ensure that all properties are configured correctly. Next step is to run the command in a Shell step. This removes any environment specific variables or terminal interpreters that may be helping your manual call. If you can get a command running in a Shell step, then there is no reason why that same should not work in a plug-in step. If you ever find one of these instances, please let IBM support aware!
Note: There are some syntactical issues in Ant Windows. Hence we recommend you do all testing and production deployments on Linux operating systems. View our Invalid Characters on Windows Wiki page for complete documentation.