Weblogic X Proxy
I'm using Weblogic 8.1 and I need access web service by internet, but exists a proxy server.
How to configure proxy in the weblogic server 8.1?
Thank you
Daniel
-Dhttps.proxySet=true
The problem persist!
When I use the J2SE and API javax.net.ssl.HttpsURLConnection, I don't have problem and don't need configure the proxy too, but when I use the weblogic Application Server 8.1 and API weblogic.net.http.HttpsURLConnection return exception.
Similar Messages
-
Problem with WebLogic 10.3.3, Apache 2.2.3 and WebLogic Apache proxy plugin
I have a problem with using Apache 2.2.3 as a WebLogic SSL proxy. I have Apache 2.2 running and successfully configured an SSL cert, config in ssl.conf is...
<VirtualHost secure.daftdonkey.com>
# Setup SSL for secure.daftdonkey.com
ServerName secure.daftdonkey.com
SSLEngine On
SSLCertificateFile /oracle/secure/secure.daftdonkey.com.crt
SSLCertificateKeyFile /oracle/secure/secure.daftdonkey.com.key
SSLCertificateChainFile /oracle/secure/gd_bundle.crt
</VirtualHost>
This works fine
Now I want Apache to proxy requests to my WebLogic Server and secure them over SSL as well
e.g. a request to https://secure.daftdonkey.com/service goes to https://weblogic.internal.site/service
I have downloaded and configured the weblogic module and tested it handling traffic for HTTP and that worked, then I switched the WebLogic module to use SSL.
LoadModule weblogic_module modules/mod_wl.so
<IfModule mod_weblogic.c>
WebLogicHost weblogic.internal.site
WebLogicPort 16101
Debug ALL
SecureProxy ON
WLSSLWallet /oracle/secure/my-wallet
WLLogFile /tmp/wl-proxy.log
</IfModule>
<Location /service>
SetHandler weblogic-handler
</Location>
Starting Apache throws the error. I think this is my main problem, i've searched support.oracle.com and not found anything.
[Mon Jun 07 23:00:48 2010] [crit] (20014)Internal error: WL SSL Init failed for server: (null) on 0
but Apache starts... I get this error when I make a request to https://secure.daftdonkey.com/service
Failure of server APACHE bridge:
No backend server available for connection: timed out after 10 seconds or idempotent set to OFF.
Looking into the log /tmp/wl-proxy.log I see....
Mon Jun 7 22:30:10 2010 <393212759749971> URLfactory Created
Mon Jun 7 22:30:10 2010 <393312759750102> ================New Request: [GET /service HTTP/1.1] =================
Mon Jun 7 22:30:10 2010 <393312759750102> INFO: SSL is configured
Mon Jun 7 22:30:10 2010 <393312759750102> Using Uri /service
Mon Jun 7 22:30:10 2010 <393312759750102> After trimming path: '/service'
Mon Jun 7 22:30:10 2010 <393312759750102> The final request string is '/service'
Mon Jun 7 22:30:10 2010 <393312759750102> parseServerList: Socket Address hostnames 'weblogic.internal.site:16101'
Mon Jun 7 22:30:10 2010 <393312759750102> Host extracted from serverlist is [weblogic.internal.site]
Mon Jun 7 22:30:10 2010 <393312759750102> parseServerList: IP from socket Address [192.168.100.15]
Mon Jun 7 22:30:10 2010 <393312759750102> Initializing lastIndex=0 for a list of length=1
Mon Jun 7 22:30:10 2010 <393312759750102> getListNode: created a new server node: id='weblogic.internal.site:16101' server_name='secure.daftdonkey.com', port='443'
Mon Jun 7 22:30:10 2010 <393312759750102> attempt #0 out of a max of 5
Mon Jun 7 22:30:10 2010 <393312759750102> Trying a pooled connection for '192.168.100.15/16101/16101'
Mon Jun 7 22:30:10 2010 <393312759750102> getPooledConn: found a host and port/securePort match
Mon Jun 7 22:30:10 2010 <393312759750102> getPooledConn: No more connections in the pool for Host[192.168.100.15] Port[16101] SecurePort[16101]
Mon Jun 7 22:30:10 2010 <393312759750102> general list: trying connect to '192.168.100.15'/16101/16101 at line 3188 for '/service'
Mon Jun 7 22:30:10 2010 <393312759750102> SSL is not configured for this connection
Mon Jun 7 22:30:10 2010 <393312759750102> Local Port of the socket is 45580
Mon Jun 7 22:30:10 2010 <393312759750102> Remote Host 192.168.100.15 Remote Port 16101
Mon Jun 7 22:30:10 2010 <393312759750102> URL::connect SSLConn for reader is not set as it is NULL
Mon Jun 7 22:30:10 2010 <393312759750102> general list: created a new connection to '192.168.100.15'/16101 for '/service', Local port:0
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[Host]=[secure.daftdonkey.com]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[User-Agent]=[Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9 ( .NET CLR 3.5.30729)]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[Accept]=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[Accept-Language]=[en-us,en;q=0.5]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[Accept-Encoding]=[gzip,deflate]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[Accept-Charset]=[ISO-8859-1,utf-8;q=0.7,*;q=0.7]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[Keep-Alive]=[300]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[Connection]=[keep-alive]
Mon Jun 7 22:30:10 2010 <393312759750102> parse_header is done
Mon Jun 7 22:30:10 2010 <393312759750102> Method is GET
Mon Jun 7 22:30:10 2010 <393312759750102> About to call parseHeaders
Mon Jun 7 22:30:10 2010 <393312759750102> URL::parseHeaders: Value of parsedHeaders = [0]
Mon Jun 7 22:30:10 2010 <393312759750102> URL::sendHeaders(): meth='GET' file='/service' protocol='HTTP/1.1'
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Host]=[secure.daftdonkey.com]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [User-Agent]=[Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9 ( .NET CLR 3.5.30729)]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Accept]=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Accept-Language]=[en-us,en;q=0.5]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Accept-Encoding]=[gzip,deflate]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Accept-Charset]=[ISO-8859-1,utf-8;q=0.7,*;q=0.7]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Keep-Alive]=[300]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Connection]=[Keep-Alive]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [WL-Proxy-SSL]=[true]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [WL-Proxy-Client-IP]=[192.168.100.245]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Proxy-Client-IP]=[192.168.100.245]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [X-Forwarded-For]=[192.168.100.245]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [X-WebLogic-KeepAliveSecs]=[30]
Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [X-WebLogic-Force-JVMID]=[unset]
Mon Jun 7 22:30:10 2010 <393312759750102> Reader::fill(): first=0 last=0 toRead=4096
Mon Jun 7 22:30:10 2010 <393312759750102> Reader::fill(): sysRecv returned -1
Mon Jun 7 22:30:10 2010 <393312759750102> *******Exception type [READ_ERROR_FROM_SERVER] (socket read failure) raised at line 251 of ../nsapi/Reader.cpp
Mon Jun 7 22:30:10 2010 <393312759750102> caught exception in readStatus: READ_ERROR_FROM_SERVER [os error=104, line 251 of ../nsapi/Reader.cpp]: socket read failure at line 963
Mon Jun 7 22:30:10 2010 <393312759750102> PROTOCOL_ERROR: Backend Server not responding - isRecycled:0
Mon Jun 7 22:30:10 2010 <393312759750102> Marking 192.168.100.15:16101 as bad
Mon Jun 7 22:30:10 2010 <393312759750102> got exception in sendRequest phase: Backend Server not responding at line 3702
Mon Jun 7 22:30:10 2010 <393312759750102> Failing over after sendRequest() exception: PROTOCOL_ERROR as Idempotent is set to ON
Mon Jun 7 22:30:10 2010 <393312759750102> attempt #1 out of a max of 5
However connecting directly to https://192.168.100.15:16101/irm_rights is successful.
Ouput from orapki seems to show a valid wallet.
[root@content my-wallet]# /oracle/install/bin/orapki wallet display -wallet /oracle/secure/my-wallet/
Oracle PKI Tool : Version 11.1.1.2.0
Copyright (c) 2004, 2009, Oracle and/or its affiliates. All rights reserved.
Requested Certificates:
User Certificates:
Trusted Certificates:
Subject: OU=Class 2 Public Primary Certification Authority,O=VeriSign\, Inc.,C=US
Subject: OU=Secure Server Certification Authority,O=RSA Data Security\, Inc.,C=US
Subject: OU=Class 3 Public Primary Certification Authority,O=VeriSign\, Inc.,C=US
Subject: OU=Class 1 Public Primary Certification Authority,O=VeriSign\, Inc.,C=US
Subject: CN=weblogic.internal.site,OU=FOR TESTING ONLY,O=MyOrganization,L=MyTown,ST=MyState,C=US
Subject: CN=GTE CyberTrust Global Root,OU=GTE CyberTrust Solutions\, Inc.,O=GTE Corporation,C=US
Also the apache log at /var/log/httpd/ssl_error_log shows.
[Mon Jun 07 23:59:03 2010] [error] [client 192.168.100.245] ap_proxy: trying GET /service/ at backend host '192.168.100.15/16101; got exception 'Backend Server not responding'
[Mon Jun 07 23:59:03 2010] [error] [client 192.168.100.245] ap_proxy: trying GET /service/ at backend host '192.168.100.15/16101; got exception 'Backend Server not responding'
[Mon Jun 07 23:59:03 2010] [error] [client 192.168.100.245] ap_proxy: trying GET /service/ at backend host '192.168.100.15/16101; got exception 'Backend Server not responding'
[Mon Jun 07 23:59:03 2010] [error] [client 192.168.100.245] ap_proxy: trying GET /service/ at backend host '192.168.100.15/16101; got exception 'Backend Server not responding'
[Mon Jun 07 23:59:03 2010] [error] [client 192.168.100.245] ap_proxy: trying GET /service/ at backend host '192.168.100.15/16101; got exception 'Backend Server not responding'
[Mon Jun 07 23:59:03 2010] [error] [client 192.168.100.245] ap_proxy: trying GET /service/ at backend host '192.168.100.15/16101; got exception 'Backend Server not responding'
Editing the httpd.conf and sending traffic from Apache to WebLogic over regular HTTP works, config is...
LoadModule weblogic_module modules/mod_wl.so
<IfModule mod_weblogic.c>
WebLogicHost weblogic.internal.site
WebLogicPort 16100
Debug ALL
# SecureProxy ON
# WLSSLWallet /oracle/secure/my-wallet
WLLogFile /tmp/wl-proxy.log
</IfModule>
Resulting detail from /tmp/wl-proxy.log
Mon Jun 7 23:20:50 2010 <415912759780351> URLfactory Created
Mon Jun 7 23:20:50 2010 <416012759780502> ================New Request: [GET /service/ HTTP/1.1] =================
Mon Jun 7 23:20:50 2010 <416012759780502> Using Uri /service/
Mon Jun 7 23:20:50 2010 <416012759780502> After trimming path: '/service/'
Mon Jun 7 23:20:50 2010 <416012759780502> The final request string is '/service/'
Mon Jun 7 23:20:50 2010 <416012759780502> parseServerList: Socket Address hostnames 'weblogic.internal.site:16100'
Mon Jun 7 23:20:50 2010 <416012759780502> Host extracted from serverlist is [weblogic.internal.site]
Mon Jun 7 23:20:50 2010 <416012759780502> parseServerList: IP from socket Address [192.168.100.15]
Mon Jun 7 23:20:50 2010 <416012759780502> Initializing lastIndex=0 for a list of length=1
Mon Jun 7 23:20:50 2010 <416012759780502> getListNode: created a new server node: id='weblogic.internal.site:16100' server_name='secure.daftdonkey.com', port='443'
Mon Jun 7 23:20:50 2010 <416012759780502> attempt #0 out of a max of 5
Mon Jun 7 23:20:50 2010 <416012759780502> Trying a pooled connection for '192.168.100.15/16100/16100'
Mon Jun 7 23:20:50 2010 <416012759780502> getPooledConn: found a host and port/securePort match
Mon Jun 7 23:20:50 2010 <416012759780502> getPooledConn: No more connections in the pool for Host[192.168.100.15] Port[16100] SecurePort[16100]
Mon Jun 7 23:20:50 2010 <416012759780502> general list: trying connect to '192.168.100.15'/16100/16100 at line 3188 for '/service/'
Mon Jun 7 23:20:50 2010 <416012759780502> SSL is not configured for this connection
Mon Jun 7 23:20:50 2010 <416012759780502> Local Port of the socket is 56647
Mon Jun 7 23:20:50 2010 <416012759780502> Remote Host 192.168.100.15 Remote Port 16100
Mon Jun 7 23:20:50 2010 <416012759780502> URL::connect SSLConn for reader is not set as it is NULL
Mon Jun 7 23:20:50 2010 <416012759780502> general list: created a new connection to '192.168.100.15'/16100 for '/service/', Local port:0
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Host]=[secure.daftdonkey.com]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[User-Agent]=[Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9 ( .NET CLR 3.5.30729)]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Accept]=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Accept-Language]=[en-us,en;q=0.5]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Accept-Encoding]=[gzip,deflate]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Accept-Charset]=[ISO-8859-1,utf-8;q=0.7,*;q=0.7]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Keep-Alive]=[300]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Connection]=[keep-alive]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Cookie]=[JSESSIONID=YF4nMNfZ3lJ5ZrVV9HGpKwj3hf12yRvlf4zksQf6pkKx2LhJ2ywY!34167467]
Mon Jun 7 23:20:50 2010 <416012759780502> parse_header is done
Mon Jun 7 23:20:50 2010 <416012759780502> Method is GET
Mon Jun 7 23:20:50 2010 <416012759780502> About to call parseHeaders
Mon Jun 7 23:20:50 2010 <416012759780502> URL::parseHeaders: Value of parsedHeaders = [0]
Mon Jun 7 23:20:50 2010 <416012759780502> URL::sendHeaders(): meth='GET' file='/service/' protocol='HTTP/1.1'
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Host]=[secure.daftdonkey.com]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [User-Agent]=[Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9 ( .NET CLR 3.5.30729)]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Accept]=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Accept-Language]=[en-us,en;q=0.5]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Accept-Encoding]=[gzip,deflate]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Accept-Charset]=[ISO-8859-1,utf-8;q=0.7,*;q=0.7]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Keep-Alive]=[300]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Cookie]=[JSESSIONID=YF4nMNfZ3lJ5ZrVV9HGpKwj3hf12yRvlf4zksQf6pkKx2LhJ2ywY!34167467]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Connection]=[Keep-Alive]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [WL-Proxy-SSL]=[true]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [WL-Proxy-Client-IP]=[192.168.100.245]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Proxy-Client-IP]=[192.168.100.245]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [X-Forwarded-For]=[192.168.100.245]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [X-WebLogic-KeepAliveSecs]=[30]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [X-WebLogic-Force-JVMID]=[unset]
Mon Jun 7 23:20:50 2010 <416012759780502> Reader::fill(): first=0 last=0 toRead=4096
Mon Jun 7 23:20:50 2010 <416012759780502> Reader::fill(): sysRecv returned 568
Mon Jun 7 23:20:50 2010 <416012759780502> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 302 Moved Temporarily]
Mon Jun 7 23:20:50 2010 <416012759780502> URL::parseHeaders: StatusLine set to [302 Moved Temporarily]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from WLS:[Date]=[Tue, 08 Jun 2010 06:20:50 GMT]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from WLS:[Transfer-Encoding]=[chunked]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from WLS:[Location]=[https://secure.daftdonkey.com/service/faces/LoginPage.jspx]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from WLS:[X-WebLogic-JVMID]=[34167467]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from WLS:[X-Powered-By]=[Servlet/2.5 JSP/2.1]
Mon Jun 7 23:20:50 2010 <416012759780502> parsed all headers OK
Mon Jun 7 23:20:50 2010 <416012759780502> done with sendRequest
Mon Jun 7 23:20:50 2010 <416012759780502> sendResponse() : r->status = '302'
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to client (add):[Date]=[Tue, 08 Jun 2010 06:20:50 GMT]
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to client (add):[Location]=[https://secure.daftdonkey.com/service/faces/LoginPage.jspx]
Mon Jun 7 23:20:50 2010 <416012759780502> for 192.168.100.15/16100/16100, updated JVMID: 34167467
Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to client (add):[X-Powered-By]=[Servlet/2.5 JSP/2.1]
Mon Jun 7 23:20:50 2010 <416012759780502> calling closeConn() with non-null URL* at 3826
Mon Jun 7 23:20:50 2010 <416012759780502> canRecycle: conn=1 status=302 isKA=1 clen=-1 isCTE=1
Mon Jun 7 23:20:50 2010 <416012759780502> closeConn: pooling for '192.168.100.15/16100'
Mon Jun 7 23:20:50 2010 <416012759780502> closeConn: pooling '0'
Mon Jun 7 23:20:50 2010 <416012759780502> request [irm_rights/] processed successfully..................
Mon Jun 7 23:20:50 2010 <415912759780351> Cleaning up the list node 'weblogic.internal.site:16100'list Length '1'I found the answer to this. The documentation is not clear enough, LD_LIBRARY_PATH MUST be set and MUST have a pointer to the directory where the SSL .so modules are. I wrote up a blog article explaining the configuration and detailed this issue.
http://blogs.oracle.com/irm/2010/06/quick_guide_to_oracle_irm_11g_1.html -
Weblogic.servlet.proxy.HttpProxyServlet
Hi,
I configured HttpProxyServlet to proxy the request to another web application. When I invoke the URL configured in proxy servlet mapping from browser everything works fine. However I need to invoke the second web application resource from within servlet using server side include. I couldn't get this working. The request is never dispatched to second web app (analyzed access logs).
- How do I make this work?
- Is there any specific Debug parameters I can enable to troubleshoot? I enabled HttpDebug but couldn't find anything useful.
ThanksNothing in Server logs I could tie to issue. Here is the proxy configuration:
<servlet>
<servlet-name>WebAppBProxy</servlet-name>
<servlet-class>weblogic.servlet.proxy.HttpProxyServlet</servlet-class>
<init-param>
<param-name>redirectURL</param-name>
<param-value>http://webapphostb:port</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>WebAppBProxy</servlet-name>
<url-pattern>/appB/ServiceRequest.do</url-pattern>
</servlet-mapping>
In the servlet I have
request.getDispatcher("/appB/ServiceRequest.do").include(request,response)
Environment: WL10.3 & Web app 2.3 -
Weblogic server proxy issues with twitter4j api
I am using weblogic 10.3.4 using twitter4j Api running behind the proxy. I am not sure why I am getting this error. I do have the proxy name,port number, userid and password set in the twiiter4j api. The same code works fine for me in tomcat behind proxy. When I was trying to migrate from tomcat to weblogic i am getting following error. Any help is really appreciated. I am not sure its the issue with weblogic
Thanks for the help
Vinoj
<Failed to communicate with proxy: tmsproxy.tms.toyota.com/80. Will try c
onnection stream.twitter.com/443 now.
weblogic.net.http.HttpUnauthorizedException: Proxy or Server Authentication Required
at weblogic.net.http.HttpURLConnection.getAuthInfo(HttpURLConnection.java:297)
at weblogic.net.http.HttpsClient.makeConnectionUsingProxy(HttpsClient.java:440)
at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:351)
at weblogic.net.http.HttpsClient.New(HttpsClient.java:527)
at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:239)
Truncated. see log file for complete stacktrace
Dumping beanImpl -> ejbName map
weblogic.management.j2ee.mejb.MejbBean: Mejb
connect timed out
Relevant discussions can be found on the Internet at:
http://www.google.co.jp/search?q=944a924a or
http://www.google.co.jp/search?q=24fd66dc
TwitterException{exceptionCode=[944a924a-24fd66dc 944a924a-24fd66b2], statusCode=-1, message=null, code=-1, retryAfter=-1, rateLim
itStatus=null, version=3.0.4-SNAPSHOT(build: f34757f6d8512eca8028601d9de303e0173d8d42)}
at twitter4j.internal.http.HttpClientImpl.request(HttpClientImpl.java:177)
at twitter4j.internal.http.HttpClientWrapper.request(HttpClientWrapper.java:61)
at twitter4j.internal.http.HttpClientWrapper.post(HttpClientWrapper.java:98)
at twitter4j.TwitterStreamImpl.getFilterStream(TwitterStreamImpl.java:304)
at twitter4j.TwitterStreamImpl$7.getStream(TwitterStreamImpl.java:292)
at twitter4j.TwitterStreamImpl$TwitterStreamConsumer.run(TwitterStreamImpl.java:462)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at weblogic.net.http.HttpsClient.openWrappedSSLSocket(HttpsClient.java:565)
at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:287)
at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:364)
at weblogic.net.http.HttpsClient.New(HttpsClient.java:527)
at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:239)
at weblogic.net.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:255)
at twitter4j.internal.http.HttpClientImpl.request(HttpClientImpl.javaHi,
Has anybody got the solution like 64-bit libroxy or its source code to compile as 64-bit? I'm facing the same problem. -
OHS to Weblogic Reverse Proxy configuration Problem
Hi,
Pls go through the following points and suggest.
1. I have an Access Manager in place and I need to integrate it with Webcenter and Oracle Identity Manager.
2. I have only one webserver in place which is reverse proxied for both the application servers(OIM as well as Webcenter) and only one webgate installed.
Can I achieve SSO with this architecture? My doubt is while specifying the challenge parameter in Access Manager,how can i specify it?Thanks for the reply. Let me detail you regarding my configuration.
1. One webserver configured as reverse proxy for two app serrvers(weblogic1 for webcenter and weblogic2 for Identity manager)
2. My reverse proxy config in httpd.conf file are as follows
ProxyPass /webcenter http://app1:8888/webcenter
ProxyPassReverse /webcenter http://app1:8888/webcenter
ProxyPass /xlWebApp http://app2:7001/xlWebApp
ProxyPassReverse /xlWebApp http://app2:7001/xlWebApp
3. Created two policy domains for /webcenter and /xlWebApp and Iam using form based authentication scheme.
My Challenge parameters as follows:
form: /am_login/login.html (am_login.war is deployed on both app1 and app2)
creds:userid password
action:/dummy.cgi
Now the problem is whenever http://webserverhost:7777/webcenter is accessed,it should redirect to http://webserverhost:7777/am_login/login.html. But its not happening so reason being,after hitting the url it is not able to find the am_login.war in /webcenter on the appserver.Instead its deployed on the root "/" not inside "/webcenter".
Samething is happening for /xlWebApp too. Can you suggest some configuration which would make my things work? -
HttpClusterServlet Proxy Plugin problem - Weblogic Express 10
Hi,
I am using Weblogic Express 10 version. I am trying to configure HttpClusterServelet in one of my test machine.
I have a Admin server and 3 Managed servers which are part of clusters. I have a test war file which is deployed on to the cluster.
I am able to open the test war file application by hitting Managed servers URL's & Port no's
for eg: http://hostname:portno/testapp
Now I have created a war file with httpclusterserver features and deployed it to Admin server. (created web.xml & weblogic.xml inside WEB-INF directory and built it as war file and deployed it to Admin server)
so practically whenever I hit the Admin server URL my request should be proxied to one of the three Managed server which are part of the cluster
But when I try to open the application through admin server hostname and port no, I get below 403 exception on browser
Error 403--Forbidden
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.4 403 Forbidden
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
Below is the content of my web.xml & weblogic.xml war file
web.xml
-bash-3.00$ more web.xml
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd";>
<web-app>
<servlet>
<servlet-name>HttpClusterServlet</servlet-name>
<servlet-class>
weblogic.servlet.proxy.HttpClusterServlet
</servlet-class>
<init-param>
<param-name>WebLogicCluster</param-name>
<param-value>
ManagedSrv1_Hostname:PortNo|ManagedSrv2_Hostname:PortNo|ManagedSrv3_Hostname:PortNo
</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>*.jsp</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>*.htm</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>*.html</url-pattern>
</servlet-mapping>
</web-app>
weblogic.xml
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN" "http://www.bea.com/servers/wls810/dtd/
weblogic 810-web-jar.dtd">
<weblogic-web-app>
<context-root>/</context-root>
</weblogic-web-app>
Kindly advise on this problem.
- - Weblogic ConsultantHi,
Did you configure the replication correctly in the weblogic.xml?
Also fill in the correct cluster address in the weblogic configuration.
http://edocs.bea.com/wls/docs90/cluster/setup.html#726973
Schelstraete Bart
[email protected]
http://www.schelstraete.org
http://www.linkedin.com/in/bschelst -
Unable to find .so file for Apache proxy in Weblogic 92
Hi,
I'm trying to configure Apache as a proxy for Weblogic 9.2 cluster on HP - Itanium. Apache and Weblogic are installed, configured and running. I used the jar file installer to install Weblogic.
Now i'm unable to find the Apache plugin anywhere in my weblogic directory. Any ideas how I can get one ??
Thanks in advance,
Anup.Hi,
Thank you both for your help. Installed the plugins and now the proxy is running very nicely. Configuration was really very simple.
Would like to ask one nore thing. The system i'm configuring now is supposed to cater a very heavy load in terms of connections. We know the application can take it as right now the Weblogic HTTP proxy is what is failing and that's when we decided on Apache. Any recomendations on the Apache side ??
Thanks once more,
Anup. -
Weblogic to IIS - reverse proxying - WL 7.0
Hi All.
Due to performance reasons, we cannot put IIS as a webserver proxy to weblogic
anymore.
Can anyone tell me if the built in webserver of weblogic can be configured to
proxy ASP pages ?
I know weblogic is an app server but is there a way we can add a handler in weblogic
that will handle ASP pages by proxying the requests to an IIS server sitting behind
it ?
Thanks,
MallikYou can use weblogic.servlet.proxy.HttpProxyServlet to achieve this.
Heres the link for more info
http://edocs.bea.com/wls/docs61/adminguide/http_proxy.html
Nagesh
"Mallik" <[email protected]> wrote in message
news:3f00ece6$[email protected]..
>
Hi All.
Due to performance reasons, we cannot put IIS as a webserver proxy toweblogic
anymore.
Can anyone tell me if the built in webserver of weblogic can be configuredto
proxy ASP pages ?
I know weblogic is an app server but is there a way we can add a handlerin weblogic
that will handle ASP pages by proxying the requests to an IIS serversitting behind
it ?
Thanks,
Mallik -
NES proxy connection to WebLogic server
Is there a service pack available which enables SSL traffic (https rather than http)
between the weblogic NES proxy and weblogic server 5.1?Copy the <Weblogic81>\server\lib\weblogic.jar to the <JDeveloper>\jdev\lib\ext directory. <WebLogic81> is the directory in which your WebLogic 8.1 server is installed. <JDeveloper> is the directory in which JDeveloper 10g is installed.
-
Weblogic 4.5.1 and NSAPI wl-proxy
Hi everyone. I have a question regarding the weblogic NSAPI proxy for
Netscape web servers. We have a cluster of 8 WebLogic 4.5.1 servers
running on two 5500 Sun servers (Solaris 2.6), each with 2GB of RAM.
The weblogic clustering proxy runs on another machine what also acts as
the document server. The web server on the proxy box is Netscape
Enterprise Server v3.62.
We are using in-memory replication on the weblogic servers. In this
enviornment, is the weblogic NSAPI proxy/plugin our only bottleneck?
Does anyone have any numbers on the time the wl-proxy takes up?? Is
there a limit on the number of connections the wl-proxy can handle??
Thanks
--vinny
Generally speaking NSAPI is has performance impact since it is a legacy API
added on top of the NS static serving engine. We have seen in high volume
applications a better than 50% performance hit for requests handling by
NSAPI code. Note that the internal NSAPI modules enjoy tighter integration
with the server pump (i.e., undocumented internal API).
I believe NES 4.0 goes to a new server arch. where the static serving engine
is build on the same new servlet API (C++ and Java) that developers would
use.
-phil (plindsayebuilt.net)
eBuilt, Inc.
Vinny Carpenter <[email protected]> wrote in message
news:[email protected]..
>
> Hi everyone. I have a question regarding the weblogic NSAPI proxy for
> Netscape web servers. We have a cluster of 8 WebLogic 4.5.1 servers
> running on two 5500 Sun servers (Solaris 2.6), each with 2GB of RAM.
> The weblogic clustering proxy runs on another machine what also acts as
> the document server. The web server on the proxy box is Netscape
> Enterprise Server v3.62.
>
> We are using in-memory replication on the weblogic servers. In this
> enviornment, is the weblogic NSAPI proxy/plugin our only bottleneck?
> Does anyone have any numbers on the time the wl-proxy takes up?? Is
> there a limit on the number of connections the wl-proxy can handle??
>
> Thanks
>
> --vinny
>
>
-
I'm creating a servlet filter that filters the content of resources that are proxied
by the Weblogic Proxy servlet (weblogic.servlet.proxy.HttpProxyServlet)
The filtering of the content is working but getting the filtering of incoming
and outgoing headers is a problem.
I get ClasscastExceptions if I try to implement my own request wrapper in WL 7
SP2 (incoming headers). And filtering headers in the response wrapper (outgoing
headers) causes a IndexOutOfBoundsException. This is caused by a call to response.setHeader
in the wrapper.
Has someone managed to get header filtering to work?
java.lang.IndexOutOfBoundsException
at java.io.BufferedInputStream.read(BufferedInputStream.java:270)
at java.io.DataInputStream.read(DataInputStream.java:108)
at weblogic.servlet.proxy.GenericProxyServlet.sendResponse(GenericProxyServlet.java:595)
This looks like a bug in the ProxyServlet. I would report this to support.
Sam
Sven Andersson wrote:
> I'm creating a servlet filter that filters the content of resources that are proxied
> by the Weblogic Proxy servlet (weblogic.servlet.proxy.HttpProxyServlet)
>
> The filtering of the content is working but getting the filtering of incoming
> and outgoing headers is a problem.
>
> I get ClasscastExceptions if I try to implement my own request wrapper in WL 7
> SP2 (incoming headers). And filtering headers in the response wrapper (outgoing
> headers) causes a IndexOutOfBoundsException. This is caused by a call to response.setHeader
> in the wrapper.
>
> Has someone managed to get header filtering to work?
>
> java.lang.IndexOutOfBoundsException
> at java.io.BufferedInputStream.read(BufferedInputStream.java:270)
> at java.io.DataInputStream.read(DataInputStream.java:108)
> at weblogic.servlet.proxy.GenericProxyServlet.sendResponse(GenericProxyServlet.java:595)
-
How to protect an application running on weblogic through OAM
I have a requirement where in I need to protect an application (URL/root) deployed on weblogic through Oracle Access Manager.
Here's what I did:
Installed webgate on the Host where the application is deployed.
Configured the webgate on Access System Console.
Configured the policy domain -
a) Mentioned the Resource type and URL to be protected
b) Authentication Type (Basic)
c) Autherization Rules (Anyone can acess)
Issue: When I try to access the application http://<hostname>:7001/myapp
I expect the webgate/OAM to intercept this request and challenge the user with the basic authentication
but the request is carried through and the Home page of myapp is displayed.
Do I need to do some configurations in the webserver (httpd.conf) or deployment descriptors in the application server to get the authentication?
The application above can also be substituted with Oracle Identity Manager, where I'm getting the same result. I'm able to view OIM Home page without prior authentication. I tried protecting with the following pattern <host variation>/xlWebApp
I am new to Oracle Access Manager and looking for some guidance.
ThanksHi Joe,
1. Please elaborate step2 or guide me to a link where I can configure reverse proxy from Apache Webserver to weblogic. I think here's where I'm going wrong.
For more details on proxy refer to these links:
http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs90/plugins/apache.html#119517
OHS to Weblogic Reverse Proxy configuration Problem
After this configuration, won't I be able to access the application /myapp running on weblogic through port 7001 and will I have access to it only on port 80 (web s erver default port)?
You will be able to access the application through 7001, but the request will not be intercepted by OAM. The request will be processed directly by your myApp.
2. I did some reading and found some instructions on using weblogic SSPI plugin. Is this required at all? When is this used?
You can use SSPI Connector if you want to protect the weblogic port. i.e., OAM intercepts the request when you access the application on 7001 port.
Hope this helps
Hrushi -
How does a proxy servlet work and how to set up
I'm a newbie to Weblogic, using 8.1SP3. I came across documentation about a Proxy Servlet that allow weblogic to proxy requests to another web server. This is the scenerio I'm trying to set up. I want to create a weblogic module that proxies to yahoo.com. The communications between weblogic and yahoo may not be SSL, but from weblogic back to my client is SSL. I created a yahoo directory under user-projects\domains\mydomain. I created a WEB-INF\web.xml with the following based on the documentation:
<!DOCTYPE web-app PUBLIC
"-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_3.dtd">
<web-app>
<servlet>
<servlet-name>ProxyServlet</servlet-name>
<servlet-class>weblogic.servlet.proxy.HttpProxyServlet
</servlet-class>
<init-param>
<param-name>redirectURL</param-name>
<param-value>http://www.yahoo.com:80</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>ProxyServlet</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>ProxyServlet</servlet-name>
<url-pattern>*.jsp</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>ProxyServlet</servlet-name>
<url-pattern>*.htm</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>ProxyServlet</servlet-name>
<url-pattern>*.html</url-pattern>
</servlet-mapping>
</web-app>
I deploy the yahoo directory from the admin console and when I go to https://localhost:7002/
I would expect to see the www.yahoo.com page. Am I missing something. Is this not what the proxy servlet is for, is the above possible? Any help and suggestions appreciated.
--SamHey Anders, it's working....
Believe it or not, all I did after adding the weblogic.xml was restart the bea server; even though I had redeployed the module.
So, thank you very much for your patience and suggestions.
--Sam -
We are evaluating the Cluster features of WebLogic and got a eval
license for the Cluster Support.
I am running a default cluster (mycluster) using the default Multicast
address (237.0.0.1) and am seeing
some strange behaviour/errors.
Would appreciate some asistance in this matter.
Our Environment
I created directory in a shared file system to host the cluster.
(h:\kkanth\weblogic)
Created the mycluster directory and other directories as recommended in
the Administrator's guide.
I have two WL Servers (asera190 and asera162) with permanent IP
addresses of 10.1.1.61 and 10.1.1.70 respectively. They run NT 4.0.
I'm using a NES proxy on asera190 with the plugin for WL specified in
obj.conf alongwith the other parameters.
I'm able to have both the servers join to cluster mycluster and the WL
Admin Console does display a tree that depicts the cluster as well as
servers in it (server61 and server70). The individual server directories
are being created in h:\kkanth\weblogic\mycluster directory with the
appropriate access.log and weblogic.log files.
When a browser attempts to access a URL such as
http://asera190/weblogic/snoop it does return the proper response, but
all requests are processed by asera162 which is listed first in the
obj.conf. Opening multiple sessions does not cause the requests to be
sent to asera190 which is the second server in the cluster. When
asera162 is shutdown and removed from the cluster, I hoped that
subsequent requests would go to asera190. However , depending on the
origin of the request, different errors were thrown. If I try to access
http://asera190/weblogic/snoop from a browser on asera190, I get an
error "Failure at line 351 of file proxy.cpp" ,while trying the same URL
from asera162 cause "Failure at line 706 of file proxy.cpp".
I'm attaching the weblogic.properties file kept in h:\kkanth\weblogic
directory as well as the obj.conf file in the ....\config\ directory of
asera190.
We are running NES 3.5.1 and have setup proxy35.dll appropriately.
weblogic.properties
# THE WEBLOGIC PROPERTIES FILE
# This file, which conforms to the java.util.Properties file
# definition, configures your WebLogic products. You cannot run
# WebLogic Server without setting required configuration properties in
this
# file. Required properties are marked and appear first in the file.
# Details on each entry and important information about configuration
# and security are documented on our website. Please go to:
# http://www.weblogic.com/docs45/admindocs/properties.html
# for full instructions on how to edit this file.
# You do not need to include properties in this file unless you want to
# change the default, embedded property. Some properties on the
# T3AdminProps page are not listed here because the default property
# is being used. You can change the default by adding the property and
# its value to this file.
# You cannot set weblogic.system.home in this file, since the WebLogic
Server
# must know where home is in order to retrieve this file. You can
# change WebLogic home on the command line when you start the
# WebLogic Server.
# CLUSTER USERS: Note that the (shared) per-cluster properties file
should
# contain most all of the properties in this file. The only properties
# that potentially belong in a per-server properties file for a server
# running in a cluster are the registration (startup class) of pinned
# RMI objects, and a few tuning properties that may be different for
# servers in the cluster, depending upon hardware and memory. If you use
# a per-server properties file, please REMOVE all properties except
those
# that are specifically required in the per-server properties file. You
# can find specific notes on clusters by searching through this file for
# "CLUSTER USERS".
# The way this file is organized:
# Core properties (includes REQUIRED and RECOMMENDED)
# Core system properties
# Core security-related properties
# Core security-related properties for SSL
# Core HTTPD administrative properties
# Optional properties
# Administrator properties
# System properties
# System startup files
# System shutdown files
# Security-related properties for Workspaces
# Jolt for WebLogic properties
# WebLogic Enterprise Connectivity properties
# WebLogic File properties
# WebLogic JMS demo properties
# WebLogic RMI demo properties
# WebLogic EJB demo properties
# WebLogic ZAC demo properties
# HTTPD administrative properties
# WebLogic JDBC driver properties
# WebLogic JDBC connection pool management
# WebLogic demo connection pool
# WebLogic HTTP Servlet properties
# Proxy servlet registration
# Classpath servlet registration
# File servlet registration
# ServerSideInclude servlet registration
# PageCompileServlet (used by JHTML)
# JSPServlet (used by JSP)
# ServletServlet registration
# Servlet reload properties
# Servlet ACLs
# WebLogic JHTML properties
# User-written and demo servlet registrations
# CORE PROPERTIES
# You should set these before you start the WebLogic Server the first
time.
# If you need more instructions on individual properties in this
# section, check the same section in the Optional Properties, where
# we've left the long explanations. Or, better yet, go to our
# website and read all about properties, at:
# http://www.weblogic.com/docs45/admindocs/properties.html
# CORE SYSTEM PROPERTIES
# TCP/IP port number at which the WebLogic Server listens for
connections
weblogic.system.listenPort=7001
# CORE SECURITY-RELATED PROPERTIES
# Read important information about security at:
# http://www.weblogic.com/docs45/admindocs/properties.html
# REQUIRED: The system password MUST be set in order to start the
# WebLogic Server. This password is case-sensitive, at least 8
characters.
# The username for the privileged user is ALWAYS "system".
# This username and password also includes httpd access (see
# HTTPD properties below).
weblogic.password.system=kaykayka
# RECOMMEND Set to 'everyone' if HTTPD is enabled
weblogic.allow.execute.weblogic.servlet=everyone
# Set individual ACLs to restrict access to HTTP-related resources,
# such as the Administration servlets.
# To make your own servlets generally available, follow this
# pattern (provide a weblogic.allow.execute) for your packages and
# set ACLs as appropriate.
# CORE SECURITY-RELATED PROPERTIES FOR SSL
# Read important information about SSL at:
# http://www.weblogic.com/docs45/classdocs/API_secure.html
# Enable SSL
# (default if property not defined is false)
weblogic.security.ssl.enable=true
# SSL listen port
weblogic.system.SSLListenPort=7002
# Servlets for SSL
# Authentication servlet for creating tokens for applets
weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationServlet
# Limits number of unclaimed stored tokens
weblogic.security.certificateCacheSize=3
# Capture CA root of client servlet
weblogic.httpd.register.T3AdminCaptureRootCA=admin.T3AdminCaptureRootCA
# Certificates for SSL
# Name of acceptable CA roots
# For client authentication change value to a valid .pem file
#weblogic.security.clientRootCA=SecureServerCA.pem
# Server certificates for SSL
weblogic.security.certificate.server=democert.pem
weblogic.security.key.server=demokey.pem
weblogic.security.certificate.authority=ca.pem
# registration for certificate generator servlet
weblogic.httpd.register.Certificate=utils.certificate
weblogic.allow.execute.weblogic.servlet.Certificate=system
# CORE HTTPD ADMINISTRATIVE PROPERTIES
# True permits the HTTPD to run (default)
# Uncomment this property to disable HTTPD
#weblogic.httpd.enable=false
# If authentication is required, add username/password for each user
# who will be included in an ACL, as in this commented-out example:
#weblogic.password.peter=#8gjsL4*
# OPTIONAL PROPERTIES
# These properties affect the behavior of the WebLogic Server.
# You only need to set these properties if you want
# to change the default setting, which is the property shown.
# ADMINISTRATOR PROPERTIES
# Administrator properties are optional information properties,
# particularly useful for clusters.
#weblogic.administrator.location=3355 California Drive, West Hampshire,
CA 94104
#weblogic.administrator.name=Joe Administrator
#weblogic.administrator.phone=1 415 555 1234
# SYSTEM PROPERTIES
# System properties in this section are set to system defaults
# Performance pack. The shared library must be accessible from your
# PATH (NT) or from your shared library path (UNIX; the name of the
# variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
weblogic.system.nativeIO.enable=true
# Outputs logging information to the console as well as to the log file
weblogic.system.enableConsole=true
# Sets the directory or URL for the WebLogic Admin help pages
# The help pages are shipped in the "docs/adminhelp" directory, in the
# default document root in public_html
weblogic.system.helpPageURL=d:/weblogic/myserver/public_html/docs/adminhelp/
# If you prefer to access the most recent help pages, you can do so
online
# by commenting out the previous property and uncommenting this one:
#weblogic.system.helpPageURL=http://www.weblogic.com/docs45/adminhelp/
# Properties for tuning the server's performance
# Number of WebLogic Server execute threads.
weblogic.system.executeThreadCount=15
# Other optional system properties
# Limits size of weblogic.log (in K) and versions old log
weblogic.system.maxLogFileSize=1024
# Adjust minimum length of password
weblogic.system.minPasswordLen=8
# UNIX only: If running on port 80 on UNIX, enable the setUID program
#weblogic.system.enableSetUID=false
# UNIX only: Unprivileged user to setUID to after starting up
# WebLogic Server on port 80
#weblogic.system.nonPrivUser=nobody
# CLUSTER-SPECIFIC PROPERTIES
# Cluster-specific properties in this section are set to system
defaults.
# CLUSTER USERS: Note that ALL Cluster-specific properties should be set
# in the per-cluster properties file ONLY.
# Time-to-live (number of hops) for the cluster's multicast messages
# (default 1, range 1-255).
#weblogic.cluster.multicastTTL=1
# Sets the load-balancing algorithm to be used between
# replicated services if none is specified. If not specified,
# round-robin is used.
#weblogic.cluster.defaultLoadAlgorithm=round-robin
# SERVER-SPECIFIC CLUSTER PROPERTIES
# Cluster-related properties in this section are set to system defaults.
# CLUSTER USERS: Note that these server-specific cluster-related
properties
# should be set in the per-server properties file ONLY.
# Sets the weight of the individual server for the weight-based
load-balancing.
# Range is 0 - 100.
# Larger numbers increase the amount of traffic routed to this server.
#weblogic.system.weight=100
# SYSTEM STARTUP FILES - Examples
# CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
# objects should be registered in the per-server properties file.
# All other startup classes should be registered in the per-cluster
# properties file.
# For more info on writing and using startup file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs45/classdocs/API_t3.html
# Register a startup class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.startupClass.[virtual_name]=[full_pathname]
# Add arguments for the startup class
#weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
# This example shows the entry for examples/t3client/StartupQuery.java
#weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
#weblogic.system.startupArgs.doquery=\
# query=select * from emp,\
# db=jdbc:weblogic:pool:demoPool
# Other system startup files for use with VisiBroker
# Starts the VisiBroker WebLogic Server proxy with the WebLogic Server
# You must have installed Visigenic 2.5 for use with
# the WebLogic Server before you uncomment these properties
#weblogic.system.startupClass.dovisi=weblogic.corba.visi.t3server.Startup
#weblogic.system.startupArgs.dovisi=\
# clientName=T3Client Manager,\
# connName=T3Connection Manager
# SYSTEM SHUTDOWN FILES - Examples
# For more info on writing and using shutdown file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs45/classdocs/API_t3.html
# Register a shutdown class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
# Add arguments for the shutdown class
#weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
# This example shows the entry for examples/t3client/ShutdownTest.java
#weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
#weblogic.system.shutdownArgs.ShutdownTest=\
# outfile=c:/temp/shutdown.log
# SECURITY-RELATED PROPERTIES FOR WORKSPACES
# For backward compatibility, the following entries disable Access
# Control on Workspaces
weblogic.allow.read.weblogic.workspace=everyone
weblogic.allow.write.weblogic.workspace=everyone
# JOLT FOR WEBLOGIC PROPERTIES
# These properties configure a BEA Jolt connection pool for use with
# the simpapp and bankapp examples, and register a servlet for use with
# with the simpapp example. The default server address provided here
# points to a public TUXEDO server that is hosted by BEA for use with
# this example.
# Servlet registration for simpapp example:
#weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServlet
# Pool creation and cleanup
# note this example is set up to work with the public
# demo TUXEDO server available from BEA's website:
#weblogic.system.startupClass.demojoltpoolStart=\
# bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
#weblogic.system.startupArgs.demojoltpoolStart=\
# poolname=demojoltpool,\
# appaddrlist=//beademo1.beasys.com:8000,\
# failoverlist=//beademo1.beasys.com:8000,\
# minpoolsize=1,\
# maxpoolsize=3
#weblogic.system.shutdownClass.demojoltpoolStop=\
# bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
#weblogic.system.shutdownArgs.demojoltpoolStop=\
# poolname=demojoltpool
# WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
# The registrations enable a BEA IIOP connection pool and
# register servlets for use with the simpapp and university examples.
# Configure for your environment and uncomment to use.
# Uncommenting these properties requires WebLogic Enterprise
Connectivity
# and an operating WebLogic Enterprise Server.
# Servlet registration for simpapp servlet example
#weblogic.httpd.register.SimpappServlet=\
# examples.wlec.servlets.simpapp.SimpappServlet
#weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
# Servlet registration for simpapp EJB example
# (You'll need to add the wlec_ejb_simpapp.jar to the
# weblogic.ejb.deploy property in this file.)
#weblogic.httpd.register.ejbSimpappServlet=\
# examples.wlec.ejb.simpapp.ejbSimpappServlet
#weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
# Pool creation and cleanup for the simpapp example
#weblogic.CORBA.connectionPool.simplepool=\
# appaddrlist=//wlehost:2468,\
# failoverlist=//wlehost:2468,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# domainname=simpapp
# Servlet registration for university Servlet example:
#weblogic.httpd.register.UniversityServlet=\
# examples.wlec.servlets.university.UniversityServlet
#weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
# Pool creation and cleanup for the University example:
#weblogic.CORBA.connectionPool.Univpool=\
# appaddrlist=//wlehost:2498,\
# failoverlist=//wlehost:2498,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# apppassword=wlepassword,\
# domainname=university
# WEBLOGIC FILE PROPERTIES
# Maps a volume name to a path, for client file read/write
#weblogic.io.fileSystem.[volumeName]=[fullPathName]
# WEBLOGIC JMS DEMO PROPERTIES
# CLUSTER USERS: Note that ALL JMS deployment should be done in the
# per-cluster properties file ONLY.
# You set up a JDBC connection pool if you want persistent messages
# (including durable subscriptions). To use JMS and EJBs in the same
# transaction, both must use the same JDBC connection pool. Uncomment
# the following property to use the default JDBC connection pool
# 'demo', which is defined in the Demo connection pool section of this
file.
#weblogic.jms.connectionPool=demoPool
# The JMS Webshare example demonstrates how the ClientID for a
# durable subscriber is configured in the connection factory:
#weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
#weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
#weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
#weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
# The JMS trader example shows how to use JMS with an EJB. In addition
# to uncommenting the following properties, you must also set up and
# deploy the EJB example examples.ejb.basic.statefulSession.Trader to
# try out this JMS example:
#weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
#weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
#weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
#weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
# Registers the underlying servlet
#weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
# These properties are used with the ServerReceive JMS example,
# which demonstrates how to establish a JMS message consumer
# in a startup class:
#weblogic.system.startupClass.serverReceive=\
# examples.jms.startup.ServerReceive
#weblogic.system.startupArgs.serverReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# These properties are used with the PoolReceive JMS example,
# which demonstrates how to establish a pool of JMS message consumers
# in a startup class:
#weblogic.system.startupClass.poolReceive=\
# examples.jms.startup.PoolReceive
#weblogic.system.startupArgs.poolReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# WEBLOGIC RMI DEMO PROPERTIES
# CLUSTER USERS: Note that pinned RMI objects should be registered
# in the per-server properties file ONLY. All other RMI startup
# classes should be registered in the per-cluster properties file.
# Remote classes registered at startup after the pattern:
#weblogic.system.startupClass.[virtualName]=[fullPackageName]
# These examples can be compiled to see RMI in action. Uncomment to use:
#weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
#weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
# WEBLOGIC EJB DEMO PROPERTIES
# CLUSTER USERS: Note that ALL EJB deployment should be done in the
# per-cluster properties file ONLY.
# See WebLogic Demo Connection Pool below for a connection pool
# to use with these examples.
# Deploys EJBeans. Uncomment the appropriate lines below and
# modify DBMS-related info and paths to match your particular
installation:
#weblogic.ejb.deploy=\
# d:/weblogic/myserver/cluster_ejb.jar, \
# d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
# d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
# d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
# d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
# d:/weblogic/myserver/ejb_extensions_isModified.jar, \
# d:/weblogic/myserver/ejb_extensions_isModifiedBeanManaged.jar, \
# d:/weblogic/myserver/ejb_sequence_jdbc.jar, \
# d:/weblogic/myserver/ejb_sequence_oracle.jar, \
# d:/weblogic/myserver/ejb_subclass.jar, \
# d:/weblogic/myserver/jolt_ejb_bankapp.jar
# Servlets used by the EJB basic examples beanManaged and
# containerManaged. Uncomment to use:
#weblogic.httpd.register.beanManaged=\
# examples.ejb.basic.beanManaged.Servlet
#weblogic.httpd.register.containerManaged=\
# examples.ejb.basic.containerManaged.Servlet
# Add a list of users (set the password with
weblogic.password.[username]=XXX)
# to set an ACL for this servlet:
#weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
#weblogic.allow.execute.weblogic.servlet.containerManaged=user1,user2,etc
#weblogic.password.user1=user1Password
#weblogic.password.user2=user2Password
# WEBLOGIC ZAC DEMO PROPERTIES
# These registrations enable the ZAC Publish Wizard.
weblogic.zac.enable=true
# Set the publish root for a WebLogic Server. Edit and
# uncomment to use
#weblogic.zac.publishRoot=d:/weblogic/zac
# Set an ACL for each package you publish. The [name] is
# the "Package name" you assign in the ZAC Publish Wizard.
# Publish a package, edit this property, and uncomment to use.
#weblogic.allow.read.weblogic.zac.[name]=[user list]
#weblogic.allow.write.weblogic.zac.[name]=system
# HTTPD ADMINISTRATIVE PROPERTIES
# Enables logging of HTTPD info in common log format and
# sets the log file name (default is "access.log" in "myserver")
weblogic.httpd.enableLogFile=true
weblogic.httpd.logFileName=access.log
# Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
weblogic.httpd.enableEvents=false
# Enables HTTP sessions
weblogic.httpd.session.enable=true
# Sets an optional cookie name. The default name is "WebLogicSession".
# Prior to version 4.0, the default was "TengahSession". To make
# this backward compatible with cookies generated from previous
# installations, you should set this property to "TengahSession".
# Uncomment this line and set this to any string of your choice,
# or comment out this property to use the default.
#weblogic.httpd.session.cookie.name=WebLogicSession
# MIME types
weblogic.httpd.mimeType.text/html=html,htm
weblogic.httpd.mimeType.image/gif=gif
weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
weblogic.httpd.mimeType.application/pdf=pdf
weblogic.httpd.mimeType.application/zip=zip
weblogic.httpd.mimeType.application/x-java-vm=class
weblogic.httpd.mimeType.application/x-java-archive=jar
weblogic.httpd.mimeType.application/x-java-serialized-object=ser
weblogic.httpd.mimeType.application/octet-stream=exe
# In seconds, the keep-alive for HTTP and HTTPS requests
weblogic.httpd.http.keepAliveSecs=60
weblogic.httpd.https.keepAliveSecs=120
# WEBLOGIC JDBC DRIVER PROPERTIES
# Enables JDBC driver logging and sets the file name for the log
# The weblogic.jdbc.logFile is placed in the per-server
# directory (default is "myserver")
weblogic.jdbc.enableLogFile=false
weblogic.jdbc.logFileName=jdbc.log
# WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# For creating JDBC connection pools. This example shows a connection
# pool called "oraclePool" that allows 3 T3Users "guest," "joe," and
"jill"
# to use 4 JDBC connections (with a potential for up to 10 connections,
# incremented by two at a time, with a delay of 1 second between each
# attempt to connect to the database), to an Oracle database server
called
# "DEMO." If more than 4 connections are opened, after 15 minutes,
unused
# connections are dropped from the pool until only 4 connections remain
open.
# Every 10 minutes, any unused connections in the pool are tested and
# refreshed if they are not viable.
#weblogic.jdbc.connectionPool.oraclePool=\
# url=jdbc:weblogic:oracle,\
# driver=weblogic.jdbc.oci.Driver,\
# loginDelaySecs=1,\
# initialCapacity=4,\
# maxCapacity=10,\
# capacityIncrement=2,\
# allowShrinking=true,\
# shrinkPeriodMins=15,\
# refreshMinutes=10,\
# testTable=dual,\
# props=user=SCOTT;password=tiger;server=DEMO
# Get more details on each argument for this property in the
# Administrators Guide on setting properties at:
# http://www.weblogic.com/docs45/admindocs/properties.html
# Set up ACLs for this connection pool with the following:
#weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=\
# guest,joe,jill
#weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
#weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
# This property is an ACL that specifies the users who can
# create dynamic connection poolsTry the following obj.conf file. By the way why are using NES 35 version. If you are using NES 36 you should use proxy36.dll.
Init fn="load-types" mime-types="mime.types"
Init fn="load-modules" funcs="wl-proxy,wl-init" shlib="d:/weblogic/bin/proxy35.dll"
Init fn="wl-init"
Init access="C:/Netscape/SuiteSpot/https-octavia/logs/accessNewELF" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-request%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%
\"%Req->headers.referer%\" \"%Req->headers.user-agent%\" %Req->reqpb.method% %Req->reqpb.uri% %Req->reqpb.query% \"%Req->reqpb.protocol%\"" fn="flex-init"
<Object name="tg" ppath="*/weblogic/*">
Service fn="wl-proxy" WebLogicCluster="asera190:7001,asera162:7001" PathTrim="/weblogic"
</Object>
<Object name="default">
NameTrans fn="pfx2dir" from="/ns-icons" dir="C:/Netscape/SuiteSpot/ns-icons"
NameTrans fn="pfx2dir" from="/mc-icons" dir="C:/Netscape/SuiteSpot/ns-icons"
NameTrans fn="pfx2dir" from="/help" dir="C:/Netscape/SuiteSpot/manual/https/ug"
NameTrans fn="document-root" root="C:/Netscape/SuiteSpot/docs"
PathCheck fn="nt-uri-clean"
PathCheck fn="check-acl" acl="default"
PathCheck fn="find-pathinfo"
PathCheck fn="find-index" index-names="index.html,home.html"
ObjectType fn="type-by-extension"
ObjectType fn="force-type" type="text/plain"
Service method="(GET|HEAD|POST|PUT)" type="text/jsp" fn="wl-proxy" WebLogicCluster="asera190:7001,asera162:7001"
Service method="(GET|HEAD)" type="magnus-internal/imagemap" fn="imagemap"
Service method="(GET|HEAD)" type="magnus-internal/directory" fn="index-common"
Service method="(GET|HEAD)" type="*~magnus-internal/*" fn="send-file"
AddLog fn="flex-log" name="access"
</Object>
<Object ppath="/usr/suitespot/docs/.perf">
Service fn="service-dump"
</Object>
<Object name="cgi">
ObjectType fn="force-type" type="magnus-internal/cgi"
Service fn="send-cgi"
</Object>
Hope this helps
Krishna Kanth wrote:
> We are evaluating the Cluster features of WebLogic and got a eval
> license for the Cluster Support.
> I am running a default cluster (mycluster) using the default Multicast
> address (237.0.0.1) and am seeing
> some strange behaviour/errors.
> Would appreciate some asistance in this matter.
>
> Our Environment
> ----------------
>
> I created directory in a shared file system to host the cluster.
> (h:\kkanth\weblogic)
> Created the mycluster directory and other directories as recommended in
> the Administrator's guide.
>
> I have two WL Servers (asera190 and asera162) with permanent IP
> addresses of 10.1.1.61 and 10.1.1.70 respectively. They run NT 4.0.
> I'm using a NES proxy on asera190 with the plugin for WL specified in
> obj.conf alongwith the other parameters.
>
> I'm able to have both the servers join to cluster mycluster and the WL
> Admin Console does display a tree that depicts the cluster as well as
> servers in it (server61 and server70). The individual server directories
> are being created in h:\kkanth\weblogic\mycluster directory with the
> appropriate access.log and weblogic.log files.
>
> When a browser attempts to access a URL such as
>
> http://asera190/weblogic/snoop it does return the proper response, but
> all requests are processed by asera162 which is listed first in the
> obj.conf. Opening multiple sessions does not cause the requests to be
> sent to asera190 which is the second server in the cluster. When
> asera162 is shutdown and removed from the cluster, I hoped that
> subsequent requests would go to asera190. However , depending on the
> origin of the request, different errors were thrown. If I try to access
> http://asera190/weblogic/snoop from a browser on asera190, I get an
> error "Failure at line 351 of file proxy.cpp" ,while trying the same URL
> from asera162 cause "Failure at line 706 of file proxy.cpp".
>
> I'm attaching the weblogic.properties file kept in h:\kkanth\weblogic
> directory as well as the obj.conf file in the ....\config\ directory of
> asera190.
>
> We are running NES 3.5.1 and have setup proxy35.dll appropriately.
>
> weblogic.properties
> *********
> # THE WEBLOGIC PROPERTIES FILE
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # This file, which conforms to the java.util.Properties file
> # definition, configures your WebLogic products. You cannot run
> # WebLogic Server without setting required configuration properties in
> this
> # file. Required properties are marked and appear first in the file.
> #
> # Details on each entry and important information about configuration
> # and security are documented on our website. Please go to:
> #
> # http://www.weblogic.com/docs45/admindocs/properties.html
> #
> # for full instructions on how to edit this file.
> #
> # You do not need to include properties in this file unless you want to
> # change the default, embedded property. Some properties on the
> # T3AdminProps page are not listed here because the default property
> # is being used. You can change the default by adding the property and
> # its value to this file.
> #
> # You cannot set weblogic.system.home in this file, since the WebLogic
> Server
> # must know where home is in order to retrieve this file. You can
> # change WebLogic home on the command line when you start the
> # WebLogic Server.
> #
> # CLUSTER USERS: Note that the (shared) per-cluster properties file
> should
> # contain most all of the properties in this file. The only properties
> # that potentially belong in a per-server properties file for a server
> # running in a cluster are the registration (startup class) of pinned
> # RMI objects, and a few tuning properties that may be different for
> # servers in the cluster, depending upon hardware and memory. If you use
>
> # a per-server properties file, please REMOVE all properties except
> those
> # that are specifically required in the per-server properties file. You
> # can find specific notes on clusters by searching through this file for
>
> # "CLUSTER USERS".
> #
> # -------------------------------------------------
> # The way this file is organized:
> # Core properties (includes REQUIRED and RECOMMENDED)
> # Core system properties
> # Core security-related properties
> # Core security-related properties for SSL
> # Core HTTPD administrative properties
> #
> # Optional properties
> # Administrator properties
> # System properties
> # System startup files
> # System shutdown files
> # Security-related properties for Workspaces
> # Jolt for WebLogic properties
> # WebLogic Enterprise Connectivity properties
> # WebLogic File properties
> # WebLogic JMS demo properties
> # WebLogic RMI demo properties
> # WebLogic EJB demo properties
> # WebLogic ZAC demo properties
> # HTTPD administrative properties
> # WebLogic JDBC driver properties
> # WebLogic JDBC connection pool management
> # WebLogic demo connection pool
> # WebLogic HTTP Servlet properties
> # Proxy servlet registration
> # Classpath servlet registration
> # File servlet registration
> # ServerSideInclude servlet registration
> # PageCompileServlet (used by JHTML)
> # JSPServlet (used by JSP)
> # ServletServlet registration
> # Servlet reload properties
> # Servlet ACLs
> # WebLogic JHTML properties
> # User-written and demo servlet registrations
> # -------------------------------------------------
>
> #################################################################
> # CORE PROPERTIES
> # -------------------------------------------------
> # You should set these before you start the WebLogic Server the first
> time.
> # If you need more instructions on individual properties in this
> # section, check the same section in the Optional Properties, where
> # we've left the long explanations. Or, better yet, go to our
> # website and read all about properties, at:
> # http://www.weblogic.com/docs45/admindocs/properties.html
> #################################################################
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE SYSTEM PROPERTIES
> # -------------------------------------------------
> # TCP/IP port number at which the WebLogic Server listens for
> connections
> weblogic.system.listenPort=7001
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE SECURITY-RELATED PROPERTIES
> # -------------------------------------------------
> # Read important information about security at:
> #
> # http://www.weblogic.com/docs45/admindocs/properties.html
> #
> # REQUIRED: The system password MUST be set in order to start the
> # WebLogic Server. This password is case-sensitive, at least 8
> characters.
> # The username for the privileged user is ALWAYS "system".
> # This username and password also includes httpd access (see
> # HTTPD properties below).
> weblogic.password.system=kaykayka
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # RECOMMEND Set to 'everyone' if HTTPD is enabled
> weblogic.allow.execute.weblogic.servlet=everyone
> # Set individual ACLs to restrict access to HTTP-related resources,
> # such as the Administration servlets.
> # To make your own servlets generally available, follow this
> # pattern (provide a weblogic.allow.execute) for your packages and
> # set ACLs as appropriate.
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE SECURITY-RELATED PROPERTIES FOR SSL
> # ------------------------------------------------
> # Read important information about SSL at:
> #
> # http://www.weblogic.com/docs45/classdocs/API_secure.html
> #
> # Enable SSL
> # (default if property not defined is false)
> weblogic.security.ssl.enable=true
> #
> # SSL listen port
> weblogic.system.SSLListenPort=7002
>
> # Servlets for SSL
> # ------------------------------------------------
> # Authentication servlet for creating tokens for applets
> weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationServlet
>
> # Limits number of unclaimed stored tokens
> weblogic.security.certificateCacheSize=3
> # Capture CA root of client servlet
> weblogic.httpd.register.T3AdminCaptureRootCA=admin.T3AdminCaptureRootCA
>
> # Certificates for SSL
> # ------------------------------------------------
> # Name of acceptable CA roots
> # For client authentication change value to a valid .pem file
> #weblogic.security.clientRootCA=SecureServerCA.pem
> #
> # Server certificates for SSL
> # ------------------------------------------------
> weblogic.security.certificate.server=democert.pem
> weblogic.security.key.server=demokey.pem
> weblogic.security.certificate.authority=ca.pem
>
> # registration for certificate generator servlet
> weblogic.httpd.register.Certificate=utils.certificate
> weblogic.allow.execute.weblogic.servlet.Certificate=system
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE HTTPD ADMINISTRATIVE PROPERTIES
> # ------------------------------------------------
> # True permits the HTTPD to run (default)
> # Uncomment this property to disable HTTPD
> #weblogic.httpd.enable=false
> #
> # If authentication is required, add username/password for each user
> # who will be included in an ACL, as in this commented-out example:
> #weblogic.password.peter=#8gjsL4*
>
> #################################################################
> # OPTIONAL PROPERTIES
> # ------------------------------------------------
> # These properties affect the behavior of the WebLogic Server.
> # You only need to set these properties if you want
> # to change the default setting, which is the property shown.
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # ADMINISTRATOR PROPERTIES
> # ------------------------------------------------
> # Administrator properties are optional information properties,
> # particularly useful for clusters.
> #weblogic.administrator.location=3355 California Drive, West Hampshire,
> CA 94104
> #weblogic.administrator.name=Joe Administrator
> #weblogic.administrator.phone=1 415 555 1234
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SYSTEM PROPERTIES
> # ------------------------------------------------
> # System properties in this section are set to system defaults
>
> # Performance pack. The shared library must be accessible from your
> # PATH (NT) or from your shared library path (UNIX; the name of the
> # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
> weblogic.system.nativeIO.enable=true
>
> # Outputs logging information to the console as well as to the log file
> weblogic.system.enableConsole=true
>
> # Sets the directory or URL for the WebLogic Admin help pages
> # The help pages are shipped in the "docs/adminhelp" directory, in the
> # default document root in public_html
> weblogic.system.helpPageURL=d:/weblogic/myserver/public_html/docs/adminhelp/
>
> # If you prefer to access the most recent help pages, you can do so
> online
> # by commenting out the previous property and uncommenting this one:
> #weblogic.system.helpPageURL=http://www.weblogic.com/docs45/adminhelp/
>
> # Properties for tuning the server's performance
> # ------------------------------------------------
> # Number of WebLogic Server execute threads.
> weblogic.system.executeThreadCount=15
>
> # Other optional system properties
> # ------------------------------------------------
> # Limits size of weblogic.log (in K) and versions old log
> weblogic.system.maxLogFileSize=1024
>
> # Adjust minimum length of password
> weblogic.system.minPasswordLen=8
>
> # UNIX only: If running on port 80 on UNIX, enable the setUID program
> #weblogic.system.enableSetUID=false
>
> # UNIX only: Unprivileged user to setUID to after starting up
> # WebLogic Server on port 80
> #weblogic.system.nonPrivUser=nobody
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CLUSTER-SPECIFIC PROPERTIES
> # ------------------------------------------------
> # Cluster-specific properties in this section are set to system
> defaults.
> # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
>
> # in the per-cluster properties file ONLY.
> #
> # Time-to-live (number of hops) for the cluster's multicast messages
> # (default 1, range 1-255).
> #weblogic.cluster.multicastTTL=1
> #
> # Sets the load-balancing algorithm to be used between
> # replicated services if none is specified. If not specified,
> # round-robin is used.
> #weblogic.cluster.defaultLoadAlgorithm=round-robin
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SERVER-SPECIFIC CLUSTER PROPERTIES
> # ------------------------------------------------
> # Cluster-related properties in this section are set to system defaults.
>
> # CLUSTER USERS: Note that these server-specific cluster-related
> properties
> # should be set in the per-server properties file ONLY.
> #
> # Sets the weight of the individual server for the weight-based
> load-balancing.
> # Range is 0 - 100.
> # Larger numbers increase the amount of traffic routed to this server.
> #weblogic.system.weight=100
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SYSTEM STARTUP FILES - Examples
> # ------------------------------------------------
> # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
> # objects should be registered in the per-server properties file.
> # All other startup classes should be registered in the per-cluster
> # properties file.
> #
> # For more info on writing and using startup file, see the
> # Developers Guide "Writing a WebLogic Client application," at
> # http://www.weblogic.com/docs45/classdocs/API_t3.html
> #
> # Register a startup class by giving it a virtual name and
> # supplying its full pathname.
> #weblogic.system.startupClass.[virtual_name]=[full_pathname]
> #
> # Add arguments for the startup class
> #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
> #
> # This example shows the entry for examples/t3client/StartupQuery.java
> #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
> #weblogic.system.startupArgs.doquery=\
> # query=select * from emp,\
> # db=jdbc:weblogic:pool:demoPool
> #
> # Other system startup files for use with VisiBroker
> # ------------------------------------------------
> # Starts the VisiBroker WebLogic Server proxy with the WebLogic Server
> # You must have installed Visigenic 2.5 for use with
> # the WebLogic Server before you uncomment these properties
> #weblogic.system.startupClass.dovisi=weblogic.corba.visi.t3server.Startup
>
> #weblogic.system.startupArgs.dovisi=\
> # clientName=T3Client Manager,\
> # connName=T3Connection Manager
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SYSTEM SHUTDOWN FILES - Examples
> # ------------------------------------------------
> # For more info on writing and using shutdown file, see the
> # Developers Guide "Writing a WebLogic Client application," at
> # http://www.weblogic.com/docs45/classdocs/API_t3.html
> #
> # Register a shutdown class by giving it a virtual name and
> # supplying its full pathname.
> #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
> #
> # Add arguments for the shutdown class
> #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
> #
> # This example shows the entry for examples/t3client/ShutdownTest.java
> #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
>
> #weblogic.system.shutdownArgs.ShutdownTest=\
> # outfile=c:/temp/shutdown.log
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SECURITY-RELATED PROPERTIES FOR WORKSPACES
> # ------------------------------------------------
> # For backward compatibility, the following entries disable Access
> # Control on Workspaces
> weblogic.allow.read.weblogic.workspace=everyone
> weblogic.allow.write.weblogic.workspace=everyone
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # JOLT FOR WEBLOGIC PROPERTIES
> # ------------------------------------------------
> # These properties configure a BEA Jolt connection pool for use with
> # the simpapp and bankapp examples, and register a servlet for use with
> # with the simpapp example. The default server address provided here
> # points to a public TUXEDO server that is hosted by BEA for use with
> # this example.
> #
> # Servlet registration for simpapp example:
> # ------------------------------------------------
> #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServlet
>
> #
> # Pool creation and cleanup
> # note this example is set up to work with the public
> # demo TUXEDO server available from BEA's website:
> # ------------------------------------------------
> #weblogic.system.startupClass.demojoltpoolStart=\
> # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
> #weblogic.system.startupArgs.demojoltpoolStart=\
> # poolname=demojoltpool,\
> # appaddrlist=//beademo1.beasys.com:8000,\
> # failoverlist=//beademo1.beasys.com:8000,\
> # minpoolsize=1,\
> # maxpoolsize=3
> #
> #weblogic.system.shutdownClass.demojoltpoolStop=\
> # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
> #weblogic.system.shutdownArgs.demojoltpoolStop=\
> # poolname=demojoltpool
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
> # ------------------------------------------------
> # The registrations enable a BEA IIOP connection pool and
> # register servlets for use with the simpapp and university examples.
> # Configure for your environment and uncomment to use.
> # Uncommenting these properties requires WebLogic Enterprise
> Connectivity
> # and an operating WebLogic Enterprise Server.
> #
> # Servlet registration for simpapp servlet example
> # ------------------------------------------------
> #weblogic.httpd.register.SimpappServlet=\
> # examples.wlec.servlets.simpapp.SimpappServlet
> #
> #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
> #
> # Servlet registration for simpapp EJB example
> # (You'll need to add the wlec_ejb_simpapp.jar to the
> # weblogic.ejb.deploy property in this file.)
> # --------------------------------------------
> #weblogic.httpd.register.ejbSimpappServlet=\
> # examples.wlec.ejb.simpapp.ejbSimpappServlet
> #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
> #
> # Pool creation and cleanup for the simpapp example
> # -------------------------------------------------
> #weblogic.CORBA.connectionPool.simplepool=\
> # appaddrlist=//wlehost:2468,\
> # failoverlist=//wlehost:2468,\
> # minpoolsize=2,\
> # maxpoolsize=3,\
> # username=wleuser,\
> # userrole=developer,\
> # domainname=simpapp
> #
> # Servlet registration for university Servlet example:
> # ---------------------------------------------------
> #weblogic.httpd.register.UniversityServlet=\
> # examples.wlec.servlets.university.UniversityServlet
> #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
> #
> # Pool creation and cleanup for the University example:
> # ----------------------------------------------------
> #weblogic.CORBA.connectionPool.Univpool=\
> # appaddrlist=//wlehost:2498,\
> # failoverlist=//wlehost:2498,\
> # minpoolsize=2,\
> # maxpoolsize=3,\
> # username=wleuser,\
> # userrole=developer,\
> # apppassword=wlepassword,\
> # domainname=university
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC FILE PROPERTIES
> # ------------------------------------------------
> # Maps a volume name to a path, for client file read/write
> #weblogic.io.fileSystem.[volumeName]=[fullPathName]
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC JMS DEMO PROPERTIES
> # -------------------------------------------------
> # CLUSTER USERS: Note that ALL JMS deployment should be done in the
> # per-cluster properties file ONLY.
> #
> # You set up a JDBC connection pool if you want persistent messages
> # (including durable subscriptions). To use JMS and EJBs in the same
> # transaction, both must use the same JDBC connection pool. Uncomment
> # the following property to use the default JDBC connection pool
> # 'demo', which is defined in the Demo connection pool section of this
> file.
> #
> #weblogic.jms.connectionPool=demoPool
> #
> # The JMS Webshare example demonstrates how the ClientID for a
> # durable subscriber is configured in the connection factory:
> #
> #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
> #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
>
> #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
> #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
> #
> # The JMS trader example shows how to use JMS with an EJB. In addition
> # to uncommenting the following properties, you must also set up and
> # deploy the EJB example examples.ejb.basic.statefulSession.Trader to
> # try out this JMS example:
> #
> #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
> #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
> #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
> #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
> #
> # Registers the underlying servlet
> #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
> #
> # These properties are used with the ServerReceive JMS example,
> # which demonstrates how to establish a JMS message consumer
> # in a startup class:
> #
> #weblogic.system.startupClass.serverReceive=\
> # examples.jms.startup.ServerReceive
> #weblogic.system.startupArgs.serverReceive=\
> # connectionFactory=javax.jms.TopicConnectionFactory,\
> # topic=javax.jms.exampleTopic
> #
> # These properties are used with the PoolReceive JMS example,
> # which demonstrates how to establish a pool of JMS message consumers
> # in a startup class:
> #weblogic.system.startupClass.poolReceive=\
> # examples.jms.startup.PoolReceive
> #weblogic.system.startupArgs.poolReceive=\
> # connectionFactory=javax.jms.TopicConnectionFactory,\
> # topic=javax.jms.exampleTopic
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC RMI DEMO PROPERTIES
> # ------------------------------------------------
> # CLUSTER USERS: Note that pinned RMI objects should be registered
> # in the per-server properties file ONLY. All other RMI startup
> # classes should be registered in the per-cluster properties file.
> #
> # Remote classes registered at startup after the pattern:
> #weblogic.system.startupClass.[virtualName]=[fullPackageName]
> #
> # These examples can be compiled to see RMI in action. Uncomment to use:
>
> #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
>
> #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC EJB DEMO PROPERTIES
> # -------------------------------------------------
> # CLUSTER USERS: Note that ALL EJB deployment should be done in the
> # per-cluster properties file ONLY.
> #
> # See WebLogic Demo Connection Pool below for a connection pool
> # to use with these examples.
> #
> # Deploys EJBeans. Uncomment the appropriate lines below and
> # modify DBMS-related info and paths to match your particular
> installation:
> #weblogic.ejb.deploy=\
> # d:/weblogic/myserver/cluster_ejb.jar, \
> # d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
> # d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
> # d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
> # d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
> # d:/weblogic/myserver/ejb_extensions_isModified.jar, \
> # d:/weblogic/myserver/ejb_extensions_isModifiedBeanManaged.jar, \
>
> # d:/weblogic/myserver/ejb_sequence_jdbc.jar, \
> # d:/weblogic/myserver/ejb_sequence_oracle.jar, \
> # d:/weblogic/myserver/ejb_subclass.jar, \
> # d:/weblogic/myserver/jolt_ejb_bankapp.jar
> #
> # Servlets used by the EJB basic examples beanManaged and
> # containerManaged. Uncomment to use:
> #weblogic.httpd.register.beanManaged=\
> # examples.ejb.basic.beanManaged.Servlet
> #weblogic.httpd.register.containerManaged=\
> # examples.ejb.basic.containerManaged.Servlet
> #
> # Add a list of users (set the password with
> weblogic.password.[username]=XXX)
> # to set an ACL for this servlet:
> #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
> #weblogic.allow.execute.weblogic.servlet.containerManaged=user1,user2,etc
>
> #weblogic.password.user1=user1Password
> #weblogic.password.user2=user2Password
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC ZAC DEMO PROPERTIES
> # -------------------------------------------------
> # These registrations enable the ZAC Publish Wizard.
> #
> weblogic.zac.enable=true
> #
> # Set the publish root for a WebLogic Server. Edit and
> # uncomment to use
> #
> #weblogic.zac.publishRoot=d:/weblogic/zac
> #
> # Set an ACL for each package you publish. The [name] is
> # the "Package name" you assign in the ZAC Publish Wizard.
> # Publish a package, edit this property, and uncomment to use.
> #weblogic.allow.read.weblogic.zac.[name]=[user list]
> #weblogic.allow.write.weblogic.zac.[name]=system
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # HTTPD ADMINISTRATIVE PROPERTIES
> # ------------------------------------------------
> # Enables logging of HTTPD info in common log format and
> # sets the log file name (default is "access.log" in "myserver")
> weblogic.httpd.enableLogFile=true
> weblogic.httpd.logFileName=access.log
>
> # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
> weblogic.httpd.enableEvents=false
>
> # Enables HTTP sessions
> weblogic.httpd.session.enable=true
>
> # Sets an optional cookie name. The default name is "WebLogicSession".
> # Prior to version 4.0, the default was "TengahSession". To make
> # this backward compatible with cookies generated from previous
> # installations, you should set this property to "TengahSession".
> # Uncomment t -
Proxy servlet returns "page not found"
I want all request ending with "/PPO" will be proxy to "http://www.yahoo.com".
Explanation:
Our application is deployed on:
C:\bea\user_projects\rci_domain\applications\rdas
"rdas" is an applications context, we access our application using:
http://localhost:7001/rdas/LoginDev.jsp
I want the following request should be proxied to another server.
http://localhost:7001/rdas/PPO (request for "PPO")
Should Proxy to: http://www.yahoo.com
I tried to simulate the same type of scenario. Following is a part from my web.xml file.
<servlet>
<servlet-name>ProxyServlet</servlet-name>
<servlet-class>weblogic.servlet.proxy.HttpProxyServlet
</servlet-class>
<init-param>
<param-name>redirectURL</param-name>
<param-value>http://www.yahoo.com</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>ProxyServlet</servlet-name>
<url-pattern>/PPO</url-pattern>
</servlet-mapping>
Problem:
It is taking me to yahoo.com, but with "Page Not Found" content. I don’t know why it is showing the yahoo.com page with "Page not found". For example you will see the same page what I am seeing using HTTPProxyServlet, if you try the following:
http://www.yahoo.com/rdas/PPO
or
http://www.yahoo.com/blabla
Note: I can not define "context-root" set to "/" parameter in weblogic.xml file, because our application is accessed using "/rdas". All request must have /rdas as well.
I don’t know what I am missing here. Your solution/suggestions are really important. Your earliest reply is really grateful.
Thanks
FarhanAs Peter says, it might be a bug. I did another test. Selected the URL from my IDD, opened the Hyperlink panel, clicked on Create New Hyperlink and this is what I get: http://www.projectorcentral.com/paint_perfect_screen_%24100.htm. So ID is changing "$" to "%24". But, when I click on Go To Destination, still takes me to the website! I'm on a PC with CS6 8.0.1 and using Google Chrome.
Did a second test just for fun: without selecting the URL in the ID, I went to Type/Hyperlinks & Cross-References/Convert URLs to Hyperlinks and ID creates two Hyperlinks: http://www.projectorcentral.com/paint_perfect_screen_ and a separate: 100.htm. So, ID splits the Hyperlink right at "$". So definitely ID doesn't like the "$".
Maybe you are looking for
-
What is the literal constant or expression which results in the blank meta-value?
Numbers is horsey about not tolerating null values, and yet I can't seem to find a way for the result of a formula to be the blank cell null value. I need a formula that will sparsely replicate the cells of another column depending on a condition, su
-
Where can I find arrows to insert into a video in PE 12?
I would like to know where I can find a variety of arrows, how to find them and then how to insert them. Example; I do not know where and how to find Clip Art in case arrows might be located there. I have searched the archives, but failed to find a
-
How to get data from a second page?
Hi guys, I have the first page, where I have a button, which will navigate to the second page to let user make some choices. After the user makes the choices, user will click a button to get back. How can I pass the choices back to the first page? Re
-
Will HP be sending anything for Win 10 download?
I don't know if I have asked this question correctly so bare with me! I am trying to make sure my computer is ready for the Windows 10 update 7/29/15. I have been concerned about the AMD video card issue was not corrected with an update from HP. T
-
New ipod wont restore back to my old ipod settings.
okay, so I picked up a new ipod today in the apple store due to the fact that my old one had an unresponsive touch screen(it wouldn't unlock) they took mine and gave me a new one. i had my old ipod stuff backed up on my Itunes and when i tried restor