Problems between iPlanet and Weblogic

Hi guys, I'm having a problem, we I try to access the application through the iPlanet. The iPlanet crash and it restarts again.
I got this message on the errors log of the iPlanet
[17/Sep/2009:11:42:48] catastrophe (14873): CORE3260: Server crash detected (signal SIGSEGV)
[17/Sep/2009:11:42:48] info (14873): CORE3261: Crash occurred in NSAPI SAF wl-proxy
[17/Sep/2009:11:42:48] info (14873): CORE3262: Crash occurred in function INTcrit_enter from module /opt/iplanet/bin/https/lib/libns-httpd40.so
[17/Sep/2009:11:42:48] failure (14819): CORE3107: Child process closed admin channel
[17/Sep/2009:11:42:48] fine (14819): CORE3061: signal_handler_thread: received signal 18
[17/Sep/2009:11:42:48] fine (14819): CORE3049: Primordial process detected child 14873 died: status 11
[17/Sep/2009:11:42:48] fine (14819): CORE3050: Is our child, will spawn replacement
[17/Sep/2009:11:42:48] fine (14819): CORE3062: Unlinking of /tmp/https-emergo2.cert.sabre.com.443-3b90a480/.cgistub_14873 returned -1
I can add the the iplanet we are using is the 6.1sp5 and the weblogic is the version 9. everything is working on sun 9.
I'm going to appreciate any help.
Thanks

Did you get SSL authentication on iPlanet AND forwarding this to WLS
working?
We can do certificate based authentication on iPlanet and the plugin
forwards this to WLS (6.0sp1). WLS does not do anything with it.
Thanks,
Ronald
Vlatas wrote:
The trusted CA file holds the root CA certificates that will be trusted by
the proxy plugin. So if your
App server has CertA from Verisign, and CertA was issued by a Verisign CA
certificate, then you
want to have the Verisign CA certificate in the trusted CA file for the
proxy plugin.
Also, look in /tmp/wlproxy.log, errors should be getting logged in there
that will help determine the
problem.
Tony
"caris" <[email protected]> wrote in message
news:3b0dbfb4$[email protected]..
I'm using WebLogic 6.0 and iPlanet 4.1 for my application.
I've got certificate from Versign for WebLogic and tested it well for
standalone
App Server.
However, when I use iPlanet for proxy, the page doesn't display at all.
Here is
my config statement for iPlanet
<Object name="weblogic" ppath="*/*">Service fn=wl-proxy
WebLogicHost=localhost
WebLogicPort=7002 SecureProxy=ON
TrustedCAFile="c:/bea/wlserver6.0sp1/config/mydomain/getcacert.cer"</Object>
Am I get it right? And I wonder what should it be put in the field
"TrustedCAFile"
By the way, I've got the certificate for the iPlanet Web Server too.
It works fine for iPlanet with SSL pointing to the WebLogic port 7001.
However it can't work at all when I pointing to the port 7002..
Thanks for any ppl who can help me..

Similar Messages

SSL Acceleration between iPlanet and WLS

I was wondering if anybody has successfully deployed a SSL accelerator card for SSL acceleration between iPlanet and WLS?

This is a feature in the latest release, WebLogic Server 6.1.0
          <http://e-docs.bea.com/wls/docs61/////adminguide/nsapi.html#101168>. It is
          not available for WebLogic Server 5.1.0.
          Regards,
          -- Ian
          "Abhinandan" <[email protected]> wrote in message
          news:3ba5dfa9$[email protected]..
          > Can i get SSL communication between iPlanet and Weblogic 5.1? if yes then
          how??

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.

Do any of you experience Im having with my ipad? I can't make a comment in Facebook for older posts and I can't open numerous comments from old posts of my friends. but everything works perfectly when I use laptop. is there problem between apple and FB?

do any of you experience Im having with my ipad? I can't make a comment in Facebook for older posts and I can't open numerous comments from old posts of my friends. but everything works perfectly when I use my laptop(non-apple). is there problem between apple and FB?

Facebook apparently has their site coded poorly for tablets with touch screens. Try using the Facebook app. It is not perfect either but it is better than view in a browser lately.

Problems between PE4 and 10

I have a drawing that was resized to a certain length using PE4. I have now upgraded to PE10 and when I print the drawing , it prints 3-4 times larger than what it should be. When I view the drawing, the ruler at the top of the screen shows it being the correct length and when I checked the deminsion in the resize box, it also has the correct length. Have I done something wrong or should I delete the drawing and start over from scratch?

Could you be a little more specific please? Sorry, I am not a tech guy just a poor laymen.
Date: Thu, 2 Aug 2012 20:30:55 -0600
From: [email protected]
To: [email protected]
Subject: Problems between PE4 and 10
    Re: Problems between PE4 and 10
    created by photodrawken in Photoshop Elements - View the full discussion
Check your PSE print settings, especially the DPI value in the "Print Quality". Ken
     Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4595437#4595437
     To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4595437#4595437. In the Actions box on the right, click the Stop Email Notifications link.
     Start a new discussion in Photoshop Elements by email or at Adobe Forums
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Problems with AM and WebLogic 8.1 sp3

Hello,
The following are my environment. (both on Solaris 10)
- Sun AM
- WebLogic 8.1 sp3
I want to try an easy integration between AM and WebLogic. After I installed policy agent for WebLogic and properly configured. It seem to work at some basic level.
When I try to access protected resource on WebLogic. The agent can intercept and redirect to AM's login page where I enter username and password. After I enter correct username and password, it will be redirected back to my protected resource. However, this time I got error 403 forbidden.
I think this is because WebLogic doesn't know that I just already sign-in. There must be something needed to do to map AM's userid to WebLogic id.
But I don't know how.
Could someone give me some suggestion or point me to some documents? Thanks in advance.

I meant creating a policy in the SAM web interface, where you can add the required rule (specifying resource) and the subjects to whom the policy is applicable.
Of course, if you are using J2EE_POLICY, the URL policy is of no consequence. The best practice is to use amFilter.mode = ALL, where the J2EE policies are enforced and verified by the application / app server, and the URL's are protected by SAM as well. In that case, the user has to be authorized by both SAM as well as J2EE to access the application.
This, of course, is subject to the "best of my knowledge" clause!

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

How can I fix a problem between Firefox and my printer? When I try to print a window appears Save as ,then another saying Firefox not responding and printing does not work

I used to be able to print correctly using Firefox as my browser,but something changed in the last month or so,possibly after a Firefox update. I`m not really sure how it happened but there seems to be a problem between Firefox and my printer. So I have been using Internet Explorer as my default so I can print. I would prefer to use Firefox again since that is where my bookmarks are. Is there a way to get the connection between Firefox and my printer back?

'''Save as''' = sounds like you don't have your printer selected, or you have ''Print to file'' selected
http://kb.mozillazine.org/Problems_printing_web_pages

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

Problems with IIS and Weblogic 6.0 Redirecting thru IIS

Hi
I have just installed Welblogic 6.0 and I am having problems with the configuration
of the ISAPI Plugin.
I created the iisproxy.ini file and then copied that into wlserver6.0/bin directory
and copied the iisproxy.dll file into the inetpub/wwroot directory for iis to
see
Now when I type in my url, I get the default index.jsp page that bea supplied
but when I try to go to the Admin tool, existing portals created or new portals
added, I get the following error
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
Can any one help, here is my iisproxy.ini file
below
#This file contains initialization name/value pairs
#for the IIS/weblogic plug-in
WebLogicHost=localhost
WebLogicPort=7501
WlFowardPath=/weblogic
SecureProxy=OFF
PathTrim=/weblogic
ConnectTimeoutSecs=20
ConnectRetrySecs=2
Bola

Seems 6.0 has more than a few proxy problems. We are running IPlanet and have
had no success in running the 6.0 proxy.
FYI. We have started using the 5.1 proxy in 6.0 successfully; you might give
it a try. Not sure we want to put this in production in this condition however.
Matt Raible wrote:
Has anyone been successfully able to get the IIS Proxy working with WLS 6.0
on Win2K? I've been trying for days, working with a support engineer at BEA
and everything, but no luck.
Thanks,
Matt

Communication problem between NetBeans and Tomcat

hi!
i got a quite mysterious problem. here is what happens:
- i start NetBeans 5.5.1 (the first time)
- i want to debug my JSF-Project, the Debugger starts
- After a few seconds the debugger waits for tomcat (it sais: "Waiting for Tomcat...") and tomcat starts
- Again after a few seconds the tomcat-debugger-output sais "Tomcat startet in 3333 ms".
okay.
when i enter http://localhost:8084/ in my browser i get the tomcat homepage, so the server has definitely started! But nothing happens in NetBeans and nothing happens with my project....
In the lower-right corner i see this blue working-bar that sais "deploying project" but nothing happens. The Project-Debugger-Output still sais "Waiting for Tomcat..." but nothing happens...
And after something around 3 minutes (i guess it's a timeout) i get the error "Starting of Tomcat failed." But is HAS started, i can login to the Administration-Area in my browser!
so i guess there is a communication problem between netbeans an tomcat. Netbeans waits for a message from tomcat but tomcat doesn't send it..or netbeans doesn't understand it.
But the story goes on:
When i press the debug-button a second time it takes only a few seconds till i get the message: "Tomcat server port 8084 already in use". OF COURSE! Because Tomcat has already startet and can't be stoped by NetBeans.
i'm trying to solve this problem for 4 days now, so i would be very happy if anyone has an idea where to start/continue the search...
thanks,
flo.
some system-info:
- windows vista business 32-bit
- no firewall is running
- AntiVir Personal Edition IS running
- Yahoo Widgets Engine IS running
- no other software is running
and finally the tomcat-log:
Using CATALINA_BASE: C:\Users\Administrator\.netbeans\5.5.1\apache-tomcat-5.5.17_base
Using CATALINA_HOME: C:\Program Files\NetBeans\enterprise3\apache-tomcat-5.5.17
Using CATALINA_TMPDIR: C:\Users\Administrator\.netbeans\5.5.1\apache-tomcat-5.5.17_base\temp
Using JRE_HOME: C:\Program Files\Java\jdk1.5.0_12
Listening for transport dt_shmem at address: tomcat_shared_memory_id
21.09.2007 18:27:50 org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.5.0_12\bin;.;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\ThinkPad\ConnectUtilities;C:\Program Files\Common Files\Teleca Shared;C:\Program Files\Common Files\Adobe\AGL;C:\Program Files\MySQL\MySQL Server 5.0\bin;C:\Program Files\cvsnt;
21.09.2007 18:27:50 org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8084
21.09.2007 18:27:50 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1862 ms
21.09.2007 18:27:50 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
21.09.2007 18:27:50 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.17
21.09.2007 18:27:50 org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
21.09.2007 18:27:53 org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8084
21.09.2007 18:27:54 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
21.09.2007 18:27:54 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/31 config=null
21.09.2007 18:27:54 org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
21.09.2007 18:27:54 org.apache.catalina.startup.Catalina start
INFO: Server startup in 3626 ms

As i wrote before, the same problem occured for me. I have found a solution which is : Go to tools menu and then select options . In the proxy info, select No Proxy.
I hope this help you

RFC Sender problem between 46D and RFC adapter

Hi,
I have this simple integration scenario where I want to send data to a archiving system;
SAP -> (tRFC) -> XI -> (MQ) -> BizTalk -> (MQ) Arch.syst.
SAP side ***
A Z-program using a Z func. like;
    CALL FUNCTION 'ZSD_DCF_SEND_TAG'
      IN BACKGROUND TASK
      DESTINATION 'XISYSTEM_TRFC_DCF'
      EXPORTING
        pt_filing_info = gt_filing.
    COMMIT WORK AND WAIT.
XI side ***
Both IR and ID is configured correctly, in the development environment everything works just great. I have created a test program where I can define how many calls I will do, looping over the func. call with a commit inside the loop - 500 or more msgs are ok.
The integration scenario is transported to quality enviroment using CMS, and the RFC sender comm.ch. is configured accordingly.
The problem in quality ***
When sending just 1 msg, everything is just fine, message received and delivered to MQ.
When sending >= 2 msgs, the 1 msg is always ok, BUT all others fails due to the following from Adapter monitor;
RFC_HISTORY
- Error: 2006-01-19 10:55:18 CET: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'RFCSender_XI0002' (02d4d30de3593874942ed0659add0827, party '', schema 'TechnicalSystem', identifier 'Q93#120')
- OK: 2006-01-19 10:55:17 CET: Message processed for interface ZSD_DCF_SEND_TAG
My sending system is Q93 CLI 505 so I can understand the error, BUT I cannot understand why the RFC adapter is saying the TechnicalSystem is Q93#120 - it should be Q93#505. My Q XI has client 120...
It seems to me that the RFC adapter is kind of confused about the sender..
I have created a OSS message and SAP has looged on and looked into it with both a XI expert and RFC expert without being able to answer - all is configured correctly.
- The SLD config. for bus.system Q93 is ok -
- The bus.system in ID is showing correct vaues for
Adapter Specific Identifiers (SID Q93, client 505)
- Both Dev. and Qual. environment are running on XI 3.0 SP 14 latest patch, RFC component version on the SAP side is identical between dev. and qual. SAP systems
- It doesn't matter which gw I use (Q93 gw or XI gw), the error is persistent
- It doesn't matter if I increase initial conn, max conn.
I have also tried to use qRFC instead, but with the same result.
Anyone using tRFC for asynch. communication from SAP to XI seeing something similar?
Meanwhile, I will do RFC trace on GW and RFC Adapter on AE....
Please, do not say SP15, oss msg for FAQ RFC adapter or links to RFCAdapter config....
best regards
Torstein

Hi,
SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
<i>Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".</i>
- Give correct appserver and gateway service details in XI.
- Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek

Problems between Xcelsius and WebDynpro for Java

How should I do to show Xcelsius in WebDynpro for Java?
How should I transport data between Xcelsius and WebDynpro?
How should I control WebDynpro with Xcelsius?For example,firing plugs in Xcelsius like in WebDynpro to change one view to another.
How should I do to execute a Java method in Xcelsius?For example,scheduling a job on clicking a button in Xcelsius.
Besides these,I also want to know the same problems between other BOE contents and WebDynpro for Java.
Regards,
Abe

Hi Pradeep:
Well that purely depends on the business application (project) your client is proposing. Following are very few factors which will drive for creating web-based applications:
VC: it's a UI modeling tool (non-programming) for creating rapid creation of web-based applications.
WD: its a powered by Java and ABAP with which you can create robust business applications.
If your client is very choosy about rapid application development, reporting, rich user interface, to reduce TCO then VC is the choice. Or if the project contains typical integration with SAP and non-SAP systems, complex business logic development, integration with WCM systems...etc then WDJ is the option.
If youve some sort of custom development with facilitating the Development Infrastructure (NWDI) then WDJ is the only option I could say.
We hope with NW CE 7.1.1(referred by Priyanka Singh) tighter integration between these TWO tools may over come the ambiguity of using them.
Tnx,
MS

Color problems between Lr5 and other software

I can not see where to make adjustments to get the same tones between Lr and my other software: Photoshop, Irfanview, Windows Viewer ...
My test conditions:
My monitor is calibrated
... - Export Lr Jpeg quality 85% and also tests 16bit TIFF (sRGB, Adobe rgb and prophoto)
... - When exporting, I checked the "add to catalog" to view the same image in Lr.
Conclusion: Other software gives almost the same tones (some small differences due to the chosen color space) and Lr gives a much warmer picture (Raw or treated Jgeg reimported in the catalog). Will it have a preference of Lr to settle?
Note: the direct opening of RAW file in Photoshop with Camera Raw (same engine as Lr) without special settings, also gives a duller color different image, that directly Lr.
What is the solution?

In general, any difference between Lightroom and other color managed software is indicative of a corrupt monitor profile. No idea about Irfanview, but Lightroom, Photoshop and Windows Photo Viewer should all display identically.
What they all do is convert from the source/document color space to the target color space, which for display is your monitor profile. The result should be identical - that is in fact the whole point of color management. But since the source space may be different the actual conversion itself may also be different. So one conversion may go bad but not others.
A difference between Library and Develop will have the same explanation (different source spaces; Library is Adobe RGB while Develop is linear ProPhoto).
It also happens that different applications react differently to a bad monitor profile. It may work in one application and fail in others.
Any software that is not color managed will simply display in the native monitor color space, which can be anything under the sun, so you can just ignore and disregard that. It won't be accurate anyway.
So the solution is to have a valid and healthy monitor profile. Then everything color managed will display identically (save for gamut differences, but in practice that only applies if you have a wide gamut monitor. With a standard monitor any source space will have equal or larger gamut than the monitor).
Some calibration software has been known to not follow specifications strictly at all times, so check for updated software. Or the profile can simply have become corrupt. It happens. A way to test this is to set sRGB as default monitor profile in the OS - or Adobe RGB if you have a wide gamut monitor - and see if the problem clears.

Is there a problem with JMS and Weblogic?

          Hi,
          I am using JMS and Weblogic (Not Message Driven bean).
          My problem is that after some time my listeners disappears.
          I am sending them a message and instead of 6 listeners
          I get only 4 messages.
          So, My question is: Is there any problem working with JMS
          and Weblogic???
          Thanks,
          Tal.


Too little information and a very vague question. Need more info.
          "Tal" <[email protected]> wrote in message
          news:[email protected]..
          >
          > Hi,
          > I am using JMS and Weblogic (Not Message Driven bean).
          > My problem is that after some time my listeners disappears.
          > I am sending them a message and instead of 6 listeners
          > I get only 4 messages.
          > So, My question is: Is there any problem working with JMS
          > and Weblogic???
          > Thanks,
          > Tal.

Problems between iPlanet and Weblogic

Similar Messages

Maybe you are looking for