Runtime tools : Core components : Operations : Reference : Operation step external definitions
  
Operation step external definitions
The following table shows the tags (corresponding to classes) and tag attributes (corresponding to class variables) used for externalizing client Operation objects. The operation tag can be either "operation", a tag name with a related class set in the toolkit definition file (such as MyOperation), or a specific class name (such as myPackage.MyOperation). See Tag linking for more information on the refFormat tag.
operation or operation <ClassName> tag attributes
Id
The name of the operation step. This is a mandatory attribute.
ImplClass
The name of the class the toolkit is to instantiate if the tag name is "operation". This value overrides any definition for the operation in the toolkit definition file.
Context
The name of the operation context.
serverOperation
The name of the class of the server operation.
serverOperationParentContext
The parent context of the server operation.
XVal
The name of the class implementing the process for validating a cross business operation. This class must implement the OperationXValidate interface. By providing a specific class that implements the business validation for the concrete operation, the applications can use a generic operation class for more than one business operation yet invoke a concrete validation that may be specific to each operation.
Scope
The implementation model for caching operation data. provides the following scopes:
Request Scope: If you do not specify any scope in the operation definition, operation data is disposed after the request.
Flow Scope: The result is stored at flow context level and destroyed along with Flow Processor. Flow scope also supports flow level failover.
Session Scope: The result is stored along with SessionContext and has same lifecycle.
Application Scope: The result is cached in root Context level by default scope manager and opens for extension.
Customization Scope: provides extension points for cache customization. Customization scope is an extension point in btt.xml settings section. You can override the eligibility and potential of cache in the original results and define a new scope based on your business logic.
Expire Time
The expiration time of operation cache. The default value is 0, which means that the result never expires. You can define the expiration time in seconds according to your business requirements. You can also define further expiration control features in ScopeManager extensions, for example, the result expires at a given time or times of day.
refFormat (FormatElement) tag attributes
name
The type of formatter required. The value of this attribute is one of the following:
csRequestFormat (for requests)
csReplyFormat (for responses)
refId
The name of the formatter.
refOpSteps (OperationStep) tag attributes
refId
The name of the collection containing the operation flow.
Go up to
Reference