Error running sendevent or jil commands through iXp CLI

Products

• CA Workload Automation iXP

Issue/Introduction

Users experience errors when executing AutoSys commands such as sendevent and jil via the iXp command-line interface ․
Commands run directly on the IXP/AutoSys server outside of the iXp WebUI, complete successfully out.

ERROR MESSAGE:
Error:
Sendevent Successes:0/1
/apps/ixphome/tmp/comm-<DateTime>.out (no such file or directory)

SYMPTOMS:

• AutoSys commands fail in iXp CLI

• Local commands on iXp/AutoSys server work normally

CONTEXT:
This occurs when using the iXp WebUI CLI to send events to AutoSys ․

IMPACT: Users cannot issue commands through the iXp interface ․

 

 

Environment

CA Workload Automation iXP 11․4

Cause

Incorrect setup of the Command line Paths in the iXp Admin Tool.
The client had put the same path in the shell commands as Actual JIL and SENDEVENT commands

Resolution

1․ OPEN IXP ADMIN TOOL

Log in to the iXp Admin GUI ․

EXPECTED: Admin interface loads successfully

2․ LOCATE INSTANCE SETTINGS

Navigate to the Instance tab ․
Select the AutoSys instance from the drop-down menu ․

EXPECTED: Instance details display

3․ MODIFY COMMAND LINE OPTIONS

Select the Command Line tab on the left side ․
Clear the values in the Sendevent shell command and JIL shell command fields ․

EXPECTED: Fields are blank

4․ SAVE AND RESTART

Save the configuration changes ․
Restart the iXp webservice ․

EXPECTED: Service restarts without errors

VERIFY SUCCESS:

• Log back in to iXp

• Confirm sendevent and jil commands execute successfully

   

   

Additional Information

What is the "Sendevent Shell Command" Setting?

When an iXp user performs an action in the GUI that requires sending an event to AutoSys (like starting a job, placing it on hold, or killing it), the iXp Server has to execute a command locally on its own OS to pass that instruction to AutoSys.

This setting tells the iXp Server which shell program to use to execute that sendevent.

How to Configure It

You can find this setting by opening the iXp Admin Tool, navigating to the Instance tab, selecting your specific AutoSys instance, and looking under the Command-Line Options section.

Here is how you should configure the field based on your architecture:

• The Default Configuration (Leave Blank): By default, if you do not specify anything, iXp uses standard local shells. It will use /bin/sh if your iXp Server is running on UNIX/Linux, or cmd /c if it is running on Windows. You should use the default if the AutoSys client binaries (the sendevent executable) are installed directly on the iXp Server and the iXp daemon user has the right paths set to run it locally.

• Alternate Configuration (e.g., ssh): If your iXp Server does not have the AutoSys client utilities installed locally, or if you need to execute the command on a remote machine for security/architecture reasons, you can specify an alternate shell command here. A very common configuration here is to enter ssh so that iXp initiates a secure shell session to the actual AutoSys server to run the sendevent