ADMB

ADMB0001E: The system configuration contains more than one node. The product supports a single node only for the importWasprofile and exportWasprofile commands.

Explanation

This is a restriction of the product.

Action

Do not use this command when there are more than one node in the system configuration.

ADMB0003E: The configuration archive contains more than one node. The product supports single node for importWasprofile and exportWasprofile command.

Explanation

This is a restriction of the product.

Action

Do not use this command where there is more than one node in the configuration archive.

ADMB0005E: Server {1} on Node {0} does not exist.

Explanation

The specified node name or server name are not valid.

Action

Specify a valid node name and server name.

ADMB0007E: Server {0} already exists on node {1}.

Explanation

The importServer command creates a new server based on the server configuration from the archive.

Action

Specify a different server name.

ADMB0008I: The importWasprofile command overwrites the current configuration of the wsprofile profile.

Explanation

This message is for informational purposes only.

Action

No user action is required.

ADMB0009E: The specified node {0} does not exist.

Explanation

The specified node name does not match any node that is defined in the configuration.

Action

Check the spelling of the node name.

ADMB0010E: The deployed application {1} in systemapps.xml in configuration archive does not contain prefix of {0}.

Explanation

The systemapps.xml file in the configuration archive does not contain the specified variable prefix for the application.

Action

Make sure that <deployedApplications> entries in systemapps.xml start with ${WAS_INSTALL_ROOT}.

ADMB0016E: The number of servers in the configuration archive does not match the number of servers in the system configuration. The product only supports importWasprofile for profiles with the same number of servers.

Explanation

The importWasprofile command requires that the number of servers in the configuration archive and the system configuration match.

Action

Only use this command when both system configuration and configuration archive contains the same number of the servers, except for the case that the system configuration contains no server.

ADMB0017E: Either the server names in the configuration archive do not match the server names in the system configuration or the server types in the configuration archive do not match the server types in the system configuration. The product only supports importWasprofile for profiles with the same amount of servers with the same server names and types.

Explanation

The importWasprofile command requires that the names and the types of servers in the configuration archive to match the names and the types of servers in the system configuration.

Action

Only use this command when the names and the types of all the servers are the same between the configuration archive and the system configuration.

ADMB0018E: Either targetNodeName or targetServerName is missing or targetClusterName is missing for the importApplicationFromWasprofile command.

Explanation

The importApplicationsFromWasprofile command requires either both targetNode and targetServerName parameters or only targetClusterName parameter.

Action

Specify both targetNodeName and targetServerName parameters or targetClusterName parameter for the importApplicationsFromWasprofile command.

ADMB0019E: Target node {0} does not exist.

Explanation

The node specified with targetNodeName does not exist in the target configuration.

Action

Specify a valid target node name.

ADMB0020E: Target server {1} on target node {0} does not exist.

Explanation

The server specified with targetServerName does not exist in the specified node of the target configuration.

Action

Specify a valid target node name and server name.

ADMB0021E: The server {0}/{1} specified for the target configuration is a cluster member server.

Explanation

The importApplicationsFromWasprofile does not support application import on a cluster member server.

Action

Do not specify a cluster member server as a target server for the importApplicationsFromWasprofile command.

ADMB0022E: The server {0}/{1} specified for the target configuration is not an application server.

Explanation

The importApplicationsFromWasprofile only supports application import on an applicaiton server.

Action

Specify an application server as a target server for the importApplicationsFromWasprofile command.

ADMB0023E: An application server named {0} does not exist in the configuration archive file.

Explanation

The application server chosen as the source server does not exist in the configuration archive file.

Action

Specify a valid server name for the source server.

ADMB0024E: The server {0} specified for the source server is not an application server.

Explanation

The importApplicationsFromWasprofile only supports application import from an applicaiton server.

Action

Specify an application server as a source server for the importApplicationsFromWasprofile command.

ADMB0025E: Application {0} is already installed in the target cell.

Explanation

The application cannot be imported because it is already installed in the target cell.

Action

Remove or rename the application either in the target cell or in the configuration archive file.

ADMB0026E: TargetClusterName parameter cannot be used with TargetNodeName and TargetServerName parameters.

Explanation

Applications can be deployed either to an application server or to a cluster server, but not to both.

Action

Use both targetNodeName and targetServerName parameters or targetClusterName parameter as a target server which applications are deployed to.

ADMB0027E: Target cluster {1} does not exist.

Explanation

The cluster specified with targetClusterName does not exist in the specified node of the target configuration.

Action

Specify a valid target cluster name.

ADMB0028E: A server cluster named {0} does not exist in the configuration archive file.

Explanation

The server cluster chosen as the source server cluster does not exist in the configuration archive file.

Action

Specify a valid server name for the source server.