- HCL Z and I Emulator for Web server
- A compatible Web browser such as:
- Google Chrome v59.0.3071.115 or above
- Firefox v51.0.1 or above
- An Application server such as:
- IBM WebSphere Application Server v184.108.40.206 and above
- IBM WebSphere Application Server v220.127.116.11 and above
- Embedded Server
- Tomcat and
- Liberty Server
- A supported Client Operating Systems such as:
- Windows 10 and above
- RHEL 7.2 and above
- Mac OS 10.11 and above (Only Firefox browser is supported)
- Download the HCL ZIE for Web Client package from Flexnet.
- Extract the contents of HCL ZIE for Web Client package (.zip) file.
- Deploy the EAR (Enterprise Application archive) file on WAS using WAS Admin console – using all the default options.
- Restart WAS after deploying the EAR file. The ZIE for Web Client runtime. needs to be configured to connect to the ZIEWeb server.
- Click on ZIE for Web Client application on the applications page.
- Select “Initialize parameters for servlets” link on the Configuration page
- Configure the initial parameters of ZIE for Web Client application on WAS with Z and I Emulator for Web service manager and web server details.
In short: ZIEWebServer, ZIEWebServerPort and ZIEAlias point to the http-server part of the ZIEWeb Server (same data that is entered in the browser session).
ConfigServer and ConfigServerPort should only be required with Config based model clients. These values pick up default one. If the users have modified default settings, they need to provide the same in these fields.
Accessing ZIEWeb sessions
Configuration server based model pages
On the client PC, start a browser and navigate to
This can be a configuration model based page created using ZIEWeb’s deployment wizard or one of the default pages – default.html, defaultdebug.html.
Above URLs show a login page and users can login using their ZIEWeb server credentials.
HTML based model pages
On the client PC, open a browser and navigate to
This should be a HTML based model page created using ZIEWeb’s Deployment Wizard.
Session information in both cases is retrieved from the ZIEWeb server.