Skip to Main Content
  • Questions

  • Apex Installation with ORDS in WEBLOGIC

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Lucas.

Asked: August 18, 2022 - 9:21 pm UTC

Last updated: February 07, 2023 - 3:37 am UTC

Version: 21.2

Viewed 10K+ times! This question is

You Asked

Hi Guys,

I'm Lucas, an Oracle Apex Developer. In my current project Me and DBA are currently trying to install Oracle Apex with ORDS in an Oracle EBS server using WEBLOGIC. We manage to do all the DB steps to instal both of them, ORDS and APEX, with all the required USERS as APEX_PUBLIC_USER, APEX_REST_PUBLIC_USER, APEX_LISTENER, ORDS_METADATA, ORDS_PUBLIC_USER. However, when we try to deploy the ORDS with WEBlogic using the console it doesn't work and when we try to do the same using command line, we get the error message bellow.
We manage to install it before, but the server was refreshed for the project and now its not working anymore.


wls:/EBS_domain_DLSI/serverConfig> progress=deploy('ords','/DLSI/ebs/app/ords/ords.war','AdminServer')
Deploying application from /DLSI/ebs/app/ords/ords.war to targets AdminServer (upload=false) ...
<Aug 18, 2022 5:32:19 PM BRT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, ords [archive: /DLSI/ebs/app/ords/ords.war], to AdminServer .>
.Failed to deploy the application with status failed
Current Status of your Deployment:
Deployment command type: deploy
Deployment State       : failed
Deployment Message     : weblogic.application.ModuleException: [HTTP:101064][WebAppModule(ords:ords.war)] Error parsing descriptor in Web appplication "/DLSI/ebs/app/ords/ords.war"
weblogic.application.ModuleException: Unmarshaller failed
        at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1356)
        at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:375)
        at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
        at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
        at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
        at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
        at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
        at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
        at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
        at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208)
        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
        at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:221)
        at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
        at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
        at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
        at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:550)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:263)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=web-app@http://xmlns.jcp.org/xml/ns/javaee
        at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:371)
        at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
        at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:336)
        at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:317)
        at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:168)
        at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
        at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
        at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:325)
        at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:803)
        at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:408)
        at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:774)
        at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:783)
        at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
        at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1342)
        ... 26 more

weblogic.application.ModuleException: Unmarshaller failed
Traceback (innermost last):
  File "<console>", line 1, in ?
  File "<iostream>", line 246, in deploy
  File "<iostream>", line 1855, in raiseWLSTException
WLSTException: Error occured while performing deploy : Target exception thrown while deploying application: Error occured while performing deploy : Deployment Failed. : Error occured while performing deploy : Deployment Failed.
Use dumpStack() to view the full stacktrace


EBS Version 12.2.4
DB Version 12.1.0.2
ORDS Version 21.2.0.r17
APEX Version 21.2

Thanks.

and Connor said...

Have you built/deployed the static files first?

Check (starting at page 1-36) the installation steps - you need to build the static elements first.

https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/21.4/aelig/oracle-rest-data-services-installation-configuration-and-development-guide.pdf

If this doesn't work, then it time to log an SR with Support so you can provide them with all of the logs/config etc.


Rating

  (1 rating)

Is this answer out of date? If it is, please let us know via a Comment

Comments

WebLogic server on EBS

Sylvain Martel, February 07, 2023 - 3:24 am UTC

I know this is quite an old post, but for the benefit of the community, I think there are be some additional useful information for other readers.

You can not utilize the Oracle WebLogic Server 11.2 installed by Oracle E-Business Suite 12.2, as this release does not support JDK 8 required by ORDS. It is not supported to update the release of Oracle WebLogic Server utilized by Oracle E-Business Suite.

A separate Oracle WebLogic Server license is required, other than the Oracle WebLogic Suite for Oracle EBS.
Connor McDonald
February 07, 2023 - 3:37 am UTC

Thanks for the info
more

Connor and Chris don't just spend all day on AskTOM. You can also catch regular content via Connor's blog and Chris's blog. Or if video is more your thing, check out Connor's channel and Chris's channel from their Youtube channels. And of course, keep up to date with AskTOM via the official twitter account.