SOA OSB Single Managed Server Why?

I am trying to understand why the option exists to run OSB and SOA in the same managed server (same jvm). Can someone answer this question for me please? I inherited a SOA/OSB server and the previous administrator has taken this approach. I have not been able to find any documentation on the subject, it is briefly mentioned in the OSB install guide but with out explanation as to why someone would want to do this http://docs.oracle.com/cd/E23943_01/doc.1111/e15017/configure_osb.htm#BGBDGGBE
Thanks

Troubleshooting Interoperability Between OSB and SOA Suite 10g and 11gR1 [ID 1267207.1]
Should OSB and SOA Suite Run in one single JVM?
To run OSB and SOA Suite in one single JVM, i.e. one single WebLogic Server instance, is very handsome for scenarios that only have low load and low memory requirements. For these development or test systems, OSB and SOA Suite can be set up to run in one of the following topologies:
Both OSB and SOA Suite in one single Admin Server (supported in 11.1.1.4 and upwards).
In a domain with one Admin Server and one single, non-clustered managed server to run OSB and SOA Suite on it (supported in 11.1.1.3 and upwards).
However, this is only recommended and supported for development or test environments.

Similar Messages

EPM 11.1.2.x deployment to single managed server

Hi Gurus,
I have 2 questions:
1) If we install some applications on single port number:9000(deploy to single managed server), after that if we deploy some applications to individual ports. is this installation work?
2) for example we have installed and configured all applications to single managed server:9000. Now can we change this to individual port numbers??
I mean can we configure all application to individual port numbers??
Just asking with curiosity to know about this scenarios.
Thanks,
mady

Hi Pablo,
Hope you are doing good. In Starting of Carrer on Hyperion, JohnGoodwin and Your replies on the Forum was very helpful to me. Nowadays,you are busy i think, and we are not getting more responses from you .
Pablo wrote:
If what you're trying to do is deploy everything to 9000, test that and then deploy everything to its own managed server, the answer is yes you can but you need to re-run the OHS configuration at the end everytime as it will need to update the mod_wl_ohs.conf file to update the ports/# of managed servers.
Pablo
In the response, Can we get any conflict between services if we do reconfigure to the Own managed server.?
(why i am asking this question is, at the time of configuration to single managed server, we get EPM Server Service, then some more services only. But if we do reconfigure to the Own managed server, we will get more services in Services.msc)
I didn't test this yet, just i got this doubt if we do like this what will happens. is it work or not?
Thanks for your valuable time Pablo.
Thanks,
mady

Deploy to single managed server checked and greyed out while performing upgrade to EPM 11.1.2.4

Hi Gurus,
We are trying to upgrade EPM from 11.1.2.2 to EPM 11.1.2.4 and have applied the maintenance release successfully.
Issue:
When we are trying to configure EPM 11.1.2.4 and are providing the same Shared Service database details, at the summary screen, we are not able to uncheck the option "Deploy to Single Managed server" which is checked and is greyed out.
We have tried the following:
1. We updated the HSS_COMPONENT_PROPERTY_VALUE table and updated the PROPERTY_NAME "isCompact" to false.
2. Modified the config.xml file located at EPMSystem/config and epmsystem1/config to remove the property for compactState.
We are still having the issue where we are not able to uncheck the option for Compact Deployment. Any help would be appreciated.
Thanks in advance.

As it is a maintenance release and it deployed as a single managed server then you will not be able to change the deployment type when applying the maintenance release.
There is a procedure to change a deployment type from compact to single managed server that I created as an internal document.
you may want to give it a go but you would need to test this first as this was an in house test that I carried out.
Hyperion Planning - Version 11.1.2.2.300 and later
Information in this document applies to any platform.
Goal
The scenario:
EPM system 11.1.2.3 was configured and deployed as a single managed server compact deployment so that only one JVM was used for all products EPMServer0.
Later on, due to performance issues, the decision was made to go for using a JVM for each product and get rid of the compact deployment.
The administrator went ahead and redeployed the application servers individually into their own JVM.
However everytime the webserver is reconfigured, the weblogicCluster entry in the OHS file mod_wl_ohs has 2 servers, one for EPMSserver running on port 9000 and another server running on the product default port (as if it was being load balanced)
The aim:
It is clear that initial compact deployment has not been cleared from the EPM environment and the aim in this exercise is to clear the registry and the file system so that the compact deployment is removed fromthe EPMenvironment and we are left with the desired configuration Single JVM deployment for earch web application.
Solution
Caution:
Make sure that you take a backup of the following:
- TheFoundation Services database schema backup
- Take a backup of the following folders:
\Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component
\Oracle\Middleware\user_projects\domains\EPMSystem\servers
\Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\servers
Disclaimer:
This was tested in House and it worked for this specific environment and it may not work for your environment. So the suggestion is to test first in a development environment and make sure that you take the appropriate backups in case it does not go according to plan.
Use at your own discretion.
Procedure:
1- Run the epmsys_registry to generate the Registry report
2- Search through the report for the word applicationServerDeployment with a corresponding value of configured and take the ObjectID number down for any entry of applicationServerDeployment that has a value of Configured
i.e:
Instance Tasks Configuration (INSTANCE_TASKS_CONFIGURATION)
Object ID:   e4b3a86a82c26941S32ef81a1455fe48473S7adf
3- use the object ID of each entry you have taken down throughout the Registry HTML Report to manually set it back to Pending using the following procedure:
                Start a command prompt and set the working directory to
                 \Oracle\Middleware\user_projects\epmsystem1\bin
                run the command:
                 epmsys_registry.bat updateproperty #e4b3a86a82c26941S32ef81a1455fe48473S7adf/@applicationServerDeployment=Pending
                Repeat this command for each ObjectID that has its applicationServerDeployment
                 property set to Configured
4- rerun the epmsys_registry.bat to generate the Registry HTML report and search for applicationServerDeployment in the newly generated report to make sure that they are all set to Pending and there none missed (very Important).
5- Search the registry HTML report this time for EPMServer0 which is the default serverName given to the single managed server deployment (there will be multiple entries)
Take note of the first ObjectID entry in the section header: for example
WORKSPACE_WEBAPP (WORKSPACE_WEBAPP)
Object ID:   e4b3a86a82c26941S32ef81a1455fe48473S7bd3
- Start a command prompt and set the working directory to
                 \Oracle\Middleware\user_projects\epmsystem1\bin
- run the command:
                 epmsys_registry.bat view #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
-Note the Parents ID in the output:
For example:
Parent 1
NAME - WORKSPACE_LWA
ID - e4b3a86a82c26941S32ef81a1455fe48473S7bd0
TYPE - LOGICAL_WEB_APP
Parent 2
NAME - HOST:BACHVMPS3TR
ID - e4b3a86a82c26941S32ef81a1455fe48473S7ffe
TYPE - HOST
- Note the single child ID:
For Example:
Child 1
NAME - WebLogic 10
ID - e4b3a86a82c26941S32ef81a1455fe48473S7fd6
TYPE - APP_SERVER
Now run the following command to remove the Link between Parent and child:
epmsys_registry removelink #parentObjectID #childObjectID
In this example that would translate to:
To remove the single child1 link to the WORKSPACE_WEBAPP (#e4b3a86a82c26941S32ef81a1455fe48473S7bd3 ):
epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7bd3 #e4b3a86a82c26941S32ef81a1455fe48473S7fd6
And do the following To remove the link between WORKSPACE_WEBAPP (#e4b3a86a82c26941S32ef81a1455fe48473S7bd3 ) and Parent1 and Parent2:
epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7bd0
#e4b3a86a82c26941S32ef81a1455fe48473S7bd3
epmsys_registry removelink #e4b3a86a82c26941S32ef81a1455fe48473S7ffe
#e4b3a86a82c26941S32ef81a1455fe48473S7bd3
- Now that the link has been removed, delete the WORKSPACE_WEBAPP component using its ObjectID :
epmsys_registry deletecomponent #parentObjectID
In this example:
epmsys_registry deletecomponent #e4b3a86a82c26941S32ef81a1455fe48473S7bd3
- Delete also the Parent representing the WORKSPACE_LWA
epmsys_registry deletecomponent #e4b3a86a82c26941S32ef81a1455fe48473S7bd0
Note:So we have now deleted the WEBAPP and LWA for workspace.
6- Repeat steps in section No 5 for every WEBAPP with EPMServer0
7- Start the Weblogic admin console and login
Then go to the left panel and Expand Environment -> Server
Click on Lock & Edit -> Select EPMServer0 -> click on Delete and confirm
Activate Changes and Log off
8- Stop the weblogic admin console server
9- Go to the following location and delete the folder EPMServer0:
\Oracle\Middleware\user_projects\domains\EPMSystem\servers
Delete also EPMServer0 from the following location:
\Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig\servers
10- Start a command prompt and delete the Windows service that was created for EPMServer0 (if using Microsoft Windows Operating System):
Right click on the service 'OracleHyperion EPM Server - Java Web Application (epmssystem1)' and get its service name i.e: HyS9EPMServer_FOUNDATION1
Run the following command: sc delete HyS9EPMServer_FOUNDATION1
11- Launch the EPMSystem configurator and redeploy the web application server to their own JVM
12- Go to the following location \Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component and rename the file mod_wl_ohs.conf to mod_wl_ohs.conf.old.
13- Copy the unconfigured mod_wl_ohs.conf file from the location C:\Oracle\Middleware\ohs\ohs\conf to the location \Oracle\Middleware\user_projects\FOUNDATION1\httpConfig\ohs\config\OHS\ohs_component
14- Run the EPM System Configurator again and configure the WebServer to reconfigure the OHS configuration file mod_wl_ohs.conf.
Once done then open the mod_wl_ohs.conf file and make sure that there are no servers configured with Port 9000.
15- Start the services and test the workspace

EPM single Managed Server for all applicatoins vs EPM multiple managed servers

Hi Guys
There are two options of setting my managed serves in weblogic
1 - All application comes under single managed server.
2 - Every application have it's own managed server.
(Please correct me if there are other ways to other than this.)
What are the advantages and disadvantages of both?
Regards

Actually the purpose of these purely lies in your usage and env capacity ..
Suppose I have a test env where in I frequently suppose to restart the services , then I will better go for single managed option as I would not like wasting my time in stopping and starting of services .
Note this will have high RAM burden as you would be starting all the service even if you don't need that .
If you are constantly bringing services up and down you want the control of being able to choose what you are restarting. Lets say in your Test environment you want to change the deployment settings of JVM, change the Planning properties, change Essbase Server settings, you hose FDMEE and need to restart.... this list can easily go on ... you want to be able to restart the individual component rather than everything. You cannot accurately test patches in Test, because they don't simulate Prod - so you have to bank on having another pre-prod environment to do all of this in. You cannot tune accurately, because you have no control over the individual web apps.
As Dattatray said " 2. as there is only one window service, RAM and processor consumption will be less"
as JohnGoodwin said "I am not a fan of the single managed server unless it is for low resourced machine, e.g. laptop or POC, it is more trouble than it is worth."
The RAM usage is going to be lower, not higher.

ODI - Multiple Java EE Agents on Single Managed Server

Hello All,
Can we configure more than 1 Java EE Agent on single managed server in ODI? I have configured 1 Java EE agent successfully.
Kindly suggest, if this is possible?
Cheers,
Andy.

A default JEE agent is created when you create domain, which is named as OracleDIAgent.
1. In Studio, duplicate the agent, change its name to genAgent, change the web application context to genagent.
2: Go to datasource of genAgent, drop all datasources.
3: Generate server template. put the jar file under odi\common\templates\wls
4: Deploy this template by update the existing domain. Bring up the config.cmd, choose update existing domain.
5: Update the domain using the template that just generated.
Go through the Configuration wizard. (I did not modify anything or configure anything here).
6: The wizard will give information says the deployment was successful.
7: Bring up the admin server and ODI_server1.

Deploy() and undeploy() for a single managed server do not work properly

i tried undeploying an application using the following command undeploy('app_name','managed_server1') which in the WebLogic documentation states that this can undeploy the application from the single managed server, but this untargets the application from ALL managed servers.
Is the command being invoked properly for a single managed server deployment?
For the deploy() command, the same issue exists but for deployments. It either deploys to a single vm but cannot be later updated to be re-targeted.

hi,
Is managed servers are in cluster or stand-alone servers? pls check it properly,if so there is no chance to undeploy the application from all servers even if try to undeploy from onr server.
regards,
abhi

Could not create SOA as a Managed server

Hi
I Installed Oracle SOA suite and then I created the Weblogic domain. But the SOA server is not installed as a separate Managed server. I could not find anywhere create as a Managed server option while creating domain or installation.
The strange thing is that when I install BAM or OSB they appear as a Manged servers on Weblogic console but not SOA as I following the same process.
Please help me to figure out this problem.
Thank you,
Nasir

Hi,
As shown by your screenshots, your soa managed server is not started, that's the main reason you cannot see the "SOA" folder on EM.
EM is just a administration console and is per default deployed on the admin server. So it's normal that EM can be up and running while the "soa_infra", that should be target to the managed server, is down (since the managed server is not launched).
And no, when you launch your weblogic server with "startWeblogic.cmd" for example, it will only start the admin server of the domain.
If you want to launch your soa managed server you need to :
- use the "startManaged*.cmd" (don't recall the exact name) for a manual launch. Don't forget to give the name of the managed server you want to start as an argument of the script.
- register it as a service for an automated launch.
regards,
mathieu

Error while starting Soa Managed server on weblogic11g

Hi All,
I am facing one issue while starting the soa managed server on weblogic11g.
it gives error like :
"<Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
java.lang.NoClassDefFoundError: java/lang/IOException.
java.lang.NoClassDefFoundError: java/lang/IOException
What can be done to get over this issue & start the soa server ???
Thanks & Regards,
Nupur

Hi,
Full stack trace of log is :
<Apr 12, 2011 7:04:19 AM IST> <Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
java.lang.NoClassDefFoundError: java/lang/IOException.
java.lang.NoClassDefFoundError: java/lang/IOException
     at jrockit.ext.epoll.EPoll.epollCtl0(Native Method)
     at jrockit.ext.epoll.EPoll.epollEnableOneshot(EPoll.java:87)
     at weblogic.socket.EPollSocketMuxer.read(EPollSocketMuxer.java:84)
     at weblogic.socket.BaseAbstractMuxableSocket.dispatch(BaseAbstractMuxableSocket.java:302)
     at weblogic.socket.MuxableSocketDiscriminator.dispatch(MuxableSocketDiscriminator.java:177)
     Truncated. see log file for complete stacktrace
>
<Apr 12, 2011 7:04:41 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'soademoDatabase1' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:290)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
     Truncated. see log file for complete stacktrace
Caused By: weblogic.common.ResourceException: ORA-28001: the password has expired
     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:479)
     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:173)
     at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1193)
     at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1117)
     at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:244)
     Truncated. see log file for complete stacktrace
Apr 12, 2011 7:05:49 AM IST> <Error> <Socket> <BEA-000405> <Uncaught Throwable in processSockets
java.lang.NoClassDefFoundError: java/lang/IOException.
java.lang.NoClassDefFoundError: java/lang/IOException
     at jrockit.ext.epoll.EPoll.epollCtl0(Native Method)
     at jrockit.ext.epoll.EPoll.epollEnableOneshot(EPoll.java:87)
     at weblogic.socket.EPollSocketMuxer.read(EPollSocketMuxer.java:84)
     at weblogic.socket.BaseAbstractMuxableSocket.dispatch(BaseAbstractMuxableSocket.java:302)
     at weblogic.socket.MuxableSocketDiscriminator.dispatch(MuxableSocketDiscriminator.java:177)
     Truncated. see log file for complete stacktrace
<Apr 12, 2011 7:05:53 AM IST> <Warning> <oracle.sdp.messaging.driver.base> <SDP-26024> <Registration of driver Email-Driver did not complete; will retry periodically until messaging server responds.>
<Apr 12, 2011 7:05:56 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'FtpAdapter' due to error weblogic.application.ModuleException: weblogic.connector.exception.RAException: Jndi Name is null or empty..
weblogic.application.ModuleException: weblogic.connector.exception.RAException: Jndi Name is null or empty.
     at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:224)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
     Truncated. see log file for complete stacktrace
No this is not a clustered environment.
yeah but under domains there are two domains we have created.
i.e. domains/ domain1 domain2
both are having soa servers as managed server.
in one domain soa is up but in domain2 it is not getting up causing above errors while starting.
FYI : It is causing problem now only.. before this , soa server on both the server have been up & running simultaneously.
Regards,
Nupur

OSB managed server not starting

I am facing following issue in my one osb managed server and osb first managed server is working fine.
Error :
<Feb 19, 2013 1:37:32 PM SGT> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean ALSB1354685722852. Error - weblogic.management.DeploymentException: error in opening zip file with : /usr/appl/softwares/user_projects/domains/OSB/sbgen/_ALSB_1354685722852.ear.
weblogic.management.DeploymentException: error in opening zip file with : /usr/appl/softwares/Middleware_Home_IF/user_projects/domains/OSB/sbgen/_ALSB_1354685722852.ear
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:89)
     Truncated. see log file for complete stacktrace
Caused By: java.io.IOException: error in opening zip file with : /usr/appl/softwares/user_projects/domains/OSB/sbgen/_ALSB_1354685722852.ear
     at java.util.zip.ZipFile.open(Native Method)
     at java.util.zip.ZipFile.<init>(ZipFile.java:150)
     at java.util.jar.JarFile.<init>(JarFile.java:149)
     at java.util.jar.JarFile.<init>(JarFile.java:113)
     at weblogic.utils.jars.JarFileDelegate.<init>(JarFileDelegate.java:32)
     Truncated. see log file for complete stacktrace
>
Please help , second node is starting in admin mode.
Thanks,
Abhishek

Hi, thanks, it will make my system is in running mode but while next restart it will go down again in admin mode.
actually i have a ear file in sbgen folder (containing all meta data) . its not able to load that particular ear file.
I tried to change that file with other node but no luck.
please help if you have any idea.
Regards,
Abhishek

Nodemanager does not restart managed server after Linux OS reboot

Running Linux 2.6.18, Sun JDK 1.6.0_14, and WebLogic 10.3, we have a correctly functioning nodemanager watching a single managed server. If I kill -9 the managed server, the nodemanager fires up a new one immediately. If, however, we reboot the box, the nodemanager will start cleanly and will not start the managed server. It appears to believe the node should remain down and reports its status as UNKNOWN.
I've seen where this is a known problem on Windows boxes, easily gotten around by supplying the -Xrs parameter to the startup parms for the managed server. (Section 5 of the general nodemanager config doc.) I don't see, however, where there's an equally clean solution for Linux.
Things I've tried:
+ When I set the server to DEBUG, it shows zero sign of receiving a shutdown signal. It's dumping loads of cluster messages, etc, into the log and then suddenly the log just ends so it's dying via kill -9. If the nodemanager is still running at that time, it might try to restart the managed server and log it somewhere as permanently failed.
+ The nodemanager only logs to INFO level, and logs no evidence of deciding to leave the node down. (DEBUG is an invalid LogLevel, so that's all I've got.)
+ A restart signal sent from our AdminServer (on another Linux box) successfully starts the managed node through the nodemanager. Nothing unusual occurs or is logged.
Things I'm curious about:
+ Is there some way to see in what state the nodemanager believes the managed server to be?
+ Is there some value in some doc somewhere that might say the server should not be restarted?
+ Is there not a log of NodeManager client actions? I don't see anything in domain.log or AdminServer.log except when the NM is down.
Thanks,
Kevin
ListenPort=5556
ListenBacklog=50
SecureListener=true
AuthenticationEnabled=true
NativeVersionEnabled=false
CrashRecoveryEnabled=true
JavaHome=/appl/java/jre
StartScriptEnabled=false
StopScriptEnabled=false
StartScriptName=startWebLogic.sh
StopScriptName=
LogFile=/appl/bea/wlserver_10.3/common/nodemanager/logs/nodemanager.log
LogLevel=INFO
LogLimit=0
LogCount=1

can you set NativeVersionEnabled to true. We have faced this in windows which was fixed by changing this property. Some notes from that issue:
Faced this interesting issue in Windows 2008 environment. Managed Servers were started by node manager and it was expected that on a system restart after a crash, the node manager will restore the state of the managed servers to the state it was before the crash. Node Manger was configured to run as a windows service. Hence it started after the server restart. But the individual managed servers were not getting started. Interestingly, for the managed servers started by the node manager there were no <Managed_Server_Name>.lck file in the <Server>/data/NodeManger folder.
To fix this always set the following properties in the nodemanager.properties on the node maager home directory.
CrashRecoveryEnabled=true /* This by default is set to false. This needs to be turned for auto restart after crash to work */
NativeVersionEnabled=true /* This is by default set to true and it should be set as such. If you turn this off on platforms for which weblogic provide native JNI libraries ( e.g. as in Windows 2008) then this wont create the .lck file and hence node manager wont restart the managed server after the crash.
Note: As per official documentation .lck files are required for weblogic node managers to do auto restart after system crash
From Official documentation:
After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.
If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
*/

Problem while starting managed server using nodemanager

Hi everyone,
I am using WLST of Weblogic server 10.3, to automate the creation of domain, managed servers,JDBC,JMS resources etc.. and trying to start the managed servers using node manager. I have an environment which contains few domains. All the domains are using machine named "X".
Now, i am creating the same machine in my domain WLSTDomain. I have the following doubts.
Is there a way to check whether the nodemanager(of X) is already running.
If there is a way to check that, how can we start the managed servers in WLSTDomain using that existing nodemanager.

1. yes you can check if the nodemanage is running using the following ways.
For linux env:-
a. Check if the JAVA process for nodemanager is running ps -ef | grep java and see the nodemanager process else /usr/sbin/lsof -i:$port (port of nodemanager).
b. Login to Admin Console --> Environment --> Machines --> Click on Machines --> Nodemanager --> Monitoring will give you nodemanager status from Admin console.
c. use nm() command with WLST
Example:
wls:/mydomain/serverConfig> nm()
Currently connected to Node Manager that is monitoring the domain "mydomain"
wls:/mydomain/serverConfig> nm()
Not connected to any Node Manager
wls:/mydomain/serverConfig>
To see if WLST connects to nodemanager or not?
help('nmLog') --> to check the nm logs
2. To start the nodemanager using WLST here are the commands
Example:
For single managed Server
wls:/mydomain/serverConfig> start('myserver', 'Server', block='false')
Starting server 'myserver' ...
The server 'myserver' started successfully.
wls:/mydomain/serverConfig>
For Cluster
wls:/mydomain/serverConfig> start('mycluster', 'Cluster')
Starting the following servers in Cluster, mycluster: MS1, MS2, MS3...
All servers in the cluster mycluster are started successfully.
wls:/mydomain/serverConfig>

Multiple Managed Server for Hyperion Planning in 11.1.2.2

Hi All,
I was going through some online documnetation/new features on Hyperion Planning 11.1.2.2 and came to know that from an architecture standpoint we can now have multiple Planning Managed Servers in a cluster thereby making it truly Highly Available.
I have done a standard deployment and can see a cluster for Planning with a single managed server Planning0 in weblogic admin console.
Can any one please provide me insight/documnetation as what steps needs to be done to create multiple planning managed server in 11.1.2.2.
Thanks
Perwez

Thanks John.
I was not looking for something which is scaling out Hyperion Planning(via load balancer)/Horizontal clustering.
But was looking for some thing like Vertical clustering(multiple JVMs/nodes of Hyperion Planning within a single planning server) which was applicable in 11.1.1.3.
Came to know that with 11.1.2.2 vertical clustering not more supported.
Thanks

OIM 11gR2 : Problem while starting managed server

Hello Experts,
I ran config.sh in order to extend my schema to include APM (Authorization Policy Manager) in OIM 11gR2.
After that i took a restart of the servers. When i am trying to start the managed servers they're not starting in the RUNNING mode. Instead they're starting in the ADMIN mode.
The logs are showing the following error :
Internal Exception: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
Kindly help me out.

1. yes you can check if the nodemanage is running using the following ways.
For linux env:-
a. Check if the JAVA process for nodemanager is running ps -ef | grep java and see the nodemanager process else /usr/sbin/lsof -i:$port (port of nodemanager).
b. Login to Admin Console --> Environment --> Machines --> Click on Machines --> Nodemanager --> Monitoring will give you nodemanager status from Admin console.
c. use nm() command with WLST
Example:
wls:/mydomain/serverConfig> nm()
Currently connected to Node Manager that is monitoring the domain "mydomain"
wls:/mydomain/serverConfig> nm()
Not connected to any Node Manager
wls:/mydomain/serverConfig>
To see if WLST connects to nodemanager or not?
help('nmLog') --> to check the nm logs
2. To start the nodemanager using WLST here are the commands
Example:
For single managed Server
wls:/mydomain/serverConfig> start('myserver', 'Server', block='false')
Starting server 'myserver' ...
The server 'myserver' started successfully.
wls:/mydomain/serverConfig>
For Cluster
wls:/mydomain/serverConfig> start('mycluster', 'Cluster')
Starting the following servers in Cluster, mycluster: MS1, MS2, MS3...
All servers in the cluster mycluster are started successfully.
wls:/mydomain/serverConfig>

WHAT IS ORACLE MANAGEMENT SERVER (OMS)

Hi,
every one,
what is OMS (ORACLE MANAGEMENT SERVER ) ,
Why is it necessary
plz reply me
regards rehan

It functions as a middle tier beteen 'Oracle Intelligent Agents' and management consoles,where DBAs view and control their OEM domain.
You can refer the following for more details:
http://www.lc.leidenuniv.nl/awcourse/oracle/em.920/a96673/ch1.htm

Starting One of managed server in cluster SOA Suite(11.1.1.4.0) fails

Oracle Soa Suite (11.1.1.4.0)
Weblogic (10.3.4).
Operating System : Red Hat Linux 5.5
I have installed and configured Oracle Soa Suite (11.1.1.4.0) with 1 Admin Server(host1) and 2 Managed Severs (host1,host2). Deployed wsm-pm (cluster), wsm*.*.seedpolicies* (cluster).
I was able to start the Admin Server , Started the Node Managers in both (host1) & (host2). I made sure to run the pack & unpack utility from $ORACLE_HOME/oracle_common/common/bin folder while i moved from one host to another.
Also i ran $ORACLE_HOME/oracle_common/common/bin/./setNMProps.sh on both host1 & host2. Made sureto check on both the nodemanager running on host1 & host2 has "StartScriptEnabled=true".
Now when i start Managed Server 1 in host1(Admin server run on same host) -- It started just fine.
When i Started Managed Server 2 in host2 , it started with ADMIN State and i tailed the logs and found the exception below.
I also made sure the os level permissions are not an issue here. I can see those artifacts in the folder structure mentioned and available. So not sure what am I missing here.
Any help solving this exception would be appreciated.
<Feb 18, 2011 3:09:50 PM PST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "JRF Startup Class", java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup
java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 18, 2011 3:09:50 PM PST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "JPS Startup Class", java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 18, 2011 3:09:50 PM PST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "ODL-Startup", java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 18, 2011 3:09:50 PM PST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "AWT Application Context Startup Class", java.lang.ClassNotFoundException: oracle.jrf.AppContextStartup
java.lang.ClassNotFoundException: oracle.jrf.AppContextStartup
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 18, 2011 3:09:50 PM PST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "JMX Framework Startup Class", java.lang.ClassNotFoundException: oracle.as.jmx.framework.wls.spi.StartupListener
java.lang.ClassNotFoundException: oracle.as.jmx.framework.wls.spi.StartupListener
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 18, 2011 3:09:50 PM PST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "Web Services Startup Class", java.lang.ClassNotFoundException: oracle.j2ee.ws.server.WebServiceServerStartup
java.lang.ClassNotFoundException: oracle.j2ee.ws.server.WebServiceServerStartup
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 18, 2011 3:09:50 PM PST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "JOC-Startup", java.lang.ClassNotFoundException: oracle.ias.cache.Startup
java.lang.ClassNotFoundException: oracle.ias.cache.Startup
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>
<Feb 18, 2011 3:09:50 PM PST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "DMS-Startup", java.lang.ClassNotFoundException: oracle.dms.wls.DMSStartup
java.lang.ClassNotFoundException: oracle.dms.wls.DMSStartup
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Edited by: karpra on Feb 18, 2011 3:22 PM

Ravi,
Thanks for your reply.
Yes I did pretty standard stuff on pack and unpack. I did the same in SOA Suite 11gR1 PS1 and it works fine.
I tried to do the same with PS2 which had issues clustering the osb. But soa suite ran fine using nodemanager and startManagedServer.
I am trying the same procedure and it failed in 11.1.1.4.0 version.
When i checked the classpath between the managed server on hosta and hostb it looks different.
hosta
[email protected]_11.1.1.4.0_oracle_common_ORACLE_HOME/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar:@oracle.integration.soainfra_11.1.1.4.0_Oracle_SOA1_ORACLE_HOME/soa/modules/user-patch.jar:@oracle.integration.soainfra_11.1.1.4.0_Oracle_SOA1_ORACLE_HOME/soa/modules/soa-startup.jar::@oracle.osb.top_11.1.1.4.0_Oracle_OSB1_ORACLE_HOME/lib/osb-server-modules-ref.jar:/data/u01/app/oracle/Middleware/patch_wls1034/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/data/u01/app/oracle/jrockit-jdk1.6.0_20-R28.1.0-4.0.1/lib/tools.jar:/data/u01/app/oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/data/u01/app/oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/data/u01/app/oracle/Middleware/modules/features/weblogic.server.modules_10.3.4.0.jar:/data/u01/app/oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/data/u01/app/oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/data/u01/app/oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:@oracle.as.jrf_11.1.1.4.0_oracle_common_ORACLE_HOME/soa/modules/commons-cli-1.1.jar:@oracle.as.jrf_11.1.1.4.0_oracle_common_ORACLE_HOME/soa/modules/oracle.soa.mgmt_11.1.1/soa-infra-mgmt.jar:@oracle.as.soa.top_11.1.1.4.0_Oracle_SOA1_ORACLE_HOME/soa/modules/oracle.soa.common.adapters_11.1.1/oracle.soa.common.adapters.jar:@oracle.sdp.messaging_11.1.1.4.0_Oracle_SOA1_ORACLE_HOME/communications/modules/usermessaging-config_11.1.1.jar:@oracle.as.jrf_11.1.1.4.0_oracle_common_ORACLE_HOME/modules/oracle.xdk_11.1.0/xsu12.jar:/data/u01/app/oracle/Middleware/modules/features/weblogic.server.modules.xquery_10.3.1.0.jar:@oracle.integration.soainfra_11.1.1.4.0_Oracle_SOA1_ORACLE_HOME/soa/modules/db2jcc4.jar:/data/u01/app/oracle/Middleware/user_projects/domains/ofmPrdDomain/config/soa-infra:@oracle.integration.soainfra_11.1.1.4.0_Oracle_SOA1_ORACLE_HOME/soa/modules/fabric-url-handler_11.1.1.jar:@oracle.integration.soainfra_11.1.1.4.0_Oracle_SOA1_ORACLE_HOME/soa/modules/quartz-all-1.6.5.jar:@oracle.integration.soainfra_11.1.1.4.0_Oracle_SOA1_ORACLE_HOME/soa/modules/oracle.soa.fabric_11.1.1/oracle.soa.fabric.jar:@oracle.integration.soainfra_11.1.1.4.0_Oracle_SOA1_ORACLE_HOME/soa/modules/oracle.soa.fabric_11.1.1/fabric-runtime-ext-wls.jar:@oracle.integration.soainfra_11.1.1.4.0_Oracle_SOA1_ORACLE_HOME/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar:@oracle.integration.soainfra_11.1.1.4.0_Oracle_SOA1_ORACLE_HOME/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar:@oracle.as.jrf_11.1.1.4.0_oracle_common_ORACLE_HOME/modules/oracle.jrf_11.1.1/jrf.jar:@oracle.osb.top_11.1.1.4.0_Oracle_OSB1_ORACLE_HOME/lib/version.jar:@oracle.osb.top_11.1.1.4.0_Oracle_OSB1_ORACLE_HOME/lib/alsb.jar:@oracle.osb.top_11.1.1.4.0_Oracle_OSB1_ORACLE_HOME/3rdparty/lib/j2ssh-ant.jar:@oracle.osb.top_11.1.1.4.0_Oracle_OSB1_ORACLE_HOME/3rdparty/lib/j2ssh-common.jar:@oracle.osb.top_11.1.1.4.0_Oracle_OSB1_ORACLE_HOME/3rdparty/lib/j2ssh-core.jar:@oracle.osb.top_11.1.1.4.0_Oracle_OSB1_ORACLE_HOME/3rdparty/lib/j2ssh-dameon.jar:@oracle.osb.top_11.1.1.4.0_Oracle_OSB1_ORACLE_HOME/3rdparty/classes:@oracle.osb.top_11.1.1.4.0_Oracle_OSB1_ORACLE_HOME/lib/external/log4j_1.2.8.jar:/data/u01/app/oracle/Middleware/user_projects/domains/ofmPrdDomain/config/osb:/data/u01/app/oracle/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/data/u01/app/oracle/Middleware/wlserver_10.3/server/lib/xqrl.jar
hostb
CLASSPATH=/data/u01/app/oracle/Middleware/oracle_common/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar:/data/u01/app/oracle/Middleware/Oracle_SOA1/soa/modules/user-patch.jar:/data/u01/app/oracle/Middleware/Oracle_SOA1/soa/modules/soa-startup.jar::/data/u01/app/oracle/Middleware/Oracle_OSB1/lib/osb-server-modules-ref.jar:/data/u01/app/oracle/Middleware/patch_wls1034/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/data/u01/app/oracle/jrockit-jdk1.6.0_20-R28.1.0-4.0.1/lib/tools.jar:/data/u01/app/oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/data/u01/app/oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/data/u01/app/oracle/Middleware/modules/features/weblogic.server.modules_10.3.4.0.jar:/data/u01/app/oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/data/u01/app/oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/data/u01/app/oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/data/u01/app/oracle/Middleware/oracle_common/soa/modules/commons-cli-1.1.jar:/data/u01/app/oracle/Middleware/oracle_common/soa/modules/oracle.soa.mgmt_11.1.1/soa-infra-mgmt.jar:/data/u01/app/oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.common.adapters_11.1.1/oracle.soa.common.adapters.jar:/data/u01/app/oracle/Middleware/Oracle_SOA1/communications/modules/usermessaging-config_11.1.1.jar:/data/u01/app/oracle/Middleware/oracle_common/modules/oracle.xdk_11.1.0/xsu12.jar:/data/u01/app/oracle/Middleware/modules/features/weblogic.server.modules.xquery_10.3.1.0.jar:/data/u01/app/oracle/Middleware/Oracle_SOA1/soa/modules/db2jcc4.jar:/data/u01/app/oracle/Middleware/user_projects/domains/ofmPrdDomain/config/soa-infra:/data/u01/app/oracle/Middleware/Oracle_SOA1/soa/modules/fabric-url-handler_11.1.1.jar:/data/u01/app/oracle/Middleware/Oracle_SOA1/soa/modules/quartz-all-1.6.5.jar:/data/u01/app/oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.fabric_11.1.1/oracle.soa.fabric.jar:/data/u01/app/oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.fabric_11.1.1/fabric-runtime-ext-wls.jar:/data/u01/app/oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar:/data/u01/app/oracle/Middleware/Oracle_SOA1/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar:/data/u01/app/oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/data/u01/app/oracle/Middleware/Oracle_OSB1/lib/version.jar:/data/u01/app/oracle/Middleware/Oracle_OSB1/lib/alsb.jar:/data/u01/app/oracle/Middleware/Oracle_OSB1/3rdparty/lib/j2ssh-ant.jar:/data/u01/app/oracle/Middleware/Oracle_OSB1/3rdparty/lib/j2ssh-common.jar:/data/u01/app/oracle/Middleware/Oracle_OSB1/3rdparty/lib/j2ssh-core.jar:/data/u01/app/oracle/Middleware/Oracle_OSB1/3rdparty/lib/j2ssh-dameon.jar:/data/u01/app/oracle/Middleware/Oracle_OSB1/3rdparty/classes:/data/u01/app/oracle/Middleware/Oracle_OSB1/lib/external/log4j_1.2.8.jar:/data/u01/app/oracle/Middleware/user_projects/domains/ofmPrdDomain/config/osb:/data/u01/app/oracle/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/data/u01/app/oracle/Middleware/wlserver_10.3/server/lib/xqrl.jar
I noticed the jar files in both classpath are same , but its denoted different in hosta which runs fine like "@oracle....*.jar" but in hostb its denoted as /data/..../*.jar.
Not sure if something is missing or should be run between them to work fine.

SOA OSB Single Managed Server Why?

Similar Messages

Maybe you are looking for