Chat now with support
Chat mit Support

Foglight Evolve 6.1.0 - Installing Foglight on a UNIX System with an External Oracle Database

Before Installing Foglight Installing Foglight
Preparing to install Installing a new version of the Management Server Installed directories Foglight settings HP patch checking tool Uninstalling Foglight Upgrading the Management Server Installing Foglight FAQ
Running the Management Server Installing and Upgrading Cartridges Installing Agents

Option 2 - Run SQL scripts to configure the database

If you clicked Create during the database installation step, the SQL scripts in the<foglight_home>/scripts/sql directory are prepared with the provided configuration options. There are four SQL files for each database type ([dbtype]):

•
[dbtype]_drop_db.sql
•
[dbtype]_create_db.sql
•
[dbtype]_create_schema.sql
•
[dbtype]_populate_db.sql

You can review these scripts before running them.

 
* 
NOTE: Unless you are creating custom Oracle® tablespaces, you should not need to edit these scripts. If you are creating Oracle tablespaces, check with your database administrator to correctly assign tablespace names.
It is recommended that you create a Foglight label for Data, Index, and Objects.

If custom tablespaces are configured in the storage-config.xml, as described in the Performance Tuning Field Guide, the database administrator must edit the oracle_create_db.sql script and add grants for the custom tablespaces. These grants are similar to the ones that grant a quota on the USERS tablespace. For example:

ALTER USER @db.schema.username@ QUOTA UNLIMITED ON SOME_CUSTOM_DATA_TABLESPACENAME_HERE;
ALTER USER @db.schema.username@ QUOTA UNLIMITED ON SOME_CUSTOM_INDEX_TABLESPACENAME_HERE;
ALTER USER @db.schema.username@ QUOTA UNLIMITED ON SOME_CUSTOM_LOB_TABLESPACENAME_HERE;
 
* 
NOTE: In the example above, replace the italicized text (for example, SOME_CUSTOM_DATA_TABLESPACENAME_HERE) with the actual custom tablespace names defined in the storage-config.xml file.

You must run the configured scripts against the database using a third-party tool.

To perform manual database configuration:
•
Run the .sql scripts by issuing the following commands in the order shown:
a
sqlplus <DBA_username>/<DBA_password>@SID @<foglight_home>/scripts/sql/oracle_drop_db.sql
This script must be run under an account with administrator privileges (for example, sys), because you require system access to execute it. Replace <DBA_username> and <DBA_password> with the user name and password for the database administrator account.
b
sqlplus <DBA_username>/<DBA_password>@SID @<foglight_home>/scripts/sql/oracle_create_db.sql
This script must be run under an account with administrator privileges (for example, sys), because you require system access to execute it. Replace <DBA_username> and <DBA_password> with the user name and password for the database administrator account.
c
sqlplus <foglight_username>/<foglight_password>@tnsname @<foglight_home>/scripts/sql/oracle_create_schema.sql
This script must be run using the Foglight Database Account User ID that you set in Step 11: Foglight repository database type. The default Foglight Database Account User ID is foglight.
d
sqlplus <foglight_username>/<foglight_password>@tnsname @<foglight_home>/scripts/sql/oracle_populate_db.sql
This script must be run using the Foglight Database Account User ID that you set in Step 11: Foglight repository database type. The default Foglight Database Account User ID is foglight.

After you have run all four scripts, you can start the Management Server. Proceed to Starting and stopping the Management Server.

Initializing the database

Initializing the database

For external databases, once the database has been successfully initialized, you can run Foglight.

Starting and stopping the Management Server

The following sections describe how to start and stop the Management Server:

•
Starting the Management Server
•
Stopping the Management Server

Starting the Management Server

The following sections describe how to start the Management Server from the command line and lists additional commands for use when starting or running the Management Server.

To start the Management Server from the command line:
•
Navigate to the directory <foglight_home>/bin and run the following command:
fms

When the Management Server starts successfully, the following message appears in the command window:

Forge Server startup completed.
Additional commands
 
Table 1. Starting the Management Server - additional commands
Commands
Represents
Description

-s

start

Starts the Management Server (this option is assumed if no command is specified).

-d

start the process as a daemon

Starts the Management Server as a daemon (if the process is not started as a daemon, the command prompt is held captive by the running Management Server, and remains in the foreground).

NOTE: The following scripts in $FGLHOME/bin directory can start the Management Server as a daemon and shut it down, respectively:
fmsStartup.sh
fmsShutdown.sh

-n

name

Provides a unique name for this instance of the Management Server.

-j

jvm-argument

Sets an option to be passed directly to the Java® VM.

Can be used to set more than one VM option.

-v

version

Displays the version number for this program and exits.

-h

help

Shows this information, and additional options, then exits.

Initialization scripts

Another option is to start the Management Server using initialization scripts. This option is particularly useful when you want to automatically start the Management Server after it has been rebooted.

The initialization scripts can be found in the directory <foglight_home>/scripts/init.d. A readme.txt file is available in the same location. Review this file before running the script as it contains valuable information on how to use the script for your specific platform.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen