Common considerations and limitations

Following is a list of considerations and limitations when working with HATS standard portlets:
  • Portlets can only be installed in production as Web application archives (.war files). HATS only has one project per .war file, therefore you cannot export a set of HATS applications as a single portlet application.
  • Cookies are required to authenticate within WebSphere® Portal, therefore you must run HATS in WebSphere® Portal with cookies enabled.
  • JSP files, such as templates, transformations, transformation fragments, and macro handlers, copied from HATS Web projects to HATS standard portlet projects, will not work without conversion. You can use the Convert JSP for Portal action to convert these JSP files.
  • HATS options appear in the Rational® SDP New Portlet wizard, but selecting these options only generates an empty portlet without HATS resources.
  • When a HATS portlet is on the same portal page with other portlets (HATS or non-HATS), if you disconnect the HATS portlet, it is automatically restarted as a result of the page refresh that occurs when you interact with any other portlet on the same portal page. HATS standard portlets exhibit this behavior when the portal page theme is set to PortalWeb2.
  • When HATS portlets, that use certain HATS predefined templates, run on the same portal page, the templates may interfere with one another. This is caused if all the templates use the same cascading style sheet (CSS) rule names. This only affects CSS rule names in the template.jsp file, because the names are not prefixed with div#<portletName>. To work around this limitation do one of the following:
    • Use any of the following HATS predefined templates which do not have this limitation:
      • Finance
      • Industry
      • Medical
      • Research
      • Transport
    • Edit the template.jsp file and add the prefix div#<portletName> to each CSS rule. For example, if you have this in your template.jsp file: 
      A.BOTTOMBAR:visited, 
A.BOTTOMBAR:link, 
A.BOTTOMBAR:active {color: #55839A; font-size: 1em;}

table.ApplicationKeypad { 
	color: blue; 
	white-space: nowrap;	
}
      Assuming that the portlet project in named hatsPort914, change the example as shown below: 
      div#hatsport914 A.BOTTOMBAR:visited, 
div#hatsport914 A.BOTTOMBAR:link, 
div#hatsport914 A.BOTTOMBAR:active {color: #55839A; font-size: 1em;}

div#hatsport914 table.ApplicationKeypad { 
	color: blue; 
	white-space: nowrap;	
}
  • The following HATS functions, actions, and settings are not supported in HATS portlets:
    • Dojo widgets.
    • The Enable HTTP Compression setting.
    • The asynchronous update applet.
    • The disconnectOnClose connection parameter.
    • The screen combination option, use dynamic, cached content loading.
    • HATS interoperability with WebFacing applications.
    • HATS standard portlets can only run on WebSphere® Portal or WebSphere® Application Server platforms.
    • If you add Web Express™ Logon (WEL) support to a HATS standard portlet using the WebSphere® Portal Credential Vault plug-in, it will run on supported WebSphere® Portal servers. However, it will fail to log onto the host system when running directly on WebSphere® Application Server which does not have Credential Vault Service support.
    • The following HATS actions, settings, and functions are not supported in HATS standard portlets:
      • The ability to add HATS administrative console support to the portlet project.
      • The ability to generate sample code in the New Business Logic wizard for functions such as accessing and retrieving authentication data, portlet messaging, or using a property broker.
      • The Portlet Prepresentation (Add Block Delimiter) action.
    • When using the Send global variable action, the following actions are the only actions supported between the Apply transformation action and the Send global variable action:
      • Execute business logic
      • Extract global variable
      • Insert data
      • Set global variable
      • Remove global variable
      • Perform macro transaction
      • Pause
    • When using Integration Objects:
      • Only Model 1 Web pages are supported. Struts and JSF Web pages are not supported.
      • If you copy or rename a HATS portlet project, the Model 1 JSPs generated from a standalone or first in chain Integration Object refer to the wrong connection specification. You must modify the following statement: 
        SignOn.setHPubStartPoolName(“<new_project_name>/<default_connection>”);
      • When you generate a portlet project from a Web project, the Model 1 JSP pages previously generated from integration objects do not change. You must regenerate the pages, or make the changes manually.
      • Global variables and templates are not supported.
      • To run an Integration Object that is configured to use Web Express™ Logon in standard portlets, you must ensure PortletRequest is available in the Integration Object by calling setHPubPortletRequest(javax.portlet.PortletRequest) before executing the processRequest() method. For more detail, see Using Web Express Logon.
    • When viewing active host connections using the HATS administrative console, the client connection for a HATS standard portlet displays a blank IP address.