My Oracle Support Banner

E1: ORCH: How To Use the Database Connector To Point To the Correct DB Owner Based on The Login Environment Without Creating Multiple Groovy Script For Multiple Environments? (Doc ID 2790222.1)

Last updated on JUNE 15, 2022

Applies to:

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

Goal


Goal 1: Is there an Orchestrator Property file that is similar to BSSV Property file (P951000/F951000)?

Customer has a scenario working with a database connector and complex groovy code. Inside the groovy code, there is a sql select statement that is similar to "select * from testdta.f0101" where do not wish to hardcode testdta in the sql statement. Is there something similar to BSSV property (F951000) where user can put a key/value pair for database owner = testdta. 

Goal 2:  Based on the login environment, find out the DB owner and pass the value to the groovy script to form the SQL statement. 

Solution

To view full details, sign in with your My Oracle Support account.

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


In this Document
Goal
 
Goal 1: Is there an Orchestrator Property file that is similar to BSSV Property file (P951000/F951000)?
 Goal 2:  Based on the login environment, find out the DB owner and pass the value to the groovy script to form the SQL statement. 
Solution
 Solution 1: Use Cross Reference. 
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.