Show Menu
TOPICS×

Command line usage

Before using Media Packager, ensure that you fulfill the requirements listed in Requirements and that the configuration file contains the required information (see Configuration file in the Using the Adobe Access Reference Implementations .
Media Packager is in the \Reference Implementation\Command Line tools directory on the DVD. To encrypt a single file, use the following syntax:
java -jar AdobePackager.jar  
<i class="+ topic ph hi-d="" i "="">
  source  
 <i class="+ topic ph hi-d="" i "="">
   dest [ 
  <i class="+ topic ph hi-d="" i "="">
    options] 
  </i class="+ topic> 
 </i class="+ topic> 
</i class="+ topic>

  • source is the file to be encrypted.
  • dest specifies where the encrypted content will be written. If a directory is specified, the encrypted file will be saved in this folder using the same file name as the source file, but the directory must not be the directory which contains the source file.
To encrypt multiple files with the same key (for multi-bit-rate support), use the following syntax:
java -jar AdobePackager.jar  
<i class="+ topic ph hi-d="" i "="">
  sourcefiles  
 <i class="+ topic ph hi-d="" i "="">
   dest-directory [ 
  <i class="+ topic ph hi-d="" i "="">
    options] 
  </i class="+ topic> 
 </i class="+ topic> 
</i class="+ topic>

  • sourcefiles is a series of whitespace-delimited source entries representing the files to be encrypted.
  • dest-directory specifies where the encrypted content will be written. The encrypted files will be saved in this folder using the same file names as the source files, but the directory must not be the directory that contains the source files.
To view information about an encrypted file, use the following syntax:
java -jar AdobePackager.jar -d  
<i class="+ topic ph hi-d="" i "="">
  encryptedfile [-e] [-m] 
</i class="+ topic>

  • encryptedfile is the encrypted file.
To view information about a metadata file, use the following syntax:
java -jar AdobePackager.jar -dm <metadatafile> [-e]

  • metadatafile is a .metadata file containing the DRM metadata.
During packaging, the Media Packager will no longer generate a .header file by default. To generate this file, use the -h option during packaging.
The following table contains descriptions of the command line options shown in the syntax above:
Command line option
Description
-c configfile
Specifies the location of the configuration file. If this option is not used the Media Packager will look for flashaccesstools.properties in the working directory.
-d encryptedfile
Shows information about a file that was already packaged. The source and destination files are not required.
-dm metadatafile
Shows information about existing metadata. The source and destination files are not required.
-e
Use this option with -d to extract policies from a packaged file. A file will be created in the same directory as the encrypted file using the file name and policy identifier.
-h
Use with -d to extract the DRM header from a packaged file. A file is created in the same directory as the encrypted file, using the file name and the extension .header
-i contentID
Specifies a unique identifier for this piece of content. If no identifier is specified, the destfile file name will be used.
-k key = value
Specifies a custom key/value to add to content metadata. Multiple -k options may be specified.
-m
Use this option with -d to extract metadata from a packaged file. A file will be created in the same directory as the encrypted file using the file name and the extension .metadata .
-noprompt
Do not ask whether the destination file should be overwritten. If the destination file already exists and -o is not set, an error will be returned.
-o
Overwrites the destination file without prompting, if it already exists.
-p filename [domain-transport-cert]
Specifies the name of the file containing the policy. If the policy requires domain registration with a server that uses a different transport certificate than the one specified in the properties file, the domain transport certificate also needs to be provided.
Multiple -p options may be specified, and the client will use the first by default. The values specified on the command line take precedence over those specified in the configuration file.