WebSphere Management Scripting System Non WSCP Scripting

WASX7001I: wsadmin is the the executable for WebSphere scripting. Syntax: wsadmin [ -h(elp) ] [ -? ] [ -c ] [ -p ] [ -profile ] [ -f ] [ -javaoption java_option] [ -lang language] [ -wsadmin_classpath classpath] [ -conntype SOAP [-host host_name] [-port port_number] [-user userid] [-password password] | RMI [-host host_name] [-port port_number] [-user userid] [-password password] | JMS | NONE ] [ 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 executed 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 value is "jacl". "wsadmin_classpath" is a classpath 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_name" 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; "jms parms" is not supported yet; "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. 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 executed in order of their specification.

Explanation

None

User Response:

None

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.

User Response:

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.

User Response:

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.

User Response:

Reissue the wsadmin command with a host name following the -host option.

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.

User Response:

Reissue the wsadmin command with a port number following the -port option.

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.

User Response:

Reissue the wsadmin command with a scripting language name following the -lang option.

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.

User Response:

Reissue the wsadmin command with a connection type (e.g. SOAP, RMI) following 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.

User Response:

Reissue the wsadmin command with an integer port argument for the -port option.

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.

User Response:

Supply 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

An invalid connection type was supplied on the command line -conntype option or in the com.ws.scripting.connectionType property in the wsadmin.properties file.

User Response:

Correct the connection type on the command line or properties file: use "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 can not be found.

User Response:

Correct the name of the file specified by -p, -f, or -profile, 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.

User Response:

Examine the wsadmin.traceout log file to determine the problem; there may not be enough space in the file system, or there may be file permission problems.

WASX7013E: Cannot determine scripting language for file: "{0}" -- please specify "-lang" option on the command line.

Explanation

wsadmin cannot determine which scripting language to use for the specified file.

User Response:

Specify a -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

wsadmin cannot determine which scripting language to use for an interactive session.

User Response:

Specify a -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

An error occurred during the interactive execution of the specified command.

User Response:

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.

User Response:

Examine the wsadmin.traceout log file to determine the problem; there may not be enough space in the file system, or there may be file permission problems.

WASX7017E: Exception received while running file "{0}"; exception information: {1}

Explanation

An exception occurred while running a script or profile.

User Response:

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.

User Response:

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

Connection type information is required for wsadmin -- it can be specified either by the -conntype command line option or the com.ibm.ws.scripting.connectionType property in wsadmin.properties.

User Response:

Specify a valid connection type; this can be done either by 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

The specified connection type requires that a host be specified.

User Response:

Specify a valid host; this can be done either by 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

wsadmin cannot determine which scripting language to use with the -c option.

User Response:

Specify a -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

An error occurred during the execution of the specified command.

User Response:

Examine the exception information provided in the message to determine the appropriate course of action.

WASX7023E: Error creating "{0}" connection to host "{1}"; exception information: {2}

Explanation

An error was reported from the connector when trying to establish a connection to the host.

User Response:

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

wsadmin attempted to create an ObjectName object from a string that was incorrectly formatted.

User Response:

Insure that the string included in the failing command is correctly formatted for an ObjectName string. In particular, this can occur if the string is empty.

WASX7026W: String "{0}" corresponds to {1} different MBeans; returning first one.

Explanation

An AdminControl getConfigId or completeObjectName command was invoked; these commands only return a single result, but the ObjectName template passed in as an argument matches two or more running MBeans. This informational message is issued to indicate that the first matching MBean will be used.

User Response:

None, if the first matching MBean is sufficient. Otherwise, re-issue the command, specifying the desired MBean more completely.

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 Return 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 value pairs getCell returns the cell name of the connected server getConfigId Given String version of ObjectName, return a config 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 getPort returns String representation of port in use getType returns String representation of connection type in use help Show help information invoke_jmx Given ObjectName, name of method, array of parameters and signature, invoke method on MBean specified invoke Invoke a method on the specified MBean isRegistered_jmx true if supplied ObjectName is registered isRegistered true if supplied String version of ObjectName is registered makeObjectName Return 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. reconnect reconnects with server setAttribute_jmx Given ObjectName and Attribute object, set attribute for MBean specified setAttribute Given String version of ObjectName, attribute name and attribute value, set attribute for MBean specified setAttributes_jmx Given ObjectName and AttributeList object, set attributes for the MBean specified startServer Given the name of a server, start that server. stopServer Given the name of a server, stop that server. testConnection Test the connection to a DataSource object trace Set the wsadmin trace specification

Explanation

None

User Response:

None

WASX7028I: The Help object has two purposes: First, provide general help information for the the objects supplied by wsadmin for scripting: Help, AdminApp, AdminConfig, and AdminControl. 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 wsadmin returns general help text for the wsadmin script launcher message given a message id, returns explanation and user action message

Explanation

None

User Response:

None

WASX7029I: For help, enter: "$Help help"

Explanation

None

User Response:

None

WASX7030I: For help, enter: "Help.help()"

Explanation

None

User Response:

None

WASX7031I: For help, enter: "Help.help()"

Explanation

None

User Response:

None

WASX7032I: Method: getHost Arguments: none Description: Returns the host to which the scripting process is connected.

Explanation

None

User Response:

None

WASX7033I: Method: getPort Arguments: none Description: Returns the port used for scripting connection.

Explanation

None

User Response:

None

WASX7034I: Method: reconnect Arguments: none Description: Reconnects with the server

Explanation

None

User Response:

None

WASX7035I: Method: isAlive Arguments: none Description: TBD

Explanation

None

User Response:

None

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

None

User Response:

None

WASX7037I: Method: getMBeanCount Arguments: none Description: Returns number of registered beans

Explanation

None

User Response:

None

WASX7038I: Method: getDomainName Arguments: none Description: returns "WebSphere"

Explanation

None

User Response:

None

WASX7039I: Method: getDefaultDomain Arguments: none Description: returns "WebSphere"

Explanation

None

User Response:

None

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

None

User Response:

None

WASX7041I: Method: isInstanceOf Arguments: object name, classname Description: Returns true if MBean described by "object name" is of the class given by "classname."

Explanation

None

User Response:

None

WASX7042I: Method: isRegistered Arguments: object name Description: Returns true if supplied object name is registered.

Explanation

None

User Response:

None

WASX7043I: Method: getAttribute Arguments: object name, attribute Description: Returns value of "attribute" for the MBean described by "object name."

Explanation

None

User Response:

None

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

None

User Response:

None

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

None

User Response:

None

WASX7046I: Method: setAttributes Arguments: object name, attributes Description: Sets attributes given in "attributes" for the MBean described by "object name."

Explanation

None

User Response:

None

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

None

User Response:

None

WASX7048I: Method: makeObjectName Arguments: object name Description: Return an ObjectName object constructed from the "object name" string.

Explanation

None

User Response:

None

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

None

User Response:

None

WASX7050I: Method: trace Arguments: trace specification Description: Turns on the trace specified by "trace specification" in the scripting process.

Explanation

None

User Response:

None

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

None

User Response:

None

WASX7052I: Method: getType Arguments: none Description: Returns connection type used for scripting connection.

Explanation

None

User Response:

None

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 Show the attributes for a given type checkin Check a file into the the config 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 config repository. installResourceAdapter Installs a J2C resource adapter with the given rar file name and an option string in the node. 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 config repository. existsDocument Tests for the existence of a document in the config repository. extract Extract a file from the config repository. getCrossDocumentValidationEnabled Returns true if cross-document validation is enabled. getid Show the configId of an object, given a string version of its containment getObjectName Given a config id, return a string version of the ObjectName for the corresponding running MBean, if any. 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 Show help information list Lists all configuration objects of a given type listTemplates Lists all available configuration templates of a given type. modify Change specified attributes of a given configuration object parents Show 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 Discard unsaved configuration changes save Commit 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 Show the attributes of a given configuration object showall Recursively show 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 Show the possible types for configuration validate Invokes validation

Explanation

None

User Response:

None

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

None

User Response:

None

WASX7055I: Method: remove Arguments: config id Description: Removes the configuration object named by "config id."

Explanation

None

User Response:

None

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."

Explanation

None

User Response:

None

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

None

User Response:

None

WASX7058I: Method: modify Arguments: config id, attributes Description: Changes the attributes specified by "attributes" for the configuration object named by "config id."

Explanation

None

User Response:

None

WASX7059I: Method: getConfigId Arguments: object name Description: Returns a config id for the configuration object that corresponds to the MBean named by "object name." This function communicates with the config service to look up a config 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 config id of the first matching object found. Message WASX7026W is also displayed as a warning.

Explanation

None

User Response:

None

WASX7060I: Method: contents Arguments: type Description: Displays the object types that can be contained in "type."

Explanation

None

User Response:

None

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

None

User Response:

None

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

None

User Response:

None

WASX7063E: Error creating "{0}" connection to server: server may not be running; connector properties: {1}; exception information: {2}

Explanation

An error was reported from the connector when trying to establish a connection to the server.

User Response:

Examine the accompanying exception information and the information in the wsadmin.traceout file to determine the cause of the error. The server may not be running.

WASX7068I: Method: types Arguments: type Description: Displays all the possible top-level configuration object types.

Explanation

None

User Response:

None

WASX7070E: The configuration service is not available.

Explanation

This message is displayed when a wsadmin AdminConfig command is attempted and the wsadmin process is not connected to a server with a running config service.

User Response:

Reissue the wsadmin command, specifying a server with a running config service.

WASX7072E: The control service is not available.

Explanation

This message is logged when wsadmin is initialized and the wsadmin process cannot cconnect to a server.

User Response:

Reissue the wsadmin command so that a server connection is made.

WASX7073E: Attempt to reconnect to the server failed for the following objects: {0}; server may no longer be running.

Explanation

An AdminControl reconnect command failed to reconnect to the server.

User Response:

Examine the accompanying exception information and the information in the wsadmin.traceout file to determine the cause of the error. The server may not be running.

WASX7074I: Reconnect of {0} connector to host {1} completed.

Explanation

This informational message is displayed when an AdminControl reconnect command sucessfully completes.

User Response:

None

WASX7077E: Incomplete config id: need closing parenthesis in "{0}"

Explanation

An incorrect config id was specified for an AdminConfig command.

User Response:

Specify a valid config id -- such an id must have one of two forms: name(uri) or (uri). In this case, no closing parenthesis was found.

WASX7078E: Missing config id: no id found in "{0}"

Explanation

An incorrect config id was specified for an AdminConfig command.

User Response:

Specify a valid config id -- such an id must have one of two forms: name(uri) or (uri). In this case, no opening parenthesis was found.

WASX7079E: Unable to determine attribute information for type "{0}"

Explanation

An attribute was specified on an AdminConfig command that wsadmin is unable to process.

User Response:

This is an unexpected exception. The cause can not be immediately determined.

WASX7080E: Invalid attributes specified for type "{0}" -- "{1}"

Explanation

An invalid attribute name was specified for the given type.

User Response:

Correct the attribute name; use the AdminConfig attributes command for a list of valid attribute names.

WASX7081E: Error obtaining enum information: exception information: "{0}"

Explanation

An enum attribute could not be initialized by AdminConfig.

User Response:

This is an unexpected exception. The cause can not be immediately determined.

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 needs to determine what attribute name to use for the new object in the parent. In certain cases it is not possible to determine this information -- this is true if the parent object contains more than one attribute of the type being created.

User Response:

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

wsadmin cannot find the config object specified by an AdminConfig command.

User Response:

Check to be sure that a valid config object is specified.

WASX7084E: No help available for : "{0}"

Explanation

A help command has been invoked for some wsadmin object, but no help is available for the specified argument.

User Response:

Verify that is a valid argument for help. Issue the "help" command again without the argument for a list of valid possibilities.

WASX7085I: Method: getid Arguments: containment path Description: Returns the config id for an object described by the given containment path -- for example, /Node:myNode/Server:s1/JDBCProvider:jdbc1/

Explanation

None

User Response:

None

WASX7086E: Unable to determine relationship information for type "{0}"

Explanation

An AdminConfig parents command has failed with an unknown problem.

User Response:

This is an unexpected exception. The cause can not be immediately determined.

WASX7087E: Invalid value for attribute "{0}" -- valid values are "{1}"

Explanation

An AdminConfig create or modify command has specified an attribute of some ENUM type, but the value given to the attribute is not one of the allowed values.

User Response:

Specify one of the allowed values for this ENUM attribute -- the WASX7087E error message enumerates the possible values.

WASX7088E: Invalid numeric value specified for attribute "{0}"

Explanation

An AdminConfig create or modify command has specified an attribute of some numeric type, but the value given to the attribute is not a number.

User Response:

Specify a numeric value for the attribute.

WASX7090I: Executing command: "{0}"

Explanation

This is an informational message logging that this command was invoked.

User Response:

None

WASX7091I: Executing script: "{0}"

Explanation

This is an informational message logging that this script was invoked.

User Response:

None

WASX7092I: Command not logged; contains a password.

Explanation

This informational message is logged instead of WASX7090I if the command appears to contain a password.

User Response:

None

WASX7093I: Issuing message: "{0}"

Explanation

This informational message is logged when the subject message is displayed to the user.

User Response:

None

WASX7094I: Method: parents Arguments: type Description: Displays the object types that can contain "type."

Explanation

None

User Response:

None

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 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 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. edit Edit the properties of an application editInteractive Edit the properties of an application interactively export Export application to a file exportDDL Export DDL from application to a directory help Show 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. list List all installed applications listModules List the modules in a specified application options Shows the options available, either for a given file, or in general. publishWSDL Publish WSDL files for a given application 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 updateAccessIDs Updates the user/group binding information with accessID from user registry for a given application deleteUserAndGroupEntries Deletes all the user/group information for all the roles and all the username/password information for RunAs roles for a given application.

Explanation

None

User Response:

None

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

None

User Response:

None

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

None

User Response:

None

WASX7098I: Method: options Arguments: none Description: Displays the general options available for every application. Method: options Arguments: filename Description: Displays all the options available for installing the application in the file specified by "filename."

Explanation

None

User Response:

None

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

None

User Response:

None

WASX7100I: Method: list Arguments: none Description: Lists all installed applications

Explanation

None

User Response:

None

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

None

User Response:

None

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

None

User Response:

None

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

None

User Response:

None

WASX7105I: The following options are valid for any ear file:

Explanation

This informational message is displayed in response to an AdminApp options command. The install options valid for any ear file are displayed with it.

User Response:

None

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.

User Response:

The server.root property should be set by the wsadmin.bat or wsadmin.sh launcher. If you have modified this launcher, correct the changes. If not, contact IBM Support.

WASX7107E: Invalid options specified: "{0}"; valid options are: {1}

Explanation

One or more invalid options were specified for an AdminApp or AdminConfig command.

User Response:

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

Invalid data has been specified in an AdminApp install command for the specified task.

User Response:

Examine the errors reported for this task and correct the install command.

WASX7109E: Insufficient data for install task "{0}"

Explanation

Incomplete data has been specified in an AdminApp install command for the specified task.

User Response:

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

Invalid data has been specified in an AdminApp install command for the specified task. The task consists of some number of items, but a different number has been supplied.

User Response:

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

=Invalid data has been specified in 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 consitute a key for the data, and this key must be matched exactly by the information included in an install command for this task.

User Response:

Invoke the AdminApp taskInfo command for this file and task name to determine what information is needed for the task.

WASX7112I: The following tasks are valid for "{0}"

Explanation

This informational message is displayed in response to an AdminApp options command. All the valid options are displayed with it.

User Response:

None

WASX7113E: Task "{0}" not valid; valid tasks are "{1}"

Explanation

An AdminApp taskInfo command was invoked, but the supplied task name is not valid.

User Response:

Please supply a valid task name; the valid names are included in the WAS7113E message output.

WASX7114E: Cannot create temporary file in directory "{0}"

Explanation

wsadmin failed to copy an ear file to a temporary location for AdminApp processing.

User Response:

Examine the wsadmin.traceout log file to determine the problem; perhaps there may not be enough space in the file system, or there may be file permission problems.

WASX7115E: Cannot read input file "{0}"

Explanation

wsadmin failed to read an ear file when preparing to copy it to a temporary location for AdminApp processing.

User Response:

Examine the wsadmin.traceout log file to determine the problem; there may be file permission problems.

WASX7116E: Cannot copy file "{0}" to file "{1}"

Explanation

wsadmin failed to copy an ear file to a temporary location for AdminApp processing.

User Response:

Examine the wsadmin.traceout log file to determine the problem; there may not be enough space in the file system, or there may be file permission problems.

WASX7118I: Changes have been made to the configuration, but these changes have not been saved. Enter "quit" or "exit" if you want to terminate this session without saving your changes. To save the changes, invoke the "save" command on the AdminConfig object.

Explanation

The user has requested that an interactive scripting session be terminated, but configuration changes have been made during the session and have not been saved. The user is being given the opportunity to commit the unsaved changes.

User Response:

If you wish to exit the scripting session without saving changes, respond with "quit" or "exit." Any other response will keep the session active. Use the AdminConfig save command to commit the unsaved changes.

WASX7119E: Invalid option "{0}." Valid options are "overwriteOnConflict," and "rollbackOnConflict."

Explanation

An AdminConfig setSaveMode command was issued with an invalid mode.

User Response:

Please specify a valid save mode: valid options are "overwriteOnConflict," and "rollbackOnConflict."

WASX7120E: Diagnostic information from exception with text "{0}" follows: {1}

Explanation

This message is written into the log file when an exception is encountered. It is followed by information extracted from the exception.

User Response:

Examine the exception information in the log to try to determine the source of the problem.

WASX7121E: "{0}" found instead of expected '{'. {1}

Explanation

The specified string was found when '{' was expected in the input stream.

User Response:

Correct and re-issue the command.

WASX7122E: Expected "{0}" not found. {1}

Explanation

The specified string was not found in the expected location in the input stream.

User Response:

Correct and re-issue the command.

WASX7124I: Method: save Arguments: none Description: Commits unsaved changes to the configuration repository

Explanation

None

User Response:

None

WASX7125I: Method: reset Arguments: none Description: Discard unsaved configuration changes

Explanation

None

User Response:

None

WASX7126I: Method: hasChanges Arguments: none Description: Returns true if unsaved configuration changes exist

Explanation

None

User Response:

None

WASX7127I: Method: queryChanges Arguments: none Description: Returns a list of unsaved configuration files

Explanation

None

User Response:

None

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 config changes; and "rollbackOnConflict" to cause a save operation to fail if changes conflict with other config changes; this value is the default.

Explanation

None

User Response:

None

WASX7129E: Cannot create objects of type "{0}" in parents of type "{1}"

Explanation

An AdminConfig create command was attempted, but the specified parent was of an invalid type.

User Response:

Reissue the command, specifying a valid parent object for the object to be created.

WASX7132E: Application install for {0} failed: see previous messages for details.

Explanation

An AdminApp install command failed.

User Response:

See previous messages for details.

WASX7133E: Application uninstall of {0} failed: see previous messages for details.

Explanation

An AdminApp uninstall command failed.

User Response:

See previous messages for details.

WASX7134E: "{0}" option must be specified for war file installation.

Explanation

An AdminApp install command was invoked for a war file, but the "-contextroot" option was not supplied.

User Response:

Specify a "-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

An AdminControl invoke command was issued for an MBean operation, but there is no operation defined for that MBean that accepts the same number of parameters specified in the AdminControl invoke command.

User Response:

Reissue the invoke command using the correct number of parameters. The "operations" command on the Help object can be used 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

An AdminControl invoke command was issued, in which a different number of parameters and signature elements were specified. There must be exactly one signature element for every parameter.

User Response:

Reissue the invoke command using the correct number of signature and parameter elements, or reissue the command with no signature elements at all.

WASX7141E: Incorrect trace string supplied: "{0}"

Explanation

An AdminControl trace command was specified, but the supplied trace string is not valid.

User Response:

Ensure that the trace string is spelled correctly.

WASX7143E: The object with id "{0}" does not exist.

Explanation

During the processing of an AdminConfig command, a config id was found that does not correspond to an existing configuration object.

User Response:

Ensure 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

None

User Response:

None

WASX7146I: The following configuration files contain unsaved changes: {0}

Explanation

This informational message is displayed in response to the AdminConfig queryChanges command. Each file listed has been updated by the scripting client since the last save or reset command.

User Response:

None

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 config changes; and "rollbackOnConflict" to cause a save operation to fail if changes conflict with other config changes; this value is the default.

Explanation

None

User Response:

None

WASX7148I: Method: testConnection Arguments: config id Description: Tests the connection to a DataSource. The "config id" argument is the config id of a DataSource object. The DataSource object passed in has to be saved in the configuration before attempting to run testConnection.

Explanation

None

User Response:

None

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

None

User Response:

None

WASX7152I: This method is deprecated. Use exportDDL instead.

Explanation

None

User Response:

None

WASX7153I: "cell" option; specifies the cell name for AdminApp install functions.

Explanation

None

User Response:

None

WASX7154I: "node" option; specifies the node name for AdminApp install functions.

Explanation

None

User Response:

None

WASX7155I: "server" option; specifies the server name for AdminApp install functions.

Explanation

None

User Response:

None

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

None

User Response:

None

WASX7157I: "depl.extension.reg" option; specifies location of properties file for deployment extensions

Explanation

None

User Response:

None

WASX7158I: "usedefaultbindings" option; specifies that default bindings are to used for install. Default is "nousedefaultbindings"

Explanation

None

User Response:

None

WASX7159I: "nousedefaultbindings" option; specifies that default bindings are not used for install; this is the default setting.

Explanation

None

User Response:

None

WASX7160I: "defaultbinding.datasource.jndi" option; specifies the JNDI name for the default datasource

Explanation

None

User Response:

None

WASX7161I: "defaultbinding.datasource.username" option; specifies the user name for the default datasource

Explanation

None

User Response:

None

WASX7162I: "defaultbinding.datasource.password" option; specifies the password for the default datasource

Explanation

None

User Response:

None

WASX7163I: "defaultbinding.cf.jndi" option; specifies the JNDI name for the default connection factory

Explanation

None

User Response:

None

WASX7164I: "defaultbinding.cf.resauth" option; specifies the RESAUTH for the the connection factory.

Explanation

None

User Response:

None

WASX7165I: "defaultbinding.ejbjndi.prefix" option; specifies the prefix for the JNDI name of EJBs.

Explanation

None

User Response:

None

WASX7166I: "defaultbinding.virtual.host" option; specifies the default virtual host name.

Explanation

None

User Response:

None

WASX7167I: "defaultbinding.force" option; specifies that the default bindings should override current bindings.

Explanation

None

User Response:

None

WASX7168I: "defaultbinding.strategy.file" option; specifies a custom default bindings strategy file

Explanation

None

User Response:

None

WASX7169I: "deployejb" option; specifies that EJBDeploy should be run during install; the default is "nodeployejb"

Explanation

None

User Response:

None

WASX7170I: "nodeployejb" option; specifies that EJBDeploy should not be run during install; this is the default setting.

Explanation

None

User Response:

None

WASX7171I: "deployejb.dbname" option; specifies the database name for EJBDeploy; default is"was50."

Explanation

None

User Response:

None

WASX7172I: "deployejb.dbtype" option; specifies the database type for EJBDeploy; default is"CLOUDSCAPE_V50." Other options: DB2UDB_V72, DB2UDBOS390_V6, DB2UDBAS400_V4R5, INFORMIX_V73, INFORMIX_V92, MSSQLSERVER_V7, MSSQLSERVER_2000, ORACLE_V8, ORACLE_V9I, SYBASE_V1200

Explanation

None

User Response:

None

WASX7173I: "deployejb.dbschema" option; specifies the database schema for EJBDeploy

Explanation

None

User Response:

None

WASX7174I: "deployejb.classpath" option; specifies extra classpath to be used for EJBDeploy

Explanation

None

User Response:

None

WASX7175I: "deployejb.rmic" option; specifies extra RMIC options to be used for EJBDeploy

Explanation

None

User Response:

None

WASX7176I: "deployejb.validate" option; specifies that EJBDeploy should run validation; this is the default setting.

Explanation

None

User Response:

None

WASX7177I: "nodeployejb.validate" option; specifies that EJBDeploy should not run validation; the default setting is "deployejb.validate"

Explanation

None

User Response:

None

WASX7180I: "deployejb.preCompileJSPs" option; specifies that EJBDeploy should pre-compile JSPs; the default setting is "nodeployejb.preCompileJSPs"

Explanation

None

User Response:

None

WASX7181I: "nodeployejb.preCompileJSPs" option; specifies that EJBDeploy should not pre-compile JSPs; this is the default setting.

Explanation

None

User Response:

None

WASX7182I: "distributeApp" option; specifies that the application management component should distribute application binaries. This is the default setting.

Explanation

None

User Response:

None

WASX7183I: "nodistributeApp" option; specifies that the application management component should not distribute application binaries. The default setting is "distributeApp"

Explanation

None

User Response:

None

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

None

User Response:

None

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

None

User Response:

None

WASX7186I: "ddlprefix" option; specifies DDL prefix to use when invoking exportDDL.

Explanation

None

User Response:

None

WASX7187E: Invalid value "{0}" -- possible valid values are "{1}"

Explanation

An invalid value was specified for an AdminConfig command.

User Response:

sSpply a valid value as indicated in the error message.

WASX7188I: Cross-document validation enablement set to {0}

Explanation

An informational message issued in response to invoking the AdminConfig setCrossDocumentValidationEnabled.

User Response:

None

WASX7189I: Validation level set to {0}

Explanation

An informational message issued in response to invoking the AdminConfig setValidationLevel.

User Response:

None

WASX7190I: Validation at level {0} with cross-document validation {1}, requested at {2} for action "{3}"

Explanation

This informational message is written to the validation output file every time validation is requested.

User Response:

None

WASX7193I: Validation results are logged in {0}: Total number of messages: {1}

Explanation

This message is displayed when validation is complete.

User Response:

If desired, 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 is a summary of messages generated during configuration validation.

User Response:

None

WASX7195I: Severity {0}; line {1}; target "{2}"; {3}

Explanation

This message is logged to a file when validation is requested. By default, the name of the file is wsadmin.valout, located in the logs directory.

User Response:

If the message indicates a configuration problem, the configuration should be fixed.

WASX7196E: Cannot write to validation output file "{0}"

Explanation

During wsadmin initialization, an attempt is made to open an output file for validation results. This file exists, but wsadmin cannot write to it.

User Response:

Examine the wsadmin.traceout log file to determine the problem; there may not be enough space in the file system, or there may be file permission problems.

WASX7197E: Error creating validation output file {0}; exception information: {1}

Explanation

During wsadmin initialization, an attempt is made to open an output file for validation results. This file could not be created.

User Response:

Examine the wsadmin.traceout log file to determine the problem; there may not be enough space in the file system, or there may be file permission problems.

WASX7198W: The configuration service is not running. Configuration commands will not run.

Explanation

This message is displayed if no connection can be obtained to the config service.

User Response:

Restart wsadin so that a server connection is obtained.

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

None

User Response:

None

WASX7200I: Method: setValidationLevel Arguments: level Description: Sets the validation level to one of five possibilities: none, low, medium, high, or highest.

Explanation

None

User Response:

None

WASX7201I: Method: getValidationLevel Arguments: none Description: Returns a message giving the current validation level.

Explanation

None

User Response:

None

WASX7202I: Method: setCrossDocumentValidationEnabled Arguments: flag Description: Sets the cross-document validation enabled flag to true or false.

Explanation

None

User Response:

None

WASX7203I: Method: getCrossDocumentValidationEnabled Arguments: none Description: Returns a message giving the current cross-document enablement setting.

Explanation

None

User Response:

None

WASX7204I: Method: getObjectName; Arguments: configuration id Description: Returns a string version of the ObjectName for the MBean that corresponds to this configuration object. If there is no such running MBean this returns an empty string.

Explanation

None

User Response:

None

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" using the options specified by "options."

Explanation

None

User Response:

None

WASX7206W: The application management service is not running. Application management commands will not run.

Explanation

This message is displayed if no connection can be obtained to the application management service.

User Response:

Restart wsadmin so that a server connection is obtained 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

This is an informational message displayed when wsadmin initializes or when validation settings are changed.

User Response:

None

WASX7209I: Connected to process "{0}" on node {1} using {2} connector; The type of process is: {3}

Explanation

This is an informational message displayed when wsadmin connects to a server during initialization.

User Response:

None

WASX7210W: Cannot determine type of server; exception information: {0}

Explanation

During wsadmin initialization, an attempt is made to determine the type of server to which it is connected. This determination has failed.

User Response:

Examine the wsadmin.traceout file to determine the cause of the failure.

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.

Explanation

None

User Response:

None

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 config 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

None

User Response:

None

WASX7213I: This scripting client is not connected to a server process; please refer to the log file {0} for additional information.

Explanation

The wsadmin scripting client could not connect to a server using the options supplied on the command line and contained in wsadmin.properties files.

User Response:

If a connection is not needed, no action is necessary -- in this case, the "-conntype NONE" option could be specified on the wsadmin command line to indicate the no connection is desired; this will suppress WASX7213I. If a connection is needed, then wsadmin must be re-started with connection information that will allow it to connect to a running server. Perhaps the host or port information is incorrect.

WASX7214E: Cannot resolve confid id {0}

Explanation

For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.

User Response:

This is an unexpected exception. The cause can not be immediately determined.

WASX7215E: Cannot complete testConnection function because DataSourceCfgHelper MBean is not running. Please check to see if the server started correctly.

Explanation

The DataSourceCfgHelper MBean is needed to perform the testConnection function. It should be running in a server.

User Response:

If the wsadmin process is not connected to a server, invoke wsadmin so that a connection is established. If wsadmin is connected, access the IBM WebSphere Application Server Support webpage for futher problem determination.

WASX7217I: Connection to provided datasource was successful.

Explanation

An AdminControl "testConnection" command was successfully executed. The database adapter code reported no errors or warnings.

User Response:

None

WASX7219E: The {0} attribute must be specified if the {1} attribute has the value "{2}"

Explanation

There is a constraint on the specified attribute.

User Response:

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. You 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.

User Response:

Remove the "-local" option, or invoke wsadmin using the "-conntype NONE" option to avoid being connected to a server.

WASX7223I: "preCompileJSPs" option; use this option to specify that JSPs are to be precompiled. The default is nopreCompileJSPs.

Explanation

None

User Response:

None

WASX7224I: "nopreCompileJSPs" option; use this option to specify that JSPs are not to be precompiled. This is the default

Explanation

None

User Response:

None

WASX7225I: "validateApp" option; this option is obsolete

Explanation

None

User Response:

None

WASX7226I: "novalidateApp" option; this option is obsolete

Explanation

None

User Response:

None

WASX7227W: Profile {0} is in the wrong language and will not be executed; language used is {1}

Explanation

A profile has been specified for wsadmin operation. This profile is not in the same scripting language as the scripting session, so it will not be executed.

User Response:

Correct the wsadmin.properties file or the wsadmin command line options so that the profile is not specified.

WASX7229I: "installdir" option; specifies the directory into which the application binaries should be placed.

Explanation

None

User Response:

None

WASX7230I: "was.install.root" option; this option is obsolete

Explanation

None

User Response:

None

WASX7231I: "configroot" option; this option is obsolete

Explanation

None

User Response:

None

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

None

User Response:

None

WASX7233I: "verbose" option; this option causes additional messages to be displayed during install.

Explanation

None

User Response:

None

WASX7234I: "contextroot" option; use this option to specify the context root to be used when installing a stand-alone war file.

Explanation

None

User Response:

None

WASX7235I: "defaultbinding.virtual.host" option; default name for virtual host.

Explanation

None

User Response:

None

WASX7236I: "remotedir" option; this option is obsolete

Explanation

None

User Response:

None

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

An AdminControl setAttribute command has been invoked for an MBean, but the attribute is not of a type supported by wsadmin's setAttribute command.

User Response:

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

An expected error has occurred during AdminConfig modify or create.

User Response:

Examine the wsadmin.traceout log for more information about the failure.

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 is reset and the unsaved changes are lost. This message is informational only.

User Response:

None

WASX7241I: There are no unsaved changes in this workspace.

Explanation

This message issued in response to a "queryChanges" command for the AdminConfig object. It means that no changes have been made to the WebSphere configuration by this scripting process since the last "save" or "reset" AdminConfig command.

User Response:

None

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

None

User Response:

None

WASX7243I: "rar.desc" option; this option is a description of the J2CResourceAdapter.

Explanation

None

User Response:

None

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

None

User Response:

None

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. 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

None

User Response:

None

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

wsadmin initialization failed to connect to a server process because of a problem authenticating to the server.

User Response:

Ensure 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. Method: deleteUserAndGroupEntries Arguments: application name Description: Deletes all the user/group information for all the roles and RunAs roles for a given application.

Explanation

None

User Response:

None

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.

User Response:

Reissue the wsadmin command with a user name following the -user option.

WASX7250E: The "-password" option requires a password.

Explanation

The wsadmin launcher has been invoked with the -password option, but no password argument was found.

User Response:

Reissue the wsadmin command with a password following the -password option.

WASX7252E: Unable to locate running server "{0}".

Explanation

An AdminControl stopServer command has been issued, but a running server of the specified name cannot be found.

User Response:

Ensure that the server name is spelled correctly.

WASX7254E: "{0}" action not supported when process type is "{1}"

Explanation

An AdminControl startServer command has been issued, but the scripting client is connected to the wrong type of process.

User Response:

Ensure that the scripting client is connected to a Network Deployment Manager or Node Agent process.

WASX7255E: Cannot find server "{0}" in configuration data.

Explanation

An AdminControl startServer command has been issued, but there is no server of the specified name in the configuration.

User Response:

Ensure that the server is spelled correctly.

WASX7256W: Cannot locate NodeSync object on node "{0}". Unable to synchronize configurations before starting server "{1}"

Explanation

During AdminControl startServer invocation, an attempt is made to locate the NodeSync object on the node where the server is to be started. This message reports that the NodeSync object cannot be located. An attempt is made to start the server.

User Response:

The NodeSync object should be running; examine the logs on the node to determine why it is not.

WASX7257E: Cannot locate NodeAgent object on node "{0}". Unable to start server "{1}" on that node.

Explanation

An AdminControl startServer command has been issued, but there is no running NodeAgent on the server's node.

User Response:

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 600 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 milliseconds 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 milliseconds 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

None

User Response:

None

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.

Explanation

None

User Response:

None

WASX7262I: Start completed for server "{0}" on node "{1}"

Explanation

In response to an AdminControl startServer command, the specified server has been started on the specificed node.

User Response:

None

WASX7263W: Start not completed for server "{0}" on node "{1}". The server launching process may have timed out.

Explanation

A request has been made to start the specified server process. The scripting process will wait until the start is complete or the action times out. If it does time out, this message is issued.

User Response:

Check to see that the server has indeed started before continuing.

WASX7264I: Stop completed for server "{0}" on node "{1}"

Explanation

In response to an AdminControl stopServer command, the specified server has been stopped on the specificed node.

User Response:

None

WASX7265W: Stop not completed for server "{0}" on node "{1}". The stop process may have timed out.

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. If it does time out, this message is issued.

User Response:

Check to see that the server has indeed stopped before continuing.

WASX7266I: A was.policy file exists for this application; would you like to display it?

Explanation

None

User Response:

None

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

None

User Response:

None

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

None

User Response:

None

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

None

User Response:

None

WASX7270I: Method: constructors Arguments: MBean Description: Display information about the constructors of the specified MBean.

Explanation

None

User Response:

None

WASX7271I: Method: description Arguments: MBean Description: Display the description of the specified MBean.

Explanation

None

User Response:

None

WASX7272I: Method: notifications Arguments: MBean Description: Display information about the notifications sent by the specified MBean.

Explanation

None

User Response:

None

WASX7273I: Method: classname Arguments: MBean Description: Display information about the classname of the specified MBean.

Explanation

None

User Response:

None

WASX7274I: Method: classname Arguments: MBean Description: Display information about the attributes, operations, constructors, description, notifications, and classname of the specified MBean.

Explanation

None

User Response:

None

WASX7275I: Method: AdminConfig Arguments: none Description: Display general help information for the AdminConfig object provided by wsadmin.

Explanation

None

User Response:

None

WASX7276I: Method: AdminApp Arguments: none Description: Display general help information for the AdminApp object provided by wsadmin.

Explanation

None

User Response:

None

WASX7277I: Method: AdminControl Arguments: none Description: Display general help information for the AdminApp object provided by wsadmin.

Explanation

None

User Response:

None

WASX7278I: Generated command line: {0}

Explanation

This message is generated by the installInteractive and editInteractive AdminApp commands. It is accompanied by a string that can be modified (if needed) and copied into a script for use with the install or edit commands.

User Response:

None, unless the command string is needed for use in a script.

WASX7279E: An application with name "{0}" already exists. Select a different name.

Explanation

An AdminApp install command has been invoked for the specified application name, but this name is already being used.

User Response:

Specify a different application name using the "-appname" option.

WASX7280E: An application with name "{0}" does not exist.

Explanation

An AdminApp command has been invoked for the specified application, but it does not exist.

User Response:

Ensure that the application name is spelled correctly.

WASX7281E: Cannot install application using file "{0}". Ensure that this file exists and is readable.

Explanation

An AdminApp command has been invoked for the specified file, but it cannot be used.

User Response:

Ensure that this file exists and is readable.

WASX7282E: No editing tasks are available for application "{0}"

Explanation

An AdminApp edit or editInteractive command was invoked for the given application, but that application has no valid tasks to edit.

User Response:

None; there is nothing to edit for this application.

WASX7283E: This command requires an object of type "{0}", but the specified object "{1}" has type: "{2}"

Explanation

An AdminConfig command has been invoked that requires an argument to be an object of a specific type, but the object is not of that type.

User Response:

Invoke the command again, supplying an object of the correct type.

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. 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

None

User Response:

None

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

None

User Response:

None

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

None

User Response:

None

WASX7287I: Method: isRegistered_jmx Arguments: object name (type ObjectName) Description: Returns true if supplied "object name" is registered.

Explanation

None

User Response:

None

WASX7288I: Method: getAttribute_jmx Arguments: object name (type ObjectName), attribute (String) Description: Returns value of "attribute" for the MBean described by "object name."

Explanation

None

User Response:

None

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

None

User Response:

None

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

None

User Response:

None

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

None

User Response:

None

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

None

User Response:

None

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

None

User Response:

None

WASX7294I: Method: extract Arguments: documentURI, filename Description: Check a document out of the config repository. The "documentURI" must describe a document that exists in the repository, and "filename" must be a valid local filename where the contents of the document are written. This method returns an opaque "digest" object which should be used to check the file back in using the checkin command.

Explanation

None

User Response:

None

WASX7295I: Method: checkin Arguments: documentURI, filename, digest Description: Check a document in to the config repository. The "documentURI" must describe a document that exists in the repository, and "filename" must be a valid local filename where the contents of the document are located. The "digest" parameter should be the opaque object which was returned as a result of a previous extract call.

Explanation

None

User Response:

None

WASX7296E: The name specified is not the name of a file "{0}"

Explanation

An AdminConfig extract command was invoked, but the specified filename describes an existing file system entity that is not a file.

User Response:

The specified name is probably a directory name; reissue the extract command with a valid file name.

WASX7297E: Cannot write to file "{0}"

Explanation

An AdminConfig extract command was invoked, but the document data cannot be written to the specified file.

User Response:

Examine the wsadmin.traceout log file to determine the problem; perhaps there is not enough space in the file system, or perhaps there are file permission problems.

WASX7298E: Cannot invoke "{0}" command because this client is not connected to a Network Deployment Manager server.

Explanation

An AdminConfig command was invoked that requires connection to a Network Deployment Manager server, but the scripting client is not connected to such a server.

User Response:

Either connect to a Network Deployment Manager server or refrain from invoking this AdminConfig command.

WASX7299E: "-wsadmin_classpath" option must be followed by a classpath.

Explanation

The wsadmin launcher has been invoked with the -wsadmin_classpath option, but no classpath argument was found.

User Response:

Reissue the wsadmin command with a classpath following the -wsadmin_classpath option.

WASX7300I: Method: getValidationSeverityResult Arguments: severity Description: Returns the number of validation messages with the given severity from the most recent validation.

Explanation

None

User Response:

None

WASX7301E: Cannot get the task info for {0} using file {1}. Ensure that this file exists and is readable.

Explanation

An AdminApp taskInfo command was invoked, but no task information can be obtained for this task from the specified ear file.

User Response:

Ensure that this 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

An AdminApp options command was invoked, but no task options can be obtained from the specified ear file.

User Response:

Ensure that this file exists and is readable.

WASX7303I: The following unrecognized options are passed to the scripting environment and are available as argv: "{0}"

Explanation

Options included on the wsadmin command line which are not recognized as valid wsadmin options are assumed to be arguments to be used by wsadmin scripts or commands. They are made available to the script in the variable "argv" and a count of the number of these arguments is available in the variable "argc."

User Response:

If the unrecognized options were intended to be arguments used by scripts or commands, then no action is needed. If not, correct or delete the unrecognized options.

WASX7304I: Method: getNode Arguments: none Description: Returns the node to which the scripting process is connected.

Explanation

None

User Response:

None

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

A node agent process is being started; no configuration synchronization before startup is possible since the node agent is the entity responsible for the synchronization.

User Response:

None

WASX7306E: Cannot complete testConnection function because the node for Data Source "{0}" cannot be determined.

Explanation

An AdminControl testConnection command was invoked, but the node for the specified DataSource cannot be determined.

User Response:

Ensure that the DataSource is correctly configured.

WASX7307E: Cannot create object of type "{0}" on a Network Deployment Manager node.

Explanation

An invalid AdminConfig create command was invoked; this type of object can not be created.

User Response:

Change the create command as appropriate.

WASX7309W: No "save" was performed before the script "{0}" exited; configuration changes will not be saved.

Explanation

A script concluded without saving configuration changes. This informational message logs the fact that the changes are lost.

User Response:

Insure that AdminConfig "save" commands are executed at appropriate times.

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

None

User Response:

None

WASX7313I: Generating Dynamic Scripting Objects. Please Wait...

Explanation

This message signals that the scripting process is beginning to initialize the dynamic scripting objects.

User Response:

None

WASX7314I: Finished generating Dynamic Scripting Objects.

Explanation

This message signals that the dynamic scripting objects initialized when a scripting process begins are initialized.

User Response:

None

WASX7315W: Failed to generated dynamic scripting object: "{0}"

Explanation

A dynamic scripting object failed to initialize.

User Response:

This is an unexpected exception. The cause can not be immediately determined.

WASX7316W: Error creating Dynamic Scripting object. These objects will not be available -- "{0}". Please use the generic AdminControl facilities.

Explanation

An error occurred during the initialization of dynamic scripting objects.

User Response:

Use 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.

User Response:

This is an unexpected exception. The cause can not be immediately determined.

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

A server is being started by the wsadmin "startServer" command. Because no automatic configuration synchronization is performed, this message is emitted to inform the user that the configuration used by the starting server may not be the most recent configuration.

User Response:

If the configuration is known to be 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

A wsadmin AdminControl startServer command has been issued for a server that is already started.

User Response:

Check to see that you have specified the correct server name.

WASX7321I: Method: createDocument Arguments: documentURI, filename Description: Creates a document in the config repository. The "documentURI" names the document to be created in the repository, and "filename" must be a valid local filename where the contents of the document are located.

Explanation

None

User Response:

None

WASX7322I: Method: deleteDocument Arguments: documentURI Description: Deletes a document from the config repository. The "documentURI" names the document to be deleted from the repository.

Explanation

None

User Response:

None

WASX7323E: Cannot create directory "{0}"

Explanation

wsadmin failed to create a temporary directory for AdminApp processing.

User Response:

Examine the wsadmin.traceout log file to determine the problem; perhaps there is not enough space in the file system, or perhaps there are file permission problems.

WASX7324E: Cannot copy directory "{0}" to directory "{1}"

Explanation

wsadmin failed to copy an expanded ear directory to a temporary location for AdminApp processing.

User Response:

Examine the wsadmin.traceout log file to determine the problem; perhaps there is not enough space in the file system, or perhaps there are file permission problems.

WASX7326I: Loaded properties file "{0}"

Explanation

During the initialization of a scripting process, several properties files may be loaded. This is an informational message logged so the user or service representative can tell what properties files are in use.

User Response:

None

WASX7327I: Contents of was.policy file: {0}

Explanation

A listing of the was.policy security policy file associated with this application is displayed with this message. This is for informational purposes only.

User Response:

None

WASX7328E: A single attribute name must be specified for showAttribute; received: "{0}"

Explanation

The AdminConfig showAttribute command will only display the value of a single attribute, but multiple attribute names were supplied.

User Response:

Correct the command so that only a single attribute name is supplied.

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

None

User Response:

None

WASX7330I: "cluster" option; specifies the cluster name for AdminApp install functions.

Explanation

None

User Response:

None

WASX7331I: Unexpected exception received when querying for changes in this session: {0}

Explanation

An interactive scripting session is ending, and the scripting process is attempting to determine if configuration changes have been made during the session. An unexpected exception has occurred during the process of making this determination. The connection to the server process may have been broken prior to stopping the scripting session.

User Response:

None

WASX7332I: Method: getCell Arguments: none Description: Returns the cell to which the scripting process is connected.

Explanation

None

User Response:

None

WASX7333I: This option is deprecated. Use the "update" option instead.

Explanation

None

User Response:

None

WASX7334I: This option is deprecated. Use the "update.ignore.old" option instead.

Explanation

None

User Response:

None

WASX7335I: This option is deprecated. Use the "update.ignore.new" option instead.

Explanation

None

User Response:

None

WASX7336E: The "{0}" option is required if "{1}" is specified.

Explanation

In an AdminApp install command, a required option is missing.

User Response:

Invoke the command again, supplying the missing option.

WASX7337I: Invoked stop for server "{0}" 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.

User Response:

None

WASX7338E: Caught exception stopping server "{0}." Exception information: {1}

Explanation

An exception occurred during the processing of an AdminControl stopServer command.

User Response:

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

None

User Response:

None

WASX7340I: Method: existsDocument Arguments: documentURI Description: Tests to see if a document exists in the config repository. The "documentURI" names the document to be tested in the repository. Returns true the document exists; false otherwise.

Explanation

None

User Response:

None

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. This informational message logs the fact that the changes are lost.

User Response:

Insure that AdminConfig "save" commands are executed at appropriate times.

WASX7342I: Method: installResourceAdapter Arguments: rar file name, node, options Description: Install 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", and "rar.nativePath". 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 classpath.

Explanation

None

User Response:

None

WASX7343E: The specified node name "{0}" is not the same as the node "{1}" this client is currently connected to.",

Explanation

An AdminControl startServer command has been issued, but the node name specified is not the same as that currently connected to by the NodeAgent.

User Response:

Please insure that the node name is spelled correctly.

WASX7344E: Node name is required when the client is connected to process type "{0}".

Explanation

An AdminControl startServer command has been issued, but the node name is not specified.

User Response:

Please specify the node name to locate the server in the startServer command.

WASX7345E: Cannot find node "{0}" in configuration data.

Explanation

An AdminControl startServer command has been issued, but there is no node of the specified name in the configuration.

User Response:

Ensure that the node is spelled correctly.

WASX7346E: Cannot locate NodeAgent object for server "{0}" of process type {1}.

Explanation

An AdminControl stopServer command has been issued, but the NodeAgent for the specified server is not located in the configuration.

User Response:

Ensure 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 "-node" you need to follow "-node" with the name of a node: "-node mynode."

User Response:

Supply an argument for the indicated option, or remove the option from the command line.

WASX7348I: Each element of the {0} task consists of the following {1} fields: {2} Of these fields, the following may be assigned values: {3} and the following are required: {4} The current contents of the task after running default bindings are: {5}

Explanation

This message is the output in response to a "taskInfo" command for the AdminApp object. It details the task information requested.

User Response:

None

WASX7349I: Possible value for resource authorization is container or per connection factory

Explanation

None

User Response:

None

WASX7350E: This field requires container or per connection factory as the value. Please try again.

Explanation

This message is disaplyed during interactive application install when an incorrect value is entered for the resource authorization field.

User Response:

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

A "parents" command has been issued for an object type, but that type is not supported by the parents command.

User Response:

None

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. An exception is thrown containing the help information for this command.

User Response:

Please review 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

The convention for supplying attribute values that are collections of objects is that each object is a list of name-value pairs, and the collection of objects is a list of these objects. An example of a collection consisting of two objects would be: {{{attr1 val1a} {attr2 val2a}} {attr1 val1b} {attr2 val2b}}}.

User Response:

Correct the syntax of the command so that the attribute is notated as a collection.

WASX7354E: The attribute "{0}" is an embedded object of type "{1}"; an invalid value was supplied.

Explanation

The convention for supplying attribute values that are embedded objects is that the object is a list of name-value pairs. An example of an embedded object consisting of three attributes would be: {{attr1 val1a} {attr2 val2a}}.

User Response:

Correct the syntax of the command so that the embedded object is notated 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.

User Response:

Correct the syntax of the command so that attribute is notated correctly.

WASX7356E: Unrecognized argument: {0}. The specified argument is not a valid node name or wait time when connected to {1}.

Explanation

The argument to the startServer command is not valid.

User Response:

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

A request has been made with "-conntype NONE" option in the command line or specified in com.ws.scripting.connectionType property with NONE as the value in wsadmin.properties to not to connect to a running server. This is just informational purpose only.

User Response:

None

WASX7358E: Invalid option specified: {0}

Explanation

One or more invalid options were specified for an AdminApp command.

User Response:

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

AdminApp install/installInteractive has been invoked with the -reloadInterval option, but the value following this option is not an integer.

User Response:

Reissue the AdminApp command with an integer argument for the -reloadInterval option.

WASX7360I: Method: required Arguments: type Description: Displays the required attributes contained by an object of type "type".

Explanation

None

User Response:

None

WASX7361I: No required attribute found for type "{0}".

Explanation

AdminConfig required command returns no required attribute for the specified type.

User Response:

None

WASX7362I: Method: message Arguments: Message Id Description: Display information for given message id.

Explanation

None

User Response:

None

WASX7363E: No help available for message id {0}.

Explanation

Help message command can not locate any message information for the specified message id.

User Response:

If the specified message id is incorrect, then invoke the Help message command with the correct message id.

WASX7364E: Error getting help information for message id {0}.

Explanation

The directory containing the help information does not exist.

User Response:

This is an unexpected exception. The cause can not be immediately determined.

WASX7365I: Explanation: {0} User action: {1}

Explanation

None

User Response:

None

WASX7366I: "update" option; this option specifies that an application is to be updated using the supplied ear file. If this option is specified on an install command, the -appname option is required.

Explanation

None

User Response:

None

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

None

User Response:

None

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

None

User Response:

None

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

None

User Response:

None

WASX7370E: Error registering bean {0} provided in extension: {1}

Explanation

The bean provider specified in the extension xml cannot be registered with BSF.

User Response:

Understand what the exception is included in the trace log and correct the problem accordingly. If the problem persists, contact IBM support.

WASX7371E: Error locating the class for {0} provided in extension: {1}

Explanation

The implementation class provided in the extension xml is not found.

User Response:

Correct the implementation class in the extension xml if there is a typo in the class or make sure the class is in the classpath.

WASX7372E: Error instantiating the class for {0} provided in extension: {1}

Explanation

The implementation class provided in the extension xml can not be instantiated.

User Response:

Understand what the exception is included in the trace log and correct the problem accordingly. Make sure the class provided 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 more than once.

User Response:

Remove the duplicate implementation class in the extension xml.

WASX7374W: Missing element type {0} in {1} at line {2}. Ignoring this {3} element type.

Explanation

The extension xml contains element type reported in the warning message with required element type missing.

User Response:

Add the missing element type reported in the message to the extension xml.

WASX7375E: Element type {0} is already defined.

Explanation

The same element type is used more than once in the extension xml.

User Response:

Remove the extra element type in the extension xml.

WASX7376E: Invalid element end-tag: {0}

Explanation

The reported element tag in the extension xml is not supported.

User Response:

Remove the unsupported element tag in the extension xml.

WASX7377W: 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.

User Response:

Remove the duplicate type handler in the extension xml.

WASX7378I: "reloadEnabled" option; this option specifies whether to enable class reloading.

Explanation

none

User Response:

none

WASX7379E: Language "{0}" is not supported. Supported language is jacl.

Explanation

An unsupported scripting language was specified.

User Response:

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

None

User Response:

None

WASX7381I: "nodeployws" option; specifies to not deploy WebService during install; this is the default setting.

Explanation

None

User Response:

None

WASX7382I: "deployews.classpath" option; specifies extra classpath to be used to deploy WebServices

Explanation

None

User Response:

None

WASX7383I: "deployews.jardirs" option; specifies extra extension directories to be used to deploy WebServices

Explanation

None

User Response:

None

WASX7384I: "deployws" option; specifies to deploy WebServices during install; the default is "nodeployws"

Explanation

None

User Response:

None

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 specified by "soapAddressPrefixes". Method: publishWSDL Arguments: application name, filename Description: Publish WSDL files for the application specified to the file specified by "filename".

Explanation

None

User Response:

None

WASX7386E: {0} in {1} at line {2} column {3} {4}

Explanation

none

User Response:

none

WASX7387E: Operation not supported - testConnection command in AdminControl scripting object is not supported when connected to a 5.0 server.

Explanation

testConnection command is supported in server with version 5.1 and up.

User Response:

use testConnectionToDataSource method in DataSourceCfgHelper MBean to test connection of DataSource resided in 5.0 server.

WASX7388E: Connection to provided datasource failed.

Explanation

See previous messages for details.

User Response:

See previous messages for details.

WASX7389E: Operation not supported - getPropertiesForDataSource command is not supported.

Explanation

This command is not supported.

User Response:

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

This command is not supported.

User Response:

Do not use this command.

WASX7391W: The application is granted a permission defined in the filter.policy. This application could post a security threat to the application server. Review the application policy file. Do you want to continue with the application deployment process?

Explanation

The was.policy file contains permission defined in the filter.policy.

User Response:

Review the was.policy file resided in the application.

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 Secure Socket Layer configuration. Also note that FIPS approved JSSE provider only allows TLS protocol.

Explanation

None

User Response:

None

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

None

User Response:

None

WASX7402W: "Use FIPS" is enabled, but the SSL provider is not IBMJSSEFIPS. FIPS approved cryptographic algorithms may not be used.

Explanation

None

User Response:

None

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 Secure Socket Layer 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 that is used in all prior version of WAS products.

Explanation

None

User Response:

None

WSCP0138E: Expected '}' not found

Explanation

There is a syntax error in a string provided in an attribute list

User Response:

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

User Response:

Correct the attribute list syntax.

WSCP0142E: Unexpected '}' found

Explanation

There is a syntax error in a string provided in an attribute list

User Response:

Correct the attribute list syntax.

WSCP0169E: Expected " not found

Explanation

There is a syntax error in a string provided in an attribute list

User Response:

Correct the attribute list syntax.

WSCP7123E: Unexpected "{0}" found. {1}

Explanation

The specified character was found in an unexpected location in the input stream.

User Response:

Correct and re-issue the command.

WSCP7130E: The requested operation is not supported.

Explanation

This message is issued when an UnsupportedOperationException is received from an MBean, probably as the result of an AdminControl invoke command.

User Response:

Check the spelling of the operation attempted.

WSCP7131E: Runtime exception: "{0}"

Explanation

This message is issued when a RuntimeMBeanException is received from an MBean.

User Response:

Examine the exception information and modify the the failing command, as appropriate.