Oracle Enterprise Manager(em) allows you to configure, re-configure multiple elements for Oracle forms and reports repositories as well as other deployed applications.
EM is the GUI tool provided by Oracle to configure, say, look and feel for your forms instance. Instead of manually editing formsweb.cfg, default.env, registry.dat files, using the GUI you can configure the elements related those whole configuration files, to say the least.
A default installation of Weblogic 10.3.6 does include Oracle Enterprise Manager, however if you created a service for the Weblogic Admin Server using installSvc.cmd at later stages to start the Weblogic Admin Server, most probably the Enterprise Manager will not start automatically as JAVA classpath variable misses out certain elements, thus throwing the error
“Error java.lang.ClassNotFoundException: oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener
Message icon – Warning Errors were encountered while performing this operation.”
After going through a number of OTN discussions, we managed to come up with a solution! by including “setDomainEnv.cmd” within installSvc.cmd batch file.
Please note, if you already created a windows service for Weblogic Admin Server, you must delete the service prior creating a new service. Once the service is gracefully stopped, go to elevated command prompt(Windows 8/ Windows Server 2008 Rx) and type
SC DELETE “beasvc yourdomain_AdminServer”
Refresh the Services.msc console and make sure the service is deleted.
Now backup your installSvc.cmd file
We will modify the installSvc.cmd file (Location: example, D:\WebLogic\Middleware\wlserver_10.3\server\bin) like following (use a decent text editor like Notepad++ )
The following are the default entries you would find with “installSvc.cmd” file
@echo off SETLOCAL set WL_HOME=D:\WebLogic\Middleware\wlserver_10.3 call "%WL_HOME%\common\bin\commEnv.cmd"
Which we will modify like following
@echo off SETLOCAL set WL_HOME=D:\WebLogic\Middleware\wlserver_10.3 set ENV_HOME=D:\WebLogic\Middleware\user_projects\domains\appsdomain\bin call "%WL_HOME%\common\bin\commEnv.cmd" call "%ENV_HOME%\setDomainEnv.cmd"
Now go to folder, where you have created the .cmd file(s) for creating Windows services for
- Admin Server Console
In our case we created all those “.cmd” files here
Now from the elevated command prompt
>InstallWindowsService_AdminServer.cmd (You can create the .cmd file with any name, we made it pretty descriptive for future references)
You may refer to our previous post, explaining how to install Weblogic Server 10.3.6 & Forms/Reports 11g for detailed explanation about creating Windows Services for Weblogic components.
Once the service is created, start it. Login to the console and check the status of “em” under deployments.
If the State is “Active” and Health is “OK”, your Enterprise manager is up and running. You can try to access the Enterprise manager from http://localhost:7001/em
You should provide the same credentials for the Weblogic Admin Console to login with EM.
From the EM Console, as said above, you can configure many parameters for Forms and Reports.
Even though you have managed to “fix” the EM access problem, there could be another issue, once after this exercise. You may not able to access the Forms or Report Server, though the Weblogic console shows them as running with Health being “Ok”
Stop the OPMN processes manually, and restart them and try again.
From elevated command prompt (if you haven’t sourced the environment variable for OPMN, change the working directory to, example: D:\WebLogic\Middleware\asinst_1\bin>)
- stop OPMN processes by issuing “opmnctl stopall”
- Check the status of the OPMN by issuing “opmnctl status”
- Wait until all the processes are stopped
- then restart the OPMN processes by issuing “opmnctl startall”
- Check the status and make sure all the processes are with a status “Alive”
That’s all guys. Hope you enjoyed our post.