|Home > Documentation > Configuring and administering > Configuring the Transaction Manager Identity|
In order for XA transactions to work properly, each Geronimo instance connecting to a resource manager such as an XA capable database or jms needs to have a globally unique and permanent Id.
each Geronimo instance connecting to a resource manager such as an XA capable database or jms needs to have a globally unique and permanent Id.
In Geronimo this id is a byte sequence configured in the XidFactory service in the transaction plugin. Do not change this while the server is running or while there are any in-doubt transactions anywhere in your system. This is the server identity as far as the xa system is concerned. For instance if a server becomes permanently unavailable due to hardware failure you can recover in-doubt transactions it is responsible for by setting up another server with the same apps and the dead server's TmId.
Edit the line
in var/config/config-substitutions.properties to contain a unique byte sequence.
Modify the var/config/config.xml file to look more like this (add the XidFactory element):
Again, use a unique byte sequence.