How to Define the Path to Java in Direct Suite for Windows
Posted by Aly Essa, Last modified by on 03 August 2016 05:14 PM

Overview

The FileCatalyst Direct Suite has the ability to specify a version of the Java Runtime Environment to use when launching the application as a service. Some common issues that are reported to the Support Team are:

  • Application stalls.
  • Abnormal service termination.
  • The application does not launch or exits abruptly.
  • Windows Service Manager Error 1067: "The process terminated unexpectedly".

The FileCatalyst Server, HotFolder and Central deployments can be installed as a Windows Service. If the current version of Java is updated while the application service is still active the corresponding application will experience a crash and the service will not cycle properly.

All FileCatalyst Direct Suite applications can be run in standalone mode and can experience the symptoms described above. However, the applications that run in standalone mode will pull the Java Path from the Windows Environment.

This article will provide a walkthrough on how to modify the current path to the Java command in your deployment for applications running as a service. The following instructions only apply to Windows systems and may require elevated user privileges. The resolution section is sorted by product. 

Environment

FileCatalyst Direct Suite v3.4 and later.

Resolution

For the following solutions to be deployed correctly, all FileCatalyst applications and services must be shutdown as the configuration files will be modified. Before we proceed to modify the configuration files verify the Windows Environment has a valid installation of Java RE or Java DK. 

  1. Java Installation and Verification

    1. Open the Command Prompt and run the following:

      java -version

      The expected output from the command should look like:


      C:\WINDOWS\system32>java -version
      java version "1.8.0_91"
      Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
      Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)

      Note the version of Java may vary between installations and when the Java RE or Java DK package has been installed.


    2. If you did not receive and output similar to step 1a, download a Java RE or Java DK package from: http://www.oracle.com/technetwork/java/javase/downloads/index.html.
      We recommend using a Java with x64 architecture. After the installation is complete retest step 1a.

  2. Java Path Configuration for FileCatalyst Applications

    1. FileCatalyst Server

      1. Shutdown the FileCatalyst Server service and any FileCatalyst Server Remote Admin applications.
      2. Navigate to the FileCatalyst Server installation directory. By default, it is installed in C:\Program Files\FileCatalyst Server\.
      3. Open the configuration file fcconf.conf in a text editor.
      4. Locate the Java Command. It will be located under the Wrapper Properties section and will look like:

        wrapper.java.command=C:/Program Files/Java/jre1.8.0_91/bin/java

        If you would like to use a specific Java version specify the path after wrapper.java.command=. Since the Java installation was verified in step 1, we recommend using the path that the Windows Environment recognizes to the Java Application. The property should look like:


        wrapper.java.command=java

      5. After your changes are made to the wrapper.java.command, save the file and close the text editor. On the next launch of the FileCatalyst Server (service or standalone) the new Java path will be pulled.

    2. FileCatalyst HotFolder

      1. Shutdown the FileCatalyst HotFolder service and any FileCatalyst HotFolder Remote Admin applications.
      2. Navigate to the FileCatalyst HotFolder installation directory. By default, it is installed in C:\Program Files\FileCatalyst HotFolder\.
      3. Open the configuration file fchf.conf in a text editor.
      4. Locate the Java Command. It will be located under the Wrapper Properties section and will look like:

        wrapper.java.command=C:/Program Files/Java/jre1.8.0_91/bin/java

        If you would like to use a specific Java version specify the path after wrapper.java.command=. Since the Java installation was verified in step 1, we recommend using the path that the Windows Environment recognizes to the Java Application. The property should look like:


        wrapper.java.command=java

      5. After your changes are made to the wrapper.java.command, save the file and close the text editor. On the next launch of the FileCatalyst HotFolder (service or standalone) the new Java path will be pulled.

    3. FileCatalyst Central

      1. Shutdown the FileCatalyst Central service.
      2. Navigate to the FileCatalyst Central installation directory. By default, it is installed in C:\Program Files\FileCatalyst Central\.
      3. Open the configuration file mawrapper.conf in a text editor.
      4. Locate the Java Command. It will be located under the Wrapper Properties section and will look like:

        wrapper.java.command=C:/Program Files/Java/jre1.8.0_77/bin/java

        If you would like to use a specific Java version specify the path after wrapper.java.command=. Since the Java installation was verified in step 1, we recommend using the path that the Windows Environment recognizes to the Java Application. The property should look like:


        wrapper.java.command=java

      5. After your changes are made to the wrapper.java.command, save the file and close the text editor. On the next launch of the FileCatalyst Central Service, the new Java path will be pulled from the system.

Comments (0)