![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Use the Service resource to configure services for your project. Before configuring a service, you will need to have the following in your project:
• WSDL resources for the interfaces the service publishes. You can use abstract WSDL files or WSDL files with concrete endpoint bindings. However, concrete bindings are ignored because the Service will define its own endpoint bindings. You might use a WSDL file with concrete bindings if you are modeling your service on the WSDL of another existing service.
• WSDL resources for any external partner services that operations can invoke. The WSDL files for partner services must have concrete endpoint bindings so that TIBCO ActiveMatrix BusinessWorks BPEL Extension can invoke the service.
• HTTP Connection and JMS Connection shared configuration resources for the transports used by the endpoints.
•
Only the in or in-out message exchange pattern is supported in WSDL files used by the ActiveMatrix BusinessWorks BPEL Extension.See the TIBCO ActiveMatrix BusinessWorks documentation for more information about creating and importing WSDL files into projects and defining HTTP Connection resources. See Working with Orchestration Processes for more information about creating orchestration processes. See Partners for more information about partners and Partner Link Configuration resources.
2. Specify a name for the service in the Name field, and optionally specify a description for the service in the Description field.
4. Click the + button to the right of the box in the Implementation field to add a WSDL file that describes the interface of the service.
5. In the Select a Resource dialog, locate and select the WSDL resource for the service, and select the correct Port Type for the service.
6. Repeat steps step 4 and step 5 as necessary to add more interfaces to the service, if necessary. Interfaces are added as tabs in the Implementation field. Click on the tab of the interface you wish to configure to continue the configuration. Use the Rename button to rename the selected interface, or use the X button to delete an interface, if necessary.
a. Specify a timeout for each operation listed in the operations tab. This timeout applies to how long incoming messages that are routed to a particular running job wait for the job to process them. Messages are discarded after this timeout has been reached.
b. Double click on the Operation Implementation field for each operation and use the Browse button to locate the orchestration process that implements this operation. Only orchestration processes with input partner portTypes that match the operation’s portType are listed. See Input Partners for more information about input partners and Chapter 4, Working with Orchestration Processes for more information about creating orchestration processes.
d. Click the + button to add endpoints. Use the X button to remove endpoints. Use the arrow buttons to move the endpoints up or down.
e. For each endpoint, double click the Endpoint Type field to specify either SOAP or Local. SOAP endpoints allow partners to invoke operations in this service using SOAP over HTTP or JMS. Local endpoints allow only partners contained in the current project to invoke operations within this service.
f. For SOAP endpoints, specify the HTTP Connection or JMS Connection on the Transport tab, specify any transport configuration options, then specify any desired options on the SOAP Details tab. See Service for more information about configuring a SOAP endpoint.
8. If the orchestration implementations within the service invoke partners, the Partner Binding tab allows you to specify Partner Link Configuration resources for the partners. See Partners for more information.
9. Once the service is configured, you can view the WSDL for the service on the WSDL Source tab. You can also use this tab to save a WSDL file with the concrete bindings needed for other services or web clients to invoke operations on this service.TIBCO ActiveMatrix BusinessWorks BPEL Extension allows you save a concrete WSDL file from the Service resource. This WSDL can be used by partner services to call your service. When you save your WSDL file, make certain that the Interface checkbox in the Embed in WSDL field is unchecked (see Figure 31). Checking this box embeds the portType of the interface using a separate namespace, and therefore the portType will not match the namespace of the abstract WSDL. When the Interface checkbox is unchecked, ActiveMatrix BusinessWorks BPEL Extension creates a concrete WSDL with a reference to the interface that partner services can use.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |