Network Deployment (Distributed operating systems), v8.0 > Reference > Commands (wsadmin scripting)
Policy configuration properties for all policies
We can use the attributes parameter with the setPolicyType and setBinding commands to specify various properties for each quality of service (QoS) within a policy set. We can use the properties in this topic with each QoS within application and system policy sets.
Use the following commands and parameters in the PolicySetManagement group of the AdminTask object to customize your policy set configuration.
- Use the -attributes parameter for the getPolicyType and getBinding commands to view the properties for your policy and binding configuration.
To get an attribute, pass the property name to the getPolicyType or getBinding command.
- Use the -attributes parameter for the setPolicyType and setBinding commands to add, update, or remove properties from your policy and binding configurations.
To add or update an attribute, specify the property name and value. The setPolicyType and setBinding commands update the value if the attribute exists, or adds the attribute and value if the attribute does not exist.
To remove an attribute, specify the value as an empty string (""). The -attributes parameter accepts a properties object.
If a property name or value supplied with the -attributes parameter is not valid, then the setPolicyType and setBinding commands fail with an exception. The property that is not valid is logged as an error or warning in the SystemOut.log file. However, the command exception might not contain the detailed information for the property that caused the exception. When the setPolicyType and setBinding commands fail, examine the SystemOut.log file for any error and warning messages that indicate that the input for the -attributes parameter contains one or multiple properties that are not valid.
New feature: Beginning in WAS v8.0 you can configure the server to use the HPEL log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.New feature:
Before you use the commands in this topic, verify that you are using the most recent version of wsadmin.sh. The policy set management commands that accept a properties object as the value for the attributes or bindingLocation parameters are not supported on previous versions of wsadmin.sh. For example, the commands do not run on a v6.1.0.x node.
Attributes to configure for all QoS policies
Use the following list of attributes to configure attributes across all QoS policies using Jython and wsadmin.sh:
enabled
Whether the policy type is enabled or disabled. The following example provides the format to enter the attributes parameter:
-attributes "[[enabled true]]"
provides
Provides a description for the configuration. The following example provides the format to enter the attributes parameter:
-attributes "[[provides [Messaging Security]]]"Use the setPolicyType command to set the enabled and provides properties for the myCustomSecurityPS custom policy set, which contains a ReliableMessaging policy:
AdminTask.setPolicyType('[-policySet myCustomSecurityPS -policyType WSReliableMessaging -attributes [[enabled true][provides [Messaging security]]]]')
Web services policies
Configure application and system policy sets for web services using wsadmin.sh
Configure a WS-Transaction policy set using wsadmin.sh
Use HPEL to troubleshoot applications
Related
PolicySetManagement command group
WSSecurity policy and binding properties
WSAddressing policy and binding properties
SSLTransport policy and binding properties
HTTPTransport policy and binding properties
WSReliableMessaging policy and binding properties