Articles
Introduction to ebXMLBlake Dournaee, December 6, 2004
This article will provide the reader with a general introduction to ebXML, including an overview of the main goals of the specification set and a conceptual outline of why ebXML exists. In addition to the conceptual overview, the reader will be given an introduction to some of the details regarding the messaging layer, registry, business policies, and the relationship of ebXML to XML Web services.
Introduction to RosettaNet
Hussein Badakhchani, December 6, 2004
This article introduces RosettaNet and the benefits it brings to business-to-business (B2B) supply-chain trading partners. We will start by looking at the origins of RosettaNet, the business processes it deals with, and how it fits in with other B2B integration initiatives. Digging deeper we will examine RosettaNet's specification structure, usage scenarios, and design patterns for implementing RosettaNet solutions.
Web Services in Workshop 8.1: XML Impedance Matching
Jon Mountjoy, November 29, 2004
When creating a Web Service, a developer typically will start with an existing WSDL, an existing implementation, or some combination of the two. In this article we examine some of the features of WebLogic Workshop 8.1 that make these web services robust to changes in the WSDL or implementation datatypes.
Introduction to Web Services Metadata
Anil Sharma, October 11, 2004
Get a first glimpse at what the upcoming Web Services Metadata for the Java Platform specification has in store for the developer, and how processors can generate Web services from annotated POJO's.
Benchmark Report for JMS vs. Web Services
The objective of this benchmark is to compare the performance of JMS vs. Web services for sequential request processing.
Exception Handling with JAX-RPC -compliant Web Services
In the web services world, an exception thrown by the web service endpoint is passed on to the client as a SOAP fault. According to JAX-RPC ("Java API for XML-based RPC") specification a SOAP fault is mapped to either a javax.xml.rpc.soap.SOAPFaultException, a service-specific exception class or RemoteException.
Building a Secure Web Service using BEA's WebLogic Workshop
The following is Chapter 10 from the book, Securing Web Services with WS-Security: Demystifying WS-Security, WS-Policy, SAML, XML Signature, and XML Encryption," to be published in May 2004 by Sams Publishing.
Using SOAP Faults in WebLogic Workshop Web Services
This article will discuss the support for sending and receiving SOAP faults in BEA WebLogic Workshop Web services, that is, the support for SOAP faults on both server and client side. It begins with an overview of SOAP fault and discuss in detail the support for them in Workshop.
Introduction To XACML
A new markup language has been approved by OASIS which promises to standardize policy management and access decisions. Extensible Access Control Markup Language, or XACML, was approved and became an OASIS standard in February 2003. XACML defines a general policy language used to protect resources as well as an access decision language.
Transactional Web Services
To many people, a "transaction" is a business exchange where money is traded for goods. To software engineers the meaning is more technical. Informally, a transaction implies that a group of activities is completed as a unit, so they all succeed or all fail together. This "all or none" semantic is fundamental to database access.
Using Web Services with WebLogic Portal 8.1
In this article, we will take you step by step through connecting to a Web service, creating a Java control that talks to that Web service, and exposing that service inside WebLogic Portal using Java Page Flow.
Making Sense of Web Services Standards
This article describes the set of Web services standards that BEA believes are important to customers and developers. We classify them by three criteria: the type of problem they address, the readiness of the specification for real-world use, and how fundamental the functionality of the specification is to the Web services stack.
The Race to Create Standards
The number of Web service business process (BP) specifications trying to make their way to standards status makes it difficult to tell who is doing what, especially given that many efforts are redundant. This article makes sense out of the morass by classifying Web service BP specifications into four categories: Business analyst graphs, Message choreography, Platform-independent business process programming languages and Platform-specific business process programming languages. Further, it explores each of these programming categories and explains what specifications are available in each category and their status.
Developing JAX-RPC-based Web Services
This article demonstrates how to develop JAX-RPC-based Web services. The method described here gives the developer the freedom to write client and Web services in a way that hides all the complexities of serializing objects on-the-wire XML format. For the developer, it will simply appear to be a Java method invocation. This article also highlights how easy it is to expose a given "Java class" as a Web service.
Integrating J2EE and .NET Web Services
Analysts have projected that J2EE and .NET will each have approximately 40% of the Web services that will be implemented on their platform. This means that for a customer to be able to utilize all the Web services that will be available in the future, the platforms need to interoperate. To prove that simple J2EE and .NET Web services can interoperate, two things must be demonstrated. One, a .NET Web services client should be able to call and receive a response from a J2EE Web service, and two, a J2EE Web services client should be able to call and receive a response from a .NET Web service.
The Role of Web Services in Enterprise Application Architecture
Web services play an important role in building enterprise application architectures. These architectures, by nature, provide a blueprint describing software structure. This blueprint allows enterprise application architecture to be the confluence of business and technology, supporting business requirements and providing technology enablers.
Building Better Bridges Part 2
The most challenging integration efforts frequently involve integrating enterprise resource planning (ERP) or customer relationship management (CRM) systems with new and existing custom applications.
WebLogic Web Services Security
Security is a priority for most of our customers. As more and more customers adopt Web services, they find a need to understand how Web services can be secured and what authentication mechanism to use. In order to keep Web services open and support multiple client types, it's necessary to understand how to handle Web-services security.
Standards-Based Integration: The Impact of Web Services and J2EE
Standards can redefine a marketplace - consider the impact that SQL had on the relational database market. Standards can also create new markets - without HTML and HTTP, there would be no World Wide Web.
UI for Web Services
Web services are an excellent way to communicate between computers, but what happens when you wish to surface a Web service to users? Fortunately, WebLogic Workshop automatically creates proxies, which allow you to easily call Web services from any Java code.
Understanding Coupling
Coupling is one of those ambiguous terms that gets thrown around frequently, but very few people stop to think about its meaning and its impact on a software system. Coupling is tossed around almost as much as scalability is. And, as elaborated upon in the Clustering chapter of the Mastering EJB 2.0 book (available for download at www.theserverside.com), scalability is a term that has no foundation in computer science whatsoever! Coupling should be held up to the same level of scrutiny.
Build Enterprise-Class Web Services with BEA WebLogic Workshop
This article describes how you can effectively build enterprise-class Web services using BEA's WebLogic Workshop. We'll cover five critical areas of enterprise Web services that Workshop enables: 1) Standards, 2) Public contracts, 3) Asynchronous communications, 4) Back-end integration, and 5) Testing and deployment.
