Logical port problem

Question

Hi All
I create logical port in LPCONFIG for a WS and i put the proxy class and logcal port (just variable like abc ) i choose defult port
and in runtime i choose webservice and in in call parameters in URL i put the WSDl of the WS i create via se37 .
when i activate it i get message : Web service requires state management
What i need to do to overcome this issue?
Best Regards
Nina

Answer 1

Hi Nina,
Purpose
The options for error handling depend on the type of communication chosen:
·        Asynchronous Communication: On the sender side, the application can only handle errors that occur when the message is being sent (for example,  the outbound queue is full). You can catch and persist these errors by using the exception class CX_AI_SYSTEM_FAULT. On the receiver side, as in the synchronous case, you can define fault messages, which are then only forwarded to monitoring (and not to the sender).
If you want to define how the sender is to process asynchronous errors, see the Acknowledgments section. The Web service runtime only supports synchronous communication.
·        Synchronous Communication: You can use fault messages to handle errors that have occurred on the receiver side. To confirm an error, the proxy runtime sends the fault message from the receiver back to the sender, which can then respond to it.
Process Flow
The example used here works with the XI runtime standardized structure. When using the Web service runtime, follow the same procedure to trigger an exception on the receiver side and handle it on the sender side (indicated in the source text by the comments with a hash symbol (#)). The fault message structure is defined by the WSDL description in both cases and is found in the exception class.
    1.      If an application on the receiver side triggers an error, the ABAP proxy runtime converts the corresponding exception class to a fault message and transfers it to the sender system.
       2.      In the sender system, the ABAP proxy runtime interprets the fault message and triggers the exception for the client proxy.
       3.      In the sender system, the application can catch and handle the exception using a Try/Catch block. Using the super exception class CX_AI_APPLICATION_FAULT you can - in a similar way to the statement WHEN OTHERS in a CASE statement - catch all remaining application errors.
see the following links for Possible ...
http://help.sap.com/saphelp_nw70/helpdata/EN/75/a55c3cff8ca92be10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/25/a45c3cff8ca92be10000000a114084/frameset.htm
Regards,
Prabhudas