#### Citrix Connection

**User Guide**

[Citrix Connection Information 1](#citrix-connection-information)

[Reconnecting to an Existing Session (Active)
2](#reconnecting-to-an-existing-session-active)

[Reconnecting to an Existing Session (Disconnected)
3](#reconnecting-to-an-existing-session-disconnected)

# Citrix Connection Information

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:

1.  User logs in to Citrix Web interface.

2.  User clicks on the application.

3.  The user is automatically logged into the Metaframe server using the
    Citrix login information.

4.  Any necessary login scripts are automatically run by the Windows OS.

5.  The application is launched by Citrix.

6.  The user terminates the application when done.

7.  The user is logged out of the Windows server.

8.  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

# Reconnecting to an Existing Session (Active)

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'.

  -----------------------------------------------------------------------
  ![](media/image1.png){width="6.0in" height="0.8534722222222222in"}

  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:

1.  Log onto the Citrix Web interface.

2.  The following webpage will appear. If the "Disconnect" or
    "Reconnect" button is not visible, please advance to step 5.

  -----------------------------------------------------------------------
  ![](media/image2.png){width="6.003472222222222in"
  height="5.090972222222222in"}

  Web interface allows user to disconnect or reconnect to any active
  sessions. (Note: this may vary depending on your browser)
  -----------------------------------------------------------------------

3.  Click on 'Disconnect' to disconnect any active applications.

4.  Once the login screen reappears, log in and click on the
    application.

5.  If the 'existing instance' error persists, please contact
    <MIPHelp@mapmod.com> for assistance.

# Reconnecting to an Existing Session (Disconnected)

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.

  -----------------------------------------------------------------------
  ![](media/image3.png){width="5.624305555555556in"
  height="5.221527777777778in"}

  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:

![](media/image4.png){width="0.21875in" height="0.19791666666666666in"}
OR ![](media/image5.png){width="0.22916666666666666in"
height="0.21875in"} OR
![](media/image6.png){width="0.22916666666666666in"
height="0.22013888888888888in"}

Go into Full Screen Mode to re-join a session in which ArcMap or JTX is
running by completing the following steps:

1.  Double-click on the icon to open the ICA Connection Center dialog
    window.

  -----------------------------------------------------------------------
  ![](media/image7.png){width="4.280555555555556in"
  height="3.4694444444444446in"}

  ICA Connection Center dialog window showing the existing connection
  -----------------------------------------------------------------------

2.  You will see the server on which your existing session is running.
    In this case, it is FEMA049P01P.

3.  When the server name is highlighted, click on the Full Screen
    button.

4.  The following message box will appear to warn you that you are
    switching out of seamless mode to full screen mode.

  -----------------------------------------------------------------------
  ![](media/image8.png){width="2.957638888888889in" height="1.25in"}

  ICA Connection Center window confirming the switch to full screen mode.
  -----------------------------------------------------------------------

5.  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.

  -----------------------------------------------------------------------
  ![](media/image9.png){width="5.989583333333333in"
  height="4.638194444444444in"}

  View of ArcMap project after switching to full screen mode.
  -----------------------------------------------------------------------

6.  You may continue working. If you are rejoining an edit session, be
    sure to save your edits.

7.  Switch back to seamless mode by holding down the Shift and F2 keys.