WebSphere® Portal and HATS

IBM® WebSphere® Portal gives you a single point of access to Web content and applications, personalized to each user's needs.

HATS integration with WebSphere® Portal lets data flow freely between HATS, WebSphere® Portal, and other Portal applications. All of the relevant features of WebSphere® Portal are also available for exploitation within HATS by built-in tooling or straightforward Java™ development. The majority of HATS functionality is preserved when running HATS in the WebSphere® Portal environment. See HATS portlet considerations and limitations for more information.

HATS applications can run directly within WebSphere® Portal as portlets, enabling WebSphere® Portal and HATS to interact directly. You can develop HATS portlets that comply with the standard Java™ Portlet Specification API (JSR 168 or JSR 286), hereafter referred to as the standard portlet API.

Note:
Throughout this document, HATS portlets that comply with the standard portlet API (JSR 168 or JSR 286) are referred to as standard portlets. Where a distinction is required, JSR 168 or JSR 286 is noted.

HATS Business Logic classes are able to use the WebSphere® Portal APIs, and HATS JSPs are able to include WebSphere® Portal JSP tag libraries. For more information about programming portlets and advanced portal features, refer to the Programming in HATS Portlets.

A HATS portlet project is targeted at transformation oriented applications. For adapting Model 1 Integration Object based applications to run in WebSphere® Portal, refer to the Programming in HATS Portlets. For converting Struts Integration Object based applications to run in WebSphere® Portal, refer to documentation for your level of WebSphere® Portal at https://www.ibm.com/docs/en/was/9.0.5.

For more information and help regarding the Portal Tools, select the Help menu on the Rational® SDP toolbar and select Help Contents. Click Developing portal and portlet applications from the help list on the left to access documentation for portlet developers.

Migrating a HATS IBM® portlet to a HATS standard portlet must be done manually. The steps involve:
  1. Migrating project facets.
  2. Migrating Web and portlet deployment descriptor files.
  3. Migrating transformations, templates and macro handlers.
  4. Migrating HATS specific files.
  5. Migrating other portal functions (optional).