How to Implement COS Naming Service for Reports Client-Server Interaction using OPMN

Oct 17, 2013

For Oracle Reports client-server interaction in 11g, this interaction can be performed in 1 or 2 ways:

  • Multicasting (Configured by default)
  • Naming Service

If you either wish to use a naming service instead of multicasting, or if you are using the default settings and you receive REP-51002 errors 100% of the time when running anything on rwservlet either with the in-process reports server or the standalone reports server, the following steps will show how you can set up a naming service to form a bridge between the Reports client and the Reports server. Also, this guide will explain how you can have the naming service run as an OPMN service (in Windows, this process will start up automatically).

Setup

    1. If your WLS_REPORTS WebLogic server and standalone report server(s) are running, please shut them down.
    2. Go to %ORACLE_INSTANCE%\config\OPMN\opmn and open up opmn.xml in a text editor (make a backup of this file first).
    3. Create a new <ias-component> after the ones for “dejvm” and “forms”:
      • <ias-component id=”namingservice”>
        <process-type id=”namingservice” module-id=”CUSTOM”>
        <environment>
        <variable id=”PATH” value=”%ORACLE_HOME%\jdk\bin”/>
        </environment>
        <process-set id=”namingservice” numprocs=”1″>
        <module-data>
        <category id=”start-parameters”>
        <data id=”start-executable” value=”%ORACLE_HOME%\jdk\bin\orbd”/>
        <data id=”start-args” value=”-port 1050 –ORBInitialPort %port%”/>
        </category>
        </module-data>
        </process-set>
        </process-type>
        </ias-component>
      • NOTE: %ORACLE_HOME% is the full path of your Forms Oracle Home and %port% is the port number you wish to use for your naming service.
      • IMPORTANT: Make sure that the port number %port% is not being used. Examples of port numbers we have used include 14021 or 14022.
      • image
    4. Further down in opmn.xml, look for <ias-component id=”RptSvr_%COMPUTERNAME%_asinst_1”> or something similar. After the </module-data> tag, add the following dependency (this allows OPMN to start the naming service before the standalone reports server):
      • <dependencies>
        <managed-process ias-component=”namingservice” process-type=”namingservice” process-set=”namingservice” autostart=”true”/>
        </dependencies>
      • image
    5. Save and close the file.
    6. Open up Command Prompt and navigate to %ORACLE_INSTANCE%\bin.
    7. If OPMN is not running, run “opmnctl start”. Otherwise, run “opmnctl reload”.
    8. Start the naming service with the following command: “opmnctl startproc ias-component=namingservice”
    9. If successful, you should see that the process is “Alive” when you run “opmnctl status”.
    10. Go to %ORACLE_INSTANCE%\config\ReportsServerComponent\RptSvr_%COMPUTERNAME%_asinst_1 and open rwnetwork.conf in a text editor (make a backup of this file first)
    11. Comment out the line <multicast channel…> and add a new line below:
      • <namingService name=”Cos” host=”%COMPUTERNAME%” port=”%port%”/>
      • NOTE: The port number must match what was used in step 3
      • image
    12. Save and close the file.
    13. Repeat steps 10-12 for %ORACLE_INSTANCE%\config\ReportsToolsComponent\ReportsTools\rwnetwork.conf and %DOMAIN_HOME%\config\fmwconfig\servers\WLS_REPORTS\applications\reports_11.1.2\configuration\rwnetwork.conf
    14. Start up WLS_REPORTS as well as any standalone reports servers you are using.

After following the steps above, you should be able to run your reports successfully using a naming service.

Source: http://docs.oracle.com/cd/E12839_01/bi.1111/b32121/pbr_conf008.htm#CHEHAECB