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?

Similar Messages

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

Testing SSL Connections, differences between ABAP and JAVA stacks

Hello,
   I am trying to test an outbound SSL connection to a partner.   I already have multiple outbound connections to many partners, but this new one is causing an issue.   Our firewalls between the two sites are opened as required, I verified that I can telnet to the 443 port of their sever.   I then attempted to connect to their URL, via a Java SOAP message, and it is rejected. Some kind of error regarding our handshake.
   In an attempt to troubleshoot the issue I entered their URL in SM59 as a HTTPS connection, tested it, it worked fine.   Which indicates to me that the ABAP side works fine.
   I do the same on the Java stack, via the SOA Manager: Destinations, and it fails.
"Error during ping operation: Error while silently connecting org.w3c.www.protocol.http.Http.Eception: Peer sent alert: Alert Fatal: unexpected message"
I was thinking that maybe the remote partner only allows specific types of SSL version connection, and the Java side is too low. i.e. the partner only allows TLS v1, and we are attempting to use SSL v2.    Is there a place to set this on the Java side? I know I can set inbound parameters on ICM via SMICM.
Any help or assistance would be most appreciated.
Thanks,
Michael Montone

Hi,
I suggest that you verify if you use the same release of the SAP Cryptolib for the ABAP and the Java stack.
This could explain a difference of support for SSL or TLS.
Regards,
Olivier

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

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

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

(UIX XML) Sharing Connection objects between BC4J and custom java.

If I have a UIX XML page that contains some BC4J application modules, then in the event handler I call [public static EventResult handleMyEventEvent (BajaContext context, Page page, PageEvent event..) ], which in turn calls some java classes I have written that take a java.sql.Connection object and access the database doing some updates/inserts with this Connection object (via JDBC)....HOW CAN I USE THE SAME TRANSACTION AS WAS USED IN THE BC4J APPLICATION MODULE...i.e. CAN I SHARE THE CONNECTION OBJECT BETWEEN BC4J AND MY OWN JAVA CLASSES THAT USE JDBC?
What are the best ways to share such a transaction?
Thanks,
Paul.

Would it be easier to use a custom method on the bc4j Application module?
Take this scenario...
1. User opens UIX XML web page which opens a bc4j App Module..it has a VO based on all employees.
2. User presses the add button and a new employee is created (using the bc4j App Module).
(Notice: no commit yet!)
3. User presses the submit button...fires event REVIEW_SALARY.
4. This event is 'handled' in the event section of the UML XML...it calls:-
public static EventResult handleREVIEW_SALARYEvent (BajaContext context, Page page, PageEvent event)...
5. I now want to call a java class I wrote that computes an employees new salary and updates the employee record with this new salary. This update will fail unless it is part of the same transaction as the one used by the bc4j App Module (that inserted the new employee).
How best to proceed from here?
How about having a method on the bc4j App Mod's VO called 'reviewSalary'? Calling this would use the same transaction? I could then call my java class from within the VO's method? However do I still have the same problem in that my java class expects to be passed the connection object?
The approach you suggested previously seems a touch dangerous....in that these are not 'publically exposed'...and a new release of JDev may break my code.
Thanks,
Paul.

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.

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

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

SSL Connectivity Configuration

Hi,
I installed the SSL Certificates on the windows machine where our CPO server is configured. And I also configured the web service adapter to use secured authentication on the default port.
Is there anything else I would need to configure other than the above inorder to have the SSL connectivity? Also are there any standard tests I can perform from CPO inorder to validate this configuration.
Thanks,
Greg

You need to make sure you have followed all the steps on page 12 of the Northbound Web Services guide. If you have you can test by opening a browser and going to https:// teo server>:/WS/Process?WSDL
You can test with portal feeding information in or you can run web service executes (in CPO) against it to further test.

ESS/MSS sso configure between java and abap instance

Dear Gurus,
I want to configure sso between java and abap instance for ESS/MSS. I couldnt find any guide for it, could you please help me gurus ?
Other question is, is there any specific role for ESS/MSS users in JAVA instance. I want to create users and assign this role to them.
Best Regards

Hi Kemal,
Hope you are doing good.
There should be a / in the ITS path before SAP.
Basically the entry that you have mentioned here should be accessible via browser as well. For eg in your case:
http://<its hist name>/sap/bc/gui/sap/its/webgui should be accessible over browser.
I also think you have put in a extra space in "w ebgui". It should be "webgui".
If the connector settings are working, then we can be sure that system connection is fine. You do not need to configure ITS settings.
Also for SSO, refer the SAP note:1083421 and configure the SS0 settings again.
Please run the SSO2 wizard and then make the automatic connection to
the abap server. This will solve any inconsistencies on the server
due to manual interventions.
Most likely reason for the error is that certificates were loaded
manually rather than using SSO wizard.
More help:
<http://wiki.sdn.sap.com/wiki/display/EP/Troubleshooting+SSO+between+AS-ABAP+and+AS-JAVA>
The SSO enabling parameters should be set on the R/3 server.
SSO Logon Ticket-> login/accept_sso2_ticket and login/create_sso2_ticket
More info:
<http://help.sap.com/saphelp_nw04/Helpdata/EN/22/41c43ac23cef2fe10000000a114084/frameset.htm>
Thank you and have a nice day :).
Kind Regards,
Hemanth
SAP AGS

Apache and Weblogic authentication

Apache 2.0 and WL 8.1 SP6;
Apache redirects to a wl web app and the web app's front page is password protected using Apache's authentication services.
Turns out, the users configured with Apache's 'htpasswd' have to be duplicated in weblogic. Curious to know why this is. There appears to be no documentation of this necessity that I could find.
Any ideas about the configuration principles involved here?
Thanks,
Karoly

Hi Scott,
The only way it can work is when Apache adds another token to the request
say
MyToken : value
U can create a Custom Identity Asserter to read that token and authenticate the user.
U can find the steps to create custom identity asserter here
http://weblogic-wonders.com/weblogic/2010/03/15/custom-identity-asserter-for-weblogic-server/
HTH,
Faisal

Connecting OC48 Between ASR9K and ASR1K

Hi there.
I don't know the first thing about the WAN something like POS...
Now I'm facing some problem with connecting OC48(POS) between ASR9K and ASR1K.
There are new 9K and new 1K in same server rack for the test.
So i tried to test these for connecting OC48
9K and 1K is directly connected by OC48
9K : A9K-SIP-700 // SPA-2XOC48POS/RPR // SFP-OC48-SR
1K : ASR1000-SIP10 // SPA-1XOC48-POS // SFP-OC48-SR
After connecting these two devices directly, ASR1K shows the interface status is up/up
but ASR9K ... the interface status is down/down.
I didn't configure anything. Do i need to configure something ?
When i connected POS port 1 and POS port 2 directly in the same ASR 9K chassis, the interface is up/up
please help me out
Thank you in advance. :)

exactly, so the transmit side of the 9k needs to be connected to the receive side of the 1k.
the transmit side of the 1k needs to be connected to the receive side of the 9k.
download this doc for reference:
http://www.cisco.com/c/en/us/td/docs/interfaces_modules/shared_port_adapters/install_upgrade/ASR1000/asr_sip_spa_hw/ASRsov.html#pgfId-1136398
Another link discussing the type of testing you are attempting:
http://www.cisco.com/c/en/us/support/docs/optical/synchronous-optical-network-sonet/16181-posclocking-16181.html

SSL Connection Configuration between Apache and Weblogic 8,1

Similar Messages

Maybe you are looking for