JDE agent not connecting to db after upgrade to v11.2.2

book

Article ID: 87829

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

Error Message :
java.lang.IllegalArgumentException: net.sourceforge.jtds.jdbc
Error connecting to the database. Check the JDBC login assigned to the agent and verify that it is correct. The agent login Test button can be used to test the connection.

RA JDE agent is unable to start up when using it with SQL Server in V11.2.2+build.622. There is no documentation on using RA JDE agent with SQL Server even though the release notes states:
"The JD Edwards agent runs with either Oracle or SQL Server databases with JDE EnterpriseOne. The minimum supported version of SQL Server is 2005."

Reference: http://docs.automic.com/documentation/RA_JD_Edwards/1.1/english/RA_JD_Edwards_RELEASE_NOTES/help_en.htm 

Upgrade repro: 
1. Upgraded the RA core to 11.2.2+build.622 
2. Updated the ucxjcitx.ini file 
3. Created the JD Edwards CONN object to be used for SQL Server - see screenshot, 
\\sbb01\apps\SalesForce_ServiceCloud\INC00120794\DEV\CONN.JDBC.TEST.jpg 
4. Start the RA JDE agent 

New install repro: 
1. Create a directory. For example, C:\AE\agent\rapidautomation. 
2. Execute the setup.exe file. 
3. Create the cache directory. 
4. Edit the ucxjcitx.ini file. 
5. Load the RA solution. 

Cause

Cause type:
Defect
Root Cause: Have getPackage() delegate to parent like definePackage() does so it doesn't get an Exception defining an existing package.

Environment

Release: AUTWAB99000-11.0-Automic Workload Automation-Base Edition
Component:

Resolution

This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Status: Released

Fix Version(s):
RA.JD.Edwards 1.2.0

Additional Information

Workaround :
The issue was found and fixed with RA.JD.Edwards 1.2.0 in Documentation Guides, JDEdwards.