WASX

WASX7001I: wsadmin is the executable for WebSphere scripting.

Syntax:


wsadmin
   [ -h(elp) ]
   [ -? ]
   [ -c <command> ]
   [ -p <properties_file_name>]
   [ -profile <profile_script_name>]
   [ -f <script_file_name>]
   [ -javaoption java_option]
   [ -lang language]
   [ -wsadmin_classpath class path]
   [ -profileName profile]
   [ -conntype
      SOAP
         [-host host_name]
         [-port port_number]
         [-user userid]
         [-password password] |
      RMI
         [-host host_name]
         [-port port_number]
         [-user userid]
         [-password password] |
      JSR160RMI
         [-host host_name]
         [-port port_number]
         [-user userid]
         [-password password] |
      IPC
         [-ipchost host_name]
         [-port port_number]
         [-user userid]
         [-password password] |
      NONE
   ]
   [ -jobid <jobid_string>]
   [ -tracefile <trace_file>]
   [ -appendtrace <true/false>]
   [ script parameters ]


Where    "command" is a command to be passed to the script processor;
   "properties_file_name" is a java properties file to be used;
   "profile_script_name" is a script file to be run before the
      main command or file;
   "script_file_name" is a command to be passed to the script processor;
   "java_option" is a java standard or non-standard option to be passed
      to the java program;
   "language" is the language to be used to interpret scripts;
      supported values are "jacl" and "jython".
   "classpath" is a class path to be appended to built-in one;
   "-conntype" specifies the type of connection to be used;
      the default argument is "SOAP"
      a conntype of "NONE" means that no server connection is made
      and certain operations will be performed in local mode;
   "host_name" is the host used for the SOAP or RMI connection;
      the default is the local host;
   "port_number" is the port used for the SOAP or RMI connection;
   "userid" is the userid required when the server is running in
      secure mode;
   "password" is the password required when the server is running in
      secure mode;
   "script parameters" is anything else on the command line. These
      are passed to the script in the argv variable; the number of
      parameters is available in the argc variable.
   "jobid_string" is a jobID string to be used to audit each invocation
      of wsadmin;
   "trace_file" is the log file name and location where wsadmin trace
      output is directed;


If no command or script is specified, an interpreter shell is

created for interactive use. To leave an interactive scripting session,

use the "quit" or "exit" commands.


Several commands, properties files, and profiles may be specified

on a single command line. They are processed and run in

order of their specification.
WASX7002E: "-c" option must be followed by a command.
WASX7003E: "{0}" option must be followed by a file name.
WASX7004E: The "-host" option requires a host name.
WASX7005E: The "-port" option requires a port number.
WASX7006E: "-lang" option must be followed by a language identifier.
WASX7007E: "-conntype" option must be followed by connection type information.
WASX7008E: {0} connection type requires an integer port; found: "{1}"
WASX7009E: The "{0}" connection type requires that a port be specified in a properties file or with "-port" on the command line.
WASX7010E: Invalid connection type "{0}." Valid types are "SOAP," "RMI," "NONE," and "JMS."
WASX7011E: Cannot find file "{0}"
WASX7012E: Exception received while loading properties file {0}; exception information: "{1}"
WASX7013E: Cannot determine scripting language for file: "{0}" -- please specify "-lang" option on the command line.
WASX7014E: Cannot determine scripting language to use in interactive mode -- please specify "-lang" option on the command line.
WASX7015E: Exception running command: "{0}"; exception information:
{1}
WASX7016E: Exception received while reading file "{0}"; exception information: {1}
WASX7017E: Exception received while running file "{0}"; exception information: {1}
WASX7018E: Language "{0}" is not registered to BSF.
WASX7019E: No connection type specified; use "-conntype" on the command line.
WASX7020E: The "{0}" connection type requires that a host be specified in a properties file or with "-host" on the command line.
WASX7021E: Cannot determine scripting language for command invocation -- please specify "-lang" option on the command line.
WASX7022E: Problem running command "{0}" -- exception information: {1}
WASX7023E: Error creating "{0}" connection to host "{1}"; exception information: {2}
WASX7024E: Error creating "{0}" connection to host "{1}"; ensure that the correct IPC host is specified in the wsadmin.properties file or with "-ipchost" on the command line; exception information: {2}
WASX7025E: Error found in String "{0}"; cannot create ObjectName.
WASX7026W: String "{0}" corresponds to {1} different MBeans; returning first one.
WASX7027I: The AdminControl object enables the manipulation of MBeans running
   in a WebSphere server process. The number and type of MBeans available
   to the scripting client depends on the server to which the client is
   connected. If the client is connected to a Deployment Manager, then
   all the MBeans running in the Deployment Manager are visible as are all
   the MBeans running in the Node Agents connected to this Deployment
   Manager, and all the MBeans running in the application servers on those
   nodes.


   The following commands are supported by AdminControl; more detailed
   information about each of these commands is available by using the
   "help" command of AdminControl and supplying the name of the command
   as an argument.


   Note that many of these commands support two different sets of
   signatures: one that accepts and returns strings, and one low-level
   set that works with JMX objects like ObjectName and AttributeList.
   In most situations, the string signatures are likely to be more useful,
   but JMX-object signature versions are supplied as well. Each of these
   JMX-object signature commands has "_jmx" appended to the command name.
   Hence there is an "invoke" command, as well as a "invoke_jmx" command.



completeObjectName
      Returns a String version of an object name given a template
      name

getAttribute_jmx
      Given ObjectName and name of attribute, returns value of
      attribute

getAttribute   Given String version of ObjectName and name of attribute,
      returns value of attribute

getAttributes_jmx
      Given ObjectName and array of attribute names, returns
      AttributeList.

getAttributes   Given String version of ObjectName and attribute names,
      returns String of name value pairs. Given String version
      of ObjectName, returns String of all name value pairs.

getCell      Returns the cell name of the connected server

getConfigId   Given String version of ObjectName, return a configuration
      ID for the corresponding configuration object, if any

getDefaultDomain
      Returns "WebSphere"

getDomainName   Returns "WebSphere"

getHost      Returns String representation of connected host

getMBeanCount   Returns number of registered beans

getMBeanInfo_jmx
      Given ObjectName, returns MBeanInfo structure for MBean

getNode      Returns the node name of the connected server

getObjectInstance
      Given String version of ObjectName, returns ObjectInstance
      object that match.

getPort      Returns String representation of port in use

getType      Returns String representation of connection type in use

help      Shows help information

invoke_jmx   Given ObjectName, name of method, array of parameters and
      signature, invokes method on MBean specified

invoke      Invokes a method on the specified MBean

isRegistered_jmx
      Returns true if supplied ObjectName is registered

isRegistered   Returns true if supplied String version of ObjectName is
      registered

makeObjectName   Returns an ObjectName built with the given string

queryNames_jmx   Given ObjectName and QueryExp, retrieves set of ObjectNames
      that match.

queryNames   Given String version of ObjectName, retrieves String of
      ObjectNames that match

queryMBeans   Given String version of ObjectName, returns a set of
      ObjectInstances object that match

reconnect   Reconnects with server

setAttribute_jmx
      Given ObjectName and Attribute object, sets attribute for MBean
      specified

setAttribute   Given String version of ObjectName, attribute name and
      attribute value, sets attribute for MBean specified

setAttributes_jmx
      Given ObjectName and AttributeList object, sets attributes for
      the MBean specified

setAttributes   Given String version of ObjectName, attribute name
      and value pairs, sets attributes for the MBean specified

startServer   Given the name of a server, starts that server

stopServer   Given the name of a server, stops that server

testConnection   Tests the connection to a DataSource object

trace      Sets the wsadmin trace specification
WASX7028I: The Help object has two purposes:
   First, provide general help information for the objects
   supplied by wsadmin for scripting: Help, AdminApp, AdminConfig,
   AdminControl and AdminTask.
   Second, provide a means to obtain interface information about
   MBeans running in the system. For this purpose, a variety of
   commands are available to get information about the operations,
   attributes, and other interface information about particular
   MBeans.


   The following commands are supported by Help; more detailed
   information about each of these commands is available by using the
   "help" command of Help and supplying the name of the command
   as an argument.




attributes      Given an MBean, returns help for attributes

operations      Given an MBean, returns help for operations

constructors      Given an MBean, returns help for constructors

description      Given an MBean, returns help for description

notifications      Given an MBean, returns help for notifications

classname      Given an MBean, returns help for classname

all         Given an MBean, returns help for all the above

help         Returns this help text

AdminControl      Returns general help text for the AdminControl object

AdminConfig      Returns general help text for the AdminConfig object

AdminApp      Returns general help text for the AdminApp object

AdminTask      Returns general help text for the AdminTask object

wsadmin         Returns general help text for the wsadmin script
         launcher

message         Given a message id, returns explanation and user
         action message
WASX7029I: For help, enter: "$Help help"
WASX7030I: For help, enter: "Help.help()"
WASX7031I: For help, enter: "print Help.help()"
WASX7032I: Method: getHost
   Arguments: none
   Description: Returns the host to which the scripting process is
   connected.
WASX7033I: Method: getPort
   Arguments: none
   Description: Returns the port used for scripting connection.
WASX7034I: Method: reconnect
   Arguments: none
   Description: Reconnects with the server
WASX7035I: Method: isAlive
   Arguments: none
   Description: Is the client session alive?
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.
WASX7037I: Method: getMBeanCount
   Arguments: none
   Description: Returns number of registered beans
WASX7038I: Method: getDomainName
   Arguments: none
   Description: returns "WebSphere"
WASX7039I: Method: getDefaultDomain
   Arguments: none
   Description: returns "WebSphere"
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.
WASX7041I: Method: isInstanceOf
   Arguments: object name, classname
   Description: Returns true if MBean described by "object name" is of
   the class given by "classname."
WASX7042I: Method: isRegistered
   Arguments: object name
   Description: Returns true if supplied object name is registered.
WASX7043I: Method: getAttribute
   Arguments: object name, attribute
   Description: Returns value of "attribute" for the MBean described by
   "object name."
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".
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."
WASX7046I: Method: setAttributes
   Arguments: object name, attributes
   Description: Sets attributes given in "attributes" for the MBean
   described by "object name."
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."
WASX7048I: Method: makeObjectName
   Arguments: object name
   Description: Return an ObjectName object constructed from
   the "object name" string.
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.
WASX7050I: Method: trace
   Arguments: trace specification
   Description: Turns on the trace specified by "trace specification"
   in the scripting process.
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."
WASX7052I: Method: getType
   Arguments: none
   Description: Returns connection type used for scripting connection.
WASX7053I: The AdminConfig object communicates with the Config Service in a
   WebSphere server to manipulate configuration data for a WebSphere
   installation. AdminConfig has commands to list, create, remove,
   display, and modify configuration data, as well as commands to display
   information about configuration data types.


   Most of the commands supported by AdminConfig operate in two modes:
   the default mode is one in which AdminConfig communicates with the
   WebSphere server to accomplish its tasks. A local mode is also
   possible, in which no server communication takes place. The local
   mode of operation is invoked by bringing up the scripting client with
   no server connected using the command line "-conntype NONE" option
   or setting the "com.ibm.ws.scripting.connectionType=NONE" property in
   the wsadmin.properties.


   The following commands are supported by AdminConfig; more detailed
   information about each of these commands is available by using the
   "help" command of AdminConfig and supplying the name of the command
   as an argument.



attributes   Shows the attributes for a given type

checkin      Checks a file into the configuration repository

convertToCluster
      Converts a server to be the first member of a new ServerCluster

create      Creates a configuration object, given a type, a parent, and
      a list of attributes, and optionally an attribute name for the
      new object

createClusterMember
      Creates a new server that is a member of an existing cluster

createDocument   Creates a new document in the configuration repository

createUsingTemplate
      Creates an object using a particular template type

defaults   Displays the default values for attributes of a given type

deleteDocument   Deletes a document from the configuration repository

existsDocument   Tests for the existence of a document in the configuration
      repository

extract      Extracts a file from the configuration repository

getCrossDocumentValidationEnabled
      Returns true if cross-document validation is enabled

getid      Shows the configuration ID of an object, given a string version
      of its containment

getObjectName   Given a configuration ID, returns a string version of the
      ObjectName for the corresponding running MBean, if any

getObjectType   Given a configuration ID, returns a string version of the
      object type

getSaveMode   Returns the mode used when "save" is invoked

getValidationLevel
      Returns the validation used when files are extracted from the
      repository.

getValidationSeverityResult
      Returns the number of messages of a given severity from the
      most recent validation

hasChanges   Returns true if unsaved configuration changes exist

help      Shows help information

installResourceAdapter
      Installs a J2C resource adapter with the given rar file name
      and an option string in the node

list      Lists all configuration objects of a given type

listTemplates   Lists all available configuration templates of a given type

modify      Changes specified attributes of a given configuration object

parents      Shows the objects which contain a given type

queryChanges   Returns a list of unsaved files

remove      Removes the specified configuration object

required   Displays the required attributes of a given type.

reset      Discards unsaved configuration changes

resetAttributes   Resets value of the specified attributes.

save      Commits unsaved changes to the configuration repository

setCrossDocumentValidationEnabled
      Sets the cross-document validation enabled mode.

setSaveMode   Changes the mode used when "save" is invoked

setValidationLevel
      Sets the validation used when files are extracted from the
      repository.

show      Shows the attributes of a given configuration object

showall      Recursively shows the attributes of a given configuration
      object, and all the objects contained within each attribute.

showAttribute   Displays only the value for the single attribute specified.

types      Shows the possible types for configuration

uninstallResourceAdapter
      Uninstalls a J2C resource adapter with the given resource
      adapter configuration ID.

unsetAttributes   Unsets value of the specified attributes.

validate   Invokes validation
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"
WASX7055I: Method: remove
   Arguments: config id
   Description: Removes the configuration object named by "config id."
WASX7056I: Method: list
   Arguments: type
   Description: Lists all the configuration objects of the type named
   by "type."
   Method: list
   Arguments: type, scope
   Description: Lists all the configuration objects of the type named
   by "type" within the scope of the configuration object named by "scope."
   Method: list
   Arguments: type, pattern
   Description: Lists all the configuration objects of the type named
   by "type" matching with the wildcard "pattern".
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."
WASX7058I: Method: modify
   Arguments: config id, attributes
   Description: Changes the attributes specified by "attributes" for
   the configuration object named by "config id."
WASX7059I: Method: getConfigId
   Arguments: object name
   Description: Returns a configuration ID for the configuration object that
   corresponds to the MBean named by "object name." This function
   communicates with the configuration service to look up a configuration ID that
   can be used by AdminConfig. If no configuration object exists that
   corresponds to the supplied object name string, getConfigId returns an
   empty string.
   The object name string supplied as input to this function may be a
   wildcard -- for example:
      "type=Server,*"
   In this case, getConfigId returns the configuration ID of the first matching
   object found. Message WASX7026W is also displayed as a warning.
WASX7060I: Method: contents
   Arguments: type
   Description: Displays the object types that can be contained in "type."
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.
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.
WASX7063E: Error creating "{0}" connection to server: server may not be running; connector properties: {1}; exception information: {2}
WASX7068I: Method: types
   Arguments: none
   Description: Displays all the possible top-level configuration
   object types.
   Method: types
   Arguments: pattern
   Description: Displays all the possible top-level configuration
   object types matching with the wildcard "pattern".
WASX7070E: The configuration service is not available.
WASX7072E: The control service is not available.
WASX7073E: Attempt to reconnect to the server failed for the following objects: {0}; server may no longer be running.
WASX7074I: Reconnect of {0} connector to host {1} completed.
WASX7077E: Incomplete config id: need closing parenthesis in "{0}"
WASX7078E: Missing config id: no id found in "{0}"
WASX7079E: Unable to determine attribute information for type "{0}"
WASX7080E: Invalid attributes specified for type "{0}" -- "{1}"
WASX7081E: Error obtaining enum information: exception information: "{0}"
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}
WASX7083E: Cannot find config object: "{0}"
WASX7084E: No help available for : "{0}"
WASX7085I: Method: getid
   Arguments: containment path
   Description: Returns the configuration ID for an object described by the
   given containment path -- for example, /Node:myNode/Server:s1/JDBCProvider:jdbc1/
WASX7086E: Unable to determine relationship information for type "{0}"
WASX7087E: Invalid value for attribute "{0}" -- valid values are "{1}"
WASX7088E: Invalid numeric value specified for attribute "{0}"
WASX7090I: Executing command: "{0}"
WASX7091I: Executing script: "{0}"
WASX7092I: Command not logged; contains a password.
WASX7093I: Issuing message: "{0}"
WASX7094I: Method: parents
   Arguments: type
   Description: Displays the object types that can contain "type."
WASX7095I: The AdminApp object allows application objects to be manipulated
   -- this includes installing, uninstalling, editing, and listing. Most
   of the commands supported by AdminApp operate in two modes: the default
   mode is one in which AdminApp communicates with the WebSphere server to
   accomplish its tasks. A local mode is also possible, in which no
   server communication takes place. The local mode operation is invoked
   by bringing up the scripting client with no server connected using the
   command line "-conntype NONE" option tor setting the
   "com.ibm.ws.scripting.connectionType=NONE" property in the
   wsadmin.properties.


   The following commands are supported by AdminApp; more detailed
   information about each of these commands is available by using the
   "help" command of AdminApp and supplying the name of the command
   as an argument.



deleteUserAndGroupEntries
      Deletes all the user/group information for all the roles and
      all the user name/password information for RunAs roles for a
      given application

edit      Edits the properties of an application

editInteractive   Edits the properties of an application interactively

export      Exports application to a file

exportDDL   Exports DDL from application to a directory

exportFile   Exports content of a single file from an application to a file

getDeployStatus   Returns the combined Deployment status of the application

help      Shows help information

install      Installs an application, given a file name and an option string

installInteractive
      Installs an application in interactive mode, given a file name
      and an option string

isAppReady   Checks whether the application is ready to be run

list      Lists all installed applications

listModules   Lists the modules in a specified application

options      Shows the options available, for a given file, application,
      or in general

renameApplication   Rename a given application

publishWSDL   Publishs WSDL files for a given application

searchJNDIReferences
      Lists application that refers to the given JNDIName on a given
      node

taskInfo   Shows detailed information pertaining to a given install task
      for a given file

uninstall   Uninstalls an application, given an application name and
      an option string

update      Updates an installed application

updateAccessIDs   Updates the user/group binding information with accessID
      from user registry for a given application

updateInteractive   Updates an installed application interactively

view      Views an application or module, given an application or
      module name
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.
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.
WASX7098I: Method: options
   Arguments: none
   Description: Displays the general options available for every
   application to be installed.
   Method: options
   Arguments: filename
   Description: Displays all the options available for installing the
   application in the file specified by "filename".
   Method: options
   Arguments: appname
   Description: Displays all the options available for editing the
   application specified by "appname".
   Method: options
   Arguments: modulename
   Description: Displays all the options available for editing the
   application module specified by "modulename".
   Method: options
   Arguments: filename, operation
   Description: Displays all the options available for the
   file specified by "filename" using the specified operation.
   Valid operations are "installapp", "updateapp", "addmodule",
   and "updatemodule".
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"
WASX7100I: Method: list
   Arguments: none
   Description: Lists all installed applications
   Method: list
   Arguments: target scope
   Description: List installed applications on a given "target scope"
   For example, WebSphere:cell=myCell,node=myNode,server=myServer or
   WebSphere:cell=myCell,cluster=myCluster.
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.
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.
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.
WASX7105I: The following install options are valid for any ear file:
WASX7106E: Unable to determine root of WebSphere installation. Please specify the "{0}" option on the command line.
WASX7107E: Invalid options specified: "{0}"; valid options are:
{1}
WASX7108E: Invalid data specified for install task: "{0}." Errors are: "{1}"
WASX7109E: Insufficient data for install task "{0}"
WASX7110E: Incorrect number of elements in option: "{0}" for task: "{1};" number of elements should be {2}.
WASX7111E: Cannot find a match for supplied option: "{0}" for task "{1}". The supplied option must match with the existing task data in the application and the existing task data are: "{2}"
WASX7112I: The following options are valid for "{0}"
WASX7113E: Task "{0}" not valid; valid tasks are "{1}"
WASX7114E: Cannot create temporary file in directory "{0}"
WASX7115E: Cannot read input file "{0}"
WASX7116E: Cannot copy file "{0}" to file "{1}"
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.
WASX7119E: Invalid option "{0}." Valid options are "overwriteOnConflict," and "rollbackOnConflict."
WASX7120E: Diagnostic information from exception with text "{0}" follows:

{1}
WASX7121E: "{0}" found instead of expected "{". {1}
WASX7122E: Expected "{0}" not found. {1}
WASX7123E: Unexpected "{0}" found. {1}
WASX7124I: Method: save
   Arguments: none
   Description: Commits unsaved changes to the configuration repository
WASX7125I: Method: reset
   Arguments: none
   Description: Discard unsaved configuration changes
WASX7126I: Method: hasChanges
   Arguments: none
   Description: Returns true if unsaved configuration changes exist
WASX7127I: Method: queryChanges
   Arguments: none
   Description: Returns a list of unsaved configuration files
WASX7128I: Method: setSaveMode
   Arguments: save mode
   Description: Changes the mode used when "save" is invoked.
   Possible values are:
      "overwriteOnConflict" to save changes even if they conflict
      with other configuration changes; and
      "rollbackOnConflict" to cause a save operation to fail if
      changes conflict with other configuration changes;
      this value is the default.
WASX7129E: Cannot create objects of type "{0}" in parents of type "{1}"
WASX7130E: The requested operation is not supported.
WASX7131E: Runtime exception: "{0}"
WASX7132E: Application install for {0} failed: see previous messages for details.
WASX7133E: Application uninstall of {0} failed: see previous messages for details.
WASX7134E: "{0}" option must be specified for war file installation.
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}."
WASX7140E: Length mismatch: {0} parameters were specified, but {1} signatures were supplied. The same number must be specified for both.
WASX7141E: Incorrect trace string supplied: "{0}"
WASX7143E: The object with id "{0}" does not exist.
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.
WASX7146I: The following configuration files contain unsaved changes:
{0}
WASX7147I: Method: getSaveMode
   Arguments: none
   Description: Returns the mode used when "save" is invoked.
   Possible values are:
      "overwriteOnConflict" to save changes even if they conflict
      with other configuration changes; and
      "rollbackOnConflict" to cause a save operation to fail if
      changes conflict with other configuration changes;
      this value is the default.
WASX7148I: Method: testConnection
   Arguments: config id
   Description: Tests the connection to a DataSource. The "config id"
   argument is the configuration ID of a DataSource object. The DataSource
   object passed in has to be saved in the configuration before
   attempting to run testConnection.
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."
WASX7152I: This method is deprecated. Use exportDDL instead.
WASX7153I: "cell" option; specifies the cell name for AdminApp install functions.
WASX7154I: "node" option; specifies the node name for AdminApp install functions.
WASX7155I: "server" option; specifies the server name for AdminApp install functions.
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.
WASX7157I: "depl.extension.reg" option; specifies location of properties file for deployment extensions.

This option is deprecated. There is no replacement for this option.
WASX7158I: "usedefaultbindings" option; specifies that default bindings are to used for install. Default is "nousedefaultbindings"
WASX7159I: "nousedefaultbindings" option; specifies that default bindings are not used for install; this is the default setting.
WASX7160I: "defaultbinding.datasource.jndi" option; specifies the JNDI name for the default datasource
WASX7161I: "defaultbinding.datasource.username" option; specifies the user name for the default datasource
WASX7162I: "defaultbinding.datasource.password" option; specifies the password for the default datasource
WASX7163I: "defaultbinding.cf.jndi" option; specifies the JNDI name for the default connection factory
WASX7164I: "defaultbinding.cf.resauth" option; specifies the RESAUTH for the connection factory.
WASX7165I: "defaultbinding.ejbjndi.prefix" option; specifies the prefix for the JNDI name of EJBs.
WASX7166I: "defaultbinding.virtual.host" option; specifies the default virtual host name.
WASX7167I: "defaultbinding.force" option; specifies that the default bindings should override current bindings.
WASX7168I: "defaultbinding.strategy.file" option; specifies a custom default bindings strategy file
WASX7169I: "deployejb" option; specifies that EJBDeploy should be run during install; the default is "nodeployejb"
WASX7170I: "nodeployejb" option; specifies that EJBDeploy should not be run during install; this is the default setting.
WASX7171I: "deployejb.dbname" option; specifies the database name for EJBDeploy; default is"was50."
WASX7172I: "deployejb.dbtype" option; specifies the database type for EJBDeploy; valid values are {0}.
WASX7173I: "deployejb.dbschema" option; specifies the database schema for EJBDeploy
WASX7174I: "deployejb.classpath" option; specifies extra classpath to be used for EJBDeploy
WASX7175I: "deployejb.rmic" option; specifies extra RMIC options to be used for EJBDeploy
WASX7176I: "deployejb.validate" option; specifies that EJBDeploy should run validation; this is the default setting.
WASX7177I: "nodeployejb.validate" option; specifies that EJBDeploy should not run validation; the default setting is "deployejb.validate"
WASX7180I: "deployejb.preCompileJSPs" option; specifies that EJBDeploy should pre-compile JSPs; the default setting is "nodeployejb.preCompileJSPs"
WASX7181I: "nodeployejb.preCompileJSPs" option; specifies that EJBDeploy should not pre-compile JSPs; this is the default setting.
WASX7182I: "distributeApp" option; specifies that the application management component should distribute application binaries. This is the default setting.
WASX7183I: "nodistributeApp" option; specifies that the application management component should not distribute application binaries. The default setting is "distributeApp"
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.
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.
WASX7186I: "ddlprefix" option; specifies DDL prefix to use when invoking exportDDL.
WASX7187E: Invalid value "{0}" -- possible valid values are "{1}"
WASX7188I: Cross-document validation enablement set to {0}
WASX7189I: Validation level set to {0}
WASX7190I: Validation at level {0} with cross-document validation {1}, requested at {2} for action "{3}"
WASX7193I: Validation results are logged in {0}: Total number of messages: {1}
WASX7194I: Number of messages of severity {0}: {1}
WASX7195I: Severity {0}; line {1}; target "{2}";   {3}
WASX7196E: Cannot write to validation output file "{0}"
WASX7197E: Error creating validation output file {0}; exception information: {1}
WASX7198W: The configuration service is not running. Configuration commands will not run.
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."
WASX7200I: Method: setValidationLevel
   Arguments: level
   Description: Sets the validation level to one of five possibilities:
   none, low, medium, high, or highest.
WASX7201I: Method: getValidationLevel
   Arguments: none
   Description: Returns a message giving the current validation level.
WASX7202I: Method: setCrossDocumentValidationEnabled
   Arguments: flag
   Description: Sets the cross-document validation enabled flag to
   true or false.
WASX7203I: Method: getCrossDocumentValidationEnabled
   Arguments: none
   Description: Returns a message giving the current cross-document
   enablement setting.
WASX7204I: Method: getObjectName;
   Arguments: config id
   Description: Returns a string version of the ObjectName for the MBean
   that corresponds to this configuration ID. If there is no such
   running MBean this returns an empty string.
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".
WASX7206W: The application management service is not running. Application management commands will not run.
WASX7208I: Validation settings in effect now: Level={0}, Cross-validation={1}, Output file={2}
WASX7209I: Connected to process "{0}" on node {1} using {2} connector; The type of process is: {3}
WASX7210W: Cannot determine type of server; exception information: {0}
WASX7211I: Method: listTemplates
   Arguments: type
   Description: Returns a list of the templates available for the given
   type. These templates may be used in invocations of
   createUsingTemplate.
   Method: listTemplates
   Arguments: type, match
   Description: Returns a list of the templates with display names
   that contain the string specified by "match" available for the given
   type. These templates may be used in invocations of
   createUsingTemplate.
   Method: listTemplates
   Arguments: type, pattern
   Description: Returns a list of the templates with display names
   that contain the string matching with the wildcard "pattern" for the
   given type. These templates may be used in invocations of
   createUsingTemplate.
WASX7212I: Method: createUsingTemplate
   Arguments: type, parent, attributes, template
   Description: Creates an object of the given type with the given
   parent. The specified template is used as the basis for this new
   object, and the specified attributes override settings in the template.
   The template parameter is a configuration ID of an existing object -- .
   this object can be either a template object, returned by using the
   listTemplates command, or any other existing object of the correct type.
WASX7213I: This scripting client is not connected to a server process; please refer to the log file {0} for additional information.
WASX7214E: Cannot resolve confid id {0}
WASX7215E: Cannot complete testConnection function because DataSourceCfgHelper MBean is not running. Please check to see if the server started correctly.
WASX7217I: Connection to provided datasource was successful.
WASX7219E: The {0} attribute must be specified if the {1} attribute has the value "{2}"
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.
WASX7223I: "preCompileJSPs" option; use this option to specify that JSPs are to be precompiled. The default is nopreCompileJSPs.
WASX7224I: "nopreCompileJSPs" option; use this option to specify that JSPs are not to be precompiled. This is the default.
WASX7225I: "validateApp" option; this option is obsolete
WASX7226I: "novalidateApp" option; this option is obsolete
WASX7227W: Profile {0} is in the wrong language and will not be executed; language used is {1}
WASX7229I: "installdir" option; specifies the directory into which the application binaries should be placed.

This option is deprecated. It is replaced by installed.ear.destination option.
WASX7230I: "was.install.root" option; this option is obsolete
WASX7231I: "configroot" option; this option is obsolete
WASX7232I: "appname" option; use this option to specify the name of the application. The default is to use the display name of the application.
WASX7233I: "verbose" option; this option causes additional messages to be displayed during install.
WASX7234I: "contextroot" option; use this option to specify the context root to be used when installing a stand-alone war file.
WASX7235I: "defaultbinding.virtual.host" option; default name for virtual host.
WASX7236I: "remotedir" option; this option is obsolete
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.
WASX7239E: Unexpected error setting attribute "{0}" of type "{1}" to value "{2}." Additional information may be found in the trace log.
WASX7240I: Resetting workspace at the start of a scripting session; workspace reports unsaved changes in the following files:
{0}
WASX7241I: There are no unsaved changes in this workspace.
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.
WASX7243I: "rar.desc" option; this option is a description of the J2CResourceAdapter.
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
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.
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}"
WASX7247I: Method: deleteUserAndGroupEntries
   Arguments: application name
   Description: Deletes all the user/group information for all the roles
   and RunAs roles for a given application.
WASX7249E: The "-user" option requires a user name.
WASX7250E: The "-password" option requires a password.
WASX7252E: Unable to locate running server "{0}" on node "{1}".
WASX7254E: "{0}" action not supported when process type is "{1}"
WASX7255E: Cannot find server "{0}" in configuration data.
WASX7256W: Cannot locate NodeSync object on node "{0}". Unable to synchronize configurations before starting server "{1}"
WASX7257E: Cannot locate NodeAgent object on node "{0}". Unable to start server "{1}" on that node.
WASX7258I: Method: startServer
   Arguments: server name
   Description: Starts a server by locating it in the configuration
   and asking that node"s NodeAgent to start the server. This command
   uses the default wait time of 1200 seconds. Note that this version
   of the command can only be used if the scripting process is attached
   to a Node Agent server.
   Method: startServer
   Arguments: server name, wait time
   Description: Starts a server by locating it in the configuration,
   synchronizing configuration data with the server"s node,
   and asking that node"s NodeAgent to start the server. The start
   process waits the number of seconds specified by "waittime"
   for the server to start. Note that this version of the command can
   only be used if the scripting process is attached to a Node Agent
   server.
   Method: startServer
   Arguments: server name, node name
   Description: Starts a server in the specified node by locating it in
   the configuration, synchronizing configuration data with the server"s
   node and asking that node"s NodeAgent to start the server. This version
   of the command can be used when the scripting process is attached
   either to a Node Agent or Deployment Manager process.
   Method: startServer
   Arguments: server name, node name, wait time
   Description: Starts a server in the specified node by locating it in
   the configuration, synchronizing configuration data with the server"s
   node and asking that node"s NodeAgent to start the server. The start
   process waits the number of seconds specified by "waittime"
   for the server to start. This version of the command can be used when
   the scripting process is attached either to a Node Agent or Deployment
   Manager process.
WASX7259I: Method: stopServer
   Arguments: server name
   Description: Stops a server.
   Method: stopServer
   Arguments: server name, immediate flag
   Description: Stops a server. If the "immediate flag" is set to
   "immediate" then a stopImmediate is performed for the specified
   server. Otherwise, a normal stop is performed.
   Method: stopServer
   Arguments: server name, node name
   Description: Stops a server in the specified node.
   Method: stopServer
   Arguments: server name, node name, immediate flag
   Description: Stops a server in the specified node. If the
   "immediate flag" is set to "immediate" then a stopImmediate
   is performed for the specified server. Otherwise, a normal
   stop is performed.
   Method: stopServer
   Arguments: server name, node name, terminate flag
   Description: Stops a server on the specified node. If the
   "terminate flag" is set to "terminate" then a terminate
   is performed for the specified server. Otherwise, a normal stop
   is performed.
   This operation can only be performed on a Managed Process.
   The node name is a required argument.
WASX7262I: Start completed for server "{0}" on node "{1}"
WASX7263W: Start not completed for server "{0}" on node "{1}". The server launching process may have timed out.
WASX7264I: Stop completed for server "{0}" on node "{1}"
WASX7265W: Stop not completed for server "{0}" on node "{1}". The stop process may have timed out.
WASX7266I: A was.policy file exists for this application; would you like to display it?
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.
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.
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.
WASX7270I: Method: constructors
   Arguments: MBean
   Description: Display information about the constructors of the
   specified MBean.
WASX7271I: Method: description
   Arguments: MBean
   Description: Display the description of the specified MBean.
WASX7272I: Method: notifications
   Arguments: MBean
   Description: Display information about the notifications sent by
   the specified MBean.
WASX7273I: Method: classname
   Arguments: MBean
   Description: Display information about the classname of the
   specified MBean.
WASX7274I: Method: classname
   Arguments: MBean
   Description: Display information about the attributes,
   operations, constructors, description, notifications,
   and classname of the specified MBean.
WASX7275I: Method: AdminConfig
   Arguments: none
   Description: Display general help information for the
   AdminConfig object provided by wsadmin.
WASX7276I: Method: AdminApp
   Arguments: none
   Description: Display general help information for the
   AdminApp object provided by wsadmin.
WASX7277I: Method: AdminControl
   Arguments: none
   Description: Display general help information for the
   AdminControl object provided by wsadmin.
WASX7278I: Generated command line: {0}
WASX7279E: An application with name "{0}" already exists. Select a different name.
WASX7280E: An application with name "{0}" does not exist.
WASX7281E: Cannot install application using file "{0}". Ensure that this file exists and is readable.
WASX7282E: No editing tasks are available for application "{0}"
WASX7283E: This command requires an object of type "{0}", but the specified object "{1}" has type: "{2}"
WASX7284I: Method: createClusterMember
   Arguments: cluster id, node id, member attributes
   Description: Creates a new Server object on the node specified
   by "node id." This Server is created as a new member of the existing
   cluster specified by "cluster id," and has attributes specified in
   "member attributes." One attribute is required: "memberName."
   The Server is created using the default template for
   Server objects, and has the name and specified by the
   "memberName" attribute.
   Method: createClusterMember
   Arguments: cluster id, node id, member attributes, template id
   Description: Creates a new Server object on the node specified
   by "node id." This Server is created as a new member of the existing
   cluster specified by "cluster id," and has attributes specified in
   "member attributes." One attribute is required: "memberName."
   The Server is created using the Server template
   specified by "template id," and has the name specified by
   the "memberName" attribute.
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.
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."
WASX7287I: Method: isRegistered_jmx
   Arguments: object name (type ObjectName)
   Description: Returns true if supplied "object name" is registered.
WASX7288I: Method: getAttribute_jmx
   Arguments: object name (type ObjectName), attribute (String)
   Description: Returns value of "attribute" for the MBean described by
   "object name."
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."
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."
WASX7291I: Method: setAttributes_jmx
   Arguments: object name (type ObjectName),
   attributes (type AttributeList)
   Description: Sets attributes in the MBean described by
   "object name." The attribute names and values are contained in the
   "attributes" argument.
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."
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.
WASX7294I: Method: extract
   Arguments: documentURI, filename
   Description: Extracts a configuration repository document that
   is described by the "documentURI" and places it in the file named
   by the "filename". The "documentURI" describes a document that
   must exist in the repository and is relative to the root of
   repository such as "cells/MyCell/myfile.xml", and the "filename"
   must be a valid local file name to extract the document to such as
   "c:/myfile". This method returns an opaque "digest" object which
   should be used to check the file back in the repository using the
   checkin command.
WASX7295I: Method: checkin
   Arguments: documentURI, filename, digest
   Description: Checks a file named by "filename" into the configuration
   repository that is described by the "documentURI". The "documentURI"
   is relative to the root of the configuration repository such as
   "cells/MyCell/nodes/MyNode/serverindex.xml" which must exist
   in the repository, and the "filename" is the name of the source
   file to check in and it must be a valid local file name such as
   "c:/myfile". The "digest" parameter should be the opaque object
   which is returned by a prior extract command of AdminConfig object.
WASX7296E: The name specified is not the name of a file "{0}"
WASX7297E: Cannot write to file "{0}"
WASX7298E: Cannot invoke "{0}" command because this client is not connected to a Network Deployment Manager server.
WASX7299E: "-wsadmin_classpath" option must be followed by a classpath.
WASX7300I: Method: getValidationSeverityResult
   Arguments: severity
   Description: Returns the number of validation messages with the given
   severity from the most recent validation.
WASX7301E: Cannot get the task info for {0} using file {1}. Ensure that this file exists and is readable.
WASX7302E: Cannot get tasks using file {0}. Ensure that this file exists and is readable.
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "{0}"
WASX7304I: Method: getNode
   Arguments: none
   Description: Returns the node to which the scripting process is
   connected.
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.
WASX7306E: Cannot complete testConnection function because the node for Data Source "{0}" cannot be determined.
WASX7307E: Cannot create object of type "{0}" on a Network Deployment Manager node.
WASX7309W: No "save" was performed before the script "{0}" exited; configuration changes will not be saved.
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.
WASX7313I: Generating Dynamic Scripting Objects. Please Wait...
WASX7314I: Finished generating Dynamic Scripting Objects.
WASX7315W: Failed to generated dynamic scripting object: "{0}"
WASX7316W: Error creating Dynamic Scripting object. These objects will not be available -- "{0}". Please use the generic AdminControl facilities.
WASX7318E: Received exception while declaring {0}; exception information: {1}
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.
WASX7320E: Server "{0}" is already running on node "{1}" and cannot be started.
WASX7321I: Method: createDocument
   Arguments: documentURI, filename
   Description: Creates a new document in the configuration repository.
   The "documentURI" is the name of the document to be created in the
   repository which is relative to the root of the configuration
   repository such as "cells/MyCell/myfile.xml", and the "filename"
   is the name of the file to create which must be a valid local file
   name such as "c:/myfile".
WASX7322I: Method: deleteDocument
   Arguments: documentURI
   Description: Deletes a document from the configuration repository.
   The "documentURI" is the name of the document to be deleted from the
   repository which is relative to the root of configuration repository
   such as "cells/MyCell/myfile.xml".
WASX7323E: Cannot create directory "{0}"
WASX7324E: Cannot copy directory "{0}" to directory "{1}"
WASX7326I: Loaded properties file "{0}"
WASX7327I: Contents of was.policy file:
{0}
WASX7328E: A single attribute name must be specified for showAttribute; received: "{0}"
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.
WASX7330I: "cluster" option; specifies the cluster name for AdminApp install functions.
WASX7331I: Unexpected exception received when querying for changes in this session:    {0}
WASX7332I: Method: getCell
   Arguments: none
   Description: Returns the cell to which the scripting process is
   connected.
WASX7333I: This option is deprecated. Use the "update" option instead.
WASX7334I: This option is deprecated. Use the "update.ignore.old" option instead.
WASX7335I: This option is deprecated. Use the "update.ignore.new" option instead.
WASX7336E: The "{0}" option is required if "{1}" is specified.
WASX7337I: Invoked stop for server "{0}" on node "{1}"; Waiting for stop completion.
WASX7338E: Caught exception stopping server "{0}." Exception information:
{1}
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."
WASX7340I: Method: existsDocument
   Arguments: documentURI
   Description: Tests to see if a document exists in the configuration
   repository. The "documentURI" is the document to be tested which is
   relative to the root of the configuration repository such as
   "cells/MyCell/myfile.xml". Returns a true value if the document
   exists; false otherwise.
WASX7341W: No "save" was performed before the interactive scripting session exited; configuration changes will not be saved.
WASX7342I: Method: installResourceAdapter
   Arguments: rar file name, node, options
   Description: Installs a J2C resource adapter with the rar file
   specified by "rar file name" using the options specified by "options"
   in the specified "node".
   The rar file name is the fully qualified file name resided in the
   specified node.
   The valid options are "rar.name", "rar.desc", "rar.archivePath",
   "rar.classpath", "rar.nativePath", "rar.threadPoolAlias",
   "rar.propertiesSet, "isolatedClassLoader", "enabledHASupport", and
   "HACapability. All options are optional.
   The "rar.name" option is the name for the J2CResourceAdapter.
   If it is not specified, then the display name in the rar"s deployment
   descriptor is used. If that is not specified, then the rar file name
   is used.
   The "rar.desc" option is a description of the J2CResourceAdapter.
   The "rar.archivePath" is the name of the path where the file is
   to be extracted. If this is not specified, then the archive will be
   extracted to $CONNECTOR_INSTALL_ROOT directory.
   The "rar.classpath" is the additional class path.
   The "rar.threadPoolAlias" is the alias of the thread pool.
   The "rar.propertiesSet" is the property set of the J2CResourceAdapter.
   The "rar.isolatedClassLoader is the option to use isolated classloader.
   If it is specified, it indicated that the J2CResourceAdapter uses the
   isolated classloader. The default value is "false".
   The "rar.enableHASupport is the option to enable HA support.
   The default value is "false".
   The "rar.HACapability specifies the type of HA support. The choices are
   the "endpoint", "instance" and "no".
WASX7343E: The specified node name "{0}" is not the same as the node "{1}" this client is currently connected to.",
WASX7344E: Node name is required when the client is connected to process type "{0}".
WASX7345E: Cannot find node "{0}" in configuration data.
WASX7346E: Cannot locate NodeAgent object for server "{0}" of process type {1}.
WASX7347E: An argument is required for option "{0}."
WASX7348I: Each element of the {0} task consists of the following {1} fields: {2}
Of these fields, the following are required and used as keys to locate the rows in the task: {3}
and the following may be assigned new values: {4}

The current contents of the task after running default bindings are:
{5}
WASX7349I: Possible value for resource authorization is container or per connection factory
WASX7350E: This field requires container or per connection factory as the value. Please try again.
WASX7351I: The parents command cannot be used to find the parents of type "{0}"
WASX7352E: Wrong number of arguments for "{0}" command. Help information follows:
{1}
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.
WASX7354E: The attribute "{0}" is an embedded object of type "{1}"; an invalid value was supplied.
WASX7355E: The attribute "{0}" is of type "{1}"; an invalid value was supplied.
WASX7356E: Unrecognized argument: {0}. The specified argument is not a valid node name or wait time when connected to {1}.
WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
WASX7358E: Invalid option specified: {0}
WASX7359E: Incorrect value specified for reloadInterval option: {0}. reloadInterval option requires an integer value.
WASX7360I: Method: required
   Arguments: type
   Description: Displays the required attributes contained by an object
   of type "type".
WASX7361I: No required attribute found for type "{0}".
WASX7362I: Method: message
   Arguments: Message Id
   Description: Display information for given message id.
WASX7363E: No help available for message id {0}.
WASX7364E: Error getting help information for message id {0}.
WASX7365I: Explanation: {0}
User action: {1}
WASX7367I: "update.ignore.old" option; this option specifies that when an application is updated, the bindings from the old version are ignored during the reinstall operation. This option only has meaning if the "update" option is specified; otherwise it is ignored.
WASX7368I: "update.ignore.new" option; this option specifies that when an application is updated, the bindings from the new version are ignored during the reinstall operation. This option only has meaning if the "update" option is specified; otherwise it is ignored.
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."
WASX7370E: Error registering bean {0} provided in extension: {1}
WASX7371E: Error locating the class for {0} provided in extension: {1}
WASX7372E: Error instantiating the class for {0} provided in extension: {1}
WASX7373W: Duplicate implementation class entry, {0}, found in {1} at line {2}.
WASX7374W: Missing element type {0} in {1} at line {2}. Ignoring this {3} element type.
WASX7375E: Element type {0} is already defined.
WASX7376E: Invalid element end-tag: {0}
WASX7377W: <typeClass> element with the same class name, {0}, found in {1} at line {2}.
WASX7378I: "reloadEnabled" option; this option specifies to enable class reloading; this is the default setting.
WASX7379E: Language "{0}" is not supported. Supported languages are jacl and jython.
WASX7380I: Invalid file name specified: {0}. File name must end with the following file extensions: ear, jar, rar, or war
WASX7381I: "nodeployws" option; specifies to not deploy WebService during install; this is the default setting.
WASX7382I: "deployews.classpath" option; specifies extra classpath to be used to deploy WebServices
WASX7383I: "deployews.jardirs" option; specifies extra extension directories to be used to deploy WebServices
WASX7384I: "deployws" option; specifies to deploy WebServices during install; the default is "nodeployws"
WASX7385I: Method: publishWSDL
   Arguments: application name, filename, soapAddressPrefixes
   Description: Publish WSDL files for the application specified
   to the file specified by "filename" using the soap address prefixes.
   The soapAddressPrefixes is a compound parameter that defines url
   endpoint information for the soap addresses in each module.
   This information is used to customize the SOAP addresses in
   the published WSDL.
   Method: publishWSDL
   Arguments: application name, filename
   Description: Publish WSDL files for the application specified
   to the file specified by "filename".
WASX7386E: {0} in {1} at line {2} column {3}
{4}
WASX7387E: Operation not supported - testConnection command in AdminControl scripting object is not supported when connected to a 5.0 server.
WASX7388E: Connection to provided datasource failed.
WASX7389E: Operation not supported - getPropertiesForDataSource command is not supported.
WASX7390E: Operation not supported - testConnection command with config id and properties arguments is not supported. Use testConnection command with config id argument only.
WASX7391W: Your application contains policy permissions that are in the filter policy. These permissions are security sensitive and can compromise the integrity of the system. Do you want to continue with the application deployment process?
WASX7392W: Your application contains policy permissions that are in the filter policy. These permissions are security sensitive and can compromise the integrity of the system. Continuing with the application deployment process ...
WASX7393I: "allowPermInFilterPolicy" option; specifies to continue with the application deployment process even when the application contains policy permissions that are in the filter policy
WASX7394I: "noallowPermInFilterPolicy" option; specifies to not continue with the application deployment process when the application contains policy permission that are in the filter policy. This is the default setting.
WASX7395E: The specified values for -lang and -internalLang options are not the same. Use one or the other option but not both.
WASX7396I: Method: uninstallResourceAdapter
   Arguments: config id
   Description: Uninstall a J2C resource adapter by the "config id"
   Method: uninstallResourceAdapter
   Arguments: config id, option list
   Description: Uninstall a J2C resource adapter by the "config id" using options in "option list".
   Option list is optional. The valid option is "force".
   The "force" option will force the uninstall of resource adapter
   without checking whether the resource adapter is still being
   used by any application.
   If this option is not specified and the specified resource adapter is still in use,
   the resource adapter will not be uninstalled.
WASX7397I: The following J2CResourceAdapter objects are removed: {0}
WASX7398E: List of applications still using the specified Resource Adapter:
WASX7399E: List of J2CResourceAdapter objects still using the specified Resource Adapter:
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.
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.
WASX7402W: "Use FIPS" is enabled, but the SSL provider is not IBMJSSEFIPS. FIPS approved cryptographic algorithms may not be used.
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 WebSphere Application Server products.
WASX7404I: Method: view
   Arguments: name, taskname option
   Description: View the task specified by the "taskname option"
   parameter for the application or module specified by the "name"
   parameter. Use "-tasknames" as the option to get a list of valid
   task names for the application. Otherwise, specify one or more
   task names as the option.
   Method: view
   Arguments: name
   Description: View the application or module specified by
   the "name" parameter.
WASX7405E: No viewable tasks are available for application "{0}"
WASX7406E: Cannot find task name {0} in the application {1}
WASX7407I: The specified node configuration is successfully removed from the workspace. If you decide to commit this change to the master repository, your configuration may become invalid. To revert this operation and remove any unsaved configuration changes in the workspace, perform "AdminConfig reset" command.
WASX7408I: The specified node configuration is successfully removed from the workspace. If you decide to commit this change to the master cell repository, you may need to perform manual steps to complete the removal steps include restoring the original application server cell configuration as the active configuration and updating the cell value in setupCmdLine.bat. If there are still running application servers for this node, you have to manually stop those servers.
WASX7409I: Method: deleteUserAndGroupEntries
   Arguments: application name
   Description: Deletes all the user/group information for all the roles
   and RunAs roles for a given application.
   Method: deleteUserAndGroupEntries
   Arguments: application name
   Description: Deletes all the user/group information for all the roles
   and RunAs roles for a given application.
WASX7410I: Method: updateAccessIDs
   Arguments: application name, boolean:bAll
   Description: Updates the application binding file for an installed
   application with access IDs for all the users and groups. Specifying
   true for bAll updates all the users/groups even if there are access
   IDs already present in the bindings.
   Method: updateAccessIDs
   Arguments: application name, boolean:bApp
   Description: Updates the application binding file for an installed
   application with access IDs for all the users and groups.
WASX7411W: Ignoring the following provided option: {0}
WASX7412E: Invalid content type value: {0}
WASX7413E: Invalid operation value: {0}
WASX7414W: Ignoring {0} option when {1} content type is specified.
WASX7415W: Ignoring {0} option when {1} operation is specified.
WASX7416E: {0} option is required when {1} content type is specified.
WASX7417E: {0} option is required when {1} content type and {2} operation are specified.
WASX7418E: Application update for {0} failed: see previous messages for details.
WASX7419I: Method: update
   Arguments: application name, content type, options
   Description: updates the application specified by "application
   name" using update type specified by "content type" with
   options specified by "options".
   Valid update content type values are
      app - entire application
      file - a single file
      modulefile - a module
      partialapp - partial application
   All valid options for install command are valid for the
   update command. Additional update options are
      -operation - operation to be performed. Valid values are
         add - adds new contents
         addupdate - performs add or updates based on
            existence of contents in the application
         delete - deletes contents
         update - update existing contents
       This option is required if content type is file
       and modulefile. This option must have "update" as
       the value if content type is app. This option is
       ignored if content type is partialapp.
      -contents - file containing the contents to be added or
       updated. The specified file has to be local to the
       scripting client. This option is required except for
       delete operation.
      -contenturi - URI of the file to be added, updated, or
       removed from the application. This option is required if
       content type is file or modulefile. This option
       is ignored if content type is app or partialapp.
   The AdminApp "options" command may be used to get a list of all
   possible options for a given ear file. The AdminApp "help" command
   may be used to get more information about each particular option.
WASX7420I: Method: updateInteractive
   Arguments: application name, content type, options
   Description: updates the application specified by "application
   name" using update type specified by "content type" with
   options specified by "options".\ If content type is app or
   file, user is prompted for information about each relevant task.
   Valid update content type values are
      app - entire application
      file - a single file
      modulefile - a module
      partialapp - partial application
   All valid options for install command are valid for the
   update command. Additional update options are
      -operation - operation to be performed. Valid values are
         add - adds new contents
         addupdate - performs add or updates based on
            existence of contents in the application
         delete - deletes contents
         update - update existing contents
       This option is required if content type is file
       or modulefile. This option must have "update" as
       the value if content type is app. This option is
       ignored if content type is partialapp.
      -contents - file containing the contents to be added or
       updated. The specified file has to be local to the
       scripting client. This option is required except for
       delete operation.
      -contenturi - URI of the file to be added, updated, or
       removed from the application. This option is required if
       content type is file or modulefile. This option
       is ignored if content type is app or partialapp.
   The AdminApp "options" command may be used to get a list of all
   possible options for a given ear file. The AdminApp "help" command
   may be used to get more information about each particular option.
WASX7421I: "contents" option; this option is used in the update or updateInteractive command to specify the file containing the contents to be updated. Depending on the content type, the file can be a module, a partial zip, an application file, or a single file. The path to the file has to be local to the scripting client. This option is required except when delete operation is specified.
WASX7422I: "contenturi" option: this option is used in the update or updateInteractive command to specify the URI of the file to be added, updated, or removed from the application. This option is required if content type is file or modulefile. This option is ignored for other content type values.
WASX7423I: "operation" option: this option is used in the update or updateInteractive command to specify the operation to be performed. Valid values are

   add - adds new content

   addupdate - performs add or update based on existence

    of contents in the application

   delete - deletes contents

   update - update existing contents

This option is required if content type is file or modulefile.

This option must have "update" as the value if content type

is app. This option is ignored for other content type values.
WASX7424I: "createMBeansForResources" option: this option specifies that MBeans are created for all the resources such as servlets, jsps, EJBs, defined in an application when the application is started on a deployment target; the default is nocreateMBeansForResources.
WASX7425I: "nocreateMBeansForResources" option: this option specifies that MBeans are not created for all the resources such as servlets, jsps, EJBs, defined in an application when the application is started on a deployment target; this is the default setting.
WASX7426I: "noreloadEnabled" option: this option specifies not to enable class reloading; the default is reloadEnabled.
WASX7427I: "reloadInterval" option: this option specifies the time period (in seconds) in which the application"s filesystem will be scanned for updated files; the default setting is 3 seconds.
WASX7428W: contextroot option will be ignored if module exists.
WASX7429I: Method: searchJNDIReferences
   Arguments: node or nodes config id, options
   Description: List all applications that refer to the specified
   JNDIName option on the specified node or nodes.
   The valid options are -JNDIName which is a required option
   and -verbose which is an optional option that does not take any value.
   The JNDIName option takes a value of a JNDI name.
   The verbose option will show more information.
WASX7430W: This operation may take longer depending on how many applications installed on your system.
WASX7431I: "installed.ear.destination" option; specifies the directory into which the application binaries should be placed.
WASX7432I: "validateinstall" option; specifies desired level of application install validation. Valid option values are:

   off: no application deployment validation

   warn: perform application deployment validation and

      continue with the application deployment process

      even when there are reported warning or error

      messages.

   fail: perform application deployment validation and

      not to continue with the application deployment

      process when there are reported warning or

      error messages.

The default is off.
WASX7433I: "custom" option; specifies a name-value pair using the format name=value. Use this option to pass option to application deployment extension. Consult application deployment extension documentation for available custom options.
WASX7434W: Found the following deprecated option: {0}
WASX7435W: Value {0} is converted to a boolean value of false.
WASX7436W: At least one default binding option has been specified, but usedefaultbindings option has not been specified. The default binding option(s) will be ignored.
WASX7437I: "processEmbeddedConfig" option; Use this option to process the embedded configration data that is included in the application. This setting is the default.
WASX7438I: "noprocessEmbeddedConfig" option; Use this option to ignore the embedded configuration data that is included in the application. The default setting is "processEmbeddedConfig".
WASX7439I: Method: isAppReady
   Arguments: application name
   Description: Tests to see if the specified application has been
   distributed and is ready to be run. Returns true if the application
   is ready; false otherwise.
   Arguments: application name, ignoreUnknownState
   Description: Tests to see if the specified application has been
   distributed and is ready to be run. Valid values for ignoreUnknownState
   argument are true or false. If true is specified as its value, then
   any node or server with unknown state is not included in the final
   ready return. Returns true if the application is ready; false
   otherwise.
WASX7440E: "{0}" method is not supported when connecting to local mode.
WASX7441E: "{0}" action not supported when process type of server being stopped is "{1}"
WASX7442E: "{0}" action not supported when node name is not provided.
WASX7443I: Server "{0}" on node "{1}" is not being monitored. Please verify that the server has stopped before continuing.
WASX7444E: Invalid parameter value "{0}" for parameter "{1}" on command "{2}"
WASX7445E: "-jobid" option must be followed by a jobID string.
WASX7446E: "-tracefile" option must be followed by a file path.
WASX7447E: "-appendtrace" option must be followed by a "true" or "false".
WASX7448E: The trace file cannot be written to location {0}. Please specify a different location with -tracefile option.
WASX7449I: "target" option; specifies the target for AdminApp install functions.

Example of target option value is WebSphere:cell=mycell,node=mynode,server=myserver
WASX7450I: "buildVersion" option; specifies the build version of an application ear file.
WASX7451I: "allowDispatchRemoteInclude" option; Enables an enterprise application to dispatch

includes to resources across web modules in different JVMs in a managed node environment via the standard RequestDispatcher mechanism.
WASX7452I: "allowServiceRemoteInclude" option; Enables an enterprise application to service

an include request from an enterprise application with -allowDispatchRemoteInclude set to true.
WASX7453I: "filepermission" option; Allow user to set appropriate file permissions on application files in the install destination directory.


File permissions specified at the application level must be a subset of the node level file permission which defines the most lenient file permission that can be specified, otherwise node level permission value is used to set file permissions in install destination.


The default is ".*\.dll=755#.*\.so=755#.*\.a=755#.*\.sl=755"

The filename pattern is a regular expression.
WASX7454I: "noallowDispatchRemoteInclude" option; Disables an enterprise application to dispatch

includes to resources across web modules in different JVMs in a managed node environment via the standard RequestDispatcher mechanism.
WASX7455I: "noallowServiceRemoteInclude" option; Disables an enterprise application to service

an include request from an enterprise application with -allowDispatchRemoteInclude set to true.
WASX7456I: Method: queryMBeans
   Arguments: object name
   Description: Returns a Set containing ObjectInstances object
   that match the input object name.
   Method: queryMBeans
   Arguments: object name (type ObjectName), query (type QueryExp)
   Description: Returns a Set containing ObjectInstances object
   that match the input object name and query.
WASX7457I: Method: getObjectInstance
   Arguments: object name
   Description: Returns the ObjectInstance object that match the input
   object name.
WASX7458E: Invalid file permission string "{0}"
WASX7459E: The configuration service is not available. Target node"s nodeagent may not be running "{0}."
WASX7460I: Method: getDeployStatus
   Arguments: application name
   Description: Returns a string which represents the deployment status
   of the application. The status of each node, to which the application is
   deployed, is concatenated by the "+" character.
WASX7461I: Method: AdminTask
   Arguments: none
   Description: Display general help information for the
   AdminTask object provided by wsadmin.
WASX7462I: Method: wsadmin
   Arguments: none
   Description: Display general help information for the
   wsadmin script launcher.
WASX7463I: "deployejb.dbaccesstype" option; specifies the database access type for EJBDeploy
WASX7464I: "deployejb.sqljclasspath" option; specifies the SQLJ classpath for EJBDeploy
WASX7465E: stopServer action not supported when server type is "{0}"
WASX7466I: Method: getObjectType
   Arguments: config id
   Description: Displays the configuration object type by "config id."
WASX7467I: Connection to provided datasource on node {0} process {1} was successful.
WASX7468E: Connection to provided datasource on node {0} process {1} failed.
WASX7469E: One or more attributes must be specified for resetAttributes; received: {0}
WASX7470E: One or more attributes name must be specified for unsetAttributes; received: {0}
WASX7471I: Method: unsetAttributes
   Arguments: config id, attributes
   Description: Use the unsetAttributes command to reset the specific attributes for a
   configuration object to the default values.
WASX7472I: Method: resetAttributes
   Arguments: config id, attributes
   Description: Use the resetAttributes command to reset the specific attributes for a
   configuration object.
WASX7473I: "exportToLocal" option; specifies the option for AdminApp export function to export application to the client local machine.
WASX7474I: Method: exportFile
   Arguments: application name, uri, filename
   Description: This command exports the contents of a single file
   which is specified by the uri argument, from the application,
   which is specified by the application name argument, to the file,
   which is specified by the file argument.
   Specify the uri argument within the context of an application.
   For example: META-INF/application.xml. For files within a module,
   start the uri with a module uri. For example: myapp.war/WEB-INF/web.xml.
WASX7475E: The {0} output file already exists. Specify another output file name.
WASX7476I: "useAutoLink" option; allow the EJB reference targets to resolve automatically.


The application must contain an EJB 3.0 module and all modules must share one common target to enable the autolink support.
WASX7477I: "blaname" option; use this option to specify the name of the business level application.
WASX7478I: "nouseAutoLink" option; the EJB reference targets do not resolve automatically. The default setting is "nouseAutoLink"
WASX7479I: "asyncRequestDispatchType" option; specifies the asynchronous request dispatch type for web container for each application. The default setting is "DISABLED"
WASX7480E: "{0}" found instead of expected "[". {1}
WASX7481I: "deployejb.complianceLevel" option; specifies the JDK level for compiler compliance for EJBDeploy; default is 1.4.
WASX7482W: The duplicate properties are specified. The latter property value will be set.
WASX7483E: Application edit of {0} failed: see previous messages for details.
WASX7484I: "validateSchema" option; Use this option to specify that the schema is to be validated. The default is "novalidateSchema"
WASX7485I: "validateSchema" option; Use this option to specify that the schema is not to be validated. This is the default.
WASX7486W: This -clientMode option will be ignored because the -enableClientModule option is not specified.
WASX7487E: Failed to import script libraries modules: {0}; {1}
WASX7488I: Method: rename
   Arguments: application name, new application name
   Description: Renames the application specified by "application name"
   to the name specified by "new application name". In a WebSphere
   Virtual Enterprise environment, composite names are supported to
   allow specification of application name and edition. A composite
   name has the form, <name>-edition<edition>.
WASX7489E: "-extdir" option must be followed by a path to set to ws.ext.dirs.
WASX8001I: The AdminTask object enables the execution of available admin
   commands. AdminTask commands operate in two modes:
   the default mode is one which AdminTask communicates with the WebSphere
   server to accomplish its task. A local mode is also available, in which
   no server communication takes place. The local mode of operation is
   invoked by bringing up the scripting client using the command line
   "-conntype NONE" option or setting the
   "com.ibm.ws.scripting.connectiontype=NONE" property in
   wsadmin.properties file.



The number of admin commands varies and depends on your WebSphere

install. Use the following help commands to obtain a list of supported

commands and their parameters:



help -commands         Lists all the admin commands

help -commands <pattern>   Lists admin commands matching with wildcard
            "pattern"

help -commandGroups      Lists all the admin command groups

help -commandGroups <pattern>   Lists admin command groups matching with
            wildcard "pattern"

help commandName      Displays detailed information for the
            specified command

help commandName stepName   Displays detailed information for the specified
            step belonging to the specified command

help commandGroupName      Displays detailed information for the specified
            command group



There are various flavors to invoke an admin command. They are



commandName         Invokes an admin command that does not require
            any argument.



commandName targetObject   Invokes an admin command with the specified
            target object string, for example, the
            configuration object name of a resource
            adapter. The expected target object varies
            with the admin command invoked. Use help
            command to get information on the target
            object of an admin command.



commandName options      Invokes an admin command with the specified
            option strings. This invocation syntax is
            used to invoke an admin command that does
            not require a target object. It is also
            used to enter interactive mode if
            "-interactive" mode is included in the
            options string.



commandName targetObject options   Invokes an admin command with the
               specified target object and options
               strings. If "-interactive" is included
               in the options string, then interactive
               mode is entered. The target object and
               options strings vary depending on the
               admin command invoked. Use help command
               to get information on the target object
               and options.
WASX8002E: Invalid Command name: {0}
WASX8003E: Invalid help arguments: {0}
WASX8004I: Available admin commands:

{0}
WASX8005I: Available admin command groups:

{0}
WASX8006I: Detailed help for command: {0}



Description: {1}



{2}Target object: {3}



Arguments:

{4}

Steps:

{5}
WASX8007I: Detailed help for command group: {0}



Description: {1}



Commands:

{2}
WASX8008E: Command {0} does not contain any step.
WASX8009E: Invalid parameter: {0}
WASX8010E: Invalid scripting language: {0}
WASX8011W: AdminTask object is not available.
WASX8012E: Step {0} is not enabled.
WASX8013I: Detailed help for step: {0}



Description: {1}



Collection: {2}



Arguments:

{3}
WASX8014E: Step {0} is not a table.
WASX8015E: Invalid option value for step {0}: {1}
WASX8016E: Command provider error: null object type
WASX8017E: Command provider error: step {0} does not contain any key
WASX8018E: Cannot find a match for option value {0} for step {1}
WASX8019E: Incorrect number of key fields specified for step {0}: {1}
WASX8020E: An argument is required for parameter "{0}."
WASX8021E: The wsadmin with version "{0}" connected to an incompatible server or deployment manager with node version "{1}", which is not supported. "
WASX8022E: Incompatible node version; exception information: {0}
WASX8023E: The upload file "{0}" does not exist for installation.
WASX8024I: Cannot find the command or command group pattern: {0}
WASX8025W: AdminConfig object is not available.