Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX AAA Server A.06.00 Getting Started Guide: HP-UX 11.0, 11i v1 > Chapter 2 Installation

Installation and Start-Up Procedure

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

The following components are installed when you install the HP-UX AAA Server:

  • AAA Server binaries, libraries, and utilities

  • RMI objects that facilitate communication from the AAA server to Server Manager

  • AAA server AATV module for authentication

Perform the following steps to install and start the HP-UX AAA server:

  1. Log in to your HP-UX 11.0 or 11i v1 system as root.

  2. Verify the product dependencies are installed:

    # swlist |egrep "hpuxwsTomcat|T1456AA"
    hpuxwsTomcat A.1.0.00.01 HP-UX Tomcat-based Servlet Engine
    T1456AA 1.4.0.01.00 Java2 1.4 SDK for HP-UX
    IMPORTANT: Be sure you have the correct versions of the product dependencies installed.
  3. If needed, install HP-UX SDK (product #T1456AA) containing Java2 RTE 1.4.0.x

  4. If needed, install the HP-UX Tomcat-based Serverlet Engine v 1.0.00.01 (product # HPUXWST100001) or higher

  5. Download the AAA Server depot file from www.software.hp.com and move it to /tmp

  6. Verify you downloaded the file correctly: # swlist -d -s /tmp/<AAA Server>.depot

  7. Stop any active Tomcat processes. Use /opt/hpws/tomcat/bin/shutdown.sh to stop Tomcat.

  8. Install the AAA Server: # swinistall -s /tmp/<AAA Server>.depot

    NOTE: If the installation is not successful, an error message is displayed. The cause of the failure will appear at the end of /var/adm/sw/swagent.log file.
  9. After installing the product, you will need to add the following RADIUS authentication and accounting entries to the /etc/services file of your server hardware:

    # RADIUS protocol
    radius 1812/udp
    radacct 1813/udp
    NOTE: These RADIUS values are the server's defaults and are specified in the RADIUS RFC 2865.
  10. Edit the rmi.config.secret item in /opt/hpws/tomcat/webapps/aaa/WEB-INF/gui.properties and /opt/aaa/remotecontrol/rmiserver.properties so the two values are the same. This matching secret value is for secure exchange of information between Server Manager and the RMI objects.

    IMPORTANT: The rmi.config.secret you configure in /opt/aaa/remotecontrol/rmiserver.properties for all your AAA servers must be identical to rmi.config.secret in: /opt/hpws/tomcat/webapps/aaa/WEB-INF/gui.properties
  11. Start the RMI Objects by going to the /opt/aaa/remotecontrol directory and running the rmistart.sh script. See “Starting and Stopping the RMI Objects” for more information.

  12. Uncomment the following lines in /opt/hpws/tomcat/conf/web.xml:

    Commented

    <!-- The mapping for the invoker servlet -->
    <!--
    <servlet-mapping>
    <servlet-name>invoker</servlet-name>
    <url-pattern>/servlet/*</url-pattern>
    </servlet-mapping>
    -->

    Uncommented

    <!-- The mapping for the invoker servlet -->

    <servlet-mapping>
    <servlet-name>invoker</servlet-name>
    <url-pattern>/servlet/*</url-pattern>
    </servlet-mapping>

  13. Configure the Server Manager user name and password. Open /opt/hpws/tomcat/conf/tomcat-users.xml. Add your user name and password in the following syntax:
    <user username="specify" password="specify" roles="tomcat"/>

    Enter your values where "specify" is in the previous example. See “Changing Server Manager User Name and Password ” for more information.

  14. Start Server Manager. See “Starting and Stopping Server Manager” for more information.

    IMPORTANT: Always restart Server Manager after making changes to any of the HP-UX Tomcat-based Serverlet Engine configuration files.
  15. Point your browser to http://<IP-Address>:8081/aaa and log on to Server Manager using the user name and password you specified in the previous steps.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2003 Hewlett-Packard Development Company, L.P.