Using a stand-alone HATS administrative application

To administer HATS standard using a stand-alone HATS administrative application, follow these steps:
  1. Create a stand-alone HATS administrative project in the HATS Toolkit by selecting File > New > Project > HATS > HATS Administration Project. The HATS administrative project only appears in the HATS Toolkit on the Navigator tab.
  2. Export the HATS administrative .ear project to an .ear file by right-clicking the .ear project and selecting Export > Java EE > EAR.
  3. Deploy the .ear file for the stand-alone HATS administrative application to WebSphere® Application Server using the WebSphere® Application Server administrative console.
    Note:
    1. Install the .ear file to the same WebSphere® Application Server system as the WebSphere® Portal server. Where a standard HATS portlet is installed directly to WebSphere® Application Server, install the .ear file to the same server.
    2. Ensure the module is mapped to the WebSphere® Application Server, for example, server1, and not WebSphere® Portal Server.
    3. For WebSphere® Application Server V6.x, ensure the All Authenticated option on the Map security roles to users/groups panel is checked for the HATS Administrator role. For WebSphere® Application Server V7.x and V8.x, ensure the All Authenticated in Application Realm option is selected using the Map Special Subjects drop-down on the Map security roles to users/groups panel.
  4. The user id used to administer the portlets must be defined as a WebSphere® Application Server administrative console user with Administrator authority. To do so, follow these steps:
    1. From the WebSphere® Application Server administrative console, select Users and Groups > Administrative User Roles > Add.
    2. Enter the user id used to administer the portlets and map the user id to the Administrator role.
    Note:
    For more information, see HATS administrative console and WebSphere security.
  5. Start the HATS administrative application using the WebSphere® Application Server administrative console.
  6. Access the stand-alone HATS administrative console. For example, use the URL, http://<washostname>/<hatsadminprojectname>/hatsadmin/admin.
    Note:
    When accessing the HATS administrative console, you must use a different browser than the one being used to access the portlets.
    1. Select Getting Started > Management Scope.
    2. Click New.
    3. In the Host field enter the same host name as your target WebSphere® Application Server host.
    4. In the Port field enter the BOOTSTRAP_ADDRESS port for your target server. To find the BOOTSTRAP_ADDRESS port for your target server, access the WebSphere® Application Server administrative console and follow these steps:
      1. Select Servers > Application Servers.
      2. Click your target server (either WebSphere® Portal server, or WebSphere® Application Server, for example server1, in the case where a standard HATS portlet is installed directly to WebSphere® Application Server.
      3. On the Configuration tab under Communications expand Ports.
      4. Note the BOOTSTRAP_ADDRESS port for your target server.
    5. Click OK.
    6. Select the newly added host.
    7. Do not select Manage all applications within the scope selected above.
    8. You can now see a list of HATS portlets. Use the HATS Administrative console to administer one portlet application at a time by selecting one from this list.