Type of configuration for web service in SOA manager

Hi Experts,
could you please let me know while creating logical port for Web sevice security which type of configuration should I select in SOA manager. There are three types of configuration. 1> WSDL Based Configuration2>Manual Configuration and 3>Process Integration Runtime.
As per the below link I am going to apply web service security but I dont have authorization to create logical port using t-code lpconfig. So I am trying to create it using SOA manager.
http://help.sap.com/saphelp_nwpi71/helpdata/EN/b8/cb1141e109ef6fe10000000a1550b0/content.htm
Regards,
Sari

Hi Krishna,
Thanks for your reply. But here I am not creating any consumer proxy. I want to create  only logical port for CO_WSSEWSSPROCESSOR_VI_DOCUMEN as mentioned in above link. I dont have any wsdl link for the same.Here I want to create logical port where I can mention the RFC for the integration server as per defined by below link.
http://help.sap.com/saphelp_nwpi71/helpdata/EN/b8/cb1141e109ef6fe10000000a1550b0/frameset.htm
When I am creating logical port by manual , its not allowing me mention any HTTP destination. By default its showing me as 'unknown' HTTP destination.
Please let me know if I have missed out any configuration. As per above link Java part  configurationI have done successfully. But for ABAP part I am confussed while creating logical port.
Regards,
Sari

Similar Messages

  • Invalid Content Type Error for Web Service

    Hi Experts,
    We have a XI / PI Web Service, and have created an Adaptive Web Service Model for the same. For using this web service model, we have created a HTTP destination of type WSDL.
    This configuration works great in our development and consolidation server.
    While working with our production server, with all the settings same as consolidation server, the following error is generated for Web Service call. using the AWS model
    java.io.IOException: Invalid content type while requesting http://<host>:<port>/webdynpro/resources/<application_package>/guicall.wsdl. Expected Content-type: text/xml, received Content-type: content/unknown, used user to connect: null
    The HTTP destination address is the one specified in bold above.
    Also, in later part of the stack trace we are bale to see this error:
    com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination
    Please guide us on this issue.
    Best Regards,
    Alka.

    Hi Alka,
    How did you configure the Webservice Destinations in Visual Admin for a webservice explosed by XI system.
    I mean what was the URL specified, did you specify XI SYSTEM userid password ???
    How was the webservice published to inspection.wsil in XI system ??
    Thanks,
    Regards,
    Aditya Metukul

  • SAML2.0 for web services - sender-vouches scenario

    We would like to configure this scenario using SAML2.0 assertion tickets. We are on ECC 6 EhP6.
    Configuration in SAML2 has been completed - no WS security policy has been configured in order to support the sender-vouches scenario.
    WSS_SETUP has run to use SAML.
    When configuring the web services we are using https for transport and SAML for authentication - the wsdl generated in this case references SAML1.1 and as result we get an error of  Wrong token type received. Endpoint expects SAML 1.1 token.
    The question is: can SAML2.0 be used for sender-vouches scenarios or not?
    Any input or help would be greatly appreciated.
    Thank you,
    Miklos

    Hi Miklos,
    Yes you can use SAML2.0 for Sendor-vouches scenarios.
    Please see the below link for configuration process:
    http://help.sap.com/saphelp_nw73/helpdata/en/b5/014086933d4576bba1b4c7e9533f4b/content.htm
    I hope it will be helpful for you.
    Regards,
    Gourav
    Message was edited by: Gourav Kumar Jena

  • Re: Why doesn't WL7.0 support get/post bindings for web services ...

    hi!!!
    Could you pls point to any code example.
    thanks
    Pushpa
    "Richard Berger" <[email protected]> wrote:
    >
    Manoj: Thanks for the answer - do you have or can you point me at any
    code samples
    that accomplish this? (Yes, .NET is limited to strings/ints in their
    get/post
    bindings).
    Thanks so much!
    RB
    PS - Also, can you explain any apparent discrepancy between your answer
    and what
    the WL documentation stated (again, it may be my misunderstanding).
    "manoj cheenath" <[email protected]> wrote:
    WL 7.0 does allow you to access the web service through
    the browser. It even allows you to invoke service methods
    with complex type arguments (.Net only supports primitive
    types) and also to view the request and response soap
    message for the invocation.
    regards,
    -manoj
    "Richard Berger" <[email protected]> wrote in message
    news:[email protected]...
    This might be a naive question, but according to the documentation,WL 7.0
    does
    not support http post/get bindings for web services. Thus, for meto
    access a
    web service, I need to write a "middle tier" of some sort (I used
    the
    automatically
    generated Java proxy code and JSP). All works fine, but it seems
    like
    it
    would
    sure be nice to have HTML forms access web services without havingto
    write a
    middle tier.
    NET does this and it is extremely useful - is there a reason that
    BEA
    chose not
    to provide this feature? (e.g. is it architecturally unsound in anyway?
    or is
    there an easy way to simulate it?). Given some of the Web Workshoppositioning
    re: ease of use and .NET comparison, this seems like an omission.
    Any insights are greatly appreciated.
    Enjoy,
    RB
    PS - Here's the info from the documentation
    Web Services Description Language (WSDL) 1.1 Specification
    WSDL is an XML-based language that describes Web services. WSDL definesWeb services
    as a set of endpoints operating on messages; these message containeither
    message-style
    or RPC-style information. The operations and messages are describedabstractly
    in WSDL, and then bound to a concrete network protocol and messageformat
    to define
    an endpoint. Related concrete endpoints are combined into abstractendpoints (services).
    WSDL is extensible to allow the description of endpoints and theirassociated
    messages regardless of what message formats or network protocols areused
    to communicate,
    however, the only bindings described in the specification describehow to
    use
    WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
    Note: WebLogic Server supports only SOAP 1.1 bindings.
    The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

    This isn't a straight FORM Post as in the http binding support in WSDL. It posts
    a soap message.
    It's apparent that Workshop supports form-post and form-get.
    But I dont see how it is done with straight WebLogic webservices. Does WebLogic
    server read the web-services.xml or the WSDL file? I dont see a way to put in
    http-post binding in the former and in the latter it seems to be ignored.
    Can someone clarify.
    Thanks.
    Chu-chi
    "manoj cheenath" <[email protected]> wrote:
    Here is a live example:
    http://65.193.192.35:7001/base/SoapInteropBaseService
    Here is an example that you can download:
    http://manojc.com/?sample2
    This is how you run it:
    http://manojc.com/?tutorial/doc/howtorun.html
    More info can be found from the edocs:
    7.0:
    http://edocs.bea.com/wls/docs70/webserv/index.html
    8.1:
    http://edocs.bea.com/wls/docs81/webserv/index.html
    Regards,
    -manoj
    http://manojc.com
    "pushpa krishna" <[email protected]> wrote in message
    news:[email protected]...
    hi!!!
    Could you pls point to any code example.
    thanks
    Pushpa
    "Richard Berger" <[email protected]> wrote:
    Manoj: Thanks for the answer - do you have or can you point me at
    any
    code samples
    that accomplish this? (Yes, .NET is limited to strings/ints in their
    get/post
    bindings).
    Thanks so much!
    RB
    PS - Also, can you explain any apparent discrepancy between your answer
    and what
    the WL documentation stated (again, it may be my misunderstanding).
    "manoj cheenath" <[email protected]> wrote:
    WL 7.0 does allow you to access the web service through
    the browser. It even allows you to invoke service methods
    with complex type arguments (.Net only supports primitive
    types) and also to view the request and response soap
    message for the invocation.
    regards,
    -manoj
    "Richard Berger" <[email protected]> wrote in message
    news:[email protected]...
    This might be a naive question, but according to the documentation,WL 7.0
    does
    not support http post/get bindings for web services. Thus, for
    me
    to
    access a
    web service, I need to write a "middle tier" of some sort (I used
    the
    automatically
    generated Java proxy code and JSP). All works fine, but it seems
    like
    it
    would
    sure be nice to have HTML forms access web services without havingto
    write a
    middle tier.
    NET does this and it is extremely useful - is there a reason that
    BEA
    chose not
    to provide this feature? (e.g. is it architecturally unsound in
    any
    way?
    or is
    there an easy way to simulate it?). Given some of the Web Workshoppositioning
    re: ease of use and .NET comparison, this seems like an omission.
    Any insights are greatly appreciated.
    Enjoy,
    RB
    PS - Here's the info from the documentation
    Web Services Description Language (WSDL) 1.1 Specification
    WSDL is an XML-based language that describes Web services. WSDL
    defines
    Web services
    as a set of endpoints operating on messages; these message containeither
    message-style
    or RPC-style information. The operations and messages are describedabstractly
    in WSDL, and then bound to a concrete network protocol and messageformat
    to define
    an endpoint. Related concrete endpoints are combined into abstractendpoints (services).
    WSDL is extensible to allow the description of endpoints and theirassociated
    messages regardless of what message formats or network protocols
    are
    used
    to communicate,
    however, the only bindings described in the specification describehow to
    use
    WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
    Note: WebLogic Server supports only SOAP 1.1 bindings.
    The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

  • Why doesn't WL7.0 support get/post bindings for web services ...

    This might be a naive question, but according to the documentation, WL 7.0 does
    not support http post/get bindings for web services. Thus, for me to access a
    web service, I need to write a "middle tier" of some sort (I used the automatically
    generated Java proxy code and JSP). All works fine, but it seems like it would
    sure be nice to have HTML forms access web services without having to write a
    middle tier.
    .NET does this and it is extremely useful - is there a reason that BEA chose not
    to provide this feature? (e.g. is it architecturally unsound in any way? or is
    there an easy way to simulate it?). Given some of the Web Workshop positioning
    re: ease of use and .NET comparison, this seems like an omission.
    Any insights are greatly appreciated.
    Enjoy,
    RB
    PS - Here's the info from the documentation
    Web Services Description Language (WSDL) 1.1 Specification
    WSDL is an XML-based language that describes Web services. WSDL defines Web services
    as a set of endpoints operating on messages; these message contain either message-style
    or RPC-style information. The operations and messages are described abstractly
    in WSDL, and then bound to a concrete network protocol and message format to define
    an endpoint. Related concrete endpoints are combined into abstract endpoints (services).
    WSDL is extensible to allow the description of endpoints and their associated
    messages regardless of what message formats or network protocols are used to communicate,
    however, the only bindings described in the specification describe how to use
    WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
    Note: WebLogic Server supports only SOAP 1.1 bindings.
    The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

    Manoj: Thanks for the answer - do you have or can you point me at any code samples
    that accomplish this? (Yes, .NET is limited to strings/ints in their get/post
    bindings).
    Thanks so much!
    RB
    PS - Also, can you explain any apparent discrepancy between your answer and what
    the WL documentation stated (again, it may be my misunderstanding).
    "manoj cheenath" <[email protected]> wrote:
    WL 7.0 does allow you to access the web service through
    the browser. It even allows you to invoke service methods
    with complex type arguments (.Net only supports primitive
    types) and also to view the request and response soap
    message for the invocation.
    regards,
    -manoj
    "Richard Berger" <[email protected]> wrote in message
    news:[email protected]...
    This might be a naive question, but according to the documentation,WL 7.0
    does
    not support http post/get bindings for web services. Thus, for meto
    access a
    web service, I need to write a "middle tier" of some sort (I used theautomatically
    generated Java proxy code and JSP). All works fine, but it seems likeit
    would
    sure be nice to have HTML forms access web services without havingto
    write a
    middle tier.
    NET does this and it is extremely useful - is there a reason that BEAchose not
    to provide this feature? (e.g. is it architecturally unsound in anyway?
    or is
    there an easy way to simulate it?). Given some of the Web Workshoppositioning
    re: ease of use and .NET comparison, this seems like an omission.
    Any insights are greatly appreciated.
    Enjoy,
    RB
    PS - Here's the info from the documentation
    Web Services Description Language (WSDL) 1.1 Specification
    WSDL is an XML-based language that describes Web services. WSDL definesWeb services
    as a set of endpoints operating on messages; these message containeither
    message-style
    or RPC-style information. The operations and messages are describedabstractly
    in WSDL, and then bound to a concrete network protocol and messageformat
    to define
    an endpoint. Related concrete endpoints are combined into abstractendpoints (services).
    WSDL is extensible to allow the description of endpoints and theirassociated
    messages regardless of what message formats or network protocols areused
    to communicate,
    however, the only bindings described in the specification describehow to
    use
    WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
    Note: WebLogic Server supports only SOAP 1.1 bindings.
    The WSDL 1.1 Specification is available at http://www.w3.org/TR/wsdl.

  • Errors configuring the Web Service Runtime

    Hi All, I'm trying to configure the Web Service Runtime using SRT_ADMIN on SAP Netweaver Trial 7.02.
    I have almost everything working, except three things. I ran SRT_ADMIN_CHECK and i got the following messages:
    Checking cross-system settings
    bgRFC destination is operational
    bgRFC supervisor destination is registered
    WSRM event handler is active
    Task watcher is active
    Data collector for monitoring is not activated
    ICF node is active. /sap/bc/srt/
    ICF node is active. /sap/bc/srt/wsil
    ICF node is active. /sap/bc/srt/wsdl
    ICF node is active. /sap/bc/srt/esf_in
    ICF node is active. /sap/bc/srt/xip
    ICF node is active. /sap/bc/srt/rfc
    ICF node does not exist. /sap/bc/srt/pm
    ICF node is active. /sap/bc/srt/xip/sap
    ICF node does not exist. /sap/bc/srt/scs
    Some of the SRT ICF nodes are inactive or do not exist
    Ending check of cross-system settings
    I checked in SICF and these two services does not exist in the tree. These two unexsting services are a limitation of the trial version?. If not, then how can I create them, if so, what are the parameters? Can I download a note or a manual regarding these two services?. Also how can I activate the data collector?

    Hi Mauro,
    Please check SAP Note 1501709 for the missing nodes issue.
    Regarding the Data Collector, I've never seen this activated anywhere before - without any repercussions. You could maybe try doing some research on a background job called SAP_SRT_COLLECTOR_FOR_MONITORING though.
    Regards, Trevor

  • Is complex type request supported by web service data set?

    I just installed OBIEE 11g and tried to create data models with web services. It works fine for web services that takes simple data types and returns complex data types. But if the request to the web service is a complex type, it doesn't work. On the Edit Data Set page, I selected "true" for Complex Type. After I entered WSDL url, it populated the Web Service dropdown, but not the Method dropdown. Any ideas?
    The other problem I am having with web service data set is that it seems to ignore the attributes in the xml response. Only xml element is recognized.
    e.g. in <trigger priority="0" font_size="0"/>, priority and font_size are ignored in the data set. Please advise. Thanks.

    Hi,
    In this usecase , you can DnD the <serviceOperationName>_parameters as an ADF from. Then DnD the operation as a method. The methods input arg value is automatically set to the parameterIterator.currentRow.DataProvider. This works fine.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Building client proxies for web services with SOAP attachemtns

    Hi all.
    I'm currently building a series of web services that take SOAP attachments as
    input, but I am unable to generate the java proxies for testing the services via
    WebLogic Workshop 8.1. When I attempt to build the proxy, I get the following
    error:
    Warning: Failed to generate client proxy from WSDL definition for this service.
    Suggestion: Please verify the <types> section of the WSDL.
    Is there something I need to alter to get this to work, or does workshop not support
    client proxies for web services with DataHandler parameters?
    Thanks.
    -Brian

    Thanks for the help. This is my first web service with SOAP attachments, so it
    may have been a long time till I realized that.
    -Brian
    "Michael Wooten" <[email protected]> wrote:
    >
    Thanks Brian,
    The problem is that you are trying to use the "document" soap-style :-)
    If you change this to "rpc", you'll should be able to successfully generate
    the
    client proxy jar. The soap-style property, is at the bottom of the "protocol"
    property sheet section, for the JWS.
    Regards,
    Mike Wooten
    "Brian McLoughlin" <[email protected]> wrote:
    Sure, sorry about that. Attached is the wsdl for a sample web service
    I created
    just to test the proxy generation.
    "Michael Wooten" <[email protected]> wrote:
    Hi Brian,
    Would it be possible for you to post the WSDL, so we can see what might
    be causing
    the problem?
    Regards,
    Mike Wooten
    "Brian McLoughlin" <[email protected]> wrote:
    Hi all.
    I'm currently building a series of web services that take SOAP attachments
    as
    input, but I am unable to generate the java proxies for testing theservices
    via
    WebLogic Workshop 8.1. When I attempt to build the proxy, I get the
    following
    error:
    Warning: Failed to generate client proxy from WSDL definition for
    this
    service.
    Suggestion: Please verify the <types> section of the WSDL.
    Is there something I need to alter to get this to work, or does workshop
    not support
    client proxies for web services with DataHandler parameters?
    Thanks.
    -Brian

  • Question about configuring REST web service in EBS instance

    I am from EBS SCM team. From one wiki page, it says OA Framework provides REST framework to expose OAF BC4J objects as web services. Can you provide more details about how to configure REST web service for one EBS instance? Any related information is also helpful.
    Edited by: 936859 on Sep 7, 2012 5:45 PM

    IIRC you must activate PAPI-WS for the engine. In Studio you do it by right-clicking on the project, then "engine preferences". In enterprise/standalone you must activate PAPI-WS in the Admin Center.

  • About XML Parameter for Web Service invoking

    I would like to use the XML parameter as the Web Service's input(Attachment is
    the XML schema) in WebLogic Server 8 sp1. When I generated the Web Service and
    use the WebLogic Server generate test web page to test it, I got Exception. The
    WebLogic Server can't constructe the input XML.
    The correct XML should look like this:
    <ids>
    <desc>Description</desc>
    <id>1</id>
    <id>2</id>
    <id>3</id>
    </ids>
    Is there any one can tell me whether this kind of XML was permitted for Web Service
    invoking or not?
    [sample.xsd]

    Hi Andy,
    On the test page, before the invoke of the operation, did it say
    something like:
    <!-- Do not know how to create a sample instance for this part due to
    the following exception:java.lang.InstantiationException:
    javax.xml.soap.SOAPElement. Pls replace this with the correct XML before
    invoking the service. --->
    if so, the service itself may be working OK, the deficiency is that the
    test page tries its best to determine sample values for the invoke,
    however it does not know in this case.
    Did you try with a client?
    Your XML should be fine.
    Regards,
    Bruce
    Andy wrote:
    >
    I would like to use the XML parameter as the Web Service's input(Attachment is
    the XML schema) in WebLogic Server 8 sp1. When I generated the Web Service and
    use the WebLogic Server generate test web page to test it, I got Exception. The
    WebLogic Server can't constructe the input XML.
    The correct XML should look like this:
    <ids>
    <desc>Description</desc>
    <id>1</id>
    <id>2</id>
    <id>3</id>
    </ids>
    Is there any one can tell me whether this kind of XML was permitted for Web Service
    invoking or not?
    Name: sample.xsd
    sample.xsd Type: ACT Project (text/xml)
    Encoding: base64

  • When trying to access one website, Firefox says " This domain is not configured for this service. Please add it to your account."

    I am trying to access a fabric website I have used before and when I try to type in the domain name, a message appears saying "This domain is not configured for this service. Please add it to your account". How do I fix this?

    That message sounds like an address might have changed on the server...
    Are you trying to access the site directly using a bookmarks, or by typing into the address bar, or by following a link in a search engine? Sometimes links change making bookmarks and search engine entries obsolete, or Firefox's autofill feature suggests an address that no longer works, so if one approach doesn't work, you might try one of the others.

  • Why do I get parsing errors with my WSDL URL for Web Services usage

    Hi,
    I am puzzled with the errors I get when I want to create a Web Service datastore.
    Scenario: I have created a SAP Web Service from CRM using SOAMANAGER. The WSDL URL produced by SOAMANAGER is accessibile when pasting the URL directly in Internet Explorer. WSDL URL [http://UXCIQ0M.WDF.SAP.CORP:50076/sap/bc/srt/wsdl/srvc_CBDCB34C89C29304E10000000A4282C0/wsdl11/allinone/ws_policy/document?sap-client=504]
    When using the WSDL URL in the Web Service datastore URL field, I get the error An error occurred while importing metadata: WSDLException; faultcode=PARSER_ERROR: Problem parsing: The element type "br" must be terminated by matching tag "/br". (BODI-1111469) (BODI-1112446)
    When I save the WSDL defintion in a local file and use a local file path, I get the errors An error occurred while importing metadata: WSDLException (at /wsdl:definitions/wsdl:portype/wsp:Policy): faultcode=INVALID_WSDL: Encountered unexpected element 'Policy. (BODI-1111469) (BODI-1112446)
    My questions:
    - Why do I get different parsing errors despite the fact that the XML is the same?
    - The WSDL is generated by SOAMANAGER. Shouldn't it work directly when integrating with Web Services generated from an SAP environment?
    - Is this related to confiurgation issue? I have set the Job Manager to Support adapter, message broker and SNMP communication
    - What is the difference between the datastore of type Adapter and the datastore Web Service? In the white paper [http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/20bd5e60-11f9-2b10-2bbb-b5109cceff08?quicklink=index&overridelayout=true] it is mentioned to use the Adapter type to consume a Web Service. It is not clear to me why we have those 2 types.
    Thanks & Best Regards
    Isabelle

    Some updates on this issue, which might help others in the community.
    - Data Service doesn't support ws_policy.
    - SAP NetWeaver 7.0 SOAMANAGER generate WDSL with ws_policy. In future releases, it is possible to specify not to use ws_policy
    - In most cases, replacing ws_policy with standard  in the URL directly, works. It doesn't work with Data Services :(.
    - Replacing ALL ws_policy in the XML directly is currently the only way to have the WSDL definition being parsed properly by Data Services.

  • WSDL error during generation of  ABAP proxy for web service

    Hi friends,
    I am getting error during the generation of ABAP proxy object for web service developed in .NET .
    Error : Proxy generation terminated: WSDL error (<extension> not supported).
    How to make this WSDL file compatible  for  ABAP proxy.
    I have tried to edit WSDL file in XML Spy but did not get any option to replace/remove the tag <extention>.
    If any one worked on this. Please help me its urgent.
    Thanks and regards,
    Shivanand.

    HI ,
    I am having the same issue!!!
    Does ABAP Proxy Generation support <extension> ?
    Is there a list available of what is supported and what not (please consider I do not have access to sap notes)?
    Thanks

  • Problem for web service path for Xcelsius engage in flash object

    Hi, All
    I had created one xcelsius through Web Service of SAP B1.it works well.
    but when I run the flash object came from xcelsius by explorer,it gives one message
    "Can not access external data"
    thier I have to give path for swf file and web service path -- (which is given at the time of connection of xcelsius through web service in data manager)
    and I have to run the web service then it shows
    the dash board made from Xcelsius very well.
    but when i change the path of same web service to other m/c then flash file does work and it gives message
    "Can not access external data"
    but in practical my web service path can be changed, it should not fixed for path which is given in data manager in Xcelsius.
    I am using Xcelsius Engage 2008 sp3
    please give suggetions for solve the problem
    thanks in advance

    Hi Venky CRMIT, Bruce007
    Aside from the question, I tried another methods and I have succeeded calling webservice. A reference URL is
    http://www.webbasedcrmsoftware.com.au/crm-on-demand-tutorials/65-java-access-to-crm-on-demand#_Toc224720963
    Main cause may be jsessionID as you guess. When I try with EAI, I have send login information and message call at once, so URL may be incorrect.
    Thank you for your help.

  • How to access  complex data type from a soap web services?

    hello
    can u please tell me how can i access complex data type from a soap web service from jdeveloper 10g
    Jdeveloper generates 3 classes
    serviceStub
    getproperties
    response
    i have to retreview the data which is a complex data type it gives some
    unknown type. and the return value is a key-value pair data type .
    regards
    vs

    After you create the partner link and the invoke (to create the variables), change the element type of the response message to the complex type definition of your collection that appears in the XSD. You can do the same thing if you want to change the element type of the payload of the request message as well.

Maybe you are looking for