Advanced Options

Use this panel to define display, message, and additional parameters for this HTML file.

HTML parameters
The Deployment Wizard automatically includes HTML parameters for all Wizard options. However, if you want to include additional options that are not shown in the Wizard, you can use this window to add the necessary parameters to include those options. To add a parameter, type the name of the parameter in the Name field, type the value in the Value field, and click Set. Do not include quotes around the names and values. The Deployment Wizard adds the parameter in the box below. To remove a parameter, highlight the parameter in the box and click Delete.

You should not manually add these parameters to the HTML file (for example, using a text editor), or they may be lost the next time you open the file with the Deployment Wizard.

To see a list of available parameters, refer to HTML parameters.

Code base
If you are publishing files generated from the Deployment Wizard to a location other than the Host On-Demand publish directory, specify the URL of the Host On-Demand publish directory in the Code base field. This name must either be a fully qualified URL, including the hostname (for example, http://your_HOD_server/hod_publish_dir_alias/), or a relative path (for example, /hod_publish_dir_alias/). For more information on how and why you would want to publish files generated from the Deployment Wizard to a location other than the publish directory, see Setting up a separate user publish directory.

This code base is not the same as the code base you specify if you select the Web Start client. For more information, refer to Web Start Settings.

HTML templates
Include banners, backgrounds, images, and other HTML options in your Host On-Demand Web page by specifying a custom HTML template. Click Browse to choose the HTML template that you want to use. The template is applied to the Web page when it is created at the end of the Deployment Wizard. For information on creating custom HTML templates, see Using Custom HTML Templates.

Problem Determination
The Problem Determination window allows you enable the following debugging options:

None: No debugging.

Basic: Select this option to enable Basic debugging. This level of debugging allows Host On-Demand to write error messages to the Java Console. Optionally check the 'Include problem determination components' box to include Trace Facility, View Log Messages, and System Properties components, which are available from the Actions > Problem Determination menu in an active session. The 'Include problem determination components' box will already be checked by default if you are editing an existing HTML file that was created with problem determination configured.

Advanced: Select this option to enable Advanced debugging. This level of debugging allows Host On-Demand to write error messages to the Java Console, including problem determination components, and enables either a Transport or IPMonitor trace.

Both Transport and IPMonitor traces capture the telnet traffic between Host On-Demand and the host telnet server, write detailed error information to a log file, and save the log file to the client machine. The Deployment Wizard prefills the 'Log file name' field with the default file name hodtrace.txt, but you can change it if you wish. For Unix-based client platforms, include the absolute path to where you want to save the file. For Windows client platforms, if you do not specify an absolute path, the log file will be saved to the client desktop.

Both types of Advanced tracing require a session name. If you are using the HTML-based model, the 'Session name' field is prefilled with the name of the current sessions that you are configuring. If you are using the Configuration server-based or Combined models, you must manually enter the name of the session that you want to trace.

If you want to configure additional debugging options for Transport or IPMonitor traces that are not available on the Problem Determination window, you must manually add HTML parameters to your file using the HTML parameters window in Advanced Options. Any debugging parameter that you add using the HTML parameters window takes precedence over the parameters that are automatically added when you configure them on the Problem Determination window. For example, if you want to limit the number of Transport trace entries, you would need to add the TraceOptions parameter manually because this is not an option on the Problem Determination window. To see a list of available parameters, refer to HTML parameter names and values.

For more information about Transport and IPMonitor tracing, refer to Host On-Demand tracing in the Troubleshooting Guide.

User updates
When users make changes to session properties (for example, session size, placement, colors, toolbar customizations, and macros), these changes are associated with the browser window that was used to access the HTML file and will remain in effect as long as that browser window remains active. If you allow users to make updates (the default), Host On-Demand will remember the modifications the next time the user accesses the HTML file. Otherwise, if you select No, any session modifications will be lost when the user closes the browser window.

Appearance
Use the Appearance window to select a layout for displaying host sessions. Note that these options control the entire Host On-Desktop, not the sessions individually. Choices include the following:

• Standard Host On-Demand Client: This option displays the standard Host On-Demand desktop.
• Grid of Buttons: This option displays the Host On-Demand desktop as a grid of buttons.
• Hide HOD Desktop at Startup: This option hides the Host On-Demand desktop and session tabs. It is useful when you want to display only the session itself, for example, in a WebSphere Portal environment where you embed your session(s) in the Portal Web page. When selecting this option, you should also configure the following two options on the Preferences > Start Options window of session properties:
  • Set the 'Start Automatically' option to Yes.
  • Set the 'Start in Separate Window' option to No.

Applet size
Use the Applet Size window to select the size of the applet. Choices include Autosize to browser, Small, Medium, Large, or Other.

If you select Other, you must enter the width and height of the applet in pixels. This option is particularly useful when configuring sessions to run in a Portal environment because it gives you greater control and flexibility over the size of the sessions running within individual portlets. For more information about how to use Host On-Demand as a portlet, refer to the Using Host On-Demand Clients with Portal Server section in the Planning, Installing, and Configuring Host On-Demand guide.

The Autosize to browser function is not supported on Netscape 6.1 browsers.

Hide information
The following three independent options allow you to provide enhanced security by hiding certain information that would normally be visible to users. Once enabled, these options will apply to all the sessions that you are configuring for this HTML file.

• Hide destination address and port number: Removes the destination address and port number from the status bar, status bar history, and the Connections window in session properties. Checking this option does not block the destination address and port number when a client is taking a trace or running IPMonitor.
• Hide LU name (3270 Display/Printer sessions): Removes the LU name from the title of the session frame and from the Connection and Backup Servers windows in session properties.
• Hide client certificate source: Removes the certificate source URL property from the TLS/SSL window in session properties and from the View > Security > Show Client Certificate window.

Other
The following options are typically unnecessary for configuring Host On-Demand. You should only use them if you are familiar with their usage.

Session Manager API
Select Enable Session Manager JavaScript API if you want to use JavaScript APIs to manage host sessions and text-based interactions with host sessions. These public APIs allow you to communicate with host sessions that are embedded in a Web page.

There are four sets of APIs:

• Session Manager APIs
• Presentation Space APIs
• Host On-Demand Functions APIs
• Error Reporting APIs

For details about how to use these JavaScript APIs, refer to the Session Manager API Reference.

Server connection
Use this option to configure the client to use the configuration servlet or a different configuration server port to communicate with the Host On-Demand configuration server.

Do you want to use the configuration servlet?
If you do not want the client to use the system default values that are specified in the config.properties file in the Host On-Demand publish directory, do the following:

1. Uncheck Use system defaults.
2. Select Yes to use the configuration servlet.
3. Specify the URL to where the configuration servlet is installed.
This will automatically override the URL specified in the config.properties file.

Check your Web server or servlet engine's documentation for instructions on how to pass parameters to a servlet.

If you want the client to connect directly to the configuration server using a different port other than the default port 8999 or than the port specified in the config.properties file, do the following:

1. Uncheck Use system defaults.
2. Select No to use the configuration servlet.
3. Specify the new port that the configuration server is listening on. You only need to change this from the default if you change what port the configuration server is listening on. This will automatically override the port specified in the config.properties file.

Language
Use the Language window to select the language to use for all client desktop and session frame messages. If users with different languages plan to access this HTML file, you should select Use the System Locale from the Language drop-down list.

Maximum sessions
Configure how many concurrent sessions each user can have open. When this number is reached, a user will not be able to open any more sessions (regardless of session type) until some currently-opened sessions are closed.