|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |
1. Open a project in TIBCO Designer and create one or more process definitions that implement operations you wish to expose as web services. The input, output, and error schemas for each process definition must be specified as schema elements defined in the XSD. See Start Activity and End Activity for more information about defining input, output, and error schemas.
4. Choose Tools or Multi-User > Generate Web Service > From Process from the pop-up menu.
6. Click Generate to create a Service resource and WSDL file for the selected process definitions.The Service resource is named intf<processDefinitionName>-service and the WSDL file is named intf<processDefinitionName>. The service and process definition stubs are placed in the location specified in the Generate Web Service dialog.
7. Click the intf<processDefinitionName>-service resource in the project tree to display the service. Ensure the endpoint bindings are specified correctly. For HTTP transports, you may need to specify the Endpoint URI. For JMS transports, you must specify the destination name and other JMS configuration information. See the description of the Service resource in TIBCO ActiveMatrix BusinessWorks Palette Reference for more information about specifying endpoint bindings.
2. If your project is not open, open your project in TIBCO Designer. If your project is already open in TIBCO Designer, choose Resources > Refresh from the menu.
5. Choose Tools or Multi-User > Generate Web Service > From WSDL from the pop-up menu.
7. Click Generate to create a Service resource and process definition stubs for the operations in this WSDL file.The Service resource is named <interfaceName>-service and the process definition stubs are named <portType><operationName>. The service and process definition stubs are placed in the location specified in the WSDL to Process dialog.
8. Click the <interfaceName>-service resource in the project tree to display the service. Ensure the endpoint bindings are specified correctly. For HTTP transports, you may need to specify the Endpoint URI. For JMS transports, you must specify the destination name and other JMS configuration information. See the description of the Service resource in TIBCO ActiveMatrix BusinessWorks Palette Reference for more information about specifying endpoint bindings.
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |