Domain wide administration port and node manager

I need a little help understanding how to properly configure the domain-wide
administration port in a clustered domain using node manager. After I enabled
the port in my domain, node manager will no longer start the managed servers
running on the same box as the domain's admin server. I don't have problems
starting remote managed servers. I see the problem but I don't know how to
fix it.
<Error> <Configuration Management> <BEA-150019> <The address provided to
get to the admin server (https://<host>@port) resolves to a managed server
local address (host@port) rather than a remote address as expected, or the
local managed server port might already be in use if you have setup domain
wide admin port, please check the configuration and correct the problem.>
The host I'm specifying is the host of my admin server, the port is the domain-wide
administration port. I don't get this error when starting my remote managed
servers, only the managed servers running on the same box as the admin server.
Grant

Cause might The managed server was given a URL to boot from that resolves to a managed server address. If the managed server is running on the same machine as the admin server, this can be caused by a failure to specify a unique admin port.
Inspect the address:port provided to the managed server from which to boot. This address should be changed to reference the admin server rather than resolving to a managed server. If the managed server is running on the same machine as the admin server, you must differentiate them by providing a unique port number.
Now we log a clear message that prints something like ,
The address provided to get to the admin server x.x.x.x resolves to a m
anaged server local address x.x.x.x:nnnn rather than a remote address as
expected, or the local managed server port might already be in use if you
have setup domain wide admin port, please check the configuration and correct
the problem.
Regards,
Prasanna Yalam

Similar Messages

Datasync and domain Wide administration port problem

Hi,
After enabling domain wide administration port in WLP 8.1, wee start to see following
exception on our managed servers log file. This happes in every mananaged server.
Datasync.war is deployed only in adminserver as the manual says. We see this error
every time we boot our managed servers.
Any ideas?
####<Nov 3, 2003 11:00:27 PM EET> <Error> <DataSync> <demomachine> <ManagedServer1>
<main> <<anonymous>> <> <BEA-400618> <Creation of the Master Data Repository failed.
Application data will not be available to services. Correct the problem and redeploy
the application.
java.lang.SecurityException: User <anonymous> does not have access to the administrator
port.
Regards, Mika

Cause might The managed server was given a URL to boot from that resolves to a managed server address. If the managed server is running on the same machine as the admin server, this can be caused by a failure to specify a unique admin port.
Inspect the address:port provided to the managed server from which to boot. This address should be changed to reference the admin server rather than resolving to a managed server. If the managed server is running on the same machine as the admin server, you must differentiate them by providing a unique port number.
Now we log a clear message that prints something like ,
The address provided to get to the admin server x.x.x.x resolves to a m
anaged server local address x.x.x.x:nnnn rather than a remote address as
expected, or the local managed server port might already be in use if you
have setup domain wide admin port, please check the configuration and correct
the problem.
Regards,
Prasanna Yalam

Domain-wide administration port?

Hi,
I tried to start a cluster of 2 servers across 2 physical machines, I got error and server starting failed:
"Starting Managed Servers in Standby mode requires the domain-wide administration port."
My topology is as following:
Domain A is created in machine A and copy to machine B:
Machine A: admin serverr at port 8001. Managed server at port 8088 of cluster1.
Machine B: Managed server at port 8088 of the same cluster1.
What is wrong? Why I cannot start cluster? Why I got error " need domain-wide administration port"? What is "domain-wide administration port"? Why my created domain admin server at Machine A didn't work?
Your prompt help is highly appreciated. I am waiting for your help.
Thank you in advance

Hi,
First of all the domain-wide administration port enables you to start a WebLogic Server instance in STANDBY state. It also allows you to separate administration traffic from application traffic in your domain.
so check in ur console whether u have specified the start up mode as STANDBY.if so change it to Running and try restarting the server:-
You can do that by chking the below link:-
http://e-docs.bea.com/wls/docs92/ConsoleHelp/taskhelp/startstop/SpecifyAStartupMode.html.
Domain-wide administration port is used when you have configured ssl for ur servers. Refer http://e-docs.bea.com/wls/docs103/ConsoleHelp/taskhelp/domainconfig/EnableTheDomainwideAdministrationPort.html for more info.

WLST with Domain-wide Admin Port configured

Anybody tried WLST with Domain-wide Administration Port (DAP) turned on?
Is there a set of instuctions to change over smoothly to using the DAP URL instead
of the plain-text URL?
Thanks,
-RAJ

Hello Raj, to use DAP start WLST as
java -Dweblogic.security.SSL.ignoreHostnameVerification=true
-Dweblogic.security.TrustKeyStore=DemoTrust weblogic.WLST
if you are using the demonstration SSL keys and certificates
Thanks,
-satya
Raj Sesetti wrote:
Anybody tried WLST with Domain-wide Administration Port (DAP) turned on?
Is there a set of instuctions to change over smoothly to using the DAP URL instead
of the plain-text URL?
Thanks,
-RAJ

Reg: node and node manager

Hi to all
iam new to this forum, iam new administrator in weblogic plese help me.....
what is diference between node and node manager?
Thanks & Regardes
Ashok

Hi Ashok,
Node term usually we use for a Physical Box.
Nodemanager is a WebLogic Specific Java program which can be used to Manage a Remote Manage Server. Every Machine (Machine is a Logical name which represents a Physical box where Managed server is running) must have a NodeManager. AdminServer usually interacts with NodeManager to give start or stop Servers instructions to the Nodemanager, NodeManager program runs & resides in the same Managed Server Box...so it actually follows AdminServer's Instructions.
Nodemanager gets the Latest Configuration files from AdminServer while starting a Server in the physical box. or if AdminServer is not running at the time of starting a Managed Server then ... nodemanager uses the "msi-config.xml" file to provide to managed Servers while starting them.
Please refer to the below Post: http://weblogic-wonders.com/weblogic/2010/04/28/weblogic-clustering-in-remote-boxes/ to know what is the need of NodeManager and how to configure it.
To know in-depth about Nodemanager please refer to James Bayers....Post: http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
Thanks
Jay Sensharma

Oracle HTTP Server and Node Manager

Hi,
I installed Oracle HTTP Server with Node Manager. I set "CrashRecoveryEnabled=true" in the nodemanager.properties. It works fine when I reboot the machine, but when I kill the root process (kill -9), the new process can not be started as the previous process does not have enough time to die and still uses the ports. I tried to run "nmGenBootStartupProps" in wlst, or set the
RestartMax=2
RestartDelaySeconds=5
variables in "[domain_name]/servers/[server_name]/data/nodemanager/startup.properties" - no success.
Any ideas, how to set the number of retries and the delay between restarts?
Versions:
Oracle HTTP Server: version="12.1.3.0.0"
java version "1.7.0_79"
OHS log:
[2015-05-04T11:43:48.0653+02:00] [OHS] [NOTIFICATION:16] [OHS-9999] [mod_weblogic.c] [host_id: dev-oep-soalb-1] [host_addr: 192.168.0.226] [pid: 18651] [tid: 140166670751552] [user: app] [VirtualHost: main] WebLogic Server Plugin version 12.1.3 <WLSPLUGINS_12.1.3.0.0_LINUX.X64_140421.1459>
[2015-05-04T11:43:48.0854+02:00] [OHS] [NOTIFICATION:16] [OHS-9999] [core.c] [host_id: dev-oep-soalb-1] [host_addr: 192.168.0.226] [pid: 18651] [tid: 140166670751552] [user: app] [VirtualHost: main] Oracle-HTTP-Server-12c/12.1.3.0.0 (Unix) mod_ssl/12.1.3.0.0 OtherSSL/0.0.0 mod_plsql/11.1.1.0.0 configured -- resuming normal operations
[2015-05-04T11:48:53.9584+02:00] [OHS] [INCIDENT_ERROR:32] [OHS-9999] [worker.c] [host_id: dev-oep-soalb-1] [host_addr: 192.168.0.226] [pid: 18838] [tid: 140103489120064] [user: app] [VirtualHost: main] (98)Address already in use: make_sock: could not bind to address 192.168.0.226:80
[2015-05-04T11:48:53.9585+02:00] [OHS] [INCIDENT_ERROR:20] [OHS-9999] [worker.c] [host_id: dev-oep-soalb-1] [host_addr: 192.168.0.226] [pid: 18838] [tid: 140103489120064] [user: app] [VirtualHost: main] no listening sockets available, shutting down
[2015-05-04T11:48:53.9585+02:00] [OHS] [ERROR:32] [OHS-9999] [core.c] [host_id: dev-oep-soalb-1] [host_addr: 192.168.0.226] [pid: 18838] [tid: 140103489120064] [user: app] [VirtualHost: main] Unable to open logs
Node Manager log:
<May 4, 2015 11:37:50 AM CEST> <INFO> <Loading domains file: /opt/app/soalb_domain/nodemanager/nodemanager.domains>
<May 4, 2015 11:40:18 AM CEST> <INFO> <Loading identity key store: FileName=/opt/app/soalb_domain/security/DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
<May 4, 2015 11:40:18 AM CEST> <INFO> <Loaded NodeManager configuration properties from '/opt/app/soalb_domain/nodemanager/nodemanager.properties'>
<May 4, 2015 11:40:18 AM CEST> <INFO> <Node manager v12.1.3 #1604337>
<May 4, 2015 11:40:18 AM CEST> <INFO> <soalb_domain> <soalb_server1> <Startup configuration properties loaded from "/opt/app/soalb_domain/servers/soalb_server1/data/nodemanager/startup.properties">
<May 4, 2015 11:40:19 AM CEST> <INFO> <Secure socket listener started on port 5556, host localhost/127.0.0.1>
<May 4, 2015 11:43:53 AM CEST> <INFO> <soalb_domain> <soalb_server1> <The server 'soalb_server1' is running now.>
<May 4, 2015 11:48:53 AM CEST> <INFO> <soalb_domain> <soalb_server1> <The server 'soalb_server1' with process id 18672 is no longer alive; waiting for the process to die.>
<May 4, 2015 11:48:53 AM CEST> <INFO> <soalb_domain> <soalb_server1> <Server failed so attempting to restart (restart count = 1)>
<May 4, 2015 11:48:54 AM CEST> <SEVERE> <soalb_domain> <soalb_server1> <Unexpected error while monitoring server>
java.io.IOException: Failed to start the server soalb_server1
Check log file /opt/app/soalb_domain/system_components/OHS/ohs_nm.log
Check log file /opt/app/soalb_domain/servers/soalb_server1/logs/soalb_server1.log
        at oracle.ohs.plugin.nodemanager.OhsProcessManagementPlugin$ProcessImpl.buildIoException(Unknown Source)
        at oracle.ohs.plugin.nodemanager.OhsProcessManagementPlugin$ProcessImpl.start(Unknown Source)
        at weblogic.nodemanager.server.DecoratedSystemComponentManager$DecoratedProcess.start(DecoratedSystemComponentManager.java:129)
        at weblogic.nodemanager.server.ServerMonitor.startProcess(ServerMonitor.java:441)
        at weblogic.nodemanager.server.ServerMonitor.runMonitor(ServerMonitor.java:406)
        at weblogic.nodemanager.server.ServerMonitor.run(ServerMonitor.java:295)
        at java.lang.Thread.run(Thread.java:744)
ohs_nm.log:
<2015-05-04 11:48:53> <INFO> <OHS-0> <The server 'soalb_server1' with process id 18672 is no longer alive; waiting for the process to die.>
<2015-05-04 11:48:53> <INFO> <OHS-0> <Server failed so attempting to restart (restart count = 1)>
<2015-05-04 11:48:53> <INFO> <OHS-4018> <Starting server soalb_server1>
<2015-05-04 11:48:53> <INFO> <OHS-0> <Running /opt/app/ohs12c/wlserver/../ohs/bin/httpd.sh httpd.worker -k start -f /opt/app/soalb_domain/config/fmwconfig/components/OHS/instances/soalb_server1/httpd.conf>
<2015-05-04 11:48:53> <INFO> <OHS-0> <[Mon May 04 11:48:53 2015] [warn] Errors will be logged into /opt/app/soalb_domain/servers/soalb_server1/logs/soalb_server1.log>
<2015-05-04 11:48:54> <INFO> <OHS-0> </opt/app/ohs12c/wlserver/../ohs/bin/httpd.sh httpd.worker -k start -f /opt/app/soalb_domain/config/fmwconfig/components/OHS/instances/soalb_server1/httpd.conf: exit status = 1>
<2015-05-04 11:48:54> <INFO> <OHS-4005> <Check the instance log file for more information: /opt/app/soalb_domain/servers/soalb_server1/logs/soalb_server1.log>
<2015-05-04 11:48:54> <SEVERE> <OHS-0> <Failed to start the server soalb_server1>
<2015-05-04 11:48:54> <SEVERE> <OHS-0> <Unexpected error while monitoring server>
Node Manager properties:
#Wed Apr 29 18:31:26 CEST 2015
#Node manager properties
#Wed Apr 29 17:18:21 CEST 2015
DomainsFile=/opt/app/soalb_domain/nodemanager/nodemanager.domains
LogLimit=0
PropertiesVersion=12.1.3
AuthenticationEnabled=true
NodeManagerHome=/opt/app/soalb_domain/nodemanager
JavaHome=/opt/app/jdk1.7.0_79
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=localhost
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=true
LogCount=1
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=5000
CrashRecoveryEnabled=true
StartScriptEnabled=true
LogFile=/opt/app/soalb_domain/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
Startup properties:
#SSLArguments=-Dweblogic.security.SSL.ignoreHostnameVerification\=false -Dweblogic.ReverseDNSAllowed\=false
RestartMax=2
RestartDelaySeconds=5
FileTimeSpan=24
RestartInterval=3600
FileTimeSpanFactor=3600000
RotatedFileCount=7
RotationType=bySize
#AdminURL=http\://192.168.0.224\:7001
NumberOfFilesLimited=true
AutoRestart=true
RotationTimeStart=00\:00
FileSizeKB=500
Regards,
András

To deploy your FMX you need AS 10.1.2 Forms installed, and then you can use AS control or Forms server configuration file.
For more information regarding FMX deployment, refer to http://download.oracle.com/docs/cd/B14099_19/web.1012/b14032/toc.htm
Regards,
Preet

Accessing an EJB 3.0 Enterprise Bean and Node Manager

Hi to all
I have got a problem in using Local(Remote) EJB Interface in Weblogic. I use Node Manager.
I have two servers:
1. AdminServer (working on port 7001)
2. Server1 (working on port 7003 under node manager control)
I have one EAR application file. This file contains jars with ejb 3.0. One jar called jarnumber1.jar is deployed on AdminServer. Second jar called jarnumber2.jar id deployed on Server1.
jarnumber1.jar constains EJBBean1 class.
jarnumber2.jar constains EJBBean2 class.
I want call EJBBean2 from EJBBean1 but I can't. I got exception 'NamingException'.
Example source code:
@Stateless(mappedName = "EJBBean1")
public class EJBBean1implements EJBBean1Remote {
@EJB private EJBBean2Remote eJBBean2Remote ; //injection doesn't work
I also tried method described here: http://middlewaremagic.com/weblogic/?p=5665 but it doesn't work.
AminServer has own JNDI Tree and Server1 has own JNDI Tree. It's seems to be that EJBBean1 can't see EJBBean2 from second JDNI tree.
Pleas help me.
With Regards,
ZK

Please try the following code:
HelloEJBBean.java:
@Stateless(name="Hello")
@Remote(value={Hello.class})
public class HelloEJBBean implements Hello { ... }
hello.jsp:
Context ctx = new InitialContext();
Hello h = (Hello)ctx.lookup("ejb/Hello");
web.xml:
<ejb-ref>
<ejb-ref-name>ejb/Hello</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<remote>fi.kronodoc.test.model.Hello</remote>
</ejb-ref>
i think you should also define jndi mappings for the references in orion-ejb-jar.xml and orion-web.xml but for some reason it seems to be working also without these.

Difference between console port and dedicated management port

Can someone explain what the difference is between the console port and the dedicated management port(fa0) , on a Cisco 2960s switch.
Thank You.

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
A console port is special for two reasons. First, it's "known" to the system as its console port which means the system will send status information to it, and often treat it special when accepting input. Second, the console port is generally wired as a serial port. (It also normally doesn't have an IP address.)
The console port was intended for where the system operator controls the system from, usually nearby (physically). (Console ports are/were used for any computer based system.)
Management ports are generally for remote management using an Ethernet port. On older switches/routers, a device might be configured to use an ordinary Ethernet port for this purpose. On newer switches/routers, a Ethernet port is provided for this purpose. For these, the device may actually use different hardware for port and might treat it internally differently. For example, often the Ethernet management port is only FE, it may not have ASIC support for high speed switching, and it might be in it's own predefined VRF. Generally, a management port will have an IP address, but different from IP address spaces used by other hosts.
Out-of-the-box, a console port will allow you to configure the device, but a management port will often require some additional configuration.

How can I disable administration port?

Hello
By a mistake I enabled the domain-wide administration port, and now I can't log into the console.
Which file can I edit to disable the domain-wide administration port, without using the console?
Thanks!

Never mind. I finally managed to use the console again...
Edited by ejac at 12/07/2007 5:42 AM

Use of domain administration port breaks session access?

WLS 8.1.2;
          We have a third-party app deployed in a pretty basic cluster setup (two managed servers, each on a separate machine). When accessing the main web app, it works fine. If/when we enable the domain-wide administration port (DAP)(after enabling SSL on each server), we can no longer access the application - we get the exception shown below.
          Note - if we shut down one of the two managed servers with DAP enabled, the app works. If we disable DAP and run both managed servers using SSL, the app works.
          What have done wrong?
          tia,
          Rick
          <snip>
          ####<Jun 9, 2005 10:26:49 AM EDT> <Error> <HTTP Session> <OYARSA4> <ep01> <ExecuteThread: '9' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100060> <An unexpected error occurred while retrieving the session for Web application: ServletContext(id=247422,name=eprovision-client,context-path=/eprovision-client).
          java.lang.SecurityException: User <anonymous> does not have access to the administrator port.
               at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
               at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
               at weblogic.cluster.replication.ReplicationManager_812_WLStub.create(Unknown Source)
               at weblogic.cluster.replication.ReplicationManager.trySecondary(ReplicationManager.java:1064)
               at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:997)
               at weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:391)
               at weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:376)
               at weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:370)
               at weblogic.servlet.internal.session.ReplicatedSessionData.<init>(ReplicatedSessionData.java:95)
               at weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:304)
               at weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImpl.java:2472)
               at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:2169)
               at weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction.run(SecurityModule.java:637)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
               at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
               at weblogic.servlet.security.internal.SecurityModule.getUserSession(SecurityModule.java:612)
               at weblogic.servlet.security.internal.FormSecurityModule.stuffSession(FormSecurityModule.java:404)
               at weblogic.servlet.security.internal.FormSecurityModule.checkUserPerm(FormSecurityModule.java:391)
               at weblogic.servlet.security.internal.SecurityModule.beginCheck(SecurityModule.java:197)
               at weblogic.servlet.security.internal.FormSecurityModule.checkA(FormSecurityModule.java:181)
               at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:145)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3539)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          Caused by: java.lang.SecurityException: User <anonymous> does not have access to the administrator port.
               at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:910)
               at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:844)
               at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:222)
               at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:794)
               at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:570)
               at weblogic.socket.SSLFilter.dispatch(SSLFilter.java:281)
               at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:105)
               at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
          </snip>

An unexpected error occurred while retrieving the session for Web application: logContext.
          Cause might Failed to retrieve the session from persistent store.
          pl. check your configuration
          Prasanna Yalam

Can i use single node manager with two weblogic domain?

I am very new to weblogic and node manager.
i had created two domains in weblogic. (single node manger).
Can i connect both domains with same nodemanger?
How to do this?

The node manager uses a nodemanager.domains file to determine which domains it manages, for example,
domain_name=/path_to_domain/domain_name
other_domain_name=/path_to_other_domain/other_domain_name
This file can be found in the NODEMANAGER_HOME, that you specified when starting the node manager (startNodeManager - NODEMGR_HOME="${WL_HOME}/../oracle_common/common/nodemanager")
When you are running the domain on multiple machines you have to enroll the node manager into the domain (http://docs.oracle.com/cd/E23943_01/web.1111/e13813/reference.htm#i1065827)
A scripted example can be found here: Middleware Snippets: Automate WebLogic Installation and Configuration. The Node Manager administration guide can be found here: Oracle&reg; Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server 11g Release 1 (10.3.6) -….

Enabled WebLogic Server domain administration port, now can't connect

I am having troubles in an OID 11g cluster using new custom identity and Java standard trust, so setup a basic lab server with WLS 10.3.3 admin server and one managed server. All was well.
I enabled the domain-wide admin port (9002) and can access the admin server console via https://localhost:9002/em.
I am unable to start the managed server with ADMIN_URL of t3s://localhost:9002 or https://localhost:9002 or using the fully-qualified host name. It says "There is no server running at t3s://localhost:9002" for example.
I enabled SSL debugging, and it just "gives up" quietly, deciding there is no SSL trust:
<Mar 30, 2011 7:38:51 PM EDT> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
<Mar 30, 2011 7:38:51 PM EDT> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: -
33322804764672255361779797406005394240
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=myhostname.acme.com
Not Valid Before:Sun Mar 27 17:37:38 EDT 2011
Not Valid After:Sat Mar 28 17:37:38 EDT 2026
Signature Algorithm:MD5withRSA
>
<Mar 30, 2011 7:38:51 PM EDT> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number:
46914133237969612308202465797198785159
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=CertGenCAB
Not Valid Before:Thu Oct 24 11:54:45 EDT 2002
Not Valid After:Tue Oct 25 11:54:45 EDT 2022
Signature Algorithm:MD5withRSA
>
<Mar 30, 2011 7:38:51 PM EDT> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 0>
<Mar 30, 2011 7:38:51 PM EDT> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: -
33322804764672255361779797406005394240
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=myhostname.acme.com
Not Valid Before:Sun Mar 27 17:37:38 EDT 2011
Not Valid After:Sat Mar 28 17:37:38 EDT 2026
Signature Algorithm:MD5withRSA
>
<Mar 30, 2011 7:38:51 PM EDT> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number:
46914133237969612308202465797198785159
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=CertGenCAB
Not Valid Before:Thu Oct 24 11:54:45 EDT 2002
Not Valid After:Tue Oct 25 11:54:45 EDT 2022
Signature Algorithm:MD5withRSA
>
<Mar 30, 2011 7:38:51 PM EDT> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 0>
<Mar 30, 2011 7:38:51 PM EDT> <Debug> <SecuritySSL> <BEA-000000> <Trust status (0): NONE>
<Mar 30, 2011 7:38:51 PM EDT> <Debug> <SecuritySSL> <BEA-000000> <Performing hostname validation checks: localhost>
<Mar 30, 2011 7:38:51 PM EDT> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Mar 30, 2011 7:38:51 PM EDT> <Debug> <SecuritySSL> <BEA-000000> <873462440 SSL3/TLS MAC>
<Mar 30, 2011 7:38:51 PM EDT> <Debug> <SecuritySSL> <BEA-000000> <873462440 received HANDSHAKE>
<Mar 30, 2011 7:38:51 PM EDT> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHelloDone>
I set flags like this: -Dweblogic.security.TrustKeyStore=DemoTrust -Dweblogic.security.SSL.ignoreHostnameVerification=true , no success.
Any assistance you could provide would be much appreciated! Thank you.

More info: I'm using the default DemoTrust setup.
Correction: I can connect to the console at https://localhost:9002/console (not /em).

Administration port - network channel for admin traffic

I am trying to configure a separate channel for Administration traffic on weblogic. I followed the oracle docos and configured the SSL, domain wide admin port, server listen address, ‘admin’ channel.
The issue is admin traffic in not happening through the newly created channel.
L2 network is not getting used. I can’t see any activity in the monitoring tab of new Channel. Also the netstat is showing that the port 9101/9102 is getting used on the 192.168.100.218 and not on 10.254.252.849.
I also tried by setting up the newly created channel weight as 51, but no luck.
Is JMX connectivity related to admin channel?
Any help is highly appreciated. Thanks.
Ipconfig:
Admin: adminserver701.mycompany.internal, 192.168.100.238, 10.254.252.808
Managed: appserver701.mycompany.internal, :192.168.100.218, 10.254.252.849
Domain wide admin port: 9101
Admin:
Listen address –> adminserver701.mycompany.internal
Channel –> admin -> 10.254.252.808/9101
Startup -> -Dweblogic.admin.ListenAddress=admin://10.254.252.808:9101
Managed:(appserver701)
Listen address –> appserver701.mycompany.internal
Admin port override: 9102
Channel –> admin -> 10.254.252.849/9102
Startup -> -Dweblogic.admin.ListenAddress=admin://10.254.252.849:9102
AdminServer Logs:
####<Feb 18, 2013 1:53:33 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159613346> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://adminserver701.mycompany.internal:9101/jndi/weblogic.management.mbeanservers.runtime .>
####<Feb 18, 2013 1:53:33 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159613353> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://adminserver701.mycompany.internal:9101/jndi/weblogic.management.mbeanservers.edit .>
####<Feb 18, 2013 1:53:33 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159613367> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://adminserver701.mycompany.internal:9101/jndi/weblogic.management.mbeanservers.domainruntime .>
####<Feb 18, 2013 1:53:36 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159616699> <BEA-002613> <Channel "DefaultAdministration" is now listening on 192.168.100.238:9101 for protocols admin, ldaps, https.>
####<Feb 18, 2013 1:53:36 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159616700> <BEA-002613> <Channel "Channel-0" is now listening on 10.254.252.808:9101 for protocols admin, ldaps, https.>
####<Feb 18, 2013 1:55:12 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <cd259038c7dcf5a8:-26ac3ba0:13ceb6f767d:-8000-000000000000001a> <1361159712920> <BEA-002613> <Channel "Default" is now listening on 192.168.100.238:7001 for protocols iiop, t3, ldap, snmp, http.>
####<Feb 18, 2013 1:55:12 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <cd259038c7dcf5a8:-26ac3ba0:13ceb6f767d:-8000-000000000000001a> <1361159712920> <BEA-002613> <Channel "DefaultSecure" is now listening on 192.168.100.238:7002 for protocols iiops, t3s, ldaps, https.>
ManagedServer Logs:
####<Feb 18, 2013 2:54:19 PM EST> <Info> <JMX> <appserver701.mycompany.internal> <adp_ms01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361163259911> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://appserver701.mycompany.internal:9102/jndi/weblogic.management.mbeanservers.runtime .>
####<Feb 18, 2013 2:54:20 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361163260350> <BEA-002613> <Channel "Channel-0" is now listening on 10.254.252.849:9102 for protocols admin, CLUSTER-BROADCAST-SECURE, ldaps, https.>
####<Feb 18, 2013 2:54:20 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361163260350> <BEA-002613> <Channel "DefaultAdministration" is now listening on 192.168.100.218:9102 for protocols admin, CLUSTER-BROADCAST-SECURE, ldaps, https.>
####<Feb 18, 2013 2:54:58 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <d3208ed6c2482016:-46ac5fed:13ceba69a8e:-7ffe-000000000000000e> <1361163298045> <BEA-002613> <Channel "DefaultSecure" is now listening on 192.168.100.218:7102 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
####<Feb 18, 2013 2:54:58 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <d3208ed6c2482016:-46ac5fed:13ceba69a8e:-7ffe-000000000000000e> <1361163298045> <BEA-002613> <Channel "Default" is now listening on 192.168.100.218:7101 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
AdminServer logs update while starting managed:
####<Feb 18, 2013 2:54:57 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <cd259038c7dcf5a8:-26ac3ba0:13ceb6f767d:-8000-0000000000000162> <1361163297488> <BEA-149506> <Established JMX Connectivity with adp_ms01 at the JMX Service URL of service: jmx:admin://appserver701.mycompany.internal:9102 /jndi/weblogic.management.mbeanservers.runtime.>
Admin Server :
[oracle@adminserver701 bin]$ netstat -an | grep 9101
tcp 0 0 10.254.252.808:9101 0.0.0.0:* LISTEN
tcp 0 0 192.168.100.238:9101 0.0.0.0:* LISTEN
tcp 0 0 192.168.100.238:9101 192.168.100.218:59038 ESTABLISHED
I am wondering if the JMX connectivity is using the server listen address (adminserver701.mycompany.internal) which will by default resolve to 192.168.100.238. Is there a way to force JMX to use 10.254.252.808?

Hi
For first question the answer is no. With the administration port, you enable the SSL between the admin server and Node manager-managed Servers. You can still use the web console.
For teh second question, you can use ANT or can use the WLS Scripting ..you can get more details in dev2dev.bea.com
Jin

What is the use of Node Manager?

OBIEE Oracle Business Intelligence 11.1.1.5
I have started up the WebLogic server which delivers the WL Server Admin Console as well as the Fusion Middleware Control.
I have ignored NodeManager. It hasnt been started.
What is the use of NodeManager?
Oracle tells us:
Note: In order to start the Managed Server using the WebLogic Server Administration Console, the Node Manager must be running.
http://download.oracle.com/docs/cd/E21043_01/bi.1111/e10541/components.htm
But my Manged Server is running ok - I can check http://<host>:7001/console and its ok.
So why do I need to bother with NodeManager?
I only have WLS and OHS installed - no BI instance.
DA

Answers inline:
As I have installed weblogic server 10.3.5 on windows. while am starting it using cmd am getting two ips as
1**.*.... for weblogic server one is (channel default 4... .. and one is default 1) kindly explain.
- It doesn't generate any IP. If you have installed successfully, weblogic will run on your system and it's ip will remain same. You can access it using your systems'IP:portnumber
Also tell as I have to use cmd for starting servers how can i use unix commands for the same??
- You have installed on windows so unix command won't work for you. You can either start by going into services window in windows or start using command by going to path weblogichome\domains\domainname\bin. Execute startWebLogic.cmd
Also explain what is the use of node manager and weblogic scripting tool which are also installed in the system.
- Node manager is used for communication bentween two or more servers in a domain.
As am looking to install OIM 11g so kindly tell what are all the things I need to know about weblogic so that i can learn OIM easily.
- To install OIM, install weblogic, install oracle database. Use RCU utilities to create database and then install SOA, OIM and configure them. You can get all kinds of guides and steps for OIM 11g r2 here:
http://docs.oracle.com/cd/E27559_01/index.htm
regards,
GP

Administration Port / command line / console gui question

In the Admin_ref.pdf doc it says "After enabling the administration port, all Administration Console traffic must connect via the administration port". Does this mean that you can no longer use the web gui console to manage the servers?
I would like the option to script deployments (deploy ears, stop start servers etc.) via command line to reduce the possibility of user error during routine deployments.
I do config mgmt. and am not a developer so I may be getting hung up on the language here.
Thanks,
gj

Hi
For first question the answer is no. With the administration port, you enable the SSL between the admin server and Node manager-managed Servers. You can still use the web console.
For teh second question, you can use ANT or can use the WLS Scripting ..you can get more details in dev2dev.bea.com
Jin

Domain wide administration port and node manager

Similar Messages

Maybe you are looking for