In-app simulation settings are application specific. The developer is allowed to create In-app settings for the application and could test In-app purchase over real scenarios.
This application name is specific for a MIDlet and all the settings which are made in Purchasable Items, Restore and Restorable Products and in DRM Access, User and Device Data tabs will be saved under this application name.
Figure: Application Details UI
The developer has to choose the application name from the drop down list for the MIDlet which needs to be tested for In-app purchase scenario.
To create new In-app purchase settings, the developer has to enter the application name by selecting the Create button. This application name should be unique and should not be previously used. All application name created earlier will be listed in the drop down list. The SDK simulation will be using the currently selected application’s settings for simulating In-app purchase behavior.
The developer has to give the path for the MIDlet workspace by selecting the Browse button.
By entering the application
name and selecting the path for the project, there will be folder drm/data
created automatically in the res
directory of the MIDlet project work area which is needed for In-app
resource files.
IAP specific file IAP_VARIANTID.txt
will be generated in the res
folder automatically,
which is required to run the MIDlet which uses the IAP APIs in the
emulator.
The developer has to store the resource files for
the purchase items in the <project_root>\<resource_folder>\drm\data
folder of the MIDlet project.
Store the resource files for
each purchase item in their own subfolder named resourceid_x
, where x
is the product ID of the corresponding
purchase item. This ensures maximum content security. For example,
in an Eclipse project, store the files in <project_root>\res\drm\data\resourceid_123
, where 123
is the product ID.
For more information, see the Implementing In-app Purchase section in Java Developer's Library.
The developer has to give a short title for the MIDlet. This is just general information of the application under test.