OLM uses a servlet to upload or download physical content files. So, you do not require an FTP server, nor a middle tier installation on the content server. You simply require one container for the servlet, such as Apache and ApacheJserv. So that only the trusted servers can access OLM content, the IP addresses of the APPS middle tiers are specified in the container property file as arguments passed to the Java interpreter.

You set up a content server in two stages:

1. Set up the container.

2. Define the content server in the OLM administration interface.

   Steps to set up the container:

1. Install the container, such as Apache and ApacheJserv.

2. Create a servlet repository called servlets. For example, in Jserv, the servlets repository exists by default.

3. Copy the following files to your servlet repository directory:
   $JAVA_TOP/oracle/apps/ota/admin/common/util/ContentServerServlet.class
   $JAVA_TOP/oracle/apps/ota/admin/common/util/ProtocolConstants.class
   $JAVA_TOP/oracle/apps/ota/admin/common/util/SystemUtils.class
   $JAVA_TOP/oracle/apps/ota/admin/common/util/SystemUtils$JarUtility.class
   $JAVA_TOP/oracle/apps/ota/admin/common/util/ContentServeerClientData.class

4. Also ensure the oracle.apps.fnd.common.VersionInfo.class file is located under the class path directory that is defined for the repository.

5. In zone.properties, add the following:
   # ----- OLM Content server ----- # servlet.OtaContentServerServlet.code=oracle.apps.ota.admin.common.util.ContentServerServlet servlet.OtaProtocolConstants.code=oracle.apps.ota.admin.common.util.ProtocolConstants servlet.OtaSystemUtils.code=oracle.apps.ota.admin.common.util.SystemUtils servlet.OtaSystemUtils$JarUtility.code=oracle.apps.ota.admin.common.util.SystemUtils$JarUtility servlet.OtaContentServerClientData.code=oracle.apps.ota.admin.common.util.ContentServerClientData #
   ----- END OLM

6. Create an alias for the directory where the content will be stored. For example, in Apache, to create an alias for the physical directory D:/apache/rootdir/, add the following inside the httpd.conf file: Alias /content/ 'D:/apache/rootdir/'

7. Add the list of middle tiers and the temporary file location as arguments to the Java Interpreter. For example, in Jserv, add following lines inside the jserv.properties file: wrapper.bin.parameters=-Dmiddletier=148.87.19.51+148.87.19.50+144.25.78.202+10.10.20.140
   wrapper.bin.parameters=-DTemp=D:\temp wrapper.bin.parameters=-Djava.io.tmpdir=/dbfiles/applcsf/log
   Here the numbers, such as 148.87.19.51 and 148.87.19.50, are IP addresses of all trusted middle tiers, and + is the separator for multiple addresses. Servers not specified in the list are not able to access the servlet.
   D:\temp is the absolute path of the temp location where files are saved temporarily while handling physical content.
   /dbfiles/applcsf/log is any existing directory for log files.

   Steps to define the content server in OLM:

1. Log in to OLM with Learning Administrator responsibility.

2. Click the Setup tab.

3. Click Content Servers.

4. Click Create Content Server.

5. Provide the following information:

   1. Name: XYZ (your choice of content server name)

   2. Protocol: http or https (generally http)

      Additional Information: To use a content server protocol other than ftp, http, or https, you must add the value to the Content Server Protocol Types lookup.

   3. Host: The machine name on which your servlet container is running. Example: ap1234.oracle.com.

   4. Port: The port at which servlet container is running (by default the port is 80)

   5. Physical Directory: The absolute path of the location where the content will be stored. For example, according to the example above: D:/apache/rootdir/

   6. Virtual Directory: The alias you created when setting up the container properties. For example, according to the example above: /content.

6. Defining an Oracle WebCenter Content (OWCC) Server

   To use Oracle WebCenter Content (OWCC), formerly Oracle Universal Content Management, as a content server for OLM content, administrator must define an OWCC server. Enter details of the OWCC server and select the UCM Content Server check box. When you select this check box, a section called Test Connection appears. You can test your access to the OWCC server by entering the user name and password. You must place the SCORM adaptor files in the right location in the OWCC server for SCORM content to work correctly.