How To Install/Start A Standalone Report Server On MS Windows 2000/2003 After An Oracle AS 10g R2 Installation

How To Install/Start A Standalone Report Server On MS Windows 2000/2003 After An Oracle AS 10g R2 In

How To Install/Start A Standalone Report Server On MS Windows 2000/2003 After An Oracle AS 10g R2 In

Titleimage

Posted by Patrick Hamou on 2017:09:11 21:21:45

APPLIES TO:

Oracle Reports Developer - Version 10.1.2.0.2 to 10.1.2.3 [Release Oracle10g to 10gr2]
z*OBSOLETE: Microsoft Windows Server 2003
z*OBSOLETE: Microsoft Windows 2000
Microsoft Windows 2000Microsoft Windows Server 2003
***Checked for relevance on 15-Apr-2013*** 
 

GOAL

Per the below reference:

Oracle� Application Server Reports Services Publishing Reports to the Web
10g Release 2 (10.1.2)
B14048-01

*********************************************************************************************

Important:

You must start or stop a Reports Server registered with Oracle Enterprise Manager 10g only through Oracle Enterprise Manager 10g/OPMN. OPMN automatically restarts Reports Server if it stops responding for some reason. On Windows, OPMN itself is run as a Windows service.

Beginning with Oracle Reports 10g Release 2 (10.1.2), running Reports Server as a Windows service is no longer supported (rwserver -install server_name). As a result, the related command line keywords INSTALL and UNINSTALL are also obsolete. If you start or stop a Reports Server that is managed by OPMN running as a Windows service or through the command line, you may face the following issues:

·         The Reports Server's status will not be reflected accurately in Oracle Enterprise Manager 10g.

·         Oracle Enterprise Manager 10g may display errors when starting or stopping the Reports Server.

For more information about the obsolescence of running Reports Server as a Windows service, see A Guide to Functional Changes Between Oracle Reports 6i and 10g on the Oracle Technology Network (OTN).

 

*********************************************************************************************

If the syntax 'rwserver -install server_name' is now obsolete for the Microsoft Windows 2000 and/or Microsoft Windows Server 2003 installations as of Oracle Application Server Enterprise Edition 10g Release 2 (10.1.2.0.2), what is the proper procedure(s) for adding a new standalone Report Server?

SOLUTION

Creating a standalone report server as a Windows service is what has been obsoleted.

Instead, create a standalone report server as a non-service using the following syntax:
$ORACLE_HOME\BIN>rwserver server=reports_server_name batch=yes

To start a stopped standalone report server from command-line, use the following syntax:
$ORACLE_HOME\BIN>rwserver server=reports_server_name

*****************

If you want to create a standalone reports server and you do not want to administer it via OPMN and EM, please use the following syntax:
$ORACLE_HOME\BIN>rwserver server=reports_server_name batch=yes

If you want to create a standalone reports server and you DO want to administer it via OPMN and EM then please use the following steps. **
1- MIDTIERHOME\BIN> addNewServerTarget.bat reports_server_name
2- MIDTIERHOME\opmn\BIN> opmnctl reload
3- MIDTIERHOME\opmn\BIN> opmnctl startproc ias-component=<reports_server_name>
4- MIDTIERHOME\opmn\BIN> opmnctl status

** Notice that in the above steps the rwserver.exe command is not needed.  See also the PREREQUISITE below.

*****************

NOTE:  In an Oracle Application Server Enterprise Edition 10g release 2 (v. 10.1.2.0.2) installation, you
can also register an existing standalone report server with opmn as follows to view, stop, and start it:

PREREQUISITE:

When registering a standalone report server with OPMN/EM, if the report server is running at the time the addNewServerTarget.bat (or, in unix: addNewServerTarget.sh) command is invoked, the Report Server needs to be stopped manually first (ie. in unix: "kill -9 pid" -OR- "rwserver.sh server=report_server_name shutdown=immediate authid=username/password &) BEFORE the opmn registration using the 'addNewServerTarget' command is performed.:

To register the standalone report server with OPMN:
MIDTIERHOME\BIN> addNewServerTarget.bat reports_server_name
MIDTIERHOME\opmn\BIN> opmnctl stopall
MIDTIERHOME\opmn\BIN> opmnctl startall
MIDTIERHOME\opmn\BIN> opmnctl status

NOTE:  Do NOT register the inprocess (aka in-process) server (ie. rep_<hostname_instance>) as it is already registered with the Enterprise Manager Console website and OPMN.  Doing so will cause problems.  The inprocess server is not intended to be viewed and/or stopped/started from command-line or opmnctl. 

POST REGISTRATION STEPS:

Also, after registration with OPMN/EM, discontinue starting/stopping the standalone report server using rwserver.exe or it will conflict with its usage via opmnctl.

To start up a standalone report server that reflects down:

MIDTIERHOME\opmn\BIN> opmnctl startproc ias-component=<report server name>

To stop a standalone report server that reflects 'Alive':

MIDTIERHOME\opmn\BIN> opmnctl stopproc ias-component=<report server name>

To start up all standalone report servers displayed:

MIDTIERHOME\opmn\BIN> opmnctl startproc process-type=ReportsServer

To stop all standalone report servers displayed:
MIDTIERHOME\opmn\BIN> opmnctl stopproc process-type=ReportsServer

NOTE:  You can also stop, start, and restart the standalone report server from the EM Console
Website as well once it has been registered with OPMN.

Return to Blog