Table of Contents:
Citrix Connection Information
Reconnecting to an Existing Session (Active)
Reconnecting to an Existing Session (Disconnected)
The document provides some basic information about the Citrix connections and lists possible
solutions regarding problems with Citrix connections.
The Citrix Metaframe server is a middleware technology that allows the user to communicate with a
Microsoft Windows server/workstation. It provides the capability to run an application on a
remote computer (Metaframe server) while displaying output and receiving input on the user’s computer
(client). While Citrix’s main purpose is to establish and maintain the connection between the client
and the Metaframe server, all other functionality is performed by the Metaframe server. These
functions include (but are not limited to) user login, user authentication, and file permissions.
A Citrix connection follows the subsequent sequence:
- User logs in to Citrix Web interface.
- User clicks on the application.
- The user is automatically logged into the Metaframe server using the Citrix login
information.
- Any necessary login scripts are automatically run by the Windows OS.
- The application is launched by Citrix.
- The user terminates the application when done.
- The user is logged out of the Windows server.
- The user logs out and closes the Web interface, if necessary
The following are technical terms that help the user understand the functionality of Citrix
connections:
- Session: the time during which a user is logged into the Metaframe server. The session
begins when the user logs into the server (step 3) and ends when the user logs out again (step 7).
- Active Session: the time period during which a user is actively using the
system/application (e.g., performing WISE scoping work).
- Disconnected Session: the time period during which there’s no network connection between
the client and the Metaframe server, yet the user has a session open (i.e., is logged in to the
system). Any application will continue to run during this time. Therefore, a user could start a long
modeling process, disconnect from the system and log back in a day later to check the status and/or
results of the model run.
The relationship between the different session types is:
Total Session Time = Active Session Time + Disconnected Session Time
Note: If the user has a disconnected session, he is utilizing a single connection
license. While this may not have an effect when only a few users are logged onto the system, there is a significant impact when all connection licenses are in use. Disconnected sessions, thus, block users
that would like to work via an active session. Therefore, users should make sure to log off when the
work is complete so that a license is released to the license pool.
Several settings may be adjusted to configure the behavior of the connection. The two most
important are:
- Idle Time: the time for which no user input is received (e.g., no mouse movement). On the
FEMA production environment the allowable idle time is currently set to 30 minutes. After this time,
the server will disconnect the user without a warning. Note that the user will not be logged
out during this process and any running application will continue to run.
- Disconnect Time: the time for which the user can be disconnected from the system. The
disconnect time is currently set to 4 days on the FEMA production environment. After this time the
server will log off the user and close any open application. Note that this time will be reset
when the user reconnects to the system
In some instances the user may encounter an error when attempting to (re)connect to a published
application. The error will state that the user already has an instance of the application
running. This error may occur when the user gets disconnect from the system due to a network
failure, and the Metaframe server does not detect that the client disappears. In such a
situation, the session status is not switched to ‘disconnected’ but stays
‘active’.
|
Error message if there is already an active session open for the same application. |
The following steps allow the user to disconnect the current application:
- Log onto the Citrix Web interface.
- The following webpage will appear. If the “Disconnect” or “Reconnect” button is not
visible, please advance to step 5.
|
Web interface allows user to disconnect or reconnect to any active sessions.
(Note: this may vary depending on your browser) |
- Click on ‘Disconnect’ to disconnect any active applications.
- Once the login screen reappears, log in and click on the application.
- If the ‘existing instance’ error persists, please contact
MIPHelp@mapmodteam.com for assistance.
If your connection is terminated due to a connection time-out, the user should wait at least 10
minutes for it to be reset. If you attempt to log back immediately after your connection is
terminated, it will be unsuccessful, and you jeopardize the possibility of reconnecting to your
running session.
After waiting for a suitable amount of time, log in as you normally would. Launch the DFIRM
Tools application and click OK on the dialog boxes that appear, as you would do in a typical login.
As JTX is initializing, the system detects your existing session. A screen similar to the
following image will appear. On this screen data or dialog box hold-outs may be visible in the
center of the screen.
The rectangular area in the middle of the screen is actually a “window” into the
applications left running when your connection was timed out. In this example, an ArcMap project
with no layers visible was left running when the connection was terminated.
|
Citrix Login page with a hold-out “window” for a currently running ArcMap project |
At this point, the DFIRM Tools application running on the Citrix ICA client needs to be restored
into Full Screen mode. Doing so will allow you to view the application you left running when
your connection was terminated.
Locate the Citrix Neighborhood or ICA icon in your system tray, located inthe bottom
right−hand side of your screen display. The icon will look like one of the following:
OR
OR ![Citrix or ICA icon](https://webarchive.library.unt.edu/eot2008/20090106083255im_/https://hazards.fema.gov/femaportal/images/resources/Citrix/image014.jpg)
Go into Full Screen Mode to re-join a session in which ArcMap or JTX is running by completing the
following steps:
- Double-click on the icon to open the ICA Connection Center dialog window.
|
ICA Connection Center dialog window showing the existing connection |
- You will see the server on which your existing session is running. In this case, it is
FEMA049P01P.
- When the server name is highlighted, click on the Full Screen button.
- The following message box will appear to warn you that you are switching out of seamless mode to
full screen mode.
|
ICA Connection Center window confirming the switch to full screen mode. |
- Accept the message by clicking OK. Full screen mode will is now activated. The ICA
Connection Center window will be maximized and will contain any running application in your
session.
|
View of ArcMap project after switching to full screen mode. |
- You may continue working. If you are rejoining an edit session, be sure to save your
edits.
- Switch back to seamless mode by holding down the Shift and F2 keys.