Consultor Eletrônico

SUMMARY:

This solution applies to SonicMQ Versions 2000.x through 4.0 and discusses a simple and helpful tip for diagnosing problems encountered when you run scripts of commands with the command line Admin tool.

EXPLANATION:

Because the Admin tool is command driven, it allows you to automate complex or repetitive procedures by creating a "script" or text file that contains commands to be executed sequentially by the Admin shell.
A script is executed by invoking the Admin shell and passing the script file as input.

To do this on Windows, the command line is:

admin < myadmincommands.txt

On UNIX, the command line is:

./admin.sh < myadmincommands.txt

When Admin commands are run in this manner rather than entered at the command line, you might not see all error output from each command.

SOLUTION:

To be sure to see the line-by-line error output, start the Admin shell with the property admin.echo=true. You can do this by passing the corresponding parameter (-Dadmin.echo=1) to the JRE, as you would for
any Java property. Thus the command line in admin.bat to start the Admin shell on Windows would begin:

"%SONICMQ_JRE%" %SONICMQ_SSL_CLIENT% -Dadmin.echo=1 -cp...

Similarly, the command line in admin.sh to start the Admin shell on UNIX would begin:

$SONICMQ_JRE $SONICMQ_SSL_CLIENT -Dadmin.echo=1 -classpath...


Reference to Written Documentation:

SonicMQ 2000.x - 3.0 Installation and Administration Guide,
Chapter 4, Command-Line Administration Tool

SonicMQ 3.5 Installation and Administration Guide,
Chapter 5, Admin Tool

SonicMQ 4.0 Configuration and Administration Guide,
Chapter 1, SonicMQ Administration Tools