| Oracle® Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1) for hp Tru64 UNIX Part Number B12232-02 |
|
|
View PDF |
| Oracle® Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1) for hp Tru64 UNIX Part Number B12232-02 |
|
|
View PDF |
This chapter guides you through silent and non-interactive installation of Oracle Collaboration Suite.
This chapter contains these topics:
Oracle Collaboration Suite features two non-interacting methods of installation:
Silent installation of Oracle Collaboration Suite is accomplished by supplying Oracle Universal Installer with a response file and specifying the -silent flag. Oracle Universal Installer uses variables and values contained in a text file, called a response file, to provide answers to all of its user prompts. You include responses for all of the prompts in the response file. Silent installation displays no graphical output.
If this is a first time installation of Oracle Collaboration Suite, you must manually create three files before starting installation. These files are used by Oracle Universal Installer during the installation.
oraInst.loc
emtab
oratab
Following 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.
Use silent installation of Oracle Collaboration Suite when you want similar installations on more than one computer. Additionally, use silent installation when performing the Oracle Collaboration Suite installation from a remote location using the command line. Silent installation eliminates the need to monitor the Oracle Collaboration Suite installation because there is no graphical output and no input by the user.
|
See Also:
|
Non-interactive installation of Oracle Collaboration Suite is accomplished by supplying Oracle Universal Installer with a response file, but without specifying the -silent flag. Oracle Universal Installer uses variables and values contained in a text file, called a response file, to provide answers to some or all of its user prompts. Oracle Universal Installer provides graphical output. If you have not provided responses to all of its prompts, then you may need to enter information during the installation.
You must run the root.sh script during the installation process. The root.sh script detects settings of environmental variables and enables you to enter the full path of the local bin directory.
For a complete list of installation requirements, refer to Chapter 2, "Preparing for Installation".
If the oraInst.loc, emtab, 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. The following directories are the appropriate locations for the files:
oratab and emtab files
oraInst.loc file
/var/opt/oracle
As the root user, create the oraInst.loc file in the /var/opt/oracle directory. Ensure the file has read and write permissions set for the oracle user group. 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_HOME
where inventory_loc is the location for inventory files and $ORACLE_HOME is the absolute directory path. For example, if your $ORACLE_HOME is /private2/oracle/ocs, then the content of the file is:
inst_group=oracle_user_group inventory_loc=/private2/oracle/ocs
|
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. |
Create the emtab file in the /etc directory. Ensure that the file has read and write permissions set for the oracle user group. The emtab file should have the following text input:
DEFAULT=$ORACLE_HOME
where $ORACLE_HOME is the absolute directory path. For example, if your $ORACLE_HOME is /private2/oracle/ocs, then the content of the file is:
DEFAULT=/private2/oracle/ocs
The Oracle Collaboration Suite CD Pack provides the Oracle Universal Installer response files for the three installations shown in Table 8-1.
Table 8-1 Response Files
| For This Installation... | The Filename Is... |
|---|---|
| Oracle9iAS Infrastructure |
infrastructure.rsp |
| Oracle Collaboration Suite information storage
This installation also includes response files for Oracle Network Configuration Assistant ( |
storage.rsp |
| Oracle Collaboration Suite
This installation also includes a response file for Oracle Files configuration assistant ( |
midtier.rsp |
Response files are located in the /response directory located at the root of the first CD-ROM in the CD-ROM set of each of the three installations. You must edit the response file to satisfy your silent or non-interactive installation requirements. To use a response file, first copy it from the CD-ROM to your system.
For example:
Go to the /response directory (for example, on the first CD-ROM of the Oracle9iAS Infrastructure installation CD-ROM set).
Copy the infrastructure.rsp file to your system hard drive:
prompt> cp infrastructure.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. The comment 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.
Before you specify a response file, ensure that you have properly configured the file. Refer to the previous section 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:
prompt> ./runInstaller -responseFile absolute_path_and_filename
In non-interactive mode, the DISPLAY environment variable must be set as described in "DISPLAY". To perform a completely silent installation session, use the -silent parameter:
prompt> ./runInstaller -silent -responseFile absolute_path_and_filename
The success or failure of the non-interactive 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.
|
Important: During installation, these 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, it is recommended that you delete any copies of the response files that remain in your file system. |
When performing a silent or non-interactive installation, you must run the root.sh script after any silent installation of Oracle Collaboration Suite.
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 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.
prompt> $ORACLE_HOME/root.sh
where $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 due to the inability to start Oracle HTTP Server.
After running the root.sh script, restart Oracle HTTP Server as follows:
$ORACLE_HOME/opmn/bin opmnctl stopall $ORACLE_HOME/opmn/bin opmnctl startall
If you want 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
where $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 non-interactive 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.
prompt> $ORACLE_HOME/root.sh
where $ORACLE_HOME is the absolute directory path.
Exit root user.
For non-interactive installation, after you see ÒFinished running generic part of the root.sh scriptÓ and ÒNow product-specific root actions will be performed,Ó exit root user and return to the Install 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 a silent or non-interactive installation is logged in the silentInstall.log file. This file is created in the oraInventory 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 non-interactive 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 non-interactive installation without specifying a response file, the installation fails.
If your silent or non-interactive installation fails, you must completely deinstall any files remaining from your Oracle Collaboration Suite installation attempt.
To use a configuration assistant in non-interactive mode, do one of the following:
Configure an Oracle Universal Installer response file to start the non-interactive configuration assistant.
Run the configuration assistant in standalone mode using the following command format:
prompt> assistant_name [-silent] -responseFile filename
where assistant_name is the configuration assistant that you want to run and filename is the response file for that assistant.
If you perform an Oracle Collaboration Suite information storage installation in non-interactive 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 non-interactive session without configuring a response file. See "Response File Error Handling" for more information about troubleshooting a failed non-interactive installation. |
|
See Also:
|
Oracle Universal Installer or the configuration assistant validates the response file at runtime. If the validation fails, the non-interactive 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 installation session's log file.
|
See Also: "oraInventory Directory and Installation Session Log Files" for more information about theoraInventory directory and installation log files |
