Having installed Adobe Experience Manager 6.1 Forms Server for Red Hat JBoss (Windows), I was pleasantly surprised in the reduced boot time (vs Livecycle ES4 SP1).
I installed a Livecycle Archive (containing a HTTP Service data model and associated generated document services component) and deployed it. That caused an error: "ERROR [com.adobe.workflow.AWS] (http-/0.0.0.0:8080-2) Service: CivMilInterfaceModel not found.".
The same kind of error appears when trying to create a data model, then deploy it and use its methods 😞
First, I thought something went wrong in the installation, but after three retries I still get the same error.
I have not tried to do an in-server upgrade. I am hesitant to break my operational development server.
Please advice how to proceed or resolve this issue. Is there a tweak?
Are these answers useful? Help other community members by marking useful answers as accepted.
My apologies for not replying earlier. Things were rather busy.
Please find attached two LCA's and a server log (AEM 6.1). One LCA was created on Lifecycle ES4 SP2 and upon deploy created an external_services_ ... entry in my application. I there was able to reference the component. The same actions (see also below) performed using AEM 6.1 Forms does not create an external_services_ ... entry in my application, and thus I cannot reference it in a process.