RA Oracle Retail Connection Object requires Username and Password, causing Wallet connections to fail
Article ID: 84664
Updated On:
Products
CA Automic Workload Automation - Automation Engine
AUTOMIC WORKLOAD AUTOMATION
Issue/Introduction
Error Message :
N/A
N/A
Setting up the Oracle Retail Solution for version 12 and trying to configure the CONN.OBJECT CONN.RMS_APP with the Oracle WALLET ALIAS, causes the jobs to fail.
The CONN. OBJECTS fields in the WEBUI do not seem to recognize the WALLET ALIAS and LOGIN.
Cause
Cause type:
Defect
Root Cause: Currently the local client allows all 3 fields null. For AWI, we only removed the username/password and still requires the network alias. Underneath the connection is a SQL*Net connection , so requires alias name is OK
Defect
Root Cause: Currently the local client allows all 3 fields null. For AWI, we only removed the username/password and still requires the network alias. Underneath the connection is a SQL*Net connection , so requires alias name is OK
Environment
Release: AUTOME99000-2.0-Automic-Oracle Retail MOM-Enterprise Edition
Component:
Component:
Resolution
Update to a fix version listed below or a newer version if available where the AWI has been updated to allow null value for username and password, so that Oracle wallet can be used by entering the value to the network alias without the username and password.
Fix Status: Released
Fix Version(s):
RA.Oracle.Retail 2.1.0 - Available
Fix Status: Released
Fix Version(s):
RA.Oracle.Retail 2.1.0 - Available
Additional Information
Workaround :
Configure the connection object in the rich client.
Configure the connection object in the rich client.
Feedback
Powered by
