Using XMLink Universal Gateway


Appendix B. Upgrading XMLink Universal Gateway

This appendix describes changes made from previous releases of XMLink Universal Gateway.

Changes in Version 2.2

Upgrading from Version 2.0 or Version 1.0

If you are upgrading from Version 1.0 or Version 2.0, the following changes have been implemented:

Data Translation and Validation

Tuxedo Services File

SOAP Services File

Java System Properties

XUG.GatewayAdapter.JNDIName
The default JNDI lookup name for the Gateway Adapter EJB has been updated to:

com/prolifics/xug/dda/adapter/GatewayAdapterHome

XUG.TuxedoServices
For the Tuxedo service definition file, the name of the Java system property was changed from XUG.TuxedoRegistryFile to XUG.TuxedoServices. Its default value has been changed from Services.xml to TuxedoServices.xml.

XUG.SoapServices
For the SOAP service definition file, the name of the Java system property was changed from XUG.Services to XUG.SoapServices. Its default value has been changed from services.xml to SoapServices.xml.
Upgrading from Version 1.0

Specifying FML Formats
In Version 1.0, the FML results were configured in the files set by FIELDTBLS and FIELDTBLS32. XMLink Universal Gateway needed the following to be included:
# name              number   type    flags   comments
XMLINK_SHORT_RESULT 200 short - -
XMLINK_LONG_RESULT 201 long - -
XMLINK_CHAR_RESULT 202 char - -
XMLINK_FLOAT_RESULT 203 float - -
XMLINK_DOUBLE_RESULT 204 double - -
XMLINK_STRING_RESULT 205 string - -

As of Version 2.0, this specification was no longer necessary since the FML results are specified in the Tuxedo service definition file.

Java Environment
As of Version 2.0, make the following changes to the CLASSPATH on the Tuxedo server: