129 lines
8.2 KiB
HTML
129 lines
8.2 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Tips for using NAWT with WebSphere Application Server" />
|
||
|
|
<meta name="abstract" content="Set up NAWT for use by graphical Java programs running under WebSphere Application Server. When you use WebSphere Application Server and NAWT, you need to enable secure communications between the Virtual Network Computing (VNC) server and WebSphere Application Server." />
|
||
|
|
<meta name="description" content="Set up NAWT for use by graphical Java programs running under WebSphere Application Server. When you use WebSphere Application Server and NAWT, you need to enable secure communications between the Virtual Network Computing (VNC) server and WebSphere Application Server." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="nawt.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="nawtwas" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Tips for using NAWT with WebSphere Application Server</title>
|
||
|
|
</head>
|
||
|
|
<body id="nawtwas"><a name="nawtwas"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Tips for using NAWT with WebSphere Application Server</h1>
|
||
|
|
<div><p>Set up NAWT for use by graphical Java™ programs running under WebSphere<sup>®</sup> Application
|
||
|
|
Server. When you use WebSphere Application Server and NAWT, you need
|
||
|
|
to enable secure communications between the Virtual Network Computing (VNC)
|
||
|
|
server and WebSphere Application
|
||
|
|
Server.</p>
|
||
|
|
<p> Before reading the following information, make sure that you understand
|
||
|
|
how to install and use the Native Abstract Windowing Toolkit (NAWT) on your iSeries™ server.
|
||
|
|
In particular, you need to know how to use NAWT with the version of the Java 2
|
||
|
|
Software Development Kit (J2SDK) and <span class="keyword">i5/OS™</span> release
|
||
|
|
that you use.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle"> Ensuring secure communications</h4><p>A method called
|
||
|
|
X authority checking ensures secure communications between WebSphere Application
|
||
|
|
Server and the VNC server.</p>
|
||
|
|
<p>The process of starting the VNC server creates
|
||
|
|
an .Xauthority file that contains encrypted key information. Secure communications
|
||
|
|
between WebSphere Application
|
||
|
|
Server and VNC <strong>REQUIRES</strong> that both WebSphere Application Server and VNC
|
||
|
|
have access to the encrypted key information in the .Xauthority file.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Using X authority checking</h4><p>Use one of the following
|
||
|
|
methods to use X authority checking:</p>
|
||
|
|
<p><strong>Run WebSphere Application Server and VNC
|
||
|
|
using the same profile</strong></p>
|
||
|
|
<p>One way that you can ensure secure communications
|
||
|
|
between WebSphere Application
|
||
|
|
Server and the VNC server is by running WebSphere Application Server from
|
||
|
|
the same profile that you use to start the VNC server. To run WebSphere Application
|
||
|
|
Server and VNC the with same profile, you must change the user profile under
|
||
|
|
which the application server runs.</p>
|
||
|
|
<p>To switch the user profile for the
|
||
|
|
application server from the default user (QEJBSVR) to a different profile,
|
||
|
|
you must perform the following actions:</p>
|
||
|
|
<ol><li>Use the WebSphere Application
|
||
|
|
Server administrative console to change the application server configuration</li>
|
||
|
|
<li>Use iSeries Navigator
|
||
|
|
to enable the new profile</li>
|
||
|
|
</ol>
|
||
|
|
<p>For information about using the WebSphere Application Server administrative
|
||
|
|
console and iSeries Navigator,
|
||
|
|
see the following documentation:</p>
|
||
|
|
<p><a href="http://www.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/docs/doc.htm" target="_blank"> WebSphere Application Server</a></p>
|
||
|
|
<p><a href="../rzaih/rzaihuseradmin.htm" target="_blank">Manage
|
||
|
|
users and groups with Management Central</a></p>
|
||
|
|
<p><strong>Run WebSphere Application
|
||
|
|
Server and VNC using different profiles</strong></p>
|
||
|
|
<p>When you want WebSphere Application
|
||
|
|
Server and VNC to use different profiles, you can ensure secure communications
|
||
|
|
by having WebSphere Application
|
||
|
|
Server use the .Xauthority file.</p>
|
||
|
|
<p>To enable WebSphere Application Server to use
|
||
|
|
the .Xauthority file, complete the following steps:</p>
|
||
|
|
<ol><li>Create a new .Xauthority file (or update an existing .Xauthority file)
|
||
|
|
by starting the VNC server from your user profile. From an <span class="keyword">i5/OS</span> control
|
||
|
|
language (CL) command line, type the following command and press <strong>ENTER</strong>:
|
||
|
|
<pre> CALL QP2SHELL PARM('/QOpenSys/QIBM/ProdData/DeveloperTools/vnc/vncserver_java' ':<em>n</em>')</pre>
|
||
|
|
|
||
|
|
where <em>n</em> is the display number (a numeric value in the range of 1-99).
|
||
|
|
<p><strong>Note:</strong> The .Xauthority file resides in the directory for the
|
||
|
|
profile under which you are running the VNC server.</p>
|
||
|
|
</li>
|
||
|
|
<li>Use the following CL commands to grant the profile under which you run WebSphere Application
|
||
|
|
Server the authority to read the .Xauthority file: <pre> CHGAUT OBJ('/home') USER(<em>WASprofile</em>) DTAAUT(*RX)
|
||
|
|
CHGAUT OBJ('/home/<em>VNCprofile</em>') USER(<em>WASprofile</em>) DTAAUT(*RX)
|
||
|
|
CHGAUT OBJ('/home/<em>VNCprofile</em>/.Xauthority') USER(<em>WASprofile</em>) DTAAUT(*R)</pre>
|
||
|
|
|
||
|
|
<div class="p">where <em>VNCprofile</em> and <em>WASprofile</em> are the appropriate
|
||
|
|
profiles under which you are running the VNC server and WebSphere Application
|
||
|
|
Server.<div class="note"><span class="notetitle">Note:</span> <img src="./delta.gif" alt="Start of change" />You should only follow these steps when the <em>VNCprofile</em> and <em>WASprofile</em> are
|
||
|
|
different profiles. Following these steps when <em>VNCprofile</em> and <em>WASprofile</em> are
|
||
|
|
the same profile can cause VNC to not function correctly.<img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>From the WebSphere Application
|
||
|
|
Server administrative console, define the DISPLAY and XAUTHORITY environment
|
||
|
|
variables for your application: <ul><li>For DISPLAY, use either: <kbd class="userinput">system:n</kbd> or <kbd class="userinput">localhost:n</kbd>
|
||
|
|
<p>where <em>system</em> is the name or IP address of your iSeries system
|
||
|
|
and <em>n</em> is the display number that you used to start the VNC server.</p>
|
||
|
|
|
||
|
|
</li>
|
||
|
|
<li>For XAUTHORITY, use: <kbd class="userinput">/home/VNCprofile/.Xauthority</kbd>
|
||
|
|
<p>where <em>VNCprofile</em> is the profile that started the VNC server.</p>
|
||
|
|
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>Pick up the configuration changes by restarting WebSphere Application Server.</li>
|
||
|
|
</ol>
|
||
|
|
<p>For information about using the WebSphere Application Server administrative
|
||
|
|
console, see the following documentation:</p>
|
||
|
|
<p><a href="http://www.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/docs/doc.htm" target="_blank">WebSphere Application Server</a></p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="nawt.htm" title="The Native Abstract Windowing Toolkit (NAWT) provides Java applications and servlets with the capability to use the Abstract Windowing Toolkit (AWT) graphics function offered by the Java 2 Software Development Kit (J2SDK), Standard Edition.">Native Abstract Windowing Toolkit</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|