4 Replies Latest reply on Dec 26, 2014 11:27 AM by Pratik02

    DAD Drivers issue in EPM system for ODI

    Pratik02

      Hello all,

       

      We are trying to set up 9.1.4.7-Data-Access-Driver_06_70 to connect JDEdwards with FDMEE through ODI.

       

      EPM Environment:-

       

      Single Managed Server

       

      1)EPM 11.1.2.3.500 x64 on Windows server 2008 Windows 2008 Server EE SP2 64Bit and updated patches over it

       

      2)Database MS SQL Server 2005 x64

       

      3)Components(HSS,Essbase,planning,HFM,FDM,FDMEE,HSF,RNA)

       

      4)ODI studio 11.1.1.7 is installed and configured

       

      I want to connect to JDEdwards system to extract the data in ODI layer and pull it to HFM application through automation(i.e ODI) process, so I downloaded the JDEdwards Enterprise one tool from support 9.1.4.7-Data-Access-Driver_06_70

       

      Followed the ERPI admin guide to set up ODI to integrate with JD Edwards

      It seems like we have an issue with the Step #10 while setting up.

       

       

      STEP #10. Run the script updateODIEAR.bat / sh from the following directory: EPM_ORACLE_HOME \products\FinancialDataQuality\bin

      Before running the script, make sure that environment variables JAVA_HOME and TEMP are set correctly.

       

      The execution of Batch file completed successfully (NOT SURE IF ANY LOG IS GENERATED FOR THIS, BUT THE BATCH FILE DOES NOT THROW ANY ERROR)

       

      After completion of STEP #10, we get an issue while starting the EPM Services (Single Managed Server as mentioned above). The web-logic is going to admin state and I cant access any EPM Application using web URLs (Being Single Managed server nothing works)

       

      Here is the Log file for Starting the EPM Services

       

       

      <Dec 4, 2014 1:27:07 PM PST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\tmp\servers\EPMServer0\tmp\_WL_user\oraclediagent\cn250y/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>

      <Dec 4, 2014 1:27:07 PM PST> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.bam.odi.library, Specification-Version: 11.1.1, referenced from: C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\tmp\servers\EPMServer0\tmp\_WL_user\oraclediagent\cn250y]. Make sure the referenced optional package has been deployed as a library.>

      <Dec 4, 2014 1:27:08 PM PST> <Error> <HTTP> <BEA-101371> <There was a failure when processing annotations for application C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\tmp\servers\EPMServer0\tmp\_WL_user\oraclediagent\cn250y\oraclediagent.war. Please make sure that the annotations are valid. The error is >

      <Dec 4, 2014 1:27:08 PM PST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'oraclediagent' due to error weblogic.application.ModuleException: Failed to load webapp: 'oraclediagent'.

      weblogic.application.ModuleException: Failed to load webapp: 'oraclediagent'

      at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:395)

      at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)

      at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)

      at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)

      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)

      Truncated. see log file for complete stacktrace

      Caused By: java.lang.NoSuchMethodError: org/apache/xerces/impl/xpath/regex/RegularExpression.<init>(Ljava/lang/String;Ljava/lang/String;Ljava/util/Locale;)V

      at org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl.applyFacets(Unknown Source)

      at org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl.applyFacets1(Unknown Source)

      at org.apache.xerces.impl.dv.xs.BaseSchemaDVFactory.createBuiltInTypes(Unknown Source)

      at org.apache.xerces.impl.dv.xs.SchemaDVFactoryImpl.createBuiltInTypes(Unknown Source)

      at org.apache.xerces.impl.dv.xs.SchemaDVFactoryImpl.<clinit>(Unknown Source)

      Truncated. see log file for complete stacktrace

      >

      <Dec 4, 2014 1:27:08 PM PST> <Emergency> <Deployer> <BEA-149259> <Server 'EPMServer0' in cluster 'EPMServer' is being brought up in administration state due to failed deployments.>

      Hyperion Provider Services - Release 11.1.2.3.502.067

      Copyright (c) 1991, 2014 Oracle and / or its affiliates. All rights reserved.

      connection mode : HTTP

      essbase.properties: C:\Oracle\Middleware\EPMSystem11R1/common/EssbaseJavaAPI/11.1.2.0/bin/essbase.properties

      java System properties -DESS_ES_HOME: C:\Oracle\Middleware\EPMSystem11R1/common/EssbaseJavaAPI/11.1.2.0

      Mode: Non Fusion read from Registry

      Hyperion Provider Services - Release 11.1.2.3.502.067

      Copyright (c) 1991, 2014 Oracle and / or its affiliates. All rights reserved.

      connection mode : EMBEDDED

      essbase.properties: C:\Oracle\Middleware\EPMSystem11R1/common/EssbaseJavaAPI/11.1.2.0/bin/essbase.properties

      java System properties -DESS_ES_HOME: C:\Oracle\Middleware\EPMSystem11R1/common/EssbaseJavaAPI/11.1.2.0

      Warning: Starting ADF Library jar post-deployment on WebLogic Server. Is "provider-lazy-inited" init-param missing from LibraryFilter? Ignore this warning if the ADFJspResourceProvider is not being used.

      Started: ADF Library non-ADFJspResourceProvider post-deployment

      Finished: ADF Library non-ADFJspResourceProvider post-deployment (millis): 1357

       

       

      Any Help would be greatly appreciated

       

      Regards,

      Pratik