Qualities of service - Web services policy sets
IBM® WebSphere® Application Server V7 Feature Pack for Service Component Architecture Quality of service - Web service policy sets
This presentation covers the Web service policy set feature of the Quality of service for the SCA feature pack.
Web services policy sets
Web services policy sets Used to simplify configuring the qualities of service for Web services Create policy set bindings that might be required to configure the policy sets Developer specifies the intents required for a service/reference using annotations or the requires attribute in the composite file. Attach the policy set and policy set binding In the composite file using "wsPolicySet", "wsServicePolicySetBindings", "wsReferencePolicySetBindings" Assign/update policy set during the deployment process in the Policy set attachment panel
You can use policy sets to simplify configuring the qualities of service for Web services and clients. These policy sets are assertions about how Web services are defined and they are defined in WebSphere Application Server. WebSphere Application Server ships several default policy sets and a few more in the repository, which can be imported, or you can create new policy sets. You can also create any policy set bindings that might be required to configure the policy sets. A developer can specify the intents required for a service/reference using annotations or the requires attribute in the composite file, which are mapped to policy sets during deployment by the deployer. The policy set and policy set binding to be attached can be configured in several ways. You can specify them in the composite file using "wsPolicySet", "wsServicePolicySetBindings", and "wsReferencePolicySetBindings“, they can be assigned or updated during the deployment process in the Policy set attachment panel, or they can be assigned or updated after deployment using the Web services administrative functionality.
Web services policy set integration
Web services policy set integration locate Web service binding Web service binding WebSphere Web services policy sets Composite Component Service Reference @requires=“confidentiality.message” Policies WS-Security default
Shown here is a quality of service picture with an emphasis on the Web service binding.
Policy set attachment within composite
Policy set attachment within composite A component service or reference can be configured to require a specific Web service policy set
As shown here, a component service or reference can be configured to require a specific Web service policy set. This particular example shows configuration to support LTPA authentication. Attaching the LTPA WSSecurity default policy set to a reference will by default propagate any existing LTPA tokens on the thread with the request. It is also possible to configure the policy set to create a token for a specific user and send that token with all requests. You can reference the Information Center for more details about the LTPA WSSecurity default policy set. * The QoS namespace must be defined in the composite definition xmlns:qos="http://www.ibm.com/xmlns/prod/websphere/sca/1.0/2007/06"
Attachment through wsadmin
Attachment through wsadmin During SCA deployment Web services policy sets can be attached to the SCA services and references that have a Web service binding
When an SCA application is deployed, Web services policy and policy binding can be attached to the SCA services and references that have a Web service binding. One way to do this is through wsadmin scripting as shown here. The other option is through the administrative console.
Transport layer authentication
Transport layer authentication A component service can be configured for transport authentication by specifying the "authentication.transport" intent on the element. Transport layer authentication does not require a policy set
A component service can be configured for transport authentication by specifying the "authentication.transport" intent on the element as shown. Transport layer authentication does not require a policy set.
Security policy example – SCA intent
Security policy example – SCA intent intent
This example shows an SCA security policy intent (authentication) specified in a service, which is the first step. The next step is to map the intent to the policy set, which can be done through code or through the administrative console.
Security policy example – Map to policy set
Security policy example – Map to policy set Attach policyset
This example shows how the intent is mapped to the policy set on the administrative console using the “Attach” button
Security policy example – Service providers
Security policy example – Service providers
You can also see from the service providers the policy set that was attached to the service component.
Summary
Summary Web service policy sets are used to simplify configuring the qualities of service for Web services
Web service policy sets are used to simplify configuring the qualities of service for Web services. The following appendix contains lists of supported intents.
Appendix
Appendix Section
Intents supported by each binding
Intents supported by each binding Intent binding.ws binding.ejb binding.sca authentication.message Requires the attachment of a WebSphere policy set and policy binding that contains the WSSecurity policy type Not supported; CSIv2 can be configured to use basic auth and security token (LTPA, Kerberos) confidentiality.message integrity.message Requires the attachment of a WebSphere policy set and policy binding that contains the Security policy type Not supported
Intents supported by each binding.
Intents supported by each binding
Intents supported by each binding Intent binding.ws binding.ejb binding.sca authentication.transport Basic auth only. Reference requires the attachment of a WebSphere policy set that contains the HTTPTransport policy type. Service does not require any attachments. Intent is not supported. CSIv2 can be configured to use client certificates for authentication. confidentiality.transport integrity.transport Requires the attachment of a WebSphere policy set that contains the SSLTransport policy type Intent is not supported. CSIv2 can be configured to require SSL.
Intents supported by each binding
Intents supported by each binding Intent binding.ws propagatesTransaction Requires the attachment of a Web services policy set that contains the WSTransaction policy type
References
References SCA specifications http://www.osoa.org/display/Main/Service+Component+Architecture+Specifications SCA policy framework http://www.osoa.org/download/attachments/35/SCA_Policy_Framework_V100.pdf?version=1
Feedback
Feedback Your feedback is valuable You can help improve the quality of IBM Education Assistant content to better meet your needs by providing feedback. Did you find this module useful? Did it help you solve a problem or answer a question? Do you have suggestions for improvements? Click to send e-mail feedback: mailto:iea@us.ibm.com?subject=Feedback_about_WASv7SCA_QOS_Webservicepolicyset.ppt This module is also available in PDF format at: ../WASv7SCA_QOS_Webservicepolicyset.pdf
You can help improve the quality of IBM Education Assistant content by providing feedback on this module.
Trademarks