Whether it be a migration or a faulty entry when installing a servlet (e.g. Recording Library, Multimedia, Realtime nodes, etc) that reaches back out to the Chronicall Server, there may come a need to update the servlet to have it identify the correct location of the main Chronicall Service.
In recent iterations, the ability to update a documentbase.txt file or settings file may not be enough. Below are the methods for Windows-based & Linux-based Servers.
Windows
- Open your file explorer and navigate to the directory hosting the application
- Each application will have its own bin\app folder
- For example
C:\Program Files\Chronicall\<multimedia, recording library, realtime node, etc>\bin\app\
- Right-click the Application file here (in this case ChronicallMultimediaw) and select Run as Administrator
- Navigate to the Java tab
- Under the Java Options: section you can make adjustments to the "-Ddocumentbase=" address in order to point it to the Chronicall server.
- NOTE: If there is a hostname here instead of an IP address, there may be an internal DNS Resolution failure. We recommend using the IP address over a hostname in most instances. Try using an IP address first with the default webserver port (9080) in this line. If it continues to fail, there may be an internal routing issue that would require further assistance from Local Network IT
Linux
For both Debian & CentOS iterations of Linux, the file structure is the exact same.
- Begin by opening your preferred SSH Console (PuTTY, WinSCP, FileZilla, etc) and login to the machine with root access. If you don't have root access, ensure your User has necessary Sudo rights.
- Once connected, same as before, navigate to the directory hosting the servlet
- For example
/var/lib/Chronicall/(multimedia, recording library, realtime node, etc)/bin/app)
- For example
- Within this folder, you will see a .cfg file.
- Using vi or nano, open this file and you will see the following:
- Similarly to Windows, under the JVMOptions, you can make adjustments to the "-Ddocumentbase=" address in order to point it to the Chronicall server.
- NOTE: If there is a hostname here instead of an IP address, there may be an internal DNS Resolution failure. We recommend using the IP address over a hostname in most instances. Try using an IP address first with the default webserver port (9080) in this line. If it continues to fail, there may be an internal routing issue that would require further assistance from Local Network IT.