My Oracle Support Banner

After Any Update On Schema In Connection Results Integration Activation Failure With Error - "Failed To Generate The Orchestration Artifacts" (Doc ID 2294088.1)

Last updated on AUGUST 02, 2018

Applies to:

Integration Cloud Service - Version 16.4.1 and later
Autonomous Integration Cloud - Version 18.2.5 and later
Information in this document applies to any platform.

Symptoms

If there is any change on existing connection schema,  orchestrations attached to the connection failed to activate and logs shows the below error.

ERROR
-----------------------
[2017-07-11T14:24:57.551+00:00] [AdminServer] [ERROR] [ICS-20154] [oracle.ics.abstraction.designtime] [tid: Thread-7856] [userId: support@test.com] [ecid: 005L0hqRnPx07yELn6k3yZ0000z400007T,0:2:214] [APP: icswebapp] An error occurred while activating the integration. Failed to generate the orchestration artifacts
[2017-07-11T14:24:58.083+00:00] [AdminServer] [ERROR] [ICS-10989] [oracle.ics.webconsole.integration.activation] [tid: Thread-7856] [userId: support@test.com] [ecid: 005L0hqRnPx07yELn6k3yZ0000z400007T,0:2:214] [APP: icswebapp] Integration "CONTACTCREATION | 1.23.0" cannot be activated. Incident has been created with ID 110. [[
oracle.ics.webconsole.common.exception.GeneralException: ICS-10989: Integration "CONTACTCREATION | 1.23.0" cannot be activated. Incident has been created with ID 110.
at oracle.ics.webconsole.model.manager.IntegrationManager.activateProject(IntegrationManager.java:2456)
at oracle.ics.webconsole.view.beans.backing.composer.ViewIntegrationsBean$ActivateIntegration.run(ViewIntegrationsBean.java:1265)
at java.lang.Thread.run(Thread.java:745)
Caused by: Failed to generate the orchestration artifacts
at com.oracle.ics.abstraction.api.flow.orchestration.deployment.ICSSoaArchiveGenerator.generateSoaArchive(ICSSoaArchiveGenerator.java:162)
at com.oracle.ics.abstraction.api.flow.orchestration.ICSBPELProjectHandler.createProject(ICSBPELProjectHandler.java:174)
at com.oracle.ics.abstraction.api.operation.bpel.ICSBPELOperationManager.processActivation(ICSBPELOperationManager.java:299)
at com.oracle.ics.abstraction.api.operation.bpel.ICSBPELOperationManager.activateInInternalCompute(ICSBPELOperationManager.java:167)
at com.oracle.ics.abstraction.api.operation.bpel.ICSBPELOperationManager.activate(ICSBPELOperationManager.java:155)
at com.oracle.ics.abstraction.api.operation.bpel.ICSBPELOperationManager.activate(ICSBPELOperationManager.java:134)
at oracle.ics.webconsole.model.manager.IntegrationManager.activateProject(IntegrationManager.java:2452)
... 2 more
Caused by: One of the endpoint WSDLs used by a connection may have changed. Regenerate the integration using Actions | Regenerate Artifacts on the Edit Integration screen, if that option is available. Otherwise recreate the connection. Some connection types do not support regeneration.
at com.oracle.ics.abstraction.api.flow.orchestration.deployment.ICSSoaArchiveGenerator.compile(ICSSoaArchiveGenerator.java:302)
at com.oracle.ics.abstraction.api.flow.orchestration.deployment.ICSSoaArchiveGenerator.generateSoaArchive(ICSSoaArchiveGenerator.java:131)
... 8 more


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Change the schema for existing connection

2. Activate the existing integration using old schema results the above error.

Changes

 

Cause

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

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


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