Example Project Folder Structure
Suppose you import the example WSDL above into a Studio project called Library. The imported and generated project artifact names would appear as shown in the Project Folders and Resources column in the table below. Folders that are added by TIBCO BusinessEvents are shown in bold. The example is a concrete WSDL. In the WSDL Source column the source of folder and resource names is given for abstract as well as concrete WSDL sources.
Project Folders and Resources | Project Resource Type | WSDL Source |
---|---|---|
Library
|
Project root folder | N/A |
getBook/
|
Folder | For concrete WSDLS:
<wsdl:service> For abstract WSDLS:
|
GetBookPortType/
|
Folder | For abstract and concrete WSDLs:
<wsdl:portType> |
getBook/Events/
|
TIBCO BusinessEvents folder | |
GetBookRequestMessage
|
Event | <wsdl:input>
For abstract WSDLs, in
For concrete WSDLs, in
|
GetBookResponseMessage
|
Event | <wsdl:output>
For abstract WSDLs, in
For concrete WSDLs, in
|
getBook/RuleFunctions/
|
TIBCO BusinessEvents folder | |
GetBook
|
Rule function | <wsdl:operation>
For abstract WSDLs, in
For concrete WSDLs, in
|
getBook/Rules/
|
TIBCO BusinessEvents folder | |
GetBookPortType
|
Folder | Abstract WSDL:
<wsdl:portType name> Concrete WSDL: <wsdl:binding type> |
GetBook
|
Rule | <wsdl:operation>
For abstract WSDLs, in
For concrete WSDLs, in
|
Import from Concrete WSDLs Only If the import is from a concrete WSDL, the HTTP Connection resource, Channel resource and Destination resource are added using details in the
If the import is from an abstract WSDL, you must create these resources manually. |
||
getbook/Transports/
|
TIBCO BusinessEvents folder | |
getBookHTTPPort
|
HTTP Connection | <wsdl:port>
The host and port come from the
|
Service/
|
TIBCO BusinessEvents folder | |
getBook
|
Channel
See Channel Folders . |
<soap:address location>
(from the last part of the location URL) |
Service_getBook
|
Destination | <soap:operation soapAction>
|