Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 10 Palette Reference : Service

Service
Resource
A Service describes the following:
The Service resource has a slightly different set of configuration fields depending on whether you are configuring a TIBCO ActiveMatrix BusinessWorks service or a ActiveMatrix BusinessWorks BPEL Extension service. The Implementation Type field is used to specify which type of service you are configuring. This section describes the configuration of a ActiveMatrix BusinessWorks BPEL Extension service. See TIBCO ActiveMatrix BusinessWorks Palette Reference for more information on configuring TIBCO ActiveMatrix BusinessWorks services.
Before creating a service, you will need to create the following:
During deployment, Service resources must be added to a Process Archive. Although it is possible to add a Service resource to a Shared Archive, the resource will not properly function when located in a Shared Archive. Add your Service resources only to Process Archives.
Also, when creating your Enterprise Archive file, the menu item Tools > Create Project EAR does not add Service resources to the Process Archive. You must add any Service resources to the Process Archive by selecting the Processes tab of the Process Archive and clicking the Add a Process Starter to This Archive button.
See Chapter 7, Services and Partners for more information about defining services.
Configuration
The Configuration tab has the following fields.
This field specifies which type of Service this resource uses. The configuration of TIBCO ActiveMatrix BusinessWorks services is slightly different from ActiveMatrix BusinessWorks BPEL Extension services. If you are configuring a ActiveMatrix BusinessWorks BPEL Extension service, select ActiveMatrix BusinessWorks BPEL Extension in this field. If you are configuring a TIBCO ActiveMatrix BusinessWorks service, select ActiveMatrix BusinessWorks Process Definition in this field.
See TIBCO ActiveMatrix BusinessWorks Palette Reference for more information on configuring TIBCO ActiveMatrix BusinessWorks services.
This field contains a set of tabs, one for each interface of the service. Use the + or X button to add or remove interfaces from this field. Adding an interface brings up the Select a Resource dialog where you can select the WSDL resource that describes the correct interface. Use the Rename Current Interface button to rename the currently selected interface.
Namespace for the WSDL file of the interface. You can click the Go To Refinanced Resource button to view the WSDL file.
This sub-tab contains a table of all operations defined in the interface. This table allows you to specify the orchestration process that implements each operation. Use the Adjust for WSDL Updates button when the WSDL resource changes.
Name of the operation. This column is a read-only list of operations contained in the interface.
Timeout (in seconds) for incoming messages that are not consumed. For example, an incoming message may be for an existing orchestration process, but the orchestration process has not yet reached the point where it is ready to receive the message. Also, you may have incoming unsolicited messages that do not match any existing orchestration process. You can handle unsolicited messages by creating a TIBCO ActiveMatrix BusinessWorks automated process definition to handle them.
Operation Implementation
Double click on this field and use the Browse button to locate the orchestration process that implements each operation. Only orchestration processes whose Input Partners match the operation can be selected.
Use the + button to add endpoints, use the X button to delete endpoints, and use the arrow buttons to move the selected endpoint in the list.
Local — A local endpoint is available to consumers within the same process engine. This type of endpoint provides a highly efficient way for local services to invoke each other without incurring the overhead of using a network transport.
SOAP — A SOAP endpoint is used to expose the service by way of the SOAP protocol to other partner services or web clients.
Use the Browse button to select a transport. HTTP Connection or JMS Connection resources can be used as transports.
Use Basic Authentication
When checked, this field specifies that incoming SOAP requests must supply a valid username and password.
The user name and password specified in the incoming request must exist in the domain (users are created and managed in the domain using TIBCO Administrator).
This field specifies the name of the destination for incoming JMS messages for this service. The syntax of the destination name is specific to the JMS provider you are using. See your JMS provider documentation for more information about destination names.
Note: If you are using TIBCO Enterprise Message Service as your JMS provider, you can use the Browse button next to this field after specifying a valid connection in the JMS Connection field. The Browse button displays a list of configured destinations in the JMS server that are appropriate for this activity.
This field specifies the type of incoming messages on the specified destination. Can be either Text Message or Bytes message.
This field specifies the acknowledgement mode to use for incoming messages. Can be one of the following:
Client — the message will be acknowledged when the process implementing the operation ends successfully.
Dups OK — the message is acknowledged automatically when it is received. JMS provides this mode for lazy acknowledgement, but TIBCO ActiveMatrix BusinessWorks acknowledges messages upon receipt.
TIBCO EMS Explicit Client Acknowledge — (only available for TIBCO EMS) the message will be acknowledged at a later point by using the Confirm activity. The session is not blocked and one session handles all incoming messages for each process instance. If a message is not confirmed before the process instance ends, all messages received in the same session are redelivered.
This field is available when a JMS transport is selected and Client is selected as the Acknowledge Mode. If the JMS Destination Type is Topic, this field is read-only. If the JMS Destination Type is Queue, the value of this field can be altered.
This field specifies the maximum number of JMS sessions to create for incoming queue messages.
When a JMS queue message is received, the session is blocked until the message is acknowledged. Because the acknowledgement can comes at a later time when the process ends, this field allows you to specify a maximum number of new sessions to create to handle incoming messages.
Once the maximum number of sessions is reached, no new incoming messages can be processed. Once an incoming message is confirmed, the total number of active sessions is decreased and another incoming message can be processed.
This field is available when a JMS transport is selected and Topic is selected as the JMS destination type.
This field allows you to specify whether each operation requires a durable topic subscription.
The SOAP binding style for operations that do not explicitly set their binding style. You can specify either Document or RPC style.
Specify either SOAP 1.1 or SOAP 1.2 for the version of the SOAP specification to which incoming messages should comply.
Select each operation from the drop down list to specify the SOAP Action, Style, or Encoding for the operation.
The Advanced button allows advanced configuration of SOAP headers on BPEL endpoints for inbound service request. These headers can be mapped into a context object which is made available as service context in the orchestration through the Get Context activity.
The soapAction that is expected from incoming SOAP requests. This field is required, and by default, the operation name is used as the soapAction. Each operation in an interface must have a unique value for SOAP Action.
The SOAP binding style for the selected operation. You can specify either Document or RPC style, or you can specify that the value in the Default Style field should be used.
The encoding type for the body of the SOAP input and output messages. This can be either literal or encoded.
When encoded is specified, you can optionally specify the namespace for input, output, and fault messages.
Advanced SOAP Settings
For each operation, you can specify advanced configuration options. To access the advanced configuration options, perform the following:
1.
2.
3.
4.
Click the Advanced button next to the operation name.
The Advanced SOAP Settings dialog appears. The tabs on the Advanced SOAP Settings dialog are the same as the dialog in TIBCO ActiveMatrix BusinessWorks. Refer to Chapter 16, "Service Palette" of the TIBCO ActiveMatrix BusinessWorks Palette Reference for more information on the tabs of this dialog.
WSDL Source
The WSDL Source tab displays the concrete WSDL interface file that is generated based on the information specified on the Configuration tab of this resource. This tab has the following fields.
The Service URI portion of the URL that can be used to retrieve the WSDL file. For consumers to retrieve WSDL files from TIBCO ActiveMatrix BusinessWorks, you must define a process definition that accepts HTTP requests and uses the Retrieve Resources activity to generate the WSDL file. See TIBCO ActiveMatrix BusinessWorks Palette Reference for more information.
http://<host>:<port>/<serviceURI>?wsdl
where <serviceURI> is the value in this field.
Target Namespace
Check one or more of the following to embed the selected item(s) in the concrete WSDL file instead of using import statements:
Interface — When checked, specifies that all referenced WSDL files should be included inline in the concrete WSDL file. Otherwise, all referenced WSDL files are imported. Do not use this option if you plan on distributing the concrete WSDL to other services.
Types — When checked, specifies that all referenced XSD files should be included inline in the concrete WSDL file. Otherwise, all referenced XSD files are imported.
JNDI Properties — When checked, specifies that JDNI properties should be included inline in the service specification in the WSDL Source tab.
Overview
The Overview tab provides a tree view of the service that you can expand and collapse to view the exposed endpoints and operations for the service.
 

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved