Express (Distributed operating systems), v8.0 > Reference > Messages
WASX
WASX7001I: wsadmin is the executable for WebSphere scripting.
Syntax:
wsadmin
[ -h(elp) ]
[ -? ]
[ -c <command> ]
[ -p <properties_file_name>]
[ -profile <profile_script_name>]
[ -f <script_file_name>]
[ -javaoption java_option]
[ -lang language]
[ -wsadmin_classpath class path]
[ -profileName profile]
[ -conntype
SOAP
[-host host_name]
[-port port_number]
[-user userid]
[-password password] |
RMI
[-host host_name]
[-port port_number]
[-user userid]
[-password password] |
JSR160RMI
[-host host_name]
[-port port_number]
[-user userid]
[-password password] |
IPC
[-ipchost host_name]
[-port port_number]
[-user userid]
[-password password] |
NONE
]
[ -jobid <jobid_string>]
[ -tracefile <trace_file>]
[ -appendtrace <true/false>]
[ script parameters ]
Where "command" is a command to be passed to the script processor;
"properties_file_name" is a java properties file to be used;
"profile_script_name" is a script file to be run before the
main command or file;
"script_file_name" is a command to be passed to the script processor;
"java_option" is a java standard or non-standard option to be passed
to the java program;
"language" is the language to be used to interpret scripts;
supported values are "jacl" and "jython".
"classpath" is a class path to be appended to built-in one;
"-conntype" specifies the type of connection to be used;
the default argument is "SOAP"
a conntype of "NONE" means that no server connection is made
and certain operations will be performed in local mode;
"host_name" is the host used for the SOAP or RMI connection;
the default is the local host;
"port_number" is the port used for the SOAP or RMI connection;
"userid" is the userid required when the server is running in
secure mode;
"password" is the password required when the server is running in
secure mode;
"script parameters" is anything else on the command line. These
are passed to the script in the argv variable; the number of
parameters is available in the argc variable.
"jobid_string" is a jobID string to be used to audit each invocation
of wsadmin;
"trace_file" is the log file name and location where wsadmin trace
output is directed;
If no command or script is specified, an interpreter shell is
created for interactive use.To leave an interactive scripting session,
use the the "quit" or "exit" commands.
Several commands, properties files, and profiles may be specified
on a single command line. They are processed and run in
order of their specification.
Explanation This message is for informational purposes only. Action No action is required.
WASX7002E: "-c" option must be followed by a command.
Explanation The wsadmin launcher has been invoked with the "-c" option. This option requires that a string be supplied to be interpreted as a wsadmin command. Action Reissue the wsadmin command with a command string following the -c option.
WASX7003E: "{0}" option must be followed by a file name.
Explanation The wsadmin launcher has been invoked with an option that requires the name of a file, but no such argument was found. These options are -f, -p, and -profile. Action Reissue the wsadmin command with a file name following the option.
WASX7004E: The "-host" option requires a host name.
Explanation The wsadmin launcher has been invoked with the -host option, but no host name argument was found. Action Specify a host name for the -host option and reissue the wsadmin command.
WASX7005E: The "-port" option requires a port number.
Explanation The wsadmin launcher has been invoked with the -port option, but no port number argument was found. Action Specify a port number for the -port option and reissue the wsadmin command.
WASX7006E: "-lang" option must be followed by a language identifier.
Explanation The wsadmin launcher has been invoked with the -lang option, but no language argument was found. Action Specify a supported scripting language for the -lang option and reissue the wsadmin command.
WASX7007E: "-conntype" option must be followed by connection type information.
Explanation The wsadmin launcher has been invoked with the -conntype option, but no connection type argument was found. Action Specify a connection type for the -conntype option and reissue the wsadmin command. For example, the SOAP, RMI, or NONE connection types are valid values for the -conntype option.
WASX7008E: {0} connection type requires an integer port; found: "{1}"
Explanation The wsadmin launcher has been invoked with the -port option, but the string following -port is not an integer. Action Specify an integer port argument for the -port option and reissue the wsadmin command.
WASX7009E: The "{0}" connection type requires that a port be specified in a properties file or with "-port" on the command line.
Explanation The wsadmin launcher cannot determine what port number should be used when a connector is created. Action Specify a -port option on the wsadmin command line or a com.ws.scripting.port property in the wsadmin.properties file.
WASX7010E: Invalid connection type "{0}." Valid types are "SOAP," "RMI," "NONE," and "JMS."
Explanation The connection type was supplied on the command line -conntype option or in the com.ws.scripting.connectionType property in the wsadmin.properties file is not valid. Action Correct the connection type on the command line or properties file. Specify "SOAP," "RMI," or "NONE."
WASX7011E: Cannot find file "{0}"
Explanation The wsadmin launcher has been invoked with an option that requires the name of a file, but the file cannot be found. Action Correct the name of the file specified by the -p, -f, or -profile option, or in a wsadmin.properties file.
WASX7012E: Exception received while loading properties file {0}; exception information: "{1}"
Explanation During wsadmin initialization, a properties file could not be loaded. Action Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems.
WASX7013E: Cannot determine scripting language for file: "{0}" -- please specify "-lang" option on the command line.
Explanation The wsadmin tool cannot determine which scripting language to use for the specified file. Action Specify a value for the -lang option on the wsadmin command line, or com.ibm.ws.scripting.defaultLang property in the wsadmin.properties file.
WASX7014E: Cannot determine scripting language to use in interactive mode -- please specify "-lang" option on the command line.
Explanation The wsadmin tool cannot determine which scripting language to use for an interactive session. Action Specify a value for the -lang option on the wsadmin command line, or com.ibm.ws.scripting.defaultLang property in the wsadmin.properties file.
WASX7015E: Exception running command: "{0}"; exception information:
{1}
Explanation The wsadmin tool cannot run interactive mode for the specified command. Action Examine the accompanying exception information to determine the appropriate action.
WASX7016E: Exception received while reading file "{0}"; exception information: {1}
Explanation An IO exception occurred while reading a script or profile. Action Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system, and that there are no file permission problems.
WASX7017E: Exception received while running file "{0}"; exception information: {1}
Explanation The script or profile cannot run. The wsadmin tool created an exception. Action Examine the wsadmin.traceout log file to determine the problem.
WASX7018E: Language "{0}" is not registered to BSF.
Explanation An unsupported scripting language was specified. Action Specify a supported scripting language with the -lang option or com.ibm.ws.scripting.defaultLang option.
WASX7019E: No connection type specified; use "-conntype" on the command line.
Explanation The wsadmin tool requires connection type information. Specify the connection type with the -conntype command line option or the com.ibm.ws.scripting.connectionType property in wsadmin.properties. Action Specify a valid connection type with the -conntype command line option or the com.ibm.ws.scripting.connectionType property in wsadmin.properties.
WASX7020E: The "{0}" connection type requires that a host be specified in a properties file or with "-host" on the command line.
Explanation A host must be specified for the connection type. Action Specify a valid host with the -host command line option or the com.ibm.ws.scripting.host property in wsadmin.properties.
WASX7021E: Cannot determine scripting language for command invocation -- please specify "-lang" option on the command line.
Explanation The wsadmin tool cannot determine which scripting language to use with the -c option. Action Specify a supported scripting language with the -lang option on the wsadmin command line, or com.ibm.ws.scripting.defaultLang property in the wsadmin.properties file.
WASX7022E: Problem running command "{0}" -- exception information: {1}
Explanation The wsadmin tool created an exception when executing the command. Action Examine the exception information provided in the message to determine the appropriate user action.
WASX7023E: Error creating "{0}" connection to host "{1}"; exception information: {2}
Explanation The connector did not establish a connection to the host. Action Examine the accompanying exception information and the information in the wsadmin.traceout file to determine the cause of the error.
WASX7024E: Error creating "{0}" connection to host "{1}"; ensure that the correct IPC host is specified in the wsadmin.properties file or with "-ipchost" on the command line; exception information: {2}
Explanation The connector did not establish a connection to the host. Action Examine the accompanying exception information and the information in the wsadmin.traceout file to determine the cause of the error.
WASX7025E: Error found in String "{0}"; cannot create ObjectName.
Explanation The wsadmin tool did not create the ObjectName object because a string was incorrectly formatted. Action Verify that the string is not empty and that it is correctly formatted for an ObjectName string.
WASX7026W: String "{0}" corresponds to {1} different MBeans; returning first one.
Explanation The AdminControl getConfigId or completeObjectName command cannot run because the ObjectName template that has been specified matches two or more running MBeans. This informational message indicates that the first matching MBean will be used. Action Verify that first matching MBean is correct. Otherwise, specify the desired MBean and reissue the command.
WASX7027I: The AdminControl object enables the manipulation of MBeans running
in a WebSphere server process. The number and type of MBeans available
to the scripting client depends on the server to which the client is
connected. If the client is connected to a Deployment Manager, then
all the MBeans running in the Deployment Manager are visible as are all
the MBeans running in the Node Agents connected to this Deployment
Manager, and all the MBeans running in the application servers on those
nodes.
The following commands are supported by AdminControl; more detailed
information about each of these commands is available by using the
"help" command of AdminControl and supplying the name of the command
as an argument.
Note that many of these commands support two different sets of
signatures: one that accepts and returns strings, and one low-level
set that works with JMX objects like ObjectName and AttributeList.
In most situations, the string signatures are likely to be more useful,
but JMX-object signature versions are supplied as well. Each of these
JMX-object signature commands has "_jmx" appended to the command name.
Hence there is an "invoke" command, as well as a "invoke_jmx" command.
completeObjectName
Returns a String version of an object name given a template
name
getAttribute_jmx
Given ObjectName and name of attribute, returns value of
attribute
getAttribute Given String version of ObjectName and name of attribute,
returns value of attribute
getAttributes_jmx
Given ObjectName and array of attribute names, returns
AttributeList.
getAttributes Given String version of ObjectName and attribute names,
returns String of name pairs. Given String version
of ObjectName, returns String of all name pairs.
getCell Returns the cell name of the connected server
getConfigId Given String version of ObjectName, return a configuration
ID for the corresponding configuration object, if any
getDefaultDomain
Returns "WebSphere"
getDomainName Returns "WebSphere"
getHost Returns String representation of connected host
getMBeanCount Returns number of registered beans
getMBeanInfo_jmx
Given ObjectName, returns MBeanInfo structure for MBean
getNode Returns the node name of the connected server
getObjectInstance
Given String version of ObjectName, returns ObjectInstance
object that match.
getPort Returns String representation of port in use
getType Returns String representation of connection type in use
help Shows help information
invoke_jmx Given ObjectName, name of method, array of parameters and
signature, invokes method on MBean specified
invoke Invokes a method on the specified MBean
isRegistered_jmx
Returns true if supplied ObjectName is registered
isRegistered Returns true if supplied String version of ObjectName is
registered
makeObjectName Returns an ObjectName built with the given string
queryNames_jmx Given ObjectName and QueryExp, retrieves set of ObjectNames
that match.
queryNames Given String version of ObjectName, retrieves String of
ObjectNames that match
queryMBeans Given String version of ObjectName, returns a set of
ObjectInstances object that match
reconnect Reconnects with server
setAttribute_jmx
Given ObjectName and Attribute object, sets attribute for MBean
specified
setAttribute Given String version of ObjectName, attribute name and
attribute value, sets attribute for MBean specified
setAttributes_jmx
Given ObjectName and AttributeList object, sets attributes for
the MBean specified
setAttributes Given String version of ObjectName, attribute name
and value pairs, sets attributes for the MBean specified
startServer Given the name of a server, starts that server
stopServer Given the name of a server, stops that server
testConnection Tests the connection to a DataSource object
trace Sets the wsadmin trace specification
Explanation This message is for informational purposes only. Action No action is required.
WASX7028I: The Help object has two purposes:
First, provide general help information for the the objects
supplied by wsadmin for scripting: Help, AdminApp, AdminConfig,
AdminControl and AdminTask.
Second, provide a means to obtain interface information about
MBeans running in the system. For this purpose, a variety of
commands are available to get information about the operations,
attributes, and other interface information about particular
MBeans.
The following commands are supported by Help; more detailed
information about each of these commands is available by using the
"help" command of Help and supplying the name of the command
as an argument.
attributes Given an MBean, returns help for attributes
operations Given an MBean, returns help for operations
constructors Given an MBean, returns help for constructors
description Given an MBean, returns help for description
notifications Given an MBean, returns help for notifications
classname Given an MBean, returns help for classname
all Given an MBean, returns help for all the above
help Returns this help text
AdminControl Returns general help text for the AdminControl object
AdminConfig Returns general help text for the AdminConfig object
AdminApp Returns general help text for the AdminApp object
AdminTask Returns general help text
wsadmin Returns general help text for the wsadmin script
launcher
message Given a message id, returns explanation and user
action message
Explanation This message is for informational purposes only. Action No action is required.
WASX7029I: For help, enter: "$Help help"
Explanation This message is for informational purposes only. Action No action is required.
WASX7030I: For help, enter: "Help.help()"
Explanation This message is for informational purposes only. Action No action is required.
WASX7031I: For help, enter: "print Help.help()"
Explanation This message is for informational purposes only. Action No action is required.
WASX7032I: Method: getHost
Arguments: none
Description: Returns the host to which the scripting process is
connected.
Explanation This message is for informational purposes only. Action No action is required.
WASX7033I: Method: getPort
Arguments: none
Description: Returns the port used for scripting connection.
Explanation This message is for informational purposes only. Action No action is required.
WASX7034I: Method: reconnect
Arguments: none
Description: Reconnects with the server
Explanation This message is for informational purposes only. Action No action is required.
WASX7035I: Method: isAlive
Arguments: none
Description: Is the client session alive?
Explanation This message is for informational purposes only. Action No action is required.
WASX7036I: Method: queryNames
Arguments: object name
Description: Returns a String containing the ObjectNames that match
the input object name, which may be a wild card.
Explanation This message is for informational purposes only. Action No action is required.
WASX7037I: Method: getMBeanCount
Arguments: none
Description: Returns number of registered beans
Explanation This message is for informational purposes only. Action No action is required.
WASX7038I: Method: getDomainName
Arguments: none
Description: returns "WebSphere"
Explanation This message is for informational purposes only. Action No action is required.
WASX7039I: Method: getDefaultDomain
Arguments: none
Description: returns "WebSphere"
Explanation This message is for informational purposes only. Action No action is required.
WASX7040I: Method: getMBeanInfo_jmx
Arguments: object name (type ObjectName)
Description: Returns the MBeanInfo structure for the MBean described
by the object name. An easier way to get this information is to use
the "Help" object -- for example, the "operations" command of the Help
object returns information about all the operations supported by the
specified MBean.
Explanation This message is for informational purposes only. Action No action is required.
WASX7041I: Method: isInstanceOf
Arguments: object name, classname
Description: Returns true if MBean described by "object name" is of
the class given by "classname."
Explanation This message is for informational purposes only. Action No action is required.
WASX7042I: Method: isRegistered
Arguments: object name
Description: Returns true if supplied object name is registered.
Explanation This message is for informational purposes only. Action No action is required.
WASX7043I: Method: getAttribute
Arguments: object name, attribute
Description: Returns value of "attribute" for the MBean described by
"object name."
Explanation This message is for informational purposes only. Action No action is required.
WASX7044I: Method: getAttributes
Arguments: object name, attributes
Returns a string listing the values of the attributes named in
"attributes" for the object named by "object name".
Explanation This message is for informational purposes only. Action No action is required.
WASX7045I: Method: setAttribute
Arguments: object name, attribute name, attribute value
Description: Sets the attribute with name "attribute name" to the
value given by "attribute value" for the MBean described by
"object name."
Explanation This message is for informational purposes only. Action No action is required.
WASX7046I: Method: setAttributes
Arguments: object name, attributes
Description: Sets attributes given in "attributes" for the MBean
described by "object name."
Explanation This message is for informational purposes only. Action No action is required.
WASX7047I: Method: invoke
Arguments: object name, operation
Description: Invoke the operation named by "operation" on the MBean
described by "object name." No arguments are passed for the operation.
Method: invoke
Arguments: object name, operation, arguments
Description: Invoke the operation named by "operation" on the MBean
described by "object name" using the parameters described by
"arguments." If no arguments are required for this operation, the
"arguments" parameter may be omitted.
Method: invoke
Arguments: object name, operation, arguments, signature
Description: Invoke the operation named by "operation" on the MBean
described by "object name" using the parameters described by "arguments"
and the signatures described by "signature."
Explanation This message is for informational purposes only. Action No action is required.
WASX7048I: Method: makeObjectName
Arguments: object name
Description: Return an ObjectName object constructed from
the "object name" string.
Explanation This message is for informational purposes only. Action No action is required.
WASX7049I: Method: completeObjectName
Arguments: object name, template
Description: Returns a String version of an object name that matches
the "template." For example, the template might be "type=Server,*"
If there are several MBeans that match the template, the first match
is returned.
Explanation This message is for informational purposes only. Action No action is required.
WASX7050I: Method: trace
Arguments: trace specification
Description: Turns on the trace specified by "trace specification"
in the scripting process.
Explanation This message is for informational purposes only. Action No action is required.
WASX7051I: Method: help
Arguments: none
Description: Displays general help for AdminControl.
Method: help
Arguments: command
Description: Displays help for the AdminControl command specified by
"command."
Explanation This message is for informational purposes only. Action No action is required.
WASX7052I: Method: getType
Arguments: none
Description: Returns connection type used for scripting connection.
Explanation This message is for informational purposes only. Action No action is required.
WASX7053I: The AdminConfig object communicates with the Config Service in a
WebSphere server to manipulate configuration data for a WebSphere
installation. AdminConfig has commands to list, create, remove,
display, and modify configuration data, as well as commands to display
information about configuration data types.
Most of the commands supported by AdminConfig operate in two modes:
the default mode is one in which AdminConfig communicates with the
WebSphere server to accomplish its tasks. A local mode is also
possible, in which no server communication takes place. The local
mode of operation is invoked by bringing up the scripting client with
no server connected using the command line "-conntype NONE" option
or setting the "com.ibm.ws.scripting.connectionType=NONE" property in
the wsadmin.properties.
The following commands are supported by AdminConfig; more detailed
information about each of these commands is available by using the
"help" command of AdminConfig and supplying the name of the command
as an argument.
attributes Shows the attributes for a given type
checkin Checks a file into the the configuration repository
convertToCluster
Converts a server to be the first member of a new ServerCluster
create Creates a configuration object, given a type, a parent, and
a list of attributes, and optionally an attribute name for the
new object
createClusterMember
Creates a new server that is a member of an existing cluster
createDocument Creates a new document in the configuration repository
createUsingTemplate
Creates an object using a particular template type
defaults Displays the default values for attributes of a given type
deleteDocument Deletes a document from the configuration repository
existsDocument Tests for the existence of a document in the configuration
repository
extract Extracts a file from the configuration repository
getCrossDocumentValidationEnabled
Returns true if cross-document validation is enabled
getid Shows the configuration ID of an object, given a string version
of its containment
getObjectName Given a configuration ID, returns a string version of the
ObjectName for the corresponding running MBean, if any
getObjectType Given a configuration ID, returns a string version of the
object type
getSaveMode Returns the mode used when "save" is invoked
getValidationLevel
Returns the validation used when files are extracted from the
repository.
getValidationSeverityResult
Returns the number of messages of a given severity from the
most recent validation
hasChanges Returns true if unsaved configuration changes exist
help Shows help information
installResourceAdapter
Installs a J2C resource adapter with the given rar file name
and an option string in the node
list Lists all configuration objects of a given type
listTemplates Lists all available configuration templates of a given type
modify Changes specified attributes of a given configuration object
parents Shows the objects which contain a given type
queryChanges Returns a list of unsaved files
remove Removes the specified configuration object
required Displays the required attributes of a given type.
reset Discards unsaved configuration changes
resetAttributes Resets value of the specified attributes.
save Commits unsaved changes to the configuration repository
setCrossDocumentValidationEnabled
Sets the cross-document validation enabled mode.
setSaveMode Changes the mode used when "save" is invoked
setValidationLevel
Sets the validation used when files are extracted from the
repository.
show Shows the attributes of a given configuration object
showall Recursively shows the attributes of a given configuration
object, and all the objects contained within each attribute.
showAttribute Displays only the value for the single attribute specified.
types Shows the possible types for configuration
uninstallResourceAdapter
Uninstalls a J2C resource adapter with the given resource
adapter configuration ID.
unsetAttributes Unsets value of the specified attributes.
validate Invokes validation
Explanation This message is for informational purposes only. Action No action is required.
WASX7054I: Method: create
Arguments: type, parent, attributes
Description: Create a configuration object of the type named by
"type," the parent named by "parent," using the attributes supplied by
"attributes."
Method: create
Arguments: type, parent, attributes, parent attribute name,
Description: Create a configuration object of the type named by
"type," the parent named by "parent," using the attributes supplied
by "attributes" and the attribute name in the parent given by
"parent attribute name"
Explanation This message is for informational purposes only. Action No action is required.
WASX7055I: Method: remove
Arguments: config id
Description: Removes the configuration object named by "config id."
Explanation This message is for informational purposes only. Action No action is required.
WASX7056I: Method: list
Arguments: type
Description: Lists all the configuration objects of the type named
by "type."
Method: list
Arguments: type, scope
Description: Lists all the configuration objects of the type named
by "type" within the scope of the configuration object named by "scope."
Method: list
Arguments: type, pattern
Description: Lists all the configuration objects of the type named
by "type" matching with the wildcard "pattern".
Explanation This message is for informational purposes only. Action No action is required.
WASX7057I: Method: show
Arguments: config id
Description: Displays all the attributes for the configuration object
named by "config id."
Method: show
Arguments: config id, attribute list
Description: Displays the attributes specified in "attribute list"
for the configuration object named by "config id."
Explanation This message is for informational purposes only. Action No action is required.
WASX7058I: Method: modify
Arguments: config id, attributes
Description: Changes the attributes specified by "attributes" for
the configuration object named by "config id."
Explanation This message is for informational purposes only. Action No action is required.
WASX7059I: Method: getConfigId
Arguments: object name
Description: Returns a configuration ID for the configuration object that
corresponds to the MBean named by "object name." This function
communicates with the configuration service to look up a configuration ID that
can be used by AdminConfig. If no configuration object exists that
corresponds to the supplied object name string, getConfigId returns an
empty string.
The object name string supplied as input to this function may be a
wildcard -- for example:
"type=Server,*"
In this case, getConfigId returns the configuration ID of the first matching
object found. Message WASX7026W is also displayed as a warning.
Explanation This message is for informational purposes only. Action No action is required.
WASX7060I: Method: contents
Arguments: type
Description: Displays the object types that can be contained in "type."
Explanation This message is for informational purposes only. Action No action is required.
WASX7061I: Method: attributes
Arguments: type
Description: Displays all the possible attributes contained by an
object of type "type." The attribute types are also displayed; when
the attribute represents a reference to another object, the type of
the tattribute has a suffix of "@." When the attribute represents a
collection of objects, the type is listed with a suffix of "*." If the
type represents a base type, possible subtypes are listed after the
base type in parenthesis. If the type is an enumeration, it is listed
as "ENUM," followed by the possible values in parentheses.
Explanation This message is for informational purposes only. Action No action is required.
WASX7062I: Method: help
Arguments: none
Description: Display general help for AdminApp.
Method: help
Arguments: method or option
Description: Display help for the AdminApp method or option specified
by String.
Explanation This message is for informational purposes only. Action No action is required.
WASX7063E: Error creating "{0}" connection to server: server may not be running; connector properties: {1}; exception information: {2}
Explanation The connector did not establish a connection to the server. Action Examine the accompanying exception information and the information in the wsadmin.traceout file to determine the cause of the error. The server might not be running.
WASX7068I: Method: types
Arguments: none
Description: Displays all the possible top-level configuration
object types.
Method: types
Arguments: pattern
Description: Displays all the possible top-level configuration
object types matching with the wildcard "pattern".
Explanation This message is for informational purposes only. Action No action is required.
WASX7070E: The configuration service is not available.
Explanation The AdminConfig command did not start because the wsadmin process is not connected to a server with a running config service. Action Specify a server with a running configuration services and reissue the wsadmin command.
WASX7072E: The control service is not available.
Explanation The wsadmin tool is initialized but cannot connect to a server. Action Reissue the wsadmin command to create a server connection.
WASX7073E: Attempt to reconnect to the server failed for the following objects: {0}; server may no longer be running.
Explanation The AdminControl reconnect command did not reconnect to the server. Action Examine the accompanying exception information and the information in the wsadmin.traceout file to determine the cause of the error. The server might not be running.
WASX7074I: Reconnect of {0} connector to host {1} completed.
Explanation The AdminControl reconnect command completed successfully. Action No action is required.
WASX7077E: Incomplete config id: need closing parenthesis in "{0}"
Explanation The wsadmin tool did not recognize the configuration ID that has been specified for an AdminConfig command. No closing parenthesis was found. Action Specify a valid configuration ID using one of two forms: name(uri) or (uri).
WASX7078E: Missing config id: no id found in "{0}"
Explanation The wsadmin tool did not recognize the configuration ID that has been specified for an AdminConfig command. No opening parenthesis was found. Action Specify a valid configuration ID using one of two forms: name(uri) or (uri).
WASX7079E: Unable to determine attribute information for type "{0}"
Explanation The wsadmin tool cannot process an attribute that has been specified on an AdminConfig command. Action This exception is unexpected. The cause is not immediately known.
WASX7080E: Invalid attributes specified for type "{0}" -- "{1}"
Explanation An attribute name that has been specified for the given type is not valid. Action Specify a valid attribute name. Run the AdminConfig attributes command for a list of valid attribute names.
WASX7081E: Error obtaining enum information: exception information: "{0}"
Explanation The wsadmin tool could not initialize an enum attribute. Action This exception is unexpected. The cause is not immediately known.
WASX7082E: The creation of a {1} in a {0} object requires that an attribute name be specified, because more than one attribute exists with the same type. Please specify one of the following attribute names as a fourth parameter to the "create" method: {2}
Explanation When an object is created with AdminConfig, wsadmin determines what attribute name to use for the new object in the parent. In certain cases, wsadmin.sh cannot determine this information if the parent object contains more than one attribute of the type being created. Action Use the AdminConfig create command that uses four parameters. As a fourth parameter, supply one of the attribute names supplied in this message.
WASX7083E: Cannot find config object: "{0}"
Explanation The wsadmin tool cannot find the configuration object specified by an AdminConfig command. Action Specify a valid configuration object.
WASX7084E: No help available for : "{0}"
Explanation No help is available for the argument that has been specified with the help <argument> command. Action Verify that the argument is a valid argument for help. Reissue the "help" command without the argument for a list of valid options.
WASX7085I: Method: getid
Arguments: containment path
Description: Returns the configuration ID for an object described by the
given containment path -- for example, /Node:myNode/Server:s1/JDBCProvider:jdbc1/
Explanation This message is for informational purposes only. Action No action is required.
WASX7086E: Unable to determine relationship information for type "{0}"
Explanation The wsadmin tool could not run an AdminConfig parents command. Action This exception is unexpected. The cause is not immediately known.
WASX7087E: Invalid value for attribute "{0}" -- valid values are "{1}"
Explanation The value specified for an AdminConfig create or modify command attribute of some ENUM type is not a valid value. Action Specify one of the valid values for the ENUM attribute. See the WASX7087E error message for the possible values.
WASX7088E: Invalid numeric value specified for attribute "{0}"
Explanation An attribute specified by an AdminConfig create or modify command requires a numeric data type. Action Specify a numeric value for the attribute.
WASX7090I: Executing command: "{0}"
Explanation Informational message logging that this command was invoked. Action No action is required.
WASX7091I: Executing script: "{0}"
Explanation Informational message logging that this script was invoked. Action No action is required.
WASX7092I: Command not logged; contains a password.
Explanation This informational message is logged instead of WASX7090I if the command appears to contain a password. Action No action is required.
WASX7093I: Issuing message: "{0}"
Explanation This informational message is logged when the subject message is displayed to the user. Action No action is required.
WASX7094I: Method: parents
Arguments: type
Description: Displays the object types that can contain "type."
Explanation This message is for informational purposes only. Action No action is required.
WASX7095I: The AdminApp object allows application objects to be manipulated
-- this includes installing, uninstalling, editing, and listing. Most
of the commands supported by AdminApp operate in two modes: the default
mode is one in which AdminApp communicates with the WebSphere server to
accomplish its tasks. A local mode is also possible, in which no
server communication takes place. The local mode operation is invoked
by bringing up the scripting client with no server connected using the
command line "-conntype NONE" option tor setting the
"com.ibm.ws.scripting.connectionType=NONE" property in the
wsadmin.properties.
The following commands are supported by AdminApp; more detailed
information about each of these commands is available by using the
"help" command of AdminApp and supplying the name of the command
as an argument.
deleteUserAndGroupEntries
Deletes all the user/group information for all the roles and
all the user name/password information for RunAs roles for a
given application
edit Edits the properties of an application
editInteractive Edits the properties of an application interactively
export Exports application to a file
exportDDL Exports DDL from application to a directory
exportFile Exports content of a single file from an application to a file
getDeployStatus Returns the combined Deployment status of the application
help Shows help information
install Installs an application, given a file name and an option string
installInteractive
Installs an application in interactive mode, given a file name
and an option string
isAppReady Checks whether the application is ready to be run
list Lists all installed applications
listModules Lists the modules in a specified application
options Shows the options available, for a given file, application,
or in general
publishWSDL Publishs WSDL files for a given application
searchJNDIReferences
Lists application that refers to the given JNDIName on a given
node
taskInfo Shows detailed information pertaining to a given install task
for a given file
uninstall Uninstalls an application, given an application name and
an option string
update Updates an installed application
updateAccessIDs Updates the user/group binding information with accessID
from user registry for a given application
updateInteractive Updates an installed application interactively
view Views an application or module, given an application or
module name
Explanation This message is for informational purposes only. Action No action is required.
WASX7096I: Method: install
Arguments: filename, options
Description: Installs the application in the file specified by
"filename" using the options specified by "options". All required
information must be supplied in the options string; no prompting is
performed.
The AdminApp "options" command may be used to get a list of all
possible options for a given ear file. The AdminApp "help" command
may be used to get more information about each particular option.
Explanation This message is for informational purposes only. Action No action is required.
WASX7097I: Method: installInteractive
Arguments: filename, options
Description: Installs the application in the file specified by
"filename" using the options specified by "options". The user is
prompted for information about each relevant task.
The AdminApp "options" command may be used to get a list of all
possible options for a given ear file. The AdminApp "help" command
may be used to get more information about each particular option.
Method: installInteractive
Arguments: filename
Description: Installs the application specified by "filename" using
default options. The user is prompted for information about each
relevant task.
Explanation This message is for informational purposes only. Action No action is required.
WASX7098I: Method: options
Arguments: none
Description: Displays the general options available for every
application to be installed.
Method: options
Arguments: filename
Description: Displays all the options available for installing the
application in the file specified by "filename".
Method: options
Arguments: appname
Description: Displays all the options available for editing the
application specified by "appname".
Method: options
Arguments: modulename
Description: Displays all the options available for editing the
application module specified by "modulename".
Method: options
Arguments: filename, operation
Description: Displays all the options available for the
file specified by "filename" using the specified operation.
Valid operations are "installapp", "updateapp", "addmodule",
and "updatemodule".
Explanation This message is for informational purposes only. Action No action is required.
WASX7099I: Method: taskInfo
Arguments: filename, taskname
Description: Runs default bindings for the application specified
by "filename" and displays detailed information about the install task
specified by "taskname"
Explanation This message is for informational purposes only. Action No action is required.
WASX7100I: Method: list
Arguments: none
Description: Lists all installed applications
Method: list
Arguments: target scope
Description: List installed applications on a given "target scope"
For example, WebSphere:cell=myCell,node=myNode,server=myServer or
WebSphere:cell=myCell,cluster=myCluster.
Explanation This message is for informational purposes only. Action No action is required.
WASX7102I: Method: uninstall
Arguments: application name, options
Description: Uninstalls application named by "application name" using
the options supplied by "options".
Method: uninstall
Arguments: application name
Description: Uninstalls the application specified by
"application name" using default options.
Explanation This message is for informational purposes only. Action No action is required.
WASX7103I: Method: editInteractive
Arguments: application name, options
Description: Edits the application specified by "application name"
using the options specified by "options". The user is prompted for
information about each relevant task.
Method: editInteractive
Arguments: application name
Description: Edits the application specified by "application name."
The user is prompted for information about each relevant task.
Explanation This message is for informational purposes only. Action No action is required.
WASX7104I: Method: edit
Arguments: application name, options
Description: Modifies the application specified by "application name"
using the options specified by "options". The user is not prompted for
any information.
Explanation This message is for informational purposes only. Action No action is required.
WASX7105I: The following install options are valid for any ear file:
Explanation The wsadmin tool displays this informational message in response to an AdminApp options command. Action No action is required.
WASX7106E: Unable to determine root of WebSphere installation. Please specify the "{0}" option on the command line.
Explanation An AdminApp command is invoked in the local mode, but wsadmin cannot determine the installation root for WebSphere. Action The wsadmin.bat or wsadmin.sh launcher should set the server.root property. If you modified this launcher, correct the changes. If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
WASX7107E: Invalid options specified: "{0}"; valid options are:
{1}
Explanation One or more options that were specified for an AdminApp or AdminConfig command is not valid. Action Check the spelling of the options; correct or remove any incorrect options and reissue the command.
WASX7108E: Invalid data specified for install task: "{0}." Errors are: "{1}"
Explanation The data is not valid for an AdminApp install command for the specified task. Action Examine the errors reported for this task and correct the install command.
WASX7109E: Insufficient data for install task "{0}"
Explanation The data is not complete for an AdminApp install command for the specified task. Action Invoke the AdminApp taskInfo command for this file and task name to determine what information is needed for the task.
WASX7110E: Incorrect number of elements in option: "{0}" for task: "{1};" number of elements should be {2}.
Explanation The data is not valid for an AdminApp install command for the specified task. The task consists of some number of items, but a different number has been supplied. Action Invoke the AdminApp taskInfo command for this file and task name to determine what information is needed for the task.
WASX7111E: Cannot find a match for supplied option: "{0}" for task "{1}"
Explanation =The data is not valid for an AdminApp install command for the specified task. The task consists of some number of items, some of which cannot be changed. The unchangeable items are a key for the data must exactly match the information included in an install command for this task. Action Invoke the AdminApp taskInfo command for this file and task name to determine what information is needed for the task.
WASX7112I: The following options are valid for "{0}"
Explanation This informational message displays in response to an AdminApp options command. Action No action is required.
WASX7113E: Task "{0}" not valid; valid tasks are "{1}"
Explanation The task name is not valid for the AdminApp taskInfo command that has been invoked. Action Specify a valid task name as described in the WAS7113E message output.
WASX7114E: Cannot create temporary file in directory "{0}"
Explanation The wsadmin tool cannot copy the ear file to a temporary location for AdminApp processing. Action Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system, and that there are no file permission problems.
WASX7115E: Cannot read input file "{0}"
Explanation The wsadmin tool cannot read the ear file when preparing to copy it to a temporary location for AdminApp processing. Action Examine the wsadmin.traceout log file to determine the problem. Verify that the file path is correct and that there are no file permission problems.
WASX7116E: Cannot copy file "{0}" to file "{1}"
Explanation The wsadmin tool cannot copy the ear file to a temporary location for AdminApp processing. Action Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems.
WASX7118I: Changes have been made to the configuration, but these changes have not been saved.
Enter "quit" or "exit" to terminate this session without saving your changes.
To save the changes, invoke the "save" command on the AdminConfig object.
Explanation The user requested to terminate an interactive scripting session, but configuration changes have not yet been saved. Commit the unsaved changes. Action To exit the scripting session without saving your changes, respond with "quit" or "exit." Any other response keeps the session active. Use the AdminConfig save command to commit any unsaved changes.
WASX7119E: Invalid option "{0}." Valid options are "overwriteOnConflict," and "rollbackOnConflict."
Explanation The mode that has been specified with the AdminConfig setSaveMode command is not valid. Action Specify a valid save mode. The valid options are "overwriteOnConflict" and "rollbackOnConflict".
WASX7120E: Diagnostic information from exception with text "{0}" follows:
{1}
Explanation The wsadmin tool created an exception. Action Examine the exception information in the log file to determine the source of the problem.
WASX7121E: "{0}" found instead of expected '{'. {1}
Explanation The wsadmin tool found the specified string when '{' was expected in the input stream. Action Correct and reissue the command.
WASX7122E: Expected "{0}" not found. {1}
Explanation The wsadmin tool did not find the specified string in the expected location in the input stream. Action Correct and reissue the command.
WASX7123E: Unexpected "{0}" found. {1}
Explanation The wsadmin tool found the specified character in an unexpected location in the input stream. Action Correct and reissue the command.
WASX7124I: Method: save
Arguments: none
Description: Commits unsaved changes to the configuration repository
Explanation This message is for informational purposes only. Action No action is required.
WASX7125I: Method: reset
Arguments: none
Description: Discard unsaved configuration changes
Explanation This message is for informational purposes only. Action No action is required.
WASX7126I: Method: hasChanges
Arguments: none
Description: Returns true if unsaved configuration changes exist
Explanation This message is for informational purposes only. Action No action is required.
WASX7127I: Method: queryChanges
Arguments: none
Description: Returns a list of unsaved configuration files
Explanation This message is for informational purposes only. Action No action is required.
WASX7128I: Method: setSaveMode
Arguments: save mode
Description: Changes the mode used when "save" is invoked.
Possible values are:
"overwriteOnConflict" to save changes even if they conflict
with other configuration changes; and
"rollbackOnConflict" to cause a save operation to fail if
changes conflict with other configuration changes;
this value is the default.
Explanation This message is for informational purposes only. Action No action is required.
WASX7129E: Cannot create objects of type "{0}" in parents of type "{1}"
Explanation The parent that has been specified with the AdminConfig create command is not valid. Action Specify a valid parent object for the object to create and reissue the command.
WASX7130E: The requested operation is not supported.
Explanation The wsadmin tool created an UnsupportedOperationException exception from an MBean. This exception might result from an AdminControl invoke command. Action Check the spelling of the operation.
WASX7131E: Runtime exception: "{0}"
Explanation The wsadmin tool created a RuntimeMBeanException exception from an MBean. Action Examine the exception information and modify the command.
WASX7132E: Application install for {0} failed: see previous messages for details.
Explanation An AdminApp install command did not run. Action See previous messages for details.
WASX7133E: Application uninstall of {0} failed: see previous messages for details.
Explanation An AdminApp uninstall command did not run. Action See previous messages for details.
WASX7134E: "{0}" option must be specified for war file installation.
Explanation The -contextroot option must be specified for the AdminApp install command for invoking a war file. Action Specify a valid value for the -contextroot option.
WASX7139E: Operation "{0}" has versions that take one of the following number of parameters: {1}; {2} parameters were supplied: "{3}." The "operations" command on the Help object can be used to learn more about the signatures available for "{0}."
Explanation No operation was defined for the AdminControl invoke command that has been issued for an MBean operation. The MBean accepts the same number of parameters specified in the AdminControl invoke command. Action Specify the correct number of parameters and reissue the invoke command. Use the "operations" command for the Help object to learn more about the signatures available for this operation.
WASX7140E: Length mismatch: {0} parameters were specified, but {1} signatures were supplied. The same number must be specified for both.
Explanation A different number of parameters and signature elements have been specified for an AdminControl invoke command. There must be exactly one signature element for every parameter. Action Specify exactly one signature element for every parameter and reissue the invoke command. Alternatively, reissue the command with no signature elements.
WASX7141E: Incorrect trace string supplied: "{0}"
Explanation The trace string that has been specified for an AdminControl trace command is not valid. Action Verify that the trace string is spelled correctly.
WASX7143E: The object with id "{0}" does not exist.
Explanation The wsadmin tool did not process the AdminConfig command because a configuration ID that has been specified does not correspond to an existing configuration object. Action Verify that the id is spelled correctly.
WASX7144I: Method: showall
Arguments: config id
Description: Shows all the attributes for the configuration object
named by "config id." The showall command recursively displays the
contents of all the subobjects contained inside each of the attributes.
Method: showall
Arguments: config id, attribute list
Description: Shows the attributes specified by "attribute list" for
the configuration object named by "config id." The showall command
recursively displays the contents of each specified attribute.
Explanation This message is for informational purposes only. Action No action is required.
WASX7146I: The following configuration files contain unsaved changes:
{0}
Explanation The wsadmin tool displays this informational message in response to the AdminConfig queryChanges command. The command lists the files that have been updated by the scripting client since the last save or reset command. Action No action is required.
WASX7147I: Method: getSaveMode
Arguments: none
Description: Returns the mode used when "save" is invoked.
Possible values are:
"overwriteOnConflict" to save changes even if they conflict
with other configuration changes; and
"rollbackOnConflict" to cause a save operation to fail if
changes conflict with other configuration changes;
this value is the default.
Explanation This message is for informational purposes only. Action No action is required.
WASX7148I: Method: testConnection
Arguments: config id
Description: Tests the connection to a DataSource. The "config id"
argument is the configuration ID of a DataSource object. The DataSource
object passed in has to be saved in the configuration before
attempting to run testConnection.
Explanation This message is for informational purposes only. Action No action is required.
WASX7151I: Method: export
Arguments: application name, filename, options
Description: Exports the application specified by "application name"
to the file specified by "filename" using the options specified by
"options".
Method: export
Arguments: application name, filename
Description: Exports the application specified by "application name"
to the file specified by "filename."
Explanation This message is for informational purposes only. Action No action is required.
WASX7152I: This method is deprecated. Use exportDDL instead.
Explanation This message is for informational purposes only. Action No action is required.
WASX7153I: "cell" option; specifies the cell name for AdminApp install functions.
Explanation This message is for informational purposes only. Action No action is required.
WASX7154I: "node" option; specifies the node name for AdminApp install functions.
Explanation This message is for informational purposes only. Action No action is required.
WASX7155I: "server" option; specifies the server name for AdminApp install functions.
Explanation This message is for informational purposes only. Action No action is required.
WASX7156I: "local" option; specifies that the AdminApp function will be performed in local mode, without communicating with a server.
This option is deprecated. Use "-conntype NONE" in the command line or "com.ws.scripting.connectionType=NONE" in wsadmin.properties to perfrom AdminApp function in local mode.
Explanation This message is for informational purposes only. Action No action is required.
WASX7157I: "depl.extension.reg" option; specifies location of properties file for deployment extensions.
This option is deprecated. There is no replacement for this option.
Explanation This message is for informational purposes only. Action No action is required.
WASX7158I: "usedefaultbindings" option; specifies that default bindings are to used for install. Default is "nousedefaultbindings"
Explanation This message is for informational purposes only. Action No action is required.
WASX7159I: "nousedefaultbindings" option; specifies that default bindings are not used for install; this is the default setting.
Explanation This message is for informational purposes only. Action No action is required.
WASX7160I: "defaultbinding.datasource.jndi" option; specifies the JNDI name for the default datasource
Explanation This message is for informational purposes only. Action No action is required.
WASX7161I: "defaultbinding.datasource.username" option; specifies the user name for the default datasource
Explanation This message is for informational purposes only. Action No action is required.
WASX7162I: "defaultbinding.datasource.password" option; specifies the password for the default datasource
Explanation This message is for informational purposes only. Action No action is required.
WASX7163I: "defaultbinding.cf.jndi" option; specifies the JNDI name for the default connection factory
Explanation This message is for informational purposes only. Action No action is required.
WASX7164I: "defaultbinding.cf.resauth" option; specifies the RESAUTH for the the connection factory.
Explanation This message is for informational purposes only. Action No action is required.
WASX7165I: "defaultbinding.ejbjndi.prefix" option; specifies the prefix for the JNDI name of EJBs.
Explanation This message is for informational purposes only. Action No action is required.
WASX7166I: "defaultbinding.virtual.host" option; specifies the default virtual host name.
Explanation This message is for informational purposes only. Action No action is required.
WASX7167I: "defaultbinding.force" option; specifies that the default bindings should override current bindings.
Explanation This message is for informational purposes only. Action No action is required.
WASX7168I: "defaultbinding.strategy.file" option; specifies a custom default bindings strategy file
Explanation This message is for informational purposes only. Action No action is required.
WASX7169I: "deployejb" option; specifies that EJBDeploy should be run during install; the default is "nodeployejb"
Explanation This message is for informational purposes only. Action No action is required.
WASX7170I: "nodeployejb" option; specifies that EJBDeploy should not be run during install; this is the default setting.
Explanation This message is for informational purposes only. Action No action is required.
WASX7171I: "deployejb.dbname" option; specifies the database name for EJBDeploy; default is"was50."
Explanation This message is for informational purposes only. Action No action is required.
WASX7172I: "deployejb.dbtype" option; specifies the database type for EJBDeploy; valid values are {0}.
Explanation This message is for informational purposes only. Action No action is required.
WASX7173I: "deployejb.dbschema" option; specifies the database schema for EJBDeploy
Explanation This message is for informational purposes only. Action No action is required.
WASX7174I: "deployejb.classpath" option; specifies extra classpath to be used for EJBDeploy
Explanation This message is for informational purposes only. Action No action is required.
WASX7175I: "deployejb.rmic" option; specifies extra RMIC options to be used for EJBDeploy
Explanation This message is for informational purposes only. Action No action is required.
WASX7176I: "deployejb.validate" option; specifies that EJBDeploy should run validation; this is the default setting.
Explanation This message is for informational purposes only. Action No action is required.
WASX7177I: "nodeployejb.validate" option; specifies that EJBDeploy should not run validation; the default setting is "deployejb.validate"
Explanation This message is for informational purposes only. Action No action is required.
WASX7180I: "deployejb.preCompileJSPs" option; specifies that EJBDeploy should pre-compile JSPs; the default setting is "nodeployejb.preCompileJSPs"
Explanation This message is for informational purposes only. Action No action is required.
WASX7181I: "nodeployejb.preCompileJSPs" option; specifies that EJBDeploy should not pre-compile JSPs; this is the default setting.
Explanation This message is for informational purposes only. Action No action is required.
WASX7182I: "distributeApp" option; specifies that the application management component should distribute application binaries. This is the default setting.
Explanation This message is for informational purposes only. Action No action is required.
WASX7183I: "nodistributeApp" option; specifies that the application management component should not distribute application binaries. The default setting is "distributeApp"
Explanation This message is for informational purposes only. Action No action is required.
WASX7184I: "useMetaDataFromBinary" option; use this option to specify that the metadata (such as deployment descriptors, bindings, extensions) that are used at runtime come from the earfile; the default is "nouseMetaDataFromBinary," which means that the metadata used at runtime come from the config repository.
Explanation This message is for informational purposes only. Action No action is required.
WASX7185I: "nouseMetaDataFromBinary" option; use this option to specify that the metadata (such as deployment descriptors, bindings, extensions) that are used at runtime come from the config repository; this is the default setting. Use "useMetaDataFromBinary," to indicate that the metadata used at runtime come from the earfile.
Explanation This message is for informational purposes only. Action No action is required.
WASX7186I: "ddlprefix" option; specifies DDL prefix to use when invoking exportDDL.
Explanation This message is for informational purposes only. Action No action is required.
WASX7187E: Invalid value "{0}" -- possible valid values are "{1}"
Explanation A value that has been specified for an AdminConfig command is not valid. Action Specify a valid value for the AdminConfig command.
WASX7188I: Cross-document validation enablement set to {0}
Explanation An informational message issued in response to invoking the AdminConfig setCrossDocumentValidationEnabled. Action No action is required.
WASX7189I: Validation level set to {0}
Explanation An informational message issued in response to invoking the AdminConfig setValidationLevel. Action No action is required.
WASX7190I: Validation at level {0} with cross-document validation {1}, requested at {2} for action "{3}"
Explanation The wsadmin tool writes this informational message to the validation output file each time validation is requested. Action No action is required.
WASX7193I: Validation results are logged in {0}: Total number of messages: {1}
Explanation Validation is complete. Action Optional- Examine the messages logged in the specified file to see if corrective action is needed.
WASX7194I: Number of messages of severity {0}: {1}
Explanation This message provides a summary of messages generated during configuration validation. Action No action is required.
WASX7195I: Severity {0}; line {1}; target "{2}"; {3}
Explanation The user requested validation. By default, the name of the file is wsadmin.valout, located in the logs directory. Action Fix any configuration problems noted by the previous message.
WASX7196E: Cannot write to validation output file "{0}"
Explanation The wsadmin tool cannot open an output file for validation results. The file exists on the system, but wsadmin.sh cannot write to it. Action Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems.
WASX7197E: Error creating validation output file {0}; exception information: {1}
Explanation The wsadmin tool cannot open an output file for validation results. The wsadmin tool cannot create this file. Action Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems.
WASX7198W: The configuration service is not running. Configuration commands will not run.
Explanation No connection was obtained to the configuration service. Action Restart wsadmin.sh to obtain a server connection.
WASX7199I: Method: validate
Arguments: none
Description: Requests configuration validation results based on the
files in your workspace, the value of the cross-document validation
enabled flag, and the validation level setting.
Method: validate
Arguments: config id
Description: Requests configuration validation results based on the
files in your workspace, the value of the cross-document validation
enabled flag, and the validation level setting. The scope of this
request is the object named by "config id."
Explanation This message is for informational purposes only. Action No action is required.
WASX7200I: Method: setValidationLevel
Arguments: level
Description: Sets the validation level to one of five possibilities:
none, low, medium, high, or highest.
Explanation This message is for informational purposes only. Action No action is required.
WASX7201I: Method: getValidationLevel
Arguments: none
Description: Returns a message giving the current validation level.
Explanation This message is for informational purposes only. Action No action is required.
WASX7202I: Method: setCrossDocumentValidationEnabled
Arguments: flag
Description: Sets the cross-document validation enabled flag to
true or false.
Explanation This message is for informational purposes only. Action No action is required.
WASX7203I: Method: getCrossDocumentValidationEnabled
Arguments: none
Description: Returns a message giving the current cross-document
enablement setting.
Explanation This message is for informational purposes only. Action No action is required.
WASX7204I: Method: getObjectName;
Arguments: config id
Description: Returns a string version of the ObjectName for the MBean
that corresponds to this configuration ID. If there is no such
running MBean this returns an empty string.
Explanation This message is for informational purposes only. Action No action is required.
WASX7205I: Method: listModules
Arguments: application name, options
Description: List the modules in the application specified by
"application name using the options specified by "options". The valid
option is "-server". If "-server" is specified, then the
return value will include the server information on each module.
Method: listModules
Arguments: application name
Description: List the modules in the application specified by
"application name".
Explanation This message is for informational purposes only. Action No action is required.
WASX7206W: The application management service is not running. Application management commands will not run.
Explanation No connection was obtained to the application management service. Action Restart wsadmin.sh to obtain a server connection, or use "-conntype NONE" option to run the local mode.
WASX7208I: Validation settings in effect now: Level={0}, Cross-validation={1}, Output file={2}
Explanation The wsadmin tool is initialized or validation settings have been changed. Action No action is required.
WASX7209I: Connected to process "{0}" on node {1} using {2} connector; The type of process is: {3}
Explanation The wsadmin tool has connected to a server during initialization. Action No action is required.
WASX7210W: Cannot determine type of server; exception information: {0}
Explanation The wsadmin tool cannot determine the type of server to which it is connected. Action Examine the wsadmin.traceout file for additional information.
WASX7211I: Method: listTemplates
Arguments: type
Description: Returns a list of the templates available for the given
type. These templates may be used in invocations of
createUsingTemplate.
Method: listTemplates
Arguments: type, match
Description: Returns a list of the templates with display names
that contain the string specified by "match" available for the given
type. These templates may be used in invocations of
createUsingTemplate.
Method: listTemplates
Arguments: type, pattern
Description: Returns a list of the templates with display names
that contain the string matching with the wildcard "pattern" for the
given type. These templates may be used in invocations of
createUsingTemplate.
Explanation This message is for informational purposes only. Action No action is required.
WASX7212I: Method: createUsingTemplate
Arguments: type, parent, attributes, template
Description: Creates an object of the given type with the given
parent. The specified template is used as the basis for this new
object, and the specified attributes override settings in the template.
The template parameter is a configuration ID of an existing object -- .
this object can be either a template object, returned by using the
listTemplates command, or any other existing object of the correct type.
Explanation This message is for informational purposes only. Action No action is required.
WASX7213I: This scripting client is not connected to a server process; please refer to the log file {0} for additional information.
Explanation The wsadmin tool could not connect to a server using the options supplied on the command line and contained in wsadmin.properties files. Action If a connection is not needed, no action is necessary. Specify the "-conntype NONE" option to indicate that no connection is desired. This option suppresses the WASX7213I message. If a connection is needed, restart wsadmin.sh with connection information that will allow it to connect to a running server. Alternatively, verify that the host and port information is correct.
WASX7214E: Cannot resolve confid id {0}
Explanation More info at:
Action This exception is unexpected. The cause is not immediately known.
WASX7215E: Cannot complete testConnection function because DataSourceCfgHelper MBean is not running. Please check to see if the server started correctly.
Explanation The wsadmin tool needs the DataSourceCfgHelper MBean to perform the testConnection function. The MBean should be running in a server. Action Verify that the wsadmin process is connected to a server and the server is running. If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
WASX7217I: Connection to provided datasource was successful.
Explanation The AdminControl testConnection command was successfully run. The database adapter code reported no errors or warnings. Action No action is required.
WASX7219E: The {0} attribute must be specified if the {1} attribute has the value "{2}"
Explanation There is a constraint on the specified attribute. Action Specify the missing attribute.
WASX7220E: This operation was invoked with the "-local" option, but the scripting client is connected to process "{0}" on node "{1}." Local operations can not be performed when a connection exists to a server. We can either re-run the command without the "-local" option, or invoke the scripting client without servers running.
Explanation The "-local" option is not permitted for AdminApp functions when the scripting client is connected to a server. Action Remove the "-local" option, or use the "-conntype NONE" option to avoid connecting to a server.
WASX7223I: "preCompileJSPs" option; use this option to specify that JSPs are to be precompiled. The default is nopreCompileJSPs.
Explanation This message is for informational purposes only. Action No action is required.
WASX7224I: "nopreCompileJSPs" option; use this option to specify that JSPs are not to be precompiled. This is the default.
Explanation This message is for informational purposes only. Action No action is required.
WASX7225I: "validateApp" option; this option is obsolete
Explanation This message is for informational purposes only. Action No action is required.
WASX7226I: "novalidateApp" option; this option is obsolete
Explanation This message is for informational purposes only. Action No action is required.
WASX7227W: Profile {0} is in the wrong language and will not be executed; language used is {1}
Explanation The wsadmin tool cannot run the profile that has been specified is not in the same scripting language as the scripting session. Action Remove the profile from the wsadmin.properties file or the wsadmin command line options.
WASX7229I: "installdir" option; specifies the directory into which the application binaries should be placed.
This option is deprecated. It is replaced by installed.ear.destination option.
Explanation This message is for informational purposes only. Action No action is required.
WASX7230I: "was.install.root" option; this option is obsolete
Explanation This message is for informational purposes only. Action No action is required.
WASX7231I: "configroot" option; this option is obsolete
Explanation This message is for informational purposes only. Action No action is required.
WASX7232I: "appname" option; use this option to specify the name of the application. The default is to use the display name of the application.
Explanation This message is for informational purposes only. Action No action is required.
WASX7233I: "verbose" option; this option causes additional messages to be displayed during install.
Explanation This message is for informational purposes only. Action No action is required.
WASX7234I: "contextroot" option; use this option to specify the context root to be used when installing a stand-alone war file.
Explanation This message is for informational purposes only. Action No action is required.
WASX7235I: "defaultbinding.virtual.host" option; default name for virtual host.
Explanation This message is for informational purposes only. Action No action is required.
WASX7236I: "remotedir" option; this option is obsolete
Explanation This message is for informational purposes only. Action No action is required.
WASX7237W: The attribute "{0}" has a type that is not supported by the String signatures of AdminControl -- the type is "{1}." AdminControl will attempt to convert the attribute to and from String type, but this may not give the desired result. Use the native JMX object signatures for actions involving this type.
Explanation The AdminControl setAttribute command contains an attribute type that is not supported by the setAttribute command. Action Use the setAttribute_jmx command to set this attribute.
WASX7239E: Unexpected error setting attribute "{0}" of type "{1}" to value "{2}." Additional information may be found in the trace log.
Explanation The wsadmin tool did not invoke the AdminConfig modify or create command. Action Examine the wsadmin.traceout log for more information.
WASX7240I: Resetting workspace at the start of a scripting session; workspace reports unsaved changes in the following files:
{0}
Explanation If a scripting session begins with unsaved changes in the workspace, the workspace resets and the unsaved changes are lost. Action No action is required.
WASX7241I: There are no unsaved changes in this workspace.
Explanation No changes were made to the configuration by this scripting process since the last "save" or "reset" AdminConfig command. Action No action is required.
WASX7242I: "rar.name" option; The "rar.name" option is the name for the J2CResourceAdapter. If it is not specified, then the display name in the RAR's deployment descriptor is used. If that is not specified, then the RAR file name is used.
Explanation This message is for informational purposes only. Action No action is required.
WASX7243I: "rar.desc" option; this option is a description of the J2CResourceAdapter.
Explanation This message is for informational purposes only. Action No action is required.
WASX7244I: "rar.archivePath" option; this option is the name of the path where the file is assume to reside. If this is not specified, then the path is taken to be given by CONNECTOR_INSTALL_ROOT
Explanation This message is for informational purposes only. Action No action is required.
WASX7245I: Method: updateAccessIDs
Arguments: application name, boolean:bAll
Description: Updates the application binding file for an installed
application with access IDs for all the users and groups. Specifying
true for bAll updates all the users/groups even if there are access
IDs already present in the bindings.
Explanation This message is for informational purposes only. Action No action is required.
WASX7246E: Cannot establish "{0}" connection to host "{1}" because of an authentication failure. Ensure that user and password are correct on the command line or in a properties file.
Exception message (if any): "{2}"
Explanation The wsadmin tool did not connect to a server process because it could not authenticate to the server. Action Verify that user and password are correct on the command line or in a properties file.
WASX7247I: Method: deleteUserAndGroupEntries
Arguments: application name
Description: Deletes all the user/group information for all the roles
and RunAs roles for a given application.
Explanation This message is for informational purposes only. Action No action is required.
WASX7249E: The "-user" option requires a user name.
Explanation The wsadmin launcher has been invoked with the -user option, but no user name argument was found. Action Specify a user name for the -user option and reissue the wsadmin command.
WASX7250E: The "-password" option requires a password.
Explanation The wsadmin launcher has been invoked with the -password option, but no password argument was found. Action Specify a password for the -password option and reissue the wsadmin command.
WASX7252E: Unable to locate running server "{0}" on node "{1}".
Explanation The AdminControl stopServer command did not run because a running server of the specified name was not found. Action Verify that the server name is spelled correctly.
WASX7254E: "{0}" action not supported when process type is "{1}"
Explanation The wsadmin tool is connected to the wrong type of process. Action Verify that wsadmin.sh is connected to the correct process.
WASX7255E: Cannot find server "{0}" in configuration data.
Explanation The AdminControl startServer command did not run because the server that has been specified does not exist. Action Verify that the server name is spelled correctly.
WASX7256W: Cannot locate NodeSync object on node "{0}". Unable to synchronize configurations before starting server "{1}"
Explanation The AdminControl startServer invocation did not run because wsadmin.sh cannot locate the NodeSync object on the specified node. Action Examine the logs on the node if the NodeSync object is not running.
WASX7257E: Cannot locate NodeAgent object on node "{0}". Unable to start server "{1}" on that node.
Explanation The AdminControl startServer command did not run because the NodeAgent on the server's node is not running. Action Start the NodeAgent on the appropriate machine.
WASX7258I: Method: startServer
Arguments: server name
Description: Starts a server by locating it in the configuration
and asking that node's NodeAgent to start the server. This command
uses the default wait time of 1200 seconds. Note that this version
of the command can only be used if the scripting process is attached
to a Node Agent server.
Method: startServer
Arguments: server name, wait time
Description: Starts a server by locating it in the configuration,
synchronizing configuration data with the server's node,
and asking that node's NodeAgent to start the server. The start
process waits the number of seconds specified by "waittime"
for the server to start. Note that this version of the command can
only be used if the scripting process is attached to a Node Agent
server.
Method: startServer
Arguments: server name, node name
Description: Starts a server in the specified node by locating it in
the configuration, synchronizing configuration data with the server's
node and asking that node's NodeAgent to start the server. This version
of the command can be used when the scripting process is attached
either to a Node Agent or Deployment Manager process.
Method: startServer
Arguments: server name, node name, wait time
Description: Starts a server in the specified node by locating it in
the configuration, synchronizing configuration data with the server's
node and asking that node's NodeAgent to start the server. The start
process waits the number of seconds specified by "waittime"
for the server to start. This version of the command can be used when
the scripting process is attached either to a Node Agent or Deployment
Manager process.
Explanation This message is for informational purposes only. Action No action is required.
WASX7259I: Method: stopServer
Arguments: server name
Description: Stops a server.
Method: stopServer
Arguments: server name, immediate flag
Description: Stops a server. If the "immediate flag" is set to
"immediate" then a stopImmediate is performed for the specified
server. Otherwise, a normal stop is performed.
Method: stopServer
Arguments: server name, node name
Description: Stops a server in the specified node.
Method: stopServer
Arguments: server name, node name, immediate flag
Description: Stops a server in the specified node. If the
"immediate flag" is set to "immediate" then a stopImmediate
is performed for the specified server. Otherwise, a normal
stop is performed.
Method: stopServer
Arguments: server name, node name, terminate flag
Description: Stops a server on the specified node. If the
"terminate flag" is set to "terminate" then a terminate
is performed for the specified server. Otherwise, a normal stop
is performed.
This operation can only be performed on a Managed Process.
The node name is a required argument.
Explanation This message is for informational purposes only. Action No action is required.
WASX7262I: Start completed for server "{0}" on node "{1}"
Explanation The specified server is started on the specified node. Action No action is required.
WASX7263W: Start not completed for server "{0}" on node "{1}". The server launching process may have timed out.
Explanation The specified server process cannot start. The request has timed out. Action Verify that the server is started.
WASX7264I: Stop completed for server "{0}" on node "{1}"
Explanation The specified server is stopped on the specified node. Action No action is required.
WASX7265W: Stop not completed for server "{0}" on node "{1}". The stop process may have timed out.
Explanation The specified server process cannot stop. The request has timed out. Action Verify that the server is stopped.
WASX7266I: A was.policy file exists for this application; would you like to display it?
Explanation This message is for informational purposes only. Action No action is required.
WASX7267I: Method: help
Arguments: none
Description: Display general help for Help.
Method: help
Arguments: method
Description: Display help for the Help method specified
by String.
Explanation This message is for informational purposes only. Action No action is required.
WASX7268I: Method: attributes
Arguments: MBean
Description: Display information about the attributes of the
specified MBean.
Method: attributes
Arguments: MBean, attribute name
Description: Display information about the specified attribute on
the specified MBean.
Explanation This message is for informational purposes only. Action No action is required.
WASX7269I: Method: operations
Arguments: MBean
Description: Display information about the operations of the
specified MBean.
Method: operations
Arguments: MBean, operation name
Description: Display information about the specified operation on
the specified MBean.
Explanation This message is for informational purposes only. Action No action is required.
WASX7270I: Method: constructors
Arguments: MBean
Description: Display information about the constructors of the
specified MBean.
Explanation This message is for informational purposes only. Action No action is required.
WASX7271I: Method: description
Arguments: MBean
Description: Display the description of the specified MBean.
Explanation This message is for informational purposes only. Action No action is required.
WASX7272I: Method: notifications
Arguments: MBean
Description: Display information about the notifications sent by
the specified MBean.
Explanation This message is for informational purposes only. Action No action is required.
WASX7273I: Method: classname
Arguments: MBean
Description: Display information about the classname of the
specified MBean.
Explanation This message is for informational purposes only. Action No action is required.
WASX7274I: Method: classname
Arguments: MBean
Description: Display information about the attributes,
operations, constructors, description, notifications,
and classname of the specified MBean.
Explanation This message is for informational purposes only. Action No action is required.
WASX7275I: Method: AdminConfig
Arguments: none
Description: Display general help information for the
AdminConfig object provided by wsadmin.
Explanation This message is for informational purposes only. Action No action is required.
WASX7276I: Method: AdminApp
Arguments: none
Description: Display general help information for the
AdminApp object provided by wsadmin.
Explanation This message is for informational purposes only. Action No action is required.
WASX7277I: Method: AdminControl
Arguments: none
Description: Display general help information for the
AdminControl object provided by wsadmin.
Explanation This message is for informational purposes only. Action No action is required.
WASX7278I: Generated command line: {0}
Explanation The installInteractive or editInteractive AdminApp commands returns the previous string that can be modified and copied into a script for use with the install or edit commands. Action If needed, use the command string in a script.
WASX7279E: An application with name "{0}" already exists. Select a different name.
Explanation The AdminApp install command did not run because the specified application name already exists. Action Use the -appname option to specify a different application name.
WASX7280E: An application with name "{0}" does not exist.
Explanation The AdminApp command did not run because the specified application does not exist. Action Verify that the application name is spelled correctly.
WASX7281E: Cannot install application using file "{0}". Ensure that this file exists and is readable.
Explanation The AdminApp command did not run because specified file cannot be used. Action Verify that this file exists and is readable.
WASX7282E: No editing tasks are available for application "{0}"
Explanation The AdminApp edit or editInteractive command did not run because specified application has no valid tasks to edit. Action No action is required.
WASX7283E: This command requires an object of type "{0}", but the specified object "{1}" has type: "{2}"
Explanation An AdminConfig command did not run because a required object must be a specific type. Action Specify an object of the correct type and reinvoke the command.
WASX7284I: Method: createClusterMember
Arguments: cluster id, node id, member attributes
Description: Creates a new Server object on the node specified
by "node id." This Server is created as a new member of the existing
cluster specified by "cluster id," and has attributes specified in
"member attributes." One attribute is required: "memberName."
The Server is created using the default template for
Server objects, and has the name and specified by the
"memberName" attribute.
Method: createClusterMember
Arguments: cluster id, node id, member attributes, template id
Description: Creates a new Server object on the node specified
by "node id." This Server is created as a new member of the existing
cluster specified by "cluster id," and has attributes specified in
"member attributes." One attribute is required: "memberName."
The Server is created using the Server template
specified by "template id," and has the name specified by
the "memberName" attribute.
Explanation This message is for informational purposes only. Action No action is required.
WASX7285I: Method: queryNames_jmx
Arguments: object name (type ObjectName), query (type QueryExp)
Description: Returns a Set containing ObjectNames that match the input
object name and query.
Explanation This message is for informational purposes only. Action No action is required.
WASX7286I: Method: isInstanceOf_jmx
Arguments: object name (type ObjectName), classname (String)
Description: Returns true if the MBean described by "object name" is of
the class given by "classname."
Explanation This message is for informational purposes only. Action No action is required.
WASX7287I: Method: isRegistered_jmx
Arguments: object name (type ObjectName)
Description: Returns true if supplied "object name" is registered.
Explanation This message is for informational purposes only. Action No action is required.
WASX7288I: Method: getAttribute_jmx
Arguments: object name (type ObjectName), attribute (String)
Description: Returns value of "attribute" for the MBean described by
"object name."
Explanation This message is for informational purposes only. Action No action is required.
WASX7289I: Method: getAttributes_jmx
Arguments: object name (type ObjectName), attributes (String[])
Description: Returns an AttributeList object containing the values
of the attributes named in "attributes" for the object named by
"object name."
Explanation This message is for informational purposes only. Action No action is required.
WASX7290I: Method: setAttribute_jmx
Arguments: object name (type ObjectName), attribute (type Attribute)
Description: Sets the Attribute contained in "attribute" for the MBean
described by "object name."
Explanation This message is for informational purposes only. Action No action is required.
WASX7291I: Method: setAttributes_jmx
Arguments: object name (type ObjectName),
attributes (type AttributeList)
Description: Sets attributes in the the MBean described by
"object name." The attribute names and values are contained in the
"attributes" argument.
Explanation This message is for informational purposes only. Action No action is required.
WASX7292I: Method: invoke_jmx
Arguments: object name (type ObjectName), operation (type String),
arguments (type Object[]), signature (type String[])
Description: Invoke the operation named by "operation" on the MBean
described by "object name," using the arguments given in "arguments" and
the signature in "signature."
Explanation This message is for informational purposes only. Action No action is required.
WASX7293I: Method: convertToCluster
Arguments: server id, cluster name
Description: Creates a new ServerCluster object with the name
specified by "cluster name," and makes the server specified by
"server id" the first member of this cluster. Applications loaded
on this server are now configured on the new cluster.
Explanation This message is for informational purposes only. Action No action is required.
WASX7294I: Method: extract
Arguments: documentURI, filename
Description: Extracts a configuration repository document that
is described by the "documentURI" and places it in the file named
by the "filename". The "documentURI" describes a document that
must exist in the repository and is relative to the root of
repository such as "cells/MyCell/myfile.xml", and the "filename"
must be a valid local file name to extract the document to such as
"c:/myfile". This method returns an opaque "digest" object which
should be used to check the file back in the repository using the
checkin command.
Explanation This message is for informational purposes only. Action No action is required.
WASX7295I: Method: checkin
Arguments: documentURI, filename, digest
Description: Checks a file named by "filename" into the configuration
repository described by the "documentURI". The "documentURI"
is relative to the root of the configuration repository such as
"cells/MyCell/nodes/MyNode/serverindex.xml" which must exist
in the repository, and the "filename" is the name of the source
file to check in and it must be a valid local file name such as
"c:/myfile". The "digest" parameter should be the opaque object
which is returned by a prior extract command of AdminConfig object.
Explanation This message is for informational purposes only. Action No action is required.
WASX7296E: The name specified is not the name of a file "{0}"
Explanation The AdminConfig extract command did not run because the specified filename describes an existing file system entity that is not a file. Action Verify that the specified name is not a directory name. Specify a valid file name and reissue the command.
WASX7297E: Cannot write to file "{0}"
Explanation The AdminConfig extract command did not write document data to the specified file. Action Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems.
WASX7298E: Cannot invoke "{0}" command because this client is not connected to a Network Deployment Manager server.
Explanation The AdminConfig command requires a connection to a dmgr server. Action Connect to a dmgr server or do not invoke this AdminConfig command.
WASX7299E: "-wsadmin_classpath" option must be followed by a classpath.
Explanation The wsadmin launcher has been invoked with the -wsadmin_class path option, but no class path argument was found. Action Specify a class path for the -wsadmin_classpath option and reissue the wsadmin command.
WASX7300I: Method: getValidationSeverityResult
Arguments: severity
Description: Returns the number of validation messages with the given
severity from the most recent validation.
Explanation This message is for informational purposes only. Action No action is required.
WASX7301E: Cannot get the task info for {0} using file {1}. Ensure that this file exists and is readable.
Explanation The AdminApp taskInfo command did not obtain task information from the specified ear file. Action Verify that the file exists and is readable, and that the task name is spelled correctly.
WASX7302E: Cannot get tasks using file {0}. Ensure that this file exists and is readable.
Explanation The AdminApp options command did not obtain task options from the specified ear file. Action Verify that this file exists and is readable.
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "{0}"
Explanation The wsadmin tool did not recognize some arguments as command line parameters. The wsadmin tool stores these arguments in the argv variable and are available to the script. The argc variable contains the number of arguments available in the argv variable. Action Verify that the unrecognized arguments are arguments for scripts or commands to use. Correct or delete unrecognized options if necessary.
WASX7304I: Method: getNode
Arguments: none
Description: Returns the node to which the scripting process is
connected.
Explanation This message is for informational purposes only. Action No action is required.
WASX7305I: Client is connected to a server of type "{0}". The server "{1}" will be started on node "{2}" without attempting to synchronize the configuration.
Explanation The wsadmin tool cannot synchronize the configuration before startup because a node agent process is starting. Action No action is required.
WASX7306E: Cannot complete testConnection function because the node for Data Source "{0}" cannot be determined.
Explanation The wsadmin tool cannot determine the node for the specified DataSource that was specified by the AdminControl testConnection command. Action Verify that the DataSource is correctly configured.
WASX7307E: Cannot create object of type "{0}" on a Network Deployment Manager node.
Explanation The AdminConfig create command cannot create this type of object. Action Modify the create command.
WASX7309W: No "save" was performed before the script "{0}" exited; configuration changes will not be saved.
Explanation The changes invoked by a script concluded were not saved. No configuration changes were saved. Action Verify that the script uses the AdminConfig save command.
WASX7312I: Method: defaults
Arguments: type
Description: Displays all the possible attributes contained by an
object of type "type," along with the type and default value of each
attribute, if the attribute has a default value.
Explanation This message is for informational purposes only. Action No action is required.
WASX7313I: Generating Dynamic Scripting Objects. Please Wait...
Explanation The wsadmin tool is initializing the dynamic scripting objects. Action No action is required.
WASX7314I: Finished generating Dynamic Scripting Objects.
Explanation The wsadmin tool initialized the dynamic scripting objects. Action No action is required.
WASX7315W: Failed to generated dynamic scripting object: "{0}"
Explanation A dynamic scripting object did not initialize. Action This exception is unexpected. The cause is not immediately known.
WASX7316W: Error creating Dynamic Scripting object. These objects will not be available -- "{0}". Please use the generic AdminControl facilities.
Explanation The dynamic scripting objects did not initialize. Action Use the AdminControl invoke and get/setAttribute(s) commands to interact with MBeans instead of dynamic scripting support.
WASX7318E: Received exception while declaring {0}; exception information: {1}
Explanation An error has occurred during the initialization of the objects used by wsadmin. Action This exception is unexpected. The cause is not immediately known.
WASX7319I: The {0} attribute is set to false. A start will be attempted for server "{1}" but the configuration information for node "{2}" may not be current.
Explanation The wsadmin tool is using the startServer command to start a server. The configuration used by the starting server may not be the most recent configuration because the configuration has not be synchronized for this node. Action If the configuration is incorrect, stop the server and invoke a configuration synchronization for this node.
WASX7320E: Server "{0}" is already running on node "{1}" and cannot be started.
Explanation The AdminControl startServer command did not run because the server is already started. Action Verify that the correct server name is specified.
WASX7321I: Method: createDocument
Arguments: documentURI, filename
Description: Creates a new document in the configuration repository.
The "documentURI" is the name of the document to be created in the
repository which is relative to the root of the configuration
repository such as "cells/MyCell/myfile.xml", and the "filename"
is the name of the file to create which must be a valid local file
name such as "c:/myfile".
Explanation This message is for informational purposes only. Action No action is required.
WASX7322I: Method: deleteDocument
Arguments: documentURI
Description: Deletes a document from the configuration repository.
The "documentURI" is the name of the document to be deleted from the
repository which is relative to the root of configuration repository
such as "cells/MyCell/myfile.xml".
Explanation This message is for informational purposes only. Action No action is required.
WASX7323E: Cannot create directory "{0}"
Explanation The wsadmin tool cannot create a temporary directory for AdminApp processing. Action Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems.
WASX7324E: Cannot copy directory "{0}" to directory "{1}"
Explanation The wsadmin tool cannot copy an expanded ear directory to a temporary location for AdminApp processing. Action Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems.
WASX7326I: Loaded properties file "{0}"
Explanation During the initialization of a scripting process, several properties files might load. Use this message to determine which properties files that are in use. Action No action is required.
WASX7327I: Contents of was.policy file:
{0}
Explanation The list displays the was.policy security policy file associated with this application. Action No action is required.
WASX7328E: A single attribute name must be specified for showAttribute; received: "{0}"
Explanation The AdminConfig showAttribute command only displays the value of a single attribute, but multiple attribute names were supplied. Action Specify a single attribute name.
WASX7329I: Method: showAttribute
Arguments: config id, attribute
Description: Shows the value of the single attribute specified for
the configuration object named by "config id." The output of this
command is different from the output of "show" when a single
attribute is specified: the showAttribute command does not display a
list containing the attribute name and value; rather, the attribute
value alone is displayed.
Explanation This message is for informational purposes only. Action No action is required.
WASX7330I: "cluster" option; specifies the cluster name for AdminApp install functions.
Explanation This message is for informational purposes only. Action No action is required.
WASX7331I: Unexpected exception received when querying for changes in this session: {0}
Explanation The wsadmin tool created an exception because it could not determine if configuration changes have been made during the session. The connection to the server process might have broken before the scripting session was stopped. Action No action is required.
WASX7332I: Method: getCell
Arguments: none
Description: Returns the cell to which the scripting process is
connected.
Explanation This message is for informational purposes only. Action No action is required.
WASX7333I: This option is deprecated. Use the "update" option instead.
Explanation This message is for informational purposes only. Action No action is required.
WASX7334I: This option is deprecated. Use the "update.ignore.old" option instead.
Explanation This message is for informational purposes only. Action No action is required.
WASX7335I: This option is deprecated. Use the "update.ignore.new" option instead.
Explanation This message is for informational purposes only. Action No action is required.
WASX7336E: The "{0}" option is required if "{1}" is specified.
Explanation A required option is missing for the AdminApp install command. Action Specify each required option and reinvoke the command.
WASX7337I: Invoked stop for server "{0}" on node "{1}"; Waiting for stop completion.
Explanation A request has been made to stop the specified server process. The scripting process will wait until the stop is complete or the action times out. In the first case, WASX7264I should be issued; in the second case, WASX7265W should be issued. Action No action is required.
WASX7338E: Caught exception stopping server "{0}." Exception information:
{1}
Explanation The AdminControl stopServer command did not run. Action Examine the wsadmin.traceout file and the server log files to determine the source of the problem.
WASX7339I: Method: help
Arguments: none
Description: Displays general help for AdminConfig.
Method: help
Arguments: method name
Description: Displays help for the AdminConfig method specified by
"method name."
Explanation This message is for informational purposes only. Action No action is required.
WASX7340I: Method: existsDocument
Arguments: documentURI
Description: Tests to see if a document exists in the configuration
repository. The "documentURI" is the document to be tested which is
relative to the root of the configuration repository such as
"cells/MyCell/myfile.xml". Returns a true value if the document
exists; false otherwise.
Explanation This message is for informational purposes only. Action No action is required.
WASX7341W: No "save" was performed before the interactive scripting session exited; configuration changes will not be saved.
Explanation An interactive scripting session concluded without saving configuration changes. No configuration changes were saved. Action Invoke the AdminConfig "save" command to save the configuration changes.
WASX7342I: Method: installResourceAdapter
Arguments: rar file name, node, options
Description: Installs a J2C resource adapter with the rar file
specified by "rar file name" using the options specified by "options"
in the specified "node".
The rar file name is the fully qualified file name resided in the
specified node.
The valid options are "rar.name", "rar.desc", "rar.archivePath",
"rar.classpath", "rar.nativePath", "rar.threadPoolAlias",
"rar.propertiesSet, "isolatedClassLoader", "enabledHASupport", and
"HACapability. All options are optional.
The "rar.name" option is the name for the J2CResourceAdapter.
If it is not specified, then the display name in the rar's deployment
descriptor is used. If that is not specified, then the rar file name
is used.
The "rar.desc" option is a description of the J2CResourceAdapter.
The "rar.archivePath" is the name of the path where the file is
to be extracted. If this is not specified, then the archive will be
extracted to $CONNECTOR_INSTALL_ROOT directory.
The "rar.classpath" is the additional class path.
The "rar.threadPoolAlias" is the alias of the thread pool.
The "rar.propertiesSet" is the property set of the J2CResourceAdapter.
The "rar.isolatedClassLoader is the option to use isolated classloader.
If it is specified, it indicated that the J2CResourceAdapter uses the
isolated classloader. The default value is "false".
The "rar.enableHASupport is the option to enable HA support.
The default value is "false".
The "rar.HACapability specifies the type of HA support. The choices are
the "endpoint", "instance" and "no".
Explanation This message is for informational purposes only. Action No action is required.
WASX7343E: The specified node name "{0}" is not the same as the node "{1}" this client is currently connected to.",
Explanation The wsadmin tool cannot run the AdminControl startServer command because the node name that has been specified is not the same as the node name that is currently connected to by the node agent. Action Verify that the node name is spelled correctly.
WASX7344E: Node name is required when the client is connected to process type "{0}".
Explanation The wsadmin tool cannot run the AdminControl startServer command because the node name is not specified. Action Specify the node name to locate the server in the startServer command.
WASX7345E: Cannot find node "{0}" in configuration data.
Explanation The wsadmin tool cannot run the AdminControl startServer command because there is no node of the specified name in the configuration. Action Verify that the node name is spelled correctly.
WASX7346E: Cannot locate NodeAgent object for server "{0}" of process type {1}.
Explanation The wsadmin tool cannot run the AdminControl stopServer command because the node agent for the specified server is not located in the configuration. Action Verify that the client is connected to the appropriate process type.
WASX7347E: An argument is required for option "{0}."
Explanation The specified option requires an accompanying argument. For example, if you specify the "-node" option, follow the "-node" option with the name of a node such as "-node mynode." Action Specify an argument for the indicated option, or remove the option from the command.
WASX7348I: Each element of the {0} task consists of the following {1} fields: {2}
Of these fields, the following are required and used as keys to locate the rows in the task: {3}
and the following may be assigned new values: {4}
The current contents of the task after running default bindings are:
{5}
Explanation The previous information results from an AdminApp taskInfo command and details the task information requested. Action No action is required.
WASX7349I: Possible value for resource authorization is container or per connection factory
Explanation This message is for informational purposes only. Action No action is required.
WASX7350E: This field requires container or per connection factory as the value. Please try again.
Explanation The value for the resource authorization field was not specified. Action Enter "container" or "per connection factory" as the value of resource authorization.
WASX7351I: The parents command cannot be used to find the parents of type "{0}"
Explanation The parents command does not support the specified object type. Action No action is required.
WASX7352E: Wrong number of arguments for "{0}" command. Help information follows:
{1}
Explanation The number of arguments supplied for the given command is not correct. Action Review the help information and reissue the command with the correct number of arguments.
WASX7353E: The value of the attribute "{0}" must be a collection of objects of type "{1}"; an additional set of braces may be required to signify that this is a collection.
Explanation Specify attribute values that are collections of objects as a list of name-value pairs. An example of a collection consisting of two objects is: {{{attr1 val1a} {attr2 val2a}} {attr1 val1b} {attr2 val2b}}}. Action Correct the syntax of the command to note the attribute as a collection.
WASX7354E: The attribute "{0}" is an embedded object of type "{1}"; an invalid value was supplied.
Explanation Specify attribute values that are embedded objects as a list of name-value pairs. An example of an embedded object consisting of three attributes is: {{attr1 val1a} {attr2 val2a}}. Action Correct the syntax of the command so that the embedded object is formatted as a list of name-value pairs.
WASX7355E: The attribute "{0}" is of type "{1}"; an invalid value was supplied.
Explanation The value supplied for the attribute is not valid. Action Correct the syntax and reissue the command.
WASX7356E: Unrecognized argument: {0}. The specified argument is not a valid node name or wait time when connected to {1}.
Explanation The argument passed to the startServer command is not valid. Action Reissue the command with the correct value for the argument.
WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
Explanation The wsadmin tool is not connected to a server process. A request was made with "-conntype NONE" option from the command line or specified in com.ws.scripting.connectionType property with NONE as the value in wsadmin.properties. Action No action is required.
WASX7358E: Invalid option specified: {0}
Explanation The wsadmin tool found one or more options that are not valid. Action Check the spelling of the options. Correct or remove any incorrect options and reissue the command.
WASX7359E: Incorrect value specified for reloadInterval option: {0}. reloadInterval option requires an integer value.
Explanation The value specified for the -reloadInterval option is not an integer. Action Specify an integer argument for the -reloadInterval option and reissue the AdminApp command.
WASX7360I: Method: required
Arguments: type
Description: Displays the required attributes contained by an object
of type "type".
Explanation This message is for informational purposes only. Action No action is required.
WASX7361I: No required attribute found for type "{0}".
Explanation No required attributes were found for the specified type. Action No action is required.
WASX7362I: Method: message
Arguments: Message Id
Description: Display information for given message id.
Explanation This message is for informational purposes only. Action No action is required.
WASX7363E: No help available for message id {0}.
Explanation The Help message command cannot locate any message information for the specified message id. Action Verify that the specified message id is correct.
WASX7364E: Error getting help information for message id {0}.
Explanation The directory containing the help information does not exist. Action This exception is unexpected. The cause is not immediately known.
WASX7365I: Explanation: {0}
User action: {1}
Explanation This message is for informational purposes only. Action No action is required.
WASX7367I: "update.ignore.old" option; this option specifies that when an application is updated, the bindings from the the old version are ignored during the reinstall operation. This option only has meaning if the "update" option is specified; otherwise it is ignored.
Explanation This message is for informational purposes only. Action No action is required.
WASX7368I: "update.ignore.new" option; this option specifies that when an application is updated, the bindings from the the new version are ignored during the reinstall operation. This option only has meaning if the "update" option is specified; otherwise it is ignored.
Explanation This message is for informational purposes only. Action No action is required.
WASX7369I: Method: exportDDL
Arguments: application name, directory name, options
Description: Exports DDL from the application specified by
"application name" to the directory specified by "directory name" using
the options specified by "options".
Method: exportDDL
Arguments: application name, directory name
Description: Exports DDL from the application specified by
"application name" to the directory specified by "directory name."
Explanation This message is for informational purposes only. Action No action is required.
WASX7370E: Error registering bean {0} provided in extension: {1}
Explanation The system cannot register the bean provider specified in the extension xml file with the BSF. Action Examine the exception in the trace log and correct the problem accordingly. If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
WASX7371E: Error locating the class for {0} provided in extension: {1}
Explanation The system cannot find the implementation class provided in the extension xml file. Action Verify that the implementation class in the extension xml file is correct and that the class is in the class path.
WASX7372E: Error instantiating the class for {0} provided in extension: {1}
Explanation The system cannot instantiate the implementation class provided in the extension xml file. Action Examine the exception in the trace log and correct the problem accordingly. Verify that the class provides a constructor with no argument.
WASX7373W: Duplicate implementation class entry, {0}, found in {1} at line {2}.
Explanation The same implementation class is included in the extension xml file more than once. Action Remove the duplicate implementation class from the extension xml file.
WASX7374W: Missing element type {0} in {1} at line {2}. Ignoring this {3} element type.
Explanation The extension xml file contains an element type reported in this warning message with required element type missing. Action Add the missing element type reported in this message to the extension xml file.
WASX7375E: Element type {0} is already defined.
Explanation The same element type is used more than once in the extension xml file. Action Remove the extra element type in the extension xml file.
WASX7376E: Invalid element end-tag: {0}
Explanation The reported element tag in the extension xml file is not supported. Action Remove the unsupported element tag in the extension xml file.
WASX7377W: <typeClass> element with the same class name, {0}, found in {1} at line {2}.
Explanation A type handler registerd to handle the same type class is included in the extension xml more than once. Action Remove the duplicate type handler in the extension xml file.
WASX7378I: "reloadEnabled" option; this option specifies to enable class reloading; this is the default setting.
Explanation This message is for informational purposes only. Action No action is required.
WASX7379E: Language "{0}" is not supported. Supported languages are jacl and jython.
Explanation An unsupported scripting language was specified. Action Specify a supported scripting language with the -lang option or com.ibm.ws.scripting.defaultLang option.
WASX7380I: Invalid file name specified: {0}. File name must end with the following file extensions: ear, jar, rar, or war
Explanation This message is for informational purposes only. Action No action is required.
WASX7381I: "nodeployws" option; specifies to not deploy WebService during install; this is the default setting.
Explanation This message is for informational purposes only. Action No action is required.
WASX7382I: "deployews.classpath" option; specifies extra classpath to be used to deploy WebServices
Explanation This message is for informational purposes only. Action No action is required.
WASX7383I: "deployews.jardirs" option; specifies extra extension directories to be used to deploy WebServices
Explanation This message is for informational purposes only. Action No action is required.
WASX7384I: "deployws" option; specifies to deploy WebServices during install; the default is "nodeployws"
Explanation This message is for informational purposes only. Action No action is required.
WASX7385I: Method: publishWSDL
Arguments: application name, filename, soapAddressPrefixes
Description: Publish WSDL files for the application specified
to the file specified by "filename" using the soap address prefixes.
The soapAddressPrefixes is a compound parameter that defines url
endpoint information for the soap addresses in each module.
This information is used to customize the SOAP addresses in
the published WSDL.
Method: publishWSDL
Arguments: application name, filename
Description: Publish WSDL files for the application specified
to the file specified by "filename".
Explanation This message is for informational purposes only. Action No action is required.
WASX7386E: {0} in {1} at line {2} column {3}
{4}
Explanation A parser exception occured when getting the scripting extension. Action Examine the exception in the trace log and correct the problem accordingly.
WASX7387E: Operation not supported - testConnection command in AdminControl scripting object is not supported when connected to a 5.0 server.
Explanation v5.1 and later supports the testConnection command. Action Use the testConnectionToDataSource method in DataSourceCfgHelper MBean to test the connection of a DataSource that resides in a 5.0 server.
WASX7388E: Connection to provided datasource failed.
Explanation An error occured during invoking test connection to the provided data source. Action Examine the exception in the trace log and correct the problem accordingly.
WASX7389E: Operation not supported - getPropertiesForDataSource command is not supported.
Explanation The wsadmin tool does not support this command. Action Do not use this command.
WASX7390E: Operation not supported - testConnection command with config id and properties arguments is not supported. Use testConnection command with config id argument only.
Explanation The wsadmin tool does not support this command. Action Do not use this command.
WASX7391W: Your application contains policy permissions that are in the filter.policy. These permissions are security sensitive and can compromise the integrity of the system. Do to continue with the application deployment process?
Explanation The application server attempts to prevent applications from performing security-sensitive operations such as: calling the System.exit() method, replacing the java 2 Security manager, and replacing the java 2 Security policy. If the application is granted the all permission (java.security.AllPermission), the java 2 Security permission checks are disabled. This compromises the integrity of the system. Action Review the application policy that is located in the EAR/META-INF/was.policy file. Remove the security-sensitive permissions and grant the application only the permissions that are required.
WASX7392W: Your application contains policy permissions that are in the filter.policy. These permissions are security sensitive and can compromise the integrity of the system. Continuing with the application deployment process ...
Explanation The application server attempts to prevent applications from performing security-sensitive operations such as: calling the System.exit() method, replacing the java 2 Security manager, and replacing the java 2 Security policy. If the application is granted the all permission (java.security.AllPermission), the java 2 Security permission checks are disabled. This compromises the integrity of the system. Action Review the application policy that is located in the EAR/META-INF/was.policy file. Remove the security-sensitive permissions and grant the application only the permissions that are required.
WASX7393I: "allowPermInFilterPolicy" option; specifies to continue with the application deployment process even when the application contains policy permissions that are in the filter policy
Explanation This message is for informational purposes only. Action No action is required.
WASX7394I: "noallowPermInFilterPolicy" option; specifies to not continue with the application deployment process when the application contains policy permission that are in the filter.policy. This is the default setting.
Explanation This message is for informational purposes only. Action No action is required.
WASX7395E: The specified values for -lang and -internalLang options are not the same. Use one or the other option but not both.
Explanation The -lang and -internalLang options are specified. However, the values for the two options are not the same. Action Specify either the -lang or -internalLang option.
WASX7396I: Method: uninstallResourceAdapter
Arguments: config id
Description: Uninstall a J2C resource adapter by the "config id"
Method: uninstallResourceAdapter
Arguments: config id, option list
Description: Uninstall a J2C resource adapter by the "config id" using options in "option list".
Option list is optional. The valid option is "force".
The "force" option will force the uninstall of resource adapter
without checking whether the resource adapter is still being
used by any application.
If this option is not specified and the specified resource adapter is still in use,
the resource adapter will not be uninstalled.
Explanation This message is for informational purposes only. Action No action is required.
WASX7397I: The following J2CResourceAdapter objects are removed: {0}
Explanation This message is for informational purposes only. Action No action is required.
WASX7398E: List of applications still using the specified Resource Adapter:
Explanation Applications currently use the resource adapter specified in the uninstallResourceAdapter command. Action Uninstall the applications listed in this error message before uninstalling the resource adapter. To force this uninstall action without uninstalling applications first, specify the -force option with uninstallResourceAdapter command.
WASX7399E: List of J2CResourceAdapter objects still using the specified Resource Adapter:
Explanation J2CResourceAdapter objects currently use the resource adapter specified in the uninstallResourceAdapter command. Action Uninstall the resource adapters listed in this error message before attempting to uninstall the specified resource adapter. To force this uninstall action without uninstalling the other resource adapters first, use the -force option with uninstallResourceAdapter command.
WASX7400I: This will enable the use of FIPS (Federal Information Processing Standard) approved cryptographic algorithms. Note that setting this flag does not automatically change the existing JSSE provider in the SSL configuration. Also note that FIPS approved JSSE provider only allows TLS protocol.
Explanation This message is for informational purposes only. Action No action is required.
WASX7401W: The security policy is set to use only FIPS approved cryptographic algorithms, however at least one SSL configuration may not be using a FIPS approved JSSE provider. FIPS approved cryptographic algorithms may not be used in those cases.
Explanation When security policy is set to use only FIPS approved cryptographic algorithms, no SSL configuration can use FIPS approved JSSE provider. Action Examine the exception in the trace log and correct the problem accordingly.
WASX7402W: "Use FIPS" is enabled, but the SSL provider is not IBMJSSEFIPS. FIPS approved cryptographic algorithms may not be used.
Explanation We cannot use FIPS approved cryptographic algorithms if SSL provider is not IBMJSSEFIPS. Action Examine the exception in the trace log and correct the problem accordingly.
WASX7403I: This will enable the use of FIPS (Federal Information Processing Standard) approved cryptographic algorithms. Note that setting this flag does not automatically change the existing JSSE provider in the SSL configuration. Also note that FIPS approved JSSE provider only allows TLS protocol. Moreover, the FIPS approved LTPA authentication mechanism is not backward compatible with non-FIPS approved LTPA implementation used in all prior version of WAS products.
Explanation This message is for informational purposes only. Action No action is required.
WASX7404I: Method: view
Arguments: name, taskname option
Description: View the task specified by the "taskname option"
parameter for the application or module specified by the "name"
parameter. Use "-tasknames" as the option to get a list of valid
task names for the application. Otherwise, specify one or more
task names as the option.
Method: view
Arguments: name
Description: View the application or module specified by
the "name" parameter.
Explanation This message is for informational purposes only. Action No action is required.
WASX7405E: No viewable tasks are available for application "{0}"
Explanation The AdminApp view command did not run because the application has no valid tasks to view. Action This application is not editable.
WASX7406E: Cannot find task name {0} in the application {1}
Explanation The AdminApp view command did not run because the application viewable tasks are not valid. Action Specify the correct task with the correct spelling. To list the valid task names, use the -tasknames option.
WASX7407I: The specified node configuration is successfully removed from the workspace. If you decide to commit this change to the master repository, the configuration may become invalid. To revert this operation and remove any unsaved configuration changes in the workspace, perform "AdminConfig reset" command.
Explanation Removal of the node from the configuration will corrupt the configuration. Action If you did not commit the change, run the AdminConfig reset command to restore the configuration to its initial state.
WASX7408I: The specified node configuration is successfully removed from the workspace. If you decide to commit this change to the master cell repository, you may need to perform manual steps to complete the removal steps include restoring the original application server cell configuration as the active configuration and updating the cell value in setupCmdLine.bat. If there are still running application servers for this node, we have to manually stop those servers.
Explanation Removal of the node from the configuration requires some manual steps. This operation is not recommended. Alternatively, use the removeNode utility script. Action If you did not commit the change, run the AdminConfig reset command to restore the configuration to its initial state.
WASX7409I: Method: deleteUserAndGroupEntries
Arguments: application name
Description: Deletes all the user/group information for all the roles
and RunAs roles for a given application.
Method: deleteUserAndGroupEntries
Arguments: application name
Description: Deletes all the user/group information for all the roles
and RunAs roles for a given application.
Explanation This message is for informational purposes only. Action No action is required.
WASX7410I: Method: updateAccessIDs
Arguments: application name, boolean:bAll
Description: Updates the application binding file for an installed
application with access IDs for all the users and groups. Specifying
true for bAll updates all the users/groups even if there are access
IDs already present in the bindings.
Method: updateAccessIDs
Arguments: application name, boolean:bApp
Description: Updates the application binding file for an installed
application with access IDs for all the users and groups.
Explanation This message is for informational purposes only. Action No action is required.
WASX7411W: Ignoring the following provided option: {0}
Explanation The wsadmin tool cannot recognize some options specified in the AdminApp command. Action Verify that options provided in the message are correct. Reissue the AdminApp command if necessary. Otherwise, no action is required.
WASX7412E: Invalid content type value: {0}
Explanation The value for the content type parameter is not valid. Valid values for this parameter are add, addupdate, delete, and update. Action Reissue the update command with the correct content type value.
WASX7413E: Invalid operation value: {0}
Explanation The value for the operation option is not valid. Valid values for this parameter are app, file, modulefile, and partialapp. Action Reissue the update command with the correct operation value.
WASX7414W: Ignoring {0} option when {1} content type is specified.
Explanation The option specified in this message is not required if the specified content type is provided in the update command. Action No action is required.
WASX7415W: Ignoring {0} option when {1} operation is specified.
Explanation The option specified in the message is not required if the specified operation is provided in the update command. Action No action is required.
WASX7416E: {0} option is required when {1} content type is specified.
Explanation The missing option is required when the specified content type is provided in the update command. Action Specify the missing option and reissue the update command.
WASX7417E: {0} option is required when {1} content type and {2} operation are specified.
Explanation The missing option is a required option if the specified content type and operation are provided in the update command. Action Specify the missing option and reissue the update command.
WASX7418E: Application update for {0} failed: see previous messages for details.
Explanation The wsadmin tool did not run the AdminApp update command. Action No action is required.
WASX7419I: Method: update
Arguments: application name, content type, options
Description: updates the application specified by "application
name" using update type specified by "content type" with
options specified by "options".
Valid update content type values are
app - entire application
file - a single file
modulefile - a module
partialapp - partial application
All valid options for install command are valid for the
update command. Additional update options are
-operation - operation to be performed. Valid values are
add - adds new contents
addupdate - performs add or updates based on
existence of contents in the application
delete - deletes contents
update - update existing contents
This option is required if content type is file
and modulefile. This option must have "update" as
the value if content type is app. This option is
ignored if content type is partialapp.
-contents - file containing the contents to be added or
updated. The specified file has to be local to the
scripting client. This option is required except for
delete operation.
-contenturi - URI of the file to be added, updated, or
removed from the application. This option is required if
content type is file or modulefile. This option
is ignored if content type is app or partialapp.
The AdminApp "options" command may be used to get a list of all
possible options for a given ear file. The AdminApp "help" command
may be used to get more information about each particular option.
Explanation This message is for informational purposes only. Action No action is required.
WASX7420I: Method: updateInteractive
Arguments: application name, content type, options
Description: updates the application specified by "application
name" using update type specified by "content type" with
options specified by "options". If content type is app or
file, user is prompted for information about each relevant task.
Valid update content type values are
app - entire application
file - a single file
modulefile - a module
partialapp - partial application
All valid options for install command are valid for the
update command. Additional update options are
-operation - operation to be performed. Valid values are
add - adds new contents
addupdate - performs add or updates based on
existence of contents in the application
delete - deletes contents
update - update existing contents
This option is required if content type is file
or modulefile. This option must have "update" as
the value if content type is app. This option is
ignored if content type is partialapp.
-contents - file containing the contents to be added or
updated. The specified file has to be local to the
scripting client. This option is required except for
delete operation.
-contenturi - URI of the file to be added, updated, or
removed from the application. This option is required if
content type is file or modulefile. This option
is ignored if content type is app or partialapp.
The AdminApp "options" command may be used to get a list of all
possible options for a given ear file. The AdminApp "help" command
may be used to get more information about each particular option.
Explanation This message is for informational purposes only. Action No action is required.
WASX7421I: "contents" option; this option is used in the update or updateInteractive command to specify the file containing the contents to be updated. Depending on the content type, the file can be a module, a partial zip, an application file, or a single file. The path to the file has to be local to the scripting client. This option is required except when delete operation is specified.
Explanation This message is for informational purposes only. Action No action is required.
WASX7422I: "contenturi" option: this option is used in the update or updateInteractive command to specify the URI of the file to be added, updated, or removed from the application. This option is required if content type is file or modulefile. This option is ignored for other content type values.
Explanation This message is for informational purposes only. Action No action is required.
WASX7423I: "operation" option: this option is used in the update or updateInteractive command to specify the operation to be performed. Valid values are
add - adds new content
addupdate - performs add or update based on existence
of contents in the application
delete - deletes contents
update - update existing contents
This option is required if content type is file or modulefile.
This option must have "update" as the value if content type
is app. This option is ignored for other content type values.
Explanation This message is for informational purposes only. Action No action is required.
WASX7424I: "createMBeansForResources" option: this option specifies that MBeans are created for all the resources such as servlets, jsps, EJBs, defined in an application when the application is started on a deployment target; the default is nocreateMBeansForResources.
Explanation This message is for informational purposes only. Action No action is required.
WASX7425I: "nocreateMBeansForResources" option: this option specifies that MBeans are not created for all the resources such as servlets, jsps, EJBs, defined in an application when the application is started on a deployment target; this is the default setting.
Explanation This message is for informational purposes only. Action No action is required.
WASX7426I: "noreloadEnabled" option: this option specifies not to enable class reloading; the default is reloadEnabled.
Explanation This message is for informational purposes only. Action No action is required.
WASX7427I: "reloadInterval" option: this option specifies the time period (in seconds) in which the application's filesystem will be scanned for updated files; the default setting is 3 seconds.
Explanation This message is for informational purposes only. Action No action is required.
WASX7428W: contextroot option will be ignored if module exists.
Explanation Use the contextroot option with the update command, the modulefile content type, and the update or addupdate operation. Action For an update operation with a modulefile content type, wsadmin.sh ignores the contextroot option. For the addupdate operation with a modulefile the content type, wsadmin.sh ignores the contextroot option if the module exists. This message is for the informational purposes only.
WASX7429I: Method: searchJNDIReferences
Arguments: node or nodes config id, options
Description: List all applications that refer to the specified
JNDIName option on the specified node or nodes.
The valid options are -JNDIName which is a required option
and -verbose which is an optional option that does not take any value.
The JNDIName option takes a value of a JNDI name.
The verbose option will show more information.
Explanation This message is for informational purposes only. Action No action is required.
WASX7430W: This operation may take longer depending on how many applications installed on the system.
Explanation Searching for JNDI references may take longer depending on how many applications installed on the system. Action No action is required.
WASX7431I: "installed.ear.destination" option; specifies the directory into which the application binaries should be placed.
Explanation This message is for informational purposes only. Action No action is required.
WASX7432I: "validateinstall" option; specifies desired level of application install validation. Valid option values are:
off: no application deployment validation
warn: perform application deployment validation and
continue with the application deployment process
even when there are reported warning or error
messages.
fail: perform application deployment validation and
not to continue with the application deployment
process when there are reported warning or
error messages.
The default is off.
Explanation This message is for informational purposes only. Action No action is required.
WASX7433I: "custom" option; specifies a name-value pair using the format name=value. Use this option to pass option to application deployment extension. Consult application deployment extension documentation for available custom options.
Explanation This message is for informational purposes only. Action No action is required.
WASX7434W: Found the following deprecated option: {0}
Explanation The options listed in this message are deprecated for the AdminApp command. The support for these options will be removed in a future release. Action Determine if there is replacement option for the deprecated option. If so, use the replacement option. If there is no replacement option, you can exclude the deprecated option.
WASX7435W: Value {0} is converted to a boolean value of false.
Explanation A string value representing a boolean is not entered as true or false. Action Verify that the string value is correct and reissue the command.
WASX7436W: At least one default binding option has been specified, but usedefaultbindings option has not been specified. The default binding option(s) will be ignored.
Explanation To use any default binding option, specify the usedefaultbindings option. Action Usedefaultbindings option in the option string with the AdminApp install, installInteractive, update, or updateInteractive command.
WASX7437I: "processEmbeddedConfig" option; Use this option to process the embedded configration data that is included in the application. This setting is the default.
Explanation This message is for informational purposes only. Action No user action is required.
WASX7438I: "noprocessEmbeddedConfig" option; Use this option to ignore the embedded configuration data that is included in the application. The default setting is "processEmbeddedConfig".
Explanation This message is for informational purposes only. Action No user action is required.
WASX7439I: Method: isAppReady
Arguments: application name
Description: Tests to see if the specified application has been
distributed and is ready to be run. Returns true if the application
is ready; false otherwise.
Arguments: application name, ignoreUnknownState
Description: Tests to see if the specified application has been
distributed and is ready to be run. Valid values for ignoreUnknownState
argument are true or false. If true is specified as its value, then
any node or server with unknown state is not included in the final
ready return. Returns true if the application is ready; false
otherwise.
Explanation This message is for informational purposes only. Action No action is required.
WASX7440E: "{0}" method is not supported when connecting to local mode.
Explanation The wsadmin tool is connected to local mode. Action Verify that the scripting client is connected to a server and that the server is running.
WASX7441E: "{0}" action not supported when process type of server being stopped is "{1}"
Explanation Use the terminate flag only to stop servers of the managed process type. Action Verify that the server to stop is a managed process.
WASX7442E: "{0}" action not supported when node name is not provided.
Explanation Specify the node name as one of the arguments. Action Include the node name for the server in your arguments.
WASX7443I: Server "{0}" on node "{1}" is not being monitored. Please verify that the server has stopped before continuing.
Explanation The wsadmin tool issued a request to stop the specified server process. The scripting process will not wait until the request succeeds. Action Verify that the server stopped before continuing.
WASX7444E: Invalid parameter value "{0}" for parameter "{1}" on command "{2}"
Explanation A parameter value is not valid. Do not specify parameter values as null or empty strings. Action Reissue the AdminConfig command with the correct parameter value.
WASX7445E: "-jobid" option must be followed by a jobID string.
Explanation The wsadmin launcher did not run because no jobid argument was found for the -jobid option. Action Specify a value for the -jobid option and reissue the wsadmin command.
WASX7446E: "-tracefile" option must be followed by a file path.
Explanation The wsadmin launcher did not run because no logfile argument was found for the -tracefile option. Action Specify a file path for the -tracefile option and reissue the wsadmin command.
WASX7447E: "-appendtrace" option must be followed by a 'true' or 'false'.
Explanation The wsadmin launcher did not run because no argument was found for the -appendtrace option. Action Specify a string value for the -appendtrace option and reissue the wsadmin command.
WASX7448E: The trace file cannot be written to location {0}. Please specify a different location with -tracefile option.
Explanation The wsadmin launcher did not run because the location that has been specified is not writable. Action Specify a different location for the -tracefile option and reissue the wsadmin command.
WASX7449I: "target" option; specifies the target for AdminApp install functions.
Example of target option value is WebSphere:cell=mycell,node=mynode,server=myserver
Explanation This message is for informational purposes only. Action No action is required.
WASX7450I: "buildVersion" option; specifies the build version of an application ear file.
Explanation This message is for informational purposes only. Action No action is required.
WASX7451I: "allowDispatchRemoteInclude" option; Enables an enterprise application to dispatch
includes to resources across web modules in different JVMs in a managed node environment via the standard RequestDispatcher mechanism.
Explanation This message is for informational purposes only. Action No action is required.
WASX7452I: "allowServiceRemoteInclude" option; Enables an enterprise application to service
an include request from an enterprise application with -allowDispatchRemoteInclude set to true.
Explanation This message is for informational purposes only. Action No action is required.
WASX7453I: "filepermission" option; Allow user to set appropriate file permissions on application files in the install destination directory.
File permissions specified at the application level must be a subset of the node level file permission which defines the most lenient file permission that can be specified, otherwise node level permission value is used to set file permissions in install destination.
The default is ".*\.dll=755#.*\.so=755#.*\.a=755#.*\.sl=755"
The filename pattern is a regular expression.
Explanation This message is for informational purposes only. Action No action is required.
WASX7454I: "noallowDispatchRemoteInclude" option; Disables an enterprise application to dispatch
includes to resources across web modules in different JVMs in a managed node environment via the standard RequestDispatcher mechanism.
Explanation This message is for informational purposes only. Action No action is required.
WASX7455I: "noallowServiceRemoteInclude" option; Disables an enterprise application to service
an include request from an enterprise application with -allowDispatchRemoteInclude set to true.
Explanation This message is for informational purposes only. Action No action is required.
WASX7456I: Method: queryMBeans
Arguments: object name
Description: Returns a Set containing ObjectInstances object
that match the input object name.
Method: queryMBeans
Arguments: object name (type ObjectName), query (type QueryExp)
Description: Returns a Set containing ObjectInstances object
that match the input object name and query.
Explanation This message is for informational purposes only. Action No action is required.
WASX7457I: Method: getObjectInstance
Arguments: object name
Description: Returns the ObjectInstance object that match the input
object name.
Explanation This message is for informational purposes only. Action No action is required.
WASX7458E: Invalid file permission string "{0}"
Explanation The parameter value for file permission is not valid. Action Specify a file permission value with a valid string.
WASX7459E: The configuration service is not available. Target node's nodeagent may not be running "{0}."
Explanation The AdminConfig object was specified, but the wsadmin process is not connected to a server with a running configuration service. Action If the node agent of the target node is not running, start it and reissue the wsadmin command.
WASX7460I: Method: getDeployStatus
Arguments: application name
Description: Returns a string which represents the deployment status
of the application. The status of each node, to which the application is
deployed, is concatenated by the "+" character.
Explanation This message is for informational purposes only. Action No action is required.
WASX7461I: Method: AdminTask
Arguments: none
Description: Display general help information for the
AdminTask object provided by wsadmin.
Explanation This message is for informational purposes only. Action No action is required.
WASX7462I: Method: wsadmin
Arguments: none
Description: Display general help information for the
wsadmin script launcher.
Explanation This message is for informational purposes only. Action No action is required.
WASX7463I: "deployejb.dbaccesstype" option; specifies the database access type for EJBDeploy
Explanation This message is for informational purposes only. Action No action is required.
WASX7464I: "deployejb.sqljclasspath" option; specifies the SQLJ classpath for EJBDeploy
Explanation This message is for informational purposes only. Action No action is required.
WASX7465E: stopServer action not supported when server type is "{0}"
Explanation Scripting client is connected admin subsystem and try to stop the admiagent server which is not supported. Action To stop adminagent server do it from adminagent bin directory or if you are trying to stop admin subsystem connect to adminagent server directly and use AdminAgent mbean to invoke stopProfile operation.
WASX7466I: Method: getObjectType
Arguments: config id
Description: Displays the configuration object type by "config id."
Explanation This message is for informational purposes only. Action No action is required.
WASX7467I: Connection to provided datasource on node {0} process {1} was successful.
Explanation The AdminControl testConnection command was successfully run. The database adapter code reported no errors or warnings. Action No action is required.
WASX7468E: Connection to provided datasource on node {0} process {1} failed.
Explanation The AdminControl testConnection command was failed. See exception message and wsadmin.traceout file to find what is the problem Action Find the problem from the log and try to resolve the problem and reissue the command.
WASX7469E: One or more attributes must be specified for resetAttributes; received: {0}
Explanation The attribute will be reset is not specified. Action Supply the attribute to be reset.
WASX7470E: One or more attributes name must be specified for unsetAttributes; received: {0}
Explanation The attribute name will be unset is not specified. Action Supply the attribute name to be unset.
WASX7471I: Method: unsetAttributes
Arguments: config id, attributes
Description: Use the unsetAttributes command to reset the specific attributes for a
configuration object to the default values.
Explanation This message is for informational purposes only. Action No action is required.
WASX7472I: Method: resetAttributes
Arguments: config id, attributes
Description: Use the resetAttributes command to reset the specific attributes for a
configuration object.
Explanation This message is for informational purposes only. Action No action is required.
WASX7473I: "exportToLocal" option; specifies the option for AdminApp export function to export application to the client local machine.
Explanation This message is for informational purposes only. Action No action is required.
WASX7474I: Method: exportFile
Arguments: application name, uri, filename
Description: This command exports the contents of a single file
which is specified by the uri argument, from the application,
which is specified by the application name argument, to the file,
which is specified by the file argument.
Uri argument within the context of an application.
For example: META-INF/application.xml. For files within a module,
start the uri with a module uri. For example: myapp.war/WEB-INF/web.xml.
Explanation This message is for informational purposes only. Action No action is required.
WASX7475E: The {0} output file already exists. Specify another output file name.
Explanation A file, which has the same name as the specified output file name in exportFile command, exists in the local directory. Action Rerun the exportFile command and specify a non-existent output file name.
WASX7476I: "useAutoLink" option; allow the EJB reference targets to resolve automatically.
The application must contain an EJB 3.0 module and all modules must share one common target to enable the autolink support.
Explanation This message is for informational purpose only. Action No action is required.
WASX7477I: "blaname" option; use this option to specify the name of the business level application.
Explanation This message is for informational purpose only. Action No action is required.
WASX7478I: "nouseAutoLink" option; the EJB reference targets do not resolve automatically. The default setting is "nouseAutoLink"
Explanation This message is for informational purpose only. Action No action is required.
WASX7479I: "asyncRequestDispatchType" option; specifies the asynchronous request dispatch type for web container for each application. The default setting is "DISABLED"
Explanation This message is for informational purposes only. Action No action is required.
WASX7480E: "{0}" found instead of expected '['. {1}
Explanation The wsadmin tool found the specified string when '[' was expected in the input stream. Action Correct and reissue the command.
WASX7481I: "deployejb.complianceLevel" option; specifies the JDK level for compiler compliance for EJBDeploy; default is 1.4.
Explanation This message is for informational purposes only. Action No action is required.
WASX7482W: The duplicate properties are specified. The latter property value will be set.
Explanation The duplicate properties are specified in the command. The latter property value will be set to the property. Action Respecify the property name and value.
WASX7483E: Application edit of {0} failed: see previous messages for details.
Explanation An AdminApp edit command did not run. Action See previous messages for details.
WASX7484I: "validateSchema" option; Use this option to specify that the schema is to be validated. The default is "novalidateSchema"
Explanation This message is for informational purposes only. Action No action is required.
WASX7485I: "validateSchema" option; Use this option to specify that the schema is not to be validated. This is the default.
Explanation This message is for informational purposes only. Action No action is required.
WASX8001I: The AdminTask object enables the execution of available admin
commands. AdminTask commands operate in two modes:
the default mode is one which AdminTask communicates with the WebSphere
server to accomplish its task. A local mode is also available, in which
no server communication takes place. The local mode of operation is
invoked by bringing up the scripting client using the command line
"-conntype NONE" option or setting the
"com.ibm.ws.scripting.connectiontype=NONE" property in
wsadmin.properties file.
The number of admin commands varies and depends on your WebSphere
install. Use the following help commands to obtain a list of supported
commands and their parameters:
help -commands Lists all the admin commands
help -commands <pattern> Lists admin commands matching with wildcard
"pattern"
help -commandGroups Lists all the admin command groups
help -commandGroups <pattern> Lists admin command groups matching with
wildcard "pattern"
help commandName Displays detailed information for the
specified command
help commandName stepName Displays detailed information for the specified
step belonging to the specified command
help commandGroupName Displays detailed information for the specified
command group
There are various flavors to invoke an admin command. They are
commandName Invokes an admin command that does not require
any argument.
commandName targetObject Invokes an admin command with the specified
target object string, for example, the
configuration object name of a resource
adapter. The expected target object varies
with the admin command invoked. Use help
command to get information on the target
object of an admin command.
commandName options Invokes an admin command with the specified
option strings. This invocation syntax is
used to invoke an admin command that does
not require a target object. It is also
used to enter interactive mode if
"-interactive" mode is included in the
options string.
commandName targetObject options Invokes an admin command with the
specified target object and options
strings. If "-interactive" is included
in the options string, then interactive
mode is entered. The target object and
options strings vary depending on the
admin command invoked. Use help command
to get information on the target object
and options.
Explanation This message is for informational purposes only. Action No action is required.
WASX8002E: Invalid Command name: {0}
Explanation The command name is not a valid administrative command. Action Verify that the command name is correct.
WASX8003E: Invalid help arguments: {0}
Explanation The wsadmin tool cannot run the AdminTask help command. Action Verify that the number of arguments, command name, or command group name is correct. Use the AdminTask help command to view a list of valid commands for the help option.
WASX8004I: Available admin commands:
{0}
Explanation This message is for informational purposes only. Action No action is required.
WASX8005I: Available admin command groups:
{0}
Explanation This message is for informational purposes only. Action No action is required.
WASX8006I: Detailed help for command: {0}
Description: {1}
{2}Target object: {3}
Arguments:
{4}
Steps:
{5}
Explanation This message is for informational purposes only. Action No action is required.
WASX8007I: Detailed help for command group: {0}
Description: {1}
Commands:
{2}
Explanation This message is for informational purposes only. Action No action is required.
WASX8008E: Command {0} does not contain any step.
Explanation The command does not contain any step. Action Verify that step name is spelled correctly or use help command to view detailed help for the command.
WASX8009E: Invalid parameter: {0}
Explanation The command does not contain the specified parameter. Action Verify that parameter name is spelled correctly or use help command to view detailed help for the command.
WASX8010E: Invalid scripting language: {0}
Explanation The specified language is not supported. Action Specify a supported scripting language.
WASX8011W: AdminTask object is not available.
Explanation The wsadmin tool cannot connect to a server. Action Reissue the wsadmin command to create a server connection.
WASX8012E: Step {0} is not enabled.
Explanation The wsadmin tool cannot modify the data in the specified step. It is not enabled for the task. Action Reissue the AdminTask command without the step option indicated in this error message.
WASX8013I: Detailed help for step: {0}
Description: {1}
Collection: {2}
Arguments:
{3}
Explanation This message is for informational purposes only. Action No action is required.
WASX8014E: Step {0} is not a table.
Explanation More than one set of data values was specified for the step and is not a table. Action Provide one set of data values to the step indicated in this error message and reissue the AdminTask command.
WASX8015E: Invalid option value for step {0}: {1}
Explanation Option value provided to the specified step is not valid. Action Reissue the AdminTask command with the correct option value for step.
WASX8016E: Command provider error: null object type
Explanation The AdminTask command contains an internal error. Action Retry with scripting trace on and take a look wsadmin.traceout. If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
WASX8017E: Command provider error: step {0} does not contain any key
Explanation The AdminTask command contains an internal error. Action Retry with scripting trace on and take a look wsadmin.traceout. If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
WASX8018E: Cannot find a match for option value {0} for step {1}
Explanation The option values for the specified step do not match the existing data. Action Specify the correct option values for the step and reissue the AdminTask command.
WASX8019E: Incorrect number of key fields specified for step {0}: {1}
Explanation The option values provided to the specified step are not complete. Action Specify the correct number of key fields for the step and reissue the AdminTask command.
WASX8020E: An argument is required for parameter "{0}."
Explanation The specified parameter requires an accompanying argument. For example, if you specify "-node" follow "-node" with the name of a node: "-node mynode." Action Supply an argument for the indicated parameter.
WASX8021E: The wsadmin with version "{0}" connected to an incompatible server or dmgr with node version "{1}", which is not supported. "
Explanation The wsadmin tool is connecting to an incompatible version of the server or dmgr node. Action Verify that the server or dmgr node has same or higher version as wsadmin.sh. Connect to a compatible server or dmgr node.
WASX8022E: Incompatible node version; exception information: {0}
Explanation The wsadmin tool is connecting to an incompatible server or dmgr node. Action Ensure that wsadmin.sh connect to the same or higher version of the server or dmgr node.
WASX8023E: The upload file "{0}" does not exist for installation.
Explanation The file is not uploaded for installation. Action Ensure that this file exists and is readable.
WASX8024I: Cannot find the command or command group pattern: {0}
Explanation The command pattern specified is not found, try different pattern. Action Ensure that the searching pattern correctly.
WASX8025W: AdminConfig object is not available.
Explanation The AdminConfig command cannot be run because the configuration service is not available. Action Specify a server with a running configuration service and reissue the wsadmin command.
WSCP0138E: Expected '}' not found
Explanation There is a syntax error in a string provided in an attribute list Action Correct the attribute list syntax.
WSCP0140E: "{0}" found instead of expected '{'
Explanation There is a syntax error in a string provided in an attribute list Action Correct the attribute list syntax.
WSCP0142E: Unexpected '}' found
Explanation There is a syntax error in a string provided in an attribute list Action Correct the attribute list syntax.
WSCP0169E: Expected " not found
Explanation There is a syntax error in a string provided in an attribute list Action Correct the attribute list syntax.