Siebel adapter SiebeltowM

How does Siebel pass data to a wM service? I can successfully invoke a service to simply run a debug message, but I cannot receive data. Do I need to accept a node (any specific name) or a string called “inputData”?

Thanks for the help.

I forgot to mention we’re running wM IS 6.1 and Siebel 7.5.


Can you tell us a little more about what you are attempting to do? Do you want to invoke an IS Flow or java service from Siebel that will return some result set? Which Siebel tool or approach are you attempting to use?

Depending on the maturity of the web services support in Siebel these days, you should be able to expose your IS Flow services as Soap RPC web services and consume them in Siebel. You would need to generate a WSDL file using webMethods Developer for Siebel to use, but that’s pretty straightforward (at least for Soap RPC, anyway).

There are also many, many other ways to invoke IS services from Siebel. The one that works best for you depends on what you are trying to accomplish and the capabilities of the Siebel tools you have to work with.


Thanks Mark.
Siebel consultants are attempting to call a Business Service Simulator and/or a step from a Workflow. They are indeed trying to invoke a wM IS Flow by passing XML as input data.
WSDL is a novel concept, but (since I have no experience with them) when the Flow changes, a new WSDL would have to be sent, correct?
Thanks again,

Invoking a Flow service by posting a XML document is a tried and true approach that should take minimal time on the Integration Server side of the equation.

Whether you invoke a service by posting an XML document via HTTP or posting a Soap message by HTTP, you would have to make a change to the Siebel client code if your service changed to require new input parameters.

If you simply change the service without changing its inputs or outputs then you would not need to regenerate and communicate the WSDL.