A key advantage to Adobe Access SDK is that you can install it on any Java™ application server or servlet container, such as Tomcat. You also need JDK™ 1.5 or higher. For more information on software requirements, see Adobe Access SDK platform requirements: : https://www.adobe.com/products/flashaccess/systemreqs/.
The high-level steps to deploy Adobe Access are:
These steps are expanded upon in the following sections, with references to other documents containing additional information.
A 64-bit operating system, such as the 64-bit version of RedHat or Windows, provides much better performance than a 32-bit operating system.
Adobe Access SDK is provided as a Java archive (JAR) file. To learn more about installing Adobe Access, see Using Adobe Access SDK for Protecting Content and Secure Deployment Guidelines.
Using Adobe Access SDK, you must create a License Server. When content is protected using Adobe Access, it cannot be viewed until a license is issued to the consumer by the License Server. If identity-based licensing is used, password-based authentication ensures that only authorized consumers can open and view content.
When implementing a License Server, you must obtain the necessary digital certificates from Adobe. Refer to the Adobe Access Certificate Enrollment document for detailed instructions on requesting certificates.
To learn more about implementing a License Server, and obtaining digital certificates, see* Using Adobe Access SDK for Protecting Content.*
Using the Adobe Access SDK, you can create content packaging and policy management tools. The policy management APIs allow administrators to create, view details of, and update policies. The packaging APIs embed the policy into the FLV or F4V file, and encrypt the file using the content encryption key.
The Adobe Access SDK includes a reference implementation ( AdobePackager.jar) that provides examples of content packaging and policy management tools ( AdobePolicyManager.jar).
To learn more about creating content packaging and policy management tools, see Using the Adobe Access SDK For Protecting Content.
Using the usage rules supported by the SDK, you must define and create policies in support of your organization’s business model, and then package your content using those policies. Once policies are applied to content during packaging, you can maintain control of your content no matter how widely it is distributed.
The policies in Adobe Access support a wide range of different usage rules, including:
To learn more about packaging content, see Protecting Content. To learn more about the usage rules and the business models they support, see Usage Rules.
To enable consumers to access and view content, develop a video playback application using Flash Player or Adobe AIR. Once you developed a video playback application, you must deploy it to consumers. If you are developing an application using Flash Player, host it on your organization’s website. If you are developing an application using Adobe® AIR®, post the AIR application installer so that consumers can download and install the application on their computer.
To learn more about developing custom video playback applications for use with Adobe Access, see the “Working with Video” chapter in ActionScript 3.0 Developer Guide*, *the Adobe Video Technology Center, and the Open Source Media Framework.