Can we edit SOAP Header for an Outbound ABAP Proxy message?

Hi,
Can we add some information such as dynamic configuration to the SOAP header for the outbound ABAP Proxy from ABAP report in SAP Application System?
Regards,
Praveen Gujjeti.

Hi Praveen, have you found soulution for this? Can you share it with me?
From here http://help.sap.com/saphelp_nw70/helpdata/EN/d6/49543b1e49bc1fe10000000a114084/content.htm
The help described that:
Set logging in the message header. This means that this message is logged even if logging is deactivated explicitly in the configuration. The logging information is part of the message header:
¡ <SAP:Logging>1</SAP:Logging>
Activates logging explicitly.
¡ <SAP:Logging>0</SAP:Logging>
Deactivates logging explicitly.
So it means that we can edit SOAP header for outbound ABAP proxy. But i haven't find the correct method to do that.

Similar Messages

How to add Custom Attributes in the SOAP header for OWSM

Hi,
I like to know how to add the Custom Attributes in the SOAP header for OSWM username token authentication.
Currently we are getting the header element like
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
here we need to add the attribute "soap:mustUnderstand="1" , so the element will look like
<wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
Any info on this will be helpful.
Thanks,
ArunM

Hi Jay, you can make it in more than 1 way.
I suggest you the following:
- create an URL iview that points to any URL you want.
- define a Resource that points to the iview (with a window name, to open in new window)
- define an Area that points to the resource
- add your new Area to the your current Area Group
Regards!

How can I edit a droplet for Photoshop 6?

How can I edit a droplet for Photoshop 6? The company hired somebody to set up the droplet years ago, and nobody remembers how it was set up. The computer that was used to save the files has crashed, and I need to change the path the droplet uses for saving the files. I tried to open the droplet with Image Ready, but it said it was not an image ready droplet and could not be opened. The computer running Photoshop is using Windows XP.

It seems that the script on the ps scripts page is to old to work in cs5.
This is a lnk to xtools 1.8 which has the latest version of the droplet decompiler:
http://sourceforge.net/projects/ps-scripts/files/xtools/
Just unzip, find the Apps folder and look for the DropletDecompiler.jsx.
Then put your droplet on the desktop, Use File>Scripts>Browse in cs5 to navigate to the DropletDecompiler.jsx.
Here's an example using the Aged Photo.exe droplet from the ps 6 samples folder:
here's the resulting action opened in cs5:

User-exit/BADI during outbound ABAP proxy call

Hello,
I want to introduce certain check during outbound ABAP proxy calls to PI. This is a generic check, failure of which would stop the proxy call to proceed and raise an exception.
I would like to place this at the generic place which is called for all the outbound ABAP proxy calls, rather than coding this in each and every outbound proxy class as the check is generic.
Is there some user-exit/BADI where i can introduce this? Maybe within class CL_PROXY_OUTBOUND or somewhere else where i can introduce this check.
Any help in this regard would be appreciated.
Best Regards,
Gajendra.

Dear Gajendra ,
i agree with sabrish, you must be having a z report on the application system that must be calling that outbound proxy...may be if the check is generic it may not be related to a proxy so you can code a FM and then call it before you call that proxy in the z report
Giving points is another way to say thanks

Exception handling in outbound ABAP proxy

Hi All,
i need to catch exception in outbound abap proxy in two cases:
1. if RFC dest in R3 which is pinging to XI goes down.
2. IF xi server is down.
in both the cases i need to catch the exceptions.
now i written the code in this way:
DATA: v_exceptions TYPE REF TO cx_ai_system_fault.
TRY.
CALL METHOD zirco_o_msg_if_as_req_details=>execute_asynchronous
EXPORTING
output = s_reference.
COMMIT WORK.
CATCH cx_ai_system_fault INTO v_exceptions.
WRITE: 'Exception CX_AI_SYSTEM_FAULT caught'.
WRITE: / v_exceptions->errortext.
WRITE: / v_exceptions->code.
but this code is not working.
can anybody tell me how can i acheive this?

Hi All,
I need to log the error when receiver syatem is down.
Its like this:
Outbound proxy >>>XI>>>File adapter..
Now if xi goes down....means message is succussefully sent from ISD and get stuck in XI then i need to catch this exception in ISD.
Is it possible?? if yes then how??
Kunaal

CX_BGRFC_INVALID_DESTINATION during outbound abap proxy call on 7.1

Hi guys,
I'm trying to set up a scenario with outbound abap proxy call using the new WS adapter and when I execute the report with the proxy call I'm getting the CX_BGRFC_INVALID_DESTINATION exception.
I've generated proxy w/o problems, I've set up everything in SOAMANAGER.
Have you experienced this issue?
Thanks for your help,
Olian

Hi guys,
so my connection to SLD works fine now and I'm still getting the error. Any other ideas?
Just in case: this is my proxy code. Is this correct for using with 7.1 and WS adapter?
REPORT Z_PI_PROXYTEST.
data sender_object type ref to ZCO_PROXYTEST_OUT.
data out type ZMT_PROXYTEST_OUT.
data lo_sys_exception TYPE REF TO cx_ai_system_fault.
data err_result type string.
out-ZMT_PROXYTEST_OUT-data = 'sample'.
try.
    create object sender_object
      EXPORTING
        logical_port_name = 'PROXYTEST'.
    call method sender_object->PROXYTEST_OUT
      EXPORTING
        output = out.
    commit work.
catch cx_ai_system_fault into lo_sys_exception.
    call method lo_sys_exception->IF_MESSAGE~GET_TEXT
      RECEIVING
        result = err_result.
    write err_result.
endtry.
write 'Data has been sent to PI'.
Thanks for your help, Olian

How to add security credentials to SOAP header for EBS Web Service call..

All,
I am trying to invoke a webservice that I successfully exposed as a WSDL Web Service using EBS Integrated SOA Gateway. I am using OBIEE 11g Action Framework which uses WebLogic.
Here are the steps I completed:
- I exposed a WSDL web service in EBS R12 via Integrated SOA Gateway
- I granted the access to this service in EBS R12 to user SYSADMIN
- I used OBIEE 11g to make a Action to call the Web service (using Action Framework) by searching for the WSDL
- When I try to execute the action: I get the error:
Action could not be invoked.
ServiceExecutionFailure :
Error invoking web service HR_PHONE_API_Service at endpoint http://ip-10-87-33-3.ec2.internal:8000/webservices/SOAProvider/plsql/hr_phone_api/ Missing <wsse:Security> in SOAP Header
PROBLEM: I am unsure how to add the credentials for SYSADMIN user and password to add the SOAP username/pwd to the outgoing call. Anyone on this forum know how to set up the SOAP to call with the correct credentials? I have been looking at the documentation but it is not clearly explained.

Dear Heiko,
did you solve this problem?
We are facing the same problem. Every parameter that requries "cmd" does not work. I guess we don´t use this paramter the right way.
Best, Chris

How do pass the UserID and Password in the SOAP header for web services

I am encountering issues trying to pass the userid and password in the SOAP header when consuming a 3rd party web service. Rostewitz posted something similiar but I don't know how to type iv_xml. Any help would be greatly appreciated.
Thank you,
jpina

It helps to post a link to a thread when you refer to it. If you are trying to implement that solution though, you can look at the parameter of the corresponding method being called. The parameter has type 'SIMPLE' which means that it is compatible with all of the predefined elementary ABAP types. In this case, you should use 'STRING'.

Adding WS Security in SOAP header for calling soap services from PI

When i am calling a wss enabled webservice from soapui with the header parameters
Username , Password and Password Type - PasswordText , it is able to get results. The soapui tool automatically adds the following in the soap header -
     <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
         <wsse:UsernameToken wsu:Id="UsernameToken-9368150" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsse:Username>xxxxx</wsse:Username>
            <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">xxxxx</wsse:Password>
            <wsse:Nonce>aOA1P6t2hJPRyuraQ/IliQ==</wsse:Nonce>
            <wsu:Created>2009-07-10T14:58:33.781Z</wsu:Created>
         </wsse:UsernameToken>
      </wsse:Security>
However , in PI when the following configurations are made -
Web Services Security option selected in soap receiver adapter
In Receiver Agrrement -
Security Standard - http://docs.oasis ....
Security Procedure (Request) - None
Security Procedure (response) - None
the user tokens don't seem to generated and it is giving an authentication error . Is there any process of generating this in the outgoing soap header from PI.
SOAP Axis framework is not installed at present and working on PI 7.1 SP6.
Looking forward for your replies

same issue for me too.
Try using WS adapter on receiver side .
If you are able to attach SOAP header with WSSE fields using SOAP adapter at reciever channel let me know how you did it.

OSB: Attach SOAP Header for SOAP Fault

Hi,
Is there a way to return OSB SOAP Fault with custom SOAP Header?
Currently, when SOAP Fault happens, SOAP Header is not returned. I would like to insert some elements in the SOAP header and return when SOAP Fault happens.
Thanks.

Hi Eric,
Thanks for your tips. It was helpful!
I've managed to insert custom SOAP header to a SOAP fault.
In service error handler,
1. Construct custom header and replace header variable content
2. Replace body content with fault variable
3. Reply with failure
Thanks.

Can't edit narrator field for audiobooks in iTunes

I noticed a new "narrator" field in iTunes for the Audiobook media kind, but I can't edit it.
Also, I can't seem to edit the "Remember playback position" and "Skip when shuffling" options. I can fix the second issue by changing it to Music media kind, checking them, and changing it to Audiobook over again; however, seeing as there is no "narrator" field for Music, I can't use that workaround.
I am using iTunes 12.1.0.50.

Grey text when you look at the content and lock symbol at the bottom of the screen simply shows that your iPod is set to "automatically update songs and playlists". . If you want to access your iPod directly, play it through your iTunes, connect it to a second computer etc. you just need to change the update method to "Manually manage songs and Playlists" in the iPod preferences. Managing Your Songs Manually
One thing to remember about manually updating though is that the iPod also has to be manually ejected before the "Do Not Disconnect" message will go away. Safely disconnect iPod
For info: iPod 101
The iPod offers three ways to transfer music from your computer. You can select one of the following update modes from the iPod Preferences menu in iTunes (Edit=>Preferences=>'iPod' tab):
1) Automatically update all songs and playlists. This is the default mode, in which your entire music library, including playlists, is automatically synced to your iPod. If the music library on your computer exceeds the iPod storage capacity, you are prompted to select a different update method.
2) Automatically update selected playlists only. With this option, iTunes automatically copies the playlists you have selected to the iPod when you connect it to the computer.
3) Manually manage songs and playlists. You can also choose to transfer music to the iPod manually. This allows you to drag and drop individual songs and playlists from iTunes to the iPod.

JCAPS 5.12 - modifying SOAP header for webservice Invocation

I am trying to call an external web service from JCAPS 5.1.2 and need to set a token in the SOAP header. I am able to do this in other client implementations, however, the methods to modify the header don't seem to be exposed within JCAPS 5.1.2 or I do not know how to find the methods.
Has anyone tried this before?

Hi Experts,
I'm trying to protect a web service deployed in jcaps 5.1.1, using SAML assertions against an Access Manager 7/7.1, the web services clients are both, web and standalone applications, I also have read netbeans tutorials, that expose how to implement identity webservices using AppServer 9.1 + AccessManager 7.1 using the SAML Holder of key and other security mechanisms, but this implementation requiere modifications to the server.policy file to add support to SOAP message security providers and HttpServlet message security providers, the addition of a library called amwebservicesprovider.jar to the classpath suffix (this library implements the jsr-196 java Authentication Service Provider Interface for Containers) and aditional configuration required in the AM side that is not detailed in the tutorials.
Could someone guide me on how to protect the acces to a web services deployed in the jcaps logicalhost based on AM roles assigned to users?
Any help is aprecciated
Juan

Error in soap header when use webservice consumer proxy

Hi all,
I create a webservice consumer proxy to external server. the webservice provider is .Net and it required a message level security.
The soap message should include a soap header, like this:
<SOAP-ENV:Header>
<m:AuthHeader xmlns:m="http://tempuri.org/">
<m:Username>test1</m:Username>
<m:Password>test</m:Password>
</m:AuthHeader>
</SOAP-ENV:Header>
I have found many information from here. Now I used IF_WSPROTOCOL_WS_HEADER in my program, like this:
REPORT zws_jp_test01.
DATA: lo_zws_jp_co_service_soap TYPE REF TO zws_jp_co_service_soap .
DATA: lo_fault TYPE REF TO cx_ai_system_fault.
DATA: lo_appl_fault TYPE REF TO cx_ai_application_fault.
TRY.
    CREATE OBJECT lo_zws_jp_co_service_soap
      EXPORTING
        logical_port_name = 'ZWS_JP_LP4'.
CATCH cx_ai_system_fault INTO lo_fault.
    MESSAGE lo_fault TYPE 'I'.
ENDTRY.
DATA: output TYPE zws_jp_create_job_ad_soap_out .
DATA: input TYPE zws_jp_create_job_ad_soap_in .
DATA: lr_ws_header TYPE REF TO if_wsprotocol_ws_header.
DATA: lv_name TYPE string,
      lv_namespace TYPE string.
DATA l_xstring TYPE xstring.
DATA l_string TYPE string.
DATA: ixml TYPE REF TO if_ixml,
     xml_document TYPE REF TO if_ixml_document,
     xml_root TYPE REF TO if_ixml_element,
     xml_element TYPE REF TO if_ixml_element,
     xml_node TYPE REF TO if_ixml_node.
lr_ws_header ?= lo_zws_jp_co_service_soap->get_protocol(
                                           if_wsprotocol=>ws_header ).
CONCATENATE
'<SOAP-ENV:Header>'
    '<m:AuthHeader xmlns:m="http://tempuri.org/">'
      '<m:Username>test1</m:Username>'
      '<m:Password>test</m:Password>'
    '</m:AuthHeader>'
'</SOAP-ENV:Header>'
INTO l_string.
l_xstring = cl_proxy_service=>cstring2xstring( l_string ).
CALL FUNCTION 'SDIXML_XML_TO_DOM'
EXPORTING
    xml           = l_xstring
IMPORTING
    document      = xml_document
EXCEPTIONS
    invalid_input = 1
    OTHERS        = 2.
IF sy-subrc = 0 AND NOT xml_document IS INITIAL.
xml_root = xml_document->get_root_element( ).
xml_element ?= xml_root->get_first_child( ).
WHILE NOT xml_element IS INITIAL.
    lv_name = xml_element->get_name( ).
    lv_namespace = xml_element->get_namespace_uri( ).
    lr_ws_header->set_request_header(
        name            = lv_name
        namespace       = lv_namespace
        dom             = xml_element
        must_understand = SPACE
    xml_element ?= xml_element->get_next( ).
ENDWHILE.
ENDIF.
input-job_ad-id = 0.
input-job_ad_text-id = 0.
input-job_ad-publish_location = 1.
TRY.
    CALL METHOD lo_zws_jp_co_service_soap->create_job_ad
      EXPORTING
        input = input
      IMPORTING
        output = output.
CATCH cx_ai_system_fault INTO lo_fault .
    MESSAGE lo_fault TYPE 'I'.
CATCH cx_ai_application_fault INTO lo_appl_fault.
    MESSAGE lo_appl_fault TYPE 'I'.
    WRITE: output-create_job_ad_result-id.
ENDTRY.
But there is error when I run this program. the error is "SoapFaultCode:1"
In tcode ST11, I see this log:
E SOAP_RUNTIME 20100624004837.9280000 : CL_SOAP_RUNTIME_CLIENT
->EXEC_PROCESSING SOAP Fault Exception caught: : SOAP header To
was not understood.
btw the release is 701.
Any one can navigate me to solved the problem?

Hi,
I have the same problem as you did before and I posted my code in this [thread|Change SOAP Header: Consuming Webservice;.
In order to to solve your problem, I need to know what is the header that you want to add into the header, what is WSDL, and have you try testing that web service using other tool such as SOAPUI or XMLSPY and what is the result of testing tool?
Regards,
Chaiphon

"SOAP:Fault" in scenario with ABAP proxy client

Hello,
I realized the scenario CRM40_Basis620(ABAP proxy client)->XI->File.
XI:
The sender communication channel is a XI adapter (Parameters: HTTP 1.0, XI 3.0, Integration Server, Security profile unchecked, Security level - HTTP).
CRM:
The proxy generation is ok.
SLDCHECK is ok.
All RFC destinations are ok.
APPINT_200_620 for CRM was installed and configured well (I think so, but...).
When I ran the ABAP proxy client on CRM, sxmb_moni(CRM) returned the text for the XML Message (Display-CallIntegrationServer-Payloads-TraceDocument):
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = DC4424A659314CF18F500002A541D0E7</Trace>
<Trace level="1" type="T">PLNAME = SENDER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTS0004</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline SENDER</Trace>
<Trace level="1" type="T">system-ID = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
- <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV">
<Trace level="1" type="T">URL for integration server read from global configuration</Trace>
<Trace level="1" type="T">URL= http://SRMDEV.oao.sng:8011/sap/xi/engine?type=entry</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY" />
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="1" type="System_Error">HTTP-client: error response= <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header> </SOAP:Header> <SOAP:Body> <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during conversion of XI message</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIServer</SAP:Category><SAP:Code area="SECURITY">INBOUND_SECURE_LEVEL</SAP:Code><SAP:P1>DC4424A659314CF18F500002A541D0E7</SAP:P1><SAP:P2/><SAP:P3>HTTP</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Message DC4424A659314CF18F500002A541D0E7 was sent with ''. Channel configuration, however, requires 'HTTP' </SAP:Stack></SAP:Error></detail></SOAP:Fault> </SOAP:Body> </SOAP:Envelope></Trace>
</Trace>
<Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>
<Trace level="1" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>
<Trace level="1" type="System_Error">HTTP status code 500 : Error during conversion of XI message</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
</SAP:TraceHeader>
I think the main problem is the parameter "HTTP Security level" for the channel, but not sure.
Does anybody know where to find a solution?
Regards,
Roman

Hi Roman
There is no need for an XI adapter for client proxy.... we only use that for server proxies.
Vaibhav

Fault Message for inbound asynch ABAP proxy

Hi All,
I've got scenario File -> XI -> ABAP proxy all asynchronous.
Inside a proxy I'm throwing an exception using fault message.
I don't see application error in SXMB_MONI on XI, I can see that only in SXMB_MONI on receiving system.
Is it possible to have flag Application Error on XI monitor as well ?
Best Regards,
Tomasz

Jai,
I've checked that many times.
I'll describe my scenario in more details.
1. From the file I'm receiving a lot of items and trying to process as much as possible in one proxy call.
2. Those ones which are causing errors are sent out to XI (outbound proxy) one by one. XI sends them to the same interface which is used in 1. step where I have condition which checks for single item and when it's wrong then exception is thrown.
One SCM box is sender and receiver which my cause that problem.
Tomasz

Can we edit SOAP Header for an Outbound ABAP Proxy message?

Similar Messages

Maybe you are looking for