Native Call

Native Call helps you run the SH files asynchronously during the execution of a Process Flow. In a Linux-based Kubernetes environment, you'll be able to execute only SH files.

Steps to create a Native Call:

1. Click Configure > EXTENSIONS > Native Call.

2. Click Create Native Call. 

   
   
   

3. Enter the name and description of the new Native Call service in the text boxes Name and Description fields respectively.
4. Select the extension of the file .sh from the drop-down list of Default Extension.

5. Enter the relative path of the file in the field File Name.

   Make sure that the executable file is located in the shared repository. For example, if the file abc.sh is placed in a folder XYZ in the shared repository, the relative path of the file will be "XYZ/abc.sh".

6. To specify any arguments for selected executable file enter the arguments in the Argument(s) space separated field.

7. Enter the path of the directory where you want to run the specified executable file, in the Working Directory field. Make sure that the working directory resides in shared repository.

   If Working Directory is not specified, the shared repository itself becomes the working directory. The system will look into the shared repository (not in any subfolder) for the files specified in the script and if it fails to find the files, it will cause an error. Consider a scenario wherein a shell script abc.sh is placed in the folder XYZ in the shared the repository, and the script is meant to copy the content of File1.txt to File2.txt. If both of these files, File1.txt and File2.txt, are not available directly in the shared repository, you'll encounter an error. To tackle such a situation beforehand, you may need to do either of the followings:

   • Place the files specified in the script directly in the shared repository. 

   • Specify the absolute path (for example, shared/XYZ/File1.txt, and shared/XYZ/File2.txt) in the shell script file.

8. Expand the Advanced Properties.
9. Select the Project from the drop-down list of Project. 

10. Click Save.

    When using a Native Call in a Process Flow, the waitForEnd property is set to False by default. This implies that the Native Call and other activities in the Process Flow are executed simultaneously. If you want to wait until the completion of the Native Call before the next activity is executed in the Process Flow, you need to set this property to True.