HTTPS to HTTP switching in weblogic App server

Hi,
I am using servlets in Weblogic Server environemt. My client (browser based) switches
from HTTPS to HTTP and vice versa while accessing different servlets.
In IE application works fine but when using Netscape it fails in many parts .
I have read that there is a fix for Netscape , it goes like this
" Question : When a Netscape browser starts a session with WebLogic Server on an
HTTP page and then moves to an HTTPS page, a new session is created. How can I preserve
the session while switching to or from HTTPS?
Answer : The cookie WebLogic Server sends includes the port number. When the Netscape
browser sees a cookie with a different port number, it assumes the destination is
a different server, so it does not return the cookie to WebLogic Server. The way
to prevent this is to specify the domain name that WebLogic Server writes in the
cookie with the weblogic.httpd.session.cookie.domain property. For example:
weblogic.httpd.session.cookie.domain=.mydomain.com "
I have tried this also by giving different versions of the above mentioned line in
weblogic.properties file
i) weblogic.httpd.session.cookie.domain=.myServerName
where myServerName is name of the machine in which Weblogic App server is running

try
weblogic.httpd.session.cookie.domain=.myDomainName
where myDomainName is something like india.techspan.com, make sure you don't put
in the name of your machine. WLS doesn't care about that in this property.
"Ajay Singh" <[email protected]> wrote:
>
Hi,
I am using servlets in Weblogic Server environemt. My client (browser
based) switches
from HTTPS to HTTP and vice versa while accessing different servlets.
In IE application works fine but when using Netscape it fails in many parts
I have read that there is a fix for Netscape , it goes like this
" Question : When a Netscape browser starts a session with WebLogic Server
on an
HTTP page and then moves to an HTTPS page, a new session is created. How
can I preserve
the session while switching to or from HTTPS?
Answer : The cookie WebLogic Server sends includes the port number. When
the Netscape
browser sees a cookie with a different port number, it assumes the destination
is
a different server, so it does not return the cookie to WebLogic Server.
The way
to prevent this is to specify the domain name that WebLogic Server writes
in the
cookie with the weblogic.httpd.session.cookie.domain property. For example:
weblogic.httpd.session.cookie.domain=.mydomain.com "
I have tried this also by giving different versions of the above mentioned
line in
weblogic.properties file
i) weblogic.httpd.session.cookie.domain=.myServerName
where myServerName is name of the machine in which Weblogic App server
is running

Similar Messages

Help !! its urgent !!! HTTPS to HTTP switching in weblogic App server !!

Hi,
I am using servlets in Weblogic Server environemt. My client (browser based) switches
from HTTPS to HTTP and vice versa while accessing different servlets.
In IE application works fine but when using Netscape it fails in many parts .
I have read that there is a fix for Netscape , it goes like this
" Question : When a Netscape browser starts a session with WebLogic Server on an
HTTP page and then moves to an HTTPS page, a new session is created. How can I preserve
the session while switching to or from HTTPS?
Answer : The cookie WebLogic Server sends includes the port number. When the Netscape
browser sees a cookie with a different port number, it assumes the destination is
a different server, so it does not return the cookie to WebLogic Server. The way
to prevent this is to specify the domain name that WebLogic Server writes in the
cookie with the weblogic.httpd.session.cookie.domain property. For example:
weblogic.httpd.session.cookie.domain=.mydomain.com "
I have tried this also by giving different versions of the above mentioned line in
weblogic.properties file
i) weblogic.httpd.session.cookie.domain=.myServerName
where myServerName is name of the machine in which Weblogic App server is running

Which ports are you using for HTTP and HTTPS?
Robert Patrick wrote:
Is the browser talking directly to WLS or going through another web server (and the
weblogic plug-in)? In the URLs being used from the browser, do you always uss the full
machine name (e.g., mymachine.mydomain.com) or are you trying to use just the hostname
(e.g., mymachine) or the IP address?
Robert
Ajay Singh wrote:
Hi,
I am using servlets in Weblogic Server environemt. My client (browser based) switches
from HTTPS to HTTP and vice versa while accessing different servlets.
In IE application works fine but when using Netscape it fails in many parts .
I have read that there is a fix for Netscape , it goes like this
" Question : When a Netscape browser starts a session with WebLogic Server on an
HTTP page and then moves to an HTTPS page, a new session is created. How can I preserve
the session while switching to or from HTTPS?
Answer : The cookie WebLogic Server sends includes the port number. When the Netscape
browser sees a cookie with a different port number, it assumes the destination is
a different server, so it does not return the cookie to WebLogic Server. The way
to prevent this is to specify the domain name that WebLogic Server writes in the
cookie with the weblogic.httpd.session.cookie.domain property. For example:
weblogic.httpd.session.cookie.domain=.mydomain.com "
I have tried this also by giving different versions of the above mentioned line in
weblogic.properties file
i) weblogic.httpd.session.cookie.domain=.myServerName
where myServerName is name of the machine in which Weblogic App server is running

Weblogic app server wsdl web service call with SSL Validation error = 16

Weblogic app server wsdl web service call with SSL Validation error = 16
I need to make wsdl web service call in my weblogic app server. The web service is provided by a 3rd party vendor. I keep getting error
Cannot complete the certificate chain: No trusted cert found
Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure
Validation error = 16
From the SSL debug log, I can see 3 verisign hierarchy certs are correctly loaded (see 3 lines in the log message starting with “adding as trusted cert”). But somehow after first handshake, I got error “Cannot complete the certificate chain: No trusted cert found”.
Here is how I load trustStore and keyStore in my java program:
     System.setProperty("javax.net.ssl.trustStore",”cacerts”);
     System.setProperty("javax.net.ssl.trustStorePassword", trustKeyPasswd);
     System.setProperty("javax.net.ssl.trustStoreType","JKS");
System.setProperty("javax.net.ssl.keyStoreType","JKS");
System.setProperty("javax.net.ssl.keyStore", keyStoreName);
     System.setProperty("javax.net.ssl.keyStorePassword",clientCertPwd);      System.setProperty("com.sun.xml.ws.transport.http.client.HttpTransportPipe.dump","true");
Here is how I create cacerts using verisign hierarchy certs (in this order)
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignClass3G5PCA3Root.txt -alias "Verisign Class3 G5P CA3 Root"
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediatePrimary.txt -alias "Verisign C3 G5 Intermediate Primary"
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediateSecondary.txt -alias "Verisign C3 G5 Intermediate Secondary"
Because my program is a weblogic app server, when I start the program, I have java command line options set as:
-Dweblogic.security.SSL.trustedCAKeyStore=SSLTrust.jks
-Dweblogic.security.SSL.ignoreHostnameVerification=true
-Dweblogic.security.SSL.enforceConstraints=strong
That SSLTrust.jks is the trust certificate from our web server which sits on a different box. In our config.xml file, we also refer to the SSLTrust.jks file when we bring up the weblogic app server.
In addition, we have working logic to use some other wsdl web services from the same vendor on the same SOAP server. In the working web service call flows, we use clientgen to create client stub, and use SSLContext and WLSSLAdapter to load trustStore and keyStore, and then bind the SSLContext and WLSSLAdapter objects to the webSerive client object and make the webservie call. For the new wsdl file, I am told to use wsimport to create client stub. In the client code created, I don’t see any way that I can bind SSLContext and WLSSLAdapter objects to the client object, so I have to load certs by settting system pramaters. Here I attached the the wsdl file.
I have read many articles. It seems as long as I can install the verisign certs correctly to web logic server, I should have fixed the problem. Now the questions are:
1.     Do I create “cacerts” the correct order with right keeltool options?
2.     Since command line option “-Dweblogic.security.SSL.trustedCAKeyStore” is used for web server jks certificate, will that cause any problem for me?
3.     Is it possible to use wsimport to generate client stub that I can bind SSLContext and WLSSLAdapter objects to it?
4.     Do I need to put the “cacerts” to some specific weblogic directory?
---------------------------------wsdl file
<wsdl:definitions name="TokenServices" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">
     <wsp:Policy wsu:Id="TokenServices_policy">
          <wsp:ExactlyOne>
               <wsp:All>
                    <sp:TransportBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
                         <wsp:Policy>
                              <sp:TransportToken>
                                   <wsp:Policy>
                                        <sp:HttpsToken RequireClientCertificate="true"/>
                                   </wsp:Policy>
                              </sp:TransportToken>
                              <sp:AlgorithmSuite>
                                   <wsp:Policy>
                                        <sp:Basic256/>
                                   </wsp:Policy>
                              </sp:AlgorithmSuite>
                              <sp:Layout>
                                   <wsp:Policy>
                                        <sp:Strict/>
                                   </wsp:Policy>
                              </sp:Layout>
                         </wsp:Policy>
                    </sp:TransportBinding>
                    <wsaw:UsingAddressing/>
               </wsp:All>
          </wsp:ExactlyOne>
     </wsp:Policy>
     <wsdl:types>
          <xsd:schema targetNamespace="http://tempuri.org/Imports">
               <xsd:import schemaLocation="xsd0.xsd" namespace="http://tempuri.org/"/>
               <xsd:import schemaLocation="xsd1.xsd" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
          </xsd:schema>
     </wsdl:types>
     <wsdl:message name="ITokenServices_GetUserToken_InputMessage">
          <wsdl:part name="parameters" element="tns:GetUserToken"/>
     </wsdl:message>
     <wsdl:message name="ITokenServices_GetUserToken_OutputMessage">
          <wsdl:part name="parameters" element="tns:GetUserTokenResponse"/>
     </wsdl:message>
     <wsdl:message name="ITokenServices_GetSSOUserToken_InputMessage">
          <wsdl:part name="parameters" element="tns:GetSSOUserToken"/>
     </wsdl:message>
     <wsdl:message name="ITokenServices_GetSSOUserToken_OutputMessage">
          <wsdl:part name="parameters" element="tns:GetSSOUserTokenResponse"/>
     </wsdl:message>
     <wsdl:portType name="ITokenServices">
          <wsdl:operation name="GetUserToken">
               <wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetUserToken" message="tns:ITokenServices_GetUserToken_InputMessage"/>
               <wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetUserTokenResponse" message="tns:ITokenServices_GetUserToken_OutputMessage"/>
          </wsdl:operation>
          <wsdl:operation name="GetSSOUserToken">
               <wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserToken" message="tns:ITokenServices_GetSSOUserToken_InputMessage"/>
               <wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserTokenResponse" message="tns:ITokenServices_GetSSOUserToken_OutputMessage"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name="TokenServices" type="tns:ITokenServices">
          <wsp:PolicyReference URI="#TokenServices_policy"/>
          <soap12:binding transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="GetUserToken">
               <soap12:operation soapAction="http://tempuri.org/ITokenServices/GetUserToken" style="document"/>
               <wsdl:input>
                    <soap12:body use="literal"/>
               </wsdl:input>
               <wsdl:output>
                    <soap12:body use="literal"/>
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="GetSSOUserToken">
               <soap12:operation soapAction="http://tempuri.org/ITokenServices/GetSSOUserToken" style="document"/>
               <wsdl:input>
                    <soap12:body use="literal"/>
               </wsdl:input>
               <wsdl:output>
                    <soap12:body use="literal"/>
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:service name="TokenServices">
          <wsdl:port name="TokenServices" binding="tns:TokenServices">
               <soap12:address location="https://ws-eq.demo.i-deal.com/PhxEquity/TokenServices.svc"/>
               <wsa10:EndpointReference>
                    <wsa10:Address>https://ws-eq.demo.xxx.com/PhxEquity/TokenServices.svc</wsa10:Address>
               </wsa10:EndpointReference>
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>
----------------------------------application log
adding as trusted cert:
Subject: CN=VeriSign Class 3 International Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Issuer: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x641be820ce020813f32d4d2d95d67e67
Valid from Sun Feb 07 19:00:00 EST 2010 until Fri Feb 07 18:59:59 EST 2020
adding as trusted cert:
Subject: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x3c9131cb1ff6d01b0e9ab8d044bf12be
Valid from Sun Jan 28 19:00:00 EST 1996 until Wed Aug 02 19:59:59 EDT 2028
adding as trusted cert:
Subject: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x250ce8e030612e9f2b89f7054d7cf8fd
Valid from Tue Nov 07 19:00:00 EST 2006 until Sun Nov 07 18:59:59 EST 2021
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Cipher: SunPKCS11-Solaris version 1.6 for algorithm DESede/CBC/NoPadding>
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Cipher for algorithm DESede>
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm RSA/ECB/NoPadding>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSetup: loading trusted CA certificates>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 28395435>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 SSL3/TLS MAC>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 received HANDSHAKE>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
<Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure.>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
java.lang.Exception: New alert stack
     at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
     at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
     at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
     at com.certicom.tls.record.WriteHandler.write(Unknown Source)
     at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
     at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
     at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
     at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
     at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
     at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
     at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
     at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
     at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
     at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
     at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
     at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
     at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
     at javax.xml.ws.Service.<init>(Service.java:56)
     at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
     at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
     at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
     at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
     at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.removeContext(ctx): 22803607>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 14640403>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 SSL3/TLS MAC>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 received HANDSHAKE>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
<Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - 12.29.210.156 was not trusted causing SSL handshake failure.>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
java.lang.Exception: New alert stack
     at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
     at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
     at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
     at com.certicom.tls.record.WriteHandler.write(Unknown Source)
     at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
     at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
     at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
     at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
     at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
     at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
     at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
     at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
     at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
     at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
     at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
     at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
     at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
     at javax.xml.ws.Service.<init>(Service.java:56)
     at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
     at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
     at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
     at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
     at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 16189141>

I received a workaround by an internal message.
The how to guide is :
-Download the wsdl file (with bindings, not the one from ESR)
-Correct it in order that the schema corresponds to the answer (remove minOccurs or other things like this)
-Deploy the wsdl file on you a server (java web project for exemple). you can deploy on your local
-Create a new logicial destination that point to the wsdl file modified
-Change the metadata destination in your web dynpro project for the corresponding model and keep the execution desitnation as before.
Then the received data is check by the metadata logical destination but the data is retrieved from the correct server.

WebLogic App server - IHS web server

Will the same "Apache HTTP Server Plug-In" allow IBM/IHS web server to work with WebLogic App server? If so which versions are supported?

Hello I'm trying to install the plugin in IHS 2.0X as per the instructions:
copy mod_wl_20.so file to modules directory,
made a following entry in httpd.conf:
LoadModule weblogic_module modules/mod_wl_20.so
verified that httpd.conf is ok..but IHS coredumps upon startup. Any ideas please? Appreciate your help! Thanks!
This is on Solaris 8

Weblogic App server 6.0 GUI Deployer

does the new Weblogic App server 6.0 contain GUI deployer application like it exits in 5.0weblogic.EJBDeployerTool

No. But, you can use the J2EE builder, currently located on our developer
center. Developer.BEA.com
Michael Girdley
BEA Systems
Learning WebLogic? http://learnweblogic.com
"vishal mehta" <[email protected]> wrote in message
news:3a79a258$[email protected]..
does the new Weblogic App server 6.0 contain GUI deployer application likeit exits in 5.0weblogic.EJBDeployerTool

OAM (10.1.4.3) Integration with WebLogic App Server (10.3.0 or below)

Hi All,
Can I use OAM 10.1.4.3 (Authentication Provider & Identity Asserter) to implement SSO with weblogic App Server 10.3.0 or below?
OAM 10.1.4.3 Authentication Provider & Identity Asserter is the recommended way to configure SSO with Web Logic App server 10.3.1 ( Oracle Middleware 11g).
And
OAM 10.1.4.2 uses WebLogic SSPI to configure SSO between OAM 10g and WebLogic App Server 10.3.0 or below.

Hi,
This is how the integration goes with different versions of WLS and OAM.
There is oamAuthnProvider.jar available with OAM 10.1.4.3 downloads. So it provides the assertion functionality.
Can I use OAM 10.1.4.3 (Authentication Provider & Identity Asserter) to implement SSO with weblogic App Server 10.3.0 or below?
Mahendra: Yes
OAM 10.1.4.3 Authentication Provider & Identity Asserter is the recommended way to configure SSO with Web Logic App server 10.3.1 ( Oracle Middleware 11g).
Mahendra: Yes, this is the recommended and easy approach.
OAM 10.1.4.2 uses WebLogic SSPI to configure SSO between OAM 10g and WebLogic App Server 10.3.0 or below.
Mahendra: Yes, older version of OAM uses SSPI connector installation.
HTH.
Mahendra.

Microsoft IIS as a re-direct in front of a Weblogic app server hosting ADF?

Has anyone had tried to set up Microsoft IIS as a re-direct in front of a WebLogic app server hosting ADF?
Can you please share the best practices, config params, etc?
Thanks and regards
Anil

Any suggestions in this regard?

Weblogic App Server Memory Settings

Hi,
How memory management is happening weblogic app server and where I need to set the those things in weblogic server.
Thanks,

You set memory argumnets for Weblogic in server start scripts - startWeblogic.sh & startManagedWeblogic.sh. You have MEM_ARGS arguments where you set your JVM minimum and maximun heap settings.
Weblogic JVM by default has parallel garbage collection algorithm.
- - Weblogic Consultant

Weblogic app server will not start

When trying to restart weblogic app server console after shutdown it suddenly gives the following error. And console hangs. Any suggestions to what has happened ? It is on a development server.
####<May 1, 2015 5:29:52 PM CEST> <Warning> <netuix> <demnet21> <app_as_u_dom02> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <IBM-1540> <> <> <1430494192195> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=UnexpectedExceptionPage.>
####<May 1, 2015 5:29:52 PM CEST> <Error> <Console> <demnet21> <app_as_u_dom02> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <IBM-1540> <> <> <1430494192290> <BEA-240003> <Console encountered the following error Unexpected exception occured in page flow request processor:
weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[], on ResourceType: weblogic.management.mbeanservers.edit.ConfigurationManagerMBean Action: execute, Target: startEdit
        at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:206)
        at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:222)
        at javax.management.remote.rmi.RMIConnectionImpl_1036_WLStub.invoke(Unknown Source)
        at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:1033)
        at weblogic.management.jmx.MBeanServerInvocationHandler.doInvoke(MBeanServerInvocationHandler.java:544)

The Windows Security Policies required for starting Tuxedo Domains as a service are:
1. Log on as service
2. Act as part of the operating system
3. Replace process level token
4. Increase quotas
Please add these policies to the Local Admin or Network Admin account created for the Oracle Proc Manager and PeopleSoft user ids. This information is from the Km Doc: E-TUXEDO: Unable to Start Domains on Windows Server As a Service (Doc ID 1623062.1)

Error while deploying in 9.2 Beta Weblogic App Server

This is the message i am getting while deploying a J2EE application in the Weblogic 9.2 Beta App Server. Please help:
Unable to access the selected application.
[J2EE Deployment SPI:260101]Parameter may not be null. java.lang.NullPointerException at weblogic.deploy.api.internal.utils.ConfigHelper.checkParam(ConfigHelper.java:142) at weblogic.deploy.api.tools.ModuleInfo.createModuleInfo(ModuleInfo.java:82) at weblogic.deploy.api.tools.SessionHelper.getModuleInfo(SessionHelper.java:656) at com.bea.console.actions.app.install.Flow.appSelected(Flow.java:457) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:854) at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:793) at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:463) at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:290) at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:338) at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:51) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:96) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2025) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:63) at org.apache.beehive.netui.pageflow.interceptor.action.ActionInterceptor.wrapAction(ActionInterceptor.java:167) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.invoke(ActionInterceptors.java:49) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:57) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:86) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2096) at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:235) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:550) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:838) at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:634) at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:156) at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:241) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:130) at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1177) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:622) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:140) at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:107) at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:99) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:177) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:165) at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:219) at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:179) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:351) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:128) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:339) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:330) at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:162) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:137) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:370) at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:229) at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:183) at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:124) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:273) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3191) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1979) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1886) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1317) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

I was having a problem which resulted in the same error . I don't know if yours is related, but I figured I would pass the information along incase it was.
The problem was related to file permissions. We had two seperate users who had installed bea92 on the same server, under different user ids. There was a directory which seems to be used internally by WLS for which one user had permissions, but not the other. So, during deployment, the server could not write to this directory, and the deployments would fail.
The magic directory is "/var/tmp/appmergegen", atleast on Solaris 10. Haven't looked for it on any other environments. Hope that is your problem too.

Wsrp producer in weblogic app server not portal server

I am following the instructions given in [url http://edocs.bea.com/wlp/docs92/federation/Chap-Working_With_Producers.html]
to create wsrp producers on weblogic server without the portal server.
However in Figure 8-7 (Select Project Facets) of the article, the facets being selected belong to weblogic portal which means weblogic portal server will need to be installed. In my case, this defeats the purpose of being being able to create wsrp producers on weblogic server alone (i.e without the portal server installed).
Is there a way we could achieve this without installing weblogic portal? Any help would be appreciated.

No, the 8.1 instruction will not work with 9.2.
In 9.2 you do need to install WLP in order to get the correct templates
and jars.
Nate
Ranjan Saikia wrote:
You mean to say that the instructions for 8.1 will work for 9.2 too? I tried them out but could not find some of the jars(javelin.jar, knex.jar) in the 9.2 installation.
I was initially following the [url http://edocs.bea.com/wlp/docs92/federation/Chap-Working_With_Producers.html]instructions in the 9.2 docs but couldnt get the required facets until I installed the portal server.

Can not connect Weblogic App Server 10.3 from Jdeveloper 10.1.3.5

Hi Friends,
I am trying to connect JDeveloper 10.1.3.5 to WebLogic server 10.3.
I am facing some problems.
I used JDeveloper 11g to do the same and it worked.
I found that JDeveloepr 10.1.3.5 does not have any wizard for Weblogic 10.3 connection, all the available wizards are
for server version 10.1.X.
So Please tell me if it is at all possible to do this.
The reason I am trying to do this is because I can not create composite applications, as my project works only with esb projects.
As I am new to Oracle SOA suite, I accidentally downloaded JDeveloper 11g and SOA Suite 11g etc.
But I found that JDEveloper 11g can not create any ESB projects, it can only create composite projects.
So I downloaded JDeveloper 10.1.3.5. So please help me configure this IDE with the Weblogic server I have.
If it is not possible, please suggest which App Server and OSB version I need to install.
Many thanks in advance.
Edited by: user10935249 on Aug 27, 2011 5:11 AM

@sweetfa:
Thanks a lot for your reply.
Although, I have to work only with 10g, but this info is helpful in that I will not try doing something that is not possible anyway.
And Mediator revealing the ESB project after migration was a completely new info to me and a pretty helpful one.
Edited by: user10935249 on Sep 1, 2011 4:03 AM

SSO using WebLogic app server and AD as the auth source

Hi All,
I am trying to setup SSO on 10gR3 using MS Active Directory as the auth source and WebLogic as the app server.
Do I have to create a custom SSO or can this setup be configured using the basic SSO and config changes?
Any help or guidance will be appreciated.
Cheers
Bob

There are many ways. The generic answer is federation via SAML, look at the docs for Oracle Identity Federation.

Creating new domain using weblogic app server V 7.0

Hi,
I've installed Weblogic Server V7 (beta) and facing a problem. Here is it:
What I want to do
=================
I want to create a new domain parallel to mydomain in weblogic application server
V 7.0 beta.
What are the steps taken
========================
(1) Started "myserver". (2)Opened browser and go to localhost:7001/console. (3)
logged in into the server using default username and password "installadministrator".
(4) Right click on mydomain in the left pane and click on "Create or edit other
domains". (5) entered new domain name and new console contex path, accept other
default values. (6) Apply it.
Problem
=======
(1) The new domain is not being shown in the left pane. (2) If I restart myserver,
it is not started and giving error :
<Mar 21, 2002 5:35:12 PM IST> <Emergency> <WebLogicServer> <000349> <Not all the
ListenPort(s) started properly.>
<Mar 21, 2002 5:35:12 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exception>
The WebLogic Server did not start up properly. Reason: Fatal initialization exception
(3) No directory structure is being created parallel to myserver, and moreover
it is rewriting bea\user_domains\mydomain\config.xml file.
Please help.
Thanks and regards,
Sarmila

Hi,
I've installed Weblogic Server V7 (beta) and facing a problem. Here is it:
What I want to do
=================
I want to create a new domain parallel to mydomain in weblogic application server
V 7.0 beta.
What are the steps taken
========================
(1) Started "myserver". (2)Opened browser and go to localhost:7001/console. (3)
logged in into the server using default username and password "installadministrator".
(4) Right click on mydomain in the left pane and click on "Create or edit other
domains". (5) entered new domain name and new console contex path, accept other
default values. (6) Apply it.
Problem
=======
(1) The new domain is not being shown in the left pane. (2) If I restart myserver,
it is not started and giving error :
<Mar 21, 2002 5:35:12 PM IST> <Emergency> <WebLogicServer> <000349> <Not all the
ListenPort(s) started properly.>
<Mar 21, 2002 5:35:12 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exception>
The WebLogic Server did not start up properly. Reason: Fatal initialization exception
(3) No directory structure is being created parallel to myserver, and moreover
it is rewriting bea\user_domains\mydomain\config.xml file.
Please help.
Thanks and regards,
Sarmila

Is it possible to use commerce server with netscape webserver and weblogic app server

Hello,
We want to use Netscape webserver using NSAPI plug-in with WLS 5.1.
In this scenario can we get full functionality of Weblogic Commerce server
2.0.1 if we wnat to use above setup.
This is urgent please.
surya

Surya,
The NSAPI plug-in with WLS 5.1 should not adversely affect the way the
Commerce Server works. Although this platform is not 'certified', the product
is J2EE compliant and should work without error.
Hope this helps!
surya chavali wrote:
Hello,
We want to use Netscape webserver using NSAPI plug-in with WLS 5.1.
In this scenario can we get full functionality of Weblogic Commerce server
2.0.1 if we wnat to use above setup.
This is urgent please.
surya

HTTPS to HTTP switching in weblogic App server

Similar Messages

Maybe you are looking for