We have a number of processes in LiveCycle being used as web services called from a PDF embedded in workspace.
The processes are split across three Livecycle ES2 nodes with JBoss 4.2.
When I consume the WSDL via https in Designer I would expect for the endpoint to point to the cluster name on https too. However, The generated WSDL marks the wsdlsoap:address location with an http prefix rather than https
This is causing the service call lookups to break ! I know this is the cause as when I run this on the only box which can bypass the load balancer (which is also doing SSL termination), everything works.
Anyway I can get to this binding via orchestration at all ??
You can use a custom Data Type named "WebServiceSettingsBean" in a LiveCycle process. This process can be configured to have a dynamic WSDL binding.
I hope that may helps.