E1: XMLP: How to Enforce EnterpriseOne Security on JDBC Connections from BI Publisher Enterprise (Doc ID 839333.1)

Last updated on MAY 30, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.

Goal

User just created a new EnterpriseOne JDBC connection in BI Publisher Enterprise. Users are able to create and run reports without any problems. However the JDBC connection always uses the "JDE" user profile and as a consequence, no EnterpriseOne security is applied.

Is there a way to force users to use their own EnterpriseOne user profile instead?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms