ADMA

ADMA0001E: A validation error occurred in task {0}. The listener port name is not specified for the enterprise bean {1} in module {2}.
ADMA0002E: A validation error occurred in task {0}. The Java Naming and Directory Interface (JNDI) name is not specified for enterprise bean {1} in module {2}.
ADMA0003E: A validation error occurred in task {0}. The isolation level is not specified for resource reference {1} in module {2}.
ADMA0004E: A validation error occurred in task {0}. The Java Naming and Directory Interface (JNDI) name is not specified for module {1} with URI {2}. The data source must be specified for each container-managed persistence (CMP) bean that belongs to this module.
ADMA0005E: A validation error occurred in task {0}. An inappropriate resource authorization is specified for module {1} with URI {2}.
ADMA0006E: A validation error occurred in task {0}. An inappropriate protection value is specified for module {1} with URI {2}.
ADMA0007E: A validation error occurred in task {0}. The Java Naming and Directory Interface (JNDI) name is not specified for resource reference {1} in module {2} with EJB name {3}.
ADMA0008E: A validation error occurred in task {0}. The data in a hidden field used to identify an Oracle data source is not specified for resource reference {1} in module {2} with EJB name {3}.
ADMA0009E: Validation error in task {0}. User info is not specified for role {1}.
ADMA0010E: Validation error in task {0}. A virtual host is not specified for web module {1} with URI {2}.
ADMA0011E: Error saving workspace to configuration repository.
ADMA0012E: The task helper for task {0} cannot be located.
ADMA0013E: The dependency helper for task {0} cannot be located.
ADMA0014E: Validation failed. {0}
ADMA0015E: An incorrect task data format is encountered: incorrect length - {0}
ADMA0016E: The application name is null.
ADMA0017E: The context for {0} cannot be obtained. The application does not appear to be installed.
ADMA0018W: The database vendor type of "{0}" is not supported. Supported values are {1}.
ADMA0019E: An attempt to get the enterprise archive (EAR) file for {0} failed.
ADMA0020E: An error occurred backing up the enterprise archive (EAR) file - {0}
ADMA0021E: An error occurred in compiling JavaServer Pages (JSP) files - {0}
ADMA0024E: An incorrect dependency task {0} is encountered.
ADMA0025E: An incorrect isolation level is detected for resource reference {0} for module {1}.
ADMA0026E: An isolation level is not in number format - {0}
ADMA0027E: An incorrect task data format is detected: The Java Naming and Directory Interface (JNDI) name for the data source for enterprise bean {0} in module {1} is missing.
ADMA0028E: An incorrect task data format is detected: User and password data for enterprise bean {0} in module {1} is missing.
ADMA0029E: An incorrect task data value is detected for resource authorization of enterprise bean {0} in module {1}.
ADMA0030E: An incorrect task data format is detected: Resource authorization data for enterprise bean {0} in module {1} is missing.
ADMA0031E: A matching security role for role name {0} cannot be found.
ADMA0032W: The database access type of "{0}" is not supported. Supported values are {1}.
ADMA0033E: An incorrect server string is specified - {0}
ADMA0034E: An error occurred getting a role assignment.
ADMA0035E: A null pointer exception occurred when getting local methods for {0}
ADMA0036E: A null pointer exception occurred when getting home methods for {0}
ADMA0037E: A null pointer exception occurred when getting local home methods for {0}
ADMA0038E: A null pointer exception occurred when getting remote methods for {0}
ADMA0039W: The JDK compliance level of "{0}" is not supported. Supported values are {1}.
ADMA0040E: Could not find an EAR, EJB JAR, or WAR (with EJBs) to process.
ADMA0041E: The local enterprise archive (EAR) file path cannot be null for the installApplication API.
ADMA0042E: The properties cannot be null for the installApplication API.
ADMA0043E: {0} does not exist for installation.
ADMA0044E: An error occurred scheduling the installation for {0}
ADMA0045E: The application name cannot be null.
ADMA0046E: Properties cannot be null for local mode.
ADMA0047E: An error occurred when scheduling the uninstallation for {0}
ADMA0048E: An unknown module is encountered- {0}
ADMA0049E: An exception occurred when getting a module for deployment descriptor {0}
ADMA0050W: Role name is empty for security role {0}.
ADMA0053E: An error occurred closing the enterprise archive (EAR) file {0}
ADMA0054E: An exception occurred checking application existence - {0}
ADMA0055E: An error occurred getting task {0}
ADMA0056E: An incorrect task data format is detected; the Java Naming and Directory Interface (JNDI) data is missing in module {0}
ADMA0057E: An incorrect task data format is detected: the user and password data is missing in module {0}
ADMA0058E: An incorrect task data value for resource authorization exists in module {0}.
ADMA0059E: An incorrect task data format is detected. The resource authorization data is missing in module {0}
ADMA0061E: An error occurred deleting SI entry - {0}
ADMA0062E: The EJBDeploy program issued the following error messages: {0}
ADMA0063E: An error occurred during Enterprise JavaBeans (EJB) deployment. Exception: {0}
ADMA0064E: An error occurred when extracting the enterprise archive (EAR) file.
ADMA0065E: An error occurred getting a partial archive in the writeTasks method- {0}
ADMA0066E: An error occurred creating the configuration documents in the repository.
ADMA0067E: A validation error occurred in task {0}. The RunAs role, {1}, for enterprise bean {2} in module {3} has a user name and a password that are different from those in task {4}.
ADMA0068E: A validation error occurred in task {0}. An error occurred getting task {1} to validate existing RunAs roles.
ADMA0069E: A validation error occurred in task {0}. The RunAs role, {1}, for enterprise bean {2} in module {3} has a different user name and password combination.
ADMA0070W: Security policy filtering cannot be performed: An error occurred getting the repository context for a cell in the workspace.
ADMA0071W: An attempt to perform security policy filtering failed. An unexpected exception occurred {0}
ADMA0072E: Your application contains policy permissions that are in the filter policy. These permissions are security sensitive and can compromise the integrity of the system. Remove these permissions from your policy file before attempting to install your application again.
ADMA0073W: Custom permissions are found in the {0} policy file. Custom permissions can compromise the integrity of Java 2 Security.
ADMA0074E: A validation error occurred in task {0}. The Java Naming and Directory Interface (JNDI) name and resource authorization are not specified for module {1} with URI {2}. The data source for each container-managed persistence (CMP) bean belonging to this module is not specified. Specify the default data source for the entire module or provide the complete data source for each CMP bean belonging to this module.
ADMA0077W: An error occurred removing the workspace. Exception: {0}
ADMA0078W: The file: {0} cannot be deleted.
ADMA0079W: The task information for: {0} cannot be found.
ADMA0080W: A template policy file without any permission set is included in the 1.2.x enterprise application. You can modify the Java 2 Security policy for the enterprise application by editing the was.policy file that is located in the ${user.install.root}/config/cells/(yourCellName)/applications/(yourAppName).ear/deployments/(yourAppName)/META-INF directory after the application is installed.
ADMA0081W: The 1.2.x enterprise application does not contain a Java 2 Security policy. Your application might not run after it is installed.
ADMA0082E: Your application contains the following incompatible Java archive (JAR) or Web application archive (WAR) file:{0}. Correct the file before trying the operation again.
ADMA0083E: The file or directory {0} that is specified as an enterprise archive (EAR) file is not valid.
ADMA0084E: The archive {0} to wrap is not a module of type JAR or WAR.
ADMA0085E: A validation error occurred in task {0}. Application name, {1}, is not valid. An application name cannot begin with a dot, cannot have leading or trailing spaces, cannot contain "]]>", and cannot contain any of the following characters: \ / , # $ @ : ; " * ? < > | = + & % ''
ADMA0086E: [EJBDeploy] {0}
ADMA0087W: [EJBDeploy] {0}
ADMA0088E: An unacceptable usage of {0} has occurred. Operation {0} can be called only in the local mode of the AppManagement MBean.
ADMA0089E: The AppManagement MBean is not found.
ADMA0090E: The system detected a use of {0} that is not valid. Operation {0} can be called in the Java Management Extentions (JMX) mode of the AppManagement MBean only.
ADMA0091W: The resource {0} that is defined in URI {1} for module {2} is not valid. The resource has a cross reference {3} that cannot be resolved.
ADMA0092E: An unexpected exception occurred while preparing task {0}. Exception: {1}
ADMA0093E: An unexpected exception occurred while completing task {0}. Exception: {1}
ADMA0094E: An application management operation {0} is not available in your WebSphere Application Server installation.
ADMA0095W: The current backend ID ({0}) that is specified in the ibm-ejb-jar-bnd.xmi file for enterprise bean Java archive (JAR) file ({1}) does not exist.
ADMA0096I: The application management version key is found, but is not valid.
ADMA0097I: Application management is being initialized without a full product installation. All application management functions are not available.
ADMA0098E: The current backend ID {0} does not exist in the BackendId list: {1} under the META-INF/backends directory.
ADMA0099E: A validation error occurred in task {0}. The listener port name or Java Naming and Directory Interface (JNDI) name is not specified for enterprise bean {1} in module {2}.
ADMA0100E: A validation error occurred in task {0}. The Java Naming and Directory Interface (JNDI) name is not specified for connector {1} in module {2}.
ADMA0101E: A validation error occurred in task {0}. The reload interval, {1}, is not valid. The reload interval must be an integer from 0 to {2}.
ADMA0102E: {0} is not defined in the ra.xml file.
ADMA0103E: A duplicate {0} entry is found in the ra.xml file.
ADMA0104W: An unexpected exception occurred while getting the workspace. {0}
ADMA0105E: An error occurred creating the libraryRef object for the installedOptionalPackage task.
ADMA0106E: A workspace cannot be obtained. The workspace ID is {0}.
ADMA0107E: Application has J2EE/Deployment features of version {0} but they are not supported on nodes {1}
ADMA0108E: The application contains connector modules or resource adapter archives (RAR) of version {0}, which is not supported in the application version {1}
ADMA0109W: The validate install input value: {0} is not valid. Specify either off, warn, or fail as the value.
ADMA0110E: This type of J2EE application {0} is not supported on nodes {1} of version {2}
ADMA0111E: The following J2EE and deployment options {0} are selected, but are not supported while installing an application on nodes {1} of version {2}
ADMA0112E: Validation error in task {0}. The required column {1} is not specified.
ADMA0113I: [EJBDeploy] {0}
ADMA0114W: Resource assignment with JNDI name {0} is not found within scope of module {1} with URI {2} deployed to target {3}.
ADMA0115W: Resource assignment of name {0} and type {1}, with JNDI name {2} is not found within scope of module {3} with URI {4} deployed to target {5}.
ADMA0116W: Unable to start: {0} using: {1} exception is: {2}
ADMA0117W: Unable to stop: {0} using: {1} exception is: {2}
ADMA0118W: The {0} operation on application {1}, node {2}, server {3}, failed because the ApplicationManager MBean for that target server could not be found.
ADMA0119E: An unexpected exception occurred while getting the node objects in the cell {0}. Exception is {1}.
ADMA0120E: An unexpected exception occurred while getting the servers in the node {0}. Exception is {1}.
ADMA0121E: An unexpected exception occurred while getting the clusters in the cell {0}. Exception is {1}.
ADMA0122E: An unexpected exception occurred while getting the application {0}. Exception is {1}.
ADMA0123W: An unexpected exception occurred while getting the attribute {0} of object {1}. Exception is {2}.
ADMA0124E: An unexpected exception occurred while getting the Library object from the deployment.xml file of the application {0}. Exception is {1}.
ADMA0125E: The cell name cannot be null for installing or uninstalling system application {0}.
ADMA0126E: The node name cannot be null for installing or uninstalling system application {0}.
ADMA0127E: The server name cannot be null for installing or uninstalling system application {0}.
ADMA0128E: Invalid cell name {1} was passed to the installApplication API for installing application {0}
ADMA0129W: Unable to get the deployment.xml file.
ADMA0130E: The content type {0} that is specified for updating {1} is not valid.
ADMA0131E: The path to content must be specified when the contenttype value is partialapp for updating an application.
ADMA0132E: The operation {0} that is specfied for updating application {1} is not valid.
ADMA0133E: Both the content URI and the path to content values must be specified for file or modulefile updates.
ADMA0134E: Content does not exist at path {0} specified for the file and modulefile update of {1}
ADMA0135E: The content URI must be specified for file or modulefile delete.
ADMA0136E: Content type {0} and operation {1} is not valid. Because {1} is installed using zero binary copy mode only, you can use the modulefile as content type and specify add or delete as operation.
ADMA0137E: JNDI resource element {2} in module {0} with URI {1} does not have a type.
ADMA0138W: The resource assignment with JNDI name {0} is found within scope of module {1} with URI {2} deployed to target {3}, but of wrong resource type {4}. The expected resource type is {5}.
ADMA0139W: The resource assignment of name {0} and type {1}, with JNDI name {2} is found within scope of module {3} with URI {4} deployed to target {5}, but of wrong resource type {6}. The expected resource type is {7}.
ADMA0140E: A validation error occurred in task {0}. Application edition, {1}, is not valid. An application edition cannot have leading or trailing spaces and cannot contain any of the following characters: \ / , # $ @ : ; " * ? < > | = + & % '' [ ]
ADMA0141E: Application {0} cannot be uninstalled because it is active on deployment targets {1}.
ADMA0142W: Trying to close the archive that is already closed.
ADMA0143W: Unexpected exception: {0} checking if the enterprise archive (EAR) file is deployed.
ADMA0144E: Application {0} is installed with the zero binary copy option. Applications are installed using this option in a Rational unit test environment or using AppManagement MBean API. When an application is installed using this option it is not possible to perform any operation on this application using wsadmin or administrative console that involves accessing the application metadata or EAR file. Such operations include view/edit application information, export, export DDL etc. The only possible operations using wsadmin or admin console are start, stop and uninstall. If this application is installed using WSAD unit test environment then use WSAD to view/edit application information.
ADMA0145E: The application {0} is installed with the zero binary copy option. It is not possible to perform any operation on this application that involves accessing the application metadata or enterprise archivve (EAR) file.
ADMA0146E: The application {0} is installed with the zero ear copy option. It is not possible to perform edit operations with useMetaDataFromBinaries flag true.
ADMA0147E: The application {0} was installed using the zero ear copy option. It is not possible to perform any operation on this application that involves accessing the enterprise archive (EAR) file.
ADMA0148E: This type of Java Platform, Enterprise Edition application {0} is not allowed on nodes {1} of version {2} when autolink is enabled
ADMA0149E: This type of Java Platform, Enterprise Edition application {0} is not allowed on nodes {1} of version {2} when client module is deployed.
ADMA0150E: An error occurred during the deployment extension step - {0}
ADMA0151I: The system successfully ran the deployment extension step - {0}
ADMA0152E: The system failed to run the deployment extension step - {0}: {1}
ADMA0153I: The system is starting the deployment extension step - {0}
ADMA0154I: A non-J2EE artifact is detected for installation. The system searches for available enterprise archive (EAR) wrapper extensions to wrap the non-J2EE artifact to an EAR file for application deployment.
ADMA0155I: The system successfully made an enterprise archive (EAR) wrapper extension. New earFilePath: - {0}
ADMA0156I: The enterprise archive (EAR) wrapper extension class - {0} is found and ran successfully.
ADMA0157E: The system cannot find any valid enterprise archive (EAR) wrapper extensions or an extension did not run successfully to set a new EAR file path.
ADMA0158I: [EJBDeploy] {0}
ADMA0159W: Duplicate root context({0}) was found on the same node {1} and same host {2}
ADMA0160E: The target scope that is passed to the listApplications has incorrect format {0}.
ADMA0161W: The resource assignment with name {0} is not found within scope of module {1} with URI {2} that is deployed to target {3}.
ADMA0162W: The resource assignment with name {0} is found within scope of module {1} with URI {2} deployed to target {3}, but of wrong resource type {4}. The expected resource type is {5}.
ADMA0163E: Resource validation is not initialized.
ADMA0164W: Failed to load the systemapps.xml file on cell {0}, node {1}.
ADMA0165E: Content does not exist at the path specified {0} for a partialapp update.
ADMA0166E: Duplicate file {0} for {1} operation.
ADMA0167E: File {0} does not exist for {1} operation.
ADMA0168E: Attempt to remove last module {0}.
ADMA0169E: Parameter validation failure for {0}:
ADMA0170E: Authorization failure. The user does not have permission to access application {0}.
ADMA0171E: Authorization failure. The user does not have permission to manage the target {0} : {1}.
ADMA0172E: Authorization failure. The user does not have permission to perform {0} role on the resource {1}.
ADMA0173E: The EAR file for application {0} is not managed by WebSphere. Therefore, any operation such as {1} that involves changing the EAR file is not allowed.
ADMA0174E: The filepermission argument contains an invalid format or contains an invalid regular expression pattern: {0}. Correct format is file_pattern=permission. Multiple filepermissions are separated by a ''#'' (Example: .*\.jsp=644#.*\.xml=744).
ADMA0175E: The AsyncRequestDispatchType is not valid.
ADMA0176E: Application installation of {0} failed with PrivilegedActionException. Ear file path is {1}.
ADMA0177E: Application installation of {0} failed with unknown exception. Ear file path is {1}. Exception is {2}.
ADMA0178E: Checking of the existence of Application {0} failed with PrivilegedActionException.
ADMA0179E: Checking of the existence of Application {0} failed with unknown exception. Exception is {1}.
ADMA0180E: Comparing security policy failed with PrivilegedActionException.
ADMA0181E: Comparing security policy failed with unknown exception. Exception is {0}.
ADMA0182W: The JNDI name {0} specified for the message destination reference {1} does not match the JNDI name {2} of the message destination.
ADMA0183E: Cannot delete a deployment descriptor file: {0}
ADMA0184E: {0} is not a valid target.
ADMA0185W: An update application operation failed and the configuration session could not be restored to its state before the operation was initiated. The configuration session is in an inconsistent state, and changes made in the session should be discarded.
ADMA0186W: An uninstall application operation failed and the configuration session could not be restored to its state before the operation was initiated. The configuration session is in an inconsistent state, and changes made in the session should be discarded.
ADMA0187E: Authorization failure. The user does not have permission to install application {0}. The user must have deployer role or configurator role for the cell or for the targets to install/redeploy the application.
ADMA0188E: Authorization failure. The user does not have permission to uninstall application {0}. The user must have deployer role or configurator role for the cell or for the target, or deployer role for the application to uninstall it.
ADMA0189E: Authorization failure. The user does not have permission to update application {0}. The user must have deployer role or configurator role for the cell or for the target, or deployer role for the application.
ADMA0190E: Authorization failure. The user does not have permission to access application {0}. The user must have monitor role.
ADMA0191E: Authorization failure. The user does not have permission to access the resource {0}. The user must have monitor role for the cell, target node or the application.
ADMA0192E: Authorization failure. The user does not have permission to access the resource {0}. The user must have {1} role to access {2}.
ADMA0193E: Authorization failure. The user does not have permission to update the application {0}. The user must have deployer role or configurator role for the cell or deployer role of the application.
ADMA0194E: Authorization failure. The user does not have permission to start/stop application {0}. The user must have operator role of the applocation.
ADMA0195W: Environment entry {1} in module {0} does not have a type.
ADMA0196W: Environment entry {1} in module {0} does not have a value.
ADMA0197E: The application cannot be updated with the {0} file because the application server cannot expand the {1} URI as an archive file. Either the URI does not resolve to an archive file or the archive file is corrupted.
ADMA0199E: The system cannot complete the operation with autolink enabled. All modules must share one common target to enable autolink support.
ADMA0200E: The application cannot be installed as the installation logic failed to determine the runtime components that this application depends on. The error is - {0}
ADMA0201E: Application validation failed as node {0} of version {1} cannot support use of asset and composition unit shared library.
ADMA0202E: A validation error occurred in task {0}. The type of EJB reference is not specified or is not valid for EJB resource reference {1} in module {2} with EJB name {3}.
ADMA0203E: A validation error occurred in task {0}. The type is not specified for the resource reference {1} in module {2} with EJB name {3}.
ADMA0204E: The application {0} cannot be installed to server type {1} since it is not a system application.
ADMA0205E: A validation error occurred in task {0}. Java Naming and Directory Interface (JNDI) names for the bean and its local/remote home are both specified for enterprise bean {1} in module {2}. You can provide either JNDI name for the bean or JNDI names for its local/remote home. But you cannot provide both.
ADMA0206E: A validation error occurred. Java Naming and Directory Interface (JNDI) names for the bean in task "{0}" and its business interface "{1}" in task "{2}" are both specified for enterprise bean {3} in module {4}. You can provide either JNDI name for the bean or JNDI names for its business interface(s). But you cannot provide both.
ADMA0207E: Module {0} contains an unsupported xmi format bindings or extensions file.
ADMA0208E: The Enterprise Archive (EAR) contains an unsupported xmi format bindings or extensions file.
ADMA0209E: Enterprise JavaBeans (EJB) module {0} contains the following container-managed persistence (CMP) or bean-managed persistence (BMP) Entity beans: {1}.
ADMA0210E: A validation error occurred in task {0}. The extended data source properties {1} specified for resource reference {2} in module {3} with EJB name {4} is not valid.
ADMA0211E: This is a EAR file which is a system application. The system application should always be installed from an expanded directory.
ADMA0212E: The Enterprise Archive (EAR) contains both xmi and xml bindings or extensions files at the application level.
ADMA0213W: The "deploy enterprise beans" option was specified, but no enterprise beans were deployed.
ADMA0214W: The "precompile JavaServer Pages files" option was specified, but no JavaServer Pages (JSP) were compiled.
ADMA0215I: The JavaServer Pages (JSP) compile task completed.
ADMA0216E: The JavaServer Pages (JSP) compile task failed.
ADMA0217E: Validation error in task "{0}". The JSP reload interval "{3}" for web module {1} (URI: {2}) is not valid.
ADMA0218E: Environment entry {2} for EJB {1} in module {0} does not have a type.
ADMA0219E: A validation error occurred in task "{0}". The value for environment entry {3} for EJB {2} in module {1} is missing.
ADMA0220E: A validation error occurred in task "{0}". The value "{5}" for environment entry {3} (type: {4}) for EJB {2} in module {1} is not valid. Exception: {6}
ADMA0221E: Environment entry {1} in module {0} does not have a type.
ADMA0222E: A validation error occurred in task "{0}". The value for environment entry {2} in module {1} is missing.
ADMA0223E: A validation error occurred in task "{0}". The value "{4}" for environment entry {2} (type: {3}) in module {1} is not valid. Exception: {5}
ADMA0224E: The applyConfigProperties command failed. Result: {0}
ADMA0225E: The property-based configuration task failed.
ADMA0226E: Node {0} cannot be added to cluster {1} because an application currently deployed on the cluster requires EJB specification level {2}, which this node does not support
ADMA0227E: Node {0} cannot be added to cluster {1} because an application currently deployed on the cluster requires Servlet specification level {2}, which this node does not support
ADMA0228W: EJB {0} in module {1} has no binding for its datasource.
ADMA0229W: An unexpected error occurred when querying for applications running on node {0}, server {1}.
ADMA0230I: Will retry to expand the application {0}, which previously failed to expand.
ADMA0231E: Failed to set file permissions on the file {0}.
ADMA0232E: Node {0} cannot be added to cluster {1} because an application currently deployed on the cluster requires Connector specification level {2}, which this node does not support
ADMA0233E: Node {0} cannot be added to cluster {1} because an application currently deployed on the cluster requires at least Servlet specification level {2} that contains EJB content, which this node does not support
ADMA0234E: A validation error occurred in task {0}. An environment entry value {3} and lookup name {4} are specified for environment entry {2} in module {1}.
ADMA0235E: A validation error occurred in task {0}. A lookup name {3} and EJB link {4} are specified for EJB reference {2} in module {1}.
ADMA0236E: File {0} is a non-J2EE type artifact. Operation delete on modulefile content type cannot be performed on a non-J2EE type artifact.
ADMA0237I: EJBDeploy does not apply to EJBs contained in WAR files. EJBs in WAR file {0} are being skipped.
ADMA0238I: No EJB JAR files were found for EJBDeploy to process.
ADMA0239W: The application contains EJB content in web module {0}. This module can not be targeted for web server {1}.
ADMA0240E: The application contains EJB content in web module {0}. This module can not be targeted for web server {1}.
ADMA0241W: EJB {0} has a dependency on EJB {1} in another module, which conflicts with the option to initialize the modules in the order they are listed in the application deployment descriptor.
ADMA0242E: A validation error occurred in task {0}. There is a conflict in the target JNDI name for the same reference {1} in module {2}.
ADMA0243I: The file {0} has been removed, from {1} application during the open of the packaged archive.
ADMA0244E: The client mode input value: {0} is not valid. Specify either isolated, federated, or server_deployed as the value.
ADMA0245W: EJBDeploy feature is not installed. Cannot execute "deploy enterprise beans" option.
ADMA0246E: Environment entry {0} in application level does not have a type.
ADMA0247E: A validation error occurred in task "{0}". The value for environment entry {1} is missing.
ADMA0248E: A validation error occurred in task "{0}". The value "{1}" for environment entry {2} (type: {3}) is not valid. Exception: {4}
ADMA0249W: Extended datasource property is not supported for module {0} in task {1}
ADMA0500E: Unexpected exception occurred in application management command: {0}
ADMA0501E: The enterprise archive (EAR) file was not found for the application: {0}
ADMA0502E: An exception occurred while updating the enterprise archive (EAR) file in the workspace. The SQLJ customization results were not stored, however, if SQLJ binding was performed, then packages in the database have been modified. The application name is: {0} The workspace EAR file is: {1}
ADMA0503E: An exception occurred while accessing an input file. The file name is: {0}
ADMA0504W: A duplicate profile name was found. The short profile name is: {0}. The input profile name is: {1}.
ADMA0505E: An exception occurred while accessing a temporary output file. The file name is: {0}
ADMA0506I: The SQLJ operation on application {0} did not complete successfully. Exit code: {1}
ADMA0507I: The SQLJ operation on application {0} completed successfully. Exit code: {1}
ADMA0508I: The pureQuery bind operation on application {0} did not complete successfully. Exit code: {1}
ADMA0509I: The pureQuery bind operation on application {0} completed successfully. Exit code: {1}
ADMA0510I: Results from pureQuery bind processing for {0}. Return code: {1} Exception: {2}
ADMA0511E: Application {0} failed to start. There is no module target specified for the application.
ADMA2000E: An unexpected error occurred.
ADMA2001E: Unsupported object type {0} specified for source of deployable object.
ADMA2002E: The setContentPath method is not supported for the scheduler being used.
ADMA2003E: Internal error; unexpected scheduler type {0}.
ADMA2004E: Extension provider {0} encountered an error.
ADMA3000E: Unable to get the extension registry.
ADMA3001E: Unable to get the extension point {0}.
ADMA4001I: Usage: EARExpander -ear <file-name> -operation {expand|collapse} -directory <directory> | -operationDir <directory> [-expansionFlags {all | war}] [-verbose]
ADMA4002E: The option {0} is required.
ADMA4003E: The enterprise archive (EAR) file {0} is not valid.
ADMA4004E: The operation directory {0} is not valid.
ADMA4005E: The operation {0} is not valid.
ADMA4006I: Expanding enterprise archive (EAR) file {0} to directory {1}.
ADMA4007I: Collapsing the contents of directory {0} to enterprise archive (EAR) file {1}.
ADMA4008E: The value for option {0} is missing.
ADMA4009W: The value {0} for the expansion flag option is not valid.
ADMA4010W: Both the listener port and the Java Naming and Directory Interface (JNDI) name are specified for the enterprise bean: {0} in module {1}. Specify only one value, either the listener port or the JNDI name, for the enterprise bean.
ADMA4011E: A validation error occurred in task {0}. The Java Naming and Directory Interface (JNDI) name is not specified for message destination object {1} in module {2}.
ADMA4012E: A validation error occurred in task {0}. The Java Naming and Directory Interface (JNDI) name is not specified for the enterprise bean: {1} in module: {2}. Specify a JNDI name for the enterprise bean.
ADMA4013E: An unexpected exception occurred while attempting to expand the enterprise archive (EAR) file {0} to directory {1}. Exception: {2}
ADMA4014E: An unexpected exception occurred while attempting to collapse the contents of directory {0} to enterprise archive (EAR) file {1}. Exception: {2}
ADMA4015E: The argument {0} is not recognized.
ADMA5001I: The application binaries are saved in {0}
ADMA5002E: Application binaries cannot be saved in {0}: {1}
ADMA5003I: The JavaServer Pages (JSP) files in the Web Archive (WAR) {0} compiled successfully.
ADMA5004W: The JavaServer Pages (JSP) files in the Web Archive (WAR) {0} failed to compile; check the log for more information.
ADMA5005I: The application {0} is configured in the WebSphere Application Server repository.
ADMA5006E: An error occurred configuring {0} in WebSphere Application Server repository: {1}
ADMA5007I: The EJBDeploy program completed on file {0}
ADMA5008E: The EJBDeploy program failed on file {0}. Exception: {1}
ADMA5009I: Extracting application archive to {0}.
ADMA5010E: An error occurred extracting the application archive to {0}. Exception: {1}
ADMA5011I: The cleanup of the temp directory for application {0} is complete.
ADMA5012I: The installed cleanup failed for {0}: {1}
ADMA5013I: Application {0} installed successfully.
ADMA5014E: The installation of application {0} failed.
ADMA5015E: Application {0} cannot be installed because it already exists in the WebSphere Application Server configuration.
ADMA5016I: Installation of {0} started.
ADMA5017I: Uninstallation of {0} started.
ADMA5018I: The EJBDeploy program is running on file {0}.
ADMA5019E: The application name {0} is not valid. The application name cannot begin with a dot, cannot have leading or trailing spaces, cannot contain "]]>", and cannot contain any of the following characters: \ / , # $ @ : ; " * ? < > | = + & % ''
ADMA5020E: The target server {0} on node {1} that is specified for module {2} does not exist.
ADMA5022E: The target cluster {0} specified for module {1} does not exist.
ADMA5023E: Ambiguous specification for object {0}. Multiple objects exist with this name, at least one each under parents {1} and {2}. Specify parent {3}.
ADMA5024E: The cluster member {0} is specified as a target for module {1}, but the cluster {2} that {0} belongs to is not specified in the list of targets. This configuration is not valid.
ADMA5025E: The ObjectName format is incorrect for {0}.
ADMA5026E: No valid target is specified in ObjectName {0} for module {1}.
ADMA5027E: Cluster {0} is not found in the repository.
ADMA5028E: Server {0} on node {1} is not found in the repository.
ADMA5029E: Cluster member {0} that is defined in the cluster configuration for {1} cannot be found as a server.
ADMA5030E: No deployment object is found in the deployment document for {0}.
ADMA5031E: The system cannot load {0} document for the object at {1}.
ADMA5032W: The target {0} is specified more than once in {1}. Ignoring {2}
ADMA5033E: The target server {0} specified for {2} is a part of cluster {1}, but cluster {1} is not specified in the list of targets.
ADMA5034W: The server {0} mentioned in the copy.sessionmgr.servername options for installation does not exist in the configuration.
ADMA5035E: The copy operation on the session manager of {0} failed, as the copy is {1}.
ADMA5036E: An exception {0} occurred while copying session manager settings from server {1}.
ADMA5037I: The system is starting to back up the application at {0}
ADMA5038I: The system Completed the backup of the application at {0}
ADMA5039E: The node name cannot be null.
ADMA5040E: The node name {0} does not exist in the configuration.
ADMA5041E: The application {0} that is listed in the server index entry for node {1} cannot be found.
ADMA5042E: Targets {0} are not found in the repository. Server index entries for these targets are not updated.
ADMA5043I: Module {0} is bound to server {1}.
ADMA5044I: Application {0} is bound to node {1}.
ADMA5045E: The application name {0} cannot be found under any cell in the repository.
ADMA5046E: No cell name is specified in the options table that is passed as a parameter to the intallApplication API. The cell name is looked for in the module to server mapping that is specified using the AppConstants.APPDEPL_MODULE_TO_SERVER key in the options table and then in the value that corresponds to the AppConstants.APPDEPL_CELL key in the options table.
ADMA5047E: The cell name {0} does not exist in the configuration.
ADMA5048E: No cell name is specified in the input parameters.
ADMA5049E: The binary data for the enterprise archive (EAR) file of application {0} cannot be located either in the repository at context {1} or on the disk at {2}.
ADMA5050E: An unacceptable number format for the reload interval is detected. The specified value {0} is not a valid long value.
ADMA5051W: An unacceptable value {0} for the class loader policy is detected. The default MULTIPLE is used.
ADMA5052W: A value that is not valid {0} is detected for the class loading mode. The default, PARENT_FIRST, is used.
ADMA5053I: The library references for the installed optional package are created.
ADMA5054E: The InstalledOptionalPackage deployment task failed on {0}: {1}
ADMA5055E: Errors in validating application target association for {0} - {1}
ADMA5056E: Error in installing application {0}
ADMA5057E: Application validation failed with an unexpected exception while checking module to server relationship: {0}
ADMA5058I: Application and module versions are validated with versions of deployment targets.
ADMA5059E: Errors in validating resource usage for application {0} - {1}
ADMA5060E: Resource validation for application {0} failed due to unexpected exception {1}
ADMA5061W: The resource JNDI table is not created yet; call gatherJNDINames first.
ADMA5062W: An error occurred while reusing the existing deployment.xml file. The original deployment settings are not reused."
ADMA5063W: Wrong input for recycle behavior. {0} is specified as recycle option, but modules to recycle are not supplied using key {0}.
ADMA5064I: FileMergeTask completed successfully for {0}.
ADMA5065E: Exception in FileMergeTask {0}.
ADMA5066E: Error validate application {0} : {1}.
ADMA5067I: Resource validation for application {0} completed successfully.
ADMA5068I: The resource validation for application {0} completed successfully, but warnings occurred during validation.
ADMA5069E: The installation of application {0} failed. This application was in the middle of a full update and therefore is uninstalled from the configuration session. Discard your current configuration session immediately to recover the application. Do not save changes to the WebSphere Application Server configuration repository. The application is not uninstalled from this repository. Until the current configuration session is discarded you do not see this application in the current session.
ADMA5070E: The serverindex.xml for node {0} is empty. The operation cannot be completed. Save the log files and report this problem.
ADMA5071I: Distribution status check started for application {0}.
ADMA5072I: Distribution status check completed for application {0}.
ADMA5073E: An incorrect shared library string is specified - {0}
ADMA5075I: Editing of application {0} started.
ADMA5076I: Application {0} edited successfully. The application or its web modules may require a restart when a save is performed.
ADMA5077E: Editing of application {0} failed.
ADMA5078I: Update of {0} has started.
ADMA5079I: Update of {0} has ended. The application or its web modules may require a restart when a save is performed.
ADMA5080E: Update of {0} has ended. The update failed.
ADMA5081I: The bootstrap address for client module is configured in the WebSphere Application Server repository.
ADMA5082E: Error configuring the bootstrap address for application {0} - {1}
ADMA5083E: Unexpected exception while looking for application client extension.
ADMA5102I: The configuration data for {0} from the configuration repository is deleted successfully.
ADMA5103E: The deletion of the configuration data for {0} from the configuration repository failed.
ADMA5104I: The server index entry for {0} is updated successfully.
ADMA5105E: Updates to the server index entry failed for the last node in {0}
ADMA5106I: Application {0} uninstalled successfully.
ADMA5107E: The application {0} cannot be uninstalled.
ADMA5108E: Application {0} cannot be uninstalled because it does not exist in the WebSphere Application Server configuration.
ADMA5109E: Unexpected exception {0} deleting edition configuration properties for {1}
ADMA5110I: The application {0} is installed as a hidden application and will not be exposed via administrative interfaces such as GUI client, wsadmin or MBean Java API. In order to perform management operations on this application, the application name must be known.
ADMA5111E: The deployment.xml file could not be found in the expanded application directory while installing as a system application
ADMA5112E: An error occurred creating an activation plan for the application - {0}
ADMA5113I: Activation plan created successfully.
ADMA5114I: Property-based configuration file successfully applied.
ADMA5115E: An unexpected exception occurred while applying the property-based configuration file. Exception: {0}
ADMA6001I: Begin the application preparation -
ADMA6002I: The options used are:
ADMA6003I: Reading the local enterprise archive (EAR) file ...
ADMA6004I: The preferences for default bindings:
ADMA6005I: Checking the filter.policy file on server ...
ADMA6006I: ...... Saving the local enterprise archive (EAR) file ...
ADMA6007I: Proceeding with local installation.
ADMA6008I: Installation event received:
ADMA6009I: Processing is complete.
ADMA6010I: The tasks are {0}
ADMA6011I: Deleting directory tree {0}
ADMA6012I: Exception in run {0}
ADMA6013I: Extract application binaries at {0}
ADMA6014I: The cell name is {0}
ADMA6015I: Module {0} is being installed on {1}
ADMA6016I: Add to workspace {0}
ADMA6017I: The document {0} is saved.
ADMA6018I: The node-server relationship for this application is {0}
ADMA6019I: The node-serverIndex document relationship for this application is {0}
ADMA6020I: The system is adding the serverindex entry for {0} for server {1} on node {2}
ADMA6021I: Removing the serverindex entry for {0} for server {1} on node {2}, and the return code is {3}
ADMA6022E: Uri {0} conflicts with existing uri {1} in the application"
ADMA6051I: Begin the application uninstall.
ADMA6052I: Proceeding with the local uninstall ...
ADMA6053I: Uninstall event received:
ADMA6054I: Application installation deployment targets exist in different node groups {0}
ADMA7000W: An unexpected exception occurred during onChangeStart processing: {0}
ADMA7001W: An unexpected exception occurred in checking if {0} is an application enterprise archive (EAR) file: {1}. This file might not be synchronized properly, that is the application binaries might not get placed correctly.
ADMA7002E: An unexpected exception {0} occurred in building the cache for application synchronization from the serverindex.xml file. The application synchronization logic does not work for deletions or modifictions of binaries in this case.
ADMA7003E: A malformed server index entry {0} exists. The correct form for the entry is appName.ear/deployments/appName. The application binary corresponding to this entry might not be changed upon completion of the task.
ADMA7004E: An unexpected exception occurred while building the cache entry for {0} and {1}. The exception is: {2}. All the related binaries might not be changed.
ADMA7005E: An unexpected exception occurred while loading resource {0} from the repository. This error causes problems in using this resource for application synchronization logic.
ADMA7006E: An unexpected exception occurred in onChangeCompletion processing: {0}
ADMA7007E: An unexpected exception occurred in postProcess processing ID={1}: {0}
ADMA7008E: An unexpected exception occurred for the expandEar command. The enterprise archive (EAR) file {0} is not extracted in the following paths {1}. Exception: {2}
ADMA7009E: An exception {0} occurred when deleting directory {1}
ADMA7010E: An unexpected exception occurred when calling an external security provider at application installation time {0}. The exception is {1}
ADMA7011E: An unexpected exception occurred when calling an external security provider at application uninstallation time {0}. The exception is {1}
ADMA7012E: An unexpected exception occurred when calling an external security provider at application uninstallation time. The exception is {0}
ADMA7013W: Enabling the Cluster ripple option requires that you also enable the Distribute binaries option.
ADMA7014E: The Cluster ripple option cannot be specified when the target cluster is on node: {0} which has auto-sync enabled.
ADMA7015W: Unexpected exception {0} in {1} for fileURI {2}. This file might not be synchronized properly and the application binaries might not get placed correctly.
ADMA7016W: Unexpected exception {0} in {1} to build VariableMap. This file might not be synchronized properly and the application binaries might not get placed correctly.
ADMA7017W: The event type: {0} is not valid.
ADMA7018W: Malformed file list in {0}. No <file> tag found under <files>.
ADMA7019E: ERROR: {0} value in AppDataMgr for application {1} is not meaningful. AppData creation might fail, application binary may not be placed correctly.
ADMA7020E: Error processing delta files {0}.
ADMA7021I: Distribution of application {0} completed successfully.
ADMA7022E: Distribution of application {0} failed with exception {1}.
ADMA7023E: Distribution of application {0} failed. Task {1} failed.
ADMA7024E: Distribution of application {0} failed. Task {1} failed with exception {2}.
ADMA7030E: Unable to obtain NotificationService MBean in {0} process to emit application distribution notifications.
ADMA7100E: A validation error occurred in task {0}. The reload interval, {1}, is not valid. A reload interval must be an integer from 0 to 2147483647.
ADMA7101E: An unexpected error occurred for the EAR expansion process. The enterprise archive (EAR) file {0} is not extracted in the following paths {1}. On node: {2}
ADMA7102E: Resource conflict detected for resources with the name {0} between application resources in {1} and {2}.
ADMA7103W: Resource conflict detected. Applications {0} and {1} define conflicting resources with the name {2}. The problem must be resolved before the session is saved.
ADMA7104E: Resource conflict detected. Applications {0} and {1} define conflicting resources with the name {2}. The application configuration cannot be saved.
ADMA8000I: Application ripple of application {0} is successful.
ADMA8001E: Application ripple of application {0} failed.
ADMA8002I: Application ripple of application {0} started.
ADMA8003I: Stopping server {0} to perform application ripple of application {1}.
ADMA8004I: Stopped server {0} to perform application ripple of application {1}.
ADMA8005I: Synchronizing node {0} to perform application ripple of application {1}.
ADMA8006I: Synchronized node {0} to perform application ripple of application {1}.
ADMA8007I: Starting server {0} to perform application ripple of application {1}.
ADMA8008I: Started server {0} to perform application ripple of application {1}.
ADMA8009I: Server {0} is not responding. It will not be started during application ripple of application {1}.
ADMA8010I: Server {0} failed to start during application ripple of application {1}.
ADMA8011I: Synchronization of node {0} failed during application ripple of application {1}.
ADMA8012I: Cluster update of node {0} failed during application ripple of application {1}.
ADMA8013I: Application ripple of applications {0} is complete.
ADMA8014I: Application ripple of applications {0} failed.
ADMA8015I: Application ripple of applications {0} failed. The exception is {1}.
ADMA8016I: Application ripple might not be complete. Targets {0} are not found in the repository.
ADMA8017W: Cluster ripple does not function without Synchronize changes with nodes selected.
ADMA8018W: Resources that are assigned to the application are beyond deployment target scope.
ADMA8019E: The resources that are assigned to the application are beyond the deployment target scope. Resources are within the deployment target scope if they are defined at the cell, node, server, or application level when the deployment target is a server, or at the cell, cluster, or application level when the deployment target is a cluster. Assign resources that are within the deployment target scope of the application or confirm that these resources assignments are correct as specified.
ADMA8020I: Applications {1} failed to start during application ripple on server {0}.
ADMA8021I: No target server found for application {1}.
ADMA8022I: Pausing server {0} to perform application ripple of application {1}.
ADMA8023I: Paused server {0} to perform application ripple of application {1}.
ADMA8024I: Resuming server {0} to perform application ripple of application {1}.
ADMA8025I: Resumed server {0} to perform application ripple of application {1}.
ADMA8026I: Server {0} failed to pause. This server will not be resumed during application ripple of application {1}.
ADMA8027I: Server {0} failed to resume during application ripple of application {1}.
ADMA8028I: The {0} application has been successfully expanded on the {1} node.
ADMA8029E: The expansion of the {0} application has failed on the {1} node.
ADMA8030W: The {0} application did not expand on the {1} node within the expected amount of time.
ADMA8031I: The application expansion will occur as a background process on the {0} node.
ADMA8032E: Unable to get the {0} application expansion status on {1} node.
ADMA8033I: The node {0} is already synchronized.
ADMA9000E: You cannot install an application across multiple security domains. Make sure that all the deployment targets belong to the same security domain.
ADMA9001E: Installation of system application < {0} > failed because there is already a system application with that name.
ADMA9002E: Installation of application failed because LightweightLocal is set in {0} and target node is prior to 6.1
ADMA9003E: The {0} destination directory cannot be found in the enterprise archive (EAR) file.
ADMA9004E: The {0} external binding file cannot be found.
ADMA9005E: Cannot associate Access Ids {0} with mapped user/group {1} because of incompatible length.
ADMA9006E: The application failed to install. The {0} application is not licensed to be installed in this server under the {1} product.
ADMA9007I: The application server is running in a restricted mode under the {0} product.
ADMA9008E: The application server is running in a restricted mode. The {0} application management operation is not available in your application server installation.
ADMA9010E: Installation failed due to missing required parameters for properties based configuration.
ADMA9011E: Runtime provisioning component(s) {0} are malformed.
ADMA9012E: {0} is not a valid operation parameter for a full application update.
ADMA9013E: Runtime provisioning component(s) {0} cannot be specified as patterns or contain multiple key-property values.
ADMA9014E: Runtime provisioning component(s) {0} must have a domain of "WebSphere".
ADMA9015E: Runtime provisioning component(s) {0} must have a key of "specname".
ADMA9016E: A validation error occurred in task {0}. No valid value was specified for properties file variable {1}.
ADMA9998W: Unable to delete {0}.
ADMA9999W: Unable to delete {0}. Exception: {1}


Terms and conditions for information centers | Feedback

Last updated: June 12, 2013 12:15 PM EDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.management.resources.AppDeploymentMessages.dita
File name: com.ibm.ws.management.resources.AppDeploymentMessages.html