Understanding WSDL Creation

See Also

When you save an event processor in an IEP Module project, a WSDL document is automatically generated.

The name of the WSDL document is derived from the name of the event processor. For example, if the event processor is called insiderTrade.iep, then the WSDL document is called insiderTrade.wsdl.

Note: If you subsequently rename the event processor, IEP does not refactor the name of the WSDL document.

The WSDL document contains two types of message objects:

If the event processor has a Stream Input operator, then the WSDL document contains a SOAP-based binding and service.

If the event processor has a Stream Output operator, a Batched Stream Output operator, or a Relation Output operator, then the WSDL document contains a file-based binding and service.

You may need to manually update the default settings for any binding and service. For example, the default file directory is a Windows path, which would not make sense on a UNIX system.

For detailed information about the binding and service configuration, see the documentation for the HTTP Binding Component and the File Binding Component.

Note: If you manually update the WSDL document and then save the event processor again, the changes that you made to the WSDL document are overwritten. For a recommended workaround, go to the IEP release notes and read the section on iterative development.

See Also
 
Using the Stream Input Operator
Using the Stream Output Operator
 

Legal Notices