CWSAL

CWSAL0001E: Cannot write the migrated EBA file {0}.
CWSAL0002E: An IOException occurred when reading the application manifest file of the enterprise bundle archive (EBA) {0}. The file might be invalid, corrupted or unreadable.
CWSAL0003E: An internal error has occurred. Cannot read the application manifest or deployment manifest for the enterprise bundle archive (EBA) file {0}.
CWSAL0004E: An internal error has occurred. Cannot read the application manifest or deployment manifest for the enterprise bundle archive (EBA) file {0}.
CWSAL0005E: An internal error has occurred. Cannot read the application manifest or deployment manifest for the enterprise bundle archive (EBA) file {0}.
CWSAL0006E: Cannot read the bundle manifest for the JAR file {0} in the EBA file {1}.
CWSAL0007E: Cannot read the EBA file {0}.
CWSAL0008W: The Java EE application descriptor file was not found in EBA file {0}. Without this descriptor file, context roots for WAR files are set to default values.
CWSAL0009E: Cannot read the Java EE application descriptor file in EBA file {0}.
CWSAL0010E: Conversion of the WAR file {0} in EBA file {1} to a WAB file did not complete successfully.
CWSAL0011E: The EBA file {0} does not specify Application-Content, and contains no valid bundles.
CWSAL0012E: The EBA file {0} specifies Application-Content in its application manifest, but the entry is empty.
CWSAL0013E: An internal error has occurred. The enterprise bundle archive (EBA) file {0}, when resolved, has no content that can be deployed.
CWSAL0014E: EBA file {0} installed with errors.
CWSAL0015E: Cannot resolve EBA file. Exception: {0}.
CWSAL0016E: An internal error has occurred. An incorrect result was returned during provisioning of the enterprise bundle archive (EBA) file {0}, the maximum version {1} was expected to be the same as the minimum version {2}.
CWSAL0017E: An internal error has occurred. The provisioner service {0} is unavailable.
CWSAL0018E: An internal error has occurred. Cannot resolve the enterprise bundle archive (EBA) file {0} because the service {1} is unavailable.
CWSAL0019E: An internal error occurred. The Application-Content entry of the application manifest in the enterprise bundle archive (EBA) file {0} is empty, so no bundle will be installed.
CWSAL0020E: An internal error has occurred. The step {0} cannot be found.
CWSAL0021E: The virtual host {0} specified for bundle {1} does not exist.
CWSAL0022E: Cannot add asset {0} because bundles that it requires are not downloaded. To start the bundle download, save changes to the master configuration after importing the asset.
CWSAL0024E: Authentication alias {0} does not exist in the security domain {2} of the target {1}.
CWSAL0025E: Authentication alias {0} is configured incorrectly. It is not applicable to bind an alias with an authentication type of Application to references.
CWSAL0026E: An internal error has occurred. The enterprise bundle archive (EBA) file {0} is missing the following bundles: {1}.
CWSAL0027E: An internal error has occurred. A file with the correct name exists in the bundle cache, but it does not contain the expected bundle {0}/{1}.
CWSAL0028E: Cannot create the directory {0}.
CWSAL0029E: Cannot create the directory {0}.
CWSAL0030E: Cannot create the directory {0}.
CWSAL0031E: The selected bundle versions cannot be resolved or are not compatible.
CWSAL0032E: An internal error occurred. Could not extract the deployment manifest from the asset binary {0}.
CWSAL0033E: An internal error has occurred. Plugin Config File URI is not the expected format {0}.
CWSAL0034E: An internal error has occurred. Unable to get the InputStream for web.xml zip Entry in War {0}.
CWSAL0035E: Cannot find the resource reference with JNDI name {0} and type {1} on the target {2} for the web module resource reference {3} defined in bundle {4} with version {5}.
CWSAL0036E: The asset {0} cannot be deployed to both target {1} in security domain {2} and target{3} in security domain {4}.
CWSAL0037W: The asset {0} requires external downloads before it can be deployed to a composition unit.
CWSAL0038W: The asset {0} contains a JAR file {1} that is not a bundle and that will not be converted. If other parts of the application depend on this file, the application will fail at run time.
CWSAL0039E: Cannot add the asset {0} to this business-level application because it is already added to the business level application: {1}
CWSAL0040E: The specified role {0} does not exist.
CWSAL0041E: The specified user {0} is not valid.
CWSAL0042E: The specified group {0} is not valid.
CWSAL0043E: The asset {0} cannot be resolved. It requires the bundle {1}, which is not listed in the Application-Content header in the application manifest, APPLICATION.MF. This bundle imports the package {2} from bundle {3}, which is listed in the Application-Content header.
CWSAL0044E: The asset {0} cannot be resolved. It requires the bundle {1}, which is not listed in the Application-Content header in the application manifest, APPLICATION.MF. This bundle consumes the service {2} from bundle {3}, which is listed in the Application-Content header.
CWSAL0045E: The asset {0} cannot be resolved. It has incompatible version requirements on the following packages: {1}.
CWSAL0046E: The EBA file {0} application manifest lists bundles in the Application-Content header that are also listed in the Use-Bundle header.
CWSAL0047E: Cannot parse the file {0} for the enterprise bundle archive (EBA) file {1}.
CWSAL0048E: The asset {0} cannot be resolved. The attribute {1} on an import for package {2} cannot be satisfied at deployment.
CWSAL0049E: None of the servers or clusters has the required feature {0} deployed for the asset {1}.
CWSAL0050W: The EBA file {0} contains a MANIFEST.MF with the Extension-List header. Conversion of this header is not supported.
CWSAL0051E: An attempt has been made to update an OSGi application asset. This is not supported. Update of OSGi application assets can be performed using the "Update bundle versions in this application" panel from the OSGi application asset configuration page.
CWSAL0052E: The cluster member {0} is not augmented with the features, {2}, required by the OSGi application {1}.
CWSAL0053E: The EBA file {0} cannot be installed. The Application-SymbolicName {1} of the EBA is already being used by the asset {2}.
CWSAL0054I: {1} has been assigned to the directory {0}.
CWSAL0055E: An internal error occurred. Unable to obtain composition unit for asset {0}.
CWSAL0056E: An internal error occurred. Unable to locate the configuration data needed to expand {0}.
CWSAL0057E: Unable to expand enterprise bundle archive (EBA) file {0}, cannot create directory {1}.
CWSAL0058E: An internal error occurred. Unable to expand enterprise bundle archive (EBA), no expansion directory specified in the configuration for {0}.
CWSAL0059E: An internal error occurred. Unable to delete leaf directory of {0} so that a directory rename can proceed.
CWSAL0060E: Unable to rename the file {0} to {1} as part of the expansion of enterprise bundle archive (EBA) file {2}.
CWSAL0061E: enterprise bundle archive (EBA) file {1} contains directory {0}, which is not supported.
CWSAL0062E: An internal error occurred. Failed to find an MBean for the BundleCacheManager for profile {0}.
CWSAL0063E: Resolution of asset {0} indicates invalid dependencies of shared content on application content: {1}
CWSAL0064E: Unable to process the deployment manifest file that was provided by the application from this location {0}.
CWSAL0065E: The requirements specified by the deployment manifest within the EBA cannot be satisfied. The exception generated is {0}.
CWSAL0066E: The deployment manifest content is not correct. The following extra bundles are required {0}.
CWSAL0067E: The deployment manifest to import is not valid for the asset {0} because it does not meet the requirements in the application manifest.
CWSAL0068E: The deployment manifest content is not correct. The following bundles are redundant: {0}.
CWSAL0069E: Cannot export asset {0} because bundle {1} that it requires is not fully downloaded.
CWSAL0070E: Unable to create directory: {0}
CWSAL0071E: Unable to create file: {0}
CWSAL0072W: Using localhost as the host name for the transport for the server {0}.{1}. Request routing will work as long as the web server and application server are on the same node.
CWSAL0073E: The application {0} includes a composite bundle {1} in its application content. This is not supported.
CWSAL0074E: An internal error occurred. The ModelledResourceManager service is not available from the OSGi service registry.
CWSAL0075E: An internal error occurred. The DeploymentManifestManager service is not available from the OSGi service registry.
CWSAL0076E: An internal error occurred. The RepositoryAdminSupport service is not available from the OSGi service registry.
CWSAL0077E: The CompUnitStatusStep indicates that the composition unit {0} should be upgraded to the latest deployment version available from asset {1}. However, the composition unit {0} is up-to-date.
CWSAL0078E: The OSGi application deployed in composition unit {0} in business-level application {1} did not start.
CWSAL0079E: The OSGi application deployed in composition unit {0} in business-level application {1} did not stop.
CWSAL0080E: The update operation did not succeed for the OSGi application deployed in composition unit {0} in business-level application {1}.
CWSAL0081E: Cannot resolve EBA file. The included deployment manifest is not valid on this system. Exception: {0}.
CWSAL0082E: The deployment manifest for the application {0} at version {1} lists content with the same symbolic name and version as the application.
CWSAL0083E: An internal error has occurred. Cannot find the config asset object for asset {0}.
CWSAL0084E: The user {0}, is not a mapped user or a member of a mapped group for role {1}.
CWSAL0085E: The role {0}, is not a valid role.
CWSAL0086E: The user ID or password is incorrect.
CWSAL0087E: An internal error has occurred. The SecurityAdmin MBean has not been registered.
CWSAL0088E: An internal error has occurred. The Admin Service has not been registered.
CWSAL0089W: An extension to the composition unit {0} requires external downloads.
CWSAL0090E: No composition unit with name {0} can be found in the current cell.
CWSAL0091E: The composition unit {0} does not correspond to an OSGi application.
CWSAL0092E: An internal error occurred. The asset {0} could not be queried for content.
CWSAL0093E: An internal error occurred. The {0} service is not available from the OSGi service registry.
CWSAL0094W: The application {0} could not be provisioned for all nodes in the cell. The application can only be deployed on Version 8 nodes. The resolution error was {1}.
CWSAL0095W: The application {0} could not be provisioned for all nodes in the cell. The application can only be deployed on Version 7 nodes that are running the OSGi Applications Feature Pack. The resolution error was {1}.
CWSAL0096W: Provisioning the application {0} produced different results for WebSphere Application Server Version 8 and the WebSphere Application Server Version 7 OSGi Applications Feature Pack. The Version 8 result will be used.
CWSAL0097W: The application {0} contains one or more composite bundle archives (CBAs) {1} in its Application-Content. This is not supported on the WebSphere Application Server Version 7 OSGi Applications Feature Pack.
CWSAL0098E: A cluster member cannot be created on the node {0} because the OSGi application(s) {1} cannot be provisioned against it. The resolution error was {2}.
CWSAL0099E: A cluster member cannot be created on the node {0} because the OSGi application(s) {1} have been extended.
CWSAL0100E: A cluster member cannot be created on the node {0} because the OSGi application(s) {1} contain composite bundle archives (CBAs) in Application-Content.
CWSAL0101E: A cluster member cannot be created on the node {0} because the OSGi application(s) {1} define Run As Roles.
CWSAL0102W: Run As Roles cannot be configured for nodes prior to WebSphere Application Server Version 8. Any configuration will be ignored.
CWSAL0103E: The Composite Bundle Archive (CBA) {0} is not valid. Packages imported by bundles in the CBA are missing from the Import-Package header of the CBA manifest file. The following problems were reported: {1}
CWSAL0104W: The composite manifest of Composite Bundle Archive (CBA) {0} contains a CompositeBundle-ExportService header but no services defined in the CBA match this filter.
CWSAL0105W: Service references in the contents of the Composite Bundle Archive (CBA) {0} cannot be resolved. If these services are provided by bundles that are not included in the CBA, then the CBA must import them. The following service dependencies were unresolved: {1}
CWSAL0106E: The Composite Bundle Archive (CBA), {0} is not valid. The following exported packages listed in the composite manifest are not exported by bundles in the CBA: {1}
CWSAL0107E: The UpdateAppContentVersionStep command in WAS V7 has been replaced with the UpdateAppContentVersions command in WAS V8.
CWSAL0108E: The value specified for the application manifest version {0} is not supported. The supported version is {1}.
CWSAL0109E: The bundle {0} in Composition Unit {1} could not be updated as there is a conflicting extension with the same symbolic name.
CWSAL0110E: The EJB interface {0} for enterprise bean {1} in Bundle {2} at version {3} cannot be bound to the location {4}. Locally accessible EJB interfaces must be bound into the ejblocal: namespace.
CWSAL0111E: The enterprise bean {0} in bundle {1} at version {2} has multiple mappings for the interface {3} in its bindings file. The mappings were {4} and {5}.
CWSAL0112E: The enterprise bean {0} in bundle {1} at version {2} has a simple mapping name defined, but also has specific mappings in its bindings file.
CWSAL0113E: Cannot find the message destination reference or resource environment reference with JNDI name {0} and type {1} on the target {2} for the EJB message destination reference or resource environment reference {3} defined in bundle {4} with version {5}.
CWSAL0114E: Cannot find the resource reference with JNDI name {0} and type {1} on the target {2} for the EJB resource reference {3} defined in bundle {4} with version {5}.
CWSAL0115E: An internal error occurred. The module {0} was of an unexpected type.
CWSAL0116E: No default binding could be created for EJB reference {0} in bundle {1} at version {2} with interface {3} since no matching enterprise beans exist in the application.
CWSAL0117E: No default binding could be created for EJB reference {0} in bundle {1} at version {2} with interface {3} becuase there are two or more possible bindings. The reference could be bound to any of the following enterprise beans: {4}.
CWSAL0118E: EJBRefStep.validateTable(): EJBMappingsStep has not run, and should have done.
CWSAL0119E: The OSGi application {0} is not valid because its symbolic name contains two consecutive period characters.
CWSAL0120W: No MDB Activation Spec JNDI name has been configured for bean {0} in bundle {1} at version {2}, on target {3}.
CWSAL0121W: No MDB Activation Spec that matches the JNDI name {0} could be found on the target {1} for the resource used by bean {2} in bundle {3} at version {4}.
CWSAL0123W: No MDB Destination that matches the JNDI name {0} could be found on the target {1} for the resource used by bean {2} in bundle {3} at version {4}.
CWSAL0124W: No MDB Listener Auth Alias that matches the name {0} could be found on the target {1} for the resource used by bean {2} in bundle {3} at version {4}.
CWSAL0125E: An internal error occurred. The CBA bundle {0} at version {1} cannot be modelled.
CWSAL0125W: The binding {0} for EJB reference {1} in bundle {2} at version {3} with interface {4} might cause the application to function incorrectly after an update.
CWSAL0126E: An exception occurred while modelling bundle {0}: {1}


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.eba.bla.nls.Messages.dita
File name: com.ibm.ws.eba.bla.nls.Messages.html