Proxy between Apache and Weblogic

Hi ,
I need to configure a proxy server in between Apache and Weblogic which means not all the requests should go through proxy, only one particular request should go from apache to proxy server and proxy server to Weblogic. Can any one help me how to configure this and how it is going to work.
Regards,
Vamsee

Not exactly sure.However can we use proxying by MIME type here
http://download.oracle.com/docs/cd/E13222_01/wls/docs100/plugins/apache.html#wp132216
Regards

Similar Messages

SSL Connection Configuration between Apache and Weblogic 8,1

I'm currently using Apache web server as a front end server for Weblogic server 8.1 and now i' facing some configuration problem to setting up the SSL connection between this 2 server. When i open my web application page, it shows
Failure of Server Apache bridge
No backend server available for connection: timed out after 10 seconds or idempotent set to OFF.
and my proxy.log shows:
Thu Nov 03 09:36:41 2011 <182413202842013> INFO: SSL is configured
Thu Nov 03 09:36:41 2011 <182413202842013> INFO: SSL configured successfully
Thu Nov 03 09:36:41 2011 <182413202842013> Using Uri /favicon.ico
Thu Nov 03 09:36:41 2011 <182413202842013> After trimming path: '/favicon.ico'
Thu Nov 03 09:36:41 2011 <182413202842013> The final request string is '/favicon.ico'
Thu Nov 03 09:36:41 2011 <182413202842013> SEARCHING id=[ebwdsk298.ebworx.com:7002] from current ID=[ebwdsk298.ebworx.com:7002]
Thu Nov 03 09:36:41 2011 <182413202842013> The two ids matched
Thu Nov 03 09:36:41 2011 <182413202842013> @@@FOUND...id=[ebwdsk298.ebworx.com:7002], server_name=[10.122.50.218], server_port=[80]
Thu Nov 03 09:36:41 2011 <182413202842013> attempt #0 out of a max of 5
Thu Nov 03 09:36:41 2011 <182413202842013> general list: trying connect to '10.122.50.48'/7002/7002 at line 2696 for '/favicon.ico'
Thu Nov 03 09:36:41 2011 <182413202842013> New SSL URL: match = 0 oid = 22
Thu Nov 03 09:36:41 2011 <182413202842013> Connect returns -1, and error no set to 10035, msg 'Unknown error'
Thu Nov 03 09:36:41 2011 <182413202842013> EINPROGRESS in connect() - selecting
Thu Nov 03 09:36:41 2011 <182413202842013> Setting peerID for new SSL connection
Thu Nov 03 09:36:41 2011 <182413202842013> 0a7a 3230 5a1b 0000 .z20Z...
Thu Nov 03 09:36:41 2011 <182413202842013> Local Port of the socket is 2121
Thu Nov 03 09:36:41 2011 <182413202842013> Remote Host 10.122.50.48 Remote Port 7002
Thu Nov 03 09:36:41 2011 <182413202842013> general list: created a new connection to '10.122.50.48'/7002 for '/favicon.ico', Local port:2121
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs from clnt:[Host]=[10.122.50.218]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs from clnt:[Connection]=[keep-alive]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs from clnt:[Accept]=[*/*]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs from clnt:[User-Agent]=[Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.163 Safari/535.1]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs from clnt:[Accept-Encoding]=[gzip,deflate,sdch]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs from clnt:[Accept-Language]=[en-US,en;q=0.8]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs from clnt:[Accept-Charset]=[ISO-8859-1,utf-8;q=0.7,*;q=0.3]
Thu Nov 03 09:36:41 2011 <182413202842013> URL::sendHeaders(): meth='GET' file='/favicon.ico' protocol='HTTP/1.1'
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs to WLS:[Host]=[10.122.50.218]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs to WLS:[Accept]=[*/*]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs to WLS:[User-Agent]=[Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.163 Safari/535.1]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs to WLS:[Accept-Encoding]=[gzip,deflate,sdch]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs to WLS:[Accept-Language]=[en-US,en;q=0.8]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs to WLS:[Accept-Charset]=[ISO-8859-1,utf-8;q=0.7,*;q=0.3]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs to WLS:[Connection]=[Keep-Alive]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs to WLS:[WL-Proxy-SSL]=[false]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs to WLS:[WL-Proxy-Client-IP]=[10.122.50.48]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs to WLS:[Proxy-Client-IP]=[10.122.50.48]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs to WLS:[X-Forwarded-For]=[10.122.50.48]
Thu Nov 03 09:36:41 2011 <182413202842013> Hdrs to WLS:[X-WebLogic-Force-JVMID]=[unset]
Thu Nov 03 09:36:41 2011 <182413202841921> INFO: No session match found
Thu Nov 03 09:36:41 2011 <182413202842013> INFO: No CA was trusted, validation failed
Thu Nov 03 09:36:41 2011 <182413202841921> INFO: DeleteSessionCallback
Thu Nov 03 09:36:41 2011 <182413202842013> ERROR: SSLWrite failed
Thu Nov 03 09:36:41 2011 <182413202842013> SEND failed (ret=-1) at 789 of file ../nsapi/URL.cpp
Thu Nov 03 09:36:41 2011 <182413202842013> *******Exception type [WRITE_ERROR_TO_SERVER] raised at line 790 of ../nsapi/URL.cpp
Thu Nov 03 09:36:41 2011 <182413202842013> Marking 10.122.50.48:7002 as bad
Thu Nov 03 09:36:41 2011 <182413202842013> got exception in sendRequest phase: WRITE_ERROR_TO_SERVER [os error=0, line 790 of ../nsapi/URL.cpp]: at line 3078
Thu Nov 03 09:36:41 2011 <182413202842013> INFO: Closing SSL context
Thu Nov 03 09:36:41 2011 <182413202842013> INFO: Error after SSLClose, socket may already have been closed by peer
Thu Nov 03 09:36:41 2011 <182413202842013> Failing over after WRITE_ERROR_TO_SERVER exception in sendRequest()
Can anyone tell me what should i do in order to correct this error? Your help is kindly appreciate!!! Please~

1) Is the managed server up?
2) from apache server are you able to bind the managed server port?
3) can you pls send the weblogic ssl configuration?

How to configure apache and weblogic in windows 2000

i am novice,
i want to configure apache and weblogic in windows 2000
weblogic version is 6.1
apache version is 2.0
how to do?

George,
I would take the following 'first steps'
1)Install Apache20 on your Windows machine following the Apache online documentation
http://httpd.apache.org/docs-2.0/misc/tutorials.html
2)Make sure you can 'serve up' static HTML content from your Apache Server
3)Install Weblogic Server per our online documentation
http://edocs.bea.com/wls/docs61/install/index.html
4)Also, make sure you can 'serve up' both static and dynamic (e.g., JSP) content
directly from WLS server
5)Once you have both of the above 'sanity' checks attempt to configure a simple
proxy by ppath or mime type via our online documentation
http://edocs.bea.com/wls/docs61/adminguide/apache.html#103803
Chuck Nelson
DRE
BEA Technical Support

Apache and weblogic server

hi all.
i am using oracle application server 10g R2 over windows server 2003 64bit
but now i planned to go for apache and weblogic server for this i do not have idea that
should i do? plz what softwares are required to use apache and weblogic server with current version
10g R2.?

The WebLogic Server (WLS) is a Java container similar to OC4J in Application Server 10g release 2. If you want to use WLS, you will have to upgrade your Application Server 10g installation to Fusion Middleware 11g. The upgrade path typically depends on the products which you are using in 10g, e.g. the upgrade path for SOA is different than the upgrade path for Forms/Reports or Oracle Portal. The [url http://docs.oracle.com/cd/E23943_01/upgrade.1111/e10125/before_you_begin.htm]Upgrade Planning Guide is a good start.
Thanks,
EJ

Configuring apache and weblogic 7.1

have anyone tried connecting apache and weblogic 7.1. which service pack can be used for this purpose

have anyone tried connecting apache and weblogic 7.1. which service pack can be used for this purpose

What is the difference between Apache and OC4J?

Hi All,
i am new to AS
just a question in my mind
what is the difference between Apache and OC4J?
Thanks

Apache is a webserver which comes with OracleAS with added Oracle modules.
OC4J = Oracle Containers for Java
enjoy yourself with some reading
http://download.oracle.com/docs/cd/B14099_19/core.1012/b13994/toc.htm

The problem about Secure Reliable Messaging between WCF and Weblogic

I'm doing a project for testing the interoperability between WCF and Weblogic with secure reliable messaging.
When WCF client talk to Weblogic service with Secure Reliable feature enabled.We got error when CreateSequence, the error message is below:
The incoming message was signed with a token which was different from what used to encrypt the body. This was not expected.
The remote endpoint requested an address for acknowledgements that is not the same as the address for application messages. The channel could not be opened because this is not supported. Ensure the endpoint address used to create the channel is identical to the one the remote endpoint was set up with.
My understanding is that the client accepted the RSTR from weblogic (so both sides now share the secure conversation token) and moved on to CreateSequence (and failed due to config mismatches). But I don't how the error happen and how to get it fixed.
-- below is the wsdl you are using --
Any ideas about it?
Thanks in advance!!!!!!
<?xml version='1.0' encoding='utf-8'?>
<WL5G3N4:definitions name="EchoStringSignOnly" targetNamespace="http://tempuri.org/" xmlns="" xmlns:WL5G3N0="http://www.w3.org/ns/ws-policy" xmlns:WL5G3N1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:WL5G3N2="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" xmlns:WL5G3N3="http://docs.oasis-open.org/ws-rx/wsrmp/200702" xmlns:WL5G3N4="http://schemas.xmlsoap.org/wsdl/" xmlns:WL5G3N5="http://tempuri.org/" xmlns:WL5G3N6="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:WL5G3N7="http://schemas.xmlsoap.org/wsdl/soap12/">
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly1_EchoString_Input_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<sp:SignedParts xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<sp:Body/>
<sp:Header Name="Sequence" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="SequenceAcknowledgement" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="AckRequested" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly1_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<WL5G3N2:RMAssertion>
<WL5G3N2:InactivityTimeout Milliseconds="600000"/>
<WL5G3N2:AcknowledgementInterval Milliseconds="200"/>
</WL5G3N2:RMAssertion>
<sp:SymmetricBinding xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:ProtectionToken>
<wsp15:Policy>
<sp:SecureConversationToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp15:Policy>
<sp:RequireDerivedKeys/>
<sp:BootstrapPolicy>
<wsp15:Policy>
<sp:SignedParts>
<sp:Body/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
<sp:EncryptedParts>
<sp:Body/>
</sp:EncryptedParts>
<sp:AsymmetricBinding>
<wsp15:Policy>
<sp:InitiatorToken>
<wsp15:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp15:Policy>

<sp:WssX509V3Token10/>
</wsp15:Policy>
</sp:X509Token>
</wsp15:Policy>
</sp:InitiatorToken>
<sp:RecipientToken>
<wsp15:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/Never">
<wsp15:Policy>

<sp:WssX509V3Token10/>
</wsp15:Policy>
</sp:X509Token>
</wsp15:Policy>
</sp:RecipientToken>
<sp:AlgorithmSuite>
<wsp15:Policy>
<sp:Basic128Rsa15/>
</wsp15:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp15:Policy>
<sp:Strict/>
</wsp15:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
<sp:OnlySignEntireHeadersAndBody/>
</wsp15:Policy>
</sp:AsymmetricBinding>
<sp:Wss11>
<wsp15:Policy>
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefThumbprint/>
<sp:MustSupportRefEncryptedKey/>
</wsp15:Policy>
</sp:Wss11>
<sp:Trust13>
<wsp15:Policy>
<sp:MustSupportIssuedTokens/>
<sp:RequireClientEntropy/>
<sp:RequireServerEntropy/>
</wsp15:Policy>
</sp:Trust13>
</wsp15:Policy>
</sp:BootstrapPolicy>
</wsp15:Policy>
</sp:SecureConversationToken>
</wsp15:Policy>
</sp:ProtectionToken>
<sp:AlgorithmSuite>
<wsp15:Policy>
<sp:Basic128Rsa15/>
</wsp15:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp15:Policy>
<sp:Strict/>
</wsp15:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
<sp:OnlySignEntireHeadersAndBody/>
</wsp15:Policy>
</sp:SymmetricBinding>
<sp:Wss11 xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefThumbprint/>
<sp:MustSupportRefEncryptedKey/>
</wsp15:Policy>
</sp:Wss11>
<sp:Trust13 xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:MustSupportIssuedTokens/>
<sp:RequireClientEntropy/>
<sp:RequireServerEntropy/>
</wsp15:Policy>
</sp:Trust13>
<wsam:Addressing xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">
<wsp:Policy xmlns:wsp="http://www.w3.org/ns/ws-policy">
<wsam:NonAnonymousResponses/>
</wsp:Policy>
</wsam:Addressing>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly_EchoString_output_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<sp:SignedParts xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<sp:Body/>
<sp:Header Name="Sequence" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="SequenceAcknowledgement" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="AckRequested" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="UsesSequenceSTR" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="ChannelInstance" Namespace="http://schemas.microsoft.com/ws/2005/02/duplex"/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly1_EchoString_output_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<sp:SignedParts xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<sp:Body/>
<sp:Header Name="Sequence" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="SequenceAcknowledgement" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="AckRequested" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly_EchoString_Input_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<sp:SignedParts xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<sp:Body/>
<sp:Header Name="Sequence" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="SequenceAcknowledgement" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="AckRequested" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="UsesSequenceSTR" Namespace="http://docs.oasis-open.org/ws-rx/wsrm/200702"/>
<sp:Header Name="ChannelInstance" Namespace="http://schemas.microsoft.com/ws/2005/02/duplex"/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N0:Policy WL5G3N1:Id="CustomBinding_IEchoStringSignOnly_policy">
<WL5G3N0:ExactlyOne>
<WL5G3N0:All>
<WL5G3N3:RMAssertion/>
<sp:SymmetricBinding xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:ProtectionToken>
<wsp15:Policy>
<sp:SecureConversationToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp15:Policy>
<sp:RequireDerivedKeys/>
<sp:BootstrapPolicy>
<wsp15:Policy>
<sp:SignedParts>
<sp:Body/>
<sp:Header Name="ChannelInstance" Namespace="http://schemas.microsoft.com/ws/2005/02/duplex"/>
<sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"/>
<sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"/>
</sp:SignedParts>
<sp:EncryptedParts>
<sp:Body/>
</sp:EncryptedParts>
<sp:AsymmetricBinding>
<wsp15:Policy>
<sp:InitiatorToken>
<wsp15:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp15:Policy>

<sp:WssX509V3Token10/>
</wsp15:Policy>
</sp:X509Token>
</wsp15:Policy>
</sp:InitiatorToken>
<sp:RecipientToken>
<wsp15:Policy>
<sp:X509Token sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/Never">
<wsp15:Policy>

<sp:WssX509V3Token10/>
</wsp15:Policy>
</sp:X509Token>
</wsp15:Policy>
</sp:RecipientToken>
<sp:AlgorithmSuite>
<wsp15:Policy>
<sp:Basic128Rsa15/>
</wsp15:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp15:Policy>
<sp:Strict/>
</wsp15:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
<sp:OnlySignEntireHeadersAndBody/>
</wsp15:Policy>
</sp:AsymmetricBinding>
<sp:Wss11>
<wsp15:Policy>
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefThumbprint/>
<sp:MustSupportRefEncryptedKey/>
</wsp15:Policy>
</sp:Wss11>
<sp:Trust13>
<wsp15:Policy>
<sp:MustSupportIssuedTokens/>
<sp:RequireClientEntropy/>
<sp:RequireServerEntropy/>
</wsp15:Policy>
</sp:Trust13>
</wsp15:Policy>
</sp:BootstrapPolicy>
</wsp15:Policy>
</sp:SecureConversationToken>
</wsp15:Policy>
</sp:ProtectionToken>
<sp:AlgorithmSuite>
<wsp15:Policy>
<sp:Basic128Rsa15/>
</wsp15:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp15:Policy>
<sp:Strict/>
</wsp15:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
<sp:OnlySignEntireHeadersAndBody/>
</wsp15:Policy>
</sp:SymmetricBinding>
<sp:Wss11 xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
<sp:MustSupportRefThumbprint/>
<sp:MustSupportRefEncryptedKey/>
</wsp15:Policy>
</sp:Wss11>
<sp:Trust13 xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp15:Policy xmlns:wsp15="http://www.w3.org/ns/ws-policy">
<sp:MustSupportIssuedTokens/>
<sp:RequireClientEntropy/>
<sp:RequireServerEntropy/>
</wsp15:Policy>
</sp:Trust13>
<cdp:CompositeDuplex xmlns:cdp="http://schemas.microsoft.com/net/2006/06/duplex"/>
<ow:OneWay xmlns:ow="http://schemas.microsoft.com/ws/2005/05/routing/policy"/>
<wsam:Addressing xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">
<wsp:Policy xmlns:wsp="http://www.w3.org/ns/ws-policy">
<wsam:NonAnonymousResponses/>
</wsp:Policy>
</wsam:Addressing>
</WL5G3N0:All>
</WL5G3N0:ExactlyOne>
</WL5G3N0:Policy>
<WL5G3N4:types>
<xsd:schema targetNamespace="http://tempuri.org/Imports" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://tempuri.org/" schemaLocation="RequestReplySignOnly.svc.xsd0.xml"/>
<xsd:import namespace="http://schemas.microsoft.com/2003/10/Serialization/" schemaLocation="RequestReplySignOnly.svc.xsd1.xml"/>
</xsd:schema>
</WL5G3N4:types>
<WL5G3N4:message name="PingRequest">
<WL5G3N4:part element="WL5G3N5:PingRequest" name="parameters"/>
</WL5G3N4:message>
<WL5G3N4:message name="PingResponse">
<WL5G3N4:part element="WL5G3N5:PingResponse" name="parameters"/>
</WL5G3N4:message>
<WL5G3N4:portType name="IEchoStringSignOnly">
<WL5G3N4:operation name="EchoString">
<WL5G3N4:input message="WL5G3N5:PingRequest" name="PingRequest"/>
<WL5G3N4:output message="WL5G3N5:PingResponse" name="PingResponse"/>
</WL5G3N4:operation>
</WL5G3N4:portType>
<WL5G3N4:binding name="CustomBinding_IEchoStringSignOnly" type="WL5G3N5:IEchoStringSignOnly">
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly_policy"/>
</WL5G3N0:Policy>
<WL5G3N6:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<WL5G3N4:operation name="EchoString">
<WL5G3N6:operation soapAction="urn:wsrm:EchoString" style="document"/>
<WL5G3N4:input name="PingRequest">
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly_EchoString_Input_policy"/>
</WL5G3N0:Policy>
<WL5G3N6:body use="literal"/>
</WL5G3N4:input>
<WL5G3N4:output name="PingResponse">
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly_EchoString_output_policy"/>
</WL5G3N0:Policy>
<WL5G3N6:body use="literal"/>
</WL5G3N4:output>
</WL5G3N4:operation>
</WL5G3N4:binding>
<WL5G3N4:binding name="CustomBinding_IEchoStringSignOnly1" type="WL5G3N5:IEchoStringSignOnly">
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly1_policy"/>
</WL5G3N0:Policy>
<WL5G3N7:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<WL5G3N4:operation name="EchoString">
<WL5G3N7:operation soapAction="urn:wsrm:EchoString" style="document"/>
<WL5G3N4:input name="PingRequest">
<WL5G3N7:body use="literal"/>
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly1_EchoString_Input_policy"/>
</WL5G3N0:Policy>
</WL5G3N4:input>
<WL5G3N4:output name="PingResponse">
<WL5G3N7:body use="literal"/>
<WL5G3N0:Policy>
<WL5G3N0:PolicyReference URI="#CustomBinding_IEchoStringSignOnly1_EchoString_output_policy"/>
</WL5G3N0:Policy>
</WL5G3N4:output>
</WL5G3N4:operation>
</WL5G3N4:binding>
<WL5G3N4:service name="EchoStringSignOnly">
<WL5G3N4:port binding="WL5G3N5:CustomBinding_IEchoStringSignOnly" name="CustomBinding_IEchoStringSignOnly">
<WL5G3N6:address location="http://mss-rrsp-01/ReliableMessaging_Service_WSAddressing10_Indigo/RequestReplySignOnly.svc/SecureReliable_Addressable_Soap11_WSAddressing10_RM11"/>
<wsa10:EndpointReference xmlns:wsa10="http://www.w3.org/2005/08/addressing">
<wsa10:Address>http://mss-rrsp-01/ReliableMessaging_Service_WSAddressing10_Indigo/RequestReplySignOnly.svc/SecureReliable_Addressable_Soap11_WSAddressing10_RM11</wsa10:Address>
<Identity xmlns="http://schemas.xmlsoap.org/ws/2006/02/addressingidentity">
<KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">
<X509Data>
<X509Certificate>MIIDCjCCAfKgAwIBAgIQYDju2/6sm77InYfTq65x+DANBgkqhkiG9w0BAQUFADAwMQ4wDAYDVQQKDAVPQVNJUzEeMBwGA1UEAwwVT0FTSVMgSW50ZXJvcCBUZXN0IENBMB4XDTA1MDMxOTAwMDAwMFoXDTE4MDMxOTIzNTk1OVowQDEOMAwGA1UECgwFT0FTSVMxIDAeBgNVBAsMF09BU0lTIEludGVyb3AgVGVzdCBDZXJ0MQwwCgYDVQQDDANCb2IwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMCquMva4lFDrv3fXQnKK8CkSU7HvVZ0USyJtlL/yhmHH/FQXHyYY+fTcSyWYItWJYiTZ99PAbD+6EKBGbdfuJNUJCGaTWc5ZDUISqM/SGtacYe/PD/4+g3swNPzTUQAIBLRY1pkr2cm3s5Ch/f+mYVNBR41HnBeIxybw25kkoM7AgMBAAGjgZMwgZAwCQYDVR0TBAIwADAzBgNVHR8ELDAqMCiiJoYkaHR0cDovL2ludGVyb3AuYmJ0ZXN0Lm5ldC9jcmwvY2EuY3JsMA4GA1UdDwEB/wQEAwIEsDAdBgNVHQ4EFgQUXeg55vRyK3ZhAEhEf+YT0z986L0wHwYDVR0jBBgwFoAUwJ0o/MHrNaEd1qqqoBwaTcJJDw8wDQYJKoZIhvcNAQEFBQADggEBAIiVGv2lGLhRvmMAHSlY7rKLVkv+zEUtSyg08FBT8z/RepUbtUQShcIqwWsemDU8JVtsucQLc+g6GCQXgkCkMiC8qhcLAt3BXzFmLxuCEAQeeFe8IATr4wACmEQE37TEqAuWEIanPYIplbxYgwP0OBWBSjcRpKRAxjEzuwObYjbll6vKdFHYIweWhhWPrefquFp7TefTkF4D3rcctTfWJ76I5NrEVld+7PBnnJNpdDEuGsoaiJrwTW3Ixm40RXvG3fYS4hIAPeTCUk3RkYfUkqlaaLQnUrF2hZSgiBNLPe8gGkYORccRIlZCGQDEpcWl1Uf9OHw6fC+3hkqolFd5CVI=</X509Certificate>
</X509Data>
</KeyInfo>
</Identity>
</wsa10:EndpointReference>
</WL5G3N4:port>
<WL5G3N4:port binding="WL5G3N5:CustomBinding_IEchoStringSignOnly1" name="CustomBinding_IEchoStringSignOnly1">
<WL5G3N7:address location="http://mss-rrsp-01/ReliableMessaging_Service_WSAddressing10_Indigo/RequestReplySignOnly.svc/SecureReliable_Anonymous_Soap12_WSAddressing10_RM10"/>
<wsa10:EndpointReference xmlns:wsa10="http://www.w3.org/2005/08/addressing">
<wsa10:Address>http://mss-rrsp-01/ReliableMessaging_Service_WSAddressing10_Indigo/RequestReplySignOnly.svc/SecureReliable_Anonymous_Soap12_WSAddressing10_RM10</wsa10:Address>
<Identity xmlns="http://schemas.xmlsoap.org/ws/2006/02/addressingidentity">
<KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">
<X509Data>
<X509Certificate>MIIDCjCCAfKgAwIBAgIQYDju2/6sm77InYfTq65x+DANBgkqhkiG9w0BAQUFADAwMQ4wDAYDVQQKDAVPQVNJUzEeMBwGA1UEAwwVT0FTSVMgSW50ZXJvcCBUZXN0IENBMB4XDTA1MDMxOTAwMDAwMFoXDTE4MDMxOTIzNTk1OVowQDEOMAwGA1UECgwFT0FTSVMxIDAeBgNVBAsMF09BU0lTIEludGVyb3AgVGVzdCBDZXJ0MQwwCgYDVQQDDANCb2IwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMCquMva4lFDrv3fXQnKK8CkSU7HvVZ0USyJtlL/yhmHH/FQXHyYY+fTcSyWYItWJYiTZ99PAbD+6EKBGbdfuJNUJCGaTWc5ZDUISqM/SGtacYe/PD/4+g3swNPzTUQAIBLRY1pkr2cm3s5Ch/f+mYVNBR41HnBeIxybw25kkoM7AgMBAAGjgZMwgZAwCQYDVR0TBAIwADAzBgNVHR8ELDAqMCiiJoYkaHR0cDovL2ludGVyb3AuYmJ0ZXN0Lm5ldC9jcmwvY2EuY3JsMA4GA1UdDwEB/wQEAwIEsDAdBgNVHQ4EFgQUXeg55vRyK3ZhAEhEf+YT0z986L0wHwYDVR0jBBgwFoAUwJ0o/MHrNaEd1qqqoBwaTcJJDw8wDQYJKoZIhvcNAQEFBQADggEBAIiVGv2lGLhRvmMAHSlY7rKLVkv+zEUtSyg08FBT8z/RepUbtUQShcIqwWsemDU8JVtsucQLc+g6GCQXgkCkMiC8qhcLAt3BXzFmLxuCEAQeeFe8IATr4wACmEQE37TEqAuWEIanPYIplbxYgwP0OBWBSjcRpKRAxjEzuwObYjbll6vKdFHYIweWhhWPrefquFp7TefTkF4D3rcctTfWJ76I5NrEVld+7PBnnJNpdDEuGsoaiJrwTW3Ixm40RXvG3fYS4hIAPeTCUk3RkYfUkqlaaLQnUrF2hZSgiBNLPe8gGkYORccRIlZCGQDEpcWl1Uf9OHw6fC+3hkqolFd5CVI=</X509Certificate>
</X509Data>
</KeyInfo>
</Identity>
</wsa10:EndpointReference>
</WL5G3N4:port>
</WL5G3N4:service>
</WL5G3N4:definitions>

Bruce Stephens <[email protected]> wrote:
Hi Michael,
The short answer, at this time, OOTB, WS-RM interop with an unknown
vendor would be doubtful. For a longer answer, David Orchard has a good
review of the emerging web services specs [0]. You might consider ebXML
messaging [1] as a more mature solution.
Thank you Bruce. I will look at these docs.
Mike S.
Hope this helps,
Bruce
[0]
http://dev2dev.bea.com/technologies/webservices/articles/ws_orchard.jsp
[1]
http://e-docs.bea.com/wli/docs70/ebxml/getstart.htm
Michael Shea wrote:
Hello,
We have developed an application that is running on the WebLogic AppServer v8.1
sp1.
Recently we have received a request/query on providing reliable SOAPmessaging
from our application to 3rd party.
I have read the documentation on Reliable messaging support and havenoted that
it is only supported between two WebLogic Application servers.
My questions are, since we do not have control of the 3rd party's application,
and it may not be based on a WebLogic App Server:
1. Will this work?
2. Does anyone have any idea of the type of issues that may be experienced?
3. How close is the implementation to the WS Reliable Messaging specification?
So, if the other party was based on an IBM or Microsoft implementationis this
likely to work?
It goes without saying that any work done would need to be very throughlytested
and qualified.
I have looked through the WebLogic Documentation on WebServices aswell as searching
this newgroup for other posts on this topic, hopefully I have not missedanything
(If so, my apologies.)
Thanks,
Mike Shea.

Apache and webLogic Communication

Hi
we are deploying new application and client want to have Apache on one server and weblogic on another server.
Can you pls point to any notes/docs which tells how to configure Apache to have as fronend for applications in weblogic.
Thanks
Sree

Hi
Thanks for the info.
Since we are hosting team we amy not be able to allow/to code. We have existing setup where Oracle HTTP server in DMZ communicates with other report server oc4j using ajp protocol. We are also NOT allowed to use proxy pass.
For a new project we will be using Apache web server in DMZ and weblogic application server inside.
Can you Pls let me know how we can trasfer requestes thru Apache using other protocols like ajp other than proxy.
Thanks

How to specify a cipher suit used between plugin and weblogic server?

I install Weblogic8.1 SP3 which supports for strong cipher suits, and config an apache 2.50 server as an front end.
I config appache to use 2 way SSL with browser and wls one way SSL with apache plugin. Then config apache to forward client certs to WLS. now the problem is, I can see that the SSL connection between browser and apache uses a strong cipher suit('SSL_RSA_WITH_RC4_128_MD5'), but the ssl connection bwtween apache plugin and WLS uses a weak cipher suit('SSL_RSA_EXPORT_WITH_RC4_40_MD5'), with the SnoopServlet, although I use the mod_wl128_20.so module. How can I increase the cipher strength of SSL between WLS and it's apache plugin?
Thanks in advance.
Best
Regards
Jean

Hello Gunaseelan,
This is not possible because WLS 6.1 needs a config.xml file, exactly this
name, to start.
What you can do is to define a recovery domain, called myrecovery_domain for
instance, and put the config_recovery.xml, renamed "config.xml".
Hope this helps,
Ludovic.
Developer Relations Engineer
BEA Support.
"Gunaseelan Venkateswaran" <[email protected]> a écrit dans le message
news: 3cd6a324$[email protected]..
>
Hi,
I have 2 weblogic startup scripts (startWebLogic.sh and
startWebLogic_recovery.sh) for the same domain.
startWebLogic.sh uses config.xml file.
I would like to use config_recovery.xml as the configuration file forstartWebLogic_recovery.sh
>
>
How would I do this ?
I am using WebLogic Server 6.1 on SunOS 5.8 / HP-UX 11.0.
Appreciate any help.
Regards
Gunaseelan Venkateswaran

Enterprise portal access using reverse proxy using Apache and webdispatcher

Hi Guys,
As requirement, we need to give solution to customer about Reverse proxy scenario. I am new to this part.
What we have think of to use Apache and Web dispatcher.
I tried to search documents and found some sdn links also but still i am not comfortable to go about.
Need suggestion and document if anyone has used so far.reverse proxy.
As basis person, we need to do all ( Apache installation, Apache configuration, Web dispatcher installation and configuration, integration with EP.)
It will helpful to me if i can get Apache installation, Apache configuration part and integration with EP, or web dispatcher, configuration etc.
Thanks,
Deepak

We used Netscaler for Reverse Proxy implementation and can assure you that network team performed most of the set ups. This was on EP 7.01.
From BASIS stand point it would be primarily Web Dispatcher Configuration.
Also refer the links I specified in another thread. There are several scenarios discussed there -
Re: Post values for userid and passowrd fields in logon page
http://wiki.sdn.sap.com/wiki/display/BSP/Using+Proxies
~ Dhanz

Diff between BPM and weblogic integration

hi,
can anybody tell me what is the difference between aqualogic BPM and weblogic integration.
both do business process modelling.
and can anybody tell me when to use one . a usecase example would be helpful.
thanks

hi,
can anybody tell me what is the difference between aqualogic BPM and weblogic integration.
both do business process modelling.
and can anybody tell me when to use one . a usecase example would be helpful.
thanks

IIS proxy 5.1 and Weblogic 6.1 does not support sticky session

Dear Sir,
Our system is migrating from Weblogic 5.1 to Weblogic 6.1. After testing on
development environment, it is found that IIS proxy for 5.1 plug-in and Weblogic
6.1 server is perfect match for our case. Since our appliction system hit some
bugs of IIS proxy for 6.1. In development environment, one IIS match with one
Weblogic.
During production launch, another problem found. It seems that IIS proxy 5.1
plug-in with Weblogic 6.1 does not support the sticky load balancing. A sticky
service is one where a client sends its requests to the same instance and those
requests are not redirected to other instances. In production, two IIS match with
two Weblogic. Below is
#WebLogicHost=10.0.3.12
#WebLogicPort=8012
WebLogicCluster=10.0.3.12:8012,10.0.3.13:8012
COnnectionTimeoutSecs=10
ConnectionRetrySecs=2
ErrorPage=https://www.xxxx.com/eBank/sysnotready.htm
CookieName=eBankingWebLogicSession
Anyone have idea on out case?
Thanks,
KAI

My test was with 6.1 SP3.
The way to tell is by analyzing the cookie(JSESSIONID).
Perhaps the behaviour changed post SP1. I can't say for sure.
Eric
"Gary Rudolph" <[email protected]> wrote in message
news:[email protected]...
Is that entirely true concerning you don't need the persistence set to
replicated in the weblogic.xml to gain sticky load balancing?
The reason I ask was that in our situation sticky wouldn't work without
having the persistence set to replicated. This was with NSAPI and WLS 6.1
SP1. The weblogic servers were configured in a weblogic cluster. So..based
on this statement we should not have needed to set the persistence, but in
practice we did for it to work.
Gary
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
I just checked, and you are correct. You just need to have clustering
enabled in 6.1. You do not necessarily need to have persistence set to
replicated.
Of course, you won't get failover, but you will get the sticky load
balancing.
Regards,
Eric
"Ricky Wong" <[email protected]> wrote in message
news:[email protected]...
Why do we need to set session persistence to replicate in order to
perform
sticky load balancing ? There is no such requirement in WebLogic 5.1.
As
far
as I know, the IIS plugin simply interprets the value of the sessioncookie,
which should be embedded with the application server address, then
forward
the request to that particular application server.
We didn't use session replication in our environment because not allsession
variables are serializable.
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
The problem you mentionned in the other newsgroup post has been
fixed
and
will be in SP4. If you are in production or nearing production and
need
a
resolution now, then please open a case with support.
You should not need any other parameters to do the load balancing.
But
to
have the sticky load balancing, you must make sure you have session
persistence set to replicated for the webapp in question.
I'm not sure I am understanding your 3rd question.
In any case, my advice is to either wait for SP4 to bereleased(scheduled
sometime this month) or if you really need to go into production
soon,
contact support to obtain the latest IIS plugin.
Regards,
Eric
"Mike" <[email protected]> wrote in message
news:[email protected]...
Dear Eric,
Thanks very much for you kindly information, but we still have thefollowing issues
regarding the WL IIS proxy:
1. We have already tried the IIS proxy that comes with WL6.1 SP3.However, the
result from that version of IIS proxy is not satisfactory, as weexperienced cases
where the web page is not displayed correctly (as in
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.develo
per.interest.plug-in&item=994&utag=).
If there is any IIS proxy released after WL6.1 SP3, Could you
kindly
give
us
a pointer to the plugin?
2. In WL5.1 case, we are only required to have "WebLogicCluster"
parameter
set
to two weblogic servers in order use the load balancing features.
In
WL6.1, we
do not come across any additional settings required to support
load
balancing.
Is there any such settings required (e.g. in
config.xml,weblogic.xml,
application.xml,
etc?)
3. Does WL IIS proxy problem has anything to do with the version
of
the
IIS server/windows
versions that are using? we have already tried with IIS4 and IIS5
and
have
different
kinds of issues.
Thanks in advance for your kind assistance.
Mike
"Eric Gross" <[email protected]> wrote:
Yes, the session format has changed when using clustering and you
cannot
use
the 5.1 plugin to proxy to 6.1.
What problems did you have using the 6.1 plugin? Maybe you need
the
latest
6.1 plugin.
Regards,
Eric
"KAI" <[email protected]> wrote in message
news:[email protected]...
Dear Sir,
Our system is migrating from Weblogic 5.1 to Weblogic 6.1.
After
testing on
development environment, it is found that IIS proxy for 5.1
plug-in
and
Weblogic
6.1 server is perfect match for our case. Since our appliction
system
hit
some
bugs of IIS proxy for 6.1. In development environment, one IIS
match
with
one
Weblogic.
During production launch, another problem found. It seems
that
IIS
proxy 5.1
plug-in with Weblogic 6.1 does not support the sticky load
balancing.
A
sticky
service is one where a client sends its requests to the same
instance
and
those
requests are not redirected to other instances. In production,
two
IIS
match with
two Weblogic. Below is
#WebLogicHost=10.0.3.12
#WebLogicPort=8012
WebLogicCluster=10.0.3.12:8012,10.0.3.13:8012
COnnectionTimeoutSecs=10
ConnectionRetrySecs=2
ErrorPage=https://www.xxxx.com/eBank/sysnotready.htm
CookieName=eBankingWebLogicSession
Anyone have idea on out case?
Thanks,
KAI

Relation between TPMonitor and Weblogic

Hi all,
For example , take an application developed using 2 different
technologies.Say one is using an application server like weblogic and
the other is developed on Tuxedo.One of the main services that are
provided by TPMonitors like Tuxedo is to manage distributed
transactions.Same are managed by TransactionManager in weblogic.Are
these technologies completely replacable for one another ?
Thankx for your time...
-- mahati.

Mahati,
The way that I would describe it is that Tuxedo and WebLogic are both
application servers. It's just that when Tuxedo was first released, the word
application server didn't exist.
You should use the Tuxedo app. server if you have skills in and wish to use the
C, COBOL or C++ programming languages to develop your application, wheras you
shoukd use WebLogic if you have java skills that you want to use.
If you have a rage team with a mized skill-set, you can use both WebLogic and
Tuxedo and use the WebLogic Tuxedo connector to connect the 2 physical
environments to produce the effect of one logical application server.
Regards,
Peter.
Ravi Kumar Mahanti wrote:
Hi all,
For example , take an application developed using 2 different
technologies.Say one is using an application server like weblogic and
the other is developed on Tuxedo.One of the main services that are
provided by TPMonitors like Tuxedo is to manage distributed
transactions.Same are managed by TransactionManager in weblogic.Are
these technologies completely replacable for one another ?
Thankx for your time...
-- mahati.

Apache and weblogic proxying not happening properly

Hi,
I am trying to proxy my request from my apache installation to weblogic installation.
I am able to proxy request to the default page of my application in weblogic.
But when trying to browse through that page I am getting error.
Basically, It tries to listen at 7501 port of my machine(apache machine) only
and is not trying to listen at 80 port of my machineso that it can be proxied
to the 7501 port of weblogic machine.
I am unable to figure out the issue. Maybe u can help me from ur experience.
I get an exception saying:
###<Apr 28, 2003 9:53:47 PM IST> <Warning> <Entitlements> <blrkec09630a> <portalServer>
<ExecuteThread: '10' for queue: 'default'> <kernel identity> <16:b7687ce40e05e9a9>
<402716> <Missing entitlments configuration asset.>
Exception[com.bea.p13n.rules.manager.RuleSetNotFoundException: The rule set with
URI /entitlements/GlobalEntitlements.rls could not be located by the class named
com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.]
at com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.getRuleSet(RuleSetPersistenceManager.java:385)
at com.bea.p13n.rules.manager.internal.ContextPool.<init>(ContextPool.java:156)
at com.bea.p13n.rules.manager.internal.ContextPoolFactory.createContextPool(ContextPoolFactory.java:164)
at com.bea.p13n.rules.manager.internal.ContextPoolFactory.getContextPool(ContextPoolFactory.java:223)
at com.bea.p13n.rules.manager.internal.RulesManagerImpl.getContext(RulesManagerImpl.java:469)
at com.bea.p13n.rules.manager.internal.RulesManagerImpl.evaluate(RulesManagerImpl.java:350)
at com.bea.p13n.rules.manager.internal.RulesManagerImpl.evaluateRuleSet(RulesManagerImpl.java:148)
at com.bea.p13n.rules.manager.internal.RulesManagerImpl_mcr6qe_EOImpl.evaluateRuleSet(RulesManagerImpl_mcr6qe_EOImpl.java:448)
at com.bea.p13n.entitlements.rolemapper.RoleMapper.mapRoles(RoleMapper.java:179)
at com.bea.p13n.entitlements.accesscontroller.AccessController.isAccessAllowed(AccessController.java:143)
at com.bea.portal.entitlement.util.EntitlementHelper.isAccessAllowed(EntitlementHelper.java:285)
at com.bea.portal.entitlement.util.EntitlementHelper.checkEntitlementInternal(EntitlementHelper.java:231)
at com.bea.portal.entitlement.util.EntitlementHelper.checkEntitlement(EntitlementHelper.java:144)
at com.bea.portal.manager.internal.UserPortalStatePolicy.checkPortletEntitlement(UserPortalStatePolicy.java:636)
at com.bea.portal.manager.internal.UserPortalStatePolicy.generateUserPageState(UserPortalStatePolicy.java:567)
at com.bea.portal.manager.internal.UserPortalStatePolicy.generateUserPortalState(UserPortalStatePolicy.java:293)
at com.bea.portal.manager.internal.PortalManagerDelegateImpl.getUserPortalState(PortalManagerDelegateImpl.java:179)
at com.bea.portal.manager.ejb.internal.PortalManagerBean.getUserPortalState(PortalManagerBean.java:70)
at com.bea.portal.manager.ejb.internal.PortalManagerBean_w6xny9_EOImpl.getUserPortalState(PortalManagerBean_w6xny9_EOImpl.java:370)
at com.bea.portal.appflow.internal.PortalRequestImpl.getPortalState(PortalRequestImpl.java:148)
at com.bea.portal.render.servlets.jsp.PortalRenderHelper.getSelectedSkin(PortalRenderHelper.java:167)
at jsp_servlet._framework._security.__login._jspService(login.inc:11)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:445)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:20)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.RequestDispatcherImpl$ForwardAction.run(RequestDispatcherImpl.java:345)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:252)
at com.bea.p13n.appflow.webflow.servlets.internal.WebflowServlet.doGet(WebflowServlet.java:178)
at com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.doGet(PortalWebflowServlet.java:235)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:20)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.p13n.tracking.clickthrough.ClickThroughEventFilter.doFilter(ClickThroughEventFilter.java:156)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5451)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3105)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2588)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
Regards,
Vinod Thapliyal

The WebLogic Server (WLS) is a Java container similar to OC4J in Application Server 10g release 2. If you want to use WLS, you will have to upgrade your Application Server 10g installation to Fusion Middleware 11g. The upgrade path typically depends on the products which you are using in 10g, e.g. the upgrade path for SOA is different than the upgrade path for Forms/Reports or Oracle Portal. The [url http://docs.oracle.com/cd/E23943_01/upgrade.1111/e10125/before_you_begin.htm]Upgrade Planning Guide is a good start.
Thanks,
EJ

Apache and Weblogic - Performance issue

Hi Anuj,
This question should be directed to the weblogic.developer.interest.plug-in
group.
Regarding this issue, this is normal -- the access.log for WebLogic shows
the requests from the proxy. But, instead of showing you the IP address of
the proxy server, it instead shows you the IP address of the client. You
can also verify that this is a different request because the connection to
the proxy server used HTTP/1.1, and the connection to WLS used HTTP/1.0 --
this is the protocol that the proxy plug-in uses to communicate with WLS.
So, in summary, there is only one request made by the client per image, and
the plug-in is in turn making a request to WLS for each image.
Dennis Munsie
Developer Relations Engineer
BEA Support
"Anuj Nijhawan" <[email protected]> wrote in message
news:3c20e890$[email protected]..
>
We have a setup with apache acting as web server and BEA as app server.But it
seems both of them are serving images to the web browser at the same time.This
is consuming lots of memory. Can anybody help rectifing this,
here's what each log file's say,
first Apache (access_log) shows that it served it up:
172.20.100.142 - - [19/Dec/2001:01:20:24 -0800] "GET /img/divider.gif
HTTP/1.1"
304 0
172.20.100.142 - - [19/Dec/2001:01:20:24 -0800] "GET
/img/i_user_collection.gif
HTTP/1.1" 304 0
172.20.100.142 - - [19/Dec/2001:01:20:24 -0800] "GET
/img/sort_last_manual.gif H
Then BEA (access.log) shows it too:
172.20.100.142 - - [19/Dec/2001:01:20:24 -0800] "GET /img/divider.gif
HTTP/1.0"
304 0
172.20.100.142 - - [19/Dec/2001:01:20:24 -0800] "GET
/img/i_user_collection.gif
HTTP/1.0" 304 0
172.20.100.142 - - [19/Dec/2001:01:20:24 -0800] "GET
/img/sort_manual.gif HTTP/1
.0" 304 0

Proxy between Apache and Weblogic

Similar Messages

Maybe you are looking for