Developing and deploying HATS Web applications

Types of HATS applications include: Web, portlet, EJB, rich client, and administrative console. This chapter includes information about HATS Web applications. For information about the other types of applications, see the following topics:

In addition, a HATS Web application can be linked with a WebFacing application and both packaged together to interoperate with each other in a single enterprise application. For more information, see WebFacing and HATS.

HATS applications are created from HATS projects using the HATS Toolkit. When you create a new HATS project, a set of folders is created to help you organize your HATS application files. An example of a default project is shown below. The highest level folder has the same name as the name you give to your project when you create it. In that folder are other high-level folders that contain objects defined in your HATS project. Some folders do not appear until you create certain objects.

Depending on how you set up your HATS project, some or all of these folders appear in the HATS Projects view. You can also specify which folders appear in your HATS Projects view as well as hide file extensions. For more information, see Using HATS preferences.

Note:

Different folders appear for different types of HATS projects. For example, the directory tree for a HATS EJB project has no Screen Customizations, Screen Captures or Web Content folders.

You can create subfolders within these high-level folders to help organize your project. For instance, as you create screen captures for your project, you might want to create folders under the Screen Captures folder to organize and group the captured screens. To create a folder, right-click on one of the high-level folders in the tree and click New HATS > Folder. To move a file into a different folder, right-click on the file and select Move, or you can use the drag-and-drop method.

Note:

There is a limitation for subfolders. The transformation and the template files must be in subfolders of the same level. In order to use a transformation that resides at a certain level of subfolders, such as \transformations\Callup\, then the template that will be coupled with this transformation must be at the same level of subfolders, like \templates\Callup\.

HATS projects can be shared in a team environment by going to the Navigator View of your HATS perspective. Right-click the project and select Team > Share Project. Select the repository type from the list and click Next. Rational® SDP supports several repositories. For more information, refer to the Rational® SDP documentation and search on repository.

Note:

When using a version control system with your HATS projects, set the system to ignore the resourceUpdate.sts file. This file is automatically generated when testing a project within the toolkit. The file should not be under version control and can safely be ignored or deleted before placing a HATS project under version control.

To exclude the file from version control, open Window -> Preferences -> Team -> Ignored Resources and click Add Pattern to add a new pattern. Enter resourceUpdate.sts and click OK. Make sure the new pattern is selected in the list of ignored patterns and click OK to save the settings.

HATS Web projects, created in HATS Toolkit, are extensions of Web projects in the Rational® SDP workbench. For more information, click Help > Help contents from the Rational® SDP menu bar, expand Developing, and select Developing Web applications.