Need to post to HTTP destination with a dynamic URL

I have a working interface that posts to a static URL using an HTTP via an SM59 connection.
however i now need to do something similar, but use a dynamic field from the data to post as part of the url...
so it will be something like...
http://host.fqdn:port/path/goes/boldfield1bold/here/to/remove
field1 being a variable in my xml.
i guess i post to a URL with URL Address instead of HTTP destination, and i can use the header fields in adapter specific message attributes... however i do not want to send the xml....  so do i have to map just the single field to my target xml?  how do i not send the xml as it is integrated within the URL?
how do i add the field1 within the path:   /path/goes/boldfield1bold/here/to/remove into the options within the communication channel?
does that make sense?

Hi Barry,
If I understood well, and you have one part of the target URL fixed, and the other one is going to be dynamic.
You can use, as you said, the ASMA for HTTP adapter, and in the middle of the mapping you can create a simple UDF to create the URL. But as the result of that UDF, you just return the same value that you'd map if the UDF didn't exist.
For example you can use a funcion "setURL" and you can have 2 inputs: "url" and "companyname", but you just return "companyname" that is the value that really has to be mapped.
I hope this helps you.
Juan.

Similar Messages

  • Creating an HTTP destination with OAuth2SAMLBearerAssertion authentication

    Hi All,
    I'm trying to create an HTTP destination with OAuth2SAMLBearerAssertion authentication.
    However, I'm at a loss as where to put the secret/private key. It should be part of the call to the token service so must be populated somewhere. But where? I'm guessing if I create a destination via a file, there is some parameter that I could set that should contain this key, but I'm not sure what it is - certainly there is nowhere on the HCP cockpit screen that I can use.
    Downloading an existing destination that works, it looks like there is an additional "Password" parameter, but when I populate that with the private key, my connection still doesn't work.
    Is there a special format that this private key must be entered into the destination file?
    Many thanks for you help!
    Cheers,
    Chris

    Hi Timo,
    unfortunately not.
    There is also a need to pass the private key to the token generation - or to somehow get the public key that is used by HCP so that I can populate that into my remote system..
    eg for getting a SAML assert from SuccessFactors I can use (values abbreviated and altered)
    https://apisalesdemo8.successfactors.com/oauth/idp?client_id=NWI2YTMyOTdiNjA0ZmYy...kZjM2NTU2NQ&user_id=admin&token_url=…
    This generates a SAML assertion (nice of them) that I can use to get a token.
    https://apisalesdemo8.successfactors.com/oauth/token?company_id=HCPDISCC&assertion=PD94bWwgdmVy..==&client_id=NWI2YTMyOT…
    The receiving system (SuccessFactors) checks the SAML assert against the public key I have maintained against the client key on their side and grants the OAuth token which is used for subsequent authorisation.
    So somewhere I need to either - populate the system I am calling with a public key for the private key that is being used to sign the SAML assertion, or somehow pass the private key for the public key that is being used on the called system.
    I can't figure out how to do that, I'm guessing that perhaps it is more that there is a public key that I should be using on the receiving end, but not sure where I could find that.
    here's a screenshot of a working SuccessFactors connection...
    and no TrustStoreLocation so - I don't think it's using a truststore for the certificate...
    according to the doco - When the OAuth authorization server is called, it accepts the trust settings of the destination.
    Perhaps it is using the public key of the Local Service Provider in "Trust"? Certainly if this is the case it's not very obvious! (but I'm going to try!)
    Cheers,
    Chris

  • Need to solve serious security problem with Oracle Reports URL

    As mentioned repeatedly on this forum, Oracle Reports allows serious security breaches that allow users to see reports that they did not generate -- it's easy to guess a legal URL by changing the getjobid parameter.
    I've reviewed the JavaDocs to part of the rwrun.jar file and reviewed some of the example report plugins. This shows promise in helping to solve this security problem but critical pieces are missing.
    1) The javadocs are accurate for only 10g (9.0.4) but not correct for 10g (10.1.2+), which we are currently using. I need access to the updated version of this javadoc.
    2) Even with the updated version of the JavaDoc, I haven't found a class from which to inherit that would give me the opportunity to generate random jobid values, which then would effectively prevent users from guessing other jobid values, and thereby gaining access to other's reports (which in our cases, may contain sensitive information.
    3) We have found that we can send the parameter=value of EXPIRATION=1 which helps protect such information, but this requires that every program which invokes a report be modified to add this parameter. It would be far better for the report server to be configured to use a java class we write that inherits from some rwrun.jar class that would by default, add the EXPIRATION=1 parameter.

    Hi,
    Thanks for our replies. I will ask to an administrator about this security problem, now I know it depends of a security parameter.
    But I would know if it could be possible to hide the technical name of the query in the url. It could improve the security level of our reports in a first time in this way.
    Thanks a lot,
    JW.

  • Need work around for image gallery with password protected URLs

    Is there a way to display an image gallery that has password protected URLs?
    I can build the image gallery in Siena using an excel table with a list of the images and when I preview the app inside Siena I get the expected credentials prompt from IE, and I enter the credentials and the images load and display with their captions perfectly.
    There are 4-6 images in the gallery.
    When I publish and produce a store app, the app errors out with can’t connect and obviously fails on
        var GenericInitError = "The app could not connect to the server. Please try again later.",
            GenericInitTitle = "Network error";
    Most likely because Siena wants to preload everything and there is no way with preload to enter credentials.
    I am looking for any alternatives that would let me get around this.
    TIA
    -- Barb Bowman

    On Mon, 24 Mar 2014 05:10:01 +0000, Radu Gruian (MSFT) wrote:
    >One possible thing to do would be download and embed the images into your app, eliminating the need for password-based authentication.
    Nope. The app accesses a group of IP Security cameras. Static images would not
    make any sense. And authentication is required. Not negotiable.
    -- Barb Bowman

  • Error while creating the HTTP client with destination GB_DPSRetrieve

    Hi All,
    It is an interface R/3 -->XI --> HTTP ( proxy to HTTP ).
    Please find the error log below and throw some light why the HTTP adapter is getting error -
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>SystemError</SAP:MessageClass>
      <SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
      <SAP:MessageId>DC98499F-7E42-74F1-A41F-0017A4107EE6</SAP:MessageId>
      <SAP:RefToMessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:RefToMessageId>
      <SAP:TimeSent>2007-11-21T15:51:30Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">GovernmentGateway</SAP:Party>
      <SAP:Service>GGMailbox</SAP:Service>
      <SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>SAP_DEV_ERP2005</SAP:Service>
      <SAP:Interface namespace="http://sap.com/xi/HR">HR_GB_EFI_DPSretrieve</SAP:Interface>
      </SAP:Receiver>
      <SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
      </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>BestEffort</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT_DEST</SAP:Code>
      <SAP:P1>GB_DPSRetrieve</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while creating the HTTP client with destination GB_DPSRetrieve</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    - <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
      <SAP:Engine type="BS">SAP_DEV_ERP2005</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
    - <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
      <SAP:Engine type="IS">is.00.lbsth-tb1ci</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
    - <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
      <SAP:Engine type="IS" />
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
      <SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
      <SAP:Info />
      </SAP:Hop>
      </SAP:HopList>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Date>20071121</SAP:Date>
      <SAP:Time>155130</SAP:Time>
      <SAP:Host>lbsth-tb1ci</SAP:Host>
      <SAP:SystemId>XIS</SAP:SystemId>
      <SAP:SystemNr>00</SAP:SystemNr>
      <SAP:OS>Windows NT</SAP:OS>
      <SAP:DB>ORACLE</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>023</SAP:ProcStatus>
      <SAP:AdapterStatus>000</SAP:AdapterStatus>
      <SAP:User>PISUPER</SAP:User>
      <SAP:TraceLevel>1</SAP:TraceLevel>
      <SAP:LogSeqNbr>000</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
      <SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
      <SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
      <SAP:QIdInternal />
      <SAP:CommitActor>X</SAP:CommitActor>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID" />
      <SAP:EOReferenceInbound type="TID" />
      <SAP:EOReferenceOutbound type="TID" />
      <SAP:MessageSizePayload>0</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>2918</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>0</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
      <SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
      <SAP:InterfaceAction>INIT</SAP:InterfaceAction>
      <SAP:RandomNumber>15</SAP:RandomNumber>
      <SAP:AckStatus>000</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      <SAP:Receiver_Agreement_GUID>24422A5646443F8E9D975D57A3EE8162</SAP:Receiver_Agreement_GUID>
      </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.5</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.656</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>
    - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:TraceLevel>Information</SAP:TraceLevel>
      <SAP:Logging>Off</SAP:Logging>
      </SAP:Diagnostic>
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">SystemError message generated. Guid: DC98499F7E4274F1A41F0017A4107EE6</Trace>
      <Trace level="1" type="T">Error during execution of message : DC98499CA1EABEF1B4DD00110A63BF06</Trace>
      <Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): DC98499CA1EABEF1B4DD00110A63BF06</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
      </SOAP:Header>
    - <SOAP:Body>
      <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />
      </SOAP:Body>
      </SOAP:Envelope>
    Regards,
    Kishore

    Hi,
    In the HTTP Receiver what is the Addressing Type used ? (URL Address or HTTP Destination).
    If its URL Addressing Type, check if right Authentication Type is used with valid values and for HTTP Addressing Type check this HTTP Client Create Error, it could be helpful.
    Also check if the Target system can be reached from the XI server to validate the configuration parameters.
    Regards,
    S.Santhosh Kumar

  • Problem in Creating HTTP Destination

    Hello all,
    I am trying to consume a web service from ABAP and for this very reason I am creating a Client proxy and now I need to create a HTTP destination(Type G).
    I have created the Destination and when I test the connection I was facing with a error 'Service unavailable'.
    Please help me in how to resolve such an error and also let me know if there are any pre requisites before creating a HTTP Destination.
    Thanks in advance,
    Regards,
    Suman.

    Hi,
    I have raised this issue to the basis team and they are trying to figuring it out regarding the ICM/ICF paramters.
    In the mean time when I am creating the client proxy for a webservice which is internaI,I faced a error similar to which Igor has faced.
    In the WSDL document, the object
    "<complex/simpleType name="ArrayOfAnyType"> <ele..."
    from the namespace
    "http://NJNWKDEV119.enterprise.pseg.com/"
    links to the object
    from the namespace
    This webservice is from .net framework and I have asked them to check MSDN as mentioned by Anton with regards to problem faced by Igor.
    I am pasting my wsdl so that you guys can help me in finding out what exactly the error is. Thank you in advance.
    <?xml version="1.0" encoding="utf-8" ?>
    - <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://NJNWKDEV119.enterprise.pseg.com/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://NJNWKDEV119.enterprise.pseg.com/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    - <wsdl:types>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://NJNWKDEV119.enterprise.pseg.com/">
    - <s:element name="ValidatePointAddress">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="streetAddress" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="ValidatePointAddressResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="ValidatePointAddressResult" type="tns:ArrayOfAnyType" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:complexType name="ArrayOfAnyType">
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="unbounded" name="anyType" nillable="true" />
      </s:sequence>
      </s:complexType>
    - <s:element name="ValidateLineAddress">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="streetAddress" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="ValidateLineAddressResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="ValidateLineAddressResult" type="tns:ArrayOfAnyType" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="GetCrossStreetforPointAddress">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="streetAddress" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="GetCrossStreetforPointAddressResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="GetCrossStreetforPointAddressResult" type="tns:ArrayOfAnyType" />
      </s:sequence>
      </s:complexType>
      </s:element>
      </s:schema>
      </wsdl:types>
    - <wsdl:message name="ValidatePointAddressSoapIn">
      <wsdl:part name="parameters" element="tns:ValidatePointAddress" />
      </wsdl:message>
    - <wsdl:message name="ValidatePointAddressSoapOut">
      <wsdl:part name="parameters" element="tns:ValidatePointAddressResponse" />
      </wsdl:message>
    - <wsdl:message name="ValidateLineAddressSoapIn">
      <wsdl:part name="parameters" element="tns:ValidateLineAddress" />
      </wsdl:message>
    - <wsdl:message name="ValidateLineAddressSoapOut">
      <wsdl:part name="parameters" element="tns:ValidateLineAddressResponse" />
      </wsdl:message>
    - <wsdl:message name="GetCrossStreetforPointAddressSoapIn">
      <wsdl:part name="parameters" element="tns:GetCrossStreetforPointAddress" />
      </wsdl:message>
    - <wsdl:message name="GetCrossStreetforPointAddressSoapOut">
      <wsdl:part name="parameters" element="tns:GetCrossStreetforPointAddressResponse" />
      </wsdl:message>
    - <wsdl:portType name="AddValidationSoap">
    - <wsdl:operation name="ValidatePointAddress">
      <wsdl:input message="tns:ValidatePointAddressSoapIn" />
      <wsdl:output message="tns:ValidatePointAddressSoapOut" />
      </wsdl:operation>
    - <wsdl:operation name="ValidateLineAddress">
      <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">ValidatelineAddress -Public web method to validate the line address for the first call from SAP Address Validation screen</wsdl:documentation>
      <wsdl:input message="tns:ValidateLineAddressSoapIn" />
      <wsdl:output message="tns:ValidateLineAddressSoapOut" />
      </wsdl:operation>
    - <wsdl:operation name="GetCrossStreetforPointAddress">
      <wsdl:input message="tns:GetCrossStreetforPointAddressSoapIn" />
      <wsdl:output message="tns:GetCrossStreetforPointAddressSoapOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:binding name="AddValidationSoap" type="tns:AddValidationSoap">
      <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ValidatePointAddress">
      <soap:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/ValidatePointAddress" style="document" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
    - <wsdl:operation name="ValidateLineAddress">
      <soap:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/ValidateLineAddress" style="document" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
    - <wsdl:operation name="GetCrossStreetforPointAddress">
      <soap:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/GetCrossStreetforPointAddress" style="document" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="AddValidationSoap12" type="tns:AddValidationSoap">
      <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ValidatePointAddress">
      <soap12:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/ValidatePointAddress" style="document" />
    - <wsdl:input>
      <soap12:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap12:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
    - <wsdl:operation name="ValidateLineAddress">
      <soap12:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/ValidateLineAddress" style="document" />
    - <wsdl:input>
      <soap12:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap12:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
    - <wsdl:operation name="GetCrossStreetforPointAddress">
      <soap12:operation soapAction="http://NJNWKDEV119.enterprise.pseg.com/GetCrossStreetforPointAddress" style="document" />
    - <wsdl:input>
      <soap12:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap12:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:service name="AddValidation">
    - <wsdl:port name="AddValidationSoap" binding="tns:AddValidationSoap">
      <soap:address location="http://njnwkdev119/PSEGAV/AddValidation.asmx" />
      </wsdl:port>
    - <wsdl:port name="AddValidationSoap12" binding="tns:AddValidationSoap12">
      <soap12:address location="http://njnwkdev119/PSEGAV/AddValidation.asmx" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>
    Regards,
    Suman.

  • Disable Cookies in HTTP Destination

    Hi,
    Is there a possibility to disable cookies for the visual admin? Because we want to disable this for the HTTP destination service in the visual admin.
    br
    Steven

    Hi,
    that is a strange error message.
    I don't know how siteminder works but I guess your are using siteminder as SAML identity provider and configured the SAML Login Module in SAP to achieve SSO correct?
    For this purpose you need to define a HTTP Destination which is than used as SAML Receiver.
    What I do not get is the Cookie Problem.
    I don't know exactly how your process flow is but it should be something like
    - Your Client authenticates to your identity provider (let's say siteminder)
    - Any time later you try to access any resource that is configured to support SAML using SAML Assertions (e.g. SAP J2EE)
    - Your identitiy provider will generate an SAML Artifact an redirect you to the destination application (in your case some J2EE Application on SAP that is configured to validate your SAML Artifact (using the SAML Login Module)
    => This initial client request to your identity provider can contain cookies and you cannot avoid this since they are carried and sent by the client (Browser) => I hope this does not cause any problems because it really shouldn't
    Nevertheless:
    Your client request containing the SAML Articat (something like http://<j2eehost>:<j2eeport>/YourApp?TARGET=<YourApp>&SAMLArt=<Artifcat created by IDP>
    reaches the engine:
    Now the Engine creates an HTTP Post Request to your IDP that contains the SAML Assertion (SAML Assertion Request). This Assertion request also contains the Artifact and it does not contain any cookies!!! Your IDP now validates the Requests and sends an SAML Assertion Response to your engine (The SAML Login Module extracts the User from the Response (This one is carried in the NameIdentifier of the SOAP Message) and authenticates the user if it exists on the J2EE Engine
    You finally receive the response of your Destination Application.
    I don't really understand the cookie issue:
    Maybe it really helps if you allow unsecure connections for SAML in SAP J2EE  (You can enable this under Visual Admin > Configuration Adapter > saml > Settings > AllowUnsecureConnections > true)
    so you can use http instead of https. Now use Wireshark or tcpdump or something similar to create a dump of your traffic and analyze it to check where the problem is or maybe send it to me so I can have a look at it.
    Hope this helps
    Let me know if you need further assistance on this (Reward points for helpful answers are always appreciated )
    Cheers

  • HTTP Error with Status code 403 when using ABAP Server Proxies

    Hi All,
    I have been working on ABAP Client and Server proxies in my project. The weblogs by Ravikumar, Prateek Shah,  Siva Maranani & VijayaKumari were very helpful and thank them all for just helpful and guiding postings.
    Interfaces using Client proxies are working fine and have been tested successfully. But I'm facing bit problems with Server Proxies. The scenario is of File to SAP system via XI. Data is coming correct up to Technical routing in pipeline but at call adapter(for Server Proxy to SAP)in XI pipeline I receive Error:
    HTTP response contains status code 403 with the description Business Server Page (BSP) Error Error when sending by HTTP (error code: 403, error text: Business Server Page (BSP) Error)
    Previously I was receiving authentication and authorization related error of status code 401 and then in communication channel I replaced user profile with a user id having role SAP_XI_APPL_SERV_USER. The basis peron has created new user id with role SAP_XI_APPL_SERV_USER  only and that I'm using. I've tried creating a HTTP destination with the created user id and in test connection too receive same error message.
    Please help me out with your inputs and understanding on the topic.
    Thanks and Best Regards
    Prashant Rajani

    Hi Prashant,
    Please take a look at these threads..They deal with the same problem, and they have been resolved here.
    BSP Authorization error
    Service cannot be reached .  error code 403 the reason forbiddn
    403 Error when accessing the server
    Hope your issue gets resolved.
    cheers,
    Prashanth
    P.S Please mark helpful answers

  • Using a HTTP destination through a HTTP proxy

    Hi there!
    I have written a Web Dynpro application that connects to a web service using a web service model. The request is configured to use a HTTP destination by means of the _setHTTPDestinationName() method. I configured the HTTP destination in the visual administrator and it uses Logon ticket to authenticate.
    All this works perfectly in my test environment. Unfortunately in my production environment the web service must be accessed through a HTTP proxy and I could not find where to configure the proxy settings for HTTP destinations.
    I found some information about "open a transaction in SICF" an so on which doesn't help me because I have no ABAP client.
    I found some information about configuring proxies in the NWA but this does not seem to apply to my NW version, wich is 2004 SP16.
    Any clues?
    Thanks in advance.

    Hi Olivier,
    thank you for your reply.
    Is there really a possiblity to configure a proxy for any given HTTP Destination in ABAP? Because if there is, I cannot believe that there is no equivalent in Java. As there is no such a thing as a HTTP Destination "for ABAP" and a HTTP Destination "for Java", what would happen if I used the HTTP Destination with proxy settings created in ABAP for my Java program?
    There is another way to use a proxy which I found by analysing the generated Java classes of my web service model. You can do the following:
    SomeServiceImpl service = SomeDMSModel.getServiceImpl();
    service.setHTTPProxyResolver(new HTTPProxyResolver() {
      HTTPProxy proxy;
      public HTTPProxy getHTTPProxyForHost(String host) throws RemoteException {
        if (this.proxy == null) {
          this.proxy = new HTTPProxy();
          this.proxy.setProxyHost("proxy.company.com");
          this.proxy.setProxyPort(1234);
        return this.proxy;
    This is NOT a good way to do it, as it transfers a portal administration task to the programmer, but it shows that the functionality is present in Java.
    So I haven't given up on finding where it has to be configured...
    Edited by: Robert Rodewald on Jan 18, 2008 11:01 AM

  • Missing Message Attributes: URL/HTTP Destination

    Hello,
    following scenario:
    There is a sync. interface between SAP PI ante the Paypal API within the HTTP adapter calling a dynamic URL.
    The dynamic URL is created as mentioned in this blog: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/7264. [original link is broken]
    Also the HTTP adapter is configured as described (Adapter Specific Message Attributes and URL are flagged).
    Following error occours when testing the call:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_MISSING_URL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Dynamic Header - Missing Message Attributes: URL/HTTP Destination</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Is there sth. special I have to consider in the HTTP Adapter?
    Thanks in advance,
    André

    Hi Michal,
    I´m passing the URL to the attribut "TargetURL" by using a UDF in my mapping.
    In the adapter I have flagged "URL".
    So the value of TargetURL set in mapping shoul be used as destination in the adapter.
    Please have a look onto my UDF used in MM:
    http://img408.imageshack.us/i/udf.jpg/
    Adapter settings:
    http://img691.imageshack.us/i/adaptersetting1.jpg/
    http://img339.imageshack.us/i/adaptersetting2.jpg/
    How can I check that the TargetURL is successfully set as a dynamic parameter?
    Thanks,
    André

  • POST through HTTPs

    Hi, I try to perform http POST using
    http://martin.nobilitas.com/java/cookies.html
    it works.
    However, when I try to perform POST using https, by using tips
    // Dynamically register the JSSE provider.
    java.security.Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
    // Set this property to use Sun's reference implementation of the HTTPS protocol.
    System.setProperty("java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol");
    it won't work anyone. I get error
    Exception java.io.IOException: Server returned HTTP response code: 500 for URL: https://www.xyz.com/dologin.jsp
    any suggestion?
    thanks

    * Main.java
    * Created on April 15, 2007, 10:05 PM
    * To change this template, choose Tools | Template Manager
    * and open the template in the editor.
    package oskcookies;
    import java.net.*;
    import java.io.*;
    * @author yccheok
    public class Main {
        /** Creates a new instance of Main */
        public Main() {
    /** Post a string to an URL and get the reply as a string. Returns an empty
    string if things didn't work out. */
        static public String getURLPostString(URL url, String body) {
            StringBuffer sb = new StringBuffer();
         // find the newline character(s) on the current system
            String newline = null;
            try {
                newline = System.getProperty("line.separator");
            } catch (Exception e) {
                newline = "\n";
            try {
             // URL must use the http protocol!
                HttpURLConnection conn = (HttpURLConnection) url.openConnection();
                conn.setRequestMethod("POST");
                conn.setAllowUserInteraction(false); // you may not ask the user
                conn.setDoOutput(true); // we want to send things
                // the Content-type should be default, but we set it anyway
                conn.setRequestProperty( "Content-type", "application/x-www-form-urlencoded" );
                // the content-length should not be necessary, but we're cautious
                conn.setRequestProperty( "Content-length", Integer.toString(body.length()));
                // get the output stream to POST our form data
                OutputStream rawOutStream = conn.getOutputStream();
                PrintWriter pw = new PrintWriter(rawOutStream);
                pw.print(body); // here we "send" our body!
                pw.flush();
                pw.close();
                // get the input stream for reading the reply
                // IMPORTANT! Your body will not get transmitted if you get the
                // InputStream before completely writing out your output first!
                InputStream  rawInStream = conn.getInputStream();
                // get response
                BufferedReader rdr = new BufferedReader(new InputStreamReader(rawInStream));
                String line;
                while ((line = rdr.readLine()) != null) {
                    sb.append(line);
                    sb.append(newline);
                return sb.toString();
            } catch (Exception e) {
             System.out.println("Exception "+e.toString());
             e.printStackTrace();
            return ""; // an exception occurred
         * @param args the command line arguments
        public static void main(String[] args) {
            // TODO code application logic here
            try {
                // Dynamically register the JSSE provider.
                java.security.Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
                // Set this property to use Sun's reference implementation of the HTTPS protocol.
                System.setProperty("java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol");
                URL url = new java.net.URL("https://www.abc.com/dologin.jsp");
                String txtUserName = "txtUserName="+URLEncoder.encode("username");
                String txtPassword = "txtPassword="+URLEncoder.encode("name");
                String _continue = "continue="+URLEncoder.encode("/quotes.jsp");
                String sessionError = "sessionError="+URLEncoder.encode("0");
                String body = txtUserName + "&" + txtPassword + "&" + _continue + "&" + sessionError;
                /* https://www.abc.com/dologin.jsp?txtUserName=username&txtPassword=password&continue=%2Fquotes.jsp&sessionError=0 */
                System.out.println(getURLPostString(url, body));
            catch(java.net.MalformedURLException exp) {
                exp.printStackTrace();
    }please take note that, when i directly enter this URL in my web browser (https://www.abc.com/dologin.jsp?txtUserName=username&txtPassword=password&continue=%2Fquotes.jsp&sessionError=0), the page can be login successful.
    However, if I execute the above code, I get the following error:
    Exception java.io.IOException: Server returned HTTP response code: 500 for URL: https://www.abc.com/dologin.jsp

  • PI 7.1 HTTP Adapter - overwritte Prolog dynamically

    I use a HTTP Adapter to send XML Data via HTTP as form field. Therefore i use the prolog constant. Example: xmlfile=.... Now i need two new parameter (user and password) as post parameters. I can change to prolog like user=...&password=....&xmlfile=.. But in this case the prolog with the user is hard coded. in my scenaria the user and password should dynamically load from Message Mapping. The solution with the dynamic URL Parameter 1-6 could not be used, because this values are GET Parameters which are visible in der URI!
    Is there a solution for post parameters dynamically via HTTP Adapter?

    The operation mapping aka Interface mapping's need not only use 1 single mapping.
    In the interface mapping you can add multiple message mappings and / or other mapping programs.
    The mappings get executed sequentially and the output of first mapping is input to second mapping and so on.
    In this case, write a java mapping that will take the input as the output of your graphical mapping; add the prolog to this and make it the output of your Java Mapping and this is the final output of your Operation mapping!
    Regards
    Bhavesh

  • Need to Understand HTTP Server with mod_plsql

    Hi -
    I am a DBA and have been tasked with migrating our current setup Oracle 10g/Solaris/APEX 4.1 to Oracle 11g/Linux/APEX 4.1. I have completed the migration and have chose to use the embedded PL/SQL gateway for connections to the front end Apex Application.
    The Embedded PL/SQL gateway is not that good. We are having connection issues where you might have to wait 5 minutes until you get the login page. Otherwise you just keep getting "cannot display webpage" errors.
    In our old setup we had a seperate home from some type of APEX listener. I thiink it was the HTTP Server with mod_plsql. We had to run this command to start it (apachectl start). This was very reliable and I think I need to do the same on our new server. I cannot find documentation anywhere on how to install this home on the new server and how to set it up. Does anyone know where it is and point me in the right direction?
    Your help would be greatly appreciated.

    Hello,
    >> I cannot find documentation anywhere on how to install this home on the new server and how to set it up
    The following includes detailed instruction on how to install either the APEX Listener or the OHS.
    http://docs.oracle.com/cd/E23903_01/doc/doc.41/e21673/otn_install.htm#CBHBDAIF
    >> The Embedded PL/SQL gateway is not that good …
    You didn’t mention the size (and load) of your network, but the EPG was not intended to be used in a production environment. In any case, the document I pointed you to also includes some important configuration instructions for the EPG that dramatically improved its performance. Still, not recommended for crowded production environment.
    Regards,
    Arie.
    &diams; Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.
    &diams; Author of Oracle Application Express 3.2 – The Essentials and More

  • Error while creating the HTTP client with destination

    Hi ,
    I am getting this error while connecting to https location on receiver channel . The below error i am getting in SXMB_moni
    Error while creating the HTTP client with destination
    The receiver party is doing some security setting on there end and for that purpose we have provided the external IP address to them , after that we are getting the above error.
    We have already installed the client certificate on our staging server , and have done the correct setting in SM59 and channel.

    Check few things..
    1) I believe you use specify destination for the addressing type field in the comm channel. If so make sure you entered valid target URL address in the SM59 of type http destination.
    2) Check the validitity of the certificate. You can import the certificate both in java and abap stack.
    3) Make sure certificate is installed as expected.
    4) Send the request and talk to the target system and check what error information they get in their log related to ssl.

  • Help needed to start HTTP Protocol with timeout

    I am looking for information to point me in the right direction. I would like to create a class that would implement the HTTP protocol and would allow the user to specify a timeout if unable to connect to the server. I have used the URL and HttpURLConnection classes before, but have not used any of the other classes in the java.net package. I am just trying to create an app that will download a file from a specified URL. Something that I could use in the future and something to get more programming experience using the java.net package.
    Could you tell me:
    1) Which classes I would need to use to help implement a timeout
    2) Where I can find an example or other information on how to implement the HTTP protocol with the class from question 1 above.
    TIA for any information

    That would definately reduce the coding time but would
    do little to help with my understanding of classes in
    the java.net package or to gather a better
    understanding of the HTTP protocol. :-)
    That said, I am currently downloading the 1.5 beta to
    see what they have done.If it's just an academic thing to re-invent the wheel (code) that deals with the HTTP protocol, then go right ahead (ok, you don't need my permission).

Maybe you are looking for