BlueCielo Meridian Explorer 2017 User's Guide

Installing AutoVue

Installing AutoVue includes installing the AutoVue software on a Java application server and installing the components that integrate AutoVue on the web server and on the Java application server (if separate). The AutoVue software and documentation are available on the BlueCielo FTP server. Installation also includes configuring Explorer to connect to those components when a document should be viewed.

The AutoVue software includes a copy of the open source Java application server software Jetty. This is convenient if you will be deploying AutoVue and do not have an existing Java application server on which to host AutoVue. It is also useful if you want a lightweight Java application server for desktop deployment. For convenience, the AutoVue installation packages install Jetty support by default.

The Jetty server is adequate for desktop deployments and small client/server deployments. In larger deployments, we recommend deploying the BlueCielo Connector component on the Apache Tomcat Java server instead. For guidance, refer to the BlueCielo knowledge base or BlueCielo ECM Solutions Technical Support.

The following instructions can also be used to install AutoVue as a desktop deployment. In that case, the references to different computers apply to the same computer.

Before you begin

• Microsoft .NET Framework 4.6 is required on the web server where the BlueCielo web service is installed in this task and ASP.NET must enabled.

  To enable ASP.NET, run one of the following from a command line window with elevated privileges, depending on the bit width and version of .NET Framework that is installed, and restart IIS:

  %windir%\Microsoft.NET\Framework\<VersionNumber>\aspnet_regiis.exe -i
  %windir%\Microsoft.NET\Framework64\<VersionNumber>\aspnet_regiis.exe -i
  

• Meridian Explorer can use an existing AutoVue server that has already been configured to work with Meridian Enterprise as described in the BlueCielo Meridian Enterprise Administratorʹs Guide. Alternatively, another instance can be installed on a different server.
• Any firewall protecting the AutoVue server must allow inbound TCP traffic on port 80. Otherwise authentication or timeout errors can occur.

To install AutoVue:

1. Ensure that the server and client computers meet the hardware and software requirements described in the Oracle AutoVue Client/Server Deployment Installation and Configuration Guide and in the BlueCielo Meridian Explorer Administrator’s Guide.

2. If an existing installation of AutoVue will be used, skip to the next step. Otherwise, perform this step.

   On the computer that will be the AutoVue server, install the AutoVue 2D or AutoVue 3D server software using its respective Oracle setup program. If both versions will be used, each version must be installed on its own computer. Use the instructions for non-integrated installation in the Oracle AutoVue Client/Server Deployment Installation and Configuration Guide. The following table lists the installation option responses that are adequate for integration with Meridian Explorer.

   Oracle AutoVue installation options

   Option	Setting
   Specify Installation Directory	Accept the default (C:\Oracle\AutoVue)
   Select Install Set	Standard
   Select Shortcut Folder	Accept the default (Oracle AutoVue)
   Specify hostname or IP address for the AutoVue Server	Accept the default
   AutoVue Server Authentication	Configure Later
   Enabling SSL Communication	If you do not want to use the SSL protocol, select Configure Later. If you do want to use SSL: Select Configure SSL with a CA certificate and click Next. The Select the CA certificate file page appears. Select a valid CA certificate and click Next. The Select the Identity JKS Keystore file page appears. Click Next. A default file will be created as: C:\oracle\autovue\bin\AutoVueIdentity.jks The Specify the Identity JKS Keystore password page appears. Type a password and click Next. The password will be stored in the file: C:\oracle\autovue\bin\jetty\etc\jetty-ssl.xml Perform the rest of the steps described in Configuring viewing with SSL.

   Tip    These settings configure the AutoVue server as a stand-alone application that can be used outside of Explorer by opening the page at http://<ServerName>/jVue/jVue.html.

3. On the AutoVue server, open the file StartServers.bat in any text editor and verify that the paths are correct for your installation. By default, it is located in C:\Oracle\AutoVue\bin.

4. By default, the Jetty application server, the AutoVue servlet, and the BlueCielo Connector servlet will be started automatically. If this fails due to system configuration or security issues, the server can be started manually by running StartServers.bat. Two command prompt windows and the AutoVue Server console window appear. If the last lines in the command prompt windows contain the text INFO: Started and the Processes boxes in the AutoVue Server window are green, the server started successfully. The windows must stay open but can be minimized. For more information about starting the servers automatically, see Starting the servers automatically.

5. Check whether the AutoVue servlet is working:

   • Open a web browser window to the following URL:

     http://<ServerName>:5098/servlet/VueServlet

     A page titled VueServlet for AutoVue <Version> should appear.

6. (Optional) Configure Meridian Explorer to use the AutoVue server as described in Configuring the viewer options.

7. Test AutoVue by opening a document in the client application. The AutoVue applet downloads from the web server and opens the selected document.

   Note    

   To prevent the Java authentication dialog from appearing at the beginning of each viewing session, you may need to configure one or more of the following settings:

   • Add the fully qualified name of the AutoVue server to the Local intranet zone in the Internet Explorer security options on the client computers but do not add it to the Trusted sites list.
   • Add the account name that is used for the application pool under which the web application is run (for example, Web Access or Meridian Explorer) to the Act as part of the operating system policy using the Local Group Policy Editor.
   • Define an authentication level for Network security: LAN Manager authentication level using the Local Group Policy Editor. The setting cannot be Not Defined.
   • On Windows Server 2003 and Windows XP computers, the account under which the BCConnectorService logs on should be changed from Local System to an account that has access to the website.

For more information about configuring and administering AutoVue, see:

• Oracle AutoVue Client/Server Deployment Installation and Configuration Guide
• Oracle AutoVue Desktop Deployment Installation and Configuration Guide