Description of Functionality Click Log In.

Examining the Rearchitecture of Oracle WSM in Oracle Fusion Middleware 4-3 Figure 4–1 Oracle WSM 10g Components Figure 4–2 shows the Oracle Fusion Middleware 11g Release 1 11.1.1 components, and the numbers in Table 4–1 correspond to the components in the figure. Figure 4–2 Oracle Fusion Middleware 11g Web Services Security Components Comparing Oracle WSM 10g and Oracle WSM 11g Policies In both Oracle WSM 10g and Oracle WSM 11g, policies are used to enforce security. However, the structure of the policies is somewhat different. In Oracle WSM 10g a policy consists of a Request Pipeline and a Response Pipeline, each comprised of one or more policy steps. For example, in Figure 4–3 , the Request Pipeline consists of the following policy steps: Extract Credentials, LDAP Authenticate, and LDAP Authorize. The Response Pipeline contains a different policy step, XML Encrypt. The Request Pipeline and Response Pipelines can be comprised of different policy steps, and, therefore, different behaviors can be executed in the request and response messages. 4-4 Oracle Fusion Middleware Security and Administrators Guide for Web Services Figure 4–3 Oracle WSM 10g Policy Pipeline In Oracle WSM 11g, policies are comprised of one or more assertions, and you control the assertions that are used in the request and response messages. For example, in Figure 4–4 , the example 11g policy contains two assertions: 1. wss11-username-with-certificates 2. binding-authorization Figure 4–4 Oracle WSM 11g Policy Pipeline When the request message is sent to the Web service, the assertions are executed in the order shown. When the response message is returned to the client, the same assertions are executed, but this time in reverse order. The behavior of the assertion for the request message differs from the behavior for the response message. And, in some instances, it is possible that nothing happens on the response. For example, in the example above, the authorization assertion is only executed as part of the request. For information about how the Oracle WSM 10.1.3 policy steps can be mapped to Oracle WSM 11g predefined policies, see Upgrading Oracle Web Services Manager Policies in Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF Release 11g. Comparing Oracle Application Server 10g WS-Security with Oracle WSM 11g The following list identifies the primary enhancements to Oracle WSM 11g over Oracle Application Server 10g WS-Security: ■ Centralized policy management. Using the Oracle WSM Policy Manager, you centrally define security and management policies. ■ Custom policy support. You can create custom policies that support your security and management policy requirements, if the predefined policies do not meet your needs. ■ Toolset used to manage and attach policies. Security administrators can use Oracle Enterprise Manager Fusion Middleware Control to manage and attach Web services. Developers can attach security policies at development time, using Oracle JDeveloper or other IDE. ■ Policies managed at the enterprise level. Policies are defined at the enterprise level and not at the application level. Examining the Rearchitecture of Oracle WSM in Oracle Fusion Middleware 4-5 Interoperability and Upgrade Oracle WSM 11g can interoperate with the following 10.1.3 components: ■ Oracle WSM, as described in Interoperability with Oracle WSM 10g Security Environments in Interoperability Guide for Oracle Web Services Manager. ■ Oracle WSM gateways, as described in Interoperability with Oracle WSM 10g Security Environments in Interoperability Guide for Oracle Web Services Manager. ■ Application Server, as described in Interoperability with Oracle Containers for J2EE OC4J 10g Security Environments in Interoperability Guide for Oracle Web Services Manager. In addition, you can interoperate with the following components: ■ WebLogic Web services, as described Interoperability with Oracle WebLogic Server 11g Web Service Security Environments in Interoperability Guide for Oracle Web Services Manager. ■ Microsoft .NET, as described in Interoperability with Microsoft WCF.NET 3.5 Security Environments in Interoperability Guide for Oracle Web Services Manager. ■ Oracle Service Bus, as described in Interoperability with Oracle Service Bus 10g Security Environments in Interoperability Guide for Oracle Web Services Manager. ■ Axis 1.4 and WSS4J 1.58, as described in Interoperability with Axis 1.4 and WSS4J 1.58 Security Environments in Interoperability Guide for Oracle Web Services Manager. You can upgrade the following 10.1.3 features to Oracle Fusion Middleware 11g Release 1 11.1.1: ■ OC4J Web services 10.1.3 to WebLogic Web services. See Upgrading Your Java EE Applications in Oracle Fusion Middleware Upgrade Guide for Java EE Release 11g. ■ Oracle WSM 10.1.3 policies to Oracle WSM 11g . See Upgrading Oracle Web Services Manager WSM Policies in Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF Release 11g. ■ Oracle Containers for Java OC4J 10.1.3 security environments to OWSM 11g. See Upgrading Oracle Containers for J2EE OC4J Security Environments in Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF Release 11g. 4-6 Oracle Fusion Middleware Security and Administrators Guide for Web Services Part II Part II Basic Administration Part II contains the following chapters: ■ Chapter 5, Deploying Web Services Applications ■ Chapter 6, Administering Web Services ■ Chapter 7, Managing Web Service Policies ■ Chapter 8, Attaching Policies to Web Services ■ Chapter 9, Creating and Managing Policy Sets ■ Chapter 10, Setting Up Your Environment for Policies ■ Chapter 11, Configuring Policies ■ Chapter 12, Testing Web Services ■ Chapter 13, Monitoring the Performance of Web Services 5 Deploying Web Services Applications 5-1 5 Deploying Web Services Applications This chapter contains the following sections: ■ Overview ■ Deploying Web Services Applications ■ Redeploying a Web Services Application ■ Undeploying a Web Services Application Overview As you work with Web services, you will find that you can deploy and undeploy their associated applications in different ways. Follow these guidelines when deploying applications associated with Web services: ■ Use Oracle Enterprise Manager Fusion Middleware Control to deploy Java EE applications that require Oracle Metadata Services MDS or that take advantage of the Oracle Application Development Framework Oracle ADF. ■ If your application is a SOA composite, use the SOA Composite deployment wizard. ■ If your application is a WebCenter application, use Oracle Enterprise Manager Fusion Middleware Control. ■ If your application is not a SOA composite or it does not require an MDS repository or ADF connections, then you can deploy your application using Fusion Middleware Control or the Oracle WebLogic Server Administration Console. Additional Deployment Documentation Available This chapter provides an overview of the basic procedure for deploying a Web service application. For more information about deploying applications, see Deploying Applications in Oracle Fusion Middleware Administrators Guide. In particular, take note of the following sections: ■ Deploying, Undeploying, and Redeploying Java EE Applications ■ Deploying, Undeploying, and Redeploying Oracle ADF Applications ■ Deploying, Undeploying, and Redeploying SOA Composite Applications Note: To deploy WebLogic Web services, use only the Oracle WebLogic Administration Console. 5-2 Oracle Fusion Middleware Security and Administrators Guide for Web Services ■ Deploying, Undeploying, and Redeploying WebCenter Applications Deploying Web Services Applications The following is an overview of the basic procedure for deploying a Web service application using the Oracle Enterprise Manager Fusion Middleware Control. To deploy a Web services application 1. From the navigation pane, expand WebLogic Domain. 2. Expand the domain in which you want to deploy the Web service, and then select the instance of the server on which you want to deploy it.

3. Using Fusion Middleware Control, click WebLogic Server.

4. Select Application Deployment, and then select Deploy.

The first screen of the Deploy process is displayed, as shown in Figure 5–1 . Figure 5–1 Select Archive Page

5. Click on one of the following Archive or Exploded Directory options:

■ Archive is on the machine where this web browser is running. ■ Archive or exploded directory is on the server where Enterprise Manager is running.

6. A deployment plan is an XML file that you use to configure an application for

deployment to a specific environment. If you do not already have a deployment plan for the Web services application you are deploying, one is created for you when you deploy the application. Click one of the following Deployment Plan options: ■ Automatically create a new deployment plan ■ Deployment plan is present on local host Deploying Web Services Applications 5-3 ■ Deployment plan is already present on the server where Enterprise Manager is running

7. Click Next.

8. On the Select Target page, select the target WebLogic server or cluster to which you want this application deployed, and click Next. Figure 5–2 Select Target Page 9. On the Application Attributes page, enter the attributes for this Web services application, and click Next. Application Name is the only required attribute. However, if you want to be able to later redeploy this Web service application without first having to undeploy it, you must also assign a version number. The context root is the URI for the web module. Each web module or EJB module that contains web services may have a context root. Figure 5–3 Application Attributes Page 5-4 Oracle Fusion Middleware Security and Administrators Guide for Web Services 10. On the Deployment Settings page, edit the deployment settings for this Web services application, as shown in Figure 5–4 . Figure 5–4 Deployment Settings Page

11. To save a copy of the deployment plan to your local system, click Save

Deployment Plan .

12. To edit the deployment plan, possibly to add advanced deployment options, click

Edit Deployment Plan . If you do so, the Edit Deployment Plan screen is displayed, as shown in Figure 5–5 . After making changes to the deployment plan, click Apply to make the change effective. Figure 5–5 Edit Deployment Plan

13. Click Deploy on the Deployment Settings page. If successful, the Deployment

Succeeded screen is displayed.