HCL ZIETrans allows you to transform your user experience by extending 3270 and 5250 terminal applications to the web, portlet, rich client, or as standard SOAP or RESTful web services. By default, all HCL ZIETrans Web applications are stored in one enterprise archive file.

HCL ZIETrans Toolkit is an HCL ZIE component that enables you to develop new applications and allows previewing and saving each change. We can streamline the HCL ZIETrans application in such a way that it becomes easier to use the host applications whose data and functions it presents. The supported servers for multiple HCL ZIETrans applications in an ear are ‘WebSphere Application Server’ and ‘WebSphere Liberty’.

This blog describes the ways to manage the HCL ZIETrans web applications that have multiple .ear and multiple .war in the projects, using HCL ZIETrans Toolkit and the best practices.

When you export your applications as HCL ZIETrans EAR file and deploy them on WebSphere Application Server, the .ear file contains a Web archive (.war) file with the resources to run each application. An EAR may also combine multiple web projects (WAR), Enterprise JavaBeans projects (JAR), standard JARs, etc. into a single application.

Each individual .ear consumes around 25MB (minimum) of disk space during runtime. So, if you have multiple HCL ZIETrans projects you may end up having multiple HCL ZIETrans EAR of varying size depending on the complexity of the application. Based on different deployment or development scenarios may lead to developers/administrators opting for single EAR or multiple EAR’s deployment solutions.

The below table illustrates salient points of the ‘Individual’ Vs ‘Multiple wars in single’ EAR deployment method, based on these customers can decide their HCL ZIETrans application deployment architecture.

Table 1: Individual Vs Multiple wars in one EAR deployment

Ways to organize the HCL ZIETrans Web Applications:

Associating multiple .war or HCL ZIETrans projects with one .ear and de-associating can be achieved using deployment descriptor application.xml present in the META-INF folder of the EAR.

The sections below demonstrate

  • Creating individual .ear for each project on HCL ZIETrans Toolkit
  • Adding multiple .war to one .ear in application.xml
  • Removing .war from .ear in application.xml and deploying the same.

Creating individual .ear for each project

  1. Go to File->New-> ZIETrans Project. On the Create a Project console, specify a name for the
    Enterprise application project (.ear) to be created as shown.
  2. Click Next and specify connection settings. Click Finish.
A screenshot of a social media postDescription automatically generated

Figure 1: Create a project

 

The created project and EAR in the Navigator are displayed.

Figure 2: Created project

By default, all HCL ZIETrans Web applications are associated with existing enterprise archive file. Hence the next project will have a .ear name same as above ZIETrans_testOne_EAR. We could continue using it.

Or we can provide a different.ear name in step 1: ‘Create project’ dialog which will create separate .ear for the individual project.

Figure 3: .ear for the individual project

After creating individual ears and deploying it on server:


Figure 4: Individual ears deployed on server

 

Adding multiple .war to one .ear in application.xml

Initially, there are 4 projects in the workspace. Where, the project “testFour” is imported as folder into the workspace.

Figure 5: projects in the workspace

  1. Take project ear to which you want to add .war file to, for instance, ZIETrans_testThree_EAR. Expand the META-INF folder to find application.xml and double click to open the editor.

Figure 6: Deployment Descriptor Editor

As we see in ZIETrans_testThree_EAR, “testThree.war” is already present in the Overview section. Let’s add 2 others .war to it. for instance, testFour and testOne.

2. So to add .war, click on Add button shown on the right side of the Overview. Add Item window appeares. Click on Module and click OK.

Figure 7: Add Item window

3. The next window shows the available modules/projects in the workspace. Add these modules one by one. Select the module and click Finish. Save the application.xml.

Figure 8: Add modules

The Overview window is displayed as below:

Figure 9: Overview window

4. Deploy the ear on the server and the server.

Figure 10: Deploy the ear on the server

Removing .war from .ear in application.xml

  1. Select project ear from which we want to remove .war file from, for instance, ZIETrans_testThree_EAR. Expand the META-INF folder to find application.xml. Double click to open the editor.

Figure 11: Remove .war file

2. Let us remove testOne.war from the ZIETrans_testThree_EAR. Click on testOne.war in the Overview section and click on Remove button shown on the right side. Save the application.xml.

The Overview section after removing appears as shown below:

3. Deploying the ear on the server. Restart the server.

Figure 12: Deploy the ear on the server

Contact us

For further information on Organizing Web Applications in HCL ZIETrans, automation capabilities and Lab services offerings, please write to:

ZIO@hcl.com

Akshata Betageri

Developer, Lab Services

Comment wrap
Further Reading
Mainframes | January 22, 2021
Installing Z and I Emulator for Web
Z and I Emulator for Web (‘ZIEWeb’ or ‘ZIE for Web’) is a browser-based multi-platform application that is designed to be compatible with a wide range of browsers and operating systems. The product is tested with all the available versions of Chrome, Firefox, Edge, Safari, and other browsers to ensure that Users continue to have reliable access to host systems with benefits of browser-based technology. Salient features of ZIE for Web: Multi-platform browser-based emulator API Support Support for IBM system Z and I Language support English and Japanese Transport Layer Security(TLS) Installing ZIE for Web ZIE for Web can be installed on all the supported platforms using Installation Manager. Select File > Preferences. 2. Select Repositories in the left panel. This option shows all the available repositories that have been added to the Installation Manager. 3. If HCL ZIE for Web is not listed, then Select the Add Repository button on the right side. 4. Click Browse and navigate to the location of the extracted HCL ZIE WEB path and select the diskTag.inf file present in disk1 folder. 5. Click OK, to add the new repository location to the list. 6. Click Test Connections to ensure that the Repository URL is available. 7. From the Home page of the Installation Manager, click Install. The Installation Manager searches the defined repositories for available packages. 8. Select the ‘Z and I Emulator for Web’ package. Click Next. 9. Read the license agreements. If you agree to the terms of the license agreement, select the checkbox against ‘I accept the terms of the license agreement’, and then click Next to continue. 10. Select the required architecture and click on Next. 11. Select the languages that you want to install. The default language is English. Click Next. 12. Review your selection and provide the...
Mainframes | November 19, 2020
INTRODUCING HCL Z ABEND INVESTIGATOR
HCL Software is pleased to introduce Z abend Investigator. This blog talks about how ZAI provides precise real-time problem analysis to help developers swiftly recover failed applications.
Mainframes | October 14, 2020
HCL ZIE for Web Hardware and Software Pre-requisites
HCL Z and I Emulator for Web provides secure host access to Users in intranet-based and extranet-based environments. Z and I Emulator for Web is installed on a Web server, simplifying administrative management and deployment, and the Z and I Emulator for Web applet or application is downloaded to the client browser or workstation, providing user connectivity to critical host applications and data.   1.1. System Requirements This document provides the system requirements for Z and I Emulator for Web, version 1.0. Higher maintenance levels, such as fix packs and service packs, may be supported as they become available. 1.2. Supported Environments Client Environment Details Client Operating System/Architecture Client Java Java Version Java Architecture Browser Version Browser Architecture Client Type Red Hat Enterprise Linux (RHEL) 7.6 - 64-bit Oracle Java Runtime Environment (JRE) 1.8_221_11 32-bit 74 Mozilla FireFox 32-bit Java Network Launching Protocol (JNLP) Red Hat Enterprise Linux (RHEL) 7.6 - 64-bit Open Java Development Kit (JDK) 1.8.0_242 64-bit 75 Mozilla FireFox 64-bit Launcher Red Hat Enterprise Linux (RHEL) 7.6 - 64-bit Oracle Java Runtime Environment (JRE) 1.8_221_11 32-bit 74 Mozilla FireFox 32-bit Launcher Ubuntu 18.0.4 - 64-bit Oracle Java Runtime Environment (JRE) 1.8_221_11 32-bit 74 Mozilla FireFox 32-bit Java Network Launching Protocol (JNLP) Ubuntu 18.0.4 - 64-bit Open Java Development Kit (JDK) 1.8.0_242 64-bit 75 Mozilla FireFox 64-bit Launcher Ubuntu 18.0.4 - 64-bit Oracle Java Runtime Environment (JRE) 1.8_221_11 32-bit 74 Mozilla FireFox 32-bit Launcher Red Hat Enterprise Linux (RHEL) 6.10 - 64-bit Open Java Development Kit (JDK) 1.8.0_242 64-bit 60.3 Mozilla FireFox 64-bit Launcher Windows 10 - 64-bit Open Java Development Kit (JDK) 1.8.0_242 64-bit 44.18362 Edge 64-bit Launcher Windows 10 - 64-bit Open Java Development Kit (JDK) 1.8.0_242 64-bit 75 Mozilla FireFox 64-bit Launcher Windows 10 - 64-bit Oracle Java Runtime Environment (JRE) 1.8_221_11 64-bit 80 Chrome 64-bit Launcher Windows 10 - 64-bit...
a/icon/common/search Created with Sketch.