PaulD asks: Are there java levels that are too low (or high) to support 2DT in this environment?
2On your System z platform, you can display and use the Display Terminal check box. However, some additional configuration is required on the WebSphere Application Server and on your choice of a secondary network system (such as an AIX system). This configuration is necessary because the System z platform does not support graphical display devices as direct connect devices. On a System z platform, you can export the 2display terminal and graphics to an 2X Server running on the remote system. The 2X Server handles the graphical display of the terminal screen exported from the primary environment. The 2X Server is also needed by the graph component to generate graphs which are viewed by users
BruceG, in the paragraph below I added your comment about setting headless=false, 2but I am not sure how to tell the user to do it. Are they the same instructions 2as below in the UNIX section for WAS 6.x eg -Djava.awt.headless=false?
To export the graphics to an 2X Server, open the WebSphere administrative console and select Manage WebSphere Variables. Add a new variable DISPLAY and supply the address of the 2X Server. 2It is also necessary to set 2java.awt.headless=false2 for both the servant and control regions.
On the 2X Server, you must grant permission to the host to export the graphics (such as xhost +mvs03).
BruceG, I am not quit sure what you are referring to in your comment on 2the first draft "...the reason this got more complicated was because starting 2with WAS 6 on AIX, they set headless=true which is what caused us problems. 2I'm 99% sure it's only an AIX display terminal question (and for that matter, 2probably zLinux)"
PaulD asks: It would be nice to have an explicit statement of whether HATS 2supports headless mode at all (even if it can't support DT at the same time), 2since customers have asked about this before.
When running HATS applications on a UNIX platform, the DISPLAY environment must be set correctly for display terminal support. HATS applications require access to the 2X Server which specifies access with the DISPLAY environment variable. If it does not have access, the display terminal will not display.
To set the DISPLAY environment variable, type the following command where hostname is the host name or IP address of the system where the 2X Server is running:
export DISPLAY=hostname:0
On the system where the 2X Server is running it may be necessary to enable access control so that the client can connect. The xhost command is used to set access controls. The xhost command must be run on the console of the system where the 2X Server is running. It cannot be done remotely.
To enable access control so that clients from any host can connect to the 2X Server, type the following command:
xhost +
To enable access control so that only a certain client can connect to the 2X Server, type the following command where hostname is the host name or IP address of the client:
xhost + hostname
To enable access to see the display terminal when running on WebSphere Application Server 2V6.x in the WebSphere administrative console change the Generic JVM arguments located under Application servers > servername > Process Definitions > Java Virtual Machine from:
-Djava.awt.headless=true
to
-Djava.awt.headless=false
The default value is set to true which suppresses the display.
2When running WebSphere Application Server on Windows, if you 2have defined WebSphere Application Server as a Windows service, you must enable 2the appropriate WebSphere Application Server service to interact with the 2desktop in order to use the display terminal function.