Programming WebLogic Web Services
The following sections describe tasks for administering WebLogic Web Services:
Once you develop and assemble a WebLogic Web Service, you can use the Administration Console to deploy it on WebLogic Server. Additionally, you can use the Administration Console to perform standard WebLogic administration tasks on the deployed Web Services, such as undeploy, delete, view, and so on.
Typically, a Web Service is packaged as an EAR file. The EAR file consists of a WAR file that contains the web-services.xml
file and optional Java classes (such as the Java classes that implement a Web Service, handlers, and serialization classes for non-built-in data types) and a optional EJB JAR files that contain the stateless EJBs that implement the Web Service operations. The servicegen
Ant task always packages a Web Service into an EAR file.
You can also package a Web Service as just a Web application WAR file if the operations are implemented with only Java classes, and not EJBs.
The Administration Console identifies a Web Service by the contents of the WAR file. In other words, if the WAR file contained in an EAR file contains a web-services.xml
file, then the Administration Console lists the WAR file as a Web Service. The Administration Console uses the
icon to indicate that the WAR file is in fact a Web Service.
To invoke the Administration Console in your browser, enter the following URL:
http://
host
:port
/console
host
refers to the computer on which the Administration Server is running.port
refers to the port number where the Administration Server is listening for connection requests. The default port number for the Administration server is 7001.The following figure shows the main Administration Console window.
Figure 17-1 WebLogic Server Administration Console Main Window
You can perform the following tasks using the Administration Console: