The Player package uses a Java applet to handle communication with the LMS. This applet is signed, as required by recent versions of Java, but is set to still run within the sandbox security restrictions. If you install a Player package on a web server other than the LMS server, the applet will not be able to communicate with the LMS server due to cross domain restrictions enforced by the browser. When you launch the content, you receive an error (java.security.AccessControlException) and the attempt is not tracked by the LMS.

In previous versions of UPK, this could be handled by moving the Java applet from the content server to the LMS server. This is no longer necessary and the cross domain issue is now handled by deployment of a crossdomain.xml file to the document root of the LMS server. A suitable crossdomain.xml file is written to the aicc directory of published courses (the same directory in which the applet's .jar file is located).

Although we do not believe that moving the Java applet to the LMS server will normally be necessary, it is possible that some server configurations might still require this. The following section describes how to do this.

Moving the Java Applet to the LMS Server

Note: It is unlikely that you will need to do this and should only do so if your particular server configuration makes this necessary. Note that only one copy of the Java applet is needed on the LMS server for multiple LMS Packages on the content server.

1. Locate the file gethttppostdata.jar in the …\aicc folder where you published the content.
       
2. Copy this file to a location on the LMS web server that can be referenced through a URL. Note the full URL to the directory containing the file. For example:
       
      http://lmsserver/somedirectory
       
3. Open the config.js file in the root directory of the location where you published the content using any text editor such as Notepad.
       
4. Locate the following line in the file:
       
      AiccAppletPath : "",
       
5. Change the AiccAppletPath value to the URL that was noted in step #2. For example:
       
      AiccAppletPath : "http://lmsserver/somedirectory",
       
6. Save the file.

Note: If you will normally be deploying your content this way, you may want to edit the Player publishing style to avoid having to perform the steps above each time you publish content. In the Player style, you edit the config.xml file, locate the <item name="AiccAppletPath" line, and add the URL before the close of the item tag such as:

'http://127.0.0.1:81';">http://lmsserver/somedirectory</item>

For more information about customizing Player styles, see Customize the Player in the Publish Content section in the Content Development manual.

Table of Contents  Back