Restore site-specific properties files

To upgrade from Oracle Empirica Signal 9.1.0.x, 9.2.0.x, 9.2.1.x, 9.2.2.x, or 9.2.3.x , or 2025.4.x to 2026.2.01, it is necessary to restore site-specific properties files.

Perform these steps using the non-privileged user account on the application server.

  1. In a command shell, navigate to the backup directory <INSTALL_DIR>/Signal_Install_old/Signal/WEB-INF/classes.
  2. Copy the webvdme.properties file to the installation area. For example:
    $ cp webvdme.properties /u01/stage/Signal_Install/Signal/WEB-INF/classes
  3. Update the webvdme.properties file in /u01/stage/Signal_Install/Signal/WEB-INF/classes:
    1. Update the Oracle Empirica Signal help URL content from /u01/stage/Signal_Install/Signal/WEB-INF/classes/template_webvdme.properties and, if custom help is configured, uncomment help.url:
      # Signal help URL
# To override the default help URL, uncomment and change the major version and patchset version if available of the URL
# e.g., help.url=https://docs.oracle.com/pls/topic/lookup?ctx=en/industries/life-sciences/empirica-signal/9.x/userguide&id=
#help.url=https:/docs.oracle.com/pls/topic/lookup?ctx=en/industries/life-sciences/empirica-signal/
<majorVersion.minor.Version.[patchsetVersion]>/userguide&id=
    2. Remove deprecated property oracleHelpCenter.url and related content.
      # Oracle Help Center URL for hosting help content
# If the property or its value is not set, then help will default to the local help file
oracle.HelpCenter.url=https://docs.oracle.com/life-sciences-empirica-signal-90./ESIUG
  4. Copy the listener.properties file to the installation area. For example:
    $ cp listener.properties /u01/stage/Signal_Install/Signal/WEB-INF/classes
  5. Update properties. For example:
    mgps_prr_mem_limit and RGPS\ Maximum\ Lambda=0.3
RGPS\ Minimum\ Lambda=1.0
  6. Open the listener.properties file in a text editor to update the parameter. For example:
    mgps_prr_mem_limit=4054686
  7. Copy the report_listener.properties file to the installation area. For example:
    $ cp report_listener.properties /u01/stage/Signal_Install/Signal/WEB-INF/classes
  8. Copy the webvdme-fonts.properties file to the installation area. For example:
    iText.TABLE_WRITER_BASE_FONT_PATH=GoNotoCurrentJp.ttf 
iText.CASE_SERIES_DETAIL_BASE_FONT_PATH=GoNotoCurrentJp.ttf 
iText.TOPIC_WRITER_BASE_FONT_PATH=GoNotoCurrentJp.ttf
  9. Copy the log4j2.xml file to the installation area, overwriting the existing file. For example:
    $ cp -f log4j2.xml /u01/stage/Signal_Install/Signal/WEB-INF/classes
  10. Update the following file from:
    <SizeBasedTriggeringPolicy size="10 MB" />
                        </Policies>
                        <CronTriggeringPolicy schedule="0 0 0 * * ?" />
    to:
    <SizeBasedTriggeringPolicy size="10 MB" />
                 <CronTriggeringPolicy schedule="0 0 0 * * ?" />
                        </Policies>
  11. If Oracle Empirica Signal is integrated with LDAP, copy the Oracle Empirica Signal file to the installation area. For example:
    $ cp ldap.properties /u01/stage/Signal_Install/Signal/WEB-INF/classes
  12. In a command shell, navigate to the backup directory <INSTALL_DIR>/Signal_Install_old/TopicsService/WEB-INF/classes.
  13. Copy the webvdme.properties file to the installation area. For example:
    $ cp webvdme.properties /u01/stage/Signal_Install/TopicsService/WEB-INF/classes
  14. Copy the log4j2.xml file to the installation area, overwriting the existing file. For example:
    $ cp -f log4j2.xml /u01/stage/Signal_Install/TopicsService/WEB-INF/classes

Parent topic: Upgrade from Oracle Empirica Signal release 9.1 or later