Admin Console

The Admin Console is a web-based solution for managing various user and session configurations. Administrators can manage and configure the User and Session Properties.

Admin Console is deployed along with ZIEWeb-Client EAR file. Adding ‘/adminconsole’ to the ZIEWeb-Client URL will launch the Admin Console Login page.

Note: Only Admin users can log in to the Admin Console.

Sample Path: http://<IPAddress>:<port>/<contextpath>/adminconsole

Below are the Admin Console Properties:

1. USERS:

This Tab contains information about Groups and Users. All the groups and user configurations can be done here.

Following are the operations:

  • Create, Update, Delete Group
  • Create, Update, Delete User
  • Copy/Cut & Paste a User from one Group to other.
  • Manage Disable Functions of Group/User.
  • Trace Facility option is available for User.
  • Create, Update, Delete Sessions for User/Group.

2. SESSIONS:

  • Create a Session or Import Session. (Supports Only 3270 and 5250 Display)
  • Start Session, opens a popup with session launched.
  • Delete will delete the selected session.
  • Click on Properties will open Window to modify Session Properties.
  • Export will download session properties file with ‘.ws’ extension.
  • Keyboard mapping can be done by clicking on keyboard icon.
  • Copy Session from once User/Group to other User/Group by clicking on Copy Session option on Session and paste Session option on User/Group.

3. SERVICES:

This Tab allows to manage services like os400 and redirector.

  • Start/Stop the Service
  • Start/Stop Trace
  • Configure Service
  • Update Service Trace Manager Properties (Common for all services)
  • Server Log (Common for all services)

Redirector: creating, updating, deleting of a redirector can done by clicking on configure icon.

OS400: configuration like port and connections information can be updated on clicking of configure icon.

4. DIRECTORY:

This tab allows to Configure LDAP information and have option to migrate from files to LDAP and vice versa.

If LDAP is configured, all the User information will be populated from LDAP Directory. there will be changes in User Tab as well.

Following are the changes.

  • Groups will be shown in Hierarchy manner. One group can be created under Existing Group.
  • Until delete of all subgroups parent group will not be deleted.

5. HOST CONNECTIONS:

This tab allows to manage all host connections or sessions which are connected to host.

Admin can disconnect and toggle display terminal by selecting particular session. Also, provides filer options to filter host connections.

6. LOG SETTINGS:

Displays all the logs of session. History of log files can be selected and view the logs of selected file.

Download Selected log file by clicking on download. and selected Log file can be cleared by clicking on clear Log button.

Log Settings like file name, max size, no: of history files, can be updated by clicking on log Settings Icon.

7. TRACE SETTINGS:

Trace settings can be updated in this Tab. Download & clearing the Trace buttons are available here.

Trace Settings Options:

  • Server Tracing
  • User Macro Tracing
  • Display Terminal
  • Trace Output

All above Tracing related properties can be modified in this Tab.

8. Preferences (Control):

It enables admin to set preferences values.

Once Changes happen, The ZIEWeb command server restarts the web application service.

Note: The web.properties file should be present in ZIEWeb private directory\

9. Migration Utility:

The Migration Utility in the ZIE for Web client admin console serves as a web view for the traditional HOD Migration Utility, which allows the ZIE for Web client administrators to migrate the HOD user profiles and data from a lower to a higher version.

This module includes the Export, Import, and Rollback process.

Export

This process allows users to export the HOD data into a Migrationpackage.zip file which gets downloaded to the browser-configured download location on successful export.

Below inputs are provided by the users:
  1. Provide the complete HOD source installation path (mandatory field)

    Example: C:\Program Files\HCL\ZIEForWeb_2.2.0.0

  2. Provide the complete path of custom files except for the default location, i.e., HODObjs

    Example- C:\hcl\CustomFiles

The exported package consists of the HOD user files, the custom files (like kmp, .col, .mac) provided by the user, and ‘Exportinfo.txt’.Note: The path provided must have read/write permission.

Import

This process allows users to import the lower version of HOD data to migrate to a higher version as a .zip file.

Below inputs are provided by the users:
  1. Browse the MigrationPackage.zip file that needs to be imported (mandatory field).
  2. Provide the complete Target HOD installation path (mandatory field).

    Example- C:\Program Files\ibm\HostOnDemand15.0.0.0

  3. Next, the ‘Target Backup’ option (by default checked) creates the backup server files of the target HOD.

  4. There are options to override the directories (by default checked), which include ‘Private Directory, Publish Directory, PDFPdt, and Dirutils.’
  5. Next, the ‘Other optional settings’ link is available to override multiple keys and values.The mandatory dropdown allows users to select any of the following options:
    • Terminal
    • FileTransfer
    • Icon
    • FTPTerminal
    • dbaOptions targetUI
    Example: Icon – autoLaunch(Key) – false(value) .
    Note: key-value pair field should not be left blank.

On successful import, the NCService Manager will hang on until restart.

Migration Utility

This release includes the ability to override the 'Terminal' properties of configuration user profiles during import.

Users provide the following inputs for the configuration migration utility:

  1. Browse and import the ConfigParameters.properties file, which must contain ‘Terminal’ parameters as a key and value pair.

    Example: portBackup1(key) = 23(value)

  2. Provide the complete Target HOD installation path and click Import.

    Example- C:\Program Files\HCL\ZIEForWeb_2.2.0.0

  3. On successful import, the .user files under ZIEWEB private directory will be overwritten.Note:
    • .properties files disable the directories such as TargetBackupin the import panel.
    • On successful import, the NCService Manager will hang on until restart.

Limitations

ZIE for Web client must be accessed on the same machine as the source and target ZIEWEB servers.

The source and targeted ZIEWEB are independent of versions.

The supported ZIEWEB versions are ZIEWEB 1.0 , 2.0 and its refresh packs.

10. Deployment Wizard

The Deployment Wizard in the ZIE for the web client in the admin console is a WebView of the traditional deployment wizard, which is used to create the HTML pages and edit the same. This feature includes creating of the HTML pages along with the sessions and editing of the HTML pages that were created using the deployment wizard.

Create:

During the time of creation unlike the traditional deployment wizard, we wouldn’t be having the option to choose the directory where we want to save the HTML pages, by default the HTML pages would be created in the publish Directory that is ZieWeb.

When we go to the Deployment wizard section in the ZIE Web we have 3 options to choose, HTML based model, config server based model, and combined model, we must choose one of them to proceed to add the sessions.

While creation of the files in the summary panel by default the HTML is selected, and it cannot be unchecked.

Edit:

If there are no created pages already available in the publish directory then we get the message “Please Create a file before editing”, else it would display the list of the pages created by the Deployment wizard that are present in the publish directory. After selecting a row from the list. We will be able to proceed further.

After selection of the model there is host sessions page, where there is option to add sessions, copy sessions, delete sessions, and start sessions. For each session added there is option to import or export the keyboard, along with that there is an option to enable or disable certain feature for each session.

In the properties section there is option to unlock or lock the specifications so that they cannot be altered if they are locked.

The host sessions pages come up only if html model is selected, if the config server model is selected then the USERID needs to be added to access those sessions of that user. In the case of combined model, the group needs to be mentioned whose sessions need to be added.

Post adding the sessions we come across the additional options page where we have three in page options that is cache client options, advanced options, and preload options. The cache client options are majorly used for the size of the screen that displays the progress of the download of jars.

Preload options provide the list of the jars that would get downloaded, generally the user can select the jars they want it to get downloaded based on the sessions that they have added.

Advanced options provide the option to add the HTML parameters, codebase, HTML templates, Problem determination, masking the critical information, language, and maximum sessions options.

Post going through the additional options they move to the summary panel, which gives the summary of the file that is being created.

After the successful creation of the file, we get the option to open the session either in the java client or web client.

When the user edits the file, before creation of the file user gets the popup to decide whether they want to override if the name of the file is same, if the name of the file is different or is not present in the publish directory then it will directly create it.

11. Screen Timers

In milliseconds, the nominal amount of time waits while analysing outbound data using screen-settling strategies.In the admin console module, users can customize screen timers.
  1. Maximum time to wait for the screen to settle: This value is the minimum screen-to-screen delay. A higher value increases the reliability of screen transformations in case of delays at the host due to long processing times or network delays. The default value is 1200milliseconds.

  2. Minimum time to wait for initial host screen: The minimum amount of time taken from the time communications are initiated with the host until trying to recognize an initial screen. This value can be decreased for fast networks to improve initial screen response time.

    The default value is 2000 milliseconds.
    Note: To reflect the changes, restart the ZIE for Web client ear/war module.

List of Properties used in the Admin Console:

1) Webpage Properties (web.properties)

  • Status Bar Visible for all - Boolean (True or False). Lock Required.
  • Status bar editable by admin - Boolean (True or False).
  • Client Refresh Interval – Integer
  • Quick Connect – Boolean
  • Default Locale – Select Option
  • Preferred Locale – Multiple Select Option
  • Template URL – file path (C:\\Users\\test\\custom UI\\UI.jsp)

Note: If web.properties file does not exist, it will be created at the backend and saves properties with default values.

Default Values for web.properties:

  • templateURL – blank
  • QuickConnectByAdmin – false (disabled)
  • enableStatusBarForAll – false (disabled)
  • clientRefreshInterval – false (disabled)
  • defaultLocale- en
  • isStatusBarEditableByAdmin – false (disabled)

2) Web Server Properties (config.properties)

  • Server Port - Number
  • Secure Port - Number
  • Publish Context Path - Text
  • Licence Manger Context Path – Text
  • Amcms Context Path - Text

NOTE: If the web.properties file is not present under the ZIEWeb private directory, then launch the ZIEWeb-Client admin console and click on Preferences tab to create the default values under private directory.

Default values for config.properties:

  • AllowBlankPassword – YES
  • enableChannelConnection – true
  • publishDirContextPath – zie
  • WebAppServerPort - 8080
  • WebAppServerSecurePort – 8443
  • lmContextPath – lm
  • zfpClientContextPath – zieweb

Web app service port is displayed under services -web app service user can change the service port and restart the service to reflect the change.

Limitations:

1) Currently Web Based Admin Console only allows to create and manage 3270 & 5250 Display.

2) Web Express Logon Configuration is not implemented.

3) Creating admin user cannot be done through Admin Console.