Business Objects jobs do not return FAULT_OTHER status when input variables do not exist

book

Article ID: 84559

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

Error Message :
org.apache.axis2.AxisFault: get The exception is of a known origin. (Error: FWM 03005)

Unlike jobs run on other Agents, the Business Objects Agent will issue a call to Business Objects to get the result and the return code. Therefore, if parameters are not correctly set, you may see a BO job execute and terminate with ENDED_NOT_OK, whereas with other Agents the job would terminate immediately with FAULT_OTHER.
 
Investigation 
  1. Define a parameter called &PRICING_FOLDER# to be used to store the report destination for a BO job.
  2. Define a BO job to run on the RA Business Objects Agent, and reference the variable in the pre-process tab of the job, but spell it &PRICONG_FOLDER#.
  3. Run the job. 
Expected:  Job terminates and immediately goes into a status of FAULT_OTHER.
 
Actual:  Job starts and returns an error similar to the one below, and goes into a status of ENDED_NOT_OK.

org.apache.axis2.AxisFault: get The exception is of a known origin. (Error: FWM 03005)
 
This is a BO error, which when referenced in the BO documentation states that the path node does not exist in the repository.

Which means (Business Objects documentation):

(FWM 03005) The path node {0} does not exist in the repository

Cause
The URI's path node is not properly specified to query for the objects on that path. This is currently only
relevant to cuid and path URIs.


 

Cause

Cause type:
By design
Root Cause: The current Business Objects agent does not check if the folder exists in the repository or not. Therefore the job ends with ENDED_NOT_OK - aborted.

Environment

OS Version: N/A

Resolution

The current Business Objects Agent does not check to ensure the folder exists in the repository before running the job. Therefore, the job will be submitted and executed and will finally abort with a status of ENDED_NOT_OK.

If you would like the Business Objects Agent to behave similar to other Agents and have the BO Job terminate and immediately go into a status of FAULT_OTHER, an enhancement request must be submitted.

 



Fix Status: No Fix

Fix Version(s):
N/A

Additional Information

Workaround :
Verify the Path to Specific Business Objects settings are correctly set in the pre-process panel of the Job.