Professional Documents
Culture Documents
Validator
Installation and User
Manual
This manual decribes the installation, the handling and the error analysis for validation of the
DMS integration with ISPA Next ISPA Mobile.
BMW Group
Page 2
of
24
List of contents
1.
1.1
1.2
1.3
Introduction
Purpose of This Document
Target Group for this Document
Structure of This Document
4
4
4
4
2.
2.1
2.2
2.3
2.4
5
5
5
5
5
3.
3.1
3.2
3.3
3.4
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.5
3.6
3.7
Usage
Prerequisites
Starting the ISPA Next / ISPA Mobile Validator
DMS Configuration
Test Case Execution
Explanation of the Test Case UI
Executing the First Test Case
Executing DMS Test Cases
Executing Connectivity Test Cases
Dealing with Failed Test Cases
Log File Download
Create and download Test Report
Pre-Configuring the ISPA Next / ISPA Mobile Validator
6
6
6
7
10
10
11
12
13
15
16
17
19
4.
4.1
4.1.1
4.1.2
4.1.3
4.2
4.3
20
20
20
20
21
22
24
5.
Support
25
Release 1503
Copyright BMW AG
BMW Group
Page 3
of
24
List of figures
Figure 1: ISPA Next / ISPA Mobile Validator startup screen...........................................................6
Figure 2: DMS configuration screen DMS and Dealer Data...........................................................7
Figure 3: DMS connection error.................................................................................................... 9
Figure 4: Test case selected....................................................................................................... 10
Figure 5: The "Fetch DMS Configuration" test case has been completed successfully...............11
Figure 6: The "Update Customer Data" test case has been executed sucessfully......................13
Figure 7: Dealer portal test case................................................................................................ 14
Figure 8: Error when executing the "Create Vehicle" test case..................................................15
Figure 9: Test results and log files view......................................................................................16
Figure 10: Create test report view............................................................................................. 17
Figure 11: log files ZIP created.................................................................................................. 17
Figure 12: Example of results.txt file......................................................................................... 18
Figure 13: IspaValidator.properties file.......................................................................................19
Figure 14: Overall log files organization.....................................................................................20
Figure 15: Log file organization within a test group with all test cases successful.....................20
Figure 17: Example of file dms_cleanup.txt...............................................................................21
Figure 18: Test case log file header............................................................................................ 22
Figure 19: Request / response log structure...............................................................................22
Figure 20: Request / response log example...............................................................................23
Figure 21: DMS communication error example..........................................................................23
Figure 22: Log event structure................................................................................................... 24
Figure 23: A short extract from the overall log file....................................................................24
Release 1503
Copyright BMW AG
BMW Group
Page 4
of
24
1. Introduction
1.1 Purpose of This Document
The ISPA Next / ISPA Mobile Validator is a tool that allows to verify that the requirements for
operating ISPA Next and ISPA Mobile are met. The Validator visually guides through test cases
that check the availability of the implemented DMS interface and central BMW services. The
main focus of the Validator is to test if the DMS has correctly implemented the ISPA interface
that is required by the ISPA applications ISPA Next and ISPA Mobile.
The purpose of this document is to provide users of the ISPA Next / ISPA Mobile Validator with
the means to effectively use the Validator. This document describes how to install, uninstall and
use the ISPA Next / ISPA Mobile Validator.
Release 1503
Copyright BMW AG
BMW Group
Page 5
of
24
2.3 Installation
Unzip the ispa-validator-1.0.0.zip file anywhere on your computer. This will create a ispavalidator-1.0.0 folder.
Switch to this folder and execute the ispa-validator-1.0.0.exe file to start the ISPA Next /
ISPA Mobile Validator.
2.4 Uninstallation
Close the ISPA Next / ISPA Mobile Validator if it is running.
Delete the ispa-validator-1.0.0 folder.
Release 1503
Copyright BMW AG
BMW Group
Page 6
of
24
3. Usage
3.1 Prerequisites
Please make sure that
the device the Validator is installed on, has access to the DMS and the internet.
you know your proxy server URL and credentials, if you use a proxy server.
you have your DMS URL and credentials as well as your dealer portal (S-Gate or
DealerSpeed) credentials at hand.
Select your language and click on Start ISPA Validator to start the Validator.
If you want to start the validation of your DMS interface implemented, continue with
chapter 3.3.
Otherwise, if you only want to test the connectivity of other systems skip the DMS
and Dealer Data configuration and select Test Group 7: Connection to other systems
described in chapter 3.4.4.
Release 1503
Copyright BMW AG
BMW Group
Page 7
of
24
Release 1503
Copyright BMW AG
BMW Group
Page 8
of
24
When you close the application the DMS and dealer data are saved in a
configuration file on harddisk.
The next time you start the ISPA Next / ISPA Mobile Validator the configuration
values are read from this file so that you do not have to reenter all data.
The file can also be used to preconfigure the ISPA Next / ISPA Mobile Validator
before providing it to a dealership (see chapter 3.7).
Release 1503
Copyright BMW AG
BMW Group
Page 9
of
24
On the left hand side, you can see the list of available test groups. On the right hand side, you
can see the content of the currently selected test case.
You can navigate arbitrarily between test groups by clicking on the test group titles:
The test group that contains the currently selected test case will stay open.
If you click on another test case, this test case will become active and its contents will
be displayed on the right hand side.
At the bottom of the window there are two buttons Previous and Next which you can
use to navigate between test cases.
Previous will select the test case that comes before the currently selected test case
and Next will select the next one.
The last entry in the test group list is Test results. This entry provides an overview
over the status of the test cases and a convenient way to save the test logs and
generate a test report (See chapter ).
Release 1503
Copyright BMW AG
BMW Group
Page
10
of
24
Figure 5: The "Fetch DMS Configuration" test case has been completed successfully
Release 1503
Copyright BMW AG
BMW Group
Page
11
of
24
You will always being notified, if a another test group has to be excuted prior to the
execution of a subsequent test case!
Some test cases will display data fetched from the DMS and ask you whether the data returned
by the DMS is correct (see Figure 6).
Click on Yes to confirm and the test case is marked successful.
Otherweise click on No to mark the test case not successful.
Therefore always check your DMS whether the data displayed by the Validator
corresponts to the data stored in your DMS.
Oherwise there might be a mismatch in the mapping of your DMS interface
implementation!
Figure 6: The "Update Customer Data" test case has been executed sucessfully
Release 1503
Copyright BMW AG
BMW Group
Page
12
of
24
Release 1503
Copyright BMW AG
BMW Group
Page
13
of
24
Release 1503
Copyright BMW AG
BMW Group
Page
14
of
24
At the bottom right you can find the button Save log files. Click on that button.
A folder selector opens. Select the folder where you want to store the log files.
A ZIP file named Ispa-Validator-Logs- containing the logs of the most current
ISPA Next / ISPA Mobile Validator run will be created.
You can find the log files for all runs of the ISPA Next / ISPA Mobile Validator in the
logs sub-folder of the ISPA Next / ISPA Mobile Validator installation folder.
Release 1503
Copyright BMW AG
BMW Group
Page
15
of
24
A file named results.txt containing name and city you provided before and an
overview of all test cases and whether they have been executed or not:
Release 1503
Copyright BMW AG
BMW Group
Page
16
of
24
Release 1503
Copyright BMW AG
BMW Group
Page
17
of
24
Release 1503
Copyright BMW AG
BMW Group
Page
18
of
24
The log files for each test case are put within their own folders.
The file dms_cleanup.txt contains the list of test entries created in your DMS and
helps you to find and remove them from your DMS. The list contains the customer
numbers, the vehicle VINs and the Order numbers that have been created in your DMS
by the Validator.
The file dms-tester.log contains all log entries of the Validator and is intended for
experts.
4.1.2 Test cases log files
Figure 15 shows the log file organization with in a test group. The log entries for each test case
will be written into dedicated log files.
You can immediately see which test case has been executed successfully or not by the suffix at
the end of the file name (see Figure 15 and Figure 16).
Log files of successful test cases:
Figure 15: Log file organization within a test group with all test cases successful
Figure 16: Log file organization within a test group with a test case failed
Release 1503
Copyright BMW AG
BMW Group
Page
19
of
24
Release 1503
Copyright BMW AG
BMW Group
Page
20
of
24
Following the header, all communications between the Validator, DCOM and the DMS is logged.
Each request / response is logged as shown in Figure 19.
---------------------------------------------------------------------------------------------------------------------------------------------------------------Timestamp: <<TIMESTAMP>> | Direction: <<DIRECTION>> | Operation: <<OPERATION>> | Time elapsed:
<<ELAPSED>>
---------------------------------------------------------------------------------------------------------------------------------------------------------------<< REQUEST / RESPONSE >>
Release 1503
Copyright BMW AG
BMW Group
Page
21
of
24
If an error occurs, the log file will provide warning and error messages that allow to analyze the
cause of the error (Figure 21).
[2015 02-19 10:59:44.303] ERROR AbstractExceptionStrategy: DcomException thrown in route 'route2' and
processed by handler 'com.bmw.dcom.dcomservice.exception.SearchCustomersExceptionStrategy'.
Transaction ID: de7864c3-c1ce-42f8-89e6-0aea9a996ee6
Including errors:
DcomError No.1
Message: The target system has sent an invalid response.
Error Code: AA_DCOM1601
javax.xml.ws.soap.SOAPFaultException: Response was of unexpected text/html ContentType. Incoming portion of
HTML stream: <html><body><p>There are currently 0 running SoapUI
MockServices</p><ul></ul></p></body></html>
Release 1503
Copyright BMW AG
BMW Group
Page
22
of
Release 1503
24
Copyright BMW AG
BMW Group
Page
23
of
24
Release 1503
Copyright BMW AG
BMW Group
Page
24
of
24
5. Support
NSC only!
The Validator is a tool for the NSC to support the introduction of ISPA Next and/or ISPA Mobile
into a market with regard to the DMS integration.
Whenever you need support regarding the Validator, please contact only your responsible
Market Consultant of the TRAC team in Munich.
Release 1503
Copyright BMW AG