build-resource-proxy¶
Tool that compiles and links a resource proxy for a specific XA resource.
XA specification uses the term resource proxy, hence casual uses the same term. If you have experience with Tuxedo, this is the same thing as TMS
prerequisites¶
casual is installed and CASUAL_HOME is set to the install path.
The wanted resources have to be configured in $CASUAL_HOME/configuration/resources.(yaml|json|xml...).
example¶
Lets say we have configured a db2 resource in $CASUAL_HOME/configuration/resources.yaml:
resources:
- key: db2
server: rm-proxy-db2-static
xa_struct_name: db2xa_switch_static_std
libraries:
- db2
paths:
library:
- ${DB2DIR}/lib64
We just use the key to look up the configuration, and use this to compile and link the wanted resource-proxy
$ casual-build-resource-proxy --resource-key db2
Will produce a server (resource-proxy) with the name rm-proxy-db2-static. The transaction-manager will use the same configuration to know which resource-proxy to spawn for a specific key in domain-configuration.
options¶
There are a few tweaks you can use when building a resource-proxy. The most common is probably to provide compiler-directives and link-directives for your specific platform.
$ casual-build-resource-proxy --help
NAME
casual-build-resource-proxy
DESCRIPTION
builds a resource proxy
OPTIONS
name value(s) description
---------------------- -------- ------------------------------------
--output <value> name of the resulting resource proxy
--resource-key <value> key of the resource
--compiler <value> compiler to use
--compile-directives <value> additional compile directives
--link-directives <value> additional link directives
--system-configuration <value> path to system configuration file
--verbose <value> verbose output
--keep-source <value> keep the generated source file
--help <value> shows this help information
regarding this documentation¶
This information is targeted for all roles