Incorrect language is displayed in Web Administration Tool

Edit online

The tabs, table headers, and static list boxes in the Web Administration Tool are sometimes displayed in an incorrect language. This problem might be encountered only on the AIX® operating systems. However, a Linux™ system might encounter the same problem. Follow the steps to resolve this problem.

The environment variables LC_ALL and LANG must be set to a native locale supported by IBM® Semeru Runtime Certified Edition; for example en_US.iso88591. They must not be set to either POSIX or C.

export LC_ALL=new language
export LANG=new language

The translation of the tabs, table headers, and static list boxes are saved in the language that was first used by the application server. It is the language that was used the first time that a user logs in to the Web Administration Tool application. If you change the locale on your system, you might see the following exception:

java.lang.InternalError: Can't connect to X11 window server using ':0.0' 
as the value of the DISPLAY variable.
at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
at sun.awt.X11GraphicsEnvironment.<clinit>
(X11GraphicsEnvironment.java:58)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment
(GraphicsEnvironment.java:53)
at sun.awt.motif.MToolkit.<clinit>(MToolkit.java:63)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at java.awt.Toolkit$2.run(Toolkit.java:507)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:498)
at java.awt.Toolkit.getEventQueue(Toolkit.java:1171)
at java.awt.EventQueue.invokeLater(EventQueue.java:506)
at javax.swing.SwingUtilities.invokeLater(SwingUtilities.java:1086)
at javax.swing.Timer.post(Timer.java:337)
at javax.swing.TimerQueue.postExpiredTimers(TimerQueue.java:190)
at javax.swing.TimerQueue.run(TimerQueue.java:226)
at java.lang.Thread.run(Unknown Source)

To correct this exception, you must export the DISPLAY variable so that it is a valid computer; for example, the computer on which the application server is running. Then, run xhost + on the application server computer.

On the computer to which you want to export the DISPLAY, issue the command:

export DISPLAY=valid_computer_name:0

On the valid_computer_name issue the command:

xhost +