Service

Shared Configuration

A Service shared configuration resource describes an interface and its associated operations. The also specifies a set of endpoint bindings that expose the service to potential clients over specific transports.

 

Note: The user interface for the Service shared configuration resource can change depending upon the additional products you have installed. For example, the ActiveMatrix BusinessWorks BPEL Extension offers more options when configuring the Service resource. When you install a product that extends the Service resource, a new field named Implementation Type appears that allows you to specify the type of service you want to configure depending upon the product you select. For more information about configuring a Service resource using those products, see the documentation for the products you have installed. This section describes the base ActiveMatrix BusinessWorks Service resource

Before creating a Service resource, you must create the following resources:

  • A WSDL file that contains an abstract interface description. The interface can include one or more operations.

  • Process definitions provide the implementation for each operation in the service’s interface. You can specify the same process definition for more than one operation.

  • Either an HTTP Connection or JMS Connection shared configuration resource that specifies the transport used by clients of the service.

  • If you want to pass context information from the incoming request (for example, user name or security certificate), create a Context Resource that specifies the context data you want to use.

Warning: 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 does not function properly 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 only adds processes with process starters to the Process Archive for the project. You must add any Service resources to the Process Archive by selecting the Processes tab and clicking the Add a Process Starter to this archive button.

To define a Service resource, follow this general procedure:

Procedure 

  1. Provide an abstract WSDL file (see WSDL) that describes the interface to the service.

  2. For each operation in the interface, specify a process definition that implements the operation.

  3. Specify one or more endpoint bindings to expose the service to potential clients.

  4. For each endpoint binding, specify a transport configuration (either HTTP Connection or JMS Connection).

  5. Specify any transport-specific information, such as endpoint URL for HTTP transports or JMS Destination Name for JMS transports.

  6. Specify any SOAP details, such as SOAP Version or encoding for each operation.

  7. Specify attachments, headers, or context information for input and output messages, if necessary.

Note: Only Bytes Message must be used when using MTOM attachments

For more information about services, see TIBCO ActiveMatrix BusinessWorks™ Process Design.