Oracle Reports 12.2.1.4.0 - Create a Standalone Reports Server
On Friday, 27th September 2019, Oracle released the latest Version of Oracle Forms & Reports 12.2.1.4.0 (see my blog post http://dirknachbar.blogspot.com/2019/09/oracle-forms-reports-122140-available.html).
As I already created an Oracle Forms & Reports 12.2.1.4.0 environment, it's now time to have a look on the Oracle Reports 12.2.1.4.0 environment.
As usual, after you have successfully installed and configured your Oracle Forms & Reports 12.2.1.4.0 environment, the Oracle Reports Component is NOT configured completely.
Following steps you will have to perform:
Just perform following steps:
Now we have to align the rwserver.conf configuration file for the above created Oracle Standalone Reports Server, called in my example rep_server1.
To enable the Webcommands in the rwservlet just modify the rwservlet.properties file under $DOMAIN_HOME/config/fmwconfig/servers/<Name of Managed Server for Reports>/applications/reports_12.2.1/configuration
In order to see the environment/configuration for our newly created Oracle Standalone Reports Server rep_server1 just use following URL: http://<Your ServerName>:9002/reports/rwservlet/showenv?server=rep_server1
Summing up, Oracle Reports 12.2.1.4.0 is still the same as the previous release, but 2 positive topics are that you don't need anymore to create the symbolic link for the libXm.so.3 and you don't need any more the modification on the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files.
As I already created an Oracle Forms & Reports 12.2.1.4.0 environment, it's now time to have a look on the Oracle Reports 12.2.1.4.0 environment.
As usual, after you have successfully installed and configured your Oracle Forms & Reports 12.2.1.4.0 environment, the Oracle Reports Component is NOT configured completely.
Following steps you will have to perform:
- Create the required Reports Tools Instance
- Create the required Reports Server Instances
- Optionally, if you don't any kind of security for accessing the Reports, disable the security settings and activate the Webcommands for the rwservlet
What you don't need anymore in Oracle Reports 12.2.1.4.0 are following steps:
- No more symbolic link from /usr/lib/libXm.so.4 to libXm.so.3
- No more modification on the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files on your JDK and the JDK under your $MW_HOME/oracle/common/jdk
Just perform following steps:
#
# At first we are creating the required Oracle Reports Tools Instance
cd $MW_HOME/oracle_common/common/bin
./wlst.sh
# replace the password with your password and verify if port 7001 is your Admin Server Port
wls:/offline> connect('weblogic','password','localhost:7001')
wls:/fr_domain/serverConfig/> createReportsToolsInstance(instanceName='reptools1',machine='AdminServerMachine')
wls:/fr_domain/serverConfig/> exit()
# Next we are creating our required Oracle Standalone Reports Server
cd $MW_HOME/oracle_common/common/bin
./wlst.sh
wls:/offline> connect('weblogic','password','localhost:7001')
wls:/fr_domain/serverConfig/> createReportsServerInstance(instanceName='rep_server1',machine='AdminServerMachine')
wls:/fr_domain/serverConfig/> exit()
Now we have to align the rwserver.conf configuration file for the above created Oracle Standalone Reports Server, called in my example rep_server1.
#
# Open the rwserver.conf with an editor
# located under $DOMAIN_HOME/config/fmwconfig/components/ReportsServerComponent/<Reports Server Name>/rwserver.conf
# Align the following section from :
<cache class="oracle.reports.cache.RWCache">
<property name="cacheSize" value="50"/>
<!--property name="cacheDir" value="your cache directory"/-->
<!--property name="maxCacheFileNumber" value="max number of cache files"/-->
</cache>
<!--Please do not change the id for reports engine.-->
<!--The class specifies below is subclass of _EngineClassImplBase and implements EngineInterface.-->
<engine id="rwEng" class="oracle.reports.engine.EngineImpl" maxEngine="1" minEngine="1" engLife="50" >
<!--property name="sourceDir" value="your reports source directory"/-->
<!--property name="tempDir" value="your reports temp directory"/-->
<!--property name="keepConnection" value="yes"/-->
</engine>
# To (align the provided directories for cacheDir, sourceDir and tempDir to your settings)
<cache class="oracle.reports.cache.RWCache">
<property name="cacheSize" value="50"/>
<property name="cacheDir" value="/u00/app/oracle/demo_app/cache"/>
<property name="maxCacheFileNumber" value="50"/>
</cache>
<!--Please do not change the id for reports engine.-->
<!--The class specifies below is subclass of _EngineClassImplBase and implements EngineInterface.-->
<engine id="rwEng" class="oracle.reports.engine.EngineImpl" maxEngine="1" minEngine="1" engLife="50" >
<property name="sourceDir" value="/u00/app/oracle/demo_app/rdf"/>
<property name="tempDir" value="/u00/app/oracle/demo_app/temp"/>
<property name="keepConnection" value="yes"/>
</engine>
# In case you don't need any kind of security for your Oracle Reports align the following section as follows:
<job jobType="report" engineId="rwEng" securityId="rwJaznSec"/>
# To, remove the part securityId="rwJaznSec":
<job jobType="report" engineId="rwEng"/>
To enable the Webcommands in the rwservlet just modify the rwservlet.properties file under $DOMAIN_HOME/config/fmwconfig/servers/<Name of Managed Server for Reports>/applications/reports_12.2.1/configuration
# # Add the line <webcommandacess>L2</webaccesscommand> <?xml version="1.0" encoding="UTF-8"?> <rwservlet xmlns="http://xmlns.oracle.com/reports/rwservlet" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <server>rep_wls_reports_greenfield</server> <singlesignon>no</singlesignon> <inprocess>yes</inprocess> <webcommandaccess>L2</webcommandaccess> </rwservlet>Now start your Managed Server for Oracle Reports, normally WLS_REPORTS and after that start your newly created Oracle Standalone Reports Server
# cd $DOMAIN_HOME/bin # if you don't want to be prompted in future for the Nodemanager Password # use the option storeUserConfig, it will store the password ./startComponent rep_server1 storeUserConfig Starting system Component rep_server1 ... Initializing WebLogic Scripting Tool (WLST) ... Welcome to WebLogic Server Administration Scripting Shell Type help() for help on available commands Reading domain from /u00/app/oracle/user_projects/domains/demo_domain Please enter Node Manager password: Creating the key file can reduce the security of your system if it is not kept in a secured location after it is created. Creating new key... The username and password that were used for this WebLogic NodeManager connection are stored in /home/oracle/.wlst/nm-cfg-demo_domain.props and /home/oracle/.wlst/nm-key-demo_domain.props. Connecting to Node Manager ... <Sep 30, 2019 1:28:41 PM CEST> <Info> <Security> <BEA-090905> <Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true.> <Sep 30, 2019 1:28:41 PM CEST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to HMACDRBG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.> <Sep 30, 2019 1:28:41 PM CEST> <Info> <Security> <BEA-090909> <Using the configured custom SSL Hostname Verifier implementation: weblogic.security.utils.SSLWLSHostnameVerifier$NullHostnameVerifier.> Successfully Connected to Node Manager. Starting server rep_server1 ... Successfully started server rep_server1 ... Successfully disconnected from Node Manager. Exiting WebLogic Scripting Tool. DoneNow you can access the Reports rwservlet commands under http://<Your ServerName>:9002/reports/rwservlet
In order to see the environment/configuration for our newly created Oracle Standalone Reports Server rep_server1 just use following URL: http://<Your ServerName>:9002/reports/rwservlet/showenv?server=rep_server1
Summing up, Oracle Reports 12.2.1.4.0 is still the same as the previous release, but 2 positive topics are that you don't need anymore to create the symbolic link for the libXm.so.3 and you don't need any more the modification on the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files.
