Before You Install

Installation and Upgrade Guides › Policy Server Installation Guide › Installing the Administrative UI to an Existing Application Server › Delete a Report Server Connection to the Administrative UI › Test SNMP Gets for Red Hat Enterprise Linux Advanced Server › Before You Install

Before You Install

Consider the following before you install the Administrative UI:

You install the Administrative UI using the installation media on the Technical Support site.
Note: For a list of installation media names, see the Policy Server Release Notes.
If you are installing to an existing application server infrastructure, the following procedures apply. If you are using the stand-alone option to install, see Installing the Administrative UI.
(Windows) Run the installer from the Administrative UI host system. Do not run the installer from a mapped network share or UNC path.
The installation zip contains a layout.properties file and a Framework folder at the same level as the installation media. If you moved the installation media after extracting the installation zip, move the following to the same location or the installation fails:
- layout.properties file
- Framework folder
(UNIX) Depending on your permissions, run the following to add executable permissions to the directory that contains the installation media:
```
chmod -R+x directory
```
directory

Specifies the directory that contains the installation media.
(UNIX) The user installing the Administrative UI must have read/write permissions for the directory to which the application server is installed.
(UNIX) If you execute the Administrative UI installer across different subnets, it can crash. Install the Administrative UI directly on the host system.

More information:

Installing the Administrative UI

How to Install the Administrative UI

Locate the Installation Media

Installation Media Names

Install the Administrative UI

Install the Administrative UI to your existing application server to provide a management console for all tasks that are related to access control, reporting, and policy analysis.

Follow these steps:

Exit all applications that are running.
Navigate to the installation media.
Double-click installation_media.

installation_media

Specifies the Administrative UI installation executable.

The installer starts.

Note: For a list of installation media names, see the Policy Server Release Notes.
Use your completed installation worksheet to enter the required values.
Review the installation settings and click Install.
The Administrative UI is installed.

Note: You cannot use the Administrative UI to manage your environment until you have registered it with a Policy Server.

More information:

Installation Media Names

How to Register the Administrative UI

Install the Administrative UI Using a GUI

Install the Administrative UI to your existing application server to provide a management console for all tasks that are related to access control, reporting, and policy analysis.

Follow these steps:

Exit all applications that are running in the foreground.
Open a shell and navigate to the installation media.
Enter the following command:
```
./installation_media gui
```
installation_media

Specifies the Administrative UI installation executable.

The installer starts.

Note: For a list of installation media names, see the Policy Server Release Notes.
Use your completed installation worksheet to enter the required values.
Review the installation settings and click Install.
The Administrative UI is installed.
Click Done and reboot the system.
The Administrative UI is installed.

Note: You cannot use the Administrative UI to manage your environment until you have registered it with a Policy Server.

More information:

How to Register the Administrative UI

Installation Media Names

Install the Administrative UI Using a UNIX Console

Install the Administrative UI to your existing application server to provide a management console for all tasks that are related to access control, reporting, and policy analysis.

Follow these steps:

Exit all applications that are running in the foreground.
Open a shell and navigate to the installation media.
Enter the following command:
```
./installation_media -i console
```
installation_media

Specifies the Administrative UI installation executable.

The installer starts.

Note: For a list of installation media names, see the Policy Server Release Notes.
Use your completed installation worksheet to enter the required values.
Review the installation settings and press Enter.
The Administrative UI is installed.
Press Enter.
The installer closes.
Reboot the system.
The Administrative UI is installed.

Note: You cannot use the Administrative UI to manage your environment until you have registered it with a Policy Server.

More information:

How to Register the Administrative UI

Installation Media Names

How to Register the Administrative UI

Register the Administrative UI before you use it to manage your environment. Registering the Administrative UI creates a trusted connection between the Administrative UI and a Policy Server.

This process explains how to register an Administrative UI that you installed to an existing application server infrastructure. To register an Administrative UI you installed using the stand-alone option, see Installing the Administrative UI.

To register the Administrative UI, complete the following procedures:

Reset the registration window.
If necessary, create the FIPs environment variable.
Start the application server.
Register the Administrative UI.

More information:

Installing the Administrative UI

How to Register the Administrative UI

Reset the Administrative UI Registration Window

If either of the following actions occurred more than 24 hours ago, this step is required:

You used the Policy Server installation wizard to configure a policy store automatically.
You used the XPSRegClient utility to submit the SiteMinder super user credentials to the Policy Server.

Note: (UNIX) Be sure that the SiteMinder environment variables are set before you use XPSRegClient. If the environment variables are not set, set them manually.

Follow these steps:

Log in to the Policy Server host system.
Run the following command:
```
XPSRegClient siteminder_administrator[:passphrase] -adminui-setup -t timeout -r retries -c comment -cp -l log_path -e error_path -vT -vI -vW -vE -vF
```
siteminder_administrator
Specifies a SiteMinder administrator. If you are installing the Administrative UI as part of:
- A new r12.0 SP3 environment, specify the following default account:
```
siteminder
```
- An upgrade, specify any SiteMinder administrator account with super user permissions in the policy store. If you do not have a super user account in the policy store, use the smreg utility to create the default account.
passphrase

Specifies the password for the SiteMinder administrator account.

-adminui-setup

Specifies that the Administrative UI is being registered with a Policy Server for the first–time.

-t timeout

(Optional) Specifies how long you have after you install the Administrative UI to log in for the time to complete the registration. The Policy Server denies the registration request when the timeout value is exceeded.

Unit of measurement: minutes

Default: 1440 (24 hours)

Minimum limit: 1

Maximum limit: 1440 (24 hours)

-r retries

(Optional) Specifies how many failed attempts are allowed when you are registering the Administrative UI. A failed attempt can result from submitting incorrect SiteMinder administrator credentials when logging in to the Administrative UI for the first–time.

Default: 1

Maximum limit: 5

-c comment

(Optional) Inserts the specified comments into the registration log file for informational purposes.

Note: Surround comments with quotes.

-cp

(Optional) Specifies that registration log file can contain multiple lines of comments. The utility prompts for multiple lines of comments and inserts the specified comments into the registration log file for informational purposes.

Note: Surround comments with quotes.

-l log path

(Optional) Specifies where the registration log file must be exported.

Default: siteminder_home\log

siteminder_home

Specifies the Policy Server installation path.

-e error path

(Optional) Sends exceptions to the specified path.

Default: stderr

-vT

(Optional) Sets the verbosity level to TRACE.

-vI

(Optional) Sets the verbosity level to INFO.

-vW

(Optional) Sets the verbosity level to WARNING.

-vE

(Optional) Sets the verbosity level to ERROR.

-vF

(Optional) Sets the verbosity level to FATAL.
Press Enter.
The utility supplies the Policy Server with the administrator credentials. The Policy Server uses these credentials to verify the registration request when you log in to the Administrative UI for the first–time.

Create the FIPS Environment Variable

If your environment meets both of the following criteria, creating the FIPs environment variable is required to register the Administrative UI for the first–time:

The Policy Server to which you are registering is operating in FIPs–only mode.
The Administrative UI is not installed on the Policy Server host system.

Follow these steps:

Complete one of the following steps:
- (Windows) Log into the Administrative UI host system as an administrative user.
- (UNIX) Log into the Administrative UI host system as the user that installed the Administrative UI.
Set the following environment variable:
CA_SM_PS_FIPS140=ONLY

Note: For more information about setting environment variables, see your OS–specific documentation.
Verify that Windows or the UNIX shells that runs the Administrative UI correctly recognizes the CA_SM_PS_FIPS140 variable.

Start the Application Server

If you installed the Administrative UI to an existing application server infrastructure, the following procedure applies. If you installed the Administrative UI using the stand-alone option, see Installing the Administrative UI.

Follow these steps:

Complete one of the following steps:
- JBoss—From a command prompt, navigate to jboss_home\bin.
  jboss_home
  
  Specifies the JBoss installation path.
- WebLogic—From a command prompt, navigate to domains\bin.
  domains
  
  Specifies the path of the WebLogic domain you created for the Administrative UI.
  
  Example: C:\bea\user_projects\domains\mydomain
- WebSphere—From a command prompt, navigate to profile\bin.
  profile
  
  Specifies the path of the WebSphere profile name you created for the Administrative UI.
  
  Example: C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSvr01\bin
Complete one of the following steps:
Important! Before running a SiteMinder utility or executable on Windows Server 2008, open the command line window with administrator permissions. Open the command line window this way, even if your account has administrator privileges.
- JBoss
  - Windows: Type the following command and press Enter:
    run.bat
  - UNIX: Type the following command and press Enter:
    run.sh
- WebLogic
  - Windows: Type the following command and press Enter:
    startWebLogic.cmd
  - UNIX: Type the following command and press Enter:
    startWebLogic.sh
- WebSphere
  - Windows: Type the following command and press Enter:
    startServer.bat identifier
  - UNIX: Type the following command and press Enter:
    startServer.sh identifier
  identifier
  
  Specifies the identifier for the WebSphere installation.
  
  Example: startServer.bat Server1
The application server is started.

More information:

Installing the Administrative UI

Start the Application Server