| Oracle® Collaboration Suite Installation Guide 10g Release 1 (10.1.2) for AIX 5L Based Systems (64-Bit) Part Number B25471-10 |
|
|
View PDF |
| Oracle® Collaboration Suite Installation Guide 10g Release 1 (10.1.2) for AIX 5L Based Systems (64-Bit) Part Number B25471-10 |
|
|
View PDF |
This chapter guides you through silent and noninteractive installation of Oracle Collaboration Suite.
This chapter contains the following sections:
Section 10.1, "Introduction to Noninteractive Installations"
Section 10.3, "Installing Oracle Application Server Certificate Authority"
Section 10.4, "Creating Files for Silent and Noninteractive Installation"
Section 10.7, "Creating a Response File Using the Record Mode in the Installer"
Section 10.8, "Specifying a Response File and Starting the Installation"
Section 10.11, "Security Tips for Silent and Noninteractive Installations"
Section 10.14, "Using Configuration Assistants in Noninteractive Mode"
Oracle Collaboration Suite features the following two noninteractive methods of installation:
Silent installation eliminates the need to monitor the Oracle Collaboration Suite installation because there is no graphical output and no input by the user. It is accomplished by supplying Oracle Universal Installer with a response file and specifying the -silent flag on the command line.
You should use silent installation of Oracle Collaboration Suite when you want similar installations on more than one computer. Additionally, you can use silent installation when performing the Oracle Collaboration Suite installation from a remote location using the command line.
The response file used in a silent installation is a text file. Oracle Universal Installer uses variables and values specified in the response file to provide answers to all of its user prompts. Therefore, you must include responses for all of the prompts in the response file.
If this is a first-time installation of Oracle Collaboration Suite, you must manually create the following two files before starting installation:
oraInst.loc
oratab
These files are used by Oracle Universal Installer during the installation.
After any silent Oracle Collaboration Suite installation, run the root.sh script. The root.sh script detects settings of environmental variables and enables you to enter the full path of the local bin directory.
Noninteractive installations of Oracle Collaboration Suite display a graphical output. If you have not provided responses to all of the user prompts, then you may need to enter information during the installation.
Noninteractive installation of Oracle Collaboration Suite is also accomplished by supplying the Oracle Universal Installer with a response file, but without specifying the -silent flag on the command line. Oracle Universal Installer uses the variables and values contained in the response file to provide answers to some or all of its user prompts.
If this is a first-time installation of Oracle Collaboration Suite, then you must manually create oraInst.loc and oratab files before starting the installation. These files are used by Oracle Universal Installer during the installation.
After any noninteractive Oracle Collaboration Suite installation, run the root.sh script. The root.sh script detects settings of environmental variables and enables you to enter the full path of the local bin directory.
Use noninteractive installation of Oracle Collaboration Suite when there are specific screens you want to observe during installation.
For a complete list of installation requirements, refer to Chapter 2.
SKIP_ROOTPRE Environment Variable on AIX
In addition to setting the environment variables as described in Section 4.7, "Environment Variables", set the SKIP_ROOTPRE environment variable to TRUE to ensure that the installer does not prompt you while performing checks.
Example (C shell):
% setenv SKIP_ROOTPRE TRUE
Example (Bourne or Korn shell):
$ SKIP_ROOTPRE=TRUE; export SKIP_ROOTPRE
If you are installing OracleAS Certificate Authority, check the following:
If you are installing OracleAS Certificate Authority against an existing Oracle Internet Directory, then ensure that the Oracle Internet Directory has Oracle Application Server Single Sign-On configured. If not, the OracleAS Certificate Authority Configuration Assistant will fail.
If you are installing OracleAS Certificate Authority with a new Oracle Internet Directory, then ensure that you are also configuring OracleAS Single Sign-On. If not, the OracleAS Certificate Authority Configuration Assistant will fail.
In interactive mode, the installer performs the checks for you and displays a warning if the requirements are not met. However, in silent or noninteractive mode, the installer is not able to display a warning.
If the oraInst.loc and oratab files do not exist on your computer, you must create them before starting silent installation of Oracle Collaboration Suite. They are used by the Oracle Universal Installer during silent installation.
Table 10-1 lists the appropriate directory location for this platform.
As the root user, create the oraInst.loc file in the appropriate directory. Ensure that the file has read and write permissions set for the oracle user group because the oracle user group is the group performing the installation. The oraInst.loc file should have the following text input:
inst_group=oracle_user_group
inventory_loc=ORACLE_BASE/oraInventory
In this text input, inventory_loc is the location for inventory files and $ORACLE_HOME is the absolute directory path. For example, if your $ORACLE_BASE is /private2/oracle/ocs, then the content of the file is:
inst_group=oracle_user_group
inventory_loc=/private2/oracle/ocs/oraInventory
|
Note: Ifinventory_loc is not located in your Oracle home, then ensure that the directory where it is located has read and write permissions set for oracle_user_group. |
Before performing a silent or noninteractive installation, you must provide information specific to your installation in a response file. The installer will fail if you attempt an installation using a response file that is not configured correctly. Response files are text files that you can create or edit in a text editor.
The Oracle Collaboration Suite DVD Pack provides templates for the Oracle Universal Installer response files for the installations shown in Table 10-2.
Table 10-2 Response Files
| For This Installation... | The File Name Is... |
|---|---|
|
Oracle Collaboration Suite 10g Infrastructure |
|
|
Oracle Collaboration Suite 10g Infrastructure: Oracle Collaboration Suite 10g Database only |
|
|
Oracle Collaboration Suite 10g Infrastructure: Identity Management only |
|
|
Oracle Collaboration Suite 10g Infrastructure: Enabling customer Database as Oracle Collaboration Suite Database |
|
|
Oracle Collaboration Suite 10g Infrastructure and Oracle Collaboration Suite 10g Infrastructure (Single-computer installation) |
|
|
Oracle Collaboration Suite Applications |
|
Response files are located in the /response directory on Disk 1 of the Oracle Collaboration Suite DVD pack. You must edit the response file according to your requirements for silent or noninteractive installation.
To use a response file, first copy it from the DVD to your system.
For example:
Go to the /response directory (on the first DVD of the Oracle Collaboration Suite installation DVD set).
Copy the infra_complete.rsp file to your system hard drive:
# cp infra_complete.rsp /private/ocs_infr_cd1/response/infrastructure.rsp
Use any text editor to edit the response file to include information specific for your system. The response file text identifies information that you must provide.
You must specify values for variables in your response file. Each variable listed in the response file is associated with a comment, which identifies the variable type. For example:
string = "Sample Value"
Boolean = True or False
Number = 1000
StringList = {"StringValue 1", "String Value 2"}
The values that are given as <Value Required> must be specified for silent installation.
Remove the comment from the variable values in the response file before starting the Oracle Collaboration Suite installation.
You can run the installer in record mode to save your inputs to a file that you can use later as a response file. This feature is useful if you need to perform the same installation on different computers.To run the installer in record mode:
Start the installer with the -record and -destinationFile parameters.
# /path/to/runInstaller -record -destinationFile newResponseFile
Replace newResponseFile with the full path to the response file that you want the installer to create.
Example: /response/infrastructure.rsp.
Enter your values in the installer screens. The installer will write these values to the file specified in the -destinationFile parameter.
When you get to the Summary screen, the installer automatically writes all the values that you supplied to the specified file. At this point, you can complete the installation on this computer, or you can exit without performing the installation.
Before you specify a response file, ensure that all the values in the response file are correct. Refer to Section 10.6 for more information.
To make Oracle Universal Installer use the response file at installation time, specify the location of the response file as a parameter when starting Oracle Universal Installer:
# ./runInstaller -responseFile absolute_path_and_filename
In noninteractive mode, the DISPLAY environment variable must be set as described in Section 2.7.4. To make the installer use the response file, specify the location of the response file that you want to use as a parameter when starting the installer.
To perform a noninteractive installation:
# setenv DISPLAY hostname:0.0
# ./runInstaller -responseFile absolute_path_and_filename
To perform a silent installation, use the -silent parameter:
# ./runInstaller -silent -responseFile absolute_path_and_filename
The success or failure of the noninteractive installation is logged in installActions.log. The success or failure of the silent installation is logged in silentInstall.log. The log files are created in the oraInventory directory during installation.
|
Warning: During installation, response files may be copied to subdirectories under $ORACLE_HOME in order to install some Collaboration Suite components. When the installation completes successfully, these copies are removed. If the installation fails, however, these copies may not be removed. If you have provided passwords or other sensitive information in your response files, Oracle recommends that you delete any copies of the response files that remain in your file system. |
When performing a silent or noninteractive installation, you must run the root.sh script after any silent installation of Oracle Collaboration Suite.
For a silent Oracle Collaboration Suite Infrastructure and Applications installation on a single computer, you must run the root.sh script in each Oracle home for Infrastructure as well as the Applications tier.
Similarly, for a noninteractive Oracle Collaboration Suite Infrastructure and Applications installation on a single computer that is response file driven but not run with the -silent parameter, if you have not set the SHOW_ROOTSH_CONFIRMATION parameter in the response file to FALSE, then you will be prompted to run the root.sh script. In this case, you must run the root.sh script in each Oracle home for Infrastructure as well as the Applications tier.
|
Note: After the silent or noninteractive installation is complete, you must verify the log files (in the$ORACLE_BASE/oraInventory/logs directory) to see if any errors occurred during the installation. |
During any silent Oracle Collaboration Suite installation, you are not prompted to run the root.sh script. You must run the root.sh script after the silent installation.
Use the following steps to run the root.sh script.
Log in as the root user.
Run the root.sh script in the Oracle home directory.
# $ORACLE_HOME/root.sh
In this command, $ORACLE_HOME is the absolute directory path.
Exit the root user.
During silent installation, Oracle Universal Installer attempts to start Oracle HTTP Server. However, Oracle HTTP Server does not start until the root.sh script is run. Ignore any error messages generated because of the inability to start Oracle HTTP Server.
After running the root.sh script, restart Oracle HTTP Server as follows:
$ORACLE_HOME/opmn/bin opmnctl stopproc ias-component=HTTP_Server $ORACLE_HOME/opmn/bin opmnctl startproc ias-component=HTTP_Server
To use Oracle HTTP Server on a port number that is less than 1024, do not run the root.sh script. Instead, run the following script as the root user:
$ORACLE_HOME/Apache/Apache/bin/root_sh_append.sh
In the preceding command, $ORACLE_HOME is the absolute directory path.
The root_sh_append.sh script sets the necessary permissions for the Oracle HTTP Server to be run on a port less than 1024.
During noninteractive installation of Oracle Collaboration Suite, Oracle Universal Installer prompts you to run the root.sh script.
Perform the following steps to run the root.sh script:
Log on as the root user.
Run the root.sh script in the Oracle home directory.
# $ORACLE_HOME/root.sh
In the preceding command, $ORACLE_HOME is the absolute directory path.
Exit the root user.
For noninteractive installation, after you see the "Finished running generic part of the root.sh script" and "Now product-specific root actions will be performed" messages, exit the root user and return to the current installation screen.
The root.sh script detects:
Settings of the ORACLE_OWNER, ORACLE_HOME, and ORACLE_SID environment variables
Full path of the local bin directory. You can accept the default or change to a different local bin directory.
The success or failure of the noninteractive and silent installations is logged in the installActions.log file. Additionally, the silent installation creates the silentInstall.log file. The log files are created in the $ORACLE_HOME/oracle/oraInventory/oui_inventory/logs directory.
The silentInstall.log file contains the following line if the installation was successful:
The installation of OracleAS <Installation Type> was successful.
The installActions.log file contains specific information for each Oracle Collaboration Suite installation type.
One of the pieces of information in the response file is the installation password. The password information is in clear text.
To minimize security issues regarding the password in the response file, follow these guidelines:
Set the permissions on the response files so that they are readable only by the operating system user who will be performing the silent or noninteractive installation.
If possible, remove the response files from the system after the silent or noninteractive installation is completed.
If you are installing the OracleAS Metadata Repository in silent or noninteractive mode, the installer creates these log files:
ORACLE_HOME/admin/<ORACLE_SID>/create/<ORACLE_SID>.log
ORACLE_HOME/cfgtoollogs/<ORACLE_SID>.log
In the above syntax, <ORACLE_SID> is the value of your database SID.
These log files contain database password information. If possible, you should remove these files from the system after reviewing their contents.
The success or failure of a silent or noninteractive installation is logged in the silentInstall.log file. This file is created in the oraInventory/log directory.
Values for variables that are of the wrong context, format, or type are treated as if no value were specified. Variables that are outside any section are ignored.
If you attempt a silent or noninteractive installation with an incorrect or incomplete response file, or Oracle Universal Installer encounters an error, such as insufficient disk space, the installation fails.
If you attempt a noninteractive installation without specifying a response file, the installation fails.
If you perform a silent installation with the staticports.ini file for ports less than 1024, the OPMN Configuration Assistant fails, and all the remaining configuration assistants do not run.
Before you run the configuration assistants from the command line, perform the following steps:
If your silent or noninteractive installation fails, you must completely deinstall any files remaining from your Oracle Collaboration Suite installation attempt.
|
See Also: Appendix J for detailed information on deinstallation of Oracle Collaboration Suite and its components |
You can perform a silent deinstallation of Oracle Collaboration Suite by supplying a silent deinstallation parameter to the response file you used for installation. Add the following parameter to your installation response file:
REMOVE_HOMES={"<ORACLE_HOME to be removed>"}
To perform a silent deinstallation, use the -silent parameter when you enter the following command:
# ./runInstaller -silent -responseFile absolute_path_and_filename
All the Oracle Collaboration Suite configuration assistants, except for the configuration assistant for Oracle Content Services can be run in the noninteractive mode.
To use a configuration assistant in noninteractive mode, do one of the following:
Run the configuration assistant in standalone mode using the following command format:
# assistant_name [-silent] -responseFile filename
In the preceding command, assistant_name is the configuration assistant that you want to run and filename is the response file for that assistant.
Configure an Oracle Universal Installer response file to start the noninteractive configuration assistant.
If you perform an Oracle Collaboration Suite Database installation in noninteractive mode, then Oracle Net Configuration Assistant does not configure your system at the end of the installation. After the installation, run the Oracle Net configuration with the Oracle Net Configuration Assistant by executing the netca command from the Oracle home directory or use the netca.rsp response file.
|
Note: Oracle Universal Installer or a configuration assistant fails if you attempt a noninteractive session without configuring a response file. Refer to Appendix K for more information about troubleshooting a failed noninteractive installation. |
|
See Also:
|
Oracle Universal Installer or most of the configuration assistants validate the response file at run time. If the validation fails, the noninteractive installation or configuration process ends. Oracle Universal Installer treats values for parameters that are of the wrong context, format, or type as if no value was specified in the file. Variables that are outside any section are also ignored.
Information about a failure is recorded in the log file of the installation session.
|
See Also: Section 3.3.1 for more information about theoraInventory directory and installation log files |
