Publishing Reports to the Web - Downloads - Oracle

Configuring Reports Server
1. Open reports.sh and comment the environment variable value. For
example, comment the REPORTS_PATH value set in the reports.sh file.
2. Open the server_name.conf file.
3. Copy the environment variable value in the reports.sh file to the server_
name.conf file using the environment id tags. For example:
4. Add the defaultEnvId value to the appropriate tag in the server_
name.conf file.For example, add the defaultEnvId value to the engine tag
so that the engine starts with the default REPORTS_PATH.
5. Now run the report.
■ In previous releases of Oracle Reports on Solaris, you were required to add the
following line in the reports.sh file:
NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1; export NLS_LANG
This workaround was introduced because OPMN implicitly sets NLS_LANG to
AMERICAN_AMERICA.WE8MSWIN1252, which is passed to the engine if NLS_
LANG is not set. This caused a problem in Solaris because the encoding doesn't
exist. However, the NLS_LANG setting in reports.sh breaks the environment
switching feature and will result in any of the following errors:
REP-3000: Internal error starting Oracle Toolkit
or
REP-56048: Engine rwEng-0 crashed
To work around this issue, you must remove the NLS_LANG entry in
reports.sh.
3.2.3 Connecting to OracleAS Portal
By default, Reports Server can only use portal users to connect to OracleAS Portal. It
cannot use an ordinary userid, such as scott/tiger, unless you first assign
appropriate privileges to its schema.
To assign the appropriate privileges to a schema other than the portal schema, you
need to run the following script from SQL*Plus as an OracleAS Portal user:
Configuring OracleAS Reports Services 3-31