Wall Data has tested RUMBA and ARPEGGIO software running on Citrix WinFrame 1.x servers. This technical bulletin provides a general overview of installing software on a WinFrame server, as well as specific instructions for installing 32-bit RUMBA and ARPEGGIO products on a WinFrame 1.x server with Service Pack 5. This technical bulletin also covers issues related to specific RUMBA and ARPEGGIO products.
The following steps provide an overview of the procedure for installing applications on a WinFrame 1.x server with Service Pack 5.
1. Log in as administrator at the WinFrame console.
2. Start a command prompt session. Type change user /install and press Enter. This puts the session in install mode.
3. Exit the DOS(R) session.
4. Install the application according to the instructions supplied with the software.
5. After installation is complete, start a command prompt session. Type change user /execute and press Enter. This returns the session to execute mode.
6. Citrix recommends that the administrator then "write protect" the application and the following directories:
RUMBA Router Interfaces with Citrix WinFrame
Any objects (EXE files and DLL files) that are common to all users on a given machine must be registered as system global on the WinFrame server. When the RUMBA Router components are registered as system global, the router operates as if it were a gateway. This means that all users on a given Citrix server will use the same instance of the router.
Because all users connect with the same instance of the router, it is recommended that it be automatically started from the Windows NT Startup group using a common user ID and
password (each user will still enter a unique user ID and password at the AS400 or host sign-on screen).
If you are using RUMBA 95/NT 5.0 U02, RUMBA 95/NT 5.1 U00, or ARPEGGIO 1.0 U02, you must install the following PTFs in order to use the RUMBA Router interface in a WinFrame
* INS51005 or later
* APP51009 or later
* EHN51007 or later
Earlier versions of RUMBA software or ARPEGGIO software do not support the RUMBA Router interface in a WinFrame environment.
Registering RUMBA Router Components
The following components must be registered on the WinFrame server for proper operation of the RUMBA Router. To register the components, get to a DOS command prompt, change the
directory to the RUMBA install SYSTEM directory and enter the following command lines:
REGISTER WDSNA.EXE /SYSTEM
REGISTER WAPPC32.DLL /SYSTEM
REGISTER WCPIC32.DLL /SYSTEM
REGISTER WINCSV32.DLL /SYSTEM
REGISTER WINRUI32.DLL /SYSTEM
REGISTER DUNTMAP.DLL /SYSTEM
REGISTER EVLOGAPI.DLL /SYSTEM
Using RUMBA with SNA(R) Server Interface
If you are using RUMBA 95/NT 5.0 U02, RUMBA 95/NT 5.1 U00, or ARPEGGIO 1.0 U02, you must install the following PTFs in order to use the Microsoft SNA Server interface in a WinFrame environment:
* INS51005 or later
* EHN51007 or later
Earlier versions of RUMBA software or ARPEGGIO software do not support the SNA Server interface in a WinFrame environment.
Registering SNA Server Components on the WinFrame Server
See the WinFrame/Enterprise Solutions Guide concerning the configuration of Microsoft NT SNA server for a complete listing of the components requiring registration.
Specific Interface Configuration Issues
If manual response to displayable event messages is not desired, each WinFrame server may have an additional entry included in the configuration file to allow for handling of Event Messages. This entry must be added in the Base Section of the configuration file as follows:
This allows all of the Event Messages to show up in the Event log, but will not require a response from the user on the WinFrame server that started the router.
Each WinFrame user will connect to the same AS/400 controller. (The AS/400 controller name is referred to as the PC System Name in the router configuration screen or as the Control Point name in the APPC configuration utility, CONFIG.EXE.)
The controller name will be common to all users on a given WinFrame server. Wall Data suggests using a name that uniquely identifies the WinFrame server. (A name such as
"WinFrame" would be fine if only one server existed in the customer environment, but would cause confusion if there were more than one server running WinFrame.)
Using the example controller description "WinFrame", each AS/400 user will then connect to a unique 5250 device associated with that controller. The name of this device is entered in the Connect/Configure menu in the RUMBA AS/400 display session at each client workstation. Please ensure that client workstation configurations do not conflict when the device name is specified.
WinFrame users will share all configured Physical Units (PUs). PUs (called Connections when viewed using CONFIG.EXE) must be configured with enough Logical Units (LUs) to service the total number of concurrent sessions desired. This is identical to the LU pooling functions on many SNA gateways.
When connecting, users will be given the first available LU from the "pool" by default. If specific LU addresses need to be administered (printer LUs, for example), the LU address must be entered in the Connect/Configure menu of the RUMBA display session at each client workstation. Please ensure that client workstation configurations do not conflict when specific LU addresses are used. See the RUMBA Router Help topic for more information on configuring 3270 LUs.
Using Private Directories on WinFrame Servers
RUMBA and ARPEGGIO software use private directories to allow users to maintain unique configuration files, keyboard maps, display profiles, etc. The pointer to the private directory
is stored in the registry under the HKEY_LOCAL_MACHINE tree. Because WinFrame uses the same LOCAL_MACHINE tree for each user, some modifications must be made to allow unique
For each user to have his/her own private directory, the private directory pointer must point to a drive letter, and each user must map his/her unique private directory to that drive. For example, the private directory entry in the registry could point to P:PrivateDir. Each Citrix user could map a different share to drive P. This way, the entry in the registry remains the same, but each user has his/her own unique directory. The two private directory entries in the registry are:
For more information on private directories, see technical bulletin # 3007 (available at ftp.walldata.com).