Weblogic 12.2: AdminServer overwrite by restarting all your changes in the OHS mod_wl_ohs.conf file

For using Forms and Reports in Weblogic 12.2 with OHS server we changed Oracle HTTP Server Configuration in the $DOMAIN_HOME/config/fmwconfig/components/OHS/instances/ohs1/mod_wl_ohs.conf according the Oracle Documentation. But after the restarting of AdminServer the configuration file was always overwritten with default content and all our changes were gone.

By the starting of AdminServer we get following lines in the logs:

 NMProcess: Mär 24, 2017 7:51:15 AM oracle.ohs.plugin.nodemanager.OhsReplicationPlugin commit

 NMProcess: INFORMATION: Instanz ohs1 wird aktualisiert

We found, that the content of above mod_wl_ohs.conf file will be overwritten with the content of same named file from $DOMAIN_HOME/config/fmwconfig/components/OHS/ohs1 directory.

So for changes in the OHS configuration you need to edit only the file $DOMAIN_HOME/config/fmwconfig/components/OHS/ohs1/mod_wl_ohs.conf and copy it into the instance/ohs1 directory.



New feature for starting of Node Manager with WLST in Weblogic 12.2: waiting for successful connection.

For starting of the Weblogic infrastructure  our customer used a WLST script. The script looks like this:

startNodeManager(NodeManagerHome=<nmHome> ListenPort=5556,ListenAddress=localhost)


First step is the starting of the node manager. The node manager process needs some time before the listener on the port 5556 is active. The “some time” is depend on several factors and the waiting of 60 sec can be not enough for the starting of the node manager.  In this case the following connection to the node manager (nmConnect) will be fail and all components of the Weblogic infrastructure (except Node Manager:-) ) remain down. For the automatically start of the Weblogic server after an unplanned rebound of the system it’s not optimal solution.  Oracle understood the problem too and extended the startNodeManager procedure in the version with the following parameters:

block—Specifies whether WLST should block until it successfully connects to Node Manager or fails to connect within the specified timeout.

    nmConnectOptions—When block is true, use this argument to specify a list of Node Manager connection options.

    timeout—The number of milliseconds to wait for Node Manager to connect.

With this extension we can wait for successful connection to the Node Manager by starting and you don’t need the sleep() command anymore. Start node manager command will be looks like this (the blue marked parameters are the nmConnect parameters):

                  domainName= 'MYDOMAIN')

Now only if the connection to the node manager is successful, the modified script starts Admin Server and other in script defined components.

Oracle Reports: REP-56133: access is denied to write to the specified location

Last weeks I had a new challenge for me. Migration of a Forms & Reports Application to Weblogic Server version 12c. They are enough documentation about installation and configuration of Forms & Reports (I used very good Installation step-by-step manual written by Borys Neselovskyi ). In my blog I will describe only the problems encountered by the migration.

The first one: REP-56133 error by report generating.

Application: The migrated application include a forms application, batch jobs and uses standalone report server for reports generating and. The batch Jobs generate Reports in for the jobs defined output subdirectories of the directory /reports/output. After the migration we got a “REP-56133: access is denied to write to the specified location” error by report generating. In the current Reports version you need to explicit allowing access on the non-default directories for reading and writing. The solution is the adding the following text lines into the standalone server configuration file $DOMAIN_HOME/config/fmwconfig/components/ReportsServerComponent/<Rep.Serv.>/rwserver.conf




Note: the downloaded Report Version ( have a bug, if you are using wildcards for folder access (/reports/output/*). Wildcards don’t work and you get the error REP-56133 message. For solving this problem you need to install the Oracle Report Patch 22334822.