| Oracle® Application Server Release Notes 10g Release 2 (10.1.2) for Solaris Operating System (x86) and Solaris Operating System (x86-64) B25853-05 |
|
 Previous |
 Next |
| Oracle® Application Server Release Notes 10g Release 2 (10.1.2) for Solaris Operating System (x86) and Solaris Operating System (x86-64) B25853-05 |
|
Previous |
Next |
This chapter describes management and security issues associated with Oracle Application Server. It includes the following topics:
This section describes general management and security issues. It includes the following topic:
Section 3.1.1, "Restoring OracleAS Portal Configuration Files"
Section 3.1.3, "Flash Recovery Area Outside of the Oracle Home will not be Recreated during LOHA"
Section 3.1.5, "Error Message When Executing opmnctl Commands"
In order to restore OracleAS Portal configuration files, do the following:
Use the following commands to restore the instance:
bkp_restore.sh -m backup_instance_online
bkp_restore.sh -m restore_instance -t time_stamp
In the preceding command, time_stamp is the time stamp on the backup that you are using for the restore procedure.
Use the following command to restore the configuration files:
bkp_restore.sh -m restore_config -t time_stamp -F noDCM
In the preceding command, time_stamp is the time stamp on the backup that you are using for the restore procedure. This should be the same time stamp as the one used in step 1.
Before running the bkp_restore.pl script on an Oracle Application Server Metadata Repository Creation Assistant database, set the PERL5LIB environment variable to the path of the Oracle Application Server Metadata Repository Creation Assistant database Perl directory.
If the flash recovery area is outside of the Oracle home of an infrastructure metadata repository installation, then the directory will not be recreated during an Loss of Host Automation (LOHA) recovery. To avoid this issue, save the information when taking the Oracle home image backup on the original host, then make the directory available on the new host with the same read/write permissions as the original host.
An error message similar to the following may be displayed when backing up a database that does not have an OracleAS Portal application registered:
perl bkp_restore.pl -m backup_cold_incr Performing cold incremental backup ... Checking for portal registration ... Error encountered while querying database for portal registration !!! See /private/iasinst/work/db300/backup_restore/logs/2007-05-24_16-03-29_portal.tmp for more info. Incremental cold database backup completed successfully !!!
This message can be ignored.
When you execute either an opmnctl stopall or opmnctl startall command, the oidctl log file contains the following error message:
*** Instance Number already in use. *** *** Please try a different Instance number. ***
This error message can be safely ignored.
This error message occurs in Oracle Application Server Infrastructure installations with Oracle Internet Directory.
This section describes issues related to port changes. It includes the following topic:
After you change the Oracle HTTP Server Listen Port, you should update portlist.ini with the new port number. This will avoid potential problems if you later associate the middle tier with an OracleAS Infrastructure or change the OracleAS Infrastructure associated with the middle tier. The portlist.ini file is located in the following directory:
ORACLE_HOME/install
This section describes issues related to cloning Oracle Application Server instances. It includes the following topics:
Section 3.3.1, "Considerations for Cloning Oracle Ultra Search"
Section 3.3.2, "Considerations for Cloning OracleBI Discoverer"
Section 3.3.3, "Considerations for Cloning OracleAS Forms and Reports Services"
When you clone an OracleAS Portal instance that has SSL enabled, the Ultra Search Administration link on the Services portlet and Application Server Control Console page point to the URLs for the source instance, not the cloned instance.
To work around this problem, edit the following file and update the PortalListeningHostPort property with the correct port number:
Oracle_Home/sysman/emd/targets.xmlThe port number can be found in the following file:
Oracle_Home/install/portlist.ini
The following describes important information about cloning OracleBI Discoverer:
Values set by users after installation in configuration.xml are not preserved in the cloned Oracle home. The file is located at:
Oracle_Home/discoverer/config/configuration.xml
To work around this problem, reset the overwritten values by copying them from the configuration.xml file in the source Oracle home to the configuration.xml file in the cloned Oracle home.
After you clone a OracleBI Discoverer instance, when you click the Exit link on the Discoverer Viewer page, it results in a corrupted page because the port number in the oc4j.properties file has not been properly updated. To work around this problem, edit the following file and update the oracle.discoverer.applications.port property with the correct port number:
Oracle_Home/j2ee/OC4J_BI_Forms/config/oc4j.properties
The port number can be found in the following file:
Oracle_Home/install/portlist.ini
The following describes important information about cloning OracleAS Forms and Reports Services (installed from a separate CD):
If you clone OracleAS Forms and Reports Services and then associate it with an OracleAS Infrastructure, the cloned instance is not part of a farm. To make the instance part of a farm, use the following command in the cloned Oracle home:
dcmctl joinfarm
Information about cloning OracleAS Forms and Reports Services in the Oracle Application Server Administrator's Guide is not entirely correct. The section "Considerations for Cloning OracleAS Forms and Reports Services" states:
"Before you run the prepare_clone.pl script, you must update the ias.properties file in the source Oracle home, changing the value of DatabaseManagedClusterSupport from false to true, as shown in the following example:
DatabaseManagedClusterSupport=true"
This information is correct only if OracleAS Forms and Reports Services is associated with a Metadata Repository.
If OracleAS Forms and Reports Services is not associated with a Metadata Repository, the value of DatabaseManagedClusterSupport should be false.
This section describes other management issues. It includes the following topics:
Section 3.4.1, "Use Trusted Certificates When Enabling SSL Between mod_oc4j and OC4J"
Section 3.4.2, "Benign Decoding Errors When Running ldapaddmt"
Section 3.4.3, "Missing Files During restore_config Operation"
Section 3.4.4, "Additional Information for Performance Tuning on the Solaris 10 Operating System"
Section 3.4.5, "Performance Improvement on Multiple Processors Systems"
You must use trusted certificates on both ends when enabling SSL between mod_oc4j and OC4J.
Otherwise, you will get the following error when accessing the HTTPS port:
500 Internal Server Error
Chapter 11, "Changing from a Test to a Production Environment," in Oracle Application Server Administrator's Guide contains steps for migrating Oracle Internet Directory data to a production environment.These steps include running the ldapaddmt command, and examining the add.log file. The add.log file may contain a 'Decoding Error' message. This is benign and can be ignored.
Running restore_config may result in missing files messages such as:
Could not copy file /OracleAS/Devkit_1129/testdir/ to /OracleAS/Devkit_1129/backup_restore/cfg_bkp/2004-12-01_03-26-22.
During a restore_config operation, a temporary configuration backup is taken so that, if the restore fails, the temporary backup can be restored returning the instance to the same state as before the restore.If some files are deleted (including files/directories specified in config_misc_files.inp) before a restore operation, then, during the temporary backup, messages are displayed indicating that certain files are missing. These error/warning messages should be ignored since the missing files are restored as part of the restore_config operation.
Chapter 5, "Optimizing Oracle HTTP Server", of the Oracle Application Server Performance Guide contains information on setting tuning parameters for the Solaris operating system. On the Solaris 10 operating system, all System V interprocess communication (IPC) facilities are either automatically configured or controlled by resource controls. Therefore, no additional operating system tuning is required.
Therefore, for the Solaris 10 operating system, you can disregard section 5.1, "TCP Tuning Parameters (for UNIX)" in the Oracle Application Server Performance Guide.
If you have installed Oracle Application Server on a system with multiple processors, you may see a performance benefit from enabling parallel garbage collection by adding -XX:+UseParallelGC to the jvm options. Refer to the following Web site for more information:
http://java.sun.com/developer/technicalArticles/Programming/turbo/index.html
This section describes documentation errata in management documentation. It includes the following topics:
Section 3.5.1, "Errors in the Distributed Configuration Management Administrator's Guide"
Section 3.5.2, "Errors in Oracle Process Manager and Notification Server Administrator's Guide"
Section 3.5.3, "Error in Oracle Application Server Administrator's Guide"
Section 3.5.4, "No runstartupconsole command to Start and Stop Instances"
Section 3.5.5, "Incorrect Reference in Oracle Application Server Concepts Guide"
Section 3.5.6, "Incorrect Default Value for start-mode Element in Oracle HTTP Server opmn.xml file"
Section 3.5.7, "Incorrect Step in Oracle Application Server Administrator's Guide"
Section 3.5.8, "Incorrect Port Numbers in Oracle Application Server Administrator's Guide"
Section 3.5.11, ""retry" Attribute Not Valid for <ping> Element"
Section 3.5.12, "Default Ping Timeout Value in OPMN Is 30 Seconds, Not 20"
Section 3.5.13, "Correction to Cloning Procedure in Oracle Application Server Administrator's Guide"
The Distributed Configuration Management Administrator's Guide contains the following documentation errors:
In the "Tips:" listing in Section 2.2.6, "Removing an Oracle Application Server Instance From a DCM-Managed OracleAS Cluster":
"See leaveCluster for instructions on removing a DCM-Managed OracleAS Cluster from an Oracle Application Server Instance ..."
should be:
"See leaveCluster for instructions on removing an Oracle Application Server Instance from a DCM-Managed OracleAS Cluster..."
In the "Important:" listing and the paragraph before step1 in section 2.2.11.3, "Setting Up Keystore Information File on Each Instance in the OracleAS File-based Farm":
"repository host instance OracleAS File-Based Farm"
should be:
"repository host instance for OracleAS File-Based Farm (or repository host instance of OracleAS File-Based Farm) "
In the paragraph before the "Tip:" listing in section 2.3.2, "Deleting an OC4J Instance":
"nameOfOC4JInstance is the identifier for the new OC4J instance"
should be:
"nameOfOC4JInstance is the identifier for the OC4J instance you want to delete"
In the paragraph before the "Note:"listing in Section 2.4.1, "Log File Location and Naming":
"the log.xml file is renamed to log1-N.xml, and a new log.xml file is created."
should be:
"the log.xml file is renamed to logN+1.xml, and a new log.xml file is created."
In the first paragraph in section 2.2.7, "Exporting and Importing Configurations From a File-based Repository":
"This section explains how to save and restore a repository and move an Oracle Application Server Instance from one repository to another."
should be:
"This section explains how to save and restore a repository."
The Oracle Process Manager and Notification Server Administrator's Guide contains the following documentation errors:
In Section 1.12, "Security", the following sentence is incomplete:
"This is expected OPMN behavior Oracle Application Server;"
should be:
"This is expected OPMN behavior;"
In the <dependencies> lisitng in Section 3.2, "opmn.xml Element and Attribute Descriptions" the following sentence is incorrectly shown twice:
"OPMN will create an aggregate dependency list at the process-set level that contains all dependencies defined at or above it. If duplicate dependencies are defined at different levels, then duplicate checks on the dependency will be made before starting a process."
In Section 4.4, "Oracle HTTP Server Attribute Descriptions", the following paragraph is shown twice:
"The number of Oracle HTTP Server Instances to start. Only valid value is 1".
Oracle Application Server Administrator's Guide lists the following supported types for backup and recovery:
J2EE and Web Cache
J2EE Standalone
Portal and Wireless
Business Intelligence and Forms
Infrastructure (Identity Management and Metadata Repository)
Infrastructure (Identity Management only)
Infrastructure (Metadata Repository only)
OracleAS TopLink (Standalone or installed into a middle-tier Oracle home)
Oracle BPEL Process Analytics
Oracle Content Management Software Development Kit
Integration B2B
Business Intelligence CD
Cold Failover Cluster (Infrastructure)
Cold Failover Cluster (Middle Tier)
Identity Management (Oracle Internet Directory + Single Sign-On)
Identity Management (Oracle Internet Directory)
Identity Management ( Single Sign-On)
Identity Management High Availability
MRCA 10.1.0.x (Real Application Clusters Database)
MRCA 9.2.0.x
The correct is list is as follows:
J2EE and Web Cache
J2EE Standalone
Portal and Wireless
Business Intelligence and Forms
Infrastructure (Identity Management and Metadata Repository)
Infrastructure (Identity Management only)
Infrastructure (Metadata Repository only)
OracleAS TopLink (Standalone or installed into a middle-tier Oracle home)
Oracle BPEL Process Analytics
Oracle Content Management Software Development Kit
Integration B2B
Business Intelligence CD
Cold Failover Cluster (Infrastructure)
Cold Failover Cluster (Middle Tier)
Identity Management (Oracle Internet Directory + Single Sign-On)
Identity Management (Oracle Internet Directory)
Identity Management ( Single Sign-On)
Identity Management High Availability
MRCA 10.1.0.x (Real Application Clusters Database and non-Real Application Clusters Database)
MRCA 10.2 (Real Application Clusters Database and non-Real Application Clusters Database)
MRCA 9.2.0.x
The Oracle Application Server Administrator's Guide describes how to start and stop Application Server instances using the runstartupconsole command. This command is not supported for 10.1.2.0.2. Use the procedures in the following sections to start and stop instances.
This section describes how to start all processes in an OracleAS Infrastructure. The procedure applies to all OracleAS Infrastructure types:
Oracle Identity Management and OracleAS Metadata Repository: Follow both steps to start Oracle Identity Management and OracleAS Metadata Repository.
OracleAS Metadata Repository only: Follow only Step 1 to start OracleAS Metadata Repository. You do not need to perform the second step of starting Oracle Identity Management because you do not need OPMN or the Application Server Control Console in a OracleAS Metadata Repository-only installation.
Oracle Identity Management only: Follow only Step 2 to start Oracle Identity Management. Make sure the OracleAS Metadata Repository that supports Oracle Identity Management (residing in another Oracle home) is already started.
To start OracleAS Infrastructure:
If your OracleAS Infrastructure contains OracleAS Metadata Repository, start it as follows:
Set the ORACLE_HOME environment variable to the OracleAS Infrastructure Oracle home.
Set the ORACLE_SID environment variable to the OracleAS Metadata Repository SID (default is orcl).
ORACLE_HOME/bin/lsnrctl start
Start the OracleAS Metadata Repository instance:
ORACLE_HOME/bin/sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> startup
SQL> quit
Start the Oracle Enterprise Manager 10g Database Control:
emctl start dbconsole
If your OracleAS Infrastructure contains Oracle Identity Management, start it as follows:
opmnctl startall
This command starts OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and Oracle Internet Directory.
Start the Application Server Control Console:
emctl start iasconsole
Alternatively, on Windows, you can start the Application Server Control Console using the Windows Services control panel. The name of the service for the Application Server Control uses the following format:
OracleOracleHomeNameASControl
See the Oracle Application Server Administrator's Guide for more information.
Alternatively, on Windows, you can start the Infrastructure from the Programs menu: Start > Programs > Oracle Application Server Infrastructure - Infra_name > Start instanceName.
This section describes how to stop all processes in OracleAS Infrastructure. The procedure applies to all OracleAS Infrastructure types:
Oracle Identity Management and OracleAS Metadata Repository: Follow both steps to stop Oracle Identity Management and OracleAS Metadata Repository.
OracleAS Metadata Repository only: Follow step 2 only to stop OracleAS Metadata Repository.
Oracle Identity Management only: Follow step 1 only to stop Oracle Identity Management.
To stop OracleAS Infrastructure:
If your OracleAS Infrastructure contains Oracle Identity Management, stop it as follows:
Stop the Application Server Control Console:
emctl stop iasconsole
Alternatively, on Windows, you can stop the Application Server Control Console using the Services control panel. See the Oracle Application Server Administrator's Guide for more information.
opmnctl stopall
This command stops OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and Oracle Internet Directory.
If your OracleAS Infrastructure contains OracleAS Metadata Repository, stop it as follows:
Set the ORACLE_HOME environment variable to the OracleAS Infrastructure Oracle home.
Set the ORACLE_SID environment variable is set to the OracleAS Metadata Repository SID (default is orcl).
Stop the OracleAS Metadata Repository instance:
ORACLE_HOME/bin/sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> shutdown
SQL> quit
Stop the Net Listener:
ORACLE_HOME/bin/lsnrctl stop
Stop the Oracle Enterprise Manager 10g Database Control:
emctl stop dbconsole
Alternatively, on Windows, you can stop the Infrastructure from the Programs menu: Start > Programs > Oracle Application Server Infrastructure - Infra_name > Stop instanceName.
To start a middle-tier instance:
If the middle-tier instance uses OracleAS Infrastructure services, such as Oracle Identity Management or OracleAS Metadata Repository, make sure they are started.
Start components:
opmnctl startall
This command starts OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and OracleAS Web Cache, OracleAS Forms Services, and OracleAS Reports Services.
Start the Application Server Control Console:
emctl start iasconsole
Alternatively, on Windows, you can start the Application Server Control Console using the Services control panel. See the Oracle Application Server Administrator's Guide for more information.
Alternatively, on Windows, you can start the middle tier from the Programs menu: Start > Programs > Oracle Application Server - Oracle_Home > Start > instanceName.
To stop a middle-tier instance:
Stop the Application Server Control Console:
emctl stop iasconsole
Alternatively, on Windows, you can stop the Application Server Control Console using the Services control panel. See the Oracle Application Server Administrator's Guide for more information.
Stop components:
opmnctl stopall
This command stops OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and OracleAS Web Cache, OracleAS Forms Services, and OracleAS Reports Services.
Alternatively, on Windows, you can stop the middle tier from the Programs menu: Start > Programs > Oracle Application Server - Oracle_Home > Stop > instanceName.
Section 7.2, " Oracle Application Server Infrastructure Architecture" in the Oracle Application Server Concepts Guide contains the following reference:
"Some of the most frequently used deployment topologies for both Oracle Application Server Infrastructure itself and for applications which use Oracle Application Server Infrastructure are discussed in Chapter 12, "Recommended Topologies"".
The reference should be to Chapter 12, "Enterprise Deployments".
The id="start-mode" default value for the opmn.xml file listed in the Oracle HTTP Server chapter of the Oracle Process Manager and Notification Server Administrator's Guide is incorrectly listed as ssl-enabled. The default value for id="start-mode" is ssl-disabled.
Oracle Application Server Administrator's Guide contains the following error:
In Section 22.2.6 "Restoring Infrastructure Configuration Files," task 1 is incorrect. The step should not be included in the procedure.
Appendix D of the Oracle Application Server Administrator's Guide lists the default port numbers for Oracle Application Server. For the following ports, the information is incorrect:
Application Server Control Console RMI
Oracle Management Agent
Oracle Internet Directory (SSL)
For the correct ports, refer to the Oracle Application Server Installation Guide.
In the Oracle Application Server Administrator's Guide, Section 4.3.3, "Changing the Oracle HTTP Server Listen Ports" does not specify the shell used for UNIX in the examples and thus could be confusing.
The commands are shown using csh. If you are using another shell, such as bash, the syntax might be slightly different. For example, using the bash shell, the command in Task 2 would be:
alias portconfig='$ORACLE_HOME/jdk/bin/java -cp \ $ORACLE_HOME/sysman/webapps/emd/WEB-INF/lib/emd.jar:\ $ORACLE_HOME/dcm/lib/dcm.jar:\ $ORACLE_HOME/sso/lib/ossoreg.jar \ oracle.sysman.ias.sta.tools.PortConfigCmdLine \!*'
Also, in Task 2, the command that begins alias portconfig should be entered on one line. It is shown on multiple lines to make it easier to read.
In the Oracle Application Server Administrator's Guide, Section 8.2.2, "Changing the Hostname, Domain Name, or IP Address of a Middle-Tier Installation," refers to a Forms:Reports standalone installation, in addition to the middle-tier installation types listed in the section.
Chapter 6, "opmn.xml Common Configuration", of the Oracle Process Manager and Notification Server Administrator's Guide lists retry as one of the attributes of the <ping> element. This is incorrect: the retry attribute cannot be used with the <ping> element.
You can set up a custom ping command in the opmn.xml file. For details, see chapter 10, "Configuring Custom Process", in the Oracle Process Manager and Notification Server Administrator's Guide.
The Oracle Process Manager and Notification Server Administrator's Guide incorrectly states that the default ping timeout value is 20 seconds. It is actually 30 seconds.
In the Oracle Application Server Administrator's Guide, Section 10.4.2, "Preparing the Source," step 3 shows an example of how to archive and compress the source on UNIX. This example will not archive and compress any "dot files," i.e., files whose names start with a period, in the source directory. The correct commands are:
cd Source_Oracle_Home cd .. tar cf - Source_Oracle_Home | gzip > oracleas.tar.gz
To extract the files, replace the example in step 2 of Section 10.4.3, "Cloning the Instance," with the following commands:
gunzip < Dir_Containing_Tar/oracleas.tar.gz | tar xf - mv Source_Oracle_Home_Name Destination_Oracle_Home_Name
In Section 9.2.3.4, "Updating the httpd.conf File," of the Oracle Application Server Enterprise Deployment Guide, the KeepAlive line in step 7 should be:
KeepAlive Off
not
KeepAlive off
The O in Off should be in uppercase.
In additon to the required options listed in Table 8, "Required Database Options"in Section 1.5.9, "Database Options" in the Oracle Application Server Repository Creation Assistant User's Guide, you must also include Oracle XML DB. If you do not have all of the required options, OracleAS RepCA will not run properly.
