Enterprise Server enables you to easily deploy and test web services.
Deploy a web service in an enterprise archive (EAR) just as you would an enterprise application.
A web service can also be implemented by a POJO (plain old Java Object). Deploy a POJO web service using the auto-deploy feature by dragging and dropping it into the auto-deploy directory. Enterprise Server will automatically generate the appropriate web XML files and deploy the web service.
In Admin Console, you can view a list of deployed web services under Application Server > Web Services | General.
To test a web service with Admin Console, select Applications > Web Services > web-service-name | General. Admin Console displays t the attributes of the web service:
Name: the name of the web service.
Endpoint Address URI: the URI of the web service endpoint.
Application: Click on the link to display the properties of the web application or enterprise application.
WSDL: Click on the link to display the WSDL file for the web service.
Module name: the name of the WAR or EAR file for the web service.
Mapping File: Click on the link to display the Java WSDL mapping file.
Webservices.xml: click on the link to display the webservices.xml file.
Implementation Type: SERVLET or EJB
Implementation Class Name:
Admin Console enables you to test web services and diagnose problems. You can ping a deployed web service with a generic test Servlet. SOAP messages are displayed for each method invocation.
To test a web service with Admin Console, select Applications > Web Services > web-service-name | General, then click the Test button.
Support for SOAP message layer security is based on the SAML token profile of WS-Security. Tamper-proof auditing for Web services is also provided.