In order to use XA database drivers with WebSphere, add the following configuration to your <ATG9dir>/home/localconfig/GLOBAL.properties file:
localTransactionModeInitialization=false
If you have installed the WebSphere Network Deployment version, when you run the ATG installer you must select the IBM Websphere - cluster setup option (even if you are not actually using clustering).
If using WebSphere on AIX, to avoid errors when importing application data using ATG import scripts, you must set the following in the <ATG9dir>/home/localconfig/postEnvironment.sh file:
JAVA_ARGS="${JAVA_ARGS} -Djava.net.preferIPv4Stack=true"You must also set it in the WebSphere environment:
In WebSphere Admin, go to Servers > Application servers > server >Java and Process Management > Process Definition > Java Virtual Machine.
Under Generic JVM arguments set the following:
-Djava.net.preferIPv4Stack=true
If you do encounter this problem, you will see errors such as the following:
Error: Jan 30, 2008 12:45:01 PM javax.jmdns.JmDNScloseMulticastSocket
WARNING: closeMulticastSocket() Close socketexception
java.net.SocketException: The socket name is not available on this system.
To use XA data sources with WebSphere, add the following line to your <ATG9dir>/home/servers/servername/localconfig/GLOBAL.properties file:
localTransactionModeInitialization=false
In order to create scenarios in the ACC, you must add the <WSdir>/AppServer/j2ee.jar file to your class path. To do this, copy j2ee.jar into the /lib directory of your standalone ACC installation, then modify the bin/startClient.bat file to include j2ee.jar in the class path.
