Hello Rachid,
Can you code in the function module or is it standard?
The idea is that with some extra code you can use Application log.
See function groups SBAL and SBAL_TOOLBOX.
Examples in package SZAL.
You can create your own application log object in tcode SLG0.
Monitoring of log in tcode SLG1.
Hi everyone,
I built a very simple schema and for some reasons the framework ignores the restrictions.
The web service methode has a parameter that I would like to set a max length.
The problem is that I succeed calling the web service and passing a parameter with a length bigger than expected.
Here is the schema:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://test.ilg/" targetNamespace="http://test.ilg/">
<wsdl:types>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://test.ilg/" version="1.0">
<xs:element name="sayHello" type="tns:sayHello"/>
<xs:element name="sayHelloResponse" type="tns:sayHelloResponse"/>
<xs:complexType name="sayHello">
<xs:sequence>
<xs:element name="newarg">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
<xs:maxLength value="5"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="sayHelloResponse">
<xs:sequence>
<xs:element minOccurs="0" name="return" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
</wsdl:types>
<wsdl:message name="sayHelloIn">
<wsdl:part element="tns:sayHello" name="parameters"/>
</wsdl:message>
<wsdl:message name="sayHelloOut">
<wsdl:part element="tns:sayHelloResponse" name="sayHelloResponse"/>
</wsdl:message>
<wsdl:portType name="Test">
<wsdl:operation name="sayHello" parameterOrder="parameters">
<wsdl:input message="tns:sayHelloIn"/>
<wsdl:output message="tns:sayHelloOut"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" name="TestBinding" type="tns:Test">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sayHello">
<soap:operation soapAction=""/>
<wsdl:input>
<soap:body parts="parameters" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="TestService">
<wsdl:port binding="tns:TestBinding" name="TestBeanPort">
<soap:address xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" location="http://server/TestService/Test"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Thanks a lot.
Regards.
Hello,
I've created some WS on my system using FM -> Enterprice Services -> SOAMANAGER but, when I use the Web Service Tool in "ADMIN" business role, i can't see any of them... What are the differences between the two roads to crete / deploy a web services? is there a way to see the WS in the WS Tool?
Thank you
Hi Guys,
I have a big problem when instantiating PROXY object in ABAP for sending data through my Web Service.
Context:
A Program calls a Mondule Function that calls afterwards a Webservice.
Realization:
in SE80, I created my Webservice correctly.
and my PORT is defined correctly:
When I go to SE80 and test my WEBSERVICE in TEST Mode, SAP got me all information needed via the Matchcode to test it properly .
Also, my methods are displayed via the PORT defined:
But unfortunately, when I do some codes in the MF for calling the Webservice, I got an Exception Message when executing the program during "CREATE OBJECT PROXY" statement.
" ERROR_WEBSERVICE_RUNTIME_INIT No logical port 'LP_WOLOAD' exists for the proxy class 'ZWOLOADCO_ISERVICE' "
Have you got any idea?
Thank you all.
Rachid.
I found note 1543696 about generating a logical port in the local client.
The error occurs because the logical port for the monitored system cannot be found. As of logical ports are client dependent they need to be regenerated in the client in case the setup was made in a different one. Normally this could be done via RZ21 Menu Technical Infrastructure -> Reorganize segment table.
Hi,
I add to soamanager web service and turn off all authorization but when I execute URL with webservice
always I have message to enter login and password.
I added to WS profile security to NONE. Where is the problem, in SICF/basis?
Thanx for any answers
We are consuming a third party web service using the following steps :
We are giving some input and getting the corresponding output - We are able to consume the external WS absolutely fine.
If the server location of the above web service changes do we have to follow the above steps all over again that is create new PROXY CLASS??
What if the third party application also have a landscape just like SAP for ex - DEV, QA, PRD - the IP of the web service is different on each system.
The user(who is not a technical person) wants something very simple where they just want to put the web service's new link and system should function as it was with old link.
Hi Charlie,
How do we change the WSDL style? Do you mean the WSDL provider needs to change and regenerate the WSDL again?
I have got a WSDL generated by a non-SAP system and using that WSDL, I created the proxy. When i execute the proxy, the target system receives my message and they respond back with some response. However I get the same error message (exception) that is discussed in this thread.
Hi Karthick,
In my case, Yes. The service provider should change their WSDL style and provide the "document" style WSDL.
regards, Charlie
Hi Jordi
i am facing same problem. let me know the solution if you solved this.
thanks in advance.
Hi Krishna Teja,
I am facing a simillar error with the WSDL file. Can you please share what have you done to overcome this error.
Thanks,
Subhash.
No reply, hope my question is clear to the experts.
Hi All,
I have developed a Webservice and tesing it using WS Navigator of SOA Manager.
I am facing the issue as in the Screen-shot. I have searched and gone through forums, but I am not able to get the exact solution for this.
Please help me to know the way to take it forward.
With Regards,
Gurulakshmi
Hi experts,
We have created some service definitions from a BAPI. Runtime configuration has been set up in transaction SOAMANAGER and everything is working fine in development environment. We've just transported our service definitions to quality environment but the services are not visible in SOAMANAGER.
Any idea about what can be the issue?
Many thanks for your time.
Regards.
Hello Experts
We created a webservice from a functional module in ECC. After the webservice configuration we generated a WSDL file and when we try to access the URL present in WSDL file from our browsers, it throws 403: Forbidden error. Please note, the url has worked fine in all the environments previously, we are only facing an issue in production environment. i do not suspect any configuration issue since same steps were followed in production, could this be related to port or firewall? How can we check what could be the issue, helpful answers will be awarded points immediately, thank you.
Hi,
I'm trying to find the URL for a service called "DocumentERPFileVariantByIDAndFileVariantIDQueryResponse"
so it can be called through .NET.
I've been able to locate the WSDL and generated the proxy objects through this URL:
But in the WSDL there's no end point definition included, so where can the service it self be found?
Thanks.
Regards,
Frank
Hi Frank
Did you check in SOAMANAGER if the service is there? If there is no end point there, you can create one.
Rgds
Eng Swee
Hi Brad,
You would not believe it.
I had the same issue and came to this link, and thanks to your comment I realized that I had not created the Logical Port!
I love SDN for this!
Issue resolved and all working now.
For all others, creation of the Logical port was done through SOAMANAGER (t-code).
Regards,
Nelson
Have a look at SAP Note 1318499 - Transportability of Web services ... depending on how recent your SAP system is, you will probably need to do your setup in each target client once you have transported your service definitions.
Jonathan
Hi Jonathan,
Definitely it was a problem with the transport. I had to apply 1903490note to solve the problem.
Many thanks for your input.
Have a nice day.
Regards