Defining service definitions

Service definitions are a representation of the logic that regulates document workflow services.

The Service Builder is a graphical interface that enables you to create a graphical representation of these services, in the following situations:

Services can be accessed using the following mechanisms:

Note: If you try to configure more than one action serially using the Service Definition Framework, the Applications Manager throws an error message, "A continue link must be attached to the next condition or action." To avoid this error, group these actions and replace them with one service.

Service nodes

Service nodes contain the logic that you can use to build a service definition.

The following service nodes are available from the Service Palette:

Connector nodes are only available from the right-click menu.

Transport nodes

Transport nodes forward messages, allowing Sterling Selling and Fulfillment Foundation to communicate with external systems. Transports (and the entire service) can be classified into the following categories:

You may use either type, depending on your needs. The following sections list the types of synchronous and asynchronous transport types.

You can add a transport node by dragging it from the pallet into the work area.

Synchronous services forward messages immediately. Sterling Selling and Fulfillment Foundation supports the following synchronous transport types:

Asynchronous services store and forward messages. They queue up messages in a database or a queuing mechanism, which allows you to reprocess exceptions, if any, at a later time. Sterling Selling and Fulfillment Foundation supports the following asynchronous transport types:

Each transport type has the following sender and receiver aspects:

Whether a transport is a sender or receiver depends on how you have connected the flow of logic to be directed.

Component nodes

Component nodes format or translate data. Sterling Selling and Fulfillment Foundation supports the following components:

You can add a component node by dragging it from the pallet into the work area.

Adapter nodes

Adapter nodes allow you to implement a Sterling Selling and Fulfillment Foundation Adapter with an external system.

Sterling Selling and Fulfillment Foundation supports the IBM® Sterling B2B Integrator.

Connector nodes

Connector nodes allow you to link nodes together without adding any additional logic. This allows you to complete a service. The types of available connector nodes are as follows:

You can add a connector node by right-clicking in the work area and selecting from the above connector node types.

Criteria of a complete service flow

The following conditions must be met in order to save a service: