> Installing the Administration Server > Post Installation Tasks

Installing the Administration Server

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

Post Installation Tasks

This section discusses the steps you need to take after installing the Administration Server.

 

Installing the Policy Database Schema

The installer program offers you the option of installing the policy database schema as part of the installation procedure. There are two situations in which you should not install the database schema again:

If you have not installed the policy database schema, you must do so now; otherwise, you will not be able to the start the Administration Server processes.

Before beginning this procedure, ensure that you have completed the following configuration and setup steps:

For instructions for installing the database schema, see the following topics:

Installing the Policy Database Schema on Windows

To install the policy database schema in a Microsoft Windows environment, perform the following steps:

  1. Change to the active directory in which to install the database schema, for example:
    2. cd \bea\ales22-admin\bin
  2. To install the database schema:

    3. For an Oracle database, type: 

    install_schema_oracle.bat server dblogin dbpassword enterprise_domain [policyowner]

    For a Sybase database, type: 

    install_schema_sybase.bat server database dblogin dbpassword enterprise_domain [policyowner]

    Where:

    • server—The name of the Oracle net service name or Sybase server name.
    • database—The name of the Sybase database.
    • dblogin—The username to use to access the database; the username for the database administrator. Owner of the policy database (optional, defaults to the user login, usually the same as the username). The policy owner is a database username or user ID that controls the database schema in the database instance.
    • dbpassword—Password to use to access the database; the password for the database administrator.
    • enterprise_domain —The name of the enterprise domain. The enterprise domain name is used to link all the components and is referred to as the Enterprise Domain Name when you installed the Administration Server.
    • [policyowner] —The Owner of the tables/schema in the policy database.

For more information on the database schema installation, examine the install_schema_oracle.log or install_schema_sybase.log in the log directory.

Installing the Policy Database Schema on Sun Solaris

To install the policy database schema in a Sun Solaris platform, perform the following steps:

  1. Change to the active directory in which to install the database schema, for example:
    2. cd /bea/ales22-admin/bin
  2. Locate the script install_schema_dbtype.sh

    3. Important: Make sure all scripts in this directory have execute permission.

  3. To install the policy database schema, perform the following steps:

    4. For an Oracle database, type: 

    install_schema_oracle.sh server dblogin dbpassword enterprise_domain [policyowner]

    For a Sybase database, type: 

    install_schema_sybase.sh server database dblogin dbpassword enterprise_domain [policyowner]

    Where:

    • server—The name of the Oracle net service name or Sybase server name.
    • database—The name of the Sybase database.
    • dblogin —The username to use to access the database; the username for the database administrator. Owner of the policy database (optional, defaults to the user login, usually the same as the username). The policy owner is a database username or user ID that controls the set of database schema in the database instance.
    • dbpassword—The password to use to access the database; the password for the database administrator.
    • enterprise_domain - Name of the enterprise domain. The enterprise domain name is used to link all the components and is referred to as the Enterprise Domain Name when you installed the Administration Server.
    • [policyowner] —The owner of the tables/schema in the policy database.

For more information on the database schema installation, examine the install_schema_oracle.log or install_schema_sybase.log in the log directory.

Installing the Policy Database Schema on Linux

To install the policy database schema in a Linux platform:

  1. Change to the active directory in which to install the database schema, for example:
    2. cd /bea/ales22-admin/bin
  2. Locate the script install_schema_dbtype.sh

    3. Important: Make sure all scripts in this directory have execute permission.

  3. To install the policy database schema, perform the following steps:

    4. For an Oracle database, type: 

    install_schema_oracle.sh server dblogin dbpassword enterprise_domain [policyowner]

    For a Sybase database, type: 

    install_schema_sybase.sh server database dblogin dbpassword enterprise_domain [policyowner]

    Where:

    • server—The name of the Oracle net service name or Sybase server name.
    • database—The name of the Sybase database.
    • dblogin —The username to use to access the database; the username for the database administrator. Owner of the policy database (optional, defaults to the user login, usually the same as the username). The policy owner is a database username or user ID that controls the set of database schema in the database instance.
    • dbpassword—The password to use to access the database; the password for the database administrator.
    • enterprise_domain —The name of the enterprise domain. The enterprise domain name is used to link all the components and is referred to as the Enterprise Domain Name when you installed the Administration Server.
    • [policyowner] —The owner of the tables/schema in the policy database.

For more information on the database schema installation, examine the install_schema_oracle.log or install_schema_sybase.log in the log directory.

 

Starting and Stopping Processes

After you have installed the Administration Server, you must start the necessary processes by running the appropriate batch or shell scripts. On UNIX, run WLESadmin.sh start or WLESadmin.sh console. On Windows, you can start the WLESadmin start or WLESadmin console processes as services from the Programs menu or as commands from a console window.

For more detailed instructions on how to start and stop the required processes, see Starting and Stopping Processes in the Administration and Deployment Guide.

 

Logging into the Administration Console

At this time, you can log into the Administration Console and check that all the components are working correctly. For descriptions of the processes that are running, see Starting and Stopping Processes in the Administration and Deployment Guide.

To log into the Administration Console:

  1. Open Internet Explorer.

    2. To ensure that your transactions are securely encrypted, the Administration Console uses two-way Secure Socket Layers (SSL) to communicate with your Administration Server.

  2. Enter the URL for the Administration Console: 
    3. https://hostname:port/asi

    Where:

    hostname is the Domain Name Server (DNS) name or IP address of the Administration Server.

    port is the port number through which the Administration Server is connected.

    asi is the name of the Enterprise Domain (that you assigned during the installation procedure).

  3. When the login page appears, enter the username and the password granted to one of the security roles that has a login privilege and click Sign In. If you are using the default username and password, enter system (username) and weblogic (password). This is the default administrator configured on install and should only be used for the initial login.
  4. Several security certificate verification dialog boxes appear. Check OK on each one. If you do not have the proper version of the JRE installed, then on the first attempt, the console prompts you to install it.
  5. Once you have started the console, you should set up additional administrative users or configure an Authentication provider to authenticate console users to an external authentication source such as LDAP or Microsoft Windows NT and update the administration policy accordingly, as described in What's Next?.
    6. Note: The Administration Console allows administrators to edit configurations or perform other operations based on security roles granted by the administration policy. If your security roles do not permit editing of configuration data, for example, the data is displayed in the Administration Console but is not editable. If you try to perform an operation that is not permitted, the Administration Console displays an Access Denied.

 

What's Next?

Now that you have successfully installed the Administration Server, you are ready to install your Security Service Modules and configure and deploy your security configurations and policies.

For instructions on installing Security Service Modules (SSMs), see Installing Security Service Modules.

Note: In a production environment, BEA recommends that you install your Security Service Modules on machines other than the machine on which the Administration Server is installed.

For instructions on how to write and deploy policies to SSMs to protect resources, see the Policy Managers Guide. This document describes how to define resources, identities, and roles, and how to writer authorization policies and role mapping policies. It also describes how to create policy data files that you can use to import policy data into the Administration Server and how import and export policy data.


  Back to Top       Previous  Next