Tips and tricks - Axonet Software Gmbh

Tips and tricks 

• How to set up a test and debug environment 

• How to use the protocol tester 

• How to find memory leaks 

• How to use the stress test tool 

02/12/2002 Copyright AxoNet Software GmbH Sheet 1

Test and debug environment 

• Prerequisite: 2 PCs running TCP/IP 

• Install the asanetwork network manager on a separate PC (if available) 

else use your developer PC: 

– You need to reboot your machine after set-up is complete. If not already done, 

add the blue copy protection box (dongle). 

– After reboot, login and check the tray bar. There‘s a small asanetwork icon. 

This indicates that the network manager is up and running. If you click on the 

icon, the GUI is displayed. Verify that there were no errors displayed. 

• Install the asanetwork SDK on your developer PC 

• There you find 3 tools (in ...\sdk\tools) 

– Order generator (office32.exe) 

– Universal client (client.exe) 

– Protocol tester (awntest2.exe) 


Verify your set-up 

• Select the „universal client“ from the 

asanetwork SDK program group. 

– Click on the „create service“ button. 

Watch for the connected, logged in 

strings displayed under order and 

result service. 

• Select the „order generator“ from the 

asanetwork SDK program group. 

• The display of the „universal client“ 

should now be filled with orders. 

• If you see orders, your set-up is 

working! 


Order generator (office32.exe) 

• Used for client development, simulates a customer order service together 

with a data storage service 

• creates test orders and extended vehicle data from 2 files: 

– Order.dat 

– Vehicle.dat 

• These files contain raw data as defined in section 6.1.4 and 6.1.5 of the 

asanetwork documentation. You can edit these files if necessary, but be 

very careful! 

• On start-up some orders are already active or finished to test your client 

behaviour. This is by design. After the first query from a client all orders 

are reset to the new state. 

• Received results are saved in the temp directory and displayed using 

notepad. If you double click on a result file (000000??.awn), the viewer 

starts up and displays the XML data. 


Office32.exe usage 

• Usage: simply start the EXE 

• You may add command line 

parameters: 

-s don't show received results in notepad 

-d debug mode, write all received data to 

cust.dat/data.dat 

-i ip address in dot format, like 144.1.13.4 

-l use new DLoc 

• Office32 accepts two user 

commands: 

– D delete finished orders 

– X exit program 


Universal client 

• Used for customer order and client development 

• Accepts all kind of orders 

• Allows user to send a query for all orders 

• Allows user to start, abort, interrupt or finish orders 

– On finish you can set some of the defined result codes 

– On finish sends a result file called client.txt. You can replace this file with any 

file you like, e.g. some XML results 


Client.exe usage 

• Start EXE and click 

„create service“ 

• Click „query“ if 

necessary 

• Select an entry and 

click „start“ then „abort“, 

interrupt or „finish“ 

• Select the result code 

from the dialog. 


Protocol tester (Awntest2.exe) 

• Used for customer order and client development 

• Is used to test services with queries 

• Is used for monitoring of services 

• Has a user defined priority, so you can select what you want to monitor 

– Customer order service: DID TEST_00000, Priority 9 – client side 

– Customer order service: DID TEST_00000, Priority 0 - DMS side 

– Data storage service: DID TEST_*****, Priority 5 

• Displays detailed elements of received data 

• Allows you to save/load all data to/from disk 


Awntest2.exe usage (1) 

• Start program, then select 

either File/New or click on the 

new document button 

• Enter the service you want to 

monitor, either 00000 or ***** 

• If necessary change DiQual 

and DoQual 

• Change the priority 

• If you want to get or 

disable a retransmission 

change the repeat entry 

• Click OK 


Awntest2.exe (2) usage 

• Received data is 

logged in the list box 

and automatically 

displayed in a detailed 

dialog 

• If you double click on 

an entry the detailed 

display shows up 


How to find memory leaks 

• Memory leaks are only a problem with: 

– The C++/Delphi interface if you forget to call delete() on old objects 

– The ActiveX AxAwn interface if you call AddRef()/Release() by yourself (not 

an issue in VB or if you use one of the smart wrapper classes in C++) 

• The C-API doesn't create data structures in dynamic memory, so there is 

no possibility for memory leaks 

• Most common reason: object is not deleted from memory after use 

– On operation O_DELETE you only delete the entry in the list box and not the 

object too 

– You created temporary objects for e.g. sending of files and fail to delete them 

after the operation 


How to find memory leaks (2) 

• The debug window of the C++/AxAwn-Interface keeps track of the object count 

• Start your application, process orders, delete orders and check the debug 

window object count by clicking on „object info“ 


How to use the stress test tool 

• The asanetwork developer CD contains a tool called AwnStress (look in 

the \misc folder on your CD) 

• AwnStress is used to perform 5 steps 

1. Create a huge amount of orders (min. 101) 

2. Reverse the order DIDs on the fly (very critical, but possible) 

3. Reverse back and start all orders 

4. Finish all orders 

5. Delete all orders 

• Test your client application 

– Can you handle all orders? 

– Can you handle reverse DID? 

– Do you free all memory at end? 


How to use the stress test tool (2) 

• Start with a small stress level, each level n 

creates n*n*101 orders 

• If you have a slow network manager or if 

you‘re running all on one machine 

increase the send delay 

• Check „stop after each cycle“ 

• Click „Start“ 

• Watch your application/debug window 

• Maybe you want to clean up the network 

manager data base after finishing the 

tests: 

– Choose Options/Program... and set all time 

values for orders to zero. Restart network 

manager and reset the time to the previous 

value (default 2 months).

Tips and tricks - Axonet Software Gmbh

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?