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.
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, MikaCause 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 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.
GrantCause 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 -
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,
-RAJHello 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 -
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 -
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 -
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 -
Administration Port Definition
Hello,
I have create 1 admin server & 1 manager server on same UNIX box. Can both instance
have same Administration Port number ?
Thanks
Kumar,
I am more confused with Admin Port.
Here is my Configuration :
Domain : Admn_srvr
Server Name : Admn_srvr ( Admin Server )
Port : 4401
SSL Port : 4402
Admin Port : 4501.
Server Name : Admn_srvr1 ( Managed Server )
Port : 4403
SSL Port : 4404
Admin Port : 4502.
In stead of using 4501 on Admin server, we have to set it 0 ?
In above configuration, Everything works fine. We are getting following error
message in admn_srvr.log file. I don't understand, Why Admin server tries to
contact Managed server ?
We are not passing Discover=True on commmand line.
++++++++++++++++++++
vr> <ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'> <system> <> <170008>
<Unable to contact managed server - admn_srvr1, at 10.0.192.182:4403. Domain logfile
will not contain messages from this server.>
java.lang.IllegalArgumentException: Invalid user name or password
at weblogic.management.logging.DomainLogHandler.getMBeanHome(DomainLogHandler.java:281)
at weblogic.management.logging.DomainLogHandler.subscribeToServer(DomainLogHandler.java:243)
++++++++++++++
Thanks
Kumar Allamraju <[email protected]> wrote:
>Don't set administration port (via console) in 6.0. This is broken in 6.0 For
now just use Listen Port
>Also you can have admin & managed server's running on the same port,
>but they should be
>binded to a unique IP.
>
>--
>Kumar
>
>wlstech wrote:
>
>> Hello,
>>
>> I have create 1 admin server & 1 manager server on same UNIX box. Can
>both instance
>> have same Administration Port number ?
>>
>> Thanks
>
-
How to monitor WebLogic Server when enable the Administration Port
It works fine when use Listenport 7001, but when enable the Administration Port(9002), it does not work.
Maybe I should do something to set the system environment property, but how?
help~
Sorry for my poor English~
Thanks~HI,
If the admin port is enabled then you have to use these parameters to run any scripts
-Dweblogic.security.SSL.ignoreHostnameVerification=true
-Dweblogic.security.TrustKeyStore=DemoTrust
-The you can use Admin URL: t3s://localhost:9002 with Admin Port and Secure Protocol.
Example:
java -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust weblogic.WLST application_status.py
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to t3s://localhost:9002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'Domain_7001'.
.Regards,
Ravish Mody
http://middlewaremagic.com/weblogic
Come, Join Us and Experience The Magic… -
Cann't connect to Administrator Port of OAS 4.0.7
Hi,everyone
My web server 4.0.7 runs on Solaris 2.5.1 and Oracle 7.3.4. The connection to normal ports (etc.,80) is successful but to administrator port(etc., 8088) is failed. The message for command OWSSTAT shows normal. Please give me your idea.
Best.Hi,everyone
My web server 4.0.7 runs on Solaris 2.5.1 and Oracle 7.3.4. The connection to normal ports (etc.,80) is successful but to administrator port(etc., 8088) is failed. The message for command OWSSTAT shows normal. Please give me your idea.
Best. -
Weblogic redirects to administration port, not ssl port, for confidential
Using WLS 9.2 MP2.
I added the following into web.xml to make sure all requests are using https.
It works fine when the administration port is not enabled (weblogic redirects the request to the ssl port).
But when the administration port is enabled, weblogic redirects the request to the administration port, not the ssl port, and hence get a 404 error for the page.
I opened BEA case 759384 in Nov last year, and CR354916 was filed, but have not heard back.
<security-constraint>
<web-resource-collection>
<web-resource-name>All Pages</web-resource-name>
<description>These pages are only accessible by over SSL.</description>
<url-pattern>/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<user-data-constraint>
<description>This is how the user data must be transmitted</description>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>setting the setDomainEnv solved the issue.
set MEM_ARGS=-Xms256m -Xmx512m -XX:PermSize=128m
Regards,
Sam. -
Enterprise Edition 5 domain-wide SSL cert
We have a domain-wide cert (valid for hostnames *.uwrf.edu) we'd like to use for new installs of DSEE v5.2 2005 Q4. The Manage Certificates task, as well as the documentation I can find on certutil, assume that you will be generating the private key for Directory Server certs on the host in question, and within the Sun tools to boot. Neither of those is true when you create a cert to be used domain-wide. Is it possible to convince the DS cert store to use the private key and cert we already have?
Is it possible to convince the DS cert store to use
the private key and cert we already have?Should be. Try using pk12util to set up your cert8/key3.db. It is part of the Mozilla NSS toolkit, which is the SSL package used by Sun DS.
http://www.mozilla.org/projects/security/pki/nss/tools/pk12util.html
It's included in recent versions of Solaris at /usr/sfw/bin/pk12util.
Good luck! -
Enter SSL Administration Port [-1] {" " goes back, "!" exits} Problem
Hi all,
I installed JES2 and selected AM, Directory Service.
when installer configure web server, at
Enter SSL Administration Port [-1] {"<" goes back, "!" exits}I can't changed it to be 8989 or other ports.
Enter SSL Administration Port [-1] {"<" goes back, "!" exits}: 8989
Error: The SSL Admin Port could not be validated. Please specify a different
Port.
Enter SSL Administration Port [8989] {"<" goes back, "!" exits}: 1000
Error: The SSL Admin Port could not be validated. Please specify a different
Port.
Enter SSL Administration Port [1000] {"<" goes back, "!" exits}: 100001
Error: The SSL Admin Port specified is out of range. Please enter a valid Port.
Enter SSL Administration Port [100001] {"<" goes back, "!" exits}: 10002
Error: The SSL Admin Port could not be validated. Please specify a different
Port.Anybody help me plz.try the following
ssl-server 90 vip address 10.1.2.136
ssl-server 90 urlrewrite 1 10.1.2.136
ssl-server 90 rsacert xxxxcert
ssl-server 90 rsakey xxxxkey
ssl-server 90 cipher rsa-export-with-rc4-40-md5 10.1.2.136 4443
service esl0011-4443
ip address 10.1.1.120
port 4443
keepalive type http
keepalive uri "/"
active
content HTTP-4443
vip address 10.1.2.136
port 4443
protocol tcp
add service esl0011-4443
active
BTW, I also corrected your urlrewrite command as it was incorrect. You need to specify the host. So not http or https in front.
Gilles. -
When you're implementing PCNS, once you have PCNS installed on all your DCs and you add a target using the Pcnscfg.exe addtarget command in the command prompt. Is this setting domain wide? Do you run it just once on one of the DCs and the value for the
target FIM instance will replicate to all the others or do you need to run the command on each DC with PCNS installed?All settings are stored in configuration partition not in Schema.
One thing that is good to know and that I could not find. If you PCNS is installed in a different forest the SPN should be created in the domain that the target server is in. The pcnscfg.exe will tell you about that the SPN is missing but it's ok if you
got it right.
/Robert
Maybe you are looking for
-
I can't watch youtube videos or any other videos, i also cant play any of the little flash player games that my kids like.
-
Closing AP Period without Sweeping unaccounted invoices or payments
Hello, Is there a way to close the period in Payables without sweeping unaccounted invoices or payments for that period? Thanks, Vikram
-
Error when creating Alert on PER_PERIODS_OF_SERVICE table (error:DRG-10502)
R12.1.3 I have create an alert on PER_PERIODS_OF_SERVICE table (after insert, after update). After Terminating an employee, ALert Manager is attempting to run the DQM Serial Sync Index Program and am receiving the following error: DRG-10502: index AR
-
It is Possible to get Preflight information using javascript...?
Hi EveryOne!!! I'm new baby to Acrobat using javascript .Please Help me? It is Possible to get Preflight information(trim size, colorspace and fonts) using javascript...? Thanks in Advance. -yajiv
-
Hi, I have setup everything on my system to deploy CS4 automatically via a script. When the system restarts it starts to install and seems to complete properly but when i log in i don't have flash, dreamweaver or fireworks installed. OTher programmes