Server-side service components in the desktop Process Designer

Learn about the tools and components available when building server-side services in the desktop IBM® Process Designer.

Note: The desktop Process Designer is deprecated.

When developing a service diagram in the Designer view in the desktop IBM Process Designer, the following tools and components are available from the palette. Not all tools and components are available for each type of service.

• All service types
• Integration service (deprecated)
• Heritage human service
• Decision service (deprecated)
• IBM Case Manager Integration service

All service types

The following tools and components are available from the palette for all service types:

Table 1. Tools and components available from the palette for all service types

Component icon	Description
Selection tool	Use to select and move components on the diagram.
Sequence Flow tool	Use to connect service components to establish the order in which the steps in the service occur.
Server Script	Use when you want to write JavaScript to run on the Process Server in the service context. The Server Script component is useful for parsing through variables and executing programmatic commands.
Server Scriptlet	Use to bind blocks of formatted text (for example, HTML, XML, or XSLT) directly to a service variable. This eliminates the need to store large blocks of text in default values for variables.
Decision Gateway	Use to model a point in the process execution where only one of several paths can be followed, depending on a condition.
End Event	Use to end service execution. For services that contain multiple paths, each path requires its own end event. Note: An end event is automatically included each time you create a service.
Note	Use to add information about the overall service or each step in the service to the diagram. Adding notes helps other developers understand your design.
Error End Event	Use to purposely throw an error and end processing. You might, for example, use an Error End Event component if you return too many rows from a database (over a limit that is normal and would bog down the server).
Invoke UCA	Use to invoke an undercover agent (UCA) from your service.
Error Intermediate Event	Use to listen for errors from the service component to which it is attached.
Intermediate Tracking Event	Use to indicate a point in a service at which you want IBM Business Process Manager to capture the runtime data for reporting purposes. For more information about tracking data, see Enabling processes for tracking and reporting.
Modify Task	Use to change the priority, due date, status, or other aspects of a task.
Nested Service	Use to incorporate other services in your current service. Nested services are generally defined to perform specific, repeatable functions such as exception handling routines, integration with outside systems, or data manipulation. Nested services are often used in multiple process applications and likely reside in a toolkit. Note: Heritage human services can be nested only within other heritage human services. Ajax services cannot be nested. Note: You must use a nested service to invoke an Advanced Integration service.
Send Alert	Use to send task-related alerts (deprecated). In prior releases, the Send Alert component was used to send alerts to an IBM Process Portal user. Starting in IBM Business Process Manager V8, alerts can be retrieved only with the TWSearch JavaScript API by querying on tasks with the status of Alert.

Integration service (deprecated)

The following tools and components from the palette are available for Integration services only.

Table 2. Tools and components that are available for Integration services only

Component icon	Description
Web Service Integration	Use to run an external web service. This component enables you to supply a WSDL URI and then use any of the available services.
Java Integration	Use to call methods from a Java class. You can use the methods to complete tasks like reading or writing files or sending SMTP mail.
Content Integration	Use to integrate with an IBM Enterprise Content Management system.

Heritage human service

The following tools and components from the palette are available for heritage human services only.

Table 3. Tools and components that are available for heritage human services only

Component icon	Description
Coach	Use to implement the interfaces for your heritage human services so that users can participate in a business process. For more information, see Building coaches. The coach tool is shared with the client-side human services. For more information, see Tools available from the client-side human services palette.
Heritage Coach (deprecated)	Use to implement the interfaces for your heritage human services so that users can participate in a business process. For more information, see Building heritage coaches. This component is used for heritage human services only.
Postpone Task	Use to halt processing without changing the status of a task. This component is used for heritage human services only.

Decision service (deprecated)

The following tools and components from the palette are available for Decision services only.

Table 4. Tools and components that are available for Decision services only

Component icon	Description
Decision Table	Use to build conditions for your Decision services.
JRules Decision Service	Use to include decision services available on an IBM Operational Decision Manager Rule Execution Server instance.
BAL Rule	Use the Business Action Language (BAL) Rule component to author business rules using natural language technology

IBM Case Manager Integration service

The following tools and components from the palette are available for IBM Case Manager services only.

Table 5. Tools and components that are available for IBM Case Manager services only

Component icon	Description
IBM Case Manager Integration	Use to integrate a case management case in IBM Case Manager.