Host On-Demand allows users to save the following component definitions into separate files on their local machines and use the definitions in host sessions without having to import them into the session configuration itself:
Users can define macro, keyboard, toolbar, popup keypad, and file transfer list definitions and save them into separate files. These separate files are then immediately available to other sessions. Users no longer need to configure the identical component again for the new session or import the file. If the user subsequently updates any of these macro, keyboard, toolbar, popup keypad, or file transfer list definitions files, other sessions that use those external files will automatically get the updates.
The ability of the session to use external definitions is available for the HTML, Configuration server-based, and Combined models. You can disable this ability for macros, keyboard, toolbars, popup keypad and file transfer lists.
By default, the macro, keyboard, toolbar, popup keypad and file transfer list
component files that users create are stored on their
local machines in the HODObjs subdirectory.
The complete path for the HODObjs subdirectory is a writable location unique
to the user, and the exact path depends on the platform, browser, and JVM
level. A typical path
on a Windows machine using Internet Explorer, for example, might be Documents
and Settings\username\HODObjs\
.
If you have configured the Save HTML parameter,
the HODObjs subdirectory
will use the Save path that you specify.
All of the session windows that list available macros, such as the Play Macro window, allow you to select a macro location. Possible locations include the following:
When users record new macros or update existing ones, they have the option to save them to the current session, their personal library or to any network location for which they have write access. Also, on the Available Macros window, which is accessed from the drop-down menu on the Macro Manager toolbar, users can copy and paste any number of macros from one macro location to another.
The Open button on the keyboard window allows users to change the current keyboard definition being used by the session. At any given time, there is only one keyboard definition associated with an active session, but users can open a different one whenever the need arises. The Open button launches a window that allows users to choose either the legacy keyboard defined internally in the session (the Current Session option) or an external file. Users can open a keyboard definition file from any location on their system, but the default location is the HODObjs subdirectory. Regardless of which keyboard definition the user opens, the selected definition becomes the current one used by the Host On-Demand session. Any updates that the user makes to the keyboard using the Save button are saved back to the location from which the keyboard was loaded (either the current session or the particular file). The next time the user launches the session, the same keyboard is automatically loaded from either the current session or the file.
The Save As button on the keyboard window allows users to save the current keyboard definition to a different location or file than is currently being used by the session. When the user selects Save As, the newly-saved keyboard becomes the current one for the session. This means that the saved keyboard will be the one loaded the next time the user launches the session.
Like the keyboard, the toolbar offers Open and Save As options. These options are available by clicking Edit > Preferences > Toolbar in a host session or by right-clicking the toolbar itself.
Like the keyboard, the popup keypad offers Open and Save As options. These options are found on the Customize Popup Keypad window, which is available by clicking Edit > Preferences > Popup Keypad > Customize in a host session or Edit > Customize in a popup keypad.
All of the session windows that allow users to select or specify a file transfer list also allow them to select a file transfer list location. Possible locations include the following:
Users can work with file transfer lists using either Host File Transfer or FTP/sftp, depending on the type of session they are running.
The fact that macros, keyboard, toolbar, popup keypad and file transfer list definitions can exist as separate files makes it easier for you to reuse components when you are configuring sessions for your users. However, you should understand that these sessions should not normally point to file components, since the files are not distributed to your users along with the session definitions. Generally, any macro, keyboard, toolbar, popup keypad or file transfer list definition that you want to make available to your users should be saved in the current session.
You can configure sessions from either the Deployment Wizard (for the HTML model) or the Host On-Demand Administration Utility (for the Configuration server-based and Combined models) In either case, you can start the sessions you wish to configure, and from the launched sessions, you will have access to all the user functions relating to macro, keyboard, toolbar, popup keypad and file transfer list definitions that are discussed above.
The following examples demonstrate the steps you need to follow to use the file components in a session that you are configuring for your users:
He must follow the Save As step to save the toolbar definition into the session and make it available to his users. If he does not follow the Save As step, then when the user starts the session, Host On-Demand will search for the file on the user's local machine, and it will not find it. |
The steps for Host File Transfer include the following:
- The power user opens the file transfer list from the current session.
- The power user gives the list a name and saves it to his personal library (the HODObjs subdirectory).
- The power user sends the new file via e-mail to the other users in your department.
- The users receive the new file and save it to their own personal libraries (HODObjs subdirectory) on their local machines.
- While in an open session, the users select the new file transfer list from their personal libraries and use it to transfer files.
The steps for FTP/sftp include the following:
- The power user uses the drop-down button on the Transfer List Manager toolbar to select the file transfer list from the current session. This causes that file transfer list to become active.
- The power user selects a file name and uses the 'Copy Current Transfer List' button to copy the list to his personal library.
- The power user sends the new file via e-mail to the other users in your department.
- The users receive the new file and save it to their own personal libraries (HODObjs subdirectory) on their local machines.
- While in an open session, the users select the new file transfer list from their personal libraries and use it to transfer files.