Troubleshooting command-line adapter issues

The command-line adapter displays error messages at startup and when commands run.

About this task

If you receive errors when you start the command-line adapter, follow these steps:
  • Make sure that you are using a JRE at version 1.5 or later.
  • The adapter can do unexpected things when it switches users or servers, so to get a clean start, remove, or rename the config.ini file that the adapter creates. Then, run start.bat or start.sh again with all required arguments.
  • After you start the adapter, click Execution > Adapter Console to make sure that the server can receive messages from the adapter.
  • If you are starting the command-line adapter on a UNIX system, try specifying a different shell in the launch script. For example, change #!/bin/sh to #!/bin/bash in the start.sh script.
The adapter outputs information when it runs a command. If you receive errors when the command-line adapter is running, follow these steps:
  • Check the output from the application-under-test, which is captured and attached to the log file.
  • To add more environment information to the standard out, wrap the command in a .bat or .sh script.
Note: If a network issue causes the command-line adapter to disconnect from the server, do not manually stop the adapter if a test case execution record is in progress. After the test case execution record is completed, the adapter automatically reconnects to the server after the network connection is back and uploads the test case result. If you manually stop and reconnect the adapter, it does not upload the test case result.

What to do next

For more information about the command-line adapter, see https://jazz.net/library/article/809.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki