Odin Business Execute v1
The Odin Business Execute Node executes calls against the Odin Business service.
Properties
Connection
Type: Connection Input
The Connection for Odin Business Execute and Odin Business Complete should be the same.
Server - Host name or IP address of a server where OA Billing Application is installed
Type: String
Port - The xmlrpcd port on which the OA Billing Core server listens. The default is 5224.
Type: Int32
Username - Username to log in to the control panel
Type: String
Password - Password to log in to the control panel
Type: Password
UseSsl - True if service is set up with encryption
Type: Boolean
Container
Type: String Input
Provided by the sample, for example, BM_Container.
Object
Type: String Input
Provided by the sample, for example, BM_Object.
Method
Type: String Input
Provided by the sample, for example, AccountAdd_API.
Locale
Type: String Input
The language of the response, for example, nl_NL. This Property can be left blank.
TransactionId
Type: String InputOutput
The ID of a transaction that should be used. Leave blank when AutoCommitTx is True.
AutoCommitTx
Type: Boolean Input
True when a single call is made. False if a transaction should be used. See Using Transactions.
ParameterXml
Type: Xml Input
The ParameterXml Property contains the request sent to the server. Select a sample to view examples.
ResultXml
Type: Xml Output
Response returned from the server.
Remarks
Using Transactions
OA Billing uses transactions to process requests. If a request succeeds, OA Billing commits the changes. If it fails, OA Billing rolls back the changes.
XML-RPC supports transactional requests. If you do not specify a transaction ID, OA Billing creates a transaction, processes the request, commits or rolls back the changes, and closes the transaction. Set AutoCommitTx to False to prevent an immediate commit.
With automatic commit disabled, OA Billing creates a transaction, processes the request, stores the changes, and returns the transaction ID. Include that ID in subsequent requests to join them to the existing transaction.
The transaction originator must explicitly commit or roll back the transaction by passing the returned ID to the Odin Business Complete Node. Otherwise, the transaction remains open and may lock later requests to the object or interfere with the control panel and other PBA functions.