Introduction:

The HCL Z and I Emulator for Web (ZIE for Web) Deployment Wizard guides the user through the steps required for creating an HTML page to which users can connect to launch a client session. The Deployment Wizard has a quick and easy interface to help the users configure the many available features of the HCL Z and I Emulator for Web client.

Walk through for features:

Using HCL Z and I Emulator for Web Deployment Wizard, User can create a new HTML file that is like an existing one by editing the existing file, making changes (if any), and saving the new HTML file as a different file name. User can specify the new file name on the File Name and Output Format window of the Deployment Wizard without changing the original file. The new HTML file name will be the value specified by the user in the File Name field, and the file will be identical to the one user chose to edit, with any added changes.

Before asking for session information, the Deployment Wizard prompts to select which configuration model user want to use.

User can choose from three different configuration models, which are defined below:

  1. HTML-based model
  2. Configuration server-based model

Combined model

  1. HTML-based model:

Specifies that all session information is defined and managed in this HTML file. If this option is selected, the administrator uses the Deployment Wizard to define sessions in the HTML. Any changes the user makes are stored on the user’s machine. (However, Admin can still choose to not allow users to save any session changes or to lock properties.) If the Administrator then updates the session data using the Deployment Wizard, those updates will be merged with any changes the user has made previously. In this case, all user preferences will be kept unless the administrator chooses to override those preferences.

Benefits:

  • The configuration server is not used. Therefore, no need to start the ZIE for Web service manager unless ZIE for Web services, such as the Redirector, i5/OS and OS/400 proxy etc. are used.
  • Performance may be better than using the configuration server because no burden of large numbers of users accessing personalized configurations on the configuration server.
  • You do not have to create or maintain ZIE for Web User IDs.
  • There is no user logon.

Limitations (depending on environment):

  • If users make changes to their personal configurations, those changes may not be available on other machines without physically copying them.
  • If the administrator needs to define many different configurations, it may become cumbersome maintaining all the HTML files.
  • The Deployment Wizard does not run remotely. Therefore, there is no built-in mechanism for administering sessions remotely.
  1. Configuration server-based model:

Specifies that all sessions are configured and managed on the configuration server using the Administration Utility and that each user has an ID on the configuration server where user-specific information is maintained. Necessary configuration is stored in group or user IDs on the configuration server; user preferences, if allowed, are stored in the user’s ID. One user ID per user is required on the configuration server.

Benefits:

  • It allows users to access their personalized configurations from any machine with network access because those configurations are stored on the configuration server.
  • For large numbers of different configurations, it might be advantageous to organize them using the configuration server group and user structures.
  • It allows remote administration of sessions using the Administration Utility.

Limitations:

  • There are very high administrative requirements to create and maintain all of the user IDs.
  • Performance may be diminished with large numbers of users accessing personalized configurations in the configuration server.
  • Requires each user contacting the configuration server before using ZIE for Web.
  • Users must log on.
  • In this model, the Administrator uses the Administration Utility to define session information for users and Groups.
  1. Combined model:

Like the configuration server-based model, specifies that all session information is defined and managed on the configuration server using the Administration Utility (users get their default sessions from a specified group on the configuration server). However, unlike the configuration server-based model, necessary configuration information and user preferences, if allowed, are stored locally on the user’s machine rather than on the configuration server in the user’s ID.

Benefits:

  • No ZIE for Web User IDs to create or maintain.
  • Performance may be better than using the configuration server because, while you still have to access the configuration server, you will not have large numbers of users accessing personalized configurations on the configuration server (some information is stored locally).
  • There is no user logon.
  • For large numbers of different configurations, it might be advantageous to organize them using the configuration server group and user structures.
  • It allows remote administration of sessions using the Administration Utility.

Limitations (depending on environment):

  • If you make changes to your personal configurations, those changes are not available on other machines without physically copying them.
  • Performance may be diminished with large numbers of users simultaneously accessing the configuration server to obtain their default configurations. However, users will not be accessing the configuration server to obtain or store their user preferences.

HCL Z and I Emulator for Web Deployment wizard is available with Launcher Type options, which will allow user to choose between:

  • Java™ Web Start Launcher: When you run the client on a client workstation for the first time, it downloads the components of the Z and I Emulator for Web client from the Z and I Emulator for Web server and stores them on the hard drive of the client workstation. On subsequent usage of the client, it uses the components stored on the hard drive instead of downloading components from the server.
  • ZIEWeb Lite Client Launcher: When you run the client on a client workstation for the first time, the ‘zieclient.msi’ file gets downloaded to the local system. Users would need to click on ‘Run’ to install the ZIEWeb Lite Client Launcher. This is a one-time activity, and upon subsequent launches, the client gets launched directly by the ZIEWeb Lite Client Launcher. Required component files will be cached into user directory.

User can specify the file name and page name and can save the file to the publish directory with below output formats:

  • Output HTML: Creates the set of Deployment Wizard-generated files. This format is required for use by the Web server.
  • Output Zip: Creates a zip file of the Deployment Wizard-generated files.

To summarize, HCL Z and I emulator for web is offering the Deployment Wizard as a utilitarian administrative tool for creating emulator client HTML files to provide administrators a quick and easy build of ZIE for web HTML files that are customized for an organization’s needs.

References

https://zieweb.hcldoc.com/help/index.jsp

Contact

Praveen Shashikant

 

Comment wrap
Further Reading
a/icon/common/search Created with Sketch.