Does NodeManager make the Admin Server restart at reboot?

I have been trying to run both my Admin server and SOA Suite using the Node Manager based on this article:
http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
When I reboot, the soa_server1 (managed server) starts up but the AdminServer does not.
Am I missing something? Is this not something the NodeManager is supposed to support?
Thanks for quick replies,
Jeremy

It depends on how you have deployed your application on Weblogic. Generally, organizations do not have any of their applications on the Admin server. They generally use a clustered set of managed servers to have their applications deployed on them. From the security perspective also, the Admin server is preferred to be kept down as this prevents unauthorized users from gaining access to the Admin console and making changes on them. However, before keeping the Admin server down, you must make sure that none of your application components are deployed on the Admin server or make use of the Admin server.
Edited by: Smithan John on Jun 8, 2010 1:33 PM

Similar Messages

BEA-141151 The admin server could not be reached at ...

I have been at this for 3 days now... I created a new ManagedServer, but I'm not able to make it connect to the Admin server.
The Admin server is running and listening on port 5306. I can connect to the Admin Console (web).
I can also connect to the Admin server via WLST, using this command: connect('operator','operator01','t3://localhost:5306')
However, when I try to run the managed server from a script, it does not see the Admin server. This is the command I run:
java -Dweblogic.Name=ManSer1 -Dweblogic.management.server=t3://localhost:5306 -Dweblogic.RootDirectory=<path to my domain> weblogic.Server
This is the error I get:
<BEA-141151> <The admin server could not be reached at http://localhost:5306.>
I believe it's trying to connect using "http", because I've never actually connected in the past. Here is a website explaining this: http://download.oracle.com/docs/cd/E17904_01/web.1111/e13749/weblogicserver.htm#i1031832
Note: Regardless of which protocol you specify, the initial download of a Managed Server's configuration is over HTTP or HTTPS. After the RMI subsystem initializes, the server instance can use the T3 or T3S protocol.
I'm not sure what else to try... Firewalls are not in play, since this is traffic moving around on the local machine. I'm running on SunOS. Weblogic is version 9.2 MP3.
Appreciate any help.

Is the NodeManager , AdminServer running ?The NodeManager is not running. Is it required?
Also, I haven't closed the command prompt.
I noticed the issue when I tried to deploy my project. Connected to Localhost/7001 but in the deploy project window, I dont see any soa_server instance
running. Also, in the console the soa_server status is shutdown.

Does SNMP agent on the admin server polls managed objects automatically?

Hi All,
If I enable SNMP agent on the admin server, does it mean that it polls and caches MIB of all the managed servers in the domain and return it if a client requests for information or it polls and caches that MIB value only when requested?
2)Suppose a client requests for SNMP data of a managed instance and the instance is down, does admin server keep polling or does it timeout after a number of secs or retries. I don't see any config params in weblogic 8.1.3 or weblogic 9.0 console.
Thanks. I appreciate your answers.
Thanks,

Are you saying the notes are incorrect?
No, I wasn't commenting on that at all. I was just saying that DBUA is the recommended way of upgrading databases... and that's in spades if you're talking about 100GB databases.
I'll lay odds that DBUA to 10.2.0.1 and then patching to 10.2.0.3 is quicker than exporting and importing 100GB of data.
(Applying a 10.2.0.3 patch is done with opatch and doesn't require a fresh installation of Oracle. A patch mostly just modifies the data dictionary: it's finished in minutes, not hours).
My real point: these sorts of questions are incredibly easy to ask, answer, discard, re-ask, modify, mull over and basically experiment with in a virtual environment.
And again: it's utterly bizarre why you wouldn't have physical access to this database (and keep in mind that I can't keep in mind little nuggets of information such as this one which you didn't see fit to share earlier!)
It's in a virtual server. Virtual servers can be zipped up and emailed! (OK, maybe not 100GB... but I've shipped a small hard disk in a zip-lok pack envelope half way round the world before now -though obviously it wasn't critical to have the contents of that envelope available for use all the time... Still, it sounds to me like here's a technology (virtualisation) that's not being properly exploited).

The admin server AdminServer cannot be restarted.

Hi OTN,
I face this problem really often.
In WebLogic console I have done some changes with security realms.
Adter I click "Save" it says I nned to restart server for changes to take effect.
I click go Change Center -> View changes and restarts -> Restart Checklist and see AdminServer here.
I check it (the checkbox) and click Restart. In reply I have the following message:
The admin server AdminServer cannot be restarted.All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.>
What should I do with it?
Thanks.
WLS 10.3

Same issue was found on WLS1036.
Scenario with AdminServer and ms1, no cluster.
- created a DS and targeted to ms1.
- ms1 is up & running and tests with DS are OK
Test 1. Changing URL to DS
- once the URL was modified, WLS thrown these messages:
MS1: "All changes have been activated. However 1 items must be restarted for the changes to take effect."
MS2: "Settings updated successfully."
- in the Restart Checklist, the JDBC resource is ready to be restarted. The DS is targeted to ms1
- select the DS and click over Restart button and we got the message : "All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed."
- DS was restarted manually but the item in the Restart Checklist remains until the MS is restarted.
This issue was due to a bug on product. Please request to support patch 14504923.

Weblogic does not support failover for the admin server.

There is a single point of failure in the current weblogic architecture. If the
admin server dies there is no automatic alternate admin server.

That is true, and we plan to fix it in one of the next major releases. Currently
the story is not as bad as it appears to be for following reasons:
1. Failure of admin server doesn't mean failure of already running managed server.
2. You can start a new server as admin server of domain with discover flag=true and
it will recognize all already exisiting managed server.
Viresh Garg
Principal Developer Relations Engineer
BEA Systems
naresh gupta wrote:
There is a single point of failure in the current weblogic architecture. If the
admin server dies there is no automatic alternate admin server.

Newbie cluster question: where does the admin server live?

Hello, I'm looking at clustering for our application where I work, and so I'm reading through the cluster-related documentation for 11g. I have a sort of an architecture question: where should the admin server be started? Hypothetically speaking, if you have two nodes for your cluster, would the AdminServer run on a 3rd box which sort of stood in front of the two nodes?
Thanks much -

The ideal situation would be for your admin server to be separate from the machines hosting your managed server. This allows you to control access to the admin server, eliminate the performance impact if you have the admin + managed on the same host, and limits impact if youir #1 host fails, etc.
But companies may be unwilling to invest in a distinct (3rd) host just for the admin server, especially if you have multiple environments ( prod, testing, dev, etc. ).
So usually the admin winds up sharing the host with a managed server.

How to start the admin server on another WLS machine?

Hi,
          I have a weblogic cluster with 2 weblogic machines: machineA and machineB.
          The cluster contains 4 managed servers (2 on each WLS machine)
          The admin server runs on machineA (standalone).
          I have a file backup of the domain directory on machineA.
          Suppose machineA crashes.
          How can I start the admin server on machineB?
          Kind regards,
          Pieter

Thanks for your reply,
          I know how to (re)start the admin server on machineA. But in this case I want to start the admin server on machineB.
          The documentation says:
          Restarting an Administration Server on Another Machine
          If a machine crash prevents you from restarting the Administration Server on the same machine, you can recover management of the running Managed Servers as follows:
          Install the WebLogic Server software on the new administration machine (if this has not already been done).
          Make your application files available to the new Administration Server by copying them from backups or by using a shared disk. Your application files should be available in the same relative location on the new file system as on the file system of the original Administration Server.
          Make your configuration and security data available to the new administration machine by copying them from backups or by using a shared disk. For more information, refer to Directory and File Backups for Failure Recovery.
          Restart the Administration Server on the new machine.
          Simply starting the admin server on the other machine does not work because it tries to start the admin server on the ip address of the old machine.
          Edited by [email protected] at 05/10/2007 7:47 AM

"Unauthorized Host" error when you try to connect to the admin server

"Unauthorized Host" error when you try to connect to the admin server

If you see this error message when you try to connect to a Netscape
administration server:
Internal Error
The administration server was unable to fulfill your request.
Reason: Unauthorized host
--------------------------
Here is how to solve the problem and gain access. First you should
temporarily open access to all sites, and then once you make sure that
this lets you get into your administration server, try again to set up
the domain name or IP address access restrictions you want.
For all 2.x/3.x Netscape servers on Windows NT and Unix, or for Commerce and
Communications servers (1.x) on Unix:
<OL>
<LI>Open the "ns-admin.conf" file with a text editor. You can
find this file in the "admserv" directory under your Netscape
server root. The directory is named "admin-serv" in 3.x servers.
<LI>Delete the "Hosts" and "Addresses" lines you see there (either one
of them might not be present). Don't confuse the "Addresses" line,
which you should delete, with the "Address" line, which you should NOT
delete.
<LI>Save the file, then restart your administration server (on Unix run
"stop-admin" then "start-admin"; on Windows NT go into the Services
control panel and stop/start the "Netscape Admin Server" service).
</OL>
For Commerce Server or Communications Server (1.x) on Windows NT:
<OL>
<LI>Go into the registry editor. On Windows NT 4.0, run the command
"regedit". On Windows 3.51, run the command
"regedt32".
<LI>Navigate down to the section
"HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Administration".
<LI>Delete the "Hosts" and "Addresses" entries you see there (either one
of them might not be present). Don't confuse the "Addresses" entry,
which you should delete, with the "Address" entry, which you should NOT
delete.
<LI>Close the registry editor, then restart your administration server
by going into the Services control panel and stopping then starting the
"Netscape Administration" service.
</OL>
Now try again to access your administration server. Remember, the URL
will be something like "http://servername:12345/", where
"12345" is where the administration server's port number goes.
If you still get the same "Unauthorized host" error, then make sure that
your "ns-admin.conf" file really doesn't contain any "Hosts" or
"Addresses" lines any more, and try stopping your administration server
again then starting it back up.
Once you have access to your administration server, you can try again to
set up the access controls you want.
<UL>
<LI>For the administration server on a 3.x server installation, select
"Admin Preferences" from the General Administration page (the first page
you see when you connect to the admin server), then click on "Superuser Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 2.x server installation, select
"Configure Administration" from the Server Selector page (the first page
you see when you connect to the admin server), then click on "Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 1.x server installation, select
"Configure Administration Server" from the bottom of the Server Manager
page, then enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the substrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that your
DNS can resolve those hostnames -- it's generally safer to stick with IP address
restrictions.
When you're finished configuring this, click "Make These Changes" then
restart your admin server.
</UL>
If you still find yourself getting an "Unauthorized host" error message,
you can use the above steps to open up access and try different
settings.

"Unauthorized Host" error when you try to connect to the admin server

If you see this error message when you try to connect to a Netscape
administration server:
Internal Error
The administration server was unable to fulfill your request.
Reason: Unauthorized host
--------------------------
Here is how to solve the problem and gain access. First you should
temporarily open access to all sites, and then once you make sure that
this lets you get into your administration server, try again to set up
the domain name or IP address access restrictions you want.
For all 2.x/3.x Netscape servers on Windows NT and Unix, or for Commerce and
Communications servers (1.x) on Unix:
<OL>
<LI>Open the "ns-admin.conf" file with a text editor. You can
find this file in the "admserv" directory under your Netscape
server root. The directory is named "admin-serv" in 3.x servers.
<LI>Delete the "Hosts" and "Addresses" lines you see there (either one
of them might not be present). Don't confuse the "Addresses" line,
which you should delete, with the "Address" line, which you should NOT
delete.
<LI>Save the file, then restart your administration server (on Unix run
"stop-admin" then "start-admin"; on Windows NT go into the Services
control panel and stop/start the "Netscape Admin Server" service).
</OL>
For Commerce Server or Communications Server (1.x) on Windows NT:
<OL>
<LI>Go into the registry editor. On Windows NT 4.0, run the command
"regedit". On Windows 3.51, run the command
"regedt32".
<LI>Navigate down to the section
"HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Administration".
<LI>Delete the "Hosts" and "Addresses" entries you see there (either one
of them might not be present). Don't confuse the "Addresses" entry,
which you should delete, with the "Address" entry, which you should NOT
delete.
<LI>Close the registry editor, then restart your administration server
by going into the Services control panel and stopping then starting the
"Netscape Administration" service.
</OL>
Now try again to access your administration server. Remember, the URL
will be something like "http://servername:12345/", where
"12345" is where the administration server's port number goes.
If you still get the same "Unauthorized host" error, then make sure that
your "ns-admin.conf" file really doesn't contain any "Hosts" or
"Addresses" lines any more, and try stopping your administration server
again then starting it back up.
Once you have access to your administration server, you can try again to
set up the access controls you want.
<UL>
<LI>For the administration server on a 3.x server installation, select
"Admin Preferences" from the General Administration page (the first page
you see when you connect to the admin server), then click on "Superuser Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 2.x server installation, select
"Configure Administration" from the Server Selector page (the first page
you see when you connect to the admin server), then click on "Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 1.x server installation, select
"Configure Administration Server" from the bottom of the Server Manager
page, then enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the substrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that your
DNS can resolve those hostnames -- it's generally safer to stick with IP address
restrictions.
When you're finished configuring this, click "Make These Changes" then
restart your admin server.
</UL>
If you still find yourself getting an "Unauthorized host" error message,
you can use the above steps to open up access and try different
settings.

Deploying applications on the Admin Server

Hi there
I have recently moved to a new project team who have been deploying their applications to the admin server. They have been doing this for years with no issues.
I was always led to believe that the best practice was to keep the admin server completely separate. And I always deployed to a managed server (or a cluster of servers).
Does anyone know of any specific reasons why applications should not be deployed to an admin server.
Thanks in advance.

Typically, you want your managed servers to focus on applications, and the admin server to focus on management of the servers. If you have your heavy load applications deployed to the admin server, then that impacts both your applications and the management of those applications.
If your applications are deployed to the managed server, and not the admin server, you can recycle applications remotely just through the admin server console. If you need to restart the application, and it's running on the admin server, then you'll have to take additional steps to get the server running again.

Could not load Logmanager "oracle.core.ojdl.logging.ODLLogManager" error while starting the Admin server

Hi,
 I installed weblogic 12.1.2.0.0 with RHEL5.6. After the installation, I tried to post the following class path in setDomainEnv.sh file under the domain home directory,
POST_CLASSPATH="/prosun/jasper/jasperreports-3.6.0.jar:/prosun/jasper/commons-digester-1.7.jar:/prosun/jasper/log4j-1.2.15.jar:/prosun/jasper/org.apache.commons.beanutils_1.6.jar:/prosun/jasper/org.apache.commons.collections_3.1.jar:/prosun/jasper/org.apache.commons.logging_1.0.4.jar:/prosun/jasper/iText-2.1.0.jar:/prosun/jasper/groovy-all-1.5.5.jar"
While i am trying to start the Admin server, the server didn't started and following exception is reported in nohup.out file. Please help me to resolve this issue.
The above library jars are required for our applications.
Could not load Logmanager "oracle.core.ojdl.logging.ODLLogManager"
java.lang.ClassNotFoundException: oracle.core.ojdl.logging.ODLLogManager
java.lang.ClassNotFoundException: oracle.core.ojdl.logging.ODLLogManager
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager$1.run(LogManager.java:186)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.security.AccessController.doPrivileged(Native Method)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at java.util.logging.LogManager.<clinit>(LogManager.java:176)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.util.logging.Logger.getAnonymousLogger(Logger.java:483)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at java.util.logging.Logger.getAnonymousLogger(Logger.java:452)
at java.util.logging.LogManager$1.run(LogManager.java:186)
at weblogic.kernel.KernelLogManager.createClientLogger(KernelLogManager.java:44)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.kernel.KernelLogManager.access$000(KernelLogManager.java:17)
at java.util.logging.LogManager.<clinit>(LogManager.java:176)
at weblogic.kernel.KernelLogManager$LoggerMaker.<clinit>(KernelLogManager.java:20)
at java.util.logging.Logger.getAnonymousLogger(Logger.java:483)
at weblogic.kernel.KernelLogManager.getLogger(KernelLogManager.java:26)
at java.util.logging.Logger.getAnonymousLogger(Logger.java:452)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at weblogic.kernel.KernelLogManager.createClientLogger(KernelLogManager.java:44)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at weblogic.kernel.KernelLogManager.access$000(KernelLogManager.java:17)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at weblogic.kernel.KernelLogManager$LoggerMaker.<clinit>(KernelLogManager.java:20)
at java.lang.reflect.Method.invoke(Method.java:601)
at weblogic.kernel.KernelLogManager.getLogger(KernelLogManager.java:26)
at weblogic.logging.MessageLogger.log(MessageLogger.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at weblogic.logging.MessageLogger.log(MessageLogger.java:111)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at weblogic.logging.WLMessageLogger.log(WLMessageLogger.java:52)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at weblogic.security.SecurityLogger.logDisallowingCryptoJDefaultJCEVerification(SecurityLogger.java:13444)
at java.lang.reflect.Method.invoke(Method.java:601)
at weblogic.security.utils.SecurityUtils.turnOffCryptoJDefaultJCEVerification(SecurityUtils.java:81)
at weblogic.logging.MessageLogger.log(MessageLogger.java:96)
at weblogic.Server.main(Server.java:70)at weblogic.logging.MessageLogger.log(MessageLogger.java:111)
at weblogic.logging.WLMessageLogger.log(WLMessageLogger.java:52)
Could not load Logmanager "oracle.core.ojdl.logging.ODLLogManager"
java.lang.ClassNotFoundException: oracle.core.ojdl.logging.ODLLogManager
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at java.util.logging.LogManager$1.run(LogManager.java:186)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.<clinit>(LogManager.java:176)
at java.util.logging.Logger.getAnonymousLogger(Logger.java:483)
at java.util.logging.Logger.getAnonymousLogger(Logger.java:452)
at weblogic.kernel.KernelLogManager.createClientLogger(KernelLogManager.java:44)
at weblogic.kernel.KernelLogManager.access$000(KernelLogManager.java:17)
at weblogic.kernel.KernelLogManager$LoggerMaker.<clinit>(KernelLogManager.java:20)
at weblogic.kernel.KernelLogManager.getLogger(KernelLogManager.java:26)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
Regards,
Anand Krishnan

hi, you should not do nothing with user root.
please, don't use root again for weblogic administration.
list all files with root permissions:
move to Middleware Home, example: cd /u01/app/oracle/Middleware
find . -user root
if there are files with root permissions, change it to oracle:oinstall
I saw this:
Could not load Logmanager "oracle.core.ojdl.logging.ODLLogManager"
java.lang.ClassNotFoundException: oracle.core.ojdl.logging.ODLLogManager
Please check in DOMAIN_HOME/bin/setDomainEnv.sh file if exist this:
JAVA_OPTIONS="-Djava.util.logging.manager=oracle.core.ojdl.logging.ODLLogManager ${JAVA_OPTIONS}"
export JAVA_OPTIONS
MWCONFIG_CLASSPATH=${FMWCONFIG_CLASSPATH}${CLASSPATHSEP}${COMMON_COMPONENTS_HOME}/modules/oracle.odl_11.1.1/ojdl.jar
export FMWCONFIG_CLASSPATH
if exist, replace for:
JAVA_OPTIONS="${JAVA_OPTIONS}"
export JAVA_OPTIONS
if not existe, its necesary for you to use /prosun/jasper/org.apache.commons.logging_1.0.4.jar in your classpath?. If it isn't necesary delete it, and restart the AdminServer.

Errors & warnings when using the Admin Server Console - Help Needed

hi,
i just installed weblogic 12c and created a new domain which contains an adminServer and managedServer under
one cluster.
after finishing the installation, i started the Admin Server and afterwards started the admin server console.
and i got the next warning and errors.
the warning look like this:
<20:00:35 IST 23/03/2012> <Warning> <Munger> <BEA-2156203> <A version attribute
was not found in element "web-app" in the deployment descriptor C:\Oracle\Middle
ware\user_projects\domains\base_domain\servers\AdminServer\tmp\_WL_internal\cons
oleapp\jxhze9\console-ext\sipserver-console-ext\WEB-INF\web.xml. A version attri
bute is required, but this version of the WebLogic Server will assume that the l
atest version is used. Future versions of WebLogic Server will reject descriptor
s that do not specify the Java EE version. To eliminate this warning, add an app
ropriate "version=" to element "web-app" in the deployment descriptor.>
the errors look like this:
<20:01:51 IST 23/03/2012> <Error> <netuix> <BEA-423158> <No content found at con
tentUri = /PortalConfig/security/providers/AuthenticatorConfigCommon.portlet.>
what is the problem? anyone knows?

If you want to have an weblogic environment with one domain having server spread across different physical machines , then you will have to perform the installations of the weblogic server separately on all the machines . Also make sure that the version of the Weblogic server you are installing is same across the machines and the directory structure is also exactly same.
In short you will have to perform the below steps :
1 : install the weblogic server on all the machines with exactly same version and same dir structure .
2 : Create domain on MachineA providing all the details of the Managed Server and different machine hostnames.
3 : Start the Admin Server on machineA and then shut down it.
4 : execute the WLST pack command on MachineA creating a domain template JAR file.
5 : copy the create jar file on all the Machines ( B , C , D ) you have to distribute your domain.
6 : Execute the WLST unpack command on all the machines ( B , C , D ) .
7 : Execute the WLST nmEnroll () command on all the machines ( B, C , D ).
8 : Start the Managed Servers on all the machines ( B , C , D )

How to upgrade the Admin Server to WLS 9.2.3 while Managed on 9.2.2

HI,
I have a WLS 9.2.2 domain with Admin and 2 Managed instances clustered. Admin and Managed Servers are on different machines.
I want to upgrade only the Admin Server to WLS 9.2 MP3 while all my Managed Servers are in WLS 9.2 MP2.
Can any one provide me the detailed steps on how to upgrade only the Admin server to WLS 9.2 MP3?
And I read in the Weblogic documentation that this supported. But could not find any detailed steps on how to upgrade only the Admin server to the Major version.
Thanks in Advance.

Hi
1. "And I read in the Weblogic documentation that this supported". Can you please provide the link or documenation that exactly says that this is Supported ???
2. As far as I know, one of the basic requirements for Weblogic Cluster with managed servers across different remote machines is, all the machines, Admin and Managed Servers machines should have Exact Same Version (including Service Pack) of WLS deployed. Right now I do not have this link on top of my head. But this is the only Supported and one basic requirement for Weblogic Cluster.
Since WLS uses all Shared Modules and each Shared module do have like Implementation and Specification Version. If you upgrade admin server domain, most probably config.xml file will be upgraded with all modules version as 10.0.2.3 (something like that). This means when you restart Managed Servers, they will get a new copy of config.xml file from admin server machine. So now on Managed Servers all these modules (10.0.2.3 etc) should exist on their local machines. This is just my thought.
Thanks
Ravi Jegga

Em showing everything is down including the admin server eventhough they are up in Weblogic Admin Console

Hi there,
We are running with Oracle Fusion Middleware 11.1.1.3.0 on top of Oracle Weblogic 10.3.3.0 which is installed on Windows Server 2008 64 bit. We have configured two SOA domains under this middleware home.For example, we will consider the SOA domain name as SOA1 and SOA2. When we logon to SOA1 Em console, Everything is showing the exact status as like SOA1 admin console. Whereas SOA2 is not the same case. SOA2 EM console showing all in red down arrow including Admin server but SOA2 admin console says everything running fine.
We checked the Oracle Doc ID 1484381.1 for more troubleshooting, But they have provided the patch only the version from 11.1.1.5.0 or later. Also we could see below error in the emos.log
[2015-03-03T10:49:58.166+01:00] [AdminServer] [NOTIFICATION:24] [] [oracle.sysman.emas.sdk.model.jmx.JMXUtil] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 0000KjV2fVZDSc4_RTl3id1Kw52A00005M,0] [APP: em] [dcid: e80eae2a2ac05444:-1dcaadaf:14bcabbbf24:-8000-000000000000029b] Found no object names where one was expected for query: oracle.dms:name=AggreSpy,type=Spy,*
[2015-03-03T10:49:58.175+01:00] [AdminServer] [NOTIFICATION:24] [] [oracle.sysman.emas.model.region.FMWRegionModel] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 0000KjV2fVZDSc4_RTl3id1Kw52A00005M,0] [APP: em] [dcid: e80eae2a2ac05444:-1dcaadaf:14bcabbbf24:-8000-000000000000029b] Error getting Response metrics
[2015-03-03T10:49:58.176+01:00] [AdminServer] [NOTIFICATION:32] [] [oracle.sysman.emas.model.region.FMWRegionModel] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 0000KjV2fVZDSc4_RTl3id1Kw52A00005M,0] [APP: em] [dcid: e80eae2a2ac05444:-1dcaadaf:14bcabbbf24:-8000-000000000000029b] Error getting Response metrics[[
Please help us to make sync the SOA2 EM console with SOA2 Admin console.
Thanks
Lakshman,

Hi Lakshman,
what about about the WLS admin console? What is reported there for both
domains?
When starting the managed servers for SOA2 domain, have you provided
the URL of the Admin Server of SOA2 domain?
Cheers,
A.

6.0 cluster startup without the admin server...

Is it possible to start a WL6.0 cluster without the admin server being up
 and running? If not, are there any workarounds that eliminate the admin
 server as a single point of failure?


 I have same questions.
 1.The admin server's primary task is up the cluster?And if admin server is down
 that can't affect the cluster running.
 2.Is it right when the cluster is working,the useful ip is admin server's ip?For
 example,admin 10.10.10.1,cluster1 10.10.10.2,cluster2 10.10.10.3,the only useful
 ip is 10.10.10.1 in the cluster.
 3.Is it correct that because the only useful ip is 10.10.10.1,therefor my client
 access the cluster from 10.10.10.1?
 When my admin server is down,then my system will be down.
 4.which is the dispatch in the cluster system ?
 my step of configuration of th cluster:
 1.add two managed servers to admin server and edit startweblogic.cmd;
 2.config cluster.(admin server address 10.10.10.1:8168,cluster address 10.10.10.2:7001,10.10.10.3:7001),multicast(237.0.0.1)
 please help explain these questions!thanks a lot!
 2.
 Kumar Allamraju <[email protected]> wrote:
 >Sorry if i wasn't clear, what i mean to say is
 >
 >When you first start the managed server's you have to have admin server
 >up &
 >running.
 >Admin server can go down when cluster is running, but then you can't
 >add servers
 >to cluster
 >and I think its ok to have it that way from administration point of view.
 >
 >Yes, there's no facility to achieve single point of failure for admin
 >servers.
 >
 >--
 >Kumar
 >
 >
 >
 >William Wallace wrote:
 >
 >> I may be misreading that page, but it doesn't really tell me how to
 >> successfully start to start a managed server is the admin server is
 >down. If
 >> you run the managed server script you get an "cannot connect to admin
 >> server" exception if the admin server is not running. Now, I imagine
 >that I
 >> could script something up to restart the admin server if it's down,
 >but that
 >> doesn't protect me from hardware failure.
 >>
 >> "Kumar Allamraju" <[email protected]> wrote in message
 >> news:[email protected]...
 >> > http://e-docs.bea.com/wls/docs60/adminguide/startstop.html#1035064
 >> >
 >> > --
 >> > Kumar
 >> >
 >> >
 >> > William Wallace wrote:
 >> >
 >> > > Is it possible to start a WL6.0 cluster without the admin server
 >being
 >> up
 >> > > and running? If not, are there any workarounds that eliminate the
 >admin
 >> > > server as a single point of failure?
 >> >
 >

What about the admin server not working?

Hello,
I noticed that, even when the admin server is down, the LDAP server nicely serves search, create or modify clients requests. At least the extended operation persistent search works as well.
My question is what does stop working in the DS if the admin server is down?
- Likely the Server console.
- SNMP monitoring?
- Replication?
- SSL authentication?
- What else?
My concern is of course Linux ES 3.0 support.
Thanks for all your answers.

The admin server is just a http server used for administration with the console. Most admin functions can also be done from the command line, so it's really GUI administration that you are losing.

Does NodeManager make the Admin Server restart at reboot?

Similar Messages

Maybe you are looking for