Please note that Metaflow does NOT support any official DRM standard such as OMA 1.0 or 2.0 or their sub-parts. Nor does Metaflow support integration into certain manufacturer-specific DRM capabilities found on some devices.
Metaflow Digital Rights Fingerprinting allows the user to add a small text file called wmcdist.id to the Jar file in every bundle or a specific bundle depending on the user's specific requirement. This file contains a signature (shown in the image below) which allows the game manufacturer to track the game.
One example is a publisher receiving notification that a newly released game has been found
on a unplanned/unconstructed site. The user who submitted the game has
enabled fingerprinting. By downloading the game from the site, you would be able to read the
However, the user should be aware that this file will affect the size of the packaged output jar file. The file will be added to the jar using standard jar compression to ensure compatibility with all handsets. If the user does decide to use fingerprinting, he should always check that the file does not exceed the Maximum, Permitted File Size specified in the Submission Specification for the channel to which he is submitting.
There are 3 examples as shown below:
Fingerprinting can be enabled/disabled during the Metaflow Discovery process in the project's default properties MIDlet tab (as highlighted in the image below). Enabling the feature from this point will enable it for all bundles in your project by default. This includes any bundles added at a later stage for Backfilling. (NOTE: If a user runs re-discovery on a project on which he enabled fingerprinting for original discovery but has now DISABLED fingerprinting, fingerprinting will ONLY be switched off on new bundles discovered. Any Bundles previously discovered have to be done manually from the bundle multi editor)
Fingerprinting can also be enabled/disabled from the Multi-Edit feature. From the Plan tree view, right-click on the bundles folder and select Multi-Edit from the drop down (as shown in image below).
From the MIDlet screen, the user can select/de-select the fingerprinting feature for each specific bundle by selecting the next button in the lower right hand corner and selecting finish when all required bundles have had the feature enabled/disabled as required.(as highlighted in image below)
During packaging, the user may be required to enable/disable fingerprinting for 1 bundle only. To achieve this, the user would double left-click on the specific bundle in the packaging view and then select the MIDlet tab in the lower section of the screen opened (as highlighted in the image below). (NOTE: This is only applied at the DELTA level. To apply this at a scoped level, the user must double-click the bundle link in the top left hand corner as highlighted.)
After the user has applied the fingerprinting feature, he will need to re-package any bundles to which this change has been applied. To confirm the file has been included in the specific bundles required, the user would double-click the bundle (or right-click on a bundle and select Open) and select the JAR tab, the Packaged tab, double-click on the greyed-out bundle and then scroll to the bottom. (All highlighted in the image below)
