Administration Server Installation Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Installation

This chapter contains the following sections:

 

Installation Steps

To install the Administration Server:

  1. Shut down any processes on the machine.
  2. Unzip the installation ZIP file.

    3. The file name is OES10gR3_admin_win32.zip (Windows), OES10gR3_admin_solaris32.zip (UNIX), or OES10gR3_admin_linux.zip (Linux).

  3. Launch the install using one of the options described in Table 4-1.

    4. Table 4-1 Installer Launch Commands
    Platform
    Command
    Windows
    Start OES10gR3_admin_win32.exe
    Sun Solaris
    1. Change the protection on the install file by entering: chmod u+x OES10gR3_admin_solaris32.bin
    2. Enter: ./OES10gR3_admin_solaris32.bin
    Red Hat
    1. Change the protection on the install file by entering: chmod u+x oes320admin_linux.bin
    2. Enter: ./oes320admin_linux.bin

    NOTES:

    • If there is not enough temporary space, use add – Djava.io.tmpdir=<path>
    • (UNIX, Linux) The installation program loads in GUI mode if the machine supports Java-based GUI. Otherwise, it starts in console mode.
  4. Complete the installation prompts as described in Table 4-2.

    5. Table 4-2 Administration Server Installation 
    In this Window:
    Perform this Action:
    Welcome
    Click Next.
    Choose BEA Home Directory
    Select the default BEA home or use the Browse button to specify a different one. Then click Next.
    Choose Product Installation Directories
    This window carries forward the BEA home specified on the previous window. Accept the default values for the Administration Application and SCM and click Next.
    NOTE: If an earlier version of this product is detected, a window asks if you want to upgrade. To do so, click Next and see Upgrading from Earlier Versions.
    Choose Application Server for Administration Application
    Select the type of server that was installed to host the administration application and click Next.
    If you select Tomcat, also complete the Web Server Installation Directory field by navigating to and selecting the Tomcat directory. Then click Next.
    Warning: The Tomcat directory name cannot contain spaces.
    Choose Network Interfaces
    Select the IP address checkbox used to listen for requests to distribute policy and configuration data and click Next.
    Notes:
    • IPV6 is not supported.
    • For machines with multiple network cards, select an internal address to avoid exposing the SCM through a public address.
    Configure Administration Application
    HTTP Port (7000)—HTTP port for the application server’s (WebLogic or Tomcat) administration console.
    SSL Port (7010)—HTTPS port for the Administration Server.
    WARNING: The port specified must be the first of four consecutive ports reserved for use by the Administration Server. Failure to reserve these ports will prevent necessary component connections.
    CA Duration—Years the certificate remains in effect.
    Configure Database Connection
    Database client—Select the type from the dropdown list.
    JDBC URL—Replace the bracketed values. These vary by database type:
      <SERVER>—name/IP address of the database machine
      <PORT>—port number where the database listener is running
      <INSTANCE>—instance name to connect to on <server>
      <SID>—database SID of database
    JDBC driver—Accept the default
    Driver location—If required, browse to and select the directory.
    Login ID—user created using the database setup script described in Database Setup.
    Password and Confirm Password—user password.
    Install Database Schema—Accept the default to install the schema unless you are installing the server as a failover server.
    When you click Next, the JDBC connection is tested. If unsuccessful, you are re-prompted for the information.
    Key Protection Password Selection
    Generate Random Password—select to randomly generate key passwords for Administration Server components.
    Advanced Password Configuration—select this option if you want to specify these passwords. Then supply the passwords as prompted.
    These options are equally secure. The only reason for specifying your own passwords is that they are required to decrypt SCM and SSM cache files, which may be useful for debugging.
    Choose JDK
    The installation auto-selects a JDK. Accept this value or specify a different one.

  5. If the installer detects a previous version of the server, it disables the Install Database Schema checkbox and a window asks if you want to run the upgrade wizard. See Upgrading from Earlier Versions for instructions.
  6. On the Installation Complete window, click Done. If you selected to install the schema, a script will perform the following actions:
    • Create database tables and out-of-box objects
    • Load objects for starting the Administration Server.
    • Start the SCM and Administration Server
    • Load the administration policy

When the script completes, you may open the administration tools (see Starting the Administration Tools).

Note: If you did not install the schema and need to do so separately, see Installing the Policy Database Schema.

 

Upgrading from Earlier Versions

If the installer detects a previous version of the server, it disables the Install Database Schema checkbox and a window asks if you want to run the upgrade wizard.

Note: The upgrade wizard launches only when installing in GUI mode. To invoke it manually, run upgrade_ales_schema.bat|sh in BEA_HOME/ales32-admin/upgrade.

To upgrade, run the wizard to completion. After the wizard finishes, start the Administration Server and execute a script that adds policies to the database, as follows:

  1. When you see the Run Upgrade Wizard checkbox on the installation window, select it and click Done. This launches the wizard.
  2. On the initial window, click Next. A window displays status messages and then closes when the upgrade completes.
  3. Start the Administration Server.
  4. Run upgrade_policies.bat|sh located in BEA_HOME/ales32-admin/upgrade.
Notes:

  Back to Top       Previous  Next