NonStop Server Guide for BEA WebLogic Server 8.1

XA Resource Manager (XARM)
HP NonStop Server Guide for BEA WebLogic Server 8.1—529891-001
6-2
Configuring the WebLogic Server XA Resource
Object
Configuring the WebLogic Server XA
Resource Object
To configure the NonStop server XA resource object into a WebLogic Server, you must
define a startup class. A startup class is a special class that implements the
T3StartupDef interface.
This startup class is loaded by the WebLogic Server as part of the WebLogic Server
startup. For the NonStop server, the startup class WLSNonStopTxHelper has to be
configured for every server in the domain.
This class, when instantiated, constructs the Java XA resource object for TMF and
registers that resource as a static resource manager with the WebLogic Server. The
object is also published in the JNDI as a non-replicated custom object so that the
WebLogic Server does not attempt to replicate it to other servers in the cluster.
The WLSNonStopTxHelper, when creating the Java XA resource, passes in some
configuration information to the Java object so that the communication between the XA
resource object and TMF can be realized. You can provide these parameters to the
startup class in a property file or as Java system properties. If specified, the Java
system property for a parameter takes precedence.
To specify the property file explicitly for an instance, set the Java system property
hp.nsk.xares.properties to refer to the properties file. Use absolute paths to
specify the file so that the file can be opened and processed regardless of the current
directory of the WebLogic Server instance on startup.
The property file can be implicitly specified by naming it
servername.xaproperties, where servername is the name of the WebLogic
Server instance to which the property file applies. This file should be placed in the
current directory (typically the domain directory) or under the server root directory.
Note that the server root directory defaults to ".", but you can change the root directory
by using the ServerStart element in the configuration file; however, note that this
change is useful only when the Node Manager is used.
You should explicitly specify the Property file so no confusion occurs between the
current directory and root directory checks. When configuring servers that are to be
started using the Node Manager, for each configured server, set the arguments of the
ServerStart element to specify this property.