[AIX HP-UX Linux Solaris Windows]This topic applies only on the IBM i operating system.

Command line tool problems

This article provides troubleshooting support for a variety of problems relating to using command line tools.

What kind of problem are you having?

The addNode.sh script or BBOWADDN job fails during node federation. [AIX Solaris HP-UX Linux Windows]

This error occurs only if the BBODCFGW job is run on the deployment manager during customization. The BBODCFGW adds an unmanaged node with a Web server to the Deployment Manager, causing the Node Federation from a base server to fail.

To fix this problem, do not configure the BBODCFGW job on the Deployment manager until all nodes are federated into the cell. Also, do not add any unmanaged nodes into the cell until all managed Node Federations are complete. A Web server can be configured on a managed node without any problems.

Just-in-time (JIT) compiler is disabled when you start the application server with DEBUG enabled on a Red Hat Linux machine [AIX Solaris HP-UX Linux Windows]

The just-in-time (JIT) compiler is disabled when you start the application server with Software Developer Kit (SDK) DEBUG enabled on a Red Hat Linux® machine, even though JIT is set to enabled. To verify this setting, check the SystemOut.log or the startServer.log file.

Use the administrative console to remove the following DEBUG options of the Java™ process definition. -Xdebug -Xnoagent

For more information, see the V6.0 Information Center Release Notes page.

The startServer.sh or stopServer.sh commands fail to start or stop the server when the server definition is part of the configuration repository. [AIX Solaris HP-UX Linux Windows]

This problem occurs when the startServer.sh or stopServer.sh commands are trying to start or stop non Java™ process. To solve this problem, use the -nowait option to start or stop the server, for example:
startServer.sh webserver1 -nowait
stopServer.sh webserver1 -nowait

With Windows service, there is no indication when a server is already started. [Windows]

When attempting to start an already-started server from the command line, there is no indication that the server is already started and running. When running startManager.bat on Windows® the following output is displayed before the command returns:

ADMU7701I: Because dmgr is registered to run as a Windows Service, the request to start this server will be completed by starting the associated Windows Service.

When running startServer.bat, the following output is displayed before the command returns:

ADMU7701I: Because server1 is registered to run as a Windows Service, the request to start this server will be completed by starting the associated Windows Service.

When running WASService.exe, the following output is displayed before the command returns:

Starting Service: service name

To check if the server is started or if the service is running, use the serverStatus server name command or the WASService -status service name command.

[Updated in April 2013]

Using one or more % characters as part of the value for a parameter [Windows]

The % character is a special character that is used by the Microsoft Windows operating systems. If you are running on a Microsoft Windows operating system, and you are:
  • Invoking a command or .bat file, such as stopServer.bat from the profile_root directory, and the command or .bat file contains a call to a .bat file in the installation_root directory and
  • Using one or more % characters as part of the value for a parameter

You must use two % characters (%%) for each % character contained in the parameter value to prevent the % characters that are part of the parameter value from being consumed by the operating system.

For example, if you want to use was%admin as the value of the -password parameter, you must specify the following command:

wsadmin.bat -username wsadmin -password was%%admin

instead of:

wsadmin.bat -username wsadmin -password was%admin

[Updated in April 2013]
apr2013

Server templates unavailable after upgrading deployment manager version

If you upgrade the deployment manager from V6.0.1 to V6.0.2, the server templates that are needed to create V5 servers are not available. This does not apply if you upgrade the deployment manager directly from V5.0, or V5.1, to V6.0.2.

Run the following command from the bin directory of the deployment manager profile to add the R5 server templates to your deployment manager profile and create V5 servers:

For UNIX systems:
ws_ant.sh -buildfile updateNDProfileTemplates.xml
For Windows systems:
ws_ant.bat -buildfile updateNDProfileTemplates.xml

"ADMU0125E: Change the clock of the new node to be within {0} minutes of the clock of the deployment manager" error message occurs during federation

The workaround for this problem is to adjust the time on the node to be within the recommended amount of the deployment manager. Verify that the time zones are correct and that the times within the time zones are correct. For AIX systems, if the time on the node system is within five minutes of the deployment manager, review the timezone setting in the /etc/environment file. Verify that the TZ= property is set correctly. For example, in the Central Time Zone, it should read TZ=CST6CDT. For more information, see the environment file section of the Files Reference Web site.

The stopServer command fails to stop the server because the system cannot create a connector to an invalid hostname.

If the stopServer command fails to stop the server because the system cannot create a connector to an invalid hostname, you can stop the server using one of following methods:
  • Stop the server process on the operating system (e.g., on Unix based systems issue the kill command).

    Or

  • Open a wsadmin tool connection directly to the connector port of the server and call the stop method for the MBean of the server. This method is recommended because it allows ongoing work to shut down gracefully.
    1. Issue the following command to connect to the server:
      wsadmin -host <host_name>  -port <connector_port>  -conntype [SOAP | RMI ] -user <user ID> -password <password>
    2. Invoke the stop method on the MBean of the server. For example, in Jython you can use:
      serverMBean = AdminControl.completeObjectName("*,type=Server")
         AdminControl.invoke(serverMBean, "stop")

Entering passwords on the command line [Windows] [AIX]

There are operating system differences when specifying environment variables and for directory notation. When using the Windows command line, replace $variable with %variable% for environment variables and replace each forward slash (/) with a backslash (\) in directory paths. If you are using the bash shell on a Windows system, you can use the UNIX conventions.

On Unix type operating systems, it is usually better to always encapsulate string values associated with all tags in double quotes (""). You will also need to escape, using a '\' character, the following characters if they appear in the string values: '!', '\', '"', '`'. This will prevent some command line shells from interpreting specific characters within these values.

Some examples of usage follow:
gsk7capicmd -keydb -create -db "/tmp/key.kdb" -pw "j\!jj" 
Note: When prompted by gsk7capicmd for a value (for example a password) quoting the string and adding the escape characters should not be done because the shell is no longer influencing this input.
[Windows]
stopserver server1 -username fn_wasadmin -password $mypass35%% -trace 
[AIX]
stopserver server1 -username fn_wasadmin -password '$mypass35%' -trace 
Avoid trouble Avoid trouble: [Updated in September 2012] In general, for ws_ant.sh scripts, use single quote for strings containing special characters:
  • For a string containing a single quote or a double quote, use the other character to quote the string. For example, if you specify bin/ws_ant.sh -f ant.xml -Dsystem.property='"a quoted String"', the property is set to "a quoted string". Similarly, if you specify bin/ws_ant.sh -f ant.xml -Dsystem.peoperty="'a quoted string'", the property is set to 'a quoted string'.

    You cannot include both single and double quotes in the same string.

  • For a string containing a back quote, use a single quotes surrounding the string and escape the back quote with backslash. For example, if you specify bin/ws_ant.sh -f ant.xml -Dsystem.property='\`a quoted string\`', the property is set to `a quoted string`.
  • For a string containing a backslash, surround the string with single quotes and escape it with a backslash. For example, if you specify bin/ws_ant.sh -f ant.xml -Dsystem.property='c:\\Program Files\\IBM'. the property is set to c:\Program Files\IBM.
  • For a string containing a dollar sign, surround the string with single quotes and escape it with a backslash. For example, if you specify bin/ws_ant.sh -f ant.xml -Dsystem.property='\$3.99', the property is set to $3.99.
[Updated in September 2012]
sep2012
gotcha

[AIX Solaris HP-UX Linux Windows] If none of these steps fixes your problem, check to see if the problem has been identified and documented by looking at the available online support (hints and tips, technotes, and fixes). If you don't find your problem listed there contact IBM support.




Related tasks
Using command line tools
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jun 11, 2013 8:40:09 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=rtrb_commandprobs
File name: rtrb_commandprobs.html