|
|
The following sections provide information that you need to know before installing your BEA software:
The installation program provides a complete framework for the installation and uninstallation of your entire BEA software product, or individual components, as desired. You can install AquaLogic Enterprise Repository using one of the following options:
You can use the BEA Products installation program in one of the following modes.
Graphical-mode installation is an interactive, GUI-based method for installing your software. It can be run on both Windows and UNIX systems. For installation procedures, see Running the Installation Program in Graphical Mode
If you want to run graphical-mode installation, the console attached to the machine on which you are installing the software must support a Java-based GUI. All consoles for Windows systems support Java-based GUIs, but not all consoles for UNIX systems do.
| Note: | If you attempt to start the installation program in graphical mode on a system that cannot support a graphical display, the installation program automatically starts console-mode installation. |
Console-mode installation is an interactive, text-based method for installing your software from the command line, on either a UNIX system or a Windows system. For instructions for using this method, see Running the Installation in the Console Mode
Silent-mode installation is a noninteractive method of installing your software that requires the use of an XML properties file for selecting installation options. You can run silent-mode installation in either of two ways: as part of a script or from the command line. Silent-mode installation is a way of setting installation configurations only once and then using those configurations to duplicate the installation on many machines. For information on running the installation program in the silent mode, see Running the Installation in the Silent Mode
Using the BEA Products installation program, you can install the following components on your system.
For additional information about:
ALER manages the metadata for any type of software asset, from business processes and Web services to patterns, frameworks, applications, and components. It maps the relationships and interdependencies that connect those assets to improve impact analysis, promote and optimize their reuse, and measure their impact on the bottom line.
ALER consists of the following subcomponents that can be installed on your system:
| Note: | You can specify whether or not you want to install the new Eclipse plug-ins for ALER into a new WorkSpace Studio location or to use an existing Eclipse installation. For more information, see Using BEA WorkSpace Studio for Repository Access. |
The Advanced Edition of ALER 3.0 includes the ALBPM Process Engine to process the repository’s Advanced Registration Flows. This feature automates the manual asset registration process by providing a set of predefined flows designed to automate a set of common ALER asset registration tasks, such as asset submission, acceptance, registration, and other governance processes.
To accomplish this, ALER 3.0 includes an embedded, JMS-based event manager that manages the flow of ALER asset registration events, which are emitted in the form of Web Service events. ALER also includes the ALBPM Process Engine to process the Web Service events. When ALER is installed, it provides an option to install and configure the ALBPM Process Engine.
For more information on obtaining the Advanced Edition of ALER 3.0, contact your BEA sales representative.
Your BEA software is distributed on both the BEA Web site and DVD.
You can download your software from the BEA Web site at
http://commerce.bea.com.
In the left panel click on BEA AquaLogic to go to the download page of BEA AquaLogic Product Family. Click on BEA AquaLogic Enterprise Repository from the list of AquaLogic products. From the drop down list choose the appropriate operating system and click Select.
| Note: | You must register before you can download the installer. |
If you purchased your software from your local sales representative, you will find the following items in the product box:
The following sections specify the installation prerequisites:
The system requirements for your installation are given in the following table.
A supported configuration of hardware, operating system, application server, JDK, and database is required. See
BEA Products Supported Configurations.
|
|
The BEA Products installation program requires a Java run-time environment (JRE) to run. A Java Development Kit (JDK), which includes a JRE, is bundled in the Windows installation program and in some UNIX installation programs (those with filenames ending in
.bin). For other UNIX platforms, the installation program does not install a JDK. Filenames for these installation programs end in .jar.
To run the
.jar installation programs, you must have the appropriate version of the JDK installed on your system, and include the bin directory of the JDK at the beginning of the PATH variable definition. It is important that you use a JDK because the installation process assigns values to JAVA_HOME and related variables to point to the JDK directory.
|
The BEA installation program uses a temporary directory into which it extracts the files necessary to install the software on the target system. During the installation process, your temporary directory must contain sufficient space to accommodate the compressed Java run-time environment (JRE) bundled with the installation program and an uncompressed copy of the JRE that is expanded into the temporary directory. The extracted files are deleted from the temporary directory at the end of the installation process. As a general rule, installation programs require approximately 2.5 times the amount of temporary space that is ultimately required by the installed files.
By default, the installation program uses the following temporary directories:
| Note: | If you do not have enough temporary space to run the installation program, you are prompted to specify an alternate directory or exit the installation program. |
To make sure that you have adequate temporary space, you may want to allocate an alternate directory for this purpose. To do so, follow the instructions provided in the following table.
On Windows systems, Administrator privileges are required to create Start menu shortcuts in the All Users folder.
When you are installing the software as a user with Administrator privileges, you are presented with the option to create the Start menu shortcuts in the All Users folder, or in the Local user’s Start menu folder. The following table describes the options available.
If a user without Administrator privileges installs the software, the Start menu entries are created in the user’s local Start menu folder.
The database administrator must create an empty database for ALER to install its files into. A user for this database must also be created (e.g., ALER_USER) and that user must have database owner privileges on the ALER database.
If you are installing the Advanced Edition of ALER 3.0 with the Advanced Registration Flows feature, then during the installation process, additional database administrator credentials will need to be supplied during the ALBPM portion of the procedure so that the installer can create two new databases and two new users. These two databases are used by the ALBPM process engine for transaction tracking and management.
Appropriate administrative privileges are necessary to complete this process.
| Tip: | A known bug on Oracle XE may cause an ORA-12519 error after the database is running for some period of time. To permanently fix this problem, run the following statement:ALTER SYSTEM SET PROCESSES=150 SCOPE=SPFILE; COMMIT; |
You will need to verify the following database prerequisites before beginning the ALER installation process.
ojdbc14.jar (driver version 10.2.0.2)| Note: | Do not supply the BEA installer with the classes12.jar file used in previous releases of ALER. |
Follow these steps to create the necessary tablespaces before installing ALER 3.0:
The following example scripts show how to create the ALER_DATA and ALER_INDEX tablespaces.
| Note: | These scripts are for a Unix/Linux based DataFile. For Windows, a file path value of c:\oracle\...\file.dbf is appropriate syntax. |
CREATE TABLESPACE ALER_DATA
DATAFILE '/opt/oracle/oradata/aler/aler_data.dbf' SIZE 100M AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL AUTOALLOCATE
LOGGING
ONLINE
SEGMENT SPACE MANAGEMENT AUTO;
CREATE TABLESPACE ALER_INDEX
DATAFILE '/opt/oracle/oradata/aler/aler_index.dbf' SIZE 100M AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL AUTOALLOCATE
LOGGING
ONLINE
SEGMENT SPACE MANAGEMENT AUTO;
Follow these steps to create the necessary database user before installing ALER 3.0:
The following example script show how to create a user for newly created ALER Tablespaces.
CREATE USER ALER IDENTIFIED BY ALER_PWD
DEFAULT TABLESPACE ALER_DATA
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;
GRANT "CONNECT" TO ALER;
ALTER USER ALER DEFAULT ROLE "CONNECT";
GRANT CREATE MATERIALIZED VIEW TO ALER;
GRANT CREATE SEQUENCE TO ALER;
GRANT CREATE SESSION TO ALER;
GRANT CREATE SYNONYM TO ALER;
GRANT CREATE SNAPSHOT TO ALER;
GRANT CREATE TABLE TO ALER;
GRANT CREATE TRIGGER TO ALER;
GRANT CREATE VIEW TO ALER;
GRANT UNLIMITED TABLESPACE TO ALER;
Appropriate administrative privileges are necessary to complete this process. These instructions assume the use of Enterprise Manager.
You will need to verify the following database prerequisites before beginning the ALER installation process.
| Note: | Do not supply the BEA installer with the msbase.jar, msutil.jar, mssqlserver.jar files as was required previous releases of ALER. |
Follow these steps to create the necessary database before installing ALER 3.0:
ALER as the database name.ALER_DATA.ALER_USER as the database owner (or choose a Windows login account as appropriate for your security policy).Follow these steps to create the necessary user before installing ALER 3.0:
| Note: | This step is only necessary if you are using SQL Server Authentication for the ALER application installation. |
ALER_USER as the Login name (or choose a Windows login account as appropriate for your security policy).public and db_owner.These sections explain how to configure supported databases for UTF-8/Unicode character encoding.
SQL Server is automatically configured to support UTF-8/Unicode character encoding. No additional configuration is necessary.
--#SET TERMINATOR
-- UDB Client Invocation Command:
-- db2 -tv (allows semicolons as the command terminator)
--
-- Dependencies:
-- UDB Client
-- In DB2 ADDNODE of server - 8 character alias (@NODE-NAME)
-- Create the ALER database
DROP DATABASE ALER;
CREATE DATABASE ALER USING CODESET UTF-8 TERRITORY US;
-- Connect to the ALER database
CONNECT TO ALER USER ALER_USER USING ALER_USER_PWD;
-- Create the ALER 32K Buffer Pools
CREATE BUFFERPOOL ALER32KDATAbp SIZE 1000 PAGESIZE 32K;
CREATE BUFFERPOOL ALER32KINDXbp SIZE 1000 PAGESIZE 32K;
CREATE BUFFERPOOL ALER32KBLOBbp SIZE 1000 PAGESIZE 32K;
CREATE BUFFERPOOL ALER32KTEMPbp SIZE 1000 PAGESIZE 32K;
CONNECT RESET;
CONNECT TO ALER USER ALER_USER USING ALER_USER_PWD;
CREATE REGULAR TABLESPACE alerdatats PAGESIZE 32 K MANAGED BY DATABASE USING(file '/opt/IBM/DB2/data/alerdatats.dat' 300M) extentsize 512k BUFFERPOOL ALER32KDATAbp;
CREATE REGULAR TABLESPACE alerindxts PAGESIZE 32 K MANAGED BY DATABASE USING(file '/opt/IBM/DB2/data/alerindxts.dat' 300M) extentsize 512k BUFFERPOOL ALER32KINDXbp;
CREATE REGULAR TABLESPACE alerlobts PAGESIZE 32 K MANAGED BY DATABASE USING(file '/opt/IBM/DB2/data/alerlobts.dat' 300M) extentsize 512k BUFFERPOOL ALER32kBLOBbp;
-- Create the ALER Temp Tablespace
CREATE TEMPORARY TABLESPACE alertempts PAGESIZE 32 K MANAGED BY DATABASE USING(file '/opt/IBM/DB2/data/alertempts.dat' 128M) BUFFERPOOL ALER32KTEMPbp;
-- TUNING PARAMETERS
-- Default Values
-- UPDATE DATABASE CONFIGURATION FOR ALER USING APP_CCTL_HEAP_SZ 128;
-- UPDATE DATABASE CONFIGURATION FOR ALER USING CHNGPGS_THRESH 60;
-- UPDATE DATABASE CONFIGURATION FOR ALER USING DBHEAP 600;
-- UPDATE DATABASE CONFIGURATION FOR ALER USING LOCKLIST 50;
-- UPDATE DATABASE CONFIGURATION FOR ALER USING LOGPRIMARY 3;
-- UPDATE DATABASE CONFIGURATION FOR ALER USING MAXAPPLS 40;
-- UPDATE DATABASE CONFIGURATION FOR ALER USING MINCOMMIT 1;
-- UPDATE DATABASE CONFIGURATION FOR ALER USING NUM_IOCLEANERS 1;
-- UPDATE DATABASE CONFIGURATION FOR ALER USING STMHEAP 2048;
-- UPDATE DATABASE CONFIGURATION FOR ALER USING DFT_DEGREE 1;
-- New Values Growth
UPDATE DATABASE CONFIGURATION FOR ALER USING LOGBUFSZ 131;
UPDATE DATABASE CONFIGURATION FOR ALER USING MAXLOCKS 60;
UPDATE DATABASE CONFIGURATION FOR ALER USING DFT_PREFETCH_SZ 32;
UPDATE DATABASE CONFIGURATION FOR ALER USING LOGFILESIZ 1024;
UPDATE DATABASE CONFIGURATION FOR ALER USING SOFTMAX 120;
UPDATE DATABASE CONFIGURATION FOR ALER USING SORTHEAP 737;
UPDATE DATABASE CONFIGURATION FOR ALER USING CATALOGCACHE_SZ 526;
UPDATE DATABASE CONFIGURATION FOR ALER USING NUM_IOSERVERS 6;
UPDATE DATABASE CONFIGURATION FOR ALER USING PCKCACHESZ 859;
UPDATE DATABASE CONFIGURATION FOR ALER USING UTIL_HEAP_SZ 39963;
UPDATE DATABASE CONFIGURATION FOR ALER USING LOGSECOND 50;
CONNECT TO ALER USER ALER USING ALER_USER_PWD;
ALTER BUFFERPOOL ALER32KDATAbp SIZE 14532;
ALTER BUFFERPOOL IBMDEFAULTBP SIZE 3633;
COMMIT;
CONNECT RESET;
Before you begin this procedure, verify that UTF-8 compatibility was defined when the Oracle SID (System Identifier) was created. Otherwise, a new SID must be created that does support UTF-8.
Drop user ALER cascade;
CREATE USER ALER IDENTIFIED BY ALER_PWD
DEFAULT TABLESPACE USER_DATA
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;
GRANT "CONNECT" TO ALER;
ALTER USER ALER DEFAULT ROLE "CONNECT";
GRANT CREATE MATERIALIZED VIEW TO ALER;
GRANT CREATE SEQUENCE TO ALER;
GRANT CREATE SESSION TO ALER;
GRANT CREATE SYNONYM TO ALER;
GRANT CREATE SNAPSHOT TO ALER;
GRANT CREATE TABLE TO ALER;
GRANT CREATE TRIGGER TO ALER;
GRANT CREATE VIEW TO ALER;
GRANT UNLIMITED TABLESPACE TO ALER;
The following is an overview of the process required to migrate database character encoding from ISO-8859 to Unicode/UTF-8. The specific operations for your database server should be performed by a database administrator.
During the installation process, you need to specify locations for the following directories.
During the installation of the BEA software, you are prompted to specify a BEA Home directory. This directory serves as a repository for common files that are used by various BEA products installed on the same machine. For this reason, the BEA Home directory can be considered a central support directory for all the BEA products installed on your system.
The files in the BEA Home directory are essential to ensuring that BEA software operates correctly on your system. These files:
The following illustration shows the structure of a sample BEA Home directory, on a Windows platform, which includes both the Sun and BEA JRockit JDKs.
This illustration depicts only the files and directories required in the BEA Home directory. If you choose the default product installation directory, however, you will see additional directories in the BEA Home directory, such as repository30 and albpm57. Although the default location for the product installation directory is within the BEA Home, you can select a different location outside the BEA Home directory.
| Notes: |
CLASSPATH may not be resolved properly. You can install only one instance of each version of a BEA product in a single BEA Home directory. For example, you can install only one instance of ALER 3.0 in a BEA Home directory, but that BEA Home directory may also contain an instance of ALER 2.6. registry.xml, or if any of the other installation directories are not empty, the following messages will be displayed. You will then be prompted to continue installation, or return to the directory selection task with the one of the error message as shown in Listing 2-1:For BEA Home directory selection task: BEA_HOME directory is not empty. Proceed with installation?For product installation directories selection task:One or more installation directories are not empty. Proceed with installation?The files and directories in the BEA Home directory are described in the following table.
Although it is possible to create more than one BEA Home directory, BEA recommends that you avoid doing so. In almost all situations, a single BEA Home directory is sufficient. There may be circumstances, however, in which you prefer to maintain separate development and production environments, with a separate product stack for each. With two directories, you can update your development environment (in a BEA Home directory) without modifying the production environment until you are ready to do so.
The product installation directory contains all the software components that you choose to install on your system, including program files and examples. You are prompted during your initial installation to choose a product installation directory. If you accept the default on a Windows system, for example, your software is installed in the following directory:
where, C:\bea is the BEA Home directory and repository30 is the product installation directory for the ALER software. However, you can specify any name and location on your system for your product installation directory; you need not name the directory repository30 or create it under the BEA Home directory. You must also create a product installation directory for the Process Engine. The default location is C:\bea\albpm57.
If you launch the installation from the command line or from a script, you can specify the -log option to generate a verbose installation log. The installation log stores messages about events that occur during the installation process, including informational, warning, error, and fatal messages. This type of file can be especially useful for silent installations.
| Note: | You may see some warning messages in the installation log. However, unless a fatal error occurs, the installation program completes the installation successfully. The installation user interface indicates the success or failure of each installation attempt, and the installation log file includes an entry indicating that the installation was successful. |
To create a verbose log file during installation, include the -log=full_path_to_log_file option in the command line. For example:
aler30_win32.exe -log=C:\logs\ALER_install.log
The path must specify a file. You cannot create a folder simply by including a name for it in a pathname; your path should specify only existing folders. If your path includes a nonexistent folder when you execute the command, the installation program does not create the log file.
For information about upgrading your software in the Upgrade Guide.
|