# @jpd:process Annotation

Contains the process logic settings for a business process.

Syntax

@jpd:process [binding="webservice | ebxml | rosettanet"] process::

<process name="processname" [freezeOnFailure="true | false"] [onSyncFailure="rethrow | rollback"] [retryCount="<count>"] [retryDelay="<delay>"]>

Note: See also the stateless attribute in the following section.

Attributes

binding

This property specifies whether the business process uses the Web service, ebXML, or RosettaNet protocol. The default value is webservice. If your business process is an ebXML or a RosettaNet process, select ebxml or rosettanet. In keeping with your selection in the Property Editor, an attribute is written to the @jpd: process annotation in the source code. For example:

@jpd:process binding="rosettanet" process::

To learn about ebXML and RosettaNet business processes, see Building ebXML Participant Business Processes and Building RosettaNet Participant Business Processes.

name

This is the name of your business process, which is displayed throughout the WebLogic Workshop application, including the WebLogic Integration Administration Console. You can change the name by clicking on this property in the Property Editor and entering a new name.

freeze on failure

When a business process fails and there is no exception handler configured to handle the exception thrown, the business process is placed into an aborted state and no recovery is possible. However, if the business process is configured to freeze on failure, the business process rolls back to the last commit point and the state is persisted if it fails. The process can then be restarted from the WebLogic Integration Administration Console. To configure a business process to freeze on failure: select true from the freeze on failure drop-down menu.

To learn how to unfreeze business processes in the WebLogic Integration Administration Console, see Process Instance Monitoring in Managing WebLogic Integration Solutions at http://edocs.bea.com/wli/docs81/manage/processmonitoring.html.

on sync failure

This property only applies to your process if it is configured to be a synchronous subprocess; it is ignored for any other business processes. If a synchronous subprocess fails, the default behavior is to mark it as rollback, which causes both the subprocess and the parent process to rollback. However, if the on sync failure property is set to rethrow, only the subprocess is rolled back. To learn more about synchronous subprocesses and the on sync failure property, see "Working with Subprocesses" in Building Synchronous and Asynchronous Business Processes.

retry count

Specify how many times, after the first attempt, the process engine should try to execute the business process.

If your business process contains an asynchronous client request node or multiple client request nodes, any one of which is asynchronous, then you can set the retry count for the business process. You cannot set the retry count property for business processes that contain only synchronous client request nodes (that is, Client Request with Return nodes).

retry delay

Specify the amount of time (in seconds) you want to pass before a retry is attempted.

If your business process contains an asynchronous client request node or multiple client request nodes, any one of which is asynchronous, then you can set the retry delay for the business process. You cannot set the retry delay property for business processes that contain only synchronous client request nodes (that is, Client Request with Return nodes).

stateless

This property is read only; it cannot be edited. It specifies whether your business process is stateless (property displays true) or stateful (property displays false). To learn more about stateless and stateful business processes, see Building Stateless and Stateful Business Processes.