|
Problem(Abstract) |
Collecting data for problems with the IBM® WebSphere®
Application Server Administrative Scripting Tools component (for example:
Apache Ant tool). Gathering this information before calling IBM support
will help familiarize you with the troubleshooting process and save you
time. |
|
|
|
Resolving the
problem |
Releases of Application Server V5.0 and higher provide the
ability to use the native Apache Ant tool. You can perform various tasks
with this tool, such as installing an enterprise application.
For more information on the tool, search the Information Centers on the
keyword "ANT", or refer to the following links:
If you have already contacted support, continue on to the
component-specific MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
Ant specific MustGather information
- Determine if the problem is in the Ant build script or a wsadmin
issue.
- Enable the debug option.
install_root/bin/ws_ant –help |
|
The preceding command will display the following
debugging parameters to run with the build script:
|
# ./ws_ant -help
ant [options] [target [target2 [target3] ...]]
Options:
-help |
print this message |
-projecthelp |
print project help information |
-version |
print the version information and exit |
-diagnostics |
print information that might be helpful to diagnose or
report problems. |
-quiet, -q |
be extra quiet |
-verbose, -v |
be extra verbose |
-debug |
print debugging information |
-emacs |
produce logging information without
adornments |
-logfile <file> |
use given file for log |
-l <file> |
'' |
-logger <classname> |
the class which is to perform logging |
-listener <classname> |
add an instance of class as a project
listener |
-buildfile <file> |
use given buildfile |
-file <file> |
'' |
-f <file>
|
'' |
-D<property>=<value> |
use value for given property |
-propertyfile <name> |
load all properties from file with -D properties
taking precedence |
-inputhandler <class> |
the class which will handle input requests |
-find <file> |
search for buildfile towards the root of the
filesystem and use it |
|
|
- Gather the following items so that the Support Team can assist in
resolving your reported issue.
- Simplify your ANT build script.
- Run the script with the following command:
install_root/bin/ws_ant –f
<build_file> -debug >
ws_ant.out |
|
- Gather your script and the ws_ant.out file.
- To determine if it is a wsadmin issue (a call being made from ANT):
- Enable the wsadmin trace by editing the wsadmin.properties
file. Locate the following section and uncomment the trace string (remove
the #).
#-------------------------------------------------
# The traceString property governs the trace in
# effect for the scripting client process.
# The default is no tracing.
#-------------------------------------------------
#com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled |
|
- For Network Deployment, if the wsadmin connects
with dmgr SOAP, the file is located in the following directory:
ND_install_root/properties/wsadmin.properties. |
|
- For Base, if the wsadmin connects to Base, the file
is located in the following directory:
Base_install_root/properties/wsadmin.properties |
|
- Run the collector tool on each Application Server node. For
instructions on how to run the Collector tool, refer to the following:
- Follow instructions to send
diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to the Administrative Scripting Tools component, search the WebSphere
Application Server support site. |
|
|
|