Known Issues in Z and I Emulator for Transformation

This documentation gives you information about the known issues and possible workarounds (if any) in various versions of HCL Z and I Emulator for Transformation.

Note : This document is updated periodically as new information becomes available.

ZIETrans functionalities will not work if the user has an unsupported JRE version. In such a scenario, follow the below workaround steps to change the compiler version.

Step 1: Right Click on the project.

Step 2: Select Properties.

Step 3: Goto Java Compiler.

Step 4: Select Change JRE version 'Compiler Compliance level.'

Step 5: Click on Apply and Close.

ZIETrans Version 1.0

  1. Unwanted logs in the console :

  2. Even while running a Project in the normal mode, the Console shows a lot of additional information other than what are relevant to running the ZIETrans project.

  3. An incorrect link to Infocenter is seen in the console while running the project in Debug mode.

ZIETrans Version 2.0

  1. The Known issues in ZIETrans 2.0 will be updated here as and when an issue is identified in the product.

ZIETrans Version 2.0.1

  1. Unable to deploy on the liberty server from the toolkit. Follow the below configuration steps to deploy.

    Step 1: Rename the application.xml file.

    Example: Rename to "application1.xml"

    Step 2: Run the application.

    Note: After deploying the application, you can rename as application.xml and redeploy.

  2. HCL ZIETrans 2.0.1_CSRF attacker error message doesn't appear on Firefox or IE browsers.
  3. Web Application using Rest API is not running on Websphere Application Server. Follow the below steps as a workaround to deploy and run the application.

    Step 1: Navigate and open the EAR deployment.xml from the installed location on the server.

    Example: C:\IBM\WebSphere\AppServer_1\profiles\AppSrv02\config\cells\\applications\\deployments\\deployment.xml

    Step 2 : Set the class loader as PARENT_LAST by updating the deployment.xml with the below code.

    Step 2.1: Replace the below snippet.

    <classloader xmi:id="Classloader_xxxxxxxxxxxxx" mode="PARENT_FIRST"/>

    with

    <classloader xmi:id="Classloader_xxxxxxxxxxxxx" mode="PARENT_LAST"/>

    Step 2.2: Add warClassLoaderPolicy="SINGLE" attribute in <deployedObject> after enableDistribution="false".

    Step 3: Save the file and restart the server.

    Step 4: Run the application.