Web service via integration engine - integration directory tasks

Hello,
I am new to PI and need help concerning the configuration of web service communication. A new enterprise service shall be exposed to the web. So, service provider is an ABAP AS, consumer is a unknown 3rd party system. Communication should be via the integration server. I have created the data types, message types, interface (query/response) in the enterprise service repository, and the proxy and proxy class in the backend.The corresponding client is already defined as a business system in the integration directory. There are also communication channels of type xi assigned to that business system. I am not sure about the next steps. My assumption:
1) create the 3rd party system as a business component
2) add the new interface to the receiver/sender (where?) tabs of the business component
3) create a communication channel of type SOA and assign it to the new business component  (to receiver or sender?)
4) ...enough for now
Probably I forgot something important, but I am not sure... I appreciate any help.
KR
Felix

Here my own "answer" after trying several things.
The reason for the errors above are the namespaces. My incoming message contains some external namespaces which disturb the Integration Engine SOAP processing, but not the J2EE SOAP Adapter.
So I skipped the IE SOAP way, receive the SOAP data via plain HTTP adapter, and remove the SOAP header data in an XSL-Mapping. This gave also some trouble with the namespaces, but after some adaptions finally works fine now.
CSY

Similar Messages

  • Invoke Siebel OnDemand Web Service via BPEL

    Hi,
    We are trying to invoke Siebel OnDemand Web Service via BPEL.
    We have followed the steps as mentioned in
    http://www.oracle.com/technetwork/topics/ofm-siebel-blog-postings-092216.html
    But still we are unable to get the Session Id.
    Do we need to opne any port to resolve this issue or do we have any other way to get the session ID.
    Please let me know if there is any solution to this...
    Thanks

    Thanks for the update..
    We are trying to invoke the CRM On Demand session ID using the BPEL. It seems the we are having some problem with the URL
    https://secure-ausomxapa.crmondemand.com/Services/Integration?command=login
    => `Integration?command=login
    we are trying to access the URL from our SOA server using wget and we are getting following result.
    [XXXXXXXXXXXXXXX ~]$ wget https://secure-ausomxapa.crmondemand.com/Services/Integration?command=login
    --07:32:19-- https://secure-ausomxapa.crmondemand.com/Services/Integration?command=login
    => `Integration?command=login'
    Resolving secure-ausomxapa.crmondemand.com... 141.146.149.68
    Connecting to secure-ausomxapa.crmondemand.com|141.146.149.68|:443...
    We are expecting that we are unable to access the URL using 443 port.

  • Publish ABAP utility implemented on PI system as Web service via PI itself.

    Hello Experts,
    We have a requirement where we might need to publish a feature related to user management from ABAP stack of PI as a web service via PI itself.
    So scenario might look like
    SOAP Client -> PI -> PI (ABAP functionality)
    I have seen some blogs on SDN which suggest publishing FM directly using menu options in SE37 (Utilities (M) u2192 More Utilities u2192 Create Web Service u2192 From the Function Module). But then this interface will not be under PI and will be exception to general architecture of having all web services published via PI.
    May be its a very simple scenario and I am thinking of solution in complex ways. Any quick inputs from experts on what would be the best way to implement this , will be a great help for me to start quickly.
    Can we implement a normal SOAP to Proxy(ABAP) scenario for PI as we do while exposing services on ECC or any other ABAP system as a SOAP service?
    Or is there any smart way of handling this scenario?
    Kind Regards,
    Abhijeet.

    Thanks Raja & Greg for quick suggestions & your valuable time.
    Appropriate points rewarded.
    Greg, thanks for suggesting names of standard BAPI, it will save us from reinventing the wheel by using custom codes.
    I will work out on SOAP to RFC scenario & close the thread when scenario works.
    Just to Share: Yesterday, just out of curiosity I tried to use proxy scenario where PI system itself was Receiver in our sandbox, the message goes in a kind of infinite loop and keeps processing the message again and again till it turns out to error.
    I  tried it using the existing Business system for PI where it is configured as Integration Server & I have also tried to create a new business system for a different client on PI system with role as "Application System", but still the result was same.
    Kind Regards,
    Abhijeet.

  • Return NULL when invoke Web Service via UTL_DBWS

    Hi all,
    right now, i'm using UTL_DBWS to acces Web Service via database.. but when i'm trying to get data from WEB SERVICE, using utl_dbws.invoke , i got NULL value.
    It happened if The result more than Varchar2 / 32767 byte.
    i'have tried to change code by :
    result := sys.utl_dbws.invoke(l_call, l_input_params);
    P_clob := sys.anydata.accessCLOB(result);
    The Output IS NULL value even if the data was less than Varchar2 or 32767 byte..
    this is my script looks like ::
    declare
    service sys.utl_dbws.SERVICE;
    l_call sys.utl_dbws.CALL;
    result ANYDATA;
    wsdl_url VARCHAR2(1024);
    service_name VARCHAR2(200);
    operation_name VARCHAR2(200);
    input_params sys.utl_dbws.ANYDATA_LIST;
    p_out VARCHAR2(32767);
    p_xml XMLTYPE;
    p_clob CLOB;
    begin
    wsdl_url := 'http://127.0.0.1/Exercise/WSDL2.php?wsdl';
    service_name :='{urn:hellowsdl}hellwsdl';
    operation_name := 'getData';
    service := sys.UTL_DBWS.create_service (
    wsdl_document_location => URIFACTORY.getURI(wsdl_url),
    service_name => service_name);
    l_call := sys.utl_dbws.create_call(
    service_handle => service,
    port_name => null,
    operation_name => operation_name
    input_params(1) := ANYDATA.ConvertVarchar2('DOCCODE');
    result := sys.utl_dbws.invoke(l_call, l_input_params);
    p_out := sys.anydata.accessVarchar2(result);
    sys.UTL_DBWS.release_call (call_handle => l_call);
    sys.UTL_DBWS.release_service (service_handle => service);
    end;
    Thanx for Any Help

    The basics are simple:
    - format a valid SOAP envelope
    - use UTL_HTTP to make the call
    - process the response (typically XML output)
    Sample source code in {message:id=4205205}.

  • Invoking Siebel CRM OnDemand Web Service via BPEL

    I'm trying to invoke a Siebel CRM OnDemand Web Service via BPEL. Basically, the Siebel guide says to post to a url with user/pwd to get a session ID returned from a cookie. I did that using embedded java and have the session ID as a variable in my BPEL process. My problem is with now calling the Web Service to perform the action. I have a WSDL from Siebel, but the guide says to use an HTTP post with the session ID in the url and the XML in the body. How do I do that? Shouldn't the WSDL handle that when I create the Partner Link? Do I need to use more embedded Java for this or can I set up a Partner Link? I created a Partner Link and it shows the methods I want to use, but I get the following error when I try to call it because I don't know where to add the session ID:
    <ErrorCode xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">SBL-ODU-01006</ErrorCode>
    <ErrorMessage xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">Internal Error: Session is not available. Aborting.</ErrorMessage>
    Any help would be GREATLY appreciated. Please let me know if you need more information.
    THANKS!

    The Siebel OnDemand web services can accept the siebel session token in the URL. Append ';jessionid={%sessionIdFromCookie%}' to the end point. Obviously this has to be done dynamically. Refer to the article called 'Making BPEL Processes Dynamic' (http://www.oracle.com/technology/pub/articles/bpel_cookbook/carey.html) pay particular attention to the 'Eliminating address dependency at run time' section.
    Peter

  • Calling web service via SSL

    Hi,
    I do not succeed in calling a web service via SSL from within a Web Dynpro application.
    Current settings of my logical port:
    Target Address: https://...
    Authentication: HTTP authentication, basic (username/password)
    I do call methods _setUser and _setPassword to set userid and password before calling method execute() of my modelclass.
    On calling method execute(), I get message "Connection closed by remote host".
    Any suggestions ?
    Many thanks.
    Jorgen

    Can you check the following?
    1) Did you install the SAP Cryptographic toolkit for Java available from service.sap.com?
    2) Did you install the "Java Cryptography Extension (JCE)
    Unlimited Strength Jurisdiction Policy Files 1.4.2". For Sun they are available here: http://java.sun.com/j2se/1.4.2/download.html (last item on page)
    3) How is the SSL server configured? Does it require client authentication? In this case you must send a client certificate.

  • Accessing Web Service via Bluetooth

    Hi,
    I'm developing a client for a web service which is running on my system.
    Can I access this web service via bluetooth.
    Thanks

    I can give you one solution not direct but in some tricky way you can achieve what you are trying to do.
    1. Built a client application in Java and run it as a service in your laptop and will be communicate with your application at the mobile end.
    2. Send some triggering command to that application(the service you are running in laptop) from your mobile which will access the web service and perform the action you want your web service to do and send the result over bluetooth to your mobile app.
    In this case instead of using the bluetooth directly to access the web service you are making one proxy application to perform. Hope this solution will help you out to move ahead. Let me know whether it works for you or not.
    Shan!!!

  • Calling Data Services Web Services via Oracle Triggers?

    Hi,
    Has anyone called Data Services web service via an oracle trigger? If so i'm interested in your experiences with volume and perfromance.
    Thanks
    Richard

    Hi,
    Has anyone called Data Services web service via an oracle trigger? If so i'm interested in your experiences with volume and perfromance.
    Thanks
    Richard

  • Is it possible to call a web service via UWL XML configuration?

    Hello
    Is it possible to call a web service via UWL XML configuration?
    If yes then an example would be great.
    Roy

    Hi Roy,
    Yes, yes it is possible.
    Yesterday only I came across the following document which will answer your questions:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20f4843e-314f-2a10-2a88-8c4afa20dda6?overridelayout=t…
    ~Ashvin

  • Wrong data when consuming web service via ABAP

    Dear all,
    we tried to consume a web service via ABAP and used one of the various existing how-to papers from the internet in order to develop everything.
    The development was not that difficult, but when we now execute our ABAP, we noticed that
    - the first 100 returned rows from the webservice are completely correct
    - then we receive 10-15 completely incorrect rows (empty fields, redundant lines, etc.)
    - the rest of the data (60 records) is correct again
    As we nearly all objects have been generated automatically via SE80, I do not really know where this problem might come from. We double checked the original data and there everything is correct.
    Any ideas?
    Thanks for your feedback,
    Andreas

    Marcelo  Almeida wrote:
    > You can use Logial port for it in LPCONFIG ( Transaction). See this examplo Below:
    >
    > TRY.
    >
    > CREATE OBJECT my_proxy
    > EXPORTING
    > logical_port_name = 'LP01'.
    > CATCH cx_ai_system_fault.
    > ENDTRY.
    >
    > TRY.
    > input-airline_id = p_carrid.
    > input-connection_id = p_connid.
    > input-flight_date = p_fldate.
    >
    > CALL METHOD my_proxy->flight_get_detail
    > EXPORTING
    > input = input
    > IMPORTING
    > output = output.
    > CATCH cx_ai_system_fault.
    > CATCH cx_ai_application_fault.
    > ENTRY.
    >
    > Its necessary create a connection in SM59 (type H) and setting in the call parameters logical port (LPCONFIG).
    Hi,
    thanks for your answer. It´s working!
    Cheers,
    Andy

  • Invoke existing DotNet web services via B1IF soap call

    Hi All,
    I have developed my own B1IF web services and invoked them with dot net.
    I now want to invoke existing hosted web services via B1IF (Not B1IF Web Services).
    Can someone guide me using the Web Service Call (soap call).
    Can I invoke any web service via B1IF scenarios (Web Service Call) ?
    Kind Regards,
    Brenden Draper

    Hi Bastian,
    I read about it for some reason I get the following error when loading the wsdl:
    Can you maybe tell me why I get this ?
    I can access the wsdl via my browser perfectly.
    Kind Regards,
    Brenden Draper

  • Creating business services in integration directory

    Hi
      When business services are created in integration directory - these business services are not tied back to entries in the SLD - i.e we can create entries for business services directly in integration directory without having to import them from SLD.
    Now, when we migrate - from Dev environment to other landscapes - my understanding is that these business service entries are going to be migrated with the same names -and no transport target entries / validations is made during the target system import time - which happens in case of business systems having entries in SLD....
    Could anybody out there - clarify these thoughts about business service entries
    Thanks in advance - for your time .

    Hi Karthik,
         Check out these help file links, hope this will help you:
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/fe/131eb4ef2fb344abf471c9eac0063a/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/fe/131eb4ef2fb344abf471c9eac0063a/frameset.htm</a>
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/c7/301640033ae569e10000000a155106/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/c7/301640033ae569e10000000a155106/frameset.htm</a>
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/7d/6b82cd0d1aef48ab5953524c9cc5b2/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/7d/6b82cd0d1aef48ab5953524c9cc5b2/frameset.htm</a>
    http://help.sap.com/saphelp_nw2004s/helpdata/en/e6/908d3f7057eb0ce10000000a114084/frameset.htm]
    Regards,
    Subhasha ranjan

  • From CC&B, consume web service with Integrated Windows Authentication

    Most of the web services to be consumed from CC&B are exposed by external applications under Integrated Windows Authenticaton. Our CC&B 2.3 is running on Bea Weblogic on AIX 6.1.
    We need to find out, how CC&B can obtain a ticket (kerberos) in this context. Already checked documentation : XAI Best Practices, OUAF Framework Security Overview.Thanks.

    For the system to function properly you would need to configure both your Web Server and your Application (CC&B) Server. Since the authentication is done by your webLogic, you would first need to configure your Windows AD to recognise the WebLogic Server to accept the communication and transfer of tokens (TGS, TGT) betwen user,weblogic and AD.
    Kerberos authentication in a Microsoft AD enviroronment is dependant on a SPN (Service Principal Name). Therefore your Weglogic host must have a user account and enabled for Kerberos within your AD.
    The following link provides detailed steps for SSO for Weblogic (Windows & Unix) with AD
    [http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs81/secmanage/sso.html]
    Secondly, since the authroization is done by your application server, you will need to import the user accounts using LDAP and configure their rghts.

  • Consuming a sap web service via jde 4.5.7 (ecc 6.0)

    Hi all,
    I have a question here, if u could help me, i have to call a sap webeservice via jde , but before i test a jde example by calling a public web service which is not a sap web service , i used to  give  url  as:
    connThread.get("http://www.webservicex.net/globalweather.asmx/GetCitiesByCountry?CountryName="Morocco;deviceside=true";
    i was not obliged to set the apn parameters and it does work
    here as it's mentioned , there is the access point, getcities ...  the method  name and the parameter name and the parameter value
    "Morocco", but i m asking how did we precise the methods  of an rfc sap, and the name parmeter and his value.
    have u any idea to help me understand how we call sap rfc, method name, parmaeter name, cz i m a newbie to sap and bb.
    but now when i try to call an rfc sap , i give the link
      connThread.get("http://hca-ecc.hca.group:8000/sap/bc/srt/wsdl/sdef_Z_WS/wsdl11/ws_policy/document?sap-client=800;deviceside=true;apn=hca-ecc.hca.group;tunnelauthusername=forma02;tunnelauthpassword=hcaforma" );
    but it's always giving me transmission failed without any error that may help me when debugger run.
    Thakx in advance.

    Hello Merry,
    Have you tried searching 'blackberry' in SDN. I found following and many more links. It gives me impression that you may have to use MDS and also may be SAP Webdynpro technology for UI rendering.
    blackberry integration with Mobile Infraestructure
    There seems to be special site from blackberry for SAP integration (free registration).
    https://www.blackberry.com/CorpDevZone/download/SAP/sap.shtml
    Re: Steps to show data on actual Blackberry :) Urgent please....
    Hope this will give you some headway in resolving your issues.
    Regards,
    Vandana.

  • Consuming a Web Service via SSL with Basic Authentication

    Hello,
    I have a simple web service (returns a parameter value) and want to consume it. Therefore I have generated a proxy for its in Netweaver Studio SP13.
    When I set up the web service to be accessed via HTTP and Basic Authentication (Username/Password), everything is fine. When I set up the web service to communicate via HTTPS, I get the following error message in my client:
    java.rmi.RemoteException: Service call exception; nested exception is:
         java.lang.NullPointerException
         at priv.senw04.wsproxy.multisec_ssl.SSLBindingStub.pingText(SSLBindingStub.java:87)
         at priv.senw04.wsproxy.multisec_ssl.SSLBindingStub.pingText(SSLBindingStub.java:96)
         at priv.se.wsclient.MultiSecSSL.main(MultiSecSSL.java:38)
    Caused by: java.lang.NullPointerException
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.disconnect(HTTPSocket.java:625)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.closeSession(HTTPTransport.java:396)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1312)
         at priv.senw04.wsproxy.multisec_ssl.SSLBindingStub.pingText(SSLBindingStub.java:80)
         ... 2 more
    Testing the web service with WebServiceNavigator and/or by using a generated WebDynpro Client results in the following error:
    000D604C66BE004E0000001300000AFC00040922E0160632 : An error occurred during processing the timestamp. The error was: com.sap.security.core.ws.wss.NoSecurityHeaderException No wsse:Security header has been defined for role soap:finalActor. Please verify the policy configuration..
    But my main focus is on the client implementation based on a proxy. Here comes the client's code:
    public class MultiSecSSL {
        public static void main(String[] args) {
            try {
                MultiSecuritySSLAuthImpl serviceInterface = new MultiSecuritySSLAuthImpl();
                SSLBindingStub service = (SSLBindingStub)serviceInterface.getLogicalPort(MultiSecuritySSLAuthViDocument.class);
                SecurityProtocol protocol = (SecurityProtocol) service._getGlobalProtocols().getProtocol("SecurityProtocol");
                AuthenticationContext auth = protocol.getAuthenticationContext();
                auth.setIgnoreSSLServerCertificate(true);
                auth.setUsername("cfpcompany");
                auth.setPassword("demo");
                String ret = service.pingText("Called service MultiSecurity via SSL");
                System.out.println(ret);
            } catch (Exception e) {
                 e.printStackTrace(System.out);
    Here comes the logical port information of the generated proxy:
    <?xml version="1.0" encoding="UTF-8"?>
    <LogicalPorts Name='MultiSecuritySSLAuth' InterfaceName='priv.senw04.wsproxy.multisec_ssl.MultiSecuritySSLAuth'>
      <LogicalPort Name='SSLPort_Document' Endpoint='https://192.168.129.76:50001/MultiSecuritySSLAuth/SSL?style=document' BindingName='SSLBinding' BindingUri='urn:MultiSecuritySSLAuthWsd/SSL/document' BindingImplementation='SOAP 1.1 HTTP Binding with Attachments' StubName='priv.senw04.wsproxy.multisec_ssl.SSLBindingStub' Default='true' InterfaceName='priv.senw04.wsproxy.multisec_ssl.MultiSecuritySSLAuthViDocument' Original='true' Valid='true'>
        <globalFeatures>
          <Feature Name='http://www.sap.com/webas/630/soap/features/headers/' Provider='SoapHeadersProtocol' Original='false'>
          </Feature>
          <Feature Name='http://www.sap.com/webas/630/soap/features/session/' Provider='SessionProtocol' Original='false'>
            <Property Name='SessionMethod' Value='httpCookies'>
            </Property>
          </Feature>
          <Feature Name='http://www.sap.com/webas/630/soap/features/authentication' Provider='SecurityProtocol' Original='true'>
            <Property Name='AuthenticationLevel' Value='None'>
            </Property>
            <Property Name='AuthenticationMechanism' Value='HTTP'>
            </Property>
            <Property Name='AuthenticationMethod' Value='BasicAuth'>
            </Property>
            <Property Name='SupportsSSO2Authentication' Value='false'>
            </Property>
          </Feature>
          <Feature Name='http://www.sap.com/webas/630/soap/features/transportguarantee' Original='true'>
            <Property Name='Level' Value='No'>
            </Property>
            <Property Name='TLSType' Value='SSL'>
            </Property>
          </Feature>
        </globalFeatures>
        <localFeatures>
          <Operation Name='pingText'>
            <Feature Name='http://www.sap.com/webas/630/soap/features/wss' Original='true'>
              <Property Name='RequestPolicy' Value='Signature'>
              </Property>
              <Property Name='ResponsePolicy' Value='None'>
              </Property>
            </Feature>
            <Feature Name='http://sap.com/webservices/authorization' Original='true'>
            </Feature>
          </Operation>
        </localFeatures>
      </LogicalPort>
    </LogicalPorts>
    To me, this looks consistent. Any idea, what is misconfigured on my machine ?

    Hi Martin,
    that is exactly, what I did.
    - Change Web Service Configuration in IDE
    - Build and Deploy the Service to my local Server
    - Check Service in Visual Administrator
    - Deleted and Regenerated the Standalone Proxy
    - Deleted and Recreated the link between CLient and Proxy Project in IDE
    - Started Client
    Here comes the section of the ws-deployment-descriptor.xml of the service. For me, it matches, what the proxy generated.
      <webservice>
        <guid>ed8363_10876a54b6d__7fe9_192_168_129_76_1135862193037</guid>
        <ejb-name-temp>MultiSecWSBean</ejb-name-temp>
        <webservice-name>
          <namespaceURI>urn:MultiSecuritySSLAuthWsd</namespaceURI>
          <localName>MultiSecuritySSLAuth</localName>
        </webservice-name>
        <webservice-internal-name>MultiSecuritySSLAuth</webservice-internal-name>
        <standard-namespaceURI>urn:MultiSecuritySSLAuthWsd</standard-namespaceURI>
        <ws-configuration>
          <configuration-name>SSL</configuration-name>
          <ejb-name>MultiSecWSBean</ejb-name>
          <service-endpoint-name>
            <namespaceURI>urn:MultiSecuritySSLAuthWsd</namespaceURI>
            <localName>SSLPort</localName>
          </service-endpoint-name>
          <wsdl-porttype-name>
            <namespaceURI>urn:MultiSecuritySSLAuthWsd</namespaceURI>
            <localName>MultiSecuritySSLAuthVi</localName>
          </wsdl-porttype-name>
          <webservice-definition-ref>
            <package>com.technidata.cfp.i3rdparty.cfpxml</package>
            <name>MultiSecuritySSLAuthWsd.wsdef</name>
          </webservice-definition-ref>
          <service-endpoint-vi-ref>
            <package>com.technidata.cfp.i3rdparty.cfpxml</package>
            <name>MultiSecuritySSLAuthVi.videf</name>
          </service-endpoint-vi-ref>
          <transport-binding name="SOAPHTTP_TransportBinding">
            <wsdl-binding-name>
              <namespaceURI>urn:MultiSecuritySSLAuthWsd</namespaceURI>
              <localName>SSLBinding</localName>
            </wsdl-binding-name>
          </transport-binding>
          <transport-address>/MultiSecuritySSLAuth/SSL</transport-address>
          <global-features>
            <feature name="http://www.sap.com/webas/630/soap/features/transportguarantee" protocol="SecurityProtocol">
              <property name="TLSType" value="SSL"/>
            </feature>
            <feature name="http://www.sap.com/webas/630/soap/features/authorization" protocol="SecurityProtocol"/>
            <feature name="http://www.sap.com/webas/630/soap/features/authentication" protocol="SecurityProtocol">
              <property name="AuthenticationMethod" value="BasicAuth"/>
              <property name="AuthenticationMechanism" value="HTTP"/>
              <property name="SupportsSSO2Authentication" value="false"/>
            </feature>
          </global-features>
          <operation-configuration uniqueViName="pingText(java.lang.String)">
            <transport-binding-configuration>
              <input>
                <property name="soapAction" value=""/>
                <property name="encodingStyle" value="http://schemas.xmlsoap.org/soap/encoding/"/>
              </input>
              <output>
                <property name="encodingStyle" value="http://schemas.xmlsoap.org/soap/encoding/"/>
              </output>
            </transport-binding-configuration>
            <feature name="http://www.sap.com/webas/630/soap/features/wss" protocol="SecurityProtocol">
              <property name="RequestPolicy" value="None"/>
              <property name="ResponsePolicy" value="None"/>
            </feature>
            <feature name="http://sap.com/webservices/authorization" protocol="SecurityProtocol">
              <property name="security-roles">
                <property name="role1" value="use_multisec_service"/>
              </property>
            </feature>
          </operation-configuration>
        </ws-configuration>
      </webservice>
    Regards,
    Stefan

Maybe you are looking for