!--a11y-->
Service Endpoint Interface 
The Service Endpoint Interface (SEI) exposes the business methods provided by a particular Web service. It is generated from the WSDL PortType and named after the PortType. The way the methods are generated depends on the PortType and the JAX-RPC 1.0 conventions.
For SAP Web Service Clients, an additional option is provided – generation of RPC-style SEI for document/literal-style WSDLs. In this case, for each generated method that has only one wrapper parameter for the input, and one wrapper parameter for the output, an additional method is generated that has the same name, but in whose signature the input and output parameters are unwrapped.

package example.client;
public interface CalendarServiceRpc extends java.rmi.Remote,javax.xml.rpc.Stub {
public float add(float p1, float p2) throws java.rmi.RemoteException; public float div(float p1, float p2) throws java.rmi.RemoteException;
} |
Sometimes, conditions exist that require user intervention such as changing the Web service location or using security. Most of these features are editable in the Logical Port editor in the SAP NetWeaver Developer Studio.
· Setting the endpoint URL

client._setProperty(CalendarServiceRpc.ENDPOINT_ADDRESS_PROPERTY, |
· Setting an HTTP proxy for this client

port._setProperty("javax.xml.rpc.http.proxyhost","proxy"); port._setProperty("javax.xml.rpc.http.proxyport","8080"); |
· Setting HTTP Basic Authentication

client._setProperty(CalendarServiceRpc.USERNAME_PROPERTY,"username"); client._setProperty(CalendarServiceRpc.PASSWORD_PROPERTY,"password"); |
See also:
Programming a Web Service Client Application
