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

Similar Messages

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

How can i start the Admin server? may be this will be like clue: "When i try to start the iplanet suite with the start-admin script, i receive the following error:

bash-2.03# ./start-admin
AdmInit: Failed to perform security initialization for communicate with LDAP in SSL mode (error code = -1) Exit
so i can not login to console (./startconsole) because the "admin-serv" is not up: "Can not connect to the Admin Server "http://myserver.com:myportnumber/" The URL is not correct or the server is not running." any ideas..."
---------------------Seumas Froemke on 1/15/2002 said: ----------------
"I'm not familiar with the error, but I'll throw in my two cents and hope it leads you somewhere.
First, be sure you start things in the correct order. LDAP->Admin->Console.
Be sure you've set nsadminservaccessaddresses and nsadminaccesshosts.
Do you have problems starting everything up when you aren't using SSL mode?
You can put startconsole into debug mode with startconsole -D 9 but I don't think there is a start-admin debug mode. You'd have to settle for a truss.
All in all, you should ask this in the LDAP (User Management & Policy) forum."
--------------------and i wrote: -------------------------------------
Homero Borgo Valdez on 1/18/2002 said:
"I start things in the correct order.
how can i check the nsadminservaccessaddresses and nsadminaccesshosts settings (i'm new on this suite as you can see).
if i moved some checkbox when the console was ok how can i view that settings in text mode?
by the way i have another server that can sun console well (port 2125) so what file can i compare to change some wrong settings?
thanks anyway, another idea?"
--------------------so following the commnets i put this history here ----
help please!!

jvm file is in your system file folder.so you can delete that jvm file and to run as it is.

How to change the machine name for the admin server?

Hi, I've incorrectly set the machine name for my admin server. I now need to change this, but it's not editable (WLS 10.3.3).
Is there a way to edit configuration files to get it changed?
Thanks
Jason

Seems all I needed to do was edit config/config.xml (under my domain's path) and change the machine name manually (before shutting the admin server down).
Regards
Jason

How to find what port the admin server is running

how can I find out what port the admin server is running on a server?
thanks,

Hi
Go to your domain root folder/config and open config.xml file in any editor. Search for the name of the admin server which is typically like AdminServer and under this tag see if you have a tag by name <listen-port>. If yes, then you should see the port number. If not, it means it is running at default port of 7001.
If you have admin access, i hope when you login you will be giving url like http://adminhost:adminport/console. Now this adminport is the port on which admin server is running. If not, then check config.xml file.
Thanks
Ravi Jegga

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?
 >> >
 >

Trying to run the SOA/BPM managed server withOUT running the Admin server

(This is for demo/development purposes... Using 11.1.1.4 in Windows 7 with 4gb)
Because of memory constrains I am trying to run the BPM/workspaces application without needing the Admin to be running.
When they both run, I can use the credentials I create with the Admin server but the response time is prohibitive and all my memory is used...
It seems to run much faster when only the bpm managed server is running but then I cannot login ...
So my question is simply: Whats the easiest way to set it up so I can use credentials elsewhere without requiring the admin server to be running?
( I could connect to an OID instance I have outside this server or the seeded demo they refer to in other posts ... but do these also require the admin server to be running???)
aTdHvAaNnKcSe ! (thanks IN advance)
Claudio
Edited by: clichten on Aug 20, 2011 9:35 AM

I don't know if what you want is possible. Only did a suggestion that works fine for me. I'm running SOA Suite and BPM Suite 11.1.1.5 on WLS 10.3.5
Configure a new WLS domain and see if the BPM Dev template is available in your version.
I've tuned my startup script (setSOADomainEnv.cmd) as follows:
set JAVA_OPTIONS=%JAVA_OPTIONS%
set DEFAULT_MEM_ARGS=-Xms512m -Xmx1024m
set PORT_MEM_ARGS=-Xms1536m -Xmx1536m
if "%JAVA_VENDOR%" == "Oracle" goto OracleJVM
set DEFAULT_MEM_ARGS=%DEFAULT_MEM_ARGS% -XX:PermSize=128m -XX:MaxPermSize=512m
set PORT_MEM_ARGS=%PORT_MEM_ARGS% -XX:PermSize=256m -XX:MaxPermSize=512m
Use visualvm that's available from your jdk/bin directory to monitor your jvm and optimize it accordingly
Regards,
Melvin

Error to start the Admin Server of WebLogic

Hi to everybody:
I have a problem when I running the Admin Server of WebLogic, this is the message:
** Setting up SOA specific environment for win...
PATH=C:\Oracle\MIDDLE~1\HOME_1~1\patch_wls1033\profiles\default\native;C:\Oracle\MIDDLE~1\HOME_1~1\patch_oepe1033\profiles\default\native;C:\Oracle\MIDDLE~1\HOME_1~1\patch_ocp353\profiles\default\native;C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\HOME_1~1\modules\ORGAPA~1.1\bin;C:\Oracle\MIDDLE~1\HOME_1~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\HOME_1~1\JDK160~1\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Rational\common;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\server\native\win\32\oci920_8;C:\Oracle\Middleware\home_11R1\Oracle_SOA1\soa\thirdparty\edifecs\XEngine\bin
USER_MEM_ARGS=-Xms768m -Xmx1536m -XX:PermSize=256m -XX:MaxPermSize=512m
JAVA_OPTIONS= -Xverify:none
** End SOA Specific environment setup for win.
** SOA specific environment is already set. Skipping ...
JAVA Memory arguments: -Xms768m -Xmx1536m -XX:PermSize=256m -XX:MaxPermSize=512m
WLS Start Mode=Development
CLASSPATH=C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\server\ext\jdbc\oracle\11g\ojdbc6dms.jar;C:\Oracle\Middleware\home_11R1\Oracle_SOA1\soa\modules\user-patch.jar;C:\Oracle\Middleware\home_11R1\Oracle_SOA1\soa\modules\soa-startup.jar;;C:\Oracle\MIDDLE~1\HOME_1~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\HOME_1~1\patch_oepe1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\HOME_1~1\patch_ocp353\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\HOME_1~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\HOME_1~1\modules\features\weblogic.server.modules_10.3.3.0.jar;C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\HOME_1~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\HOME_1~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\Middleware\home_11R1\Oracle_SOA1\soa\modules\oracle.soa.common.adapters_11.1.1\oracle.soa.common.adapters.jar;C:\Oracle\MIDDLE~1\HOME_1~1\ORACLE~1\soa\modules\commons-cli-1.1.jar;C:\Oracle\MIDDLE~1\HOME_1~1\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\Oracle\MIDDLE~1\HOME_1~1\ORACLE~1\modules\oracle.xdk_11.1.0\xsu12.jar;C:\Oracle\MIDDLE~1\HOME_1~1\modules\features\weblogic.server.modules.xquery_10.3.1.0.jar;C:\Oracle\Middleware\home_11R1\Oracle_SOA1\soa\modules\db2jcc4.jar;C:\Oracle\MIDDLE~1\HOME_1~1\USER_P~1\domains\domain1\config\soa-infra;C:\Oracle\Middleware\home_11R1\Oracle_SOA1\soa\modules\fabric-url-handler_11.1.1.jar;C:\Oracle\Middleware\home_11R1\Oracle_SOA1\soa\modules\quartz-all-1.6.5.jar;C:\Oracle\Middleware\home_11R1\Oracle_SOA1\soa\modules\oracle.soa.fabric_11.1.1\oracle.soa.fabric.jar;C:\Oracle\Middleware\home_11R1\Oracle_SOA1\soa\modules\oracle.soa.adapter_11.1.1\oracle.soa.adapter.jar;C:\Oracle\Middleware\home_11R1\Oracle_SOA1\soa\modules\oracle.soa.b2b_11.1.1\oracle.soa.b2b.jar;C:\Oracle\MIDDLE~1\HOME_1~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\server\lib\xqrl.jar
PATH=C:\Oracle\MIDDLE~1\HOME_1~1\patch_wls1033\profiles\default\native;C:\Oracle\MIDDLE~1\HOME_1~1\patch_oepe1033\profiles\default\native;C:\Oracle\MIDDLE~1\HOME_1~1\patch_ocp353\profiles\default\native;C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\HOME_1~1\modules\ORGAPA~1.1\bin;C:\Oracle\MIDDLE~1\HOME_1~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\HOME_1~1\JDK160~1\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Rational\common;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\server\native\win\32\oci920_8;C:\Oracle\Middleware\home_11R1\Oracle_SOA1\soa\thirdparty\edifecs\XEngine\bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
Starting WLS with line:
C:\Oracle\MIDDLE~1\HOME_1~1\JDK160~1\bin\java -client -Xms768m -Xmx1536m -XX:PermSize=256m -XX:MaxPermSize=512m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\server -Ddomain.home=C:\Oracle\MIDDLE~1\HOME_1~1\USER_P~1\domains\domain1 -Dcommon.components.home=C:\Oracle\MIDDLE~1\HOME_1~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=C:\Oracle\MIDDLE~1\HOME_1~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\HOME_1~1\USER_P~1\domains\domain1\config\FMWCON~1 -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\HOME_1~1\USER_P~1\domains\domain1\config\FMWCON~1\servers\AdminServer -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\HOME_1~1\USER_P~1\domains\domain1\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\HOME_1~1\USER_P~1\domains\domain1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\HOME_1~1\USER_P~1\domains\domain1\config\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\HOME_1~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\HOME_1~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dsoa.archives.dir=C:\Oracle\Middleware\home_11R1\Oracle_SOA1\soa -Dsoa.oracle.home=C:\Oracle\Middleware\home_11R1\Oracle_SOA1 -Dsoa.instance.home=C:\Oracle\MIDDLE~1\HOME_1~1\USER_P~1\domains\domain1 -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 -Djava.protocol.handler.pkgs="oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol" -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=C:\Oracle\MIDDLE~1\HOME_1~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=C:\Oracle\Middleware\home_11R1\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=C:\Oracle\Middleware\home_11R1\Oracle_SOA1 -Dums.oracle.home=C:\Oracle\Middleware\home_11R1\Oracle_SOA1 -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\HOME_1~1\patch_wls1033\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\HOME_1~1\patch_oepe1033\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\HOME_1~1\patch_ocp353\profiles\default\sysext_manifest_classpath weblogic.Server
Error occurred during initialization of VM
Could not reserve enough space for object heap
I have a computer with Windows 7 Professional 64-bits and 4 Gb of RAM
Regards

Looks like the jvm is not able to find contiguous memory space, can u try with jrokit jvm?

"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.

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.

Connecting to the admin server via SSL

Hi there,
I'm trying to connect to our Admin server in a testing environment in a DMZ from another linux box. We've tried the same method on previous testing environments and its worked ok with a .conf and .key file.
java -Dssl.debug=true -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeySore=DemoTrust weblogic.WLST
wls:/offline> connect(userConfigFile='../acols_cobb.conf', userKeyFile='../acols_cobb.key', url='https://cobb.workcover.dmz:9191')
Connecting to https://cobb.workcover.dmz:9191 with userid system ...
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 8620279>
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will NOT be Muxing>
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <write SSL_20_RECORD>
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <4600242 SSL3/TLS MAC>
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <4600242 received HANDSHAKE>
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <4600242 SSL3/TLS MAC>
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <4600242 received HANDSHAKE>
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 50788157593152036917613181257703108893
Issuer:C=US, ST=MyState, L=MyTown, O=MyOrganization, OU=FOR TESTING ONLY, CN=CertGenCAB
Subject:C=US, ST=MyState, L=MyTown, O=MyOrganization, OU=FOR TESTING ONLY, CN=cobb
Not Valid Before:Thu May 21 11:13:10 EST 2009
Not Valid After:Wed May 22 11:13:10 EST 2024
Signature Algorithm:MD5withRSA
>
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
<Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 50788157593152036917613181257703108893
Issuer:C=US, ST=MyState, L=MyTown, O=MyOrganization, OU=FOR TESTING ONLY, CN=CertGenCAB
Subject:C=US, ST=MyState, L=MyTown, O=MyOrganization, OU=FOR TESTING ONLY, CN=cobb
Not Valid Before:Thu May 21 11:13:10 EST 2009
Not Valid After:Wed May 22 11:13:10 EST 2024
Signature Algorithm:MD5withRSA
>
<Dec 31, 2009 11:21:27 AM EST> <Warning> <Security> <BEA-090542> <Certificate chain received from cobb.workcover.dmz - 203.82.216.131 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>

Hi,
You are not able to establish connection with the Admin server because there is no trust between the two.
D:\weblogic\wls924\user_projects\domains\saml_1.1_source_post>java -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.CustomTrustKeyStoreType="JKS" -Dweblogic.security.TrustKeyStore=CustomTrust -Dweblogic.security.CustomTrustKeyStoreFileName="D:/weblogic/wls924/user_projects/domains/saml_1.1_source_post/trust.jks" weblogic.WLST
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> connect()
Please enter your username [weblogic] :weblogic
Please enter your password [weblogic] :
Please enter your server URL [t3://localhost:7001] :t3s://localhost:7002
Connecting to t3s://localhost:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'sam
l_1.1_source_post'.
wls:/saml_1.1_source_post/serverConfig>
Regards,
Puneeth P

Cann't connect to the Admin Server!

Hi,everyone:
when I "startconsole",error appears:
"Cann't connect to Admin Server:http://myhostname.mydomain:port number,the URL is not correct or the server is not running "
how can I resolve this problem?
Thanks

This may seem like a dumb question, but
Is the Admin Server running on myhostname.mydomain:port number?

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 could not be reached

Dear All,
I have oracle weblogic server running on red hat enterprise Linux, with one managed server. I created a self-signed certificate to access the admin server using SSL connection, after creating the certificate and start running the domain, The admin server run fine, but when i start running the managed server using
$ ./startManagedWebLogic.sh osb_server1 https://server_ip:7006 i got that error, " The admin server could not be reached on https://server_ip:7006
and the managed server running independence of admin server, as well as admin server can not establish jmx:t3 connection with the managed server on its SSL port
also in admin server log i got this error
<Sep 30, 2013 6:51:00 PM EET> <Warning> <JMX> <BEA-149504> <The adminstration server was unable to establish JMX Connectivity with the osb_server1 at the JMX Service URL of service:jmx:t3://172.17.11.13:8011/jndi/weblogic.management.mbeanservers.runtime.>
how can i resolve this error?
thanks in advanced

Hi John,
Thanks. Notable errors in this log are:
Failed to connect.[Root Cause: Connection refused ] com.hyperion.css.spi.util.jndi.pool.JNDIConnectionPool.validateSocketConnection(Unknown Source)
Native Directory is not reachable. Will try to re-connect after 3 seconds... com.hyperion.css.spi.CSSManager.getProviderInstance(Unknown Source)
Attempting to connect to Native Directory: Retry Count: 10 com.hyperion.css.spi.CSSManager.getProviderInstance(Unknown Source)
Failed to connect to native directory. com.hyperion.css.spi.CSSManager.getProviderInstance(Unknown Source)
Any ideas?
Thanks.
Edited by: 960369 on 21-Sep-2012 02:56
Edited by: 960369 on 21-Sep-2012 03:33

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.

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

Similar Messages

Maybe you are looking for