Advanced Configuration of Standalone DEMO

FAmores

Member
Hi all,

I´m not JDE guy but EPM. I´m working on a EPM-JDE integration using Oracle Data Integrator (ODI). My source system is the standalone demo image.
ODI uses JDBC driver to connect to JDE (DAD - Data Access Driver) and I´m struggling with getting successful connection.

It seems that some configuration is missing when driver is checking the JDE environment. I guess it is because of architecture of DEMO image.

For example, the connector is launching the following SQL query:

25 Jul 2013 10:38:05,180 [APP ] - [JDBJ] SELECT SKSERSHP FROM JDESY910.F96511 WHERE ((SKMKEY = ? AND SKPORTNUM = ? AND SKPATHCD = ? AND SKMCHDETTYP = ? ))
25 Jul 2013 10:38:05,180 [APP ] - [JDBJ] SQL statement parameter marker values are :
25 Jul 2013 10:38:05,180 [APP ] - [JDBJ] Param1 : LOCAL _Types.VARCHAR,
25 Jul 2013 10:38:05,180 [APP ] - [JDBJ] Param2 : 6012_Types.NUMERIC,
25 Jul 2013 10:38:05,180 [APP ] - [JDBJ] Param3 : DEMO _Types.VARCHAR,
25 Jul 2013 10:38:05,196 [APP ] - [JDBJ] Param4 : 31 _Types.VARCHAR,

and result is:


25 Jul 2013 10:38:05,211 [SEVERE] - [METADATA] PackageLookUpService: Could not find attribute <31> in table F96511 for host <LOCAL>, port <6012>, pathcode <DEMO>.
25 Jul 2013 10:38:05,227 [SEVERE] - [JDBJ] For server <LOCAL>, port <6012>, pathcode <DEMO>, failed to find the deployed package. Aborting the discovery process. com.jdedwards.database.services.packagelookup.PackageLookupServiceException: PackageLookUpService: Could not find attribute <31> in table F96511 for host <LOCAL>, port <6012>, pathcode <DEMO>.

As i don´t have experience in JDE I was wondering if anybody can provide his feedback about configuring DEMO image for such integration.
I think integration is expecting a complete JDE E1 architecture with Deployment Server, etc...

Has anybody configured DEMO image in such way?

Thanks very much in advanced
 

Attachments

  • 184074-e1root_20130725_0.txt
    214.2 KB · Views: 160
Back
Top