 | |
| APAR#: | II11373 |
| Component: | INFOAS400 - AS/400 Information |
| Release(s): | R530, R540, R610 |
Abstract
SYSTEM I ACCESS AND MICROSOFT WINDOWS TERMINAL SERVICES SUPPORT
Error Description
** Last changed March 21, 2008 **
System i Access for Windows V5R4, with service pack SI26849 or
later, and System i Access for Windows V6R1 or later, support
Citrix XenApp running on top of Microsoft Windows Terminal
Services.
Citrix XenApp is the new name for Citrix Presentation Server.
With this environment, Citrix XenApp can be used as a gateway
between end users and the System i. End users can connect to the
Citrix XenApp using Citrix Presentation Client and use all of
the System i Access for Windows functions without having to
install System i Access for Windows on their desktop.
System i Access for Windows
--------------------------
The following functions of System i Access for Windows will
work when using the Citrix Presentation Client connected to
the Citrix XenApp which has System i Access for Windows
installed and connected to systems with i5/OS V5R3 or later:
- PC5250 Display Emulation
- ODBC
- System i Navigator
- Data Transfer
- PC5250 Printer Emulation
- AFP Viewer
- Data Queue APIs
- Database APIs
- Remote Command APIs
- NLS APIs
- Distributed Program Call APIs
- OLE DB
- ActiveX APIs
- Command Line Remote Command
- Incoming Remote Command
ENVIRONMENTS SUPPORTED
----------------------
The following environments are currently supported:
Server Environments:
- iSeries IXS/IXA running Windows 2000 Server or Windows
Server 2003 (internal server option)
- PC Server running Windows 2000 Server or Windows Server 2003
(external server option)
Coexistence with Citrix products:
- System i Access for Windows is supported with
Citrix XenApp Server System Software V 4.5,
Citrix Presentation Client (for ICA connections);
for Windows XP; and for Windows Server 2003.
In Citrix XenApp, administrators have a choice of "publishing"
just the applications that they want their end users to have to.
In this way, users are limited to just the applications on the
Terminal Server that the administrator allows. Here are the
files that need to be published for some of the System i Access
applications:
== PC5250
c:\Program Files\IBM\Client Access\Emulator\pcsfe.exe
or
c:\Program Files\IBM Client Access\Emulator\pcsws.exe
== iSeries Navigator
c:\Program Files\IBM\Client Access\cwbunnav.exe
== Data Transfer (Upload)
c:\Program Files\IBM\Client Access\cwbtf.exe /f
== Data Transfer (Download)
c:\Program Files\IBM\Client Access\cwbtf.exe /t
KEYBOARD MAPPING
----------------
All function keys (>than F12) work in Citrix environment
except a few like F14 and F15. This is because in the Citrix
environment, these keys were mapped to some functionality like
-Shift+F3 - Close remote application
-Shift+F2 - Toggle title bar
and therefore, these combination of keys were not delivered to
PC5250. Instead Citrix hotkey functionality was performed.
This can be resolved by changing the hotkey settings in the
in the Citrix Program Neighborhood.
Hotkey setting for the Citrix environment can be modified from
'Citrix Program Neighborhood' Window
(from the menu Tools->Settings->Hotkeys tab).
Workaround for Citrix NFUSE keyboard mapping issue:
---------------------------------------------------
For this same issue when using the Citrix NFUSE product, here
is a way of solving this:
On the Nfuse server, edit the template.ica file
((C:\Program Files\Citrix\Nfuse\template.ica).
To disable usage of all Citrix hotkeys for NFuse connections,
add the following entries under the [wfclient] section of the
Template.ica file:
Hotkey1Char=(none)
Hotkey1Shift=(none)
Hotkey2Char=(none)
Hotkey2Shift=(none)
Hotkey3Char=(none)
Hotkey3Shift=(none)
Hotkey4Char=(none)
Hotkey4Shift=(none)
Hotkey5Char=(none)
Hotkey5Shift=(none)
Hotkey6Char=(none)
Hotkey6Shift=(none)
Hotkey7Char=(none)
Hotkey7Shift=(none)
Hotkey8Char=(none)
Hotkey8Shift=(none)
Hotkey9Char=(none)
HotKey9Shift=(none)
You may need to restart web services to reload this template
file.
INSTALLATION INSTRUCTIONS
-------------------------
To install System i Access for Windows on a Windows server
running Citrix XenApp on top of Terminal Services, one of the
following methods must be used:
1. Use the Add/Remove Programs applet in the control panel
to invoke our Setup program. Using the Add/Remove
Programs applet automatically does the install/uninstall
in Install Mode.
2. Switch to Install Mode using the chgusr command
(chgusr /install) prior to invoking setup from the
command line. After completing the install, switch
back to execute mode using chgusr (chgusr /execute).
3. Prior to using the CD browser interface (that is
provided with the System i Setup and Operations PC CD-ROM) to
install System i Access for Windows, switch to Install Mode
using the chgusr command (chgusr /install) from the
command line. After completing the install, switch back
to execute mode using chgusr (chgusr /execute).
4. On Windows Server 2003, users can launch setup.exe
from the Windows Explorer which automatically does
install in Install Mode.
NOTE: Service packs should be installed this same way. To
help ensure this, it is recommended that users turn off the
Check Version function (in System i Access Properties);
otherwise, service packs will automatically be installed the
incorrect way.
Also, be aware that V5R4 System i Access for Windows must always
be installed from the server console logged on locally and not
from one of the remote logged-in clients. Also, ensure that the
Terminal server is running in Administration Mode before
installing System i Access for Windows. Once it is installed,
reboot the server, and log on locally with an Account with
Administrative privileges, so that System i Access for Windows
can run its initial configuration.
ADDITIONAL INFORMATION SOURCES
------------------------------
- For additional information regarding the use of the iSeries
IXS/IXA running the Windows Terminal Services, refer to
the System i Windows Integration web site:
http://www.ibm.com/systems/i/bladecenter/windows/
- For additional information on using iSeries NetServer,
refer to the iSeries NetServer web site at:
http://www.ibm.com/eserver/iseries/netserver
Problem Summary
Problem Conclusion
Comments
Informational APAR
Circumvention
PTFs Available
Affected Modules
Affected Publications
Summary Information
| Status.............................................. | CLOSED CAN |
| HIPER............................................. | No |
| Component.................................... | |
| Failing Module............................... | |
| Reported Release........................ | R540 |
| Duplicate Of................................... |
- IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information.