Kbase 16142: Testing WebSpeed(1.0&2.x) configuration without a Web server
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  6/7/1998 |
|
Testing WebSpeed(1.0&2.x) configuration without a Web server
There is a sample test that is included with WebSpeed that allows you
to test your WebSpeed configuration without using a Browser or a Web
Server. This test makes a pseudo web request to the cgiip and
WebSpeed Transaction Broker.
On UNIX, there is a script called wstest that is installed in the
$DLC/bin directory. On NT, there is a batch file called wstest.bat.
Usage: wstest <broker-host> <broker-port-number>
If the test is successful, you will get a message back that states
"The WebSpeed Dispatcher is running."
If the test is unsuccessful, you will get a message in HTML format
that states "WebSpeed error from messenger process Failure connecting
to WebSpeed Transaction Broker! Verify the Broker has been started.
Verify the specified port number is the same as the "Port" option in
the WebSpeed Transaction Broker configuration file. Error: -63
You can also test the messenger file with this syntax
wstest <messenger-filename>
If the test is successful, you will get a message back that states
"The WebSpeed Dispatcher is running."
If the test is unsuccessful, you will get a message in HTML format
that states "WebSpeed error from messenger process Disconnecting with
no header! Connection with instance abnormally terminated."
Note: The error number -63 is an error returned from the PROGRESS octo
networking layer. It means FAILED_CONNECTION_ATTEMPT. For more info
about octo errors, see also PROGRESS Technical Support Knowledgebase
entry 16147.
18-Sep-96
Progress Software Technical Support Note # 16142