InfoConnect uses a variety of files to store customized data. Administrators can simplify the user experience by preconfiguring and installing customized files.
Paths
Information required for connecting to ALC, UTS, and T27 hosts is configured in paths, which are saved in the InfoConnect database. You can include a customized database as part of your installation. See Paths.
Session documents and customization files
By default, InfoConnect saves basic terminal session configuration in a session document, which includes connection and terminal settings. Additional customizations are saved by default to separate customization files that can be associated with one or more terminal sessions. These customization files include theme files (for customizing color and font), keyboard maps, mouse maps, hotspots, customized ribbons, and QuickPads. For information about customizing InfoConnect, see Session Documents. For a complete list of files used by InfoConnect, see Files Used by InfoConnect.
Compound session documents
You can create a compound session document that includes all the settings in any associated theme, keyboard map, mouse map, hotspot, ribbon, or QuickPad file. This option enables you to deploy session files with all required customizations included in a single file. See Compound Documents.
Templates
Templates provide default configurations for connecting to specified file types. InfoConnect Desktop ships with default templates for each of the supported session types included with your product. You can also create and deploy custom templates designed to meet the needs of your users. See Session Templates.
Workspace settings
Workspace settings affect all terminal sessions. Configure these from the Workspace Settings dialog box and deploy them using a custom Application.settings file. See Workspace Settings.
Layouts
Layouts are saved Workspace arrangements. You can open and arrange multiple host sessions, then save your configuration as a layout. When you open the layout, all of the sessions in the layout open in the arranged configuration. You can include custom layout files (*.rwsp) as part of your deployment.