Installing your application in a runtime environment

After exporting the ZIETrans project as a Java™ EE application and transferring the application's .ear file to the production system, install it by launching the WebSphere® administrative console and browse to the location of the .ear file. For more information about installing applications on WebSphere Application Server refer to the WebSphere Application Server documentation at https://www.ibm.com/docs/en/was/9.0.5. In the contents under your WebSphere Application Server product, refer to the chapter about deploying applications.

After the application has been installed, test it by bringing up the URL in a Web browser on another system. Then you can publish the URL to your users. As an example, the URL might look like http://hostname/ZIETransappname/ where hostname is the IP host name and domain where WebSphere Application Server is installed and ZIETransappname is the name of your ZIETrans application.

Note:

For more information about installing ZIETrans applications on specific platforms, see Installing ZIETrans.
If your ZIETrans applications are deployed on WebSphere Application Server with Java 2 security enabled, and they do not start, see Java 2 security for more information.
ZIETrans supports multiple browser instances from the same workstation accessing the same ZIETrans application. However, these multiple browser instances must not share the same HTTP session id.
The session between the browser accessing the ZIETrans application and the WebSphere Application Server is assigned an HTTP session ID. The HTTP session ID enables subsequent requests from the same browser to return to the same ZIETrans application. Subsequent requests use the same Telnet (3270 or 5250) session that exists between the ZIETrans application on the server and the host.

Different browsers implement the HTTP session ID differently. Microsoft Internet Explorer expects all browser sessions in the same process to share the same HTTP session ID. When you launch a new browser window using the same shortcut, a new browser session starts and shares the same process and the same HTTP session ID.

One way to open a new Internet Explorer process with a unique HTTP session ID, in Windows XP for example, if Internet Explorer is in your start list, is to select Start > Internet Explorer. Selecting Start > All Programs > Internet Explorer also starts a new Internet Explorer process with a unique HTTP session ID.
Note:
1. The Ctrl-N function of Internet Explorer does not start a new process, because it opens a new window that has the same process ID and the same HTTP session ID as the window from which it originated.
2. For Internet Explorer 8, you can use File > New Session to open a new browser with a unique session ID.
Note:
In Internet Explorer, you can find the HTTP session ID for a browser window by selecting View > Source from the menu bar, or right-clicking in the Internet Explorer browser window and selecting View Source to view the source tagging for the page. Scroll down to the ZIETrans Form tag in the source window. Within that Form tag, find the SESSIONID parameter, which is similar to the following:
```
<INPUT TYPE="HIDDEN" NAME="SESSIONID" 
VALUE="PIOncS1GehNWxWo_49VCBzC" />
```
Note: When you access a ZIETrans application that only displays a default transformation of the screen and doesn't run macros when it starts, the SESSIONID has a value of "INVALID." The SESSIONID value is assigned when you send something to the host, such as pressing the Enter key, and you get a response.

You can verify whether a new process is being started by using Task Manager in Windows. Start Task Manager, and click the 'Image Name' column heading on the Processes tab to sort the information by image name. Scroll down to see how many 'iexplore.exe' processes are in the list. Try starting some new Internet Explorer windows using the Start > Internet Explorer shortcut. If a new process is started, a new iexplore.exe process is added to the display. Otherwise, an existing process is in control of the new browser window.
ZIETrans requires the application's display-name, as defined in the application's web.xml file, to match the Web application's context path used in the browser URL. If the display-name value is changed to be different than the context path of the application, you might encounter a java.lang.nullPointerException error or a javax.servlet.ServletException error when running the ZIETrans application. For example, a ZIETrans project named MyZIETransProject defaults to a display-name of MyZIETransProject. This project, when deployed as a Web application, must be reached with a URL similar to http://myServer/MyZIETransProject/ to operate properly. Changing the display-name to something other than MyZIETransProject causes the application to be inoperable.