2 Starting and Stopping OracleAS Reports Services

2.1.3.1 Starting the In-process Server (Windows and UNIX)

If you are using Reports Server as an in-process server (the default configuration), sending a run report request starts the in-process server; however, if you are sending a request through a command line, the servlet must be invoked first using either the run report URL or the Web command URL. When you have successfully started the servlet, this also means you have successfully started the in-process server.

To directly start the in-process server from a URL, enter the following from your Web browser:

http://your_machine_name:your_port_num/reports/rwservlet/startserver

2.1.3.2 Starting Reports Server from a Command Line (Windows and UNIX)

You can also start Reports Server as a standalone server on Windows using the following command:

rwserver server=server_name

Add the BATCH command line keyword to start up the server without displaying dialog boxes or messages.

rwserver server=server_name batch=yes

You can run this command on UNIX using the following syntax:

rwserver.sh server=server_name

Or:

rwserver.sh server=server_name batch=yes

You can run this command from any directory as long as the shell script can be reached in your PATH environment variable.

2.1.3.3 Stopping Reports Server

There are several ways to stop Reports Server on Windows and UNIX, as follows:

• If Reports Server is running on Windows through the rwserver executable, or on UNIX through a shell script, rwserver.sh, click Shutdown in the Reports Server dialog box.

• If you are not running Reports Server from the command line, launch Oracle Enterprise Manager 10g, and navigate to the Reports Server you wish to shut down, then click Stop on the selected Reports Server's home page. For more information on Reports Server and Oracle Enterprise Manager 10g, see Chapter 19, "Managing and Monitoring OracleAS Reports Services".

• If Reports Server is running as an in-process server through the Reports Servlet, issue the following URL:

  http://your_host_name:port_number/reports/rwservlet/stopserver
  
  

• If Reports Server is running from a command line on Windows or UNIX, use any of the following commands, depending on how you want to shut down the Reports Server.

  
  

  Note: On UNIX, use rwserver.sh instead of rwserver.

  
  

  To shut down the server normally (that is, finish pending jobs and then stop):

  rwserver server=server shutdown=normal authid=username/password
  
  

  To shut down the server immediately (that is, stop without finishing pending jobs):

  rwserver server=server shutdown=immediate authid=username/password
  
  

  To shut down the server without displaying any related messages:

  rwserver server=server shutdown=normal authid=username/password batch=yes
  
  

  The keywords used with the rwserver command are described in Appendix A, "Command Line Keywords".

  
  

  Note: authid is Reports Server's administration user name and password. For a secure Reports Server, this user must be a member of the RW_ADMINISTER privilege group in Oracle Internet Directory. For a non-secure Reports Server, this user is defined in the identifier element. The following bullet contains more information on how to stop a non-secure Reports Server using the command line.

  
  

• When you stop or shut down a non-secure Reports Server from the command line using either rwserver.sh or rwrqv.sh, you need to provide a valid authid, which must match the value set in the identifier element in the server configuration file. However, the identifier element is set during Reports configuration while installing Oracle Application Server 10g and encrypted by Reports Server. You can reset the identifier element to any value. If you have registered this Reports Server with Oracle Enterprise Manager 10g and OPMN, you also need to change the corresponding properties in targets.xml for Oracle Enterprise Manager 10g integration to work. Perform the following steps:

  1. In the non-secure Reports Server's configuration file, server_name.conf, modify the identifier element to specify the username/password and set the encrypted attribute to no. For example:

     <identifier confidential="yes" encrypted="no">scott/tiger</identifier>
     
     

  2. Stop and restart Reports Server manually for the changes made to the server_name.conf file to take effect.

     
     

     Note: You must restart Reports Server for any configuration changes to take effect.

     
     

     Reports Server will now encrypt the username/password value of the identifier element. After Reports Server reads the changes made in the server_name.conf file, the following commands should execute successfully (with scott/tiger as the username/password):

     ./rwserver.sh server=server_name shutdown=normal authid=scott/tiger
     ./rwrqv.sh server=server_name shutdown=normal authid=scott/tiger
     
     

  3. For Oracle Enterprise Manager 10g integration, edit the targets.xml file (in ORACLE_HOME/sysman/emd/) using any text editor, as follows:

     • Search for target with TYPE="oracle_repserv" and DISPLAY_NAME="Reports Server: server_name".

     • In the entry, set the UserName property and the Password property to the same user name and password as in the identifier element in the server_name.conf file. Set the ENCRYPTED attribute to FALSE for these two properties.

     • Restart Oracle Enterprise Manager 10g for the changes to take effect.

  You should now be able to stop and shut down a non-secure Reports Server using Oracle Enterprise Manager 10g.

  
  

  Note: These steps are required only for a non-secure Reports Server and not for secure Reports Servers.