CWPST

CWPST0001E: The system created an exception: {0}
CWPST0002E: The system created an exception: {0}
CWPST0003E: The command created an exception: {0}
CWPST0004E: The {0} default policy set cannot be edited.
CWPST0005E: The {0} policy set cannot be deleted. It is attached to the following applications: {1}
CWPST0006E: The command could not be validated.
CWPST0007E: The command created an exception: {0}
CWPST0008E: The cell repository context cannot be found.
CWPST0009E: Multiple cell repository contexts are found.
CWPST0011E: The following resources are not valid: {0}
CWPST0013E: The following resources are already attached to the application: {0}
CWPST0014E: The servicesIndex.xml file could not be located for the {0} application and module.
CWPST0015E: A resource was specified as empty or null.
CWPST0016E: The following directory path is not writable: {0}
CWPST0017E: The {0} path name did not contain the {1} string.
CWPST0018E: Policy set {0} cannot be deleted because it is still attached
CWPST0019E: The following directory path is not a directory: {0}
CWPST0020E: The following directory path does not exist: {0}
CWPST0021E: The following policy set directory does not contain any files: {0}
CWPST0022E: The {0} output file name exists in the configuration.
CWPST0023E: The {0} output file name is a directory.
CWPST0024E: The {0} output file name does not contain any file separator slashes.
CWPST0025E: The following list of policy types are not valid: {0}
CWPST0026E: The {0} policy set name contains characters that are not valid.
CWPST0027E: The system is unable to initialize the PolicySetManager MBean: {0}
CWPST0028E: The system could not validate a policy type within a policy set: {0}
CWPST0029E: The {1} parameter cannot be used if the {0} parameter is specified.
CWPST0030E: The {0} input argument must also be specified with the {1} input argument.
CWPST0031E: The {0} policy attachment file was not found.
CWPST0032E: The client policy attachment file was not found: {0}
CWPST0033E: The system/trust policy attachment file is not found.
CWPST0034E: The application name is required when attachment type is {0} and the attachmentProperties parameter is not specified.
CWPST0035E: The {0} attachment type is not valid.
CWPST0036E: The dynamicClient parameter is only allowed when the client attachment type is specified.
CWPST0037E: The binding reference was not found for the {0} attachment ID.
CWPST0038E: The policy set attachment file could not be created.
CWPST0039E: The system could not retrieve the policy set ID.
CWPST0040E: The system could not find the application name in the file path.
CWPST0041E: The policy attachment file is not found for the {0} application.
CWPST0042E: The PolicyTypeProvider class was not found for the {0} policy type.
CWPST0043E: Attributes are required unless you are removing or switching a binding.
CWPST0044E: The attributes could not be set for the {0} policy type.
CWPST0045E: The binding reference for the {0} attachment ID could not be created.
CWPST0046E: The bindings for the {0} policy type could not be updated.
CWPST0047E: A required property was not found for the bindingLocation parameter.
CWPST0048E: The application name is required when attachment type is {0} and the binding does not reference a WSN service client or system attachment.
CWPST0049E: The system does not allow the cell-level binding to be removed.
CWPST0050E: A policy type name must be specified to remove the server-level binding.
CWPST0051E: A binding was not found for the {0} attachment ID.
CWPST0052E: The system could not set the binding attributes for the {0} policy type.
CWPST0053E: The {0} binding was not found.
CWPST0054E: The binding reference has been removed from the attachment file, but the binding file could not be found: {0}
CWPST0055E: The {0} policy set is not found.
CWPST0056E: The {0} policy type is not found.
CWPST0057E: The {0} default policy type is not found.
CWPST0058E: The following duplicate policy set is found: {0}
CWPST0059E: The following duplicate policy type is found: {0}
CWPST0060E: The following duplicate policyAttachments.xml file is found: {0}
CWPST0061E: The following duplicate clientPolicyAttachments.xml is found: {0}
CWPST0062E: The {0} application is not found.
CWPST0063E: The {0} binding file is not found.
CWPST0064E: The {0} default cell-level binding file is not found.
CWPST0065E: The {0} default server-level binding file is not found.
CWPST0066E: Cannot find the bindings.xml file.
CWPST0067E: The file name that has been specified is not valid.
CWPST0068E: An input parameter that has been specified is not valid.
CWPST0069E: The {0} input parameter is missing or not valid.
CWPST0070E: The {0} attachment ID is not found.
CWPST0071E: The attachments were not found.
CWPST0072E: More than one attachment was found with the following id: {0}
CWPST0073E: The {0} resource already exists in the attachment.
CWPST0074E: The {0} resource was not found in the attachment.
CWPST0075E: The system cannot write to this read only instance.
CWPST0076E: The {0} policy set type is not valid.
CWPST0077E: The {0} attribute is not valid.
CWPST0078E: The policy set name cannot be modified.
CWPST0079E: The policy type cannot be modified.
CWPST0080E: The following file name is not valid: {0}
CWPST0081E: The {0} policy type is not found.
CWPST0082E: The {0} policy type exists in the policy set.
CWPST0083E: The required {0} attribute was not found in the {1} policy set.
CWPST0084E: The system created an exception: {0}
CWPST0085E: A duplicate bindings.xml file already exists: {0}
CWPST0086E: The {0} binding file is not found for the {1} policy type.
CWPST0087E: A duplicate system/trust policyAttachments.xml file is found.
CWPST0088E: The {0} system policy set type was not recognized.
CWPST0089E: The system created an error because of an unterminated variable reference.
CWPST0090E: The following recursive variable appears: {0}
CWPST0091E: The following variable is not defined: {0}
CWPST0092E: The repository cannot be initialized.
CWPST0093E: The variable map cannot be initialized.
CWPST0094E: The PolicyTypeProvider class could not be loaded: {0}
CWPST0095E: The {0} node is not found.
CWPST0096E: The {0} server is not found.
CWPST0097E: The {0} application file is not found.
CWPST0098E: The {0} zip file does not contain any files.
CWPST0099E: The {0} zip file contains entries that have no directory path information.
CWPST0100E: The {0} zip file contains directory entries that are not valid.
CWPST0101E: The {0} zip file contains the {1} policyset that exists on this system.
CWPST0102E: The {0} zip file contains more than one policy set.
CWPST0103E: The {0} zip file contains a {1} policy that is not valid on this system.
CWPST0104E: The {0} file name is a directory.
CWPST0105E: The {0} zip file does not contain a policy set.
CWPST0106E: The bindingName and remove parameters are required when you specify the attachment ID as an asterisk (*).
CWPST0107E: The {0} binding cannot be deleted because it is still referenced by an attachment.
CWPST0108E: The client policy attachment file is not found for bus: {0} WSN service: {1}
CWPST0109E: The servicesIndex.xml file could not be located for bus: {0} WSN service: {1}
CWPST0110E: The client attachment type is required when {0} and {1} are specified for the {2} parameter.
CWPST0111E: The {0} and {1} properties must be specified when the attachment is for a WSN service client.
CWPST0112E: The following resources are already attached to the WSN service: {0}
CWPST0113E: The system could not find the WSN service in the file path.
CWPST0114E: The {0} parameter did not contain valid values.
CWPST0115E: The resource cannot contain a module name if the attachment is for a WSN service client.
CWPST0116E: A policy set that contains WSReliableMessaging cannot be attached to an endpoint or operation.
CWPST0117E: WSN service client attachments are not valid at an endpoint or operation layer.
CWPST0118E: The {0} bus is not found.
CWPST0119E: The configuration service cannot be initialized.
CWPST0120E: Access denied for resource {0}, {1} authority required.
CWPST0121E: Unable to find cell name.
CWPST0122E: Either {0} or {1} must be specified, but not both.
CWPST0123E: The templates repository context was not found.
CWPST0124E: The {0} binding is not valid for the specified type.
CWPST0125E: The following binding directory does not contain any files: {0}
CWPST0126E: The following duplicate binding is found: {0}
CWPST0127E: The {0} compressed file does not contain a binding.
CWPST0128E: The {0} compressed file contains more than one binding.
CWPST0129E: The {0} compressed file contains the {1} binding that exists on this system.
CWPST0130E: A duplicate defaultBindings.xml file already exists.
CWPST0131E: The {1} parameter cannot be used if the {0} parameter is specified.
CWPST0132E: The default bindings cannot be removed for the global security domain.
CWPST0133E: The {0} binding cannot be deleted because it is still referenced by attachments for the following applications: {1}
CWPST0134E: The {0} binding cannot be deleted because it is the default binding for the following domains: {1}
CWPST0135E: The {0} binding cannot be deleted because it is the default binding for the following servers: {1}
CWPST0136E: Either httpGet or wsMex must be specified.
CWPST0137E: The {0} control file could not be found for application: {1}
CWPST0138E: A duplicate {0} file was found in application: {1}
CWPST0139E: Specifying a resource at the endpoint or operation layer is not valid for WSPolicy.
CWPST0140E: The following resource must have a policy set attachment before sharing policy: {0}
CWPST0141E: The following resource does not contain any WSPolicy settings: {0}
CWPST0142E: The imported policy set type of {0} does not match the specified policy set type of {1}.
CWPST0143W: The bindingLocation properties of node and server are deprecated.
CWPST0144E: Multiple resources are not valid when provider policy set is enabled.
CWPST0145E: Unable to add nor replace resources when provider policy set is enabled.
CWPST0146E: The application or provider attachment type is required when the systemType property in the {0} parameter is: {1}
CWPST0147E: The {0} property does not contain a valid value.
CWPST0148W: The policyset of {0} is not defined in server. You may need to manually import or define this policyset to make your application work properly.
CWPST0149E: An error occurred configuring {0} in WebSphere Application Server repository: {1}
CWPST0150E: An error occurred creating the configuration documents in the repository.
CWPST0151E: The {0} attribute cannot be modified.
CWPST0152E: The {0} domain name is not valid.
CWPST0153E: The {0} parameter cannot be specified at application level.
CWPST0154E: The security domain of the selected binding does not match the security domain of the attachment resource.
CWPST0155E: Unable to create or assign application specific bindings when provider policy set is enabled.
CWPST0156E: The {0} version is not valid for the specified application.
CWPST0157E: A general binding cannot be assigned to an application with version {0}.
CWPST0158E: The imported binding type of {0} does not match the specified binding type of {1}.
CWPST0159E: The {0} binding type is not valid.
CWPST0160E: The {0} policy type is not valid for WSMex.
CWPST0161E: A duplicate bindingDefinition.xml file already exists: {0}
CWPST0162E: The {0} domain name is not valid for the attachment resource.
CWPST0163E: The bindings for the specified application cannot be upgraded because the application is installed on a server at version {0}.
CWPST0164E: The {0} composition unit is not found.
CWPST0165E: The following resources are already attached to the asset: {0}
CWPST0166E: The {1} parameter cannot be used if the {0} parameter is specified.
CWPST0167E: The servicesIndex.xml file could not be located for the {0} asset.
CWPST0168E: The policy attachment file is not found for the {0} asset.
CWPST0169E: The system could not find the asset name in the file path.
CWPST0170E: The resource cannot contain a module name if the {0} parameter is specified.
CWPST0171E: The {0} binding name contains characters that are not valid.
CWPST0172E: The {0} policy set contains the following list of policy types that are not valid: {1}
CWPST0173E: The {0} policy set name does not match the name that is found in the policy set file.
CWPST0174E: The list of policy types in the {0} policy set file does not match the list of policy type files in the directory.
CWPST0175E: The {0} property requires the {1} property.
CWPST0176E: The {0} policy type is not valid for an HTTP GET request.
CWPST0177E: The {0} parameter must specify the name of a service when the {1} parameter is specified.
CWPST0178E: The {0} parameter is only valid when the client attachment type is specified.
CWPST0179E: A service and a service reference cannot be specified in the same attachment.
CWPST0180E: The {0} parameter is only valid when a service reference resource is specified.
CWPST0181E: The {0} parameter is not valid when the {1} parameter is set to true.
CWPST0182E: Only one resource is valid if the {0} parameter is not specified.
CWPST0183E: An endpoint or an operation is not valid if the {0} parameter is not specified.
CWPST0184E: The resources for the {0} attachment cannot be updated since the attachment does not contain a policy set.
CWPST0185E: A service reference attachment is not supported on an application that is installed on a server at version {0}.
CWPST0186E: The format of the resource is not supported on an application that is installed on a server at version {0}.
CWPST0187E: An attachment for an application or service cannot be updated with a service reference attachment.
CWPST0188E: An attachment for a service reference cannot be updated with an application or service attachment.
CWPST0189E: Attributes are not supported for the {0} policy type.
CWPST0190E: Unable to configure the {0} application because it contains configuration for WSPolicy that requires version {1} or later of the WebSphere Application Server. The application is installed on a node at version {2}.
CWPST0191E: The command cannot complete successfully because the following resource is a service reference that is configured to inherit the policy set attachment of the service: {0}
CWPST0192E: An attachment to a policy set that contains the {0} policy type is not supported on an application that is installed on a server at version {1}.
CWPST0193E: The {0} policy type cannot be added to the {1} policy set because the policy set is attached to an asset that is installed on a server at version {2}.
CWPST0194E: Provider bindings are not supported for the {0} policy type.


Terms and conditions for information centers | Feedback

Last updated: November 13, 2013 05:41 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.policyset.admin.resources.policySetAdmin.dita
File name: com.ibm.ws.policyset.admin.resources.policySetAdmin.html