One of my close associates & a person I respect as a legend, Iudith said the following with one of her recent mails to me:
Regarding all this WebLogic issue … I have a feeling that Oracle “used a cannon for killing a fly” ………
Maybe that complicated setup creates an environment which can support all kinds of other products,I really don’t know because I have mostly just heard about it.
From Oracle’s perspectives, this approach may provide them better scalability, however how far such complexities will appease the developer crowd remains a big concern.
While the modernization of Oracle forms and reports, the maximum sought legacy development means remain a frequently sought and discussed topic, Oracle is definitely NOT doing enough to regain the confidence of mortals who spent decades developing, especially by making each and every newer versions difficult to install and setup.
Less said, let us go back to the topic, how to create and configure a standalone report server instance for 12c environment. This is my 3rd post in a row about installing and configuring 12c products related to Forms and Reports
I can’t exactly remember which document says “In-process reports server has better accountability against a standalone reports instance”. I have referred minimum couple of dozen 12c related documents and tens of blogs to setup stuffs. Without arguing whether in-process server or a standalone instance is better to cater the reports services, let me list the activities one have to perform in order to setup
- Create a reports tools instance (Mandatory, if you are planning to use the same box for reports development)
- Create a reports server instance (OPTIONAL, only if you want to host a standalone reports instance)
Start WLST(Weblogic Scripting Tool) console, and execute the below commands one after another (Make sure the node manager & the Weblogic admin server services are already started)
connect("weblogic","password", "localhost:7001") createReportsToolsInstance(instanceName='rptools1', machine='AdminServerMachine') createReportsServerInstance(instanceName='repsvr_MYMACHINENAME', machine='AdminServerMachine') exit()
Once successfully completed, restart the WLS_REPORTS application using the weblogic admin console. Once bitten, twice shy…I always restart the weblogic admin server and other servers to make sure nothing is broken in between…(paranoid I must be)
Restarting the WLS_REPORTS server causes the weblogic server to configure the newly created instances of reports tools and reports instance. A successful completion let you
- Start using the reports builder
- Access the standalone reports server instance
You need minimal configurations for the standalone reports server instance. Just setup the reports (.rdf files) path, disable the security elements and you are online!
Assuming you have already configured the weblogic server components following the previous posts, switch to the reports instance configuration folder
Where repsvr_RAJESH-PC is the name of the reports instance I have created.
You need to modify the “rwserver.conf” file, please check the below image for details
Save the file and restart the WLS_REPORTS server, so that the last modifications are in place!
Now we have to start the reports instance.
Switch to DOMAIN_HOME\bin folder
and run startComponent.cmd repsvr_RAJESH-PC
Please check the below image for details
Once the report server instance starts successfully, you are all set to.
Calling the new instance
That’s all folks, as you could see OHS automatically maps the new reports instance and directs the jobs to it.