If you have specified at the application level that an application is a client and a server, you can identify which Ispecs perform particular OLTP functions.
At the Ispec level, you can:
Specify an OLTP Service Name
Specify whether the Ispec can process OLTP transactions
Specify whether the Ispec can reply to an OLTP transaction
Notes:
Several Ispecs can specify the same OLTP Service name. When this is done on MCP based hosts, all of the Ispecs sharing a particular Service name must be in the same subsystem.
If a Service name is not specified, the default Specification Service name (or on MCP based hosts, the default Subsystem Service name) is used for Ispecs that can process OLTP transactions.
When a transaction is received for an Ispec, Agile Business Suite does not check that the specified Service name for the Ispec has been used. Any Service name associated with the particular server is valid.
If an Ispec is capable of receiving an OLTP transaction, it can automatically reply to an OLTP transaction. (An Ispec can be OLTP reply-capable without being able to receive an OLTP transaction. Such an Ispec would be invoked by a Recall command.)
OLTP Ispec Configuration Properties
The following three configuration properties of the Ispec are specific to OLTP. They specify an Ispec that can receive, and also reply to, an OLTP transaction:
AutomaticEntryCapable
Select this check box when the Ispec can be used with an Automatic entry logic commands to send a transaction to an OLTP server, or to access a reply received from an OLTP server.
This property relates to a client application. If it is set, an Automatic Entry buffer description is generated for this Ispec in the client application, and the Ispec name can be used in the commands for Automatic entries.
Accept OLTP Transaction
Set this property to True to specify that the Ispec is capable of providing an OLTP service; that is, the Ispec can accept OLTP transactions. The transaction is available in the Ispec input buffer, and the _Prepare and Main method of the Ispec is executed to process the transaction.
In order for this Ispec to receive OLTP transactions, you must specify your application as an OLTP server in the Configuration you use to build your application.
If you set it to True, you must also specify that your application or Subsystem (in the Segment configuration properties under the OLTP category) or the Ispec (using the OLTP Service Name Ispec configuration property under the OLTP category) is a specified service. This field relates to a server application.
Leave this property set to its default value (False) to specify that the Ispec is not able to receive OLTP transactions for processing. If it is set to False, the Ispec can still participate in processing an OLTP transaction if your application (or another Ispec) is a specified service, because the Ispec can be recalled from another Ispec within that application in response to an OLTP transaction. In this case, _Construct method of the Ispec is executed.
If you set this property and your application or the Ispec is a specified service, the Ispec can receive and process an OLTP transaction.
By default, it is set to False.
OLTP Reply
Set this property to True to specify that the Ispec can reply to an OLTP transaction by using a Recall logic command. If you set it, the Ispec View definition is generated for loading into the OLTP CRM. This property relates to a server Specification.
By default, it is set to False.
Note: COPY.FROM Ispecs cannot accept OLTP transactions.
OLTP Component Options
Use the OLTP Service Name Ispec configuration property under the OLTP category to enter the OLTP service name to be associated with this Ispec.
An entry is not required if you have specified a service name in the Default Service Name configuration property under the OLTP category for the Segment.