SOA and OWSM in separate managed servers

Can someone please provide the pros and cons of separating SOA and OWSM into separate managed servers for a production environment. Also are there instances where customers are running OWSM in its own domain ?
Thanks-

A separate managed server requires more memory.
We do not use separate server.
EDG implements a separate server.
Any other thaughts on this?

Similar Messages

How to Separate Management Servers for Ease of Administration?

Hello,
I am fairly new to SCOM, though have been charged with creating a monitoring solution for a particular group of customers and integrating it as far as possible into our existing corporate SCOM implementation, so any help, tips and so on would be greatly
appreciated.
The customer monitoring requirements will be very different to those of our fairly standard corporate environment - we will need to monitor very different technologies, with some systems sat in different domains or a DMZ. Our central servicedesk will still
need to monitor and action alerts and events for both environments as seamlessly as possible.
At the same time, I would like to separate the environments as the configuration of the management servers for the customer environment will be quite different from our corporate one, and I want to avoid having to make changes to all our corporate servers
every time I need to change something on the customer environment - so things like management pack installs, certificate admin, static DNS config and so on.
How would I go about this please? Would it be better to create a separate management group, with servers dedicated to the customer environment, then connect this to the corporate management group so that the servicedesk can still monitor it, or is there
another way of doing it? Perhaps using resource pools? Time will be a factor here, though ultimately the goal is ease of administration going forward.
Thanks

Using resource pools will not allow you to separate configuration such as MP installs, security, etc. as they are all part of the same management group. From Technet, "A resource pool is a collection of management servers used to distribute
work amongst themselves and take over work from a failed member." If configuration needs to be completely separate from the base configuration perspective, you could use separate connected management groups.
Another option is to separate the configuration within the management group. For example, if you need to monitor SQL computers in your corp environment but not the customer environment, simply create a group containing customer computers and override
the SQL discovery. This applies to other technologies as well. You can even group computers by environment (corp/customer) by using reg key attributes like Kevin Holman describes here: (While my account is being verified
I can't post links but you can search "Creating custom dynamic computer groups based on registry keys on agents"). If you are familiar with MP authoring, you could create a new MP with a new Windows Computer based class instead of extending
the Windows Computer class. From a capabilities perspective, you can certainly monitor corporate, customer, DMZ, and other domains in the same management group. If the domain is untrusted or in the case of the DMZ, workgroups computers, you can
utilize gateway servers with certificate authentication which will be configured for each domain/dmz gateway.
Ease of administration is a tricky concept here...if you utilize separate management groups, administration will have to be handled completely separate in 2 separate consoles. If there are separate SCOM admins per management group, this is
of no issue, but if 1 team/person is managing both, this can be difficult. Alternatively, there will be some up front work to using groups to separate the environments using groups, discoveries, etc.

Administration vs Managed Servers

We are preparing to upgrade from WLS5.1 to WLS8.1 and I am having a problem with
the recommendation that the typical production environment have an administration
server and one (or more) managed servers.
In our environment, we host applications for multiple customers. Currently, each
of these customers has a separate instance of WLS5.1 running. In many cases, the
connection pools have the same name between instances, but with different userids/passwords.
In the conversion to 8.1, I have been debating having a separate domain for each
customer application versus a single domain with a separate managed server for
each customer. The single domain has many desirable features, but it does not
provide for the multiple userid /passwords for a connection pool. The separate
domain per customer eliminates the connection pool issue, but essentially doubles
the number of WLS servers (1 admin and 1 managed) for each customer.
Even though BEA recommends a separate admin server and managed server, in reality,
how important is this? Will I cause myself problems in the future if I choose
to run a combined admin and managed server?
Thanks for any thoughts on this subject.

Thanks David. As God as my witness, the tech seriously told me that they all use the same JVM. Then I got seriously confused, like I was an idiot and didn't understand what a JVM was and I started second-guessing myself. The whole conversation was very strange and yes, there was definitely a language barrier and I'm guessing I just wasn't being clear enough...I don't know...all I know is I walked away from the phone call in worse shape then when I first opened the ticket.
At any rate, do you have recommendations for admin server ram? I know there are performance tuning tools to help us figure out the optimum settings for our managed server, and I plan on implementing them...but going back to the ram for the Admin server, versus managed server...is there a recommended way of specifying different heap size for the managed servers? Is the recommended way to set the the -Xms and -Xmx settings via the 'Arguments' field on Environment > Servers > serverName > Configuration > Server Start tab via the admin console?
Thanks again for your quick reply!
Cheers,
rlb

Future support for APPV Management Servers

I have heard rumors that APPV is moving away from the separate Management servers and future releases will only support SCCM integration. Is this a true roadmap ?

I don't have any insider information BUT I have not heard this from anybody. I'd lean on the side of not believing this. It's still an ok solution for small Enterprise.
Considering the announcement yesterday, what the future holds for App-V should be very interesting.
PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog:
rorymon.com Twitter: @Rorymon

Cisco Prime Infrastructure 2.1 can't add Cisco ISE 1.2 to "External Management Servers"

Hi all,
I'm trying to add Ciso ISE 1.2 (1.2.0.899 with version 13 patch) servers (primary and secondary) as "External Management Servers" in Cisco PI 2.1 (2.1.0.0.87) but there appears such message indicating that ISE server is not reachable:
The weird thing is that ISE servers are reachable from PI and vice-versa (I can ping each other from their CLIs)
There were added ISE servers to PI long ago (primary and secondary ISE) and then secondary was deleted from PI. Primary ISE still persists in PI but its status is unreachable:
But I can see info about wired clients authenticating on the switchs (NADs for ISE) - weird, status is unreachable but client info is being received from ISE.
I tried application stop NCS/application start NCS on PI and application stop ise/application start ise on ISE - no success for that issue.
So I can't find a way to solve that weird issue, maybe you can help me find out the cause of such things. Thanks.

Hi,
-- Please Go to Administration > Logging > set the Message level to TRACE > Click save
-- Then try to add the ISE.
-- Once it fails, collect the logs from Administration > Logging >
check the "ncs-0-0.log" & search the file for "ERROR" & paste the results here. This will give us exact reason.
- Ashok
Please rate the post or mark as correct answer as it will help others looking for similar information

Problem in running Managed Servers

Hi,
I used the configuration wizard and tried creating a domain ( admin server , 2 managed servers ('new_Server_1' , 'new_Server_2' )) . Admin server listens to the port 7003.
Set up details :
Managed Servers - IP's - Port
new_Server_1 - 1.1.1.10 - 7011
new_Server_2 - 1.1.1.11 - 7011
Node Manager - 1.1.1.10 - 5555
I login into the admin console after the whole set up, node manager was running , admin server wa s running and tried starting the managed servers ,But they failed to start giving the error message -
<Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Microsystems Inc.>
<Jan 9, 2010 11:29:57 AM CET> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://1.1.1.10:7003 to check if there exists a running admin server at this URL.>
<Jan 9, 2010 11:29:57 AM CET> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jan 9, 2010 11:29:57 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Jan 9, 2010 11:29:57 AM CET> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://1.1.1.10:7003 to retrieve the initial configuration.>
<Jan 9, 2010 11:29:58 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\weblogic81\common\nodemanager\new_Server_1\new_Server_1.log is opened. All server side log events will be written to this file.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jdk142_05\jre\lib\security\cacerts.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "new_Server_1" for domain "integration">
<Jan 9, 2010 11:30:03 AM CET> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster new_Cluster on 237.0.0.1:7011.>
<Jan 9, 2010 11:30:03 AM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of new_Cluster.>
<Jan 9, 2010 11:30:36 AM CET> <Error> <Deployer> <BEA-149601> <The deployment framework was unable to resume accepting requests.>
<Jan 9, 2010 11:30:36 AM CET> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: Deployer:149601The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
java.lang.ClassNotFoundException: com.bea.wli.init.BPMStartup>
The WebLogic Server did not start up properly.
weblogic.management.AbortDeploymentException: weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
java.lang.ClassNotFoundException: com.bea.wli.init.BPMStartup
at weblogic.t3.srvr.StartupClassService.addDeployment(StartupClassService.java:92)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
Reason: Deployer:149601The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
java.lang.ClassNotFoundException: com.bea.wli.init.BPMStartup
Is this due to the WLI Start up classes set to both admin and managed servers caused this problem / jars missed out while creating a domain ,, ? any pointers to solve this issue.
thank you in advance.
colonel

Hi,
<font color=red>OPTION-A)</font>
If you are able to start the Managed Server using ...the Start Scripts then it means that the Missing class gets included in the Server Classpath ....when we use StartScripts to Start the Server.
If above one works fine...then Just try the following..
Step1). Open the "nodemanager.properties" file and then "startScriptEnabled=true" and "startScriptName=startWebLogic.cmd" ....provide these two entries there....remember if you are using any custom scripts to start your managed server ...then give that scriptname in "startScriptName" parameter..
Step2). restart the Node Manager and then try to start the Managed Server from Admin Console.
for more informations Please refer to "nodemanager.properties" details:
http://download-llnw.oracle.com/docs/cd/E15051_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
<font color=red>OPTION-B)</font>
Start the ManagedServer using the StartScripts and then open the server OUT file....
Find the value of CLASSPATH in that OUT File ...copy the CLASSPATH Value and then Login to Admin Console....
Servers--->Click on ServerName (Example MS1)---> configuration Page ---> ServerStart (TAB)
In this page Paste the CLASSPATH Value which u have copied....in the CLASSPATH Test Field...
Now restart your Server using AdminConsole.
Thanks
Jay SenSharma
Edited by: Jay SenSharma on Jan 30, 2010 6:42 PM
Edited by: Jay SenSharma on Jan 30, 2010 10:57 PM

Managed servers are started/stopped from admin console using NodeManager

Hi,
I have weblogic cluster and it has 4 managed servers on two different machines with each machine having 2 managed servers.
I have node manager setup on the two machines. I use admin console to start/stop managed servers.
Now there is a requirement to add TIBCO lib and bin path to weblogic managed server path. I have added the entries in LD_LIBARY_PATH but on starting the server using admin console the TIBCO lib/bin paths are not appended to weblogic server path.
I noticed that in nodemanager.properties we have set StartScriptEnabled=false and so it doesn't use startWebLogic.sh,which internally use other configuration files.
I'm wondering as how to add these entries in WebLogic server path. Also, how the nodemanager is able to start the managed server without using startWebLogic.sh script.
In general, what happens when I click the start button in Admin console to start the managed servers which calls NodeManager internally.
Your inputs are highly appreciated.
Thanks in advance.
BR,
Ajmal

Hi Ajmal,
For your issue there are two solution's as shown below:
Solution-1
You can add the TIBCO lib with the complete path where the TIBCO lib file is kept from console in Class Path
Console Path:
Servers > Configuration > Server Start
However this has to be done with all the managed serves.
Solution-2
If you don't want the burden to add the TIBCO lib files on every server from console then you can add the same lib files in the classpath of startWebLogic.sh and in nodemanager.properties we have set StartScriptEnabled=true. This will make sure that all the settings would be taken from the startWebLogic.sh.
This way whenever you start any of you managed servers from console it would pick up that lib files.
In both the solution you can check the managed servers *.out* files that the lib files would be present in there classpath.
Hope this would help you.
Regards,
Ravish Mody

OSB Managed Servers - How to add one to the OSB Cluster

Hi,
I have an OSB Cluster of two managed servers. There is an Admin Server that controls the two.
On the Admin Server I see that there are about 137 odd Applications and a list of Libraries installed.
However on the Managed Servers I see there is not a single application.
Does Managed Server show only the Custom applications? I feel not. Applications like AQAdapter, MQ Adapter, ALSB Routing, etc. should they all not be present on the Managed Servers?
If I create a new Managed Server that I want to Add to the Cluster there is no option to deploy those applications to the newly created Managed server in one shot. The only time it can get those applications is if the Applications were deployed to the OSB Cluster and not to the managed servers.
Is there a way (apart from extending the domains again and having those applications deployed to the OSB cluster) to have all these applications running on the Managed servers as well?

Does Managed Server show only the Custom applications? I feel not. Applications like AQAdapter, MQ Adapter, ALSB Routing, etc. should they all not be present on the Managed Servers?Your understanding is correct. Managed server should have libraries and adapters targetted to it.
Is there a way (apart from extending the domains again and having those applications deployed to the OSB cluster) to have all these applications running on the Managed servers as well? Yes, manually you have to target each and every application to the cluster but it may not be an effective process. The basic funda of cluster is to make applications independent of managed server, so that if you add/remove a managed server then it does not affect the existing configuration. I think you should follow the standard practice and always create a clustered domain where all applications are targetted to cluster and NOT to the managed server. You may like to refer -
http://download.oracle.com/docs/cd/E17904_01/doc.1111/e15022/config.htm#i1531648
Regards,
Anuj

Starting managed servers

Hi,
Environment: WebLogic 6.1 SP2, JDK1.3.1, Solaris 8
1. How to start the managed servers using NodeManager from the command line? Already
NodeManager configured and able to start managed servers from the Admin Console.
So from the console start/stop/kill managed servers is fine. From the command
line, if I use `weblogic.Server` to start managed server it's not using the node
manager.
2. In the `java weblogic.nodemanager.NodeManager help`, option `starttemplate`
defaults to `nodemanager.sh`. Any details on this please ?
3. Each time we start managed server with Node Manager, it writes the output to
the new file `OutputFile=./config/NodeManagerlogs/<server>/startserver-<XXXX.log`.
From the documentation it looks like we can set logs directory
`-Dweblogic.nodemanager.savedLogsDirectory=path`, however is it possible to specify
the log file name also?
4. Where is the location of the java applications `System.out`, if the managed
server is started with NodeManager. If the managed server is started with `weblogic.Server`
the `System.out` are printed to the console. So this enables us to redirect to
a file.
thanks
Sarva Meduri

I think you can configure the NodeMgr to start ManagedServers instead of having the
Windows Service start the servers. Basically you configure NodeMgr as a Windows Service
and then let NM take care of starting other servers. I believe you have to set
ManagedServer's HostsMigratableServices attribute to false to enable NM start the server.
By default it is true.
prasen
Gerardo Rojas wrote:
Hi:
I have been trying to configure my WebLogic environment to start the managed servers
in a domain automatically when the machine is rebooted. I have done some testing
with Node Manager but, as I understood, Node Manager only restarts a server if
it was started using Node Manager and the server crashes or fails. On the other
hand, if the server is installed as a Windows service, it will be started at reboot
time, but not when the server (not the machine) crashes or fails. So, both solutions
seems to be uncompatible. Is it right?? Is it possible to have both benefits,
that is, to get the managed servers started at boot time (as done by Windows services)
and restarted each time they fail (as done by Node Manager)?
Thanks,
Gerardo

Weblogic.Admin command for stopping all Managed Servers in cluster

Hello All,
I am using Weblogic 9.2 MP3 on Linux env. I have a domain which has 16 Managed servers which are part of a cluster, I have eight Managed Servers running on one physical machine and other eight running on another physical Machine.
I know we can do all stop and all start of Managed servers from console if we have node manager setup. We do not want to have node manager setup in our env.
I am looking for a way to do that using java weblogic.Admin utility
Please let me know on how we can achieve this using weblogic.Admin utility by passing clustername argument.
Thanks
Weblogic Consultant

hi sir,
I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
If u want to use WLST for starting managed servers and clusters
check the follwing steps.
1. java weblogic.WLST
2. startNodeManager()
3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
4. TAKE ANOTHER COMMAND PROMPT
java weblogic.WLST
5. start('man1','Server') or start('man1','Server','localhost:7003')
6. start('mycluster','Cluster')
7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
8.shutdown('mycluster','Cluster')
regards
abhi
Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM

Detecting Managed Servers

I have a Admin Server and a couple of Managed Servers running in my domain. Is
there any MBean or some other component using which I can keep track of managed
servers from the admin server?
To be more specific, I want to keep track of managed servers, and perform some
action on the admin server as and when a managed server starts...
Thanks,
jayant.
Thanks,

Holger Dewes wrote:
Kumar Allamraju <[email protected]> wrote:
pls clarify whether the process has died or servers are hung?
Hello Kumar,
that's actually a very good question. Does every managed server
run in its own process?Yes.
I will have to investigate this. All I
can say at the moment is that the web console shows the server
as not running. There's a known issue in 61 sp2 that admin console loosing the discovery
of managed servers under load. May be this is what you are seeing.
Then I start it again, and it runs fine... for aRegardless i want you to check the process id of that managed server and
see if it exists or not...
Kumar
while.
Cheers

Automatically starting of Managed Servers

Hi, is it possible to start the managed servers without the use of WLST and the admin console automatically?
I want to make it such that when the Admin Server starts up, a service will run and automatically start the managed servers at a different host via the node manager?
Is it even possible? Please advise! Thanks!

Node Manager uses WLST so I'm not sure how else you would plan on using it?
Node Manager can start your machines in the last known state they were in on reboot using CrashRecoveryEnabled=true:
http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
Another option is to use the startup/services feature of your OS as Jay described. On *nix you could remotely login to another host and invoke the domain's bin/startManagedWebLogic script directly.

Limit on number of Managed Servers in a cluster

          Hi All,
          Do you know if there is any limit on number of managed servers I can have in a
          cluster.
          If there is a limit then how many?
          If not, is there a recommended limit from BEA?
          We are using Weblogic 6.1 SP2 and we have 16 managed servers running in the cluster.
          Under heavy load (through put about 600-800) the console is not responding fast.
          Also when we try to monitor the Weblogic Servers from the console under Monitoring->performance
          , the screen is not getting refreshed faster(which makes me think the monitoring
          info I see on the console is not completely correct).
          I have a heap size of 96m for admin and 768m for Managed Servers.
          Did anyone see this problem before.
          Are there any command line arguments that I can add to make my console respond
          faster?
          If not, do we have any patch from BEA that makes console work faster?
          Please suggest.
          Thanks for your attention,
          Kiran


Hi Vineet,
In Latest version of SAP MDM which is 7.1 we have the liberty to use multiple Main tables so answer to your question is yes we can use 20-30 main tables, now the question is that what type of data model you are prepairing this question is just to understand your entire structure and may be suggest some thing at higher level on which you can think and then take corrective action as per your thoughts.
Generally even if you are integrating Customer/Products in single repository and then designing the main table you wont have to prepare such huge number of main tables you can have these two main tables and then rest of then as sub tables and refer it to each other also you need to know what imapct it will have on system performance becuase they would be referring to each other and also if you are creating some thousands of records in each repository then it is more advisable to use limited number of main tables and use MDM to it's fullest capability by designing such model that we have best utlisation of server performance.
Hope it helped a bit.
Let me know if you need any further information on same.
Thanks and Regards
Praful.

Unable to start the Managed servers OIM and SOA after starting the Weblogic

Hi,
We are unable to start the any manager servers after starting the weblogic Admin Server.
We are getting the below error after trying to start the OIM or SOA managed servers.
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 5555; nested exception is:
java.net.BindException: Address already in use
We have also cross verified that the port 5555 is listening after starting the weblogic Admin server.
Please help us to start the managed servers in the weblogic 10.3.5.
Thanks.

We are getting the below errors after starting the Admin server and Managed servers.
Admin Server:
<Jan 11, 2012 7:15:06 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Jan 11, 2012 7:16:02 AM EST> <Error> <org.apache.beehive.netui.pageflow.internal.AdapterManager> <BEA-000000> <ServletContainerAdapter manager not initialized correctly.>
Managed Server:
Starting WLS with line:
/opt/jdk1.6.0_27/bin/java -client -Xms1024m -Xmx4096m -XX:PermSize=512m -XX:MaxPermSize=1024m -Dweblogic.Name=oim_server1 -Djava.security.policy=/ama/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.security.SSL.trustedCAKeyStore=/ama/Oracle/Middleware/wlserver_10.3/server/lib/cacerts -Xverify:none -da -Dplatform.home=/ama/Oracle/Middleware/wlserver_10.3 -Dwls.home=/ama/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/ama/Oracle/Middleware/wlserver_10.3/server -Dcommon.components.home=/ama/Oracle/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/ama/Oracle/Middleware/user_projects/domains/base_domain -Djrockit.optfile=/ama/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/servers/oim_server1 -Doracle.domain.config.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig -Digf.arisidbeans.carmlloc=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/carml -Digf.arisidstack.home=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/servers/oim_server1/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/ama/Oracle/Middleware/Oracle_IDM1/server/loginmodule/wls,/ama/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/ama/Oracle/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -DXL.HomeDir=/ama/Oracle/Middleware/Oracle_IDM1/server -Djava.security.auth.login.config=/ama/Oracle/Middleware/Oracle_IDM1/server/config/authwl.conf -Dorg.owasp.esapi.resources=/ama/Oracle/Middleware/Oracle_IDM1/server/apps/oim.ear/APP-INF/classes -da:org.apache.xmlbeans... -Dsoa.archives.dir=/ama/Oracle/Middleware/Oracle_SOA1/soa -Dsoa.oracle.home=/ama/Oracle/Middleware/Oracle_SOA1 -Dsoa.instance.home=/ama/Oracle/Middleware/user_projects/domains/base_domain -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=/ama/Oracle/Middleware/wlserver_10.3/server/lib/DemoTrust.jks -Dem.oracle.home=/ama/Oracle/Middleware/oracle_common -Djava.awt.headless=true -Dums.oracle.home=/ama/Oracle/Middleware/Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://127.0.0.1:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/ama/Oracle/Middleware/patch_wls1035/profiles/default/sysext_manifest_classpath:/ama/Oracle/Middleware/patch_ocp360/profiles/default/sysext_manifest_classpath weblogic.Server
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 5555; nested exception is:
java.net.BindException: Address already in use
We have to find out why the port 5555 is in listening mode after starting the Admin server.

Hi, we need to create the test environment from our production for oracle AP Imaging. we have soa,ipm,ucm and capture managed servers in our weblogic. can anyone tell me what is the best way to clone the environment, can I just tar the weblogic file syste

Hi, we need to create the test environment from our production for oracle AP Imaging. we have soa,ipm,ucm and capture managed servers in our weblogic..
Can anyone tell me what is the best way to cloning the application from different environment, the test and production are in different physical server.
Can I just tar the weblogic file system and untar it to the new server and make the necessary changes?
Can anyone share their experiences and how to with me?
Thank in advance.
Katherine

Hi Katherine,
yes and no . You need as well weblogic + soa files as the database schemas (soa_infra, mds...).
Please refer to the AMIS Blog: https://technology.amis.nl/2011/08/11/clone-your-oracle-fmw-soa-suite-11g/
HTH
Borys

SOA and OWSM in separate managed servers

Similar Messages

Maybe you are looking for