Installing AutoVue Client/Server

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

Notes

• If AutoCAD drawings will be viewed that use custom font (.shx) files, place copies of the font files in the following location after installation:

  C:\Oracle\AutoVue\bin\fonts

• BlueCielo product licenses include the use of AutoVue Client/Server for viewing 2D documents. Viewing 3D documents requires the installation of optional licenses (M--AV3) that are available at additional cost.
• When the Meridian Enterprise Server server is upgraded to a new release, also upgrade the AutoVue server at the same time. The AutoVue server software must be the same version as the JVue applet that is included in the Meridian Enterprise Server release.

• By default, client computers download documents to the Local Workspace when files are viewed. When configured to use AutoVue Client/Server, this does not occur unless documents are printed from the viewer in or if the viewer window is separate from the primary client window (undocked in or the View documents in a separate browser window option is enabled in Web Access).

  If the use of Local Workspace must be prevented completely, for example, to avoid installing SQL Server Compact Edition on the computer to manage the Local Workspace contents, then the vault must be configured to use the BlueCielo Filesystem Service (AMFS) instead. This can be done by disabling the Force clients to access documents from Local Workspace option (enabled by default) as described in the BlueCielo Meridian Enterprise Administrator's Guide. However, this will also negate the benefits of Local Workspace (also described in the BlueCielo Meridian Enterprise Administrator's Guide) and should be carefully considered.

The AutoVue Client/Server software includes a copy of the open source Java application server software Jetty. This is convenient if you will be deploying AutoVue Client/Server 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 Client/Server installation packages install Jetty support by default. These instructions can be used to install AutoVue Client/Server as a desktop deployment. In that case, the references to different computers apply to the same computer.

Before you begin

• Microsoft .NET Framework 3.5 SP1 is required on the web server where the BlueCielo web service is installed in this task.
• Meridian Enterprise Server 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.

To install AutoVue Client/Server:

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 Enterprise Server Administrator’s Guide.

2. If an existing installation of AutoVue Client/Server will not be used, perform this step. Otherwise, skip to the next 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. 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 Enterprise Server.

   Oracle AutoVue Client/Server 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	Configure Later

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

3. On the same computer, run the Meridian Enterprise setup program that contains the same AutoVue Client/Server version as the installed version of AutoVue and install the AutoVue Client/Server Integration component. This will add the BlueCielo Connector to AutoVue and install a BlueCielo web service in the IIS default website. If the Meridian Enterprise web server is a separate computer, run the setup program there also.

4. On the Meridian Enterprise web server, test the web service by opening it in a browser with the following URL.

   http://<ServerName>/BCWebService/BCWebService.BluePrintService.svc

   A page titled BluePrintService Service appears if installation is correct to this point.

5. 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.

6. NEW  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. The windows must stay open but can be minimized. For more information about starting the servers automatically, see Starting the servers automatically.

7. On the 64-bit desktop client (not Web Access) computers, set the registry values that are described in the following tables. On the 32-bit desktop client computers, set the matching registry values in the Wow6432Node branch instead.

   HKEY_LOCAL_MACHINE\SOFTWARE\Cyco\AutoManager View Control2

   Value Name	Data Type	Value Data
   BluePrintWSDL	String	URL of the BlueCielo web service that you installed in step 3. For example: http://<ServerName>/BCWebService/BCWebService.BluePrintService.svc?wsdl
   DMSInfo	String	URL of the BlueCielo Connector that you installed in step 3. For example: http://<ServerName>:8900/wsclient/servlet/DMS. This setting should be the same as the BlueCielo Connector URL property of Meridian Enterprise Web Access.

   HKEY_CURRENT_USER\SOFTWARE\Cyco\AutoManager Meridian\CurrentVersion\Client\Settings

   Value Name	Data Type	Value Data
   ClientServerWebView	DWORD	If this value is 1, the client applications use the AutoVue Client/Server viewer. If this value is 0, the client applications use the locally installed viewers.

   If you are installing AutoVue Client/Server as a desktop deployment on one computer, also set the registry values that are described in the following table.

   HKEY_LOCAL_MACHINE\SOFTWARE\Cyco\AutoManager View Control2

   Value Name	Data Type	Value Data
   AppletRootPath	String	Path to the AutoVue Java applets, for example, C:\Oracle\AutoVue\bin\.
   AutoVueServer	String	URL to the AutoVue rendering server, for example, http://<ServerName>:5098/servlet/VueServlet. If the rendering server software is installed on the local computer, the location of the AutoVue configuration file, for example, direct//C:\Program Files\AutoVue\jVue20_0\bin\autovue.properties. The path settings in autovue.properties must be valid for the local computer.
   BCBeans	String	Path to the BlueCielo Java support libraries. By default, they are installed at: C:\Program Files\Common Files\Cyco Shared\AMViewXBeans.jar.
   JAVAVMDLL	String	Path to the Java virtual machine DLL for support of AutoVue Client/Server, for example, C:\Oracle\AutoVue\jre\bin\client\jvm.dll.

8. Users must enable the AutoVue Client/Server viewer before it will become their default viewer.

   • Web client users must enable the Use Oracle AutoVue for viewing documents option on the Preferences page in Web Access as described in theBlueCielo Meridian Enterprise Server Userʹs Guide.
   • Desktop client users must set the AutoVueViewer option first in viewer priority in the viewer options of Enterprise Server PowerUser as described in theBlueCielo Meridian Enterprise Server Userʹs Guide.
9. Configure Meridian Enterprise Server to use the AutoVue server as described in Configuring the viewer options

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

    Notes    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 Client/Server, see:

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