Software > WebSphere >

WebSphere Host Access Transformation Services

Technical detail

This technical information is for HATS V4, formerly known as Host Access Transformation Server

Deploying HATS applications on an iSeries server

You can deploy a Host Access Transformation Server (HATS) application to a WebSphere Application Server running on an iSeries server to transform 5250 or 3270 applications residing on that machine or on other server systems.

Running a HATS application on iSeries requires:

OS/400 V5R1 or V5R2 with the latest cumulative PTF fix package applied
WebSphere Application Server (WAS) with the latest iSeries Websphere Group PTFs. To see the currently available Group PTFs, go to http://www-1.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/services/service.htm. Below are the specific levels of WAS that are supported.
- WAS V4 with fix pack 3 or higher. Both WebSphere Application Server, Advanced Single Server Edition (5733-WS4) and WebSphere Application Server Advanced Edition (5733-WA4) are supported.
- WAS V5 (HATS WAS V5 support requires that your HATS applications are built by HATS Studio V4 installed as a WebSphere Studio V5 toolkit with HATS fix pack 4.0.1 applied). The following WAS V5 products are supported:
  - WAS - Express for iSeries (5722-IWE)
  - WAS V5.0 for iSeries ("Base Edition") (5733-WS5)
  - WAS V5.0 for iSeries ("Network Deployment Edition") (5733-WS5 - Feature Code 4422)
21 MB of disk space per HATS application.

This documentation is intended to describe anything that is unique about HATS on iSeries. It is expected that you also use HATS Getting Started, and the HATS Developer's Guide as sources of information on HATS, and that you review the HATS Readme .

To deploy the HATS application on iSeries, move the .ear file to the iSeries machine, then use the WAS Administrative Console to deploy the application, following the instructions in the WebSphere for iSeries Documentation Center for Administering enterprise applications and modules.

For iSeries WebSphere Application Server documentation, see,

http://www-1.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/docs/doc.htm.

Configuring directory permissions for HATS applications deployed on WebSphere Application Server V4.0 Advanced Edition

HATS applications rely on being able to write to the file system in the directory in which they are installed. HATS applications installed using the WebSphere Advanced Edition Administrative Console on iSeries are installed under the authority of the QEJB userid. However, all WebSphere applications run under the QEJBSVR userid. If you install a HATS application using the WebSphere Advanced Edition Administrative Console on iSeries, you must ensure that the QEJBSVR userid has the appropriate permissions.

In order to enable the QEJBSVR userid to write to the file system in the directory in which the HATS application is installed, you must give the QEJBSVR userid the proper authority to write to the .../installedApps/... directory. You must do this after you have installed your HATS application using the WebSphere Administrative Console.

One procedure to set the proper authority is as follows:

Determine the directories in which your HATS enterprise applications (.ear) and web applications (.war) are installed. Typically, they will be QIBM/UserData/WebASAdv4/<instanceName>/installedApps/<hats.ear_name> and QIBM/UserData/WebASAdv4/<instanceName>/installedApps/<hats.ear_name>/<hats.war_name>, where instanceName is the name of the WebSphere administrative server instance that you installed your HATS application to, and hats.ear_name and hats.war_name are the names of the HATS .ear and .war that you have installed.

Check the authorities for your directory by running this command: WRKAUT OBJ('myDirectory') where myDirectory is the fully qualified path name of the directory that contains the .war or .ear file. For example, WRKAUT OBJ('QIBM/UserData/WebASAdv4/default/installedApps/hats.ear'). Verify that the command output lists *RWX data authority for QEJBSVR, as shown here:

Opt	User	Data Authority
_____	_____	_____
	*PUBLIC	*RX
	QEJBSVR	*RWX

To add authority for the QEJBSVR user profile, use option 1 (Add user authority) as shown here. You may also use option 2 to Change user Authority if QEJBSVR is listed but does not have *RWX Data Authority:

Opt	User	Data Authority
1	QEJBSVR_____	*RWX_____

Procedure for enabling graphing support for HATS on iSeries

HATS enables you to transform host data such as tables into graphs on a Web page. Some additional iSeries software and configuration is required in order to support the complete graphing capabilities of HATS applications running on iSeries. The additional software provides Java Abstract Windowing Toolkit (AWT) methods via Native Abstract Windowing Toolkit (NAWT). The additional software is not included with the IBM Developer Kit for Java, 5722JV1, licensed product. Note that you cannot use Remote AWT (RAWT) to enable graphing for HATS because HATS graphing requires com.sun.* classes, which are not supported via RAWT.

For more information about NAWT, please refer to the iSeries Information Center at http://publib.boulder.ibm.com/iseries/v5r2/ic2924/index.htm?info/rzaha/nawt.htm

This additional software is required to support the graphing function:

5722SS1/Option 33 - Portable App Solutions Environment (PASE)
5799PTL - iSeries Tools for Developers PRPQ
For OS/400 V5R1, PASE 5722SS1 PTFs SI01551 and SI08230 are required
For OS/400 V5R2, PASE 5722SS1 PTF SI08232 is required

Follow these steps to install and configure the required software:

Obtain the required software and make the media available to the iSeries machine.
Log into an iSeries command prompt with QSECOFR authority.
To install Portable App Solutions Environment, issue the following command:
RSTLICPGM LICPGM(5722SS1) OPTION(33)
Ensure that the required PASE PTFs are installed.
To install iSeries Tools for Developers PRPQ, issue the following command:
RSTLICPGM LICPGM(5799PTL)
Make the directory to store the password for the VNC server (note that if you have configured WebSphere to run under a userid other than QEJBSVR, you will have to create a directory structure for that userid):
MKDIR DIR('/home/QEJBSVR')
MKDIR DIR('/home/QEJBSVR/.vnc')
Run the following commands to assign the appropriate permissions to the /home/QEJBSVR directory tree (or whatever directories you created in step 6):
STRQSH CMD('chown -R QEJBSVR /home/QEJBSVR')
Create the password file required by the VNC server. Note that you will be asked for a password that will be stored for the VNC server to use at start up:
QAPTL/VNCPASSWD USEHOME(*NO)PWDFILE('/home/QEJBSVR/.vnc/passwd')
Start the VNC Server under the QEJBSVR userid (or whatever userid your WebSphere Application Server runs under):
SBMJOB CMD(CALL PGM(QP2SHELL) PARM('/QOpenSys/QIBM/ProdData/DeveloperTools/vnc/vncserver_java' ':1')) USER(QEJBSVR) JOBQ(QSYSNOMAX)
It is possible to enable automatic startup of the VNC server each time that the system is restarted. Refer to the QSTRUPPGM system value in theOS/400 Work Management Guide (SC41-5306).
You may also view the log files for the VNC server by issuing DSPF '/home/QEJBSVR/.vnc' and displaying the .log files.

Start the WebSphere Administrative Console, then follow these steps:

For WebSphere Application Server Advanced Edition V4:
1. In the left pane, click the Nodes folder.
2. Click the folder corresponding to the name of your system.
3. Click the WebSphere Application Server to which you have deployed your HATS application, for example, Default Server.
4. The WebSphere Application Server must be restarted to implement these changes. Right-click the WebSphere Application Server, then choose Stop. Click OK to continue after the Application Server has stopped.
5. Right-click the WebSphere Application Server, then choose Properties.
6. Click the General tab.
7. Click the Environment button to open the Environment Editor.
8. In the Environment Editor, Click Add
9. Enter DISPLAY in the Name column and <host_name>:1 in the Value column, where host_name is the TCP/IP host name of your system. For example, myHostName:1.
10. Click Add again.
11. Enter XAUTHORITY in the Name column and /home/QEJBSVR/.Xauthority in the Value column.
12. Click OK to close the Environment Editor.
13. Click Apply on the Administrative Console.
14. Click the JVM Settings tab
15. Under Classpaths, click the Add button.
16. Enter /QIBM/ProdData/Java400/jdk13/jdkawt.jar
17. Scroll to System Properties and click the Add button.
18. Enter os400.class.path.rawt in the Name column and 2 in the Value column.
19. Click Apply on the Administrative Console.
20. Right-click the WebSphere Application Server, then choose Start to restart it.
For WebSphere Application Server Advanced Single Server Edition V4:
1. In the left pane, open the Nodes folder by clicking the plus sign.
2. Open the folder corresponding to the name of your system.
3. Open the Application Servers folder.
4. Open the folder to which you have deployed your HATS application, for example, Default Server.
5. Open the Process Definitions folder.
6. Click Process Definition.
7. Under Advanced Settings, click Environment.
8. Click New.
9. Enter DISPLAY in the Name field and <host_name>:1 in the Value field, where host_name is the TCP/IP host name of your system. For example, myHostName:1.
10. Click OK.
11. Click New again.
12. Enter XAUTHORITY in the Name field and /home/QEJBSVR/.Xauthority in the Value field.
13. Click OK.
14. Under the Process Definitions folder, click JVM Settings.
15. Under Advanced Settings, click System Properties.
16. Click New
17. Enter os400.class.path.rawt in the Name field and 2 in the Value field.
18. Click OK.
19. Make sure you save your updated configuration.
20. Click Application Servers.
21. Click Stop.
22. Click OK. The browser will go to an error page.
23. Restart the WebSphere Application Server instance by issuing these commands from the iSeries command prompt:
  1. QSH
  2. cd /QIBM/ProdData/WebASAEs4/bin
  3. strwasinst -instance <instanceName>, where instanceName is the name of the WebSphere Administrative server instance that you have installed your HATS applications to. For example, strwasinst -instance default.
  4. When you see the message that indicates that the strwasinst command has completed, press F12 to exit the QSH session
For WebSphere Application Server V5:
1. In the left pane, open the Servers folder by clicking the plus sign.
2. Click on the Application Servers link.
3. In the right pane, click on the link of the application server that your HATS application is deployed to. For example, server1.
4. On the Configuration tab of the server, under Additional Properties, page down to the Process Definition link. Click the Process Definition link.
5. Under Additional Properties, click the Environment Entries link.
6. Click New.
7. Enter DISPLAY in the Name field and <host_name>:1 in the Value field, where host_name is the TCP/IP host name of your system. For example, myHostName:1.
8. Click Apply. Click OK.
9. Click the Environment Entries link again.
10. Click New.
11. Enter XAUTHORITY in the Name field and /home/QEJBSVR/.Xauthority in the Value field.
12. Click Apply. Click OK.
13. Now click the Java Virtual Machine link.
14. Under Additional Properties, click Custom Properties.
15. Click New
16. Enter os400.class.path.rawt in the Name field and 2 in the Value field.
17. Click Apply. Click OK.
18. Make sure you save your updated configuration.
19. Logout of the Administrative Console.
20. Restart the WebSphere Application Server by issuing these commands from the iSeries command prompt:
  1. QSH
  2. cd /QIBM/ProdData/WebAS5/Base/bin
  3. stopServer <serverName>, where serverName is the name of the application server that you have installed your HATS applications to. For example, stopServer server1.
  4. Wait for completion messages that say that the application server has stopped.
  5. Restart the server by entering startServer <serverName>, where serverName is the name of the application server that you have installed your HATS applications to. For example, startServer server1.
  6. When the startServer command completes, press F12 to exit the QSH session