Upgrading From Earlier Versions of InfoConnect
You can install and use Rocket® InfoConnect (formerly a Micro Focus product) on systems running earlier versions of InfoConnect.
-
The installer will remove your prior version software before installing the new version.
-
The installer does not remove existing session, macro, or scheme files. After the upgrade, you can continue to use your legacy files.
-
When you upgrade an existing system InfoConnect continues to use your existing locations for application and data files. (When you install on a new system, Rocket® InfoConnect (formerly a Micro Focus product) uses new default locations for these files.)
Note
If you are upgrading from InfoConnect version 8.1 SP1 or later, you may need to move some files manually after the upgrade. If you configured any of the following, see Managing FTP Client and Shared Security Settings after an Upgrade.
-
FTP Client settings.
-
Secure Shell known hosts and non-default Secure Shell settings.
-
Certificates and settings configured using the Reflection Certificate Manager.
Working with your files after an upgrade
You can continue to connect to hosts and work with host screens using your existing session files and customized settings. In most cases you can continue to use your prior version files with no modification. Changes are always saved to new files using the new format; your prior version files are never changed.
| Working with these files... | After the upgrade... |
|---|---|
Terminal session files (*.adp, *.edp, *.idp) | You can open your existing session files from the InfoConnect Workspace (which replaces the Accessory Manager), or by opening the files from the Windows file explorer. When you save your session after opening a legacy file, a new session document is created using the new format and a new file extension. The legacy session file remains unchanged. InfoConnect introduces a new level of security by configuring trusted locationsand requiring that session files be in a designated trusted location. Your Windows Documents folder is configured to be a trusted location by default, so legacy files in that folder will open successfully. If you saved files to a different location, you may need to add that location to the trusted location list. |
Layouts (*.aww) | You can open your existing layout files from the InfoConnect Workspace or directly from the Windows file explorer. New and modified layouts are saved using the new format and file extension (*.rwsp). |
Keyboard maps (*.ekm) | InfoConnect supports your existing keymap files (*.ekm). You can attach new Rocket® InfoConnect (formerly a Micro Focus product) sessions to current-version keyboard map files (*.xkb) or legacy keyboard map files (*.ekm). |
QuickPads (*.eqp) and Toolbars (*.etb) | InfoConnect supports your existing QuickPad and toolbar files. (Toolbars are imported as QuickPads docked on the top of the session window.) Modifications to existing QuickPads are saved using the new format and file extension (*.rqpx). |
InfoConnect database (ic32.cfg) | After an upgrade, InfoConnect continues to use your existing database in its current location. All path configuration in the database continues to be used for existing session files and can be used to create new session files in the new format. If you install on a new system, the database is created by default in a new location. |
Hotspots (*.ehs) | InfoConnect partially supports .ehshotspots files created in previous versions of InfoConnect. (Text hotspots mappings are imported. Region hotspots mappings are not imported.) Modifications to .ehshotspots files are saved using the new hotspots file format and extension (*.xhs). |
Extra! macros (*.ebm) | You can continue to run and edit most Extra! Basic macros. For details, see Extra Macros |
CASL macros (*.xwc, *.xws) | You can continue to run and edit your CASL macros. For details, see CASL Macros. |
More information