Need to Send SOAP information on OSB message.

Hi Everyone,
iam trying to invoke BPEL process by using OSB business servicee.
The BPEL process WebService expected SOAP Header with wsse:Username and Wsse:Password along with message sent from OSB.
I did try using the service account with basic authentication it gives following error
Error authenticating the transport username/password: [Security:090304]Authentication Failed: User testuser javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User testuser denied
When service account was created in OSB the username:testuser and password:welcome1.
Since iam new to OSB i unable to figure out what might have gone wrong.
Will the above mentioned method embed the SOAP Header message to invoke my BPEL Web Service
Can some one throws some thought or suggestions for me to proceed further on this issue.I would appreicate if some could help me out on this.
This is very critical to my Project deadline.
Please Please Help
Thanks in Advance
Regards
Sabir

Hi Manoj
I tried your suggestion by adding Transport Header on the Message Request on the Proxy Message Flow.
Then i added the XML Content on the expression as string and then it says Setting Outbound request headers is only possible when the context variable "outbound" is valid. This error come ups on the Workspace
Can you please let me know if iam doing something wrong here
This is the Message Header which needs to be sent to the Web Service
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<soap:Header><wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" soap:mustUnderstand="1"><wsse:UsernameToken xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><wsse:Username>testuser</wsse:Username><wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">welcome1</wsse:Password></wsse:UsernameToken></wsse:Security></soap:Header>
Edited by: sab2 on Oct 12, 2009 12:15 PM

Similar Messages

  • Need  help sending e-mail a mobile messages

    hi!
    i'm a n00b in Java. Can you please tell how can i send e-mail and mobile messages in java?
    thnx!!

    First of all, before you do any programming, if you want to have your computer send e-mail messages then you must have access to an SMTP server.
    Next, if you do have access to one, then JavaMail is a common way to write programs that send e-mail.
    As for mobile messages ("text messages" to a cellphone?) you usually need a contract with some phone company to do that, so they can bill you for it.
    When you find out about that, they should provide you with documentation on how to proceed. If it involves sending e-mail to a particular address, see part 1 of this reply.

  • SOAP APIs needed to extract SOAP request arguments for message handler implementation

    1. I am facing problem in using the Message Handler approach for the implementation
    of webservices using SOAP on BEA weblogic 8.1. A SOAP request(XML format) can
    be interrupted using the message handler and hence can be modified before it invokes
    the webservice method. I have been able to successfully extract the SOAP Name
    space xml format as a part of the SOAP request using the APIs given below
    APIs:
    SOAPBody body = env.getBody();
    Name Spaces format:
    <m:sayHello xmlns:m="http://www.bea.com/servers/wls70/samples/examples/webservices/basic/statelessSession">
    <intVal xsi:type="xsd:int">100</intVal>
    <string xsi:type="xsd:string">vikas</string>
    </m:sayHello>
    The above is a Hello world example which invokes the sayHello method with arguments
    as an integer and a string. I have not been able to find the SOAP APIs to extract
    these arguments from the SOAP Body.
    2. But there are XML apis which can extract the tag data from the SOAPBody e.g
    NodeList nl = body.getChildNodes();
    for(int i = 0; i < nl.getLength(); i++)
    Node node = (Node)nl.item(i);
    if(node instanceof SOAPElement){
    SOAPElement se = (SOAPElement)node;
    String operationName = se.getLocalName();
    String value = se.getValue();
    The SOAPBody interface implements the following interfaces (Ref : http://java.sun.com/j2ee/1.4/docs/api/index.html
    javax.xml.soap > SOAPBody )javax.xml.soap.Node, javax.xml.soap.SOAPElement(SOAP APIs)
    org.w3c.dom.Node, org.w3c.dom.Element (XML Parser APis)
    3. But webservice implementation of Weblogic Application server 8.1(webservice.jar)
    doesn't support the XML parser APIs and only supports the SOAP APIs.
    i.e. The SOAPBody Interface of Weblogic Application Server only implements the
    javax.xml.soap.Node, javax.xml.soap.SOAPElement (SOAP APIs) and not the XML APIs
    (org.w3c.dom.Node, org.w3c.dom.Element)
    So the code snippet written as a part of point 2 will not be compiled(give compilation
    error) using the webservice.jar of Weblogic 8.1.
    4. I have tried to compile the same code using the saaj-1_2-fr-api.jar (SOAP 1.2
    apis jar) which I have downloaded from java.sun site. And the code got successfully
    compiled.
    In this latest version of SOAP APIs jar the SOAPBody interface implements both
    the SOAP as well as XML parser Apis.
    5. I was not able to run this code on the Weblogic server , bcoz at the runtime
    weblogic 8.1 is using its webservice.jar instead of saaj-1_2-fr-api.jar. And
    this code was giving me runtime error as
    java.lang.NoSuchMethodError: javax.xml.soap.SOAPBody.getChildNodes()Lorg/w3c/dom/NodeList;
    (see Fault Detail for stacktrace)</faultstring>
    So now I need to find out the version of the webservice.jar of Weblogic 8.1 which
    supports SOAP Apis as well as XML parser apis.
    Otherwise I have to find out the SOAP apis which can extract the tag data from
    the SOAP body.
    Please Help.

    You can use the SAAJ APIs to get the child nodes.
    Example here:
    http://manojc.com/tutorial/sample4/ServerHandler.java
    so instead of using body.getChildNodes(), you have to use
    body.getChildElements() which returns an iterator of SOAPElements.
    Regards,
    -manoj
    http://manojc.com
    "Vikas Garg" <[email protected]> wrote in message
    news:40dfb5e0$1@mktnews1...
    >
    1. I am facing problem in using the Message Handler approach for theimplementation
    of webservices using SOAP on BEA weblogic 8.1. A SOAP request(XML format)can
    be interrupted using the message handler and hence can be modified beforeit invokes
    the webservice method. I have been able to successfully extract the SOAPName
    space xml format as a part of the SOAP request using the APIs given below
    APIs:
    SOAPBody body = env.getBody();
    Name Spaces format:
    <m:sayHelloxmlns:m="http://www.bea.com/servers/wls70/samples/examples/webservices/basic
    /statelessSession">
    <intVal xsi:type="xsd:int">100</intVal>
    <string xsi:type="xsd:string">vikas</string>
    </m:sayHello>
    The above is a Hello world example which invokes the sayHello method witharguments
    as an integer and a string. I have not been able to find the SOAP APIs toextract
    these arguments from the SOAP Body.
    2. But there are XML apis which can extract the tag data from the SOAPBodye.g
    >
    NodeList nl = body.getChildNodes();
    for(int i = 0; i < nl.getLength(); i++)
    Node node = (Node)nl.item(i);
    if(node instanceof SOAPElement){
    SOAPElement se = (SOAPElement)node;
    String operationName = se.getLocalName();
    String value = se.getValue();
    The SOAPBody interface implements the following interfaces (Ref :http://java.sun.com/j2ee/1.4/docs/api/index.html
    javax.xml.soap > SOAPBody )javax.xml.soap.Node, javax.xml.soap.SOAPElement(SOAP APIs)
    org.w3c.dom.Node, org.w3c.dom.Element (XML Parser APis)
    3. But webservice implementation of Weblogic Application server8.1(webservice.jar)
    doesn't support the XML parser APIs and only supports the SOAP APIs.
    i.e. The SOAPBody Interface of Weblogic Application Server only implementsthe
    javax.xml.soap.Node, javax.xml.soap.SOAPElement (SOAP APIs) and not theXML APIs
    (org.w3c.dom.Node, org.w3c.dom.Element)
    So the code snippet written as a part of point 2 will not be compiled(givecompilation
    error) using the webservice.jar of Weblogic 8.1.
    4. I have tried to compile the same code using the saaj-1_2-fr-api.jar(SOAP 1.2
    apis jar) which I have downloaded from java.sun site. And the code gotsuccessfully
    compiled.
    In this latest version of SOAP APIs jar the SOAPBody interface implementsboth
    the SOAP as well as XML parser Apis.
    5. I was not able to run this code on the Weblogic server , bcoz at theruntime
    weblogic 8.1 is using its webservice.jar instead of saaj-1_2-fr-api.jar.And
    this code was giving me runtime error as
    java.lang.NoSuchMethodError:javax.xml.soap.SOAPBody.getChildNodes()Lorg/w3c/dom/NodeList;
    (see Fault Detail for stacktrace)</faultstring>
    So now I need to find out the version of the webservice.jar of Weblogic8.1 which
    supports SOAP Apis as well as XML parser apis.
    Otherwise I have to find out the SOAP apis which can extract the tag datafrom
    the SOAP body.
    Please Help.

  • SOAP handler for outgoing message

    Hello,
    I am implementing a order related webservice running under WebLogic 8.1. It sometime needs to send SOAP request to other external (outside my org) webservices. Is there a way to add a handler to intercept all outgoing SOAP message from my order webservice?
    Thanks,
    PC

    > I also want to use a module for the message received from the adapter. Do I have to call the module after the
    > sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    > entry?
    yes.

  • Sender SOAP Adapter, inconsistent behavior

    Hi,
    We are using XI 3.0 SP17. We have noticed some inconsitent behavior with the sender SOAP adapter:
    When sending a valid SOAP message to the adapter, it will reply with:
    <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header/><SOAP:Body/></SOAP:Envelope>
    To me this seems errornous, becuase it is missing "<?xml version='1.0'?>" in the beginning, and thus is not valid XML. This leads to errors on the Client that is sending messages to the Sender SOAP adapter.
    When sending an errornous SOAP message from the client to the XI Sender SOAP adapter, the error message does include the "<?xml version='1.0'?>" + the corresponding error message, so the behavior seems inconsitent and errournous.
    Can someone tell me how the get the Sender SOAP Adapter to include "<?xml version='1.0'?>" in the reply for valid SOAP messages?
    Thanks for any help on this subject!
    -Hans
    PS: Here is an example of an error message from the Sender SOAP adapter, that does include the xml header:
    <?xml version="1.0"?>
    <!-- see the documentation -->
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
         <SOAP:Body>
              <SOAP:Fault>
                   <faultcode>SOAP:Server</faultcode>
                   <faultstring>Server Error</faultstring>
                   <detail>
                        <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                             <context>XIAdapter</context>
                             <code>MalformedMessageException</code>
                             <text><![CDATA[Unexpected content in SOAP:Body; nested exception caused by: com.sap.aii.messaging.util.XMLScanException: Unexpected content in SOAP:Body\tat com.sap.aii.messaging.mo.Message.reparseRootDocument(Message.java:1014)\tat com.sap.aii.messaging.net.MIMEInputSource.readSOAPPart(MIMEInputSource.java:619)\tat com.sap.aii.messaging.net.MIMEInputSource.decodePart(MIMEInputSource.java:611)\tat com.sap.aii.messaging.net.MIMEInputSource.readBody(MIMEInputSource.java:379)\tat com.sap.aii.messaging.net.MIMEServletInputSource.parse(MIMEServletInputSource.java:58)\tat com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:378)\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:760)\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:853)\tat com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)\tat com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)\tat com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)\tat com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)\tat com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)\tat com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)\tat com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)\tat com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)\tat com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)\tat com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)\tat com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)\tat java.security.AccessController.doPrivileged(AccessController.java:180)\tat com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)\tat com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)          ]]></text>
                        </s:SystemError>
                   </detail>
              </SOAP:Fault>
         </SOAP:Body>
    </SOAP:Envelope>

    Hi,
    "Do not use SOAP Envelope" is not really an option for us.
    From help.sap.com:
    If the indicator is set, the adapter expects a message without a SOAP envelope.
    If you have set the indicator, you must also enter nosoap=true in the URL.
    The adapter then puts the whole message in the XI payloads
    So this also requires heavy changes to the client side. It would almost make more sense to use the plain HTTP adapter in that case..
    -Hans

  • How to re-use one SOAP Sender Channel for two different messages?

    Hi!
    I have an XI Proxy to SOAP Sync Scenario. 5 messages uses only 2 channels - cc_XI_Sender and cc_SOAP_Receiver. All messages comes from one Sender Channel and goes to one Receiver channel, and it works fine.
    When I make the same for SOAP to XI Proxy Sync Scenario, I've got a problem. For example I have 2 different messages (mi_so_MSG_ONE and mi_so_MSG_TWO), so it works, if I had a two different sender channels (cc_SOAP_R1 and cc_SOAP_R2).
    If I set the same Sender Channel in both Sender Agreements (cc_SOAP_R1), only one message (mi_so_MSG_ONE) goes without errors. When I send a second message (mi_so_MSG_TWO), in SXMB_MONI this message comes from Business System (BS_TEST) as message type one (mi_so_MSG_ONE), and then in stage of transformation in Interface Determination goes to message mapping program for other kind of messages (MM_MSG_ONE_to_XI_PROXY). And then - error in message mapping.
    I try many URLs for both messages:
    1) http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_TEST:cc_SOAP_R1&version=3.0&Sender.Service=&Interface=
    2) http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_TEST:cc_SOAP_R1&version=3.0&Sender.Service=BS_TEST&Interface=*
    3) http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_TEST:cc_SOAP_R1&version=3.0&Sender.Service=BS_TEST&Interface=...MyNameSpace...mi_so_MSG_TWO
    Message in payload:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!--  Inbound Message   -->
    <MSG_TWO xmlns="urn:xxx:yyy:MyNameSpace" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">... some fields... </MSG_TWO>
    But in SOAP Header I see that is NOT second message!
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    < !--  Inbound Message   -->
    <SAP:Main>
      <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
      <SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
      <SAP:MessageId>93233F70-3E2F-11DF-8CD3-00237D301CD6</SAP:MessageId>
      <SAP:TimeSent>2010-04-02T08:13:09Z</SAP:TimeSent>
      <SAP:Sender>
        <SAP:Service>BS_TEST</SAP:Service>
        <SAP:Interface namespace="urn:xxx:yyy:MyNameSpace">mi_so_MSG_ONE</SAP:Interface>
      </SAP:Sender>
      <SAP:Interface namespace="urn:xxx:yyy:MyNameSpace">mi_so_MSG_ONE</SAP:Interface>
      </SAP:Main>
    Is it correct that many kinds of messages cannot goes through one Sender Channel ? If not... How can I reuse one SOAP Sender Channel for both this messages?
    Thanks for helping.

    Thanks for answers!
    It means a webservice application will be deployed and exposed in PI using the associated Message Interface and its namespace information in the SOAP Sender channel.
    It means only one Sender Channel per one pair of names (name of Message Interface and name of namespace). And it will fail if I change something. And question is: why URL for sending SOAP message contains parameter "Interface"?
    "backward compatibility" or "for future use only"?
    Nothing happens when I change this parameter, seems that name of Interface comes from first of founded Sender Agreements.
    If the structures are the same
    No. Structures are different.
    Making one structure per all SOAP incoming messages looks workable, but... looks strange (in fact I have a lot of SOAP messages, more than 100 Sender channels).
    I found an information, that I can use one Sender channel per many messages with different structures only if I make this messages like different Operations in one Service Interface (in PI 7.1).
    But in this case in list of messages in SXMB_MONI I will see only a one name of Service Interface for all my messages and it's not so comfortably for supporting: to take a name of operation that fails I need to goes inside.
    In older version of XI (prior 7.1) using one sender channel per many messages allowed without any hints.

  • How to send authentication information to SOAP Web Service using MATE framework

    Hi,
    Can anyone please tell me how to pass authentication info (such as user name & password) while calling a webservice using MATE's webserviceinvoker? the SOAP web service expects authentication info in the header.
    Thanks in advance..

    HI Swayam,
    First of all you should tell us what blogs you have seen to avoid you to repeat information that you already know.
    we want to avoid  setting up SLD configuration for sender system because  sender system is just consuming web service .
    This is not necessary,
    Please let me know  the ways we can configure . I did understand we can publish and register the WSDL from Service interface ,but was not clear on over all  scenario .
    Do you have your ECC webservice available via SOAManager?, you only to access it via soap receiver in SAP PI.
    To publish, you need to publish only the sender SOAP, when you register there the sender soap your partner could access there to get the WSDL (Publish services from PI 7.1 to the Service Registry). Also you can generate directly the wsdl (Display WSDL - Integration Directory - SAP Library), what do you want?
    Regards,

  • How to send SOAP Message with Oracle B2B

    Hi everyone,
    I need your help to send out from Oracle B2B a SOAP message with attachment of any type of file (image, pdf, etc.). Possibly using a SOA composite application or another way, it doesn't matter. I already create an ebMS partnership with a custom document protocol and I already create a working SOA composite application to send only text message to my trading partner. I have tried this solution: http://anuj-dwivedi.blogspot.it/2011/04/ebms-attachment-handling-in-oracle-b2b.html but it doesn't work for my case... It is to be noticed that I don't give any schema to my component in the SOA application explained firstly, and I select opaque as schema.
    Thanks to all, regards
    Nello

    Hi Anuj and thanks for your help,
    I need to send an ebXML message, with SOAP, and I try to send it with a .war application written in jsp connecting to http://10.85.28.24:8001/b2b/transportServlet to send the SOAP message. The errors reported is:
    javax.xml.soap.SOAPException: Unable to receive message. Received a response from url: http://10.85.28.24:8001/b2b/transportServlet with HTTP status 200 and SOAP content-type: null.
    the code I write is the following (to evaluate the two "null" in the super constructor)
    <%!
    public class EBMSSender extends SOAPRunner
    private String cpaId;
    private String service;
    private String action;
    private String mess;
    private ArrayList<String> allegati=null;
    public EBMSSender(String cpaId, String service, String action, String mess, ArrayList<String> file)
    super("http://10.85.28.24:8001/b2b/transportServlet","null", "null");
    this.cpaId = cpaId;
    this.service = service;
    this.action = action;
    this.mess=mess;
    this.allegati=file;
    @Override
    protected void prepareRequest(SOAPMessage soapMessage, SOAPBody soapBody) throws SOAPException
    soapBody.addChildElement(SOAPUtility.createElement("CPAId", getNsPrefix(), getNsURI(),"agr3"));
    soapBody.addChildElement(SOAPUtility.createElement("service", getNsPrefix(), getNsURI(),"OracleService"));
    soapBody.addChildElement(SOAPUtility.createElement("action", getNsPrefix(), getNsURI(),"Oracletohermesb"));
    soapBody.addChildElement(SOAPUtility.createElement("serviceType", getNsPrefix(), getNsURI(),"OracleServiceType"));
    soapBody.addChildElement(SOAPUtility.createElement("convId", getNsPrefix(), getNsURI(), "convId"));
    soapBody.addChildElement(SOAPUtility.createElement("fromPartyId", getNsPrefix(), getNsURI(), "Oracle"));
    soapBody.addChildElement(SOAPUtility.createElement("fromPartyType", getNsPrefix(), getNsURI(), "Name"));
    soapBody.addChildElement(SOAPUtility.createElement("toPartyId", getNsPrefix(), getNsURI(), "Hermes-b"));
    soapBody.addChildElement(SOAPUtility.createElement("toPartyType", getNsPrefix(), getNsURI(), "Name"));
    attach(soapMessage);
    protected void attach(SOAPMessage soapMessage)
    String h=mess;
    DataHandler dh;
    AttachmentPart ap = soapMessage.createAttachmentPart(h,"text/plain");
    soapMessage.addAttachmentPart(ap);
    if(allegati!=null)
    for(int i=0; i<allegati.size();i++)
    dh=new DataHandler(new FileDataSource(new File(allegati.get(i))));
    ap=soapMessage.createAttachmentPart(dh);
    ap.setContentType(new MimetypesFileTypeMap().getContentType(allegati.get(i)));
    ap.setContentLocation(allegati.get(i));
    soapMessage.addAttachmentPart(ap);
    @Override
    protected void processFault(SOAPFault soapFault) throws SOAPException{}
    @Override
    protected Object processResponse(SOAPMessage responseMessage,SOAPBody responseBody) throws SOAPException
    SOAPElement messageId = SOAPUtility.getChild(responseBody, "message_id", getNsURI());
    return null;
    %>
    The code works fine on the other trading partner side to send ebXML message to Oracle B2B. Apart from this solution (however,it would be my favorite), I find your blog and I try to implement your solution. It works: it sends files with only text payload to the other trading partner without any problem, but if I try to send for example an image in byte array written in a file .txt, the ebxml file received has the byte array with wrong characters. it may be that I have not provided the xsd schema? in case if I wanted to send an ebXML message with text and attachments, what xsd schema do I need to provide?
    or is there another way to implement a SOA composite application to send SOAP messages with attachments?
    Thank for your help!, regards
    Nello

  • Need to send success or failure message to BAPI of SQL query action block

    Hi All,
    I need to send success or failure message(i.e. 1 or 0) to BAPI which has been called below sql query action block in transaction
    Here in SAP, i have created on BAPI with one import parameter and one export parameter.
    In the sql query action block, it insert records in the database table. If it fail or success, that message(numeric value 1 or 0) has to send to SAP program through BAPI.
    I have created a SAP ABAP program which sends message to MII Message listener through RFC then in the process rule message it will call transaction, in transaction, sql query will insert records into database table.  if it success or fail, it will pass to BAPI. And i calling that BAPI in the same SAP ABAP Program to show in the output screen.
    Here the issues, i am not getting the value from BAPI which has send by the transaction in MII.
    SAP Jco, I have mapped in conf. links --> BAPI input with sql query sucess
    Thanks,
    Kind Regards,
    Praveen Reddy M

    Dear All,
    I am facing problem regarding completion notifications in Oraclr r12, when user click the upon completion generated notifications it can only be viewd once, second time user cannot view the notifications.
    I have find that fnd_file_temp table store this information and deleted it.
    Plz help me how to view this URL again.
    thanks
    regards,
    Zubyr

  • Need Help for  SOAP sender with HTTPS protocol

    Hi Team
    We have a scenario where the sender is a 3P system and they will be sending the message using web service.They will send the data using SSL ( HTTPS) using certificates.
    In the sender soap adapter , I have two options
    1. HTTPS with client Authorization
    2. HTTPS without client Authorization
    I think I need to use the first option. But I have doubt regarding certificates
    1. Who is going to provide the certificate? is it PI Team or the third party team.
    2. Once we have the certificate where we need to store it in NWA? is it in the TrustedCA keystore view or service_ssl keystore view.

    Hi Indrajit,
    Krupa already shared a valuable resource on how to set up on Double Stack PI, so I'll focus on what's left to deal with / open questions.
    Indrajit Sarkar wrote:
    In the sender soap adapter , I have two options
    1. HTTPS with client Authorization
    2. HTTPS without client Authorization
    I think I need to use the first option. But I have doubt regarding certificates
    1. HTTPS with client authorization means that the 3rd party would not give username / password to authenticate to your PI but present a certificate you are trusting. You can think of this as an admission ticket to communicate with your PI server
    2. HTTPS without client authorization means they will authenticate with username password.
    In both cases the caller (3rd party) would need to trust your PI server. Most commonly this trust is established by not trusting your PI server's explicit certificate but in trusting the CA that issued your PI server's certificate. This CA can very well be a company internal CA. That way, if you happen to need changing the hostname of the server some time in the future, trust situation is still valid.
    In case of 1. (HTTPS with client authorization) your PI server in turn would also need to trust the 3rd party caller. This is often done in such ways that the interal CA on your side issues a client certificate with the CN of the caller. The caller presents this certificate to your server upon making a call (see here for a picture https://help.sap.com/saphelp_nw74/helpdata/en/43/dc1fa58048070ee10000000a422035/content.htm). You will also need to back up this process on your PI server by mapping the certificate to a specific user.
    --> Option 2 is the more polished one with ability to withdraw a certificate and the like. However it does result in some overhead setting it up so I personally would go with Option 1 if there's no business need / security policy enforcing so.
    HTH
    Cheers Jens

  • Weblogic 8.1 SP 6 throws Read channel closed when sending SOAP message

    Hi,
    I am using Weblogic8.1 SP6 & Axis1 to send SOAP message through RPC call using SSL. This is working intermittently.
    I use WLSSLAdapter to set up the SSL, and some properties I set:
    System.setProperty("javax.xml.soap.MessageFactory", "weblogic.webservice.core.soap.MessageFactoryImpl");
    System.setProperty("javax.xml.rpc.ServiceFactory", "weblogic.webservice.core.rpc.ServiceFactoryImpl");
    System.setProperty("weblogic.webservice.verbose", "true");
    In case of error, the server throws this:
    java.io.IOException: Read channel closed
    at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Sourc
    e)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown S
    ource)
    at com.certicom.tls.record.ReadHandler.read(Unknown Source)
    at com.certicom.tls.record.ReadHandler.read(Unknown Source)
    at com.certicom.tls.record.ReadHandler.read(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.closeWriteHandler(Unknown S
    ource)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.close(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Sourc
    e)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown S
    ource)
    at com.certicom.tls.record.WriteHandler.write(Unknown Source)
    at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
    at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66)
    at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
    AT java.io.FilterOutputStream.write(FilterOutputStream.java:80)
    at weblogic.webservice.binding.soap.HttpClientBinding.writeToStream(HttpClientB
    inding.java:430)
    at weblogic.webservice.binding.soap.HttpClientBinding.send(HttpClientBinding.ja
    va:219)
    at weblogic.webservice.core.handler.ClientHandler.handleRequest(ClientHandler.j
    ava:37)
    at weblogic.webservice.core.HandlerChainImpl.handleRequest(HandlerChainImpl.jav
    a:143)
    at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:231)
    at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:471)
    at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:566)
    at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:419)
    Before sending message, application will first retrieve WSDL from the target. This is always success.
    I need to know how to fix this problem.
    Any help is appreciated. Thanks.
    Alvin

    Hi,
    Even I am facing the same issue could any body help me out to solve this issue.

  • TS2755 Hi all, I bought one iphone and 3 ipads, i set up all on one apple ID. Now i have a problem when using messages: when sending message from one device it appears again on screen from the other 3 devices. I need help of how to set up messages on each

    Hi all, I bought one iphone and 3 ipads, i set up all on one apple ID. Now i have a problem when using messages: when sending message from one device it appears again on screen from the other 3 devices. I need help on how to set up messages on each device separately and to start using messages app on each device independently. Thanks

    search google for "iphone remove picture from contact"

  • Need to send a 403 (forbidden) message from proxy to client

    I have create a List that contains URL's that I want to block from the user. Once I search that list and see that the requested URL is in the list, I need to send a 403(forbidden) message. Does anyone know if I can just send a "HTTP/1.0 403 Forbidden" Header back to the client in bytes from my DataOutputStream object??
    Anyone have any other suggestions I would appreciate it.

    You can get all you need from the HTTP 1.1 specification. i.e. http://www.w3.org/Protocols/rfc2616/rfc2616.txt

  • Failed in Message Mapping for Sender SOAP Adapter

    I am using a synchronous Sender SOAP adapter for sending SOAP messages using HTTP security protocol. I am trying to send SOAP messages to XI and then to RFC-R/3. And Responses back from RFC to XI and then to SOAP. I am getting an error for failed in message mapping in SXMB_MONI for converting SOAP messages to RFC. When I debug it in Message Mapping in Integration Repository, it works fine.
    Any help is appreciated.
    Thanks in advance!
    Mrudula

    Hi,
    try to do a full cache refresh
    regards,
    Jakub

  • SOAP message size limitation for sender soap adapter

    Hi All,
    We are facing critical production issue in case of sender SOAP Adapter,
    If the sender soap message is having 114359 Bytes than the Third party is getting exception and SOAP request is not reaching XI.
    If the message size is less then 100kbytes then no exception will come.
    Is this a limitation that SOAP message size should not exceed 100kbyte?
    Thnaks in advance
    Best Regards,
    Harleen Kaur Chadha

    Hi ,
    Thanks for your inputs,Could you please tell me which hardware configurations are you talking about?
    Are you people talking about harware configurations for XI?
    Best Regards,
    Harleen Kaur Chadha

Maybe you are looking for