Getting Access to the Soap Header from JCD exposed as web service
I am exposing a JCD as a Web Service. Is there any way to get access to the Soap Header information from the JCD? We currently do not have the HTTP eway. I can get access to the WSDL binding editor via the Connectivity Map, and I can see where I can add a header to the message. I do not see how to expose the header information so that is then available for use by the JCD. The only parts that i can pick in the WSDL binding is the Body and is not where the header is.
# 1
I asked the question with support, incident : 1188595, here is the response...
The only way to specify the Header when exposing a web service as a JCD is within the WSDL Binding Editor in the Connectivity Map properties. As you know this does not allow you to specify an XSD to describe the header.
If this is your requirement, you will need to define a Business Process using eInsight to expose your web service which allows users to access the abstract parts of a WS Operation. The part of the message that goes into the header is defined in the Binding Section of the WSDL. Regardless of what goes in the header and what goes in the body, the entire message will be available in the BP Mapper. The process for exposing a web service using eInsight is documented in section 5.5 of the eInsight User's Guide.
# 2
Perhaps this is not the place for my reply, John, but what about the inverse of your question: where the JCD (JCAPS 5.1.2) is a consumer of a web service?
I am trying to access the Soap Header from my JCD so I can set a string into an attribute that the web service is expecting the consumer to provide.So far, I have found no way to do this either.I just don't see where JCAPS exposes it.
It's crazy to believe I would need or want to install and use eInsight to consume a single web service in a system the size of mine since I don't need robust BPEL orchestration.
Incidentally, I was told by the professional services team this was possible. They simply have not found someone that can tell me how to do it.
# 3
I have had no problem calling an external web service from a JCD in 5.1.2 I have been able to access and set the fields of the header portion of this external web service as long as the WSDL for the web service has used an explicit header description. If the WSDL contains and implicit header (the header is described as a separate message) I have not been successful getting visibility to the header. See http://www.softwaresummit.com/2005/speakers/TostPracticalLessonsLearnedInWebSer vicesDesign.pdfpages 30 - 32 it has a nice summary about the difference for header descriptions. If CAPS is cooperating with you, you should be able to import the WSDL for the external web service, create a JCD that is going to call the web service, include the OTD for the web service in your JCD and then just follow the instructions in the eGate users guide to fire off the invoke of the web service.
