Import of concrete WSDL in TIBCO Designer does not create Transport artifacts when WSDL is created in TIBCO BusinessEvents Studio release 4.0.1 or 5.0.
Article ID: KB0088911
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
Import of concrete WSDL in TIBCO Designer does not create Transport artifacts when WSDL is created in TIBCO BusinessEvents Studio release 4.0.1 or 5.0.
Environment:
==========
TIBCO BusinessEvents Studio
TIBCO Designer
Symptoms:
=========
Import of concrete WSDL in Designer does not create transport mentioned in WSDL.
Resolution:
==========
WSDL created in BE Studio is correct but since Designer is a static tool so it doesn't create the transport by itself. It must be done manually.
1). Create the HTTP transport with the port referred in WSDL.
2). In a process, add "SOAP Request Reply" activity and import WSDL. You will see the transport in the Transport tab
Description:
============
Import of concrete WSDL in TIBCO Designer does not create Transport artifacts when WSDL is created in TIBCO BusinessEvents Studio release 4.0.1 or 5.0.
Environment:
==========
TIBCO BusinessEvents Studio
TIBCO Designer
Symptoms:
=========
Import of concrete WSDL in Designer does not create transport mentioned in WSDL.
Resolution:
==========
WSDL created in BE Studio is correct but since Designer is a static tool so it doesn't create the transport by itself. It must be done manually.
1). Create the HTTP transport with the port referred in WSDL.
2). In a process, add "SOAP Request Reply" activity and import WSDL. You will see the transport in the Transport tab
Issue/Introduction
Import of concrete WSDL in TIBCO Designer does not create Transport artifacts when WSDL is created in TIBCO BusinessEvents Studio release 4.0.1 or 5.0.
Feedback
Yes
No
Powered by
