Http Proxy To JMS Proxy Call

Hi,
When i am trying to route a request from a http proxy service to JMS proxy i got following exception.
Exception on TransportManagerImpl.receiveMessage, com.bea.wli.sb.transports.TransportException: No transport information is registered for: ProxyService AssetInbound/ProxyService/AssetInboundjms
com.bea.wli.sb.transports.TransportException: No transport information is registered for: ProxyService AssetInbound/ProxyService/AssetInboundjms
     at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:201)
     at com.bea.wli.sb.transports.jms.JmsInboundMDB.onMessage(JmsInboundMDB.java:108)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:291)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4060)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3953)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4467)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
If anyone has faced such problem or know what am i doing incorrect kindly reply.
Regards,
Sandeep

Routing a message from an HTTP proxy to a JMS proxy will put the message in an intermediary queue before it is read by the JMS proxy. I haven't seen this exception before so I advise you to open a support case.
As a workaround you can route the message to a JMS business service to put the message in the queue and see if it solves your issue.
Gregory Haardt
ALSB Prg. Manager
[email protected]

Similar Messages

  • OSB JMS Proxy

    Hi ,
    can i use a Proxy service with out a Business service to write a messge onto a queue.I jus tried a sample on my local and i am able to write a message on to a queue using a proxy service .
    Flow :-
    PS1(http) using publish action invokes -> PS2 (jms uri config)
    I am clue less how this is working.when the PS2 transport has been defined as jms ,how am i able to invoke it from PS1 using publish action?
    My understanding of OSB is ProxyService is for reading message from queue and Business service is for writing or publishing a message onto a queue.
    can some body help me udnerstand how this is working.

    Basically, you're right when it comes to the difference between business and proxy services. Also, you're not the only confused when routing data from http-based proxy to JMS proxy.
    We touched the topic earlier:
    Re: Retry mechanism for HTTP Transport in OSB
    The point is your layout (HTTP PS -> JMS PS) is sound and works even without intermediate business service.

  • OSB -11g - Calling JMS Proxy Service in a stage

    Hi,
    When we createa JMS based proxy service, the proxy service keeps on polling the JMS Queue for any new messages arriving in the queue. But I do not want the proxy service to keep on polling the Queue. Instead I want to call the JMS Proxy Service in any stage (of any other Proxy Service) using a service callout. It means that I do not want the Queue to be polled always, instead the queue should be polled only when this JMS Proxy Service is invoked.
    Is it possible to do? If so, how?
    Thanks,
    Sanjay

    Hi Anuj,
    Following is my requirement:
    The producer wants to interact with us using Web Services. The input payload has some more values (username and password) apart from the HL7 data (base64 encoded) itself. I have to receive the input payload, authenticate the call and convert the HL7 encoded message into an XML and send it to the consumer.
    What have I done till now:
    1) I have created two Proxy Services PS1 and PS2
    2) Proxy Service (PS1) will be invoked by the producer.
    3) Then I get the username, password and data from the payload
    4) Populate the username and password in the SOAP Header and HL7 data in SOAP Body
    5) Call PS2 from PS1
    6) In PS2 I have configured Message Level Security to authenticate with the username and password
    7) After authentication I make a Java Callout to decode the base64 encoded HL7 data
    8) I now have written my own HL7 sender (Java code) which wraps the decoded HL7 data with MLLP requirements and then send it to the B2B server using a Socket (TCP connection). I do a Java Callout to this Java class.
    9) In B2B I have configured a RTP (Remote Trading Partner) which has a MLLP channel.
    10) I created a ADT message document and a ACK document
    11) I created two agreements between HTP and RTP (one agreement receives the HL7 data from the TRP using MLLP and another which sends the ACK to the RTP using MLLP channel)
    12) In the receiveing agreement I have configured a JMS channel (on the HTP side) becuase of which B2B receives the HL7 Pipe delimited data and translates it and then pushes the XML data into the JMS queue (which needs to be transformed to producer XML)
    13) I have also configured a JMS channel for the RTP which I am using in second agreement to get the acknowledgement. Because of this the ACK is placed in a JMS queue.
    I need to poll this JMS queue in order to send the ACK back to the producer (which I have to do in the response pipeline of PS2). Hence I wanted to pop the message from the JMS queue in the response pipeline and then send that message.
    Please advice if my approach is correct.
    Thanks,
    Sanjay
    Edited by: Sanjay Bharatiya on 17-Mar-2011 12:06 PM

  • Java client for OSB proxy with JMS Transport

    Hi,
    I am trying to call OSB proxy with JMS Transport. I am generating the client through ant task clientgen and following this article
    http://www.oracle.com/technetwork/articles/murphy-soa-jms-092653.html
    The osb proxy is req-response and is simply routing to BS which return a string value.
    When I run my client, it get stuck and does not return at all. Has any one trying java client in such scenario?
    What I may be missing?
    Below is snipped of client code:
    String url = "http://localhost:7021/sbresource?PROXY/MySample/MyJMSProxyService";
    CreditLoanApprovalServiceSoapBindingQSService service = new CreditLoanApprovalServiceSoapBindingQSService_Impl(url);
    MyPortType port = service.getCreditLoanApprovalServiceSoapBindingQSPort();
    LoanStruct in = new LoanStruct(); //populated the data structure
    String loanResult = port.processLoanApp(in); // Stuck here without any error
    System.out.println("LoanResult--> " + loanResult);
    Thx
    /Ashwani

    http://localhost:7021/sbresource?PROXY/MySample/MyJMSProxyService is the WSDL URL of the proxy.
    Transport is is picked by the client from wsdl.
    As far as the documentation of client generation is there, there is no change.
    But meanwhile I have started working on sending the message directly to queue. JMSProxy is getting called. May be I will first run the proxy this way and then try troubleshooting the java client.
    Regards
    Ashwani

  • JMS proxy and XA connection factory

    Hi all,
    I would like to ask you what is the best practice to adopt about the scenario described below.
    A JMS proxy retrieves a message and processes it.
    Any error could occurr during processing it and, in case of errors, the JMS proxy error handler publishes the message on ad hoc recovery destination D.
    (later another app will check failed messages for fixing & republishing them into ALSB).
    In that scenario we have the JMS proxy and the jms business service that, in case of errors, publishes on destination D.
    Should the JMS proxy and the business service use both a XA connection factory in order to perform all the above steps in one transaction ?
    Otherwise if the business service itself fails publishing on destination D, the message retrieved by the JMS proxy is lost and not re-delivered to the JMS proxy.
    Or XA connection factory is not needed and could I use
    Routing Options with exactly once or both are needed ?
    Thanks
    ferp

    Hi all,
    I did some tests and follow what I've achieved.
    Scenario 1.
    - Precondition
    -- A JMS proxy with XA factory + Error Destination (MyRecoveryQueue)
    -- A business service BS with XA factory that publishes into MyOutboundQueue
    -- No "exactly once" routing option used calling BS
    -- an error is forced in the pipeline
    - Flow
    -- proxy retrieves a message and try to publish it using BS
    -- an error is forced in the pipeline:
    --- transaction is rolled back, message redelivered to proxy
    --- the message is posted to the error destination after all the retries failed
    Scenario 2.
    - Precondition
    -- As 1. but no error is forced in the pipeline
    -- the MyOutboundQueue destination queue is paused
    - Flow
    -- proxy retrieves a message and try to publish it using BS
    -- BS fails to publish it on MyOutboundQueue (because it is paused)
    --- transaction is rolled back, message redelivered to proxy
    --- the message is posted to the error destination after all the retries failed
    Scenario 2A.
    - Precondition
    -- As 2. with MyOutboundQueue paused and resumed
    - Flow:
    -- proxy retrieves a message and try to publish it using BS
    -- BS fails to publish it on MyOutboundQueue (because it is paused)
    --- transaction is rolled back, message redelivered to proxy
    --- before all the retries failed the queue is resumed
    --- BS succeeds to publish the message
    Scenario 3.
    - Precondition
    -- A JMS proxy with NO XA factory + Error Destination
    -- A business service BS with NO XA factory
    -- No "exactly once" routing option used calling BS
    -- an error is forced in the pipeline
    - Flow
    -- proxy retrieves a message and try to publish it using BS
    -- an error is forced in the pipeline:
    --- transaction is NOT rolled back, message NOT redelivered to proxy
    -- so
    --- no message delivered to MyOutboundQueue2 destination
    --- no message delivered to MyRecoveryQueue2 destination
    --- message consumed from MyQueue2 and now is lost!
    To publish message into MyRecoveryQueue2 a proxy error handler has to be added and here added explicit publish to MyRecoveryQueue2.
    But naturally in that case if in the proxy error handler, the explicit publish fails or any error occurrs no message is delivered to recovery queue.
    So if I'm not using an XAFactory the message is auto-acknowledged as soon as it is read and I've to use XA factory if I want the message to be put back in the queue in case of errors and the retry to happen.
    So both my proxy service and business service use an XA factory.
    Regards
    ferp

  • JMS Proxy to Web Service Problem

    Hi All,
    I have a JMS proxy that routes messages to a web service. I have set the delivery failure parameters on the JMS queue. When a message is put onto the queue and there is a problem within the message flow proper, the message is retried the appropriate number of times and put onto the Error Destination queue as necessary. However, if there is a problem calling the web service, message delivery is NOT retried, the message is NOT put onto the Error Destination queue, and the message is lost. The web service itself isn't throwing a SOAP Fault, but the business service can't reach the web service (firewall issue). My Route Error Handler in the message flow is hit and it performs a Reply With Failure.
    Can anyone please explain to me if this is by design and, if so, why? Also, how does a person work around this? I need the message to be retried. I understand that a web service cannot participate in an XA transaction, but it seems to me any failure within the message flow should cause a retry on the JMS queue.
    Thanks.
    Edited by mvcg at 06/11/2008 1:57 PM

    You should remove the Route Node since it should only be used in HttpProxy.
    Instead use just the request pipeline for your routing.
    if (condition1)
    Service Callout (or publish) to Service1
    else if (condition2)
    Service Callout (or publish) to Service2
    else
    Rasie error?
    You shouldn't need to reply with failure. Any errors in the service callout or publish should go to exception handling if you use QoS exactly-once.

  • Proxy to JMS and JMS to Proxy - Szenario

    Hi @all,
    i've implemented an async scenario:
    Proxy to JMS (away, request)
    JMS to Proxy (way back, response)
    Backend is ECC 6.0 and Middleware is PI 7.1.
    Business Case: Run a request with a number, get an answer back with an entry. The number is an individual criteria which is not included in the answer. So I decided to write the number in JMSCorrelationID, therefore I've written an UDF in Message Mapping.
    I've checked the JMS Correlation ID in additional properties and also added this into the list of additional properties:
    key.0 -> read xxxx DCJMSCorreleationID
    value.0 -> DCJMSCorrelationID.
    First question: is there something what I should account for in JMS receiver channel?
    At the way back I've implemented another UDF for writing the JMSCorrelationID back to payload in message mapping.
    But I'm not sure that works. The coding looks like:
    try
    DynamicConfiguration conf = (DynamicConfiguration)
    container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey KEY_JMSCorrID = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/JMS","DCJMSCorrelationID");
    String a = conf.get(KEY_JMSCorrID);
    catch(Exception e){}
    return a; //a is an input field for the payload back to SAP backend.
    Second question: is there something what I should accound for JMS sender channel? Do I need to add the DCJMSCorreleationID to the list of additional properties (JMS Correlation is checked)?
    Thanks in Advance,
    Stefan

    Hi,
    thank you for your answer.
    The Proxy to JMS scenario works well and overwrites the JMSCorrelationID given by a number from message payload.
    Could you please take a look at the given udf-coding that belongs to JMS to Proxy Scenario?
    Is it possible to get the JMSCorrelation at this way?
    I also put in JMS-Sender-Channel the JMSCorrelationID into the additional JMS-Message properties and checked "correlation-id from jms message" in adapter specific message attributes.
    In Module-Tab of JMS-Sender-Channel i put the module-configuration in a way like this:
    -> key.0 insert http://sap.com/xi/XI/System/JMS DCJMSCorreleationID
    -> value.0 DCJMSCorreleationID
    Do you think that works?
    I could not verify this configuration until I get an entry in outbound queue so I can't make tests to that.
    In Message Mapping - Test a Null Pointer Exception Occurs, according to the UDF, because I'm reading the DCJMSCorreleationID which is not present at mapping ad hoc test - I think that is ok.
    Thank you in Advance,
    Stefan

  • Proxy to JMS Scenario: switch from sync to async proxy,does it makes sense?

    Hi @all,
    i've implemented a sync proxy to JMS scenario that works well. Backend is ECC 6.0 and Middleware is PI 7.1.
    Business Case: Run a request with a number and get a response back with a corresponding entry for the number. That means, there is always a response expected.
    Now the following thing appears: the receiver system could not handle many calls at one time (200 calls are planned at each run), the calls reduces the performance. Now gys at receiver system likes to develope a buffer of 10 seconds between the requests to handle some kind of load balancing with that. That means for the request that it the response takes +10 seconds back to backend. It is also possible to handle that in SAP backend with a waiting-statement in coding, so there is no need to go from sync to async - but the customer requested us to implement this scenario in async.
    JMS is always async, I know. But the Service Interfaces for Inbound and Outbound are of mode sync - so I can call my outbound Interface class in backend with Importing Output and Exporting Input.
    My question is: makes it sense to go from sync to an async scenario?
    And how looks the coding in backend for the response? I guess that it only makes sense to switch to async when no response entry is needed (example: for write operations).
    Thanks in Advance,
    Stefan

    > But in case of switching, what is the best way?
    > Should I implement 2 senarios? Or is it ok to switch the Inbound and Outbound Service Interface from sync to async?
    I don't think you need 2 scenarios for this. Just one is enough with different RDs.
    Over all in this case you have to re-create/modify the service interfaces and also you have to create 2 interface mappings. You have to also create the new inbound and outbound proxies since service interface mode will be changed. For outbound proxy the code can be reused and for inbound proxy also logic and code can be taken from your old code.

  • Problem: HTTPS connections via authenticated proxy

    Hi all,
    we are facing a problem with the BEA implementation of the HTTPS
    client/server protocol. As you might know it's possible to tunnel T3 via
    HTTP/HTTPS. We are evaluating that at the moment. To make authentication for
    proxy servers possible we followed the documentation and created a class
    implementing the ProxyAuthenticator interface. Everything worked find until
    we tried to use this together with the HTTPS-protocol. Whereas it works as
    long as the proxy doesn't ask for authentication, the ProxyAuthenticator
    class isn't even called in the other case. Has anyone of you already made it
    work?
    Your help is highly appreciated,
    Tchaw!
    Christoph Krüger

    implementing the ProxyAuthenticator interface. Everything Think your are trying to authenticate the jdk 1.2 way,
    maybe just trying it jdk 1.1 like will help.
    What i found in the jsse Docu:
    When accessing HTTPS servers through a web proxy, you must set the "https.proxyHost"
    and "https.proxyPort" system properties to
    the correct host name and port number of the web proxy.
    For example, to set this property on the command line to access HTTPS servers
    through the proxy host "webproxy" running at port 8080 you would use:
    java -Dhttps.proxyHost=webproxy -Dhttps.proxyPort=8080
    And some of my sample code for proxy auth:
    System.getProperties().put( "proxySet", "true" );
    System.getProperties().put( "proxyHost", "proxyurl" );
    System.getProperties().put( "proxyPort", "8080" );
    String authString = "userid:password";
    // enter the username and password for the proxy
    String auth = "Basic " + new sun.misc.BASE64Encoder().encode authString.getBytes());
    URL u = new URL("http://www.bild.de/");
    URLConnection connection = u.openConnection();
    connection.setRequestProperty( "Proxy-Authorization", auth ); // Set up the connection
    so it knows you are sending proxy user information
    connection.setRequestProperty( "Authorization", auth );
    connection.setDoInput( true ); // Set up the connection
    so you can do read and writes
    connection.setDoOutput( true );
    // request.getAuthType() // Rueckgabewert ueberpruefen
    Bye, Klaas

  • SOAP & HTTPS: cannot authenticate at proxy

    Hi,
    I have a problem with secure tunneling of SOAP through a HTTP proxy. The proxy
    requires authentication and SOAP simply does not provide the auth credentials if
    it is also using SSL.
    This is an example of the communication between SOAP client and proxy server.
    The client sends this:
    CONNECT www.remote-domain.de:443 HTTP/1.0
    User-Agent: Java/1.4.2_02The proxy answers with this:
    HTTP/1.1 407 Proxy Authentication Required ( The ISA Server requires authorization
    to fulfill the request. Access to the Web Proxy service is denied.  )
    Via: 1.1 SERVER1
    Proxy-Authenticate: Basic realm="server1.domain.de"
    Connection: close
    Proxy-Connection: close
    Pragma: no-cache
    Cache-Control: no-cache
    Content-Type: text/html
    Content-Length: 724   According to the HTTP RFC, there should be another header in the client
    request, Proxy-Authorization. Therefore the proxy is right to complain. But
    how can I convince SOAP to send this auth?
    This is the code:
        System.setProperty("java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol");
        Provider provider = new com.sun.net.ssl.internal.ssl.Provider();
        Security.addProvider(provider);
        Call lCall = new org.apache.soap.rpc.Call();
        lCall.setTargetObjectURI(aServiceId);
        lCall.setMethodName(aMethodName);
        lCall.setEncodingStyleURI(Constants.NS_URI_SOAP_ENC);
        lCall.setParams(aParams);
        lCall.setSOAPMappingRegistry(fSOAPRegistry);
        SOAPHTTPConnection lConnection = new SOAPHTTPConnection();      
        lConnection.setProxyHost(gProxyHost);
        lConnection.setProxyPort(gProxyPort);
        lConnection.setProxyUserName(gProxyUser);
        lConnection.setProxyPassword(gProxyPassword);
        lCall.setSOAPTransport(lConnection);
        Response lResponse = lCall.invoke(fURL, aServiceId);The invoke() at the bottom raises an exception:
    [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket:
    java.io.IOException: Unable to tunnel through server1:9090. 
    Proxy returns "HTTP/1.1 407 Proxy Authentication Required ( The ISA Server
    requires authorization to fulfill the request. Access to the Web Proxy service
    is denied.  )"; targetException=java.lang.IllegalArgumentException: Error opening
    socket: java.io.IOException: Unable to tunnel through server1:9090.  Proxy returns
    "HTTP/1.1 407 Proxy Authentication Required ( The ISA Server requires authorization
    to fulfill the request. Access to the Web Proxy service is denied.  )"]
         at org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.java:354)
         at org.apache.soap.rpc.Call.invoke(Call.java:248)I have even tried to use a descendant of SOAPHttpConnection to add the
    auth credentials myself, but this did not change a thing:
        class SoapBasicAuthConnection extends SOAPHTTPConnection
          public void send(
            java.net.URL sendTo,
            java.lang.String action,
            java.util.Hashtable headers,
            Envelope env,
            SOAPMappingRegistry smr,
            SOAPContext ctx)
            throws SOAPException
            if (headers == null)
              headers = new java.util.Hashtable();
            sun.misc.BASE64Encoder encoder = new sun.misc.BASE64Encoder();
            String proxyAuth = gProxyUser + ":" + gProxyPassword;
            proxyAuth = "Basic " + encoder.encode(proxyAuth.getBytes());
            headers.put("Proxy-Authorization", proxyAuth);
            super.send(sendTo, action, headers, env, smr, ctx);
        }    I have no more ideas to try out. There are many postings on the net dealing
    with HTTPS & proxies, but the solutions given there do not work if I have to
    stick to SOAPHttpConnection.
    If the SOAP call is made via HTTP, not HTTPS, all is well and the required
    auth header is present in the client request:
    POST http://www.remote-domain.de/soapcontext/servlet/rpcrouter HTTP/1.0
    Host: www.remote-domain.de:80
    Content-Type: text/xml; charset=utf-8
    Content-Length: 661
    SOAPAction: "urn:domain:mandator"
    Proxy-Authorization: Basic QWXXXXXXXXXXX==But then the transmitted SOAP data is not encrypted of course...
    DC

    Ok, here is the solution. The latest stable release of Apache ws-soap, v2.3.1, does not support soap vis proxy with auth. One has to use one of the nightlies. In my case it worked with the latest nightly from 2004-06-22. The classes SSLUtils and HTTPUtils have been improved a lot with this. If only this would have been easier to find...

  • Trouble with a JMS proxy listening to a distributed topic

    Hi all,
    I've setup an ALSB cluster with 1 admin instance and 2 managed instances (m01 and m02).
    I've also configured 1 distributed topic A and defined the two below proxies:
    - proxy P1 is a http proxy that publishes a message into the distributed topic A. The proxy uses a business service with jms protocol and endpoint uri:
    jms://wasdv1r3n1.dev.b-source.net:7301,wasdv1r3n1.dev.b-source.net:7303/my.ConnectionFactory/DistributedTopicA
    - proxy P2 is a JMS proxy listening to
    jms://wasdv1r3n1.dev.b-source.net:7301,wasdv1r3n1.dev.b-source.net:7303/my.ConnectionFactory/DistributedTopicA
    that logs the received message and writes it to file.
    The strange behaviour is that on the managed m01 log file I see the message received from P2 but also on the managed m02 log file I see the message received from P2.
    So I'm sending out 1 message and receiving 1 x managed that is total = 2.
    This strange behaviour is also confirmed from the fact that I see on the file system 2 files and not only 1.
    I thought it was a problem concerning the config of business service that publishes message into the distributed topicA; but I tried with an external 'normal' java JMS subscriber that listens to t3://wasdv1r3n1.dev.b-source.net:7301,wasdv1r3n1.dev.b-source.net:7303 and it works properly: it receives only 1 message.
    I'm trying to understand where is my fault.
    Do you have any idea ?
    Thanks in advance
    Patrizio

    If you publish a message to a topic, all the proxy that subscribed to this topic will receive the message. If you want the message to be processed by only one managed server you can publish to a queue instead.
    Gregory Haardt
    ALSB Prg. Manager
    [email protected]

  • HTTP Basic authentication for proxy service and its wsdl?

    Hello:
    For some reasons I needed to configure the HTTP basic authentication on a proxy service at OSB 11g. Everything was OK until I realized that, additionally to the authentication when calling the service, the OSB also asks for credentials when I try to get that proxy wsdl file.
    My requirements are to secure the proxy service when is called only, not when retrieving the wsdl.
    Is this possible to configure on OSB / WLS? How?
    Greetings!
    Edited by: user4483647 on 02-sep-2010 12:59
    Edited by: user4483647 on 02-sep-2010 13:25

    If I'm not wrong, Basic authentication is Transport level feature. So passing User/Password in SOAPHeader doesn't make sense. SOAP message can only be sent when you have a HTTP Connection open. During opening of HTTP connection User/Password is required for basic authentication.
    http://www.student.nada.kth.se/~d95-cro/j2eetutorial14/doc/Security7.html#wp156943
    Edited by: mneelapu on Apr 2, 2009 2:09 PM

  • HTTP failed - Transparent web proxy

    Hello,
    I developped an application with Flex 3 B1, it works at my
    home but when I tried it in my office I have this type of message
    sometime
    code:
    Channel.Call.Failed
    Message:
    error
    Detail:
    NetConnection.Call.Failed: HTTP: Failed
    Sometime the application works, sometime not... I think this
    is a web proxy problem. I called the person in charge of this and
    for him some program cannot works with a transparent proxy.
    Somebody have the same problem ?
    Best regards,
    Marc

    Thank you Ken for you whitepaper.
    I read the configuration and it is mentioned that the IronPort and clients are not on the same interface (segment). I also read that the IronPort Appliance and clients must be on the same ASA interface to avoid passing trough the ASA itself again.
    Which of these two is right ?
    In my architecture I'm not able to set the IronPort on the same interface as clients (2 differents interfaces and subnet).
    I attached a document explaining the architecture
    My bad I saw that the WSA and clients are on the same ASA interface in the inside networks. Still, in my configuration is it possible to enable WCCP ?
    I also so that it is possible to implement a route-map which perfrom PBR by changing the next-hop ip for specific traffic but this function is not avalaible on ASA as i heard. Can anyone confirm that ?
    Ce message a été modifié par: Maxime GERGES

  • How to resolve HTTP/1.1 407 Proxy Authorization Required issue

    Dear Sir,
    I am getting following error when connecting from SQL developer to oracle cloud. I have tested both on SQL developer 3.2.20.09.87 and sqldeveloper-4.0.2.15.21. but getting the same error as below.
    request your in getting the resolution for the same. thanks in advance
    HTTP/1.1 407 Proxy Authorization Required:
    oracle.dbtools.raptor.cloud.auth.AuthenticationFailedException: HTTP/1.1 407 Proxy Authorization Required
      at oracle.dbtools.raptor.cloud.auth.basic.BasicAuthenticationEngine.doPost(BasicAuthenticationEngine.java:162)
      at oracle.dbtools.raptor.cloud.auth.basic.BasicAuthenticationEngine.authenticate(BasicAuthenticationEngine.java:63)
      at oracle.dbtools.raptor.cloud.auth.basic.GUIBasicAuthenticationEngine.authenticate(GUIBasicAuthenticationEngine.java:26)
      at oracle.dbtools.raptor.cloud.connection.ConnectionCreator.createConnection(ConnectionCreator.java:24)
      at oracle.dbtools.raptor.cloud.connection.CConnections$C.getConnection(CConnections.java:39)
      at oracle.dbtools.raptor.cloud.connection.CConnections.getConnection(CConnections.java:176)
      at oracle.dbtools.raptor.cloud.navigator.CloudConnection.openConnectionImpl(CloudConnection.java:127)
      at oracle.dbtools.raptor.cloud.navigator.CloudConnection.getConnection(CloudConnection.java:89)
      at oracle.dbtools.raptor.cloud.navigator.ConnectionTreeNode$LoadTask.doWork(ConnectionTreeNode.java:74)
      at oracle.dbtools.raptor.cloud.navigator.ConnectionTreeNode$LoadTask.doWork(ConnectionTreeNode.java:38)
      at oracle.dbtools.raptor.backgroundTask.RaptorTask.call(RaptorTask.java:193)
      at java.util.concurrent.FutureTask.run(FutureTask.java:262)
      at oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask.run(RaptorTaskManager.java:554)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
      at java.util.concurrent.FutureTask.run(FutureTask.java:262)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      at java.lang.Thread.run(Thread.java:745)
    Caused by: java.io.IOException: HTTP/1.1 407 Proxy Authorization Required
      at oracle.dbtools.raptor.cloud.auth.basic.BasicAuthenticationHandler.handleError(BasicAuthenticationHandler.java:250)
      at oracle.dbtools.raptor.cloud.auth.basic.BasicAuthenticationHandler.handleError(BasicAuthenticationHandler.java:24)
      at oracle.dbtools.raptor.cloud.connection.CloudHander.handleResponse(CloudHander.java:38)
      at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:945)
      at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:919)
      at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:910)
      at oracle.dbtools.raptor.cloud.connection.DefaultClient.executeRequest(DefaultClient.java:96)
      at oracle.dbtools.raptor.cloud.auth.basic.BasicAuthenticationEngine.doPost(BasicAuthenticationEngine.java:153)
      ... 17 more
    Regards,
    Deenanath
    Message was edited by: 2803956
    Hi Brian,
    I did settings for Database and SFTP only. The advanced setting on "new cloud connection" screen fills automatically. when I tried to remove the advanced setting such as host name, port, server path and service name. then it is asking for hostname.
    After doing all the steps i am facing the same issue of " HTTP/1.1 407 Proxy Authorization Required".
    Could you please help me to resolve the issue?
    Thanks for your help and support.

    Did you set up your HTTP Proxies inside of the settings in SQL Developer? Does the particular database you are attempting to access, does the proxy server need authentication? Again, check the http proxy options in sql developer.
    https://docs.oracle.com/cd/E11882_01/doc.112/e12152/intro.htm#CIHFCGCD

  • HTTP/1.1 502 Proxy Error ( Connection refused )\nVia: 1.1 TMG01 -SP\nConnection

    Hi,
    I have an application that
    executes calls to a jetty
    server locally. When I try to
    run the application I get the error below.
    HTTP/1.1 502 Proxy Error ( Connection refused )\nVia: 1.1 TMG01-SP\nConnection: Keep-Alive\nProxy-Connection: Keep-Alive\nPragma: no-cache\nCache-Control: no-cache\nContent-Type: text/html\nContent-Length: 3904  \n
    But, this error only occurson a particular machine, when I run
    the the same application on other machines have no problems.
    Someone
    knows what could be? I disabled
    the firewall, proxy, includes
    rules on the firewall but nothing does this
    application working.

    Hi Namrata,
    thank to answer my question,  I haven't access to TMG Server.  But, I get a error page from ForeFront with the message:
    Technical Information (for support personnel)
    Error Code 10061: Connection refused
    Background:The server you are attempting to access has refused the connection with the gateway. This usually results from trying to connect to a service that is inactive on the server.
    Date: 9/25/2014 5:42:52 PM [GMT]
    Server: TMG02-SP.proxy
    Source: Remote server

Maybe you are looking for