Importing Subscriber Data
dsTest will increment subscriber identities for the number of subscribers in a group, beginning with the starting value defined in the XML configuration. When it is necessary to use non-adjacent values for identifiers such as IMSI or MSISDN, or to provision varying values for non-incrementing items, you can explicitly provision each subscriber by configuring and uploading a comma-separated value (CSV) file. The name of the file is referenced in the subscriber database, which also means that you can configure one CSV file to supply those values for all of your tests.
|
|
Spreadsheet programs such as Excel may default to scientific notation for large numbers. Be sure to apply a format that displays all digits as the CSV file will contain values as they are displayed in the spreadsheet column. We recommend using a text editor to inspect your CSV files before attempting to use them.
Do not provision any subscriber identities in your XML configuration if those values will be supplied by your CSV file. dsTest will not load the CSV file if there are any conflicts with existing subscriber identities.
|
dsTest will attempt to parse the referenced file as a CSV file, and then overlay its contents on the database values initialized by the XML configuration. The first line of the CSV file identifies the elements to be provisioned, and it must use the element names and the element sequence defined by the subscriber database schema. The remaining lines represent the subscribers that will be provisioned, always beginning with the first subscriber in the database (i.e, line 2 provisions subscriber 1, line 3 provisions subscriber 2, and so on).
The CSV file must have a header line which contains the XML element names, and the row index (minus 1) shall represent the subscriber record index within the database. Processing will gracefully stop at the last row of the CSV file, even if there are fewer rows than configured subscribers. Processing will also stop when or if the number of rows exceeds the number of subscribers defined in the database. For complex sub-elements such as profiles (e.g., Subscription, SmartProfile, Service, etc.), the contents of the column name should be the name of an existing profile. For SmartBuffers columns, the value of the row shall be used as the local buffer value for the subscriber matching the row index. The first SmartBuffers column will be buffer 1, and the second will be 2, and so on...
The partial CSV file display below will configure subscribers with the specified values:
.jpg)
Note that the elements specified in the first row must be in order of the schema that defines the subscriber database.
You can import subscriber data using a CSV file with either the dsClient Terminal or dsClient Desktop. If you use dsClient Desktop, you can import the CSV file into your library, making it available to your other workspaces, and the file will always be uploaded to dsTest when you transmit your workspace.
You can find example CSV files in the /usr/local/devsol/dsTest/examples directory on your dsTest server.