Adding/removing report server in 10g Application Server

To delete the Report server you have to follow some steps:

1. Stop opmn processes.
2. Stop EM console
3. Take a backup of opmn.xml
4. Open opmn.xml. There must be an entry related to your reports server.
    Carefully delete that whole tag.
5. Then do "opmnctl validate" to validate your opmn.xml.
6. Take a backup of targets.xml.
7. Open targets.xml.. There must be a entry for your reports server in that.
    Delete that whole tag from there.
8. Start opmn processes.
9. Start EM Console.

To add new reports server:
1. Adding a new report server with the name my_report_server
   $ rwserver.sh server=my_report_server batch=yes

2. Register with OEM and OPMN
   $ addNewServerTarget my_report_server

3. Open configuration file created in the name of new report server
   $ vi $ORACLE_HOME/reports/conf/my_report_server.conf

4. Change SourceDir and tempDir values to the actual one.

5. Start newly added report server process.

adapcctl.sh: exiting with status 204

On a new VIS R12.1 installation, the OHS (oracle http server) failed to start and give status 204.

Upon querying the status of opmn managed processes with adopmnctl.sh, the following status is shown:

Processes in Instance:
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
OC4JGroup:default_group          | OC4J:oafm          |    9713 | Alive
OC4JGroup:default_group          | OC4J:forms         |    9648 | Alive
OC4JGroup:default_group          | OC4J:oacore        |    9570 | Alive
HTTP_Server                      | HTTP_Server        |     N/A | Down




On  driilling through the http server logfile on $INST_TOP/logs/ora/10.1.3/opmn/HTTP_Server~1.log

found some error like this:

10.1.3/Apache/Apache/bin/httpd: error while loading shared libraries: libdb.so.2: cannot open sh
ared object file: No such file or directory

I thought this could be due to some link files, not properly linked on /usr/lib or /lib folders.
I searched for link file libdb.so.2 on /usr/lib and /lib folders. But nothing found.
So, I  went on creating a link file " libdb.so.2" on both the folders.

Now, I restarted the OHS.

This time it gave the same 204 status. Http log shows,

Cannot load $IAS_ORACLE_HOME/Apache/Apache/libexec/mod_ossl.so into server: $IAS_ORACLE_HOME/Apache/Apache/libexec/mod_ossl.so: undefined symbol: dbm_firstkey

Now, the situation got really worse. I googled a lot, but found nothing related.

Finally, I checked for the pre-requisite rpm one-by-one. I referred Metalink doc:607883 once again.
 There I got the fix.

I missed to apply patch 607883. It was clearly mentioned on this doc, that this patch would fix an issue with the Oracle HTTP Server (missing libdb.so.2)

Applied the patch and this time OHS started fine.

Disabling Single Sign-On on Report Server

While accessing a 10g Application Server report, the user need to log-in through Single Sign-on process.

Though this is an additional security feature, someone may feel this annoying.

In this Post, I'll explain, how to avoid single sign-on process while accessing 10g AS reports.

Step 1: Disable Single Sign-on:
Uncomment the SINGLESIGNON parameter in the Reports Servlet configuration file (rwservlet.properties) and set it to "NO". This file is located in $ORACLE_HOME/reports/conf directory.

Note: The SINGLESIGNON value is usually commented out after installation, but the default value is YES.

Step 2: Disable Reports Server Security:

Though, the single sign-on is disabled, we need to sign-on at "reports server security" process, in order to access the reports.
To disable this, the security element in the Reports Server configuration file, ($ORACLE_HOME/reports/conf/servername.conf) must be commented out.


The default value would be like this:

"security id="rwSec" class="oracle.reports.server.RWSecurity>"

"!--property name="securityUserid" value="portal_id/portal_password@portal_schema" 

confidential="yes" encrypted="no"-->"

"property name="oidEntity" value="%REPORTS_OID_ENTITY%" confidential="yes" 

encrypted="no"/>"

"/security>"

Commenting out the above security element will disable the Reports server security process.

Step 3: Restart the report server opmn process.

That's all...

You won't get any annoying screen, asking for username and passwords.

But remember, you are reducing an additional security feature.