An OAE Agent will not start using a pseudo-apps user with OEBS R12

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

An OAE Agent will not start using a pseudo-apps user with OEBS R12

Environment

Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent
Component:

Resolution

Detailed Description and Symptoms

Applying OEBS patch (9362691) for R12 causes the Applications Manager OEBS Agent to stop working. The OEBS patch in question, #9362691, introduces some additional security requirements which render the pseudo-apps users useless. The extra security features force the use of the 'apps' user to be used for OEBS Agents.

 

The issues being caused by the Oracle Patch are not considered bugs by Oracle. The patch was created to prevent pseudo-apps user account from performing the type of tasks needed by the Applications Manager OEBS Agent. Automic will no longer be able to install an OEBS agent as a pseudo-apps user.

Solution

To correct this and have the OAE agent start again, create a login object using the APPS user. The APPS login object only needs to be granted to the user that creates the OEBS agent. No other users need the APPS login. 

All other users can be granted access to a pseudo-apps user to perform queries or to create Subvars to gain information from the OEBS system.