3 General Management and Security Issues

This chapter describes management and security issues associated with Oracle Application Server. It includes the following topics:

Section 3.1, "General Issues and Workaround"
Section 3.2, "Port Change Issues"
Section 3.3, "Cloning Issues"
Section 3.4, "Deployment Issues"

3.1 General Issues and Workaround

This section describes general management and security issues. It includes the following topic:

Section 3.1.1, "Error Message When Executing opmnctl Commands"

3.1.1 Error Message When Executing opmnctl Commands

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.

3.2 Port Change Issues

This section describes issues related to port changes. It includes the following topic:

Section 3.2.1, "Additional Step Needed After Changing Oracle HTTP Server Listen Port"

3.2.1 Additional Step Needed After Changing Oracle HTTP Server Listen Port

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

3.3 Cloning Issues

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"

3.3.1 Considerations for Cloning Oracle Ultra Search

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:

(UNIX) Oracle_Home/sysman/emd/targets.xml

The port number can be found in the following file:

(UNIX) Oracle_Home/install/portlist.ini

3.3.2 Considerations for Cloning OracleBI Discoverer

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:
```
(UNIX) 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:
```
(UNIX) Oracle_Home/j2ee/OC4J_BI_Forms/config/oc4j.properties
```
The port number can be found in the following file:
```
(UNIX) Oracle_Home/install/portlist.ini
```

3.3.3 Considerations for Cloning OracleAS Forms and Reports Services

The following describes important information about cloning OracleAS Forms and Reports Services (installed from a separate CD):

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
```
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
```

3.4 Deployment Issues

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"

3.4.1 Use Trusted Certificates When Enabling SSL Between mod_oc4j and OC4J

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

3.4.2 Benign Decoding Errors When Running ldapaddmt

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.

3.4.3 Missing Files During restore_config Operation

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.