Configure application and system policy sets for web services using wsadmin scripting

Use the wsadmin tool, which supports the Jython and Jacl scripting languages, to configure application or system policy sets for web services. We can manage the policies for the Quality of Service (QoS) by creating policy sets and managing associated policies.

Develop a web services application. For additional information, see the web services applications topics in the information center.

If we develop an application that uses a custom policy set, the custom policy set configuration is not included in the application EAR file. Install the application and import the custom policy set separately.

The commands in the PolicySetManagement group for the AdminTask object configure both application and system policy sets. Use the following tasks to configure and manage policy sets for our web services.

For transitioning users: In WAS v7.0 and later, the security model was enhanced to a domain-centric security model instead of a server-based security model. The configuration of the default global security (cell) level and default server level bindings has also changed in this version of the product. In the WAS v6.1 Feature Pack for Web Services, we can configure one set of default bindings for the cell and optionally configure one set of default bindings for each server. In v7.0 and later, we can configure one or more general service provider bindings and one or more general service client bindings. After we have configured general bindings, we can specify which of these bindings is the global default binding. We can also optionally specify general binding used as the default for an application server or a security domain. trns

To support a mixed-cell environment, WAS supports v7.0 and v6.1 bindings. General cell-level bindings are specific to v7.0 and later Application-specific bindings remain at the version that the application requires. When the user creates an application-specific binding, the application server determines the required binding version to use for application.

Use the following guidelines to manage bindings in the environment:

• To display or modify default v6.1 bindings, v7.0 and trust service bindings, or to reference bindings by attachment for an application, specify the attachmentId and bindingLocation parameters with the getBinding or setBinding commands.

• To use or modify general v7.0 and later bindings, specify the bindingName parameter with the getBinding or setBinding commands.

• To display the version of a specific binding, specify the version attribute for the getBinding command.

Use a v6.1 binding for an application in a v7.0 and later environment if:

• The module in the application is installed on at least one Web Services Feature Pack server.

• The application contains at least one v6.1 application-specific binding. The application server does not assign general bindings to resource attachments for applications installed on a Web Services Feature Pack server. All application-specific bindings for an application must be at the same level.

General service provider and client bindings are not linked to a particular policy set and they provide configuration information that we can reuse across multiple applications. Create and manage general provider and client policy set bindings and then select one of each binding type to use as the default for an application server. Setting the server default bindings is useful if we want the services deployed to a server to share binding configuration. We can also accomplish this sharing of binding configuration by assigning the binding to each application deployed to the server or by setting default bindings for a security domain and assigning the security domain to one or more servers. We can specify default bindings for our service provider or client used at the global security (cell) level, for a security domain, for a particular server. The default bindings are used in the absence of an overriding binding specified at a reduced scope. The order of precedence from lowest to highest that the application server uses to determine which default bindings to use is as follows:

1. Server level default
2. Security domain level default
3. Global security (cell) default

The sample general bindings provided with the product are initially set as the global security (cell) default bindings. The default service provider binding and the default service client bindings are used when no application specific bindings or trust service bindings are assigned to a policy set attachment. For trust service attachments, the default bindings are used when no trust specific bindings are assigned. If we do not want to use the provided Provider sample as the default service provider binding, we can select an existing general provider binding or create a new general provider binding to meet the business needs. Likewise, if we do not want to use the provided Client sample as the default service client binding, we can select an existing general client binding or create a new general client binding.

Tasks

• Use the PolicySetManagement group of commands to configure application and client policy sets:
  • Create a new policy set or copy an existing policy set.
  • Add policies to your policy set.
  • Attach your policy set to an application, web service, endpoint, or operation.
  • Customize cell-wide, server-specific, or application binding configurations.
  • Manage and edit your policy set configurations.
    • Edit, enable, disable, or remove policies.
    • Add, edit, or remove policy set attachments.
    • Export and import policy sets.
    • Delete policy sets.

• Use the PolicySetManagement group of commands to configure system policy sets.
  • Create a new system policy set or copy an existing system policy set.
  • Add policy types for your policy set.
  • Add trust service attachments.
  • Customize binding configurations.
  • Manage and edit your policy set configurations.
    • Edit, enable, disable or remove policies.
    • Add, edit, or remove policy set attachments.
    • Export and import policy sets.
    • Delete policy sets.

Subtopics

1. Create policy sets
   
2. Update policy set attributes
   
3. Add and remove policies
   
4. Edit policy configurations
   
5. Enable secure conversation
   
6. Manage WS-Security distributed cache configurations
   
7. Configure custom policies and bindings for security tokens
   
8. Create policy set attachments
   
9. List policy sets available for attachment
   
10. Manage policy set attachments
    
11. Manage policy set attachments for service references
    
12. Configure general, cell-wide bindings for policies
    
13. Configure v6.1 server-specific default bindings for policies
    
14. Configure application-specific and system bindings
    
15. Create application-specific and trust service-specific bindings
    
16. Delete application-specific bindings from the configuration
    
17. Import and export policy sets to client or server environments
    
18. Remove policy set bindings
    
19. Remove policy set attachments
    
20. Delete policy sets
    
21. Refresh policy set configurations
    
22. Policy configuration properties for all policies
    
23. WSSecurity policy and binding properties
    
24. WSReliableMessaging policy and binding properties
    
25. WSAddressing policy and binding properties
    
26. SSLTransport policy and binding properties
    
27. HTTPTransport policy and binding properties
    
28. JMSTransport policy and binding properties
    
29. CustomProperties policy and binding properties
    
30. SecureConversation .(Deprecated)
    
31. WSSCacheManagement
    
32. PolicySetManagement
    
33. WS-Policy commands for the AdminTask object
    

Manage policy sets