Network Deployment (Distributed operating systems), v8.0 > Scripting the application serving environment (wsadmin) > Welcome to scripting for web services > Configure web services applications
Configure application and system policy sets for web services
Overview
Use wsadmin.sh to configure application or system policy sets for web services.
If you 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 configure both application and system policy sets. Use the following tasks to configure and manage policy sets for your 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, you 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, you can configure one or more general service provider bindings and one or more general service client bindings. After we have configured general bindings, you can specify which of these bindings is the global default binding. We can also optionally specify general binding that are 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 that are 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 you can reuse across multiple applications. We can 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 you want the services that are 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 your service provider or client that are 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 lower scope. The order of precedence from lowest to highest that the application server uses to determine which default bindings to use is as follows:
- Server level default
- Security domain level default
- Global security (cell) default
The sample general bindings that are 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 you do not want to use the provided Provider sample as the default service provider binding, you can select an existing general provider binding or create a new general provider binding to meet your business needs. Likewise, if you do not want to use the provided Client sample as the default service client binding, you can select an existing general client binding or create a new general client binding.
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.
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.
Related
Create policy sets
Update policy set attributes
Add and remove policies
Edit policy configurations
Enable secure conversation
Manage WS-Security distributed cache configurations
Configure custom policies and bindings for security tokens
Create policy set attachments
Manage policy set attachments
Configure general, cell-wide bindings for policies
Configure v6.1 server-specific default bindings for policies
Configure application-specific and system bindings
Create application-specific and trust service-specific bindings
Delete application-specific bindings from the configuration
Import and exporting policy sets to client or server environments
Remove policy set bindings
Remove policy set attachments
Delete policy sets
Refresh policy set configurations
Policy configuration properties for all policies
WSSecurity policy and binding properties
WSReliableMessaging policy and binding properties
WSAddressing policy and binding properties
SSLTransport policy and binding properties
HTTPTransport policy and binding properties
JMSTransport policy and binding properties
SecureConversation command group (Deprecated)
WSSCacheManagement command group
PolicySetManagement command group
WS-Policy commands
Manage policy sets
Configure secure sessions between clients and services
Configure a service provider to share its policy configuration
Configure the client.policy to use a service provider policy