Limitations on accessing Host On-Demand through a portlet

The Portal environment supports full Host On-Demand functionality with the following limitations:
  • Although Host On-Demand supports Mac OS client browsers, it is not recommended for Portal environments.
  • When running multiple portlets on a single WebSphere Portal page, note the following:
    • Use the HTML-based configuration model.
    • Use Java when configuring portlets as cached clients.
    • Configure your portlets to be either download or cached clients, not a mixture of the two.
  • When using a Java–enabled browser for sessions that are configured to run in a separate window and that have the AssociateEmbeddedMenuBar parameter set to false, the menu for 3270 and 5250 host sessions displays as a pop-up menu. For Host Print and FTP sessions, the pop-up menu does not display by default. In order to display the menu for Host Print or FTP sessions, you need to configure the sessions to start in a separate window.
  • In order to embed the menu bar in the Host On-Demand session that is configured not to run in a separate window, you need to have a Java–enabled browser and the AssociateEmbeddedMenuBar parameter set to true (the default). In the following circumstances, the menu bar for 3270, 5250, VT, and CICS host sessions will display as a pop-up menu (and not embedded in the session):
    • The client browser is enabled with Java and the AssociateEmbeddedMenuBar parameter is set to false
    If the Host On-Demand session is configured to start in a separate window, the menu bar is always associated to the session window and cannot display as a pop-up menu.
  • If the portlet uses caching for Host On-Demand (as configured in the Deployment Wizard), each machine used to access the portlet caches the Host On-Demand client.
  • Host On-Demand bookmarking does not work in the portal environment.
  • If you do not configure an applet size in the Deployment Wizard, it will default to fixed size, medium.
  • When the Host On-Demand portlet is running, you may see warning messages like java.io.FileNotFoundException in the Java Console. The messages are caused by a dummy archive file name that the Host On-Demand portlet uses to enable multiple Host On-Demand portlets to run on a single portal page. These messages do not affect the performance of the portlet, so you may ignore them.