Application Step
The Application step calls and executes any application that can be run from the command line. The Application step runs only if your administrator has not created any security restriction on calling third-party applications on the server.
Note: You can use the Application step to access any executable application. However, technical support does not offer help with building or debugging code in third-party applications.
To add an Application step:
1. Drag and drop an 
Application step from the Palette to the canvas.
Application step from the Palette to the canvas.2. Double-click the step on the canvas to open the Step Properties tab.
3. Type a unique name for the step.
4. Specify the step properties.
For more information, see Adding Steps.
Application Step Properties.
Property Name | Description |
|---|---|
Name | Unique name for the step. |
Description | (Optional) Description for the step. |
Enabled | Enables the step for execution. This option is useful when troubleshooting a process, especially when there are numerous steps in the process. |
Error Handling | Select any of the following: • Stop Process - (Default) All the steps after this one are skipped or the entire process is stopped (depending on how you have the error logging options set) if this step stops due to an error. By default, this option is selected. • Ignore Error - The remaining steps in this process are executed even if this step stops due to an error. This is useful when you want to write a Decision step that can test for the error state of a previous step. |
Command Line | Any information that will be written on the command line to call and execute this application. You can type the information, or click Browse to specify the executable file. (required) This setting may also be the path to a shell script on the server. If the script file is in a shared location, click Browse to select the file. Use the appropriate command (cmd on Windows or sh on Linux) to call the shell script. Windows Batch File Example cmd /c MyScript.bat Note: You can specify the executable without the path if the correct path is entered for Starting location. |
Starting Location | (Optional) Location of the working directory for this application. This setting may also be the path to a shell script on the server. If the script file is in a shared location, click Browse to select the directory. |
Run | Allows you to decide how the application runs: • Hide window - Hides the command line window. • Normal window - Displays the command line window. • Minimized - Minimizes the command line window on the task bar. • Maximized - Maximizes the command line window to cover the complete screen. The default value is Normal window. Note: This setting is not applicable in case of Linux operating system. Even if you set the Run option, it has no impact on the application. |
If you are calling a shell script, such as .bat or .sh, insert @echo off as the first line in the script to prevent the opening of a command prompt window on the server, then attempting to open a command window on server may interfere with the running of the script.
You may call DJEngine in an Application step as long as the DJEngine location is in PATH variable or the DJEngine location is specified in Starting location.
Note: If you start Actian DataConnect from Windows Start menu, you do not have to add path to the location property, as DataConnect batch file has already added DJEngine path to the PATH variable.
Last modified date: 10/22/2024