Your company has acquired an asanetwork license and you should do the implementation. How should you proceed?
Together with the license you received the asanetwork developer SDK. Please install the SDK first, it includes all documentation and tools.
Next install network manager. If you have a separate machine, use it and install network manager there.
Finally set-up a test environment used during development and debugging.
Next you should start reading the base documentation to get some knowledge about essential ideas and concepts of asanetwork. Please have a look at these documents (in the programs/asanetwork sdk folder):
- document 98/10 asanetwork – Basic infos about services, protocols and data models
- document 99/04 Services – More info about services
Now you should study one of the API documents to see how the protocols and data are mapped into an API. This depends on your programming environment:
- document 99/02 – C API or
- document 98/01 – C++/Delphi API or
- read the documentation of the other platform interfaces (like Java, COM or .Net Framework).
Have a look at the examples and play with them to get a better understanding.
Integrating Test Equipment
Read chapter 7 Guidelines for the definition and implementation of services, 7.1 Services provided by testers and 8 User Interface in document 98/10 asanetwork.
Have a look at the requirements for asanetwork certification for test equipment before you start your implementation.
For testing, use OrderSim to generate orders and TestClient to verify proper order locking and handling.
Implement order processing
You have to implement a customer order service. This service is called <you company DId>00000 and should remain connected all the time. This service receives order positions and is used to transmit changes back to the dealer management system (DMS).
If you use one of the client components (like AxClient, AwnClient.Net or VclClient) you save a lot of work (and time) because all order handling is already implemented and tested.
Implement XML result data
The last step is the creation of XML result data. You should read:
- document 99/05 – the manufacturer independent data format for results
- document 98/07 – XML C/C++/Delphi API or use any XML parser of your choice
The XML DTD is in the subdirectory of the asanetwork viewer which was already installed in the first step. To validate your XML results use an commercial XML editor or download an evaluation license of the asanetwork viewer PRO version.
XML results are always transmitted with one of the AWNTXnnnnn services. These services are only created and connected for a transmission.
Adding asanetwork functionality to a DMS
Read chapter 7 Guidelines for the definition and implementation of services and 7.2 Services provided by customer order systems in document 98/10 asanetwork.
Have a look at the requirements for asanetwork certification for dealer management systems before you start your implementation. Also think about your architecture. Are you creating one central interface to asanetwork (recommended!) or do you have multiple interfaces? The latter are a lot more error prone and require special attention.
For testing, use TestClient together with AwnDebug on two or more machines to verify proper order queries, locking and handling.
Implement a customer order service
You have to implement a customer order service. This service is called <you company DId>00000 and should remain connected all the time. This service is used to transmit order positions into asanetwork and receives changes and updates from test equipment. This service must also implement and handle order queries. Pay attention to special state changes like aborting an order.
If you use one of the DMS components (like AxDmsServer or AwnDms.Net) you save a lot of work (and time) because all order handling is already implemented and tested.
Implement a data storage service
You have to implement a data storage service. This service is called <you company DId>***** and should remain connected all the time. This service is used to receive all kinds of test results. Test results should be attached to the corresponding order.
A typical workshop DMS does not parse XML result data. It’s enough to start an external application (like asanetwork Viewer) to display XML results. If you implement DMS functionality for a testing organization you may need to parse and import XML results.