Siebel Financial Services eBusiness Application Integration Guide > Siebel Financial Services eAI Architecture > Industry XML Connector >

Industry XML Transaction Manager


The Industry XML Transaction Manager is responsible for interfacing with the Siebel database. It retrieves data and executes database operations for financial services industry integration architecture. The Industry XML Transaction Manager can also extract query specifications entered by users in the memory cache, and run them through the connector modules to send a query message to external systems. Furthermore, it can undo operations if it receives an error in the fault section of the response message indicating that the external systems failed to execute the specified operations.

Table 2 lists all the user properties for Industry XML Transaction Manager.

Table 2. Industry XML Transaction Manager User Properties
Name
Value
Description
DispatcherMapName
IXMLDispMap
Transaction Manager uses this map to tag the Body information for other components. This value can also be set as a runtime input argument.
IgnoreSvcMethodArgs
true or false
This parameter allows runtime input arguments.
SaveInFileForRollback
<filename>
The filename to save current record for future rollback when rollback operation is desired.
SaveInMemForRollback
<filename>
The session key to set or look up the record cached in memory if rollback operation is desired.
XXX (Operation)
ServiceName/MethodName/Argument
Type of operation to use. For example, Name = IXMLOperation_QUERY, Value= EAI Siebel Adapter/Query/PrimaryRowId;!SiebelMessage.

The Industry XML Transaction Manager uses the prebuilt methods described in Table 3 to process inbound or outbound integration.

Table 3. Industry XML Transaction Manager Methods
Method
Default Display Name
Description
Execute
Execute Transaction
This method can be used for inbound or outbound purpose, as long as the integration object instance is provided. You should use the Execute Outbound method when Row Id is the only available input.
ExecuteOutbound
Execute Outbound
This method can only be used for outbound purpose to execute operation specified in input arguments. See Table 6.
ExecuteSave
Execute and Save
This method executes outbound operation specified in input arguments and also saves the transaction into memory or file. See Table 7.

The Industry XML Transaction Manager business service uses combinations of user property, method, and method arguments to achieve different tasks.Table 4 lists all the method arguments available to use with The Industry XML Transaction Manager business service.

Table 4. Industry XML Transaction Manager Method Arguments
Argument
Default Value
Description
OnlyIOI
false
This is only used for Inbound integration. The inbound message may contain header, body, and envelope portion. When Transaction Manager takes the proper operation against the Siebel application, the integration object instances for response is generated as well. All information from the request message is dropped if this value is set to true. Therefore, the Industry XML Converter and Industry XML Data Transformation Engine do not need to deal with the overheads. If this is not set to true, then request information will still be carried over.
XMLHierarchy
N/A
Property set in internal integration object hierarchy.
IXMLMapPath
N/A
Store the key value for the dispatch map. Industry XML Transaction Manager will use it to look up the value, and attach necessary value into integration object instance.
PrimaryRowId
N/A
The PrimaryRowId of the integration object.
SiebelFINSOperationOut
N/A
The outbound operation Industry XML Transaction Manager takes through its user property.
SearchSpec
N/A
The Search Specification for query.
PlaceToSave
mem
PlaceToSave indicates whether the rollback instance is getting from "file" or "mem." Valid values are "file" or "mem."
RollbackInError
false
Indicates whether the transaction should be rolled back. Valid values are "true" or "false."

Although these arguments are available to use with the Industry XML Transaction Manager, not all can be used with each method. Table 5, though Table 7 list all the method arguments for each method.

Table 5. Method Arguments for Execute Method
Argument
Display Name
Data Type
Type
Optional
OnlyIOI
Only produce Integration Object Instance
String
Input
Yes
XMLHierarchy
XML Property Set
Hierarchy
Input/Output
No
RollbackInError
Is Rollback in Error
String
Input
Yes

Table 6. Method Arguments for ExecuteOutbound Method
Argument
Display Name
Data Type
Type
Optional
IXMLMapPath
IXML Map Path
String
Input
No
PrimaryRowId
Primary Row Id
String
Input
Yes
SiebelFINSOperationOut
Outbound Operation
String
Input
No
SearchSpec
Search Specification
String
Input
Yes
XMLHierarchy
XML Property Set
Hierarchy
Input/Output
No

Table 7. Method Arguments for ExecuteSave Method
Argument
Display Name
Data Type
Type
Optional
IXMLMapPath
IXML Map Path
String
Input
No
PrimaryRowId
Primary Row Id
String
Input
Yes
SiebelFINSOperationOut
Outbound Operation
String
Input
No
SearchSpec
Search Specification
String
Input
Yes
XMLHierarchy
XML Property Set
Hierarchy
Output
No
PlaceToSave
Place To Save
String
Input
Yes


 Siebel Financial Services eBusiness Application Integration Guide 
 Published: 18 April 2003