EBIThree.com › Clarify How-to and Tips › Best Practice to Design Data Source after Conversion Manager
Best Practice to Design dataSource after Conversion Manager
When EBI 2.6 users convert their set-ups via Clarify 3 Conversion Manager, they might bring over multiple dataSources/data bindings. The reason for multiple objects might be for different databases such as QA, Development, Production.
dataSources After Conversion Manager
Below are two EBI JDEdwards Data Sources that were converted with the Clarify 3 Conversion Manager. In EBI 2.6 these set-ups were sufficient but with team development and using the same objects between local/QA/Production Servers, we will need to update the objects.
Merging dateSources
We merge/consolidate the JDEdwards Test (PY) and Production (PD) dataSources. We merge the 2 dataSources by using global variables. The only consolation would be having the same password for PY (test) and PD (production). This is needed because a global variable cannot be used for the password.
Global Variables for dateSources
We merge/consolidate the JDEdwards Test (PY) and Production (PD) dataSources
By: Sean Hoppe on
