1 Understanding Web Services
For definitions of unfamiliar terms found in this and other books, see the Glossary.
1.1 Overview of Web Services
Web services are loosely coupled, distributed environments that allow companies to integrate heterogeneous applications within the enterprise or expose business functions to their customers and partners over the Internet.
A web service is a program that can be accessed remotely using different standards-based languages. What this program can do (that is, the functionality it implements) is described in a standard vocabulary.
Major benefits of web services include:
-
Interoperability among distributed applications that span diverse hardware and software platforms
-
Easy, widespread access to applications through firewalls using Web protocols
-
A cross-platform, cross-language data model that facilitates developing heterogeneous distributed applications
Web services are characterized by three factors:
-
What they do (the business functionality they expose).
-
Where they are (the web site which exposes that functionality).
-
How they can be accessed (the set of published interfaces necessary to use the exposed functionality).
In summary, web services are loosely coupled, distributed environments that allow companies to integrate heterogeneous applications within the enterprise or expose business functions to their customers and partners over the Internet. Because you access web services using standard Web protocols such as XML or HTTP, the diverse and heterogeneous applications on the Web (which typically already understand XML and HTTP) can automatically access web services and communicate with each other.
Table 1-1 lists the supported web service protocols.
Table 1-1 Supported Web Service Protocols
| Protocol | Description |
|---|---|
|
Simple Object Access Protocol (SOAP) |
A protocol for exchanging structured information in the implementation of web services. For more information, see About SOAP Web Services |
|
Representational State Transfer (REST) |
Any simple interface that transmits data over a standardized interface (such as HTTP) without an additional messaging layer, such as SOAP. For more information, see About RESTful Web Services |
1.1.1 About SOAP Web Services
SOAP provides a protocol for exchanging structured information in the implementation of web services.
SOAP web services rely on XML-based and other industry standards:
-
Simple Object Access Protocol (SOAP)—A protocol for exchanging structured information in the implementation of web services.
-
Extensible Markup Language (XML)—A data format that allows uniform communication between web services consumers and web services providers.
-
XML Schema—A framework that describes XML vocabularies used in business transactions.
-
Web Services Description Language (WSDL)—An XML-based language providing a model for describing SOAP-based web services.
-
WS-Policy—The WS-Policy framework provides a flexible and extensible grammar for describing the capabilities, requirements, and general characteristics of web services using policies.
-
Universal Description, Discovery, and Integration (UDDI)—A framework to publish and look up web services on the Internet.
For example, a banking web service may implement functions to check an account, print a statement, and deposit and withdraw funds. These functions are described in a WSDL file that any consumer can invoke to access the banking web service. As a result, a consumer does not have to know anything more about a web service than the WSDL file that describes what it can do.
A web service consumer (such as, a desktop application or a Java Platform, Enterprise Edition client such as a portlet) invokes a web service by submitting a request in the form of an XML document to a web service provider. The web service provider processes the request and returns the result to the web service consumer in an XML document as shown in the example below.
Figure 1-1 Example of SOAP Message Exchange Between Web Service Consumer and Provider
Description of "Figure 1-1 Example of SOAP Message Exchange Between Web Service Consumer and Provider"
In this example, the web service consumer sends a request in the form of a SOAP message (SOAP is an XML messaging framework designed to allow heterogeneous applications to exchange structured information in a distributed environment). The web service provider (www.example.com) processes the request and returns the response, in this case the stock quote for Oracle. In the example above, the web service provider may have asked for credentials to access the service, for example a username and a password. Also, the web service provider may have encrypted the response (the value of the stock).
1.1.2 About RESTful Web Services
REST describes any simple interface that transmits data over a standardized interface (such as HTTP) without an additional messaging layer, such as SOAP. REST provides a set of design rules for creating stateless services that are viewed as resources, or sources of specific information, and can be identified by their unique URIs.
A client accesses the resource using the URI, a standardized fixed set of methods, and a representation of the resource is returned. The client is said to transfer state with each new resource representation. RESTful web services are services that are built according to REST principles and, as such, are designed to work well on the Web. RESTful web services conform to the architectural style constraints defined in Introduction to the REST Architectural Style in Oracle Fusion Middleware Developing and Securing RESTful Web Services for Oracle WebLogic Server. Typically, RESTful web services are built on the HTTP protocol and implement operations that map to the common HTTP methods, such as GET, POST, PUT, and DELETE to create, retrieve, update, and delete resources, respectively.
The Java API for RESTful Web Services (JAX-RS) provides support for creating web services according to REST architectural style. JAX-RS uses annotations to simplify the development of RESTful web services. By simply adding annotations to your web service, you can define the resources and the actions that can be performed on those resources.
A JAX-RS resource is an annotated POJO that provides resource methods that are able to handle HTTP requests for URI paths that the resource is bound to. Consider the following example:
package com.example;
import javax.ws.rs.GET;
import javax.ws.rs.Path;
import javax.ws.rs.Produces;
import javax.ws.rs.core.MediaType;
/**
* Root resource (exposed at "myresource" path)
*/
@Path("myresource")
public class MyResource {
/**
* Method handling HTTP GET requests. The returned object will be sent
* to the client as "text/plain" media type.
*
* @return String that will be returned as a text/plain response.
*/
@GET
@Produces(MediaType.TEXT_PLAIN)
public String getIt() {
return "Got it!";
}
}
In this example, the resource:
-
Exposes a single resource method that is able to handle HTTP GET requests.
-
Is bound to
/myresourceURI path. -
Can produce responses with response message content represented in
text/plainmedia type. -
Returns the same "Got it!" response to all client requests.
RESTful web services rely on the following industry standards:
-
Web Application Description Language (WADL)—An XML-based language providing a model for describing RESTful web services.
-
WS-Policy—The WS-Policy framework provides a flexible and extensible grammar for describing the capabilities, requirements, and general characteristics of web services using policies.
1.2 Overview of Web Services in Oracle Fusion Middleware 12c
In Oracle Fusion Middleware 12c, two categories of web services exist: Oracle Infrastructure web services and Java EE web services.
Detailed description:
-
Oracle Infrastructure web services are SOA, Application Development Framework (ADF and Webcenter), Oracle Service Bus, and Oracle Enterprise Scheduler services
-
Java EE web services are SOAP (Java API for XML Web Services (JAX-WS)) and RESTful (JAX-RS) web services
The following figure illustrates the two web services categories.
Figure 1-2 Web Services in Oracle Fusion Middleware 12c
Description of "Figure 1-2 Web Services in Oracle Fusion Middleware 12c"
The following sections provide more detail about the Oracle Fusion Middleware 12c web services architecture and each of the web service components shown in the previous figure:
For a complete roadmap of all web service development, security, and administration tasks, see Roadmap for Implementing Oracle Infrastructure Web Services and Roadmap for Implementing Java EE (WebLogic) Web Services.
1.2.1 Types of Oracle Fusion Middleware Web Services and Clients
All web services and clients can be deployed to an Oracle Fusion Middleware environment that runs on Oracle WebLogic Server. Oracle WebLogic web services can be deployed to a standalone Oracle WebLogic Server, as well.
The following table summarizes the types of web services supported in Oracle Fusion Middleware 12c.
Table 1-2 Oracle Fusion Middleware Web Services
| Web Service | Description |
|---|---|
|
ADF Business Components (SOAP) |
ADF Business Components simplify the development, delivery, and customization of business applications for the Java EE platform by providing a library of reusable components and supporting design time facilities in Oracle JDeveloper. Using ADF Business Components, developers are not required to write the application infrastructure code required by the typical Java EE application to perform the following tasks:
Additionally, Oracle JDeveloper facilities expose ADF Business Component application modules that encapsulate built-in data manipulation operations and custom methods as web services so that a service-enabled application module can be consumed across modules of the deployed Fusion Web application. See Creating SOAP Web Services with Application Modules in Oracle Fusion Middleware Developing Fusion Web Applications with Oracle Application Development Framework. |
|
Oracle Enterprise Scheduler jobs |
Oracle Enterprise Scheduler supports web service jobs that use synchronous, one-way, and asynchronous interfaces. Both Oracle JDeveloper and Oracle Enterprise Manager offer convenient graphical user interfaces to help you create web service job definitions. When the web service job type is selected, a wizard leads the user through a simple set of steps to define the web service job. This wizard obtains the WSDL URL and asks the user to select the WSDL service, port type, and operation. The wizard populates a set of predefined system properties in the job definition with values entered or derived from what the user enters in the wizard. See Creating and Using Web Service Jobs in Oracle Fusion Middleware Developing Applications for Oracle Enterprise Scheduler. |
|
Java EE web service (SOAP and RESTful) |
SOAP Java EE web services are implemented according to the web services for Java EE specification, available at RESTful Java EE web services are implemented according to the JSR-339 JAX-RS 2.0 specification, defined at: For more information about developing SOAP and RESTful Java EE web services, see:
|
|
Oracle Service Bus proxy service (SOAP and RESTful) |
Oracle Service Bus provides intermediary services between service producers and service consumers to manage the routing and transformation of messages. Proxy services are definitions of those intermediary services that Oracle Service Bus implements locally and publishes to its clients. With Oracle Service Bus message brokering, service clients exchange messages with a proxy service rather than working directly with a service producer. For more information, see the following sections in Oracle Fusion Middleware Developing Services with Oracle Service Bus: JCA adapters enable you to integrate Oracle Service Bus business services with technologies such as databases and file systems. See How to Generate a Proxy Service form a JCA Binding Resource in Oracle Fusion Middleware Developing Services with Oracle Service Bus. |
|
SOA service binding components |
SOA Service binding components provide the outside world with an entry point to the SOA composite application. The WSDL file of the service advertises its capabilities to external applications. These capabilities are used for contacting the SOA composite application components. See Binding Components in Oracle Fusion Middleware Developing SOA Applications with Oracle SOA Suite. JCA adapters enable you to integrate SOA services with technologies such as databases and file systems. See JCA Adapters in Oracle Fusion Middleware Developing SOA Applications with Oracle SOA Suite. |
|
SOA service components (SOAP and RESTful) |
SOA composite applications include SOA service components. SOA service components are the basic building blocks of SOA applications, implementing a part of the overall business logic functionality. The following SOA service components can be managed using OWSM:
For more information about developing and securing SOA service components, see:
|
|
WebCenter services |
WebCenter services expose Web 2.0 technologies for social networking and personal productivity, such as Wiki, RSS, and blogs. WebCenter provides a set of features and services (for example, portlets, customization, and content integration) that you can selectively add to your application. For more information about integrating WebCenter services, see About Working with WebCenter Portal Assets in Oracle Fusion Middleware Developing for Oracle WebCenter Portal. |
The following table summarizes the types of web service clients supported in Oracle Fusion Middleware 12c.
Table 1-3 Oracle Fusion Middleware Web Service Clients
| Web Service Client | Description |
|---|---|
|
Oracle ADF Web applications (SOAP) |
ADF Web applications can invoke a service, such as a WebLogic web service, a SOA composite application, or a service-enabled ADF application module. In addition, ADF Web applications can work with web services in the user interface using a web service data control. For more information about generating service-enabled application modules, calling a web service from an ADF application module, or creating web service data controls. See Introduction to Building Fusion Web Applications with Oracle ADF in Oracle Fusion Middleware Developing Fusion Web Applications with Oracle Application Development Framework. |
|
Oracle Service Bus business services (SOAP and RESTful) |
Oracle Service Bus business services are definitions of the enterprise services that exchange messages during business processes, such as Web Services, JMS destinations, and EJBs. A business service invokes an external service producer once a message has been routed through Oracle Service Bus to the business service. For more information, see the following sections in Oracle Fusion Middleware Developing Services with Oracle Service Bus: JCA adapters enable you to integrate Oracle Service Bus business services with technologies such as databases and file systems. For more information, see How to Generate a Business Service form a JCA Binding Resource in Oracle Fusion Middleware Developing Services with Oracle Service Bus. |
|
Web service clients (SOAP and RESTful) |
Client applications that invoke Java EE web services can be written using any technology: Java, Microsoft.NET, and so on. There are two types of client applications:
For more information about developing WebLogic web service clients, see:
|
|
SOA reference binding components (SOAP and RESTful) |
SOA reference binding components connect the SOA composite application to external partners. For more information about developing and securing SOA reference binding components, see:
JCA adapters enable you to integrate SOA references with technologies such as databases and file systems. For more information, see "JCA Adapters" in Oracle Fusion Middleware Developing SOA Applications with Oracle SOA Suite. |
|
WebCenter portlets |
WebCenter portlets enable you to surface WebCenter services. For more information about developing WebCenter portlets, see About Portlet Development in Oracle Fusion Middleware Developing for Oracle WebCenter Portal. |
1.2.2 Types of Oracle Fusion Middleware Web Service Policies
Two types of policies can be attached to web services: Oracle Web Services Manager (OWSM) Policy and WebLogic Web Service Policy.
Table 1-4 table provides a brief description of supported policy types.
Table 1-4 Types of Web Service Policies
| Type of Policy | Description |
|---|---|
|
Oracle Web Services Manager (OWSM) Policy |
Policy provided by OWSM. For more information about OWSM and the predefined policies, see Introducing Oracle Web Services Manager in Oracle Fusion Middleware Understanding Oracle Web Services Manager. You can attach OWSM policies to Oracle Infrastructure web services. You can only attach OWSM security policies to Java EE JAX-WS and RESTful web services. You manage OWSM policies from Oracle Enterprise Manager Fusion Middleware Control. |
|
WebLogic Web Service Policy |
Policy provided by WebLogic Server. For more information about the WebLogic web service policies, see "Using Oracle Web Service Manager Security Policies" in Oracle Fusion Middleware Securing WebLogic Web Services for Oracle WebLogic Server. A subset of WebLogic web service policies interoperate with OWSM policies. For more information, see Interoperability with Oracle WebLogic Server 12c Web Service Security Environments in Oracle Fusion Middleware Interoperability Solutions Guide for Oracle Web Services Manager. You manage WebLogic web service policies from WebLogic Administration Console. |
Note:
It is recommended that you use OWSM policies over WebLogic web services whenever possible. You cannot mix your use of OWSM and WebLogic web service policies on the same web service.
1.2.3 Tools for Web Service Development, Security, and Administration
To develop Oracle Fusion Middleware web services, you can use tools such as Oracle JDeveloper, Ant, WebLogic Server Scripting Tool (WLST), Oracle Enterprise Pack for Eclipse (OEPE), Oracle Infrastructure Web Services, Java EE (WebLogic) Web Services, or you can use your preferred IDE.
Table 1-5 and Table 1-6 provide brief descriptions of supported tools for developing an Oracle Fusion Middleware web service.
Table 1-5 Tools for Web Service Development
| Tool | Description |
|---|---|
|
Oracle JDeveloper |
Provides powerful tools that help you discover and use existing web services, and develop and deploy new web services. See Developing and Securing Web Services in Oracle Fusion Middleware Developing Applications with Oracle JDeveloper. |
|
Ant |
Uses XML-based configuration files (called build.xml by default) to execute tasks written in Java. Ant is a Java-based build tool, similar to the make command but much more powerful. See Ant Task Reference in Oracle Fusion Middleware WebLogic Web Services Reference for Oracle WebLogic Server. |
|
WebLogic Server Scripting Tool (WLST) |
Enables administrators to view and configure web services, and manage web service policies from the command line. See WebLogic Server WLST Online and Offline Command Reference in Oracle Fusion Middleware WLST Command Reference for Oracle WebLogic Server. |
|
Oracle Enterprise Pack for Eclipse (OEPE) |
Provides a collection of plug-ins to the Eclipse IDE platform that facilitate development of WebLogic web services. For more information, see the Eclipse IDE platform online help. |
To secure and administer web services, the tools that you use vary depending on the web service type.
Table 1-6 Tools for Web Service Security and Administration
| To secure and administer | Use |
|---|---|
|
Oracle Infrastructure Web Services |
|
|
Java EE (WebLogic) Web Services |
|
1.3 Roadmap for Implementing Oracle Infrastructure Web Services
Roadmaps provide lists of common tasks for developing, securing, and administering Oracle Fusion Middleware web services, with links to detailed information.
This section contains the following roadmaps in table form:
1.3.1 Roadmap for Implementing ADF Components and Clients
This topic describes the roadmap for implementing ADF components and clients.
Implement web services for ADF components and clients as follows:
Table 1-7 Roadmap for Implementing ADF Components and Clients
| Task | More Information |
|---|---|
|
Develop ADF components and clients |
|
|
Deploy web services |
|
|
Administer web services |
Overview of Web Services Administration Using Fusion Middleware Control and Overview of Web Services Administration Using WLST in Oracle Fusion Middleware Administering Web Services. |
|
Create policies |
Managing Web Service Policies with Fusion Middleware Control in Oracle Fusion Middleware Securing Web Services and Managing Policies with Oracle Web Services Manager. |
|
Create custom assertions |
Creating Custom Assertions in Oracle Fusion Middleware Developing Extensible Applications for Oracle Web Services Manager. |
|
Attach policies (development time—Oracle JDeveloper) |
Defining ADF Security Policies in Oracle Fusion Middleware Developing Fusion Web Applications with Oracle Application Development Framework. |
|
Attach policies (deployment time—Oracle Enterprise Manager Fusion Middleware Control) |
"Attaching Policies in Oracle Fusion Middleware Securing Web Services and Managing Policies with Oracle Web Services Manager. |
|
Configure policies |
"Securing Web Services" in Oracle Fusion Middleware Securing Web Services and Managing Policies with Oracle Web Services Manager. |
|
Test web services |
"Testing Web Services" in Oracle Fusion Middleware Administering Web Services. |
|
Monitor web service performance |
"Monitoring and Auditing Web Services" in Oracle Fusion Middleware Administering Web Services. |
|
Manage application migration between environments |
"Managing Application Migration Between Environments" in Oracle Fusion Middleware Administering Web Services. |
|
Diagnose problems |
"Managing Diagnostic and Message Logs" in Oracle Fusion Middleware Administering Web Services. |
|
Interoperate with other security environments |
OWSM Interoperability Scenarios in Oracle Fusion Middleware Interoperability Solutions Guide for Oracle Web Services Manager. |
1.3.2 Roadmap for Implementing Oracle Enterprise Scheduler Service Jobs
This topic explains the roadmap for implementing Oracle Enterprise Scheduler Service Jobs.
Implement Oracle Enterprise Scheduler web service jobs as follows:
Table 1-8 Roadmap for Implementing Oracle Enterprise Scheduler Service Jobs
| Task | More Information |
|---|---|
|
Planning Job Development |
Planning Job Development in Oracle Fusion Middleware Developing Applications for Oracle Enterprise Scheduler. |
|
Develop Oracle Enterprise Scheduler jobs |
Creating and Using Web Service Jobs in Oracle Fusion Middleware Developing Applications for Oracle Enterprise Scheduler. |
|
Administer Oracle Enterprise Scheduler jobs |
Using Oracle Enterprise Manager to Create a Job Definition in Oracle Fusion Middleware Developing Applications for Oracle Enterprise Scheduler. |
|
Create policies |
Managing Web Service Policies with Fusion Middleware Control in Oracle Fusion Middleware Securing Web Services and Managing Policies with Oracle Web Services Manager. |
|
Create custom assertions |
Creating Custom Assertions in Oracle Fusion Middleware Developing Extensible Applications for Oracle Web Services Manager. |
|
Attach policies (development time—Oracle JDeveloper) |
Using Oracle JDeveloper to Create a Job Definition in Oracle Fusion Middleware Developing Applications for Oracle Enterprise Scheduler. |
|
Attach policies (deployment time—Oracle Enterprise Manager Fusion Middleware Control) |
|
|
Configure policies |
|
|
Diagnose problems |
Managing Diagnostic and Message Logs in Oracle Fusion Middleware Administering Web Services. |
|
Interoperate with other security environments |
OWSM Interoperability Scenarios in Oracle Fusion Middleware Interoperability Solutions Guide for Oracle Web Services Manager. |
1.3.3 Roadmap for Implementing Oracle Service Bus Services and Clients
This topic explains the roadmap for Implementing Oracle Service Bus Services and Clients.
Implement web services for Oracle Service Bus Services and Clients as follows:
Table 1-9 Roadmap for Implementing Oracle Service Bus Services and Clients
| Task | More Information |
|---|---|
|
Develop Oracle Service Bus web services and clients |
|
|
Deploy web services |
Deploying Oracle Service Bus Services in Oracle Fusion Middleware Developing Services with Oracle Service Bus. |
|
Administer web services |
|
|
Create policies |
Managing Web Service Policies with Fusion Middleware Control in Oracle Fusion Middleware Securing Web Services and Managing Policies with Oracle Web Services Manager. |
|
Create custom assertions |
Creating Custom Assertions in Oracle Fusion Middleware Developing Extensible Applications for Oracle Web Services Manager. |
|
Attach policies (development time—Oracle JDeveloper) |
|
|
Attach policies (development or deployment time—Oracle Service Bus Console) |
|
|
Attach policies (deployment time—Oracle Enterprise Manager Fusion Middleware Control) |
Managing Security Policies in Oracle Fusion Middleware Administering Oracle Service Bus. |
|
Configure policies |
|
|
Test web services |
|
|
Monitor web service performance |
|
|
Manage application migration between environments |
Managing Application Migration Between Environments in Oracle Fusion Middleware Administering Web Services. |
|
Diagnose problems |
|
|
Interoperate with other security environments |
OWSM Interoperability Scenarios in Oracle Fusion Middleware Interoperability Solutions Guide for Oracle Web Services Manager. |
1.3.4 Roadmap for Implementing SOA Composite Services and Clients
This topic explains the roadmap for implementing SOA Composite Services and Clients.
Implement web services for SOA composite services and clients as follows:
Table 1-10 Roadmap for Implementing SOA Composite Services and Clients
| Task | More Information |
|---|---|
|
Develop SOA composite web services and clients |
|
|
Deploy web services |
|
|
Administer web services |
|
|
Create policies |
"Managing Web Service Policies with Fusion Middleware Control" in Securing Web Services and Managing Policies with Oracle Web Services Manager |
|
Create custom assertions |
Creating Custom Assertions in Extensibility Solutions Guide for Oracle Web Services Manager |
|
Attach policies (development time—Oracle JDeveloper) |
"Enabling Security with Policies and Message Encryption in Developing SOA Applications with Oracle SOA Suite |
|
Attach policies (deployment time—Oracle Enterprise Manager Fusion Middleware Control) |
|
|
Configure policies |
"Securing Web Services" in Securing Web Services and Managing Policies with Oracle Web Services Manager |
|
Test web services |
"Testing Web Services" in Administering Web Services |
|
Monitor web service performance |
|
|
Manage application migration between environments |
"Managing Application Migration Between Environments" in Administering Web Services |
|
Diagnose problems |
"Managing Diagnostic and Message Logs" in Administering Web Services |
|
Interoperate with other security environments |
1.3.5 Roadmap for Implementing WebCenter Services and Clients
This topic explains the roadmap for implementing WebCenter Services and Clients.
Implement web services for WebCenter services and clients as follows:
Table 1-11 Roadmap for Implementing WebCenter Services and Clients
| Task | More Information |
|---|---|
|
Develop WebCenter services and clients |
|
|
Deploy WebCenter services |
|
|
Administer WebCenter services |
|
|
Create policies |
|
|
Create custom assertions |
Creating Custom Assertions in Extensibility Solutions Guide for Oracle Web Services Manager |
|
Attach policies (deployment time—Oracle Enterprise Manager Fusion Middleware Control) |
|
|
Configure policies |
|
|
Test WebCenter services |
Testing WebCenter Portal Assets in Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper |
|
Monitor WebCenter service performance |
Performance Monitoring and Diagnostics in Administering Oracle WebCenter Portal |
|
Manage application migration between environments |
Managing Application Migration Between Environments in Administering Web Services |
|
Diagnose problems |
Introduction to Diagnosing Problems Using Logs in Administering Web Services |
|
Interoperate with:
|
OWSM Interoperability Scenarios in Interoperability Guide for Oracle Web Services Manager. |
1.4 Roadmap for Implementing Java EE (WebLogic) Web Services
This section lists common tasks for developing, securing, and administering Java EE (WebLogic) web services, and provides links to detailed information.
Following table provides links to detailed information for common Java EE (WebLogic) Web Services:
Table 1-12 Roadmap for Implementing Java EE (WebLogic) Web Services
| Task | More Information |
|---|---|
|
Develop Java EE web services and clients |
|
|
Deploy web services |
|
|
Administer web services |
Web Services in WebLogic Server Administration Console Online Help. |
|
Create OWSM policies |
Managing Web Service Policies with Fusion Middleware Control in Oracle Fusion Middleware Securing Web Services and Managing Policies with Oracle Web Services Manager. |
|
Create WebLogic web service policies |
|
|
Configure OWSM policies |
"Securing Web Services" in Securing Web Services and Managing Policies with Oracle Web Services Manager |
|
Configure WebLogic web service policies |
|
|
Create custom OWSM policy file |
Creating Custom Assertions in Developing Extensible Applications with Oracle Web Services Manager |
|
Create custom WebLogic web service policy file |
Creating and Using a Custom Policy File in Oracle Fusion Middleware Securing WebLogic Web Services for Oracle WebLogic Server. |
|
Attach OWSM policies (development time—Oracle JDeveloper) |
|
|
Attach WebLogic web service policies (development time—Oracle JDeveloper) |
|
|
Attach OWSM policies (deployment time) |
Attaching Policies in Oracle Fusion Middleware Securing Web Services and Managing Policies with Oracle Web Services Manager |
|
Attach WebLogic web service policies (deployment time) |
Associate a WS-Policy file with a Web Service in WebLogic Server Administration Console Online Help |
|
Test web services |
|
|
Monitor web service performance |
|
|
Interoperate WebLogic and OWSM web service policies |
OWSM Interoperability Scenarios in Oracle Fusion Middleware Interoperability Solutions Guide for Oracle Web Services Manager. |