Oracle® Fusion Middleware Publishing Reports to the Web with Oracle Reports Services 11g Release 1 (11.1.1) Part Number B32121-01 |
|
|
View PDF |
The Oracle Reports bridge is used to connect two subnets. It acts as a gateway between Oracle Reports components running in different subnets.
Note:
In Oracle Reports 11g Release 1 (11.1.1), the Oracle Reports bridge is integrated with Oracle Enterprise Manager 11g. Therefore, you can see the Oracle Reports bridge status or start and stop it from the Oracle Enterprise Manager .For troubleshooting scenarios and diagnosis, see Appendix D, "Diagnosing Oracle Reports Bridge Problems".
Before you can start the Oracle Reports bridge with Oracle Process Manager and Notification (OPMN), you must add the bridge to OPMN, as shown in the following example:
ORACLE_INSTANCE/bin/opmnctl createcomponent -adminUsername weblogic -adminHost <host_name> -adminPort <port> -oracleHome <oracle_home -oracleInstance <instance_home> -instanceName <instancename> -componentName <bridge_name> -componentType ReportsBridgeComponent
To start the Oracle Reports bridge if it was configured through the Oracle Process Manager and Notification (OPMN) Server, use either of the following commands:
ORACLE_INSTANCE/bin/opmnctl startproc ias-component=bridgename ORACLE_INSTANCE/bin/opmnctl startproc process-type=ReportsBridgeComponent
To stop the Oracle Reports bridge, use the following command:
ORACLE_INSTANCE/bin/opmnctl stopproc ias-component=bridgename
To restart the Oracle Reports bridge, use the following command:
ORACLE_INSTANCE/bin/opmnctl restartproc ias-component=bridgename
The Oracle Reports bridge name must match the name in the ias-component id
in the opmn.xml
file.
You can also query the status of the Oracle Process Manager and Notification bridge, using the following command:
ORACLE_INSTANCE/bin/opmnctl status
For more information on configuring the Oracle Reports bridge through the Oracle Process Manager and Notification Server, see Section 7.8.1.3, "Oracle Reports Bridge Specification"
It is recommended that you use Enterprise Manager or OPMN to start and stop Oracle Reports components.
You need to set the following environment variable before you start or stop the Reports Bridge component:
COMPONENT_CONFIG_DIRECTORY=ORACLE_INSTANCE/config/ReportsBridgeComponent/<reports_bridge_name>
To start the Oracle Reports bridge from the command line, use the following commands:
On Windows:
rwbridge.bat name=bridgename
On UNIX:
rwbridge.sh name=bridgename
For example, to start an Oracle Reports bridge named foo
on Windows, use the following command:
rwbridge.bat name=foo
For more information about the rwbridge executable, see Section A.2.7, "rwbridge"
Oracle Reports creates a configuration file, rwbridge.conf
when the Oracle Reports bridge is started for the first time. This file is generated based on the settings in the rwbridge.template
file and is located in the ORACLE_INSTANCE\config\ReportsBridgeComponent\bridge_name
directory. Edit the rwbridge.conf
file to specify remote Oracle Reports bridges to connect to other subnets.
Note:
You must restart the Oracle Reports bridge for any configuration changes to take effect.To stop an Oracle Reports bridge, use the following command:
On Windows:
rwbridge.bat name=bridgename shutdown=normal authid=username/password
On UNIX:
rwbridge.sh name=bridgename shutdown=normal authid=username/password
For example, to stop an Oracle Reports bridge named foo
on UNIX, use the following command:
rwbridge.sh name=foo shutdown= normal authid=scott/tiger
In the configuration file, repbrg_bridgename.conf, modify the identifier element to specify the username/password
and set the encrypted
attribute to no. This is to indicate that the password is not encrypted. This password will be encrypted once the Oracle Reports bridge is started.
For example:
<identifier encrypted="no">scott/tiger</identifier>
Usage Notes
If the identifier element is commented, then it is possible to stop the Oracle Reports bridge without specifying authid
It is not possible to stop the Oracle Reports bridge remotely.
For more information see, Section 7.2.1.19, "identifier"