search cancel

import or export JIL does not work in WCC ECLI

book

Article ID: 189287

calendar_today

Updated On:

Products

CA Workload Automation AE

Issue/Introduction

When we try to import or export jil files in WCC Enterprise Command Line (ECLI) it does not work.

 

Environment

Release : 11.4

Component : Workload Control Center (WCC) 

Resolution

The encountered problem is related to the "Credential User" Not being Validated.

There are several possible solutions for configuration of the Credential User.

You can proceed by the following steps to configure the Credential User for ECLI to work fine:

1. Login to WCC as the User encountering the ECLI issue


2. In the WCC “Configuration” Tab, verify the user set for “Monitor ID”.


3. Login to your “AutoSys Server” as the “User" defined in “Monitor ID” to verify the “Password”.


4. Then in “Credentials” Tab, Add a “Global Credential User” defined on the “Monitor ID User”

The Syntax to respect is _GLOBAL_:username

Example: _Global_:autosys when the Monitor ID is “autosys”

Provide a “Valid OS password” for the user on your AutoSys Server (twice).

Then click on “Add” if this is the first time you define the _GLOBAL_:username

Otherwise, click on “Update” to validate the modification on the “Global User”


Please note the user configured as "Credential User" needs to have "Interactive Login" authorized at OS level.

Otherwise, if you can not allow the Monitor ID user to have "Interactive Login",

then another user with "Interactive Login" authorization will need to be configured as "Credential User".
 

5. Then the user will need to logout from wcc


6. Then login to wcc and verify the Global Credential User is kept


7. Now you will be able to run the commands and/or import and export jil files through ECLI