Configuration in this directory creates a connection factory object in the JNDI store on the PubSub+ appliance, with local transactions support.
msg_vpn_name
- Set todefault
in the example.connection_factory_name
- Set to/JNDI/CF/LocalTransSupport
in the example.
local_transactions_enabled
- Shall be set totrue
to configure a connection factory with local transactions support.
Note: connection factories must have the transport_direct_transport_enabled
input variable disabled to support local and XA transactions. This is automatically ensured in this module if local_transactions_enabled
is true
.
Optional module input variables have the same name as the attributes of the underlying provider resource. If omitted, then the default for the related resource attribute will be configured on the broker. For a list of attributes and the corresponding defaults, see the documentation of "solacebroker_msg_vpn_jndi_connection_factory".
The module provisioned_connection_factory
output refers to the created connection factory.
This example will create the following resources:
solacebroker_msg_vpn_jndi_connection_factory
If you don't already have access to a broker, see the Developers page for options to get started.
The sample is available from the module GitHub repo:
git clone https://github.com/SolaceProducts/terraform-solacebrokerappliance-jndi.git
cd examples/local-transactions-support
Adjust the provider parameters in main.tf
according to your broker. The example configuration shows settings for a local broker running in Docker.
Tip: You can verify configuration changes on the broker, before and after, using the PubSub+ Broker Manager Web UI.
Execute from this folder:
terraform init
terraform plan
terraform apply
Run terraform destroy
to clean up the created resources when they are no longer needed.
For more information, see Connection Factories section in the PubSub+ documentation.