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 Rocket® InfoConnect (formerly a Micro Focus product) Workspace (which replaces the Accessory Manager), or by opening the files from the Windows file explorer. (If you configured a non-default file extension for you earlier version session files, you can also open these files from the Workspace.) |
| When you save your session after opening an Extra! file or a legacy file, a new session document is created using the new format and a new file extension. The original session file remains unchanged. | |
| Rocket® InfoConnect (formerly a Micro Focus product) introduces a new level of security by configuring trusted locations and 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 Rocket® InfoConnect (formerly a Micro Focus product) 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) | Rocket® InfoConnect (formerly a Micro Focus product) 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) | Rocket® InfoConnect (formerly a Micro Focus product) 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) | Legacy hotspots files are migrated to the new hotspots file format (*.xhs). Legacy hotspots are partially supported. Text hotspots mappings are imported. Region hotspots mappings are not imported. Modifications to .ehs hotspots 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 in the InfoConnect product Help. |
CASL macros (*.xwc, *.xws) | You can continue to run and edit your CASL macros. For details, see CASL Macros in the InfoConnect product Help. |
Note
Security Files (*.esf) which were used by the Accessory Manager frame to limit access, are not used by Rocket® InfoConnect (formerly a Micro Focus product). There are other means of limiting access to Rocket® InfoConnect (formerly a Micro Focus product) features. See Lock Down InfoConnect To Restrict Access to Controls.