Build and Deploy Web Services
Built on an extensible, standards-based application infrastructure, the BEA WebLogic Enterprise Platform makes it easy to rapidly build, deploy, manage and integrate enterprise-class Web Services. Whether you are a J2EE expert using an IDE of choice (or text editor) leveraging BEA WebLogic Server 7.0's Web Services utilities, or an applications developer who prefers event and property sheet development provided by BEA WebLogic Workshop, you can build enterprise-class Web Services that use standard J2EE components, such as stateless session EJBs, message-driven beans, and JMS destinations "under the hood", and that automatically inherit all the J2EE benefits provided by the BEA WebLogic Enterprise Platform. These benefits include scalability, support for transactions, automatic life-cycle management, easy access to existing enterprise systems through the use of J2EE APIs (such as JDBC and JTA), and a simple and unified security model. Additionally, the BEA WebLogic Enterprise Platform's Web Services architecture fully interoperates with other leading vendors' production Web Services implementations.
BEA provides two approaches to developing enterprise-class Web Services. For J2EE developers using IDEs or text editors, BEA continues to provide integration with the leading J2EE development partners, including WebGain, Borland, Forte, and Rational. These partners integrate their tools with BEA WebLogic Server, enabling BEA customers to pick the tool that best fits their needs for server side Java development. For this developer community, BEA WebLogic Server 7.0 provides a new set of "utilities" and run-time capabilities to build, expose, and access Web Services, shielding developers from needing additional expertise in XML, SOAP, and WSDL.
BEA makes it easy to rapidly build and deploy enterprise-class Web Services providing the necessary environment to speed the process and shield developers from XML programming expertise.
Developers use the built in features and the Administration Console to assemble and deploy Web Services as standard J2EE Enterprise applications in an *.ear file. That contains all the components of the Web Service such as the EJB references, SOAP servlets and so on. BEA generates all the necessary XML code so developers are not required to learn something new. Everything is done automatically for them increasing developer productivity and reducing time to market.
weblogic workshop
BEA WebLogic Workshop lets application developers rapidly create, test, and deploy enterprise-class Web service applications on the BEA WebLogic Enterprise Platform. Supported by an enterprise-class runtime framework, BEA's WebLogic Workshop was developed specifically for Web services.
WebLogic Workshop includes:
- Integrated Development Framework for Web services
- Visual representation of Web services with two-way code editing
- Integrated Web service test and debugging environment
- Automated application deployment on WebLogic Server
- simplified access to J2EE APIs and Resources with WebLogic Workshop Control Architecture (controls include access to EJBs, legacy applications, Message Queues, databases, and Web services)
- support for XML-to-Java and Java-to-XML mapping for loosely coupled application logic; Web Service Runtime Framework leveraging WebLogic Server for performance, scalability, and availability.
For more on WebLogic Workshop, see dev2dev Online's WebLogic Workshop page and the WebLogic Workshop page on bea.com.
Generation of the WSDL File
Developers that create clients that invoke a BEA Web Service need the WSDL that describes the Web Service. The BEA Platform automatically generates the WSDL of a deployed Web Service so developers don't have to, eliminating time consuming XML coding.
Java Client to Invoke a WebLogic Web Service
A thin Java client is also automatically created that developers can use to develop Java clients that invoke Web Services. The Java client JAR file includes all the classes you need to invoke a Web Service. These classes include the Java client API classes and interfaces, a parser to parse the SOAP requests and responses, the Java interface to the EJB, and so on. Client applications that use this Java client JAR file to invoke Web Services do not need to include the full WebLogic Server JAR file on the client computer.
Get the details here
|
