4.2.3 Transaction Coordinator Properties

Under tmmConfiguration, provide information to configure MicroTx.

Property	Description
tmmAppName	Enter the name of the MicroTx application that you want to create. When you install MicroTx, Helm creates the MicroTx application with the name that you specify. Note down this name as you will need to provide it later. For example, tmm-app.
tmmid	Enter a value to uniquely identify each instance of MicroTx that you install. The unique identifier must have 5-characeters and can contain only alphanumeric characters (a-z, A-Z, and 0-9). For example, TMM01. Use this ID to identify MicroTx when there are multiple installations. You cannot use this ID to differentiate between replicas of a single instance of MicroTx installation as all the replicas have the same ID. You can't change this value after installing MicroTx.
port	Enter the port over which you want to internally access MicroTx within the Kubernetes cluster where you will install this service. Create the required networking rules to permit inbound and outbound traffic on this port. Note down this number as you will need to provide it later. For example, 9000.
tmmExternalURL	Enter the details required to create the external URL to access MicroTx from outside the Kubernetes cluster where you have deployed the service. Enter the protocol, host, and port number to access the Istio ingress gateway. See Access MicroTx.
httpClientTimeoutInSecs	Specify the maximum amount of time, in seconds, for which the HTTP callback API requests sent by the MicroTx coordinator to the participant services remains active. Enter an integer between 0 to 900. The default value is 180 seconds and the maximum value is 900 seconds. If you set this value to 0, then MicroTx does not enforce any limit. When the coordinator sends a HTTP callback API request to the participant services, the participant services must respond within the time period that you specify. If the participant service does not respond within the specified time period, the HTTP request sent by the coordinator times out.
xaCoordinator, lraCoordinator, or tccCoordinator	Set enabled: "true" for the transaction protocols that your microservices use. MicroTx supports three distribution transaction protocols: XA, Saga, and TCC. If you want to nest an XA transaction within an Saga transaction, set enabled: "true" for both xaCoordinator and lraCoordinator.
txMaxTimeout	Only for the XA transaction protocol. Specify the maximum amount of time, in milliseconds, for which the transaction remains active. If a transaction is not committed or rolled back within the specified time period, the transaction is rolled back. The default value is 600000 ms.
narayanaLraCompatibilityMode	Only for the Saga transaction protocol. Set enabled to true only when you want to use Saga participant applications that were implemented to work with the Narayana LRA Coordinator and now would participate in Saga transactions using MicroTx. Enable this mode to ensure that the MicroTx Saga APIs return the same response data that Narayana LRA Coordinator APIs return.
maxRetryCount	The maximum number of times that the transaction coordinator retries sending the same request again in case of any failures. For example, 10.
minRetryInterval	The minimum interval, in milliseconds, after which the transaction coordinator retries sending the same request again in case of any failures. The default value is 1000 ms.
maxRetryInterval	The maximum retry interval, in milliseconds, before which the transaction coordinator retries sending the same request again in case of any failures. For example, 10000.
skipVerifyInsecureTLS	Oracle recommends that you set this value to false and set up a valid certificate signed by trusted authorities for secure access. When you set this value to false, the transaction coordinator accesses the participant applications over the HTTPS protocol with a valid certificate signed by trusted authorities. The default value is false. If you set this value to true, the transaction coordinator can access the participant application's callback URL, without a valid SSL certificate, in an insecure manner. Caution: Do not set this value to true in production environments.
countersUpdateInterval	Enter a value between 120 to 1800 seconds to specify data collection time interval or the rate at which information about the most recent transactions is updated on the MicroTx console. If you enter 300 seconds, information about the most recent transactions is updated every 300 seconds on the console. The default value is 120 seconds. You can also update this value in the MicroTx console by changing the value in the Interval box.