================================
Update Third-party Components
================================
The following versions of third-party components are recommended:
   
   Apache 2.4.x      (2.4.41 is bundled)
   Subversion 1.12.x  (1.12.2 is bundled)
   
Since the 17.1 release, the Apache and Subversion Binaries are compiled in-house.
The Apache Haus compiled binaries are still compatible if required by any additional third-party customizations.
   
   PostgreSQL 11.4  (11.4 is bundled)
   AdoptOpenJDK 11 (LTS)   (Not bundled)
   
It is highly recommended that you update to these versions in your Polarion installation.

IMPORTANT! 


1. Polarion no longer supports Oracle's Java SE Development Kit 8 and now only supports OpenJDK 11. 

   Recommendation: Use AdoptOpenJDK 11 (LTS). It is continuously tested with Polarion and offers long-term support.
   It can be found at: https://adoptopenjdk.net/releases.html?variant=openjdk11&jvmVariant=hotspot 

   NOTE: If you've added extra GC-related runtime parameters for Java, you will need to update them accordingly for OpenJDK 11. 
   (The JVM may fail to start with Java 8 style GC options.)  

2. Back up your Java keystore before making the switch to OpenJDK.
   See the  "Update Java" and "Import Java Keystore certificate" sections in the Windows installation guide for details. 
   
3. Whenever you update OpenJDK, you will also have to update the Java path in both 
   the polarion.ini and exec.bat files. (Both files are located in C:\Polarion\polarion\ by default.)  
   

You can download or view the latest documentation in the Polarion section of Siemens' Doc Center at:
   https://polarion.plm.automation.siemens.com/documentation/latest 


Updating to the Bundled Version of PostgreSQL
=============================================
When Polarion releases a new PostgreSQL version with a product update, you must update PostgreSQL manually on Windows systems. 
This is because automated updating of the PostgreSQL binaries poses risk of data loss. Updates to bundled third-party software are 
announced in the bundled "Configuration.txt" file each release. 

Please obtain a copy of the installation guide for Windows and familiarize yourself with the information on PostgreSQL before proceeding. 

IMPORTANT:
Manually updating PostgreSQL to any version other than the one bundled in the update distribution (for existing installations)
or installed by the installer programs/scripts (for new installations) is NOT recommended. Please wait until support for a new 
version is officially announced and update scripts and/or documentation are available.

To update PostgreSQL:

1. Stop the Polarion server, then stop PostgreSQL Service. (You can leave the Apache Service running.)
   Use the shortcuts at C:\Polarion\polarion shortcuts (default path). 

2. Run the "update.bat" script found in the update distribution.

3. Update PostgreSQL to the version bundled in the Polarion update distribution.
   Use https://www.postgresql.org/docs/11/pgupgrade.html to upgrade your database, or just delete the directory and after installing the 
   same postgresql version as our bundled version, then run the "[UPDATE]\bundled\postgres\configure_postgres.bat" script to initialize 
   a fresh database.
   
4. Start PostgreSQL (which you will stop as part of the manual update procedure).

5. Start the Polarion server. 
   Note that reindexing launches on start-up, during which all necessary data are updated in PostgreSQL.

Updating to Bundled Versions of Apache and Subversion
=====================================================
This section describes how to update to the bundled versions of Apache and Subversion.
Please read and follow the instructions in this section carefully. 
 
If you would like to update to the latest service release of these components, the process is 
described in the section "Manually Updating Third-party Software" in the Polarion Installation 
Guide for Windows, available to download online in the Polarion section of Siemens' Doc Center at:
   
   https://polarion.plm.automation.siemens.com/documentation/latest

The update script prepares the update of Apache and optionally Subversion. The update procedure varies  
depending on the Polarion version you are updating. Follow the instructions that pertain to the 
version you currently have installed.

NOTE: 
In the instructions, "[INSTALL]" refers to the root folder of the Polarion installation.
this is typically C:\Polarion  

I. Updating Polarion Version 3.3.0 or newer

  Apache and Subversion: the script conditionally creates folders
  [INSTALL]\bundled\apache_[APACHE_VERSION] and 
  [INSTALL]\bundled\svn_[SVN_VERSION].
  
  (These folders are created ONLY if the script updates a version of 
  Polarion that contained an older version of Apache or Subversion.)
          
  To finalize the update of Apache and Subversion, please follow these steps:
   
  a) Stop Polarion and Apache servers.
     
  b) Remove the old Subversion folder [INSTALL]\bundled\svn and rename 
     the new one [INSTALL]\bundled\svn_[SVN_VERSION] 
     to [INSTALL]\bundled\svn.

  c) Rename the old Apache folder [INSTALL]\bundled\apache 
     to e.g. [INSTALL]\bundled\apache_old, and rename
     the new Apache folder [INSTALL]\bundled\apache_[APACHE_VERSION]
     to [INSTALL]\bundled\apache.
     
  d) Merge the "conf" folder inside "[INSTALL]\bundled\apache_old" with the one in the [INSTALL]\bundled\apache folder. 
     If you have custom changes in other folders of Apache 
     (e.g. additional modules), also copy them to the [INSTALL]\bundled\apache folder. 

  e) Upgrade Apache configuration files according to 
     http://httpd.apache.org/docs/2.4/upgrading.html

     or 

     Make following changes in httpd.conf to use compatibility mode:

     Load these modules:
     LoadModule access_compat_module modules/mod_access_compat.so
     LoadModule authn_core_module modules/mod_authn_core.so
     LoadModule authz_core_module modules/mod_authz_core.so

     Comment out these existing modules:
     #LoadModule authz_default_module modules/mod_authz_default.so
     #LoadModule authn_default_module modules/mod_authn_default.so
     
     (NOTE: If after running Apache, the error message below appears, then load the
      "LoadModule authnz_ldap_module modules/mod_authnz_ldap.so" module.)
      
     "Invalid command 'AuthzLDAPAuthoritative', perhaps misspelled or defined by a module not included in the server configuration". 

     If you have enabled SSL support then load this module in httpd.conf:
     LoadModule socache_shmcb_module modules/mod_socache_shmcb.so

     And comment out following line in httpd-ssl.conf:
     #SSLMutex default

     Make the following changes in polarionSVN.conf

     Add this to mod_authnz_ldap.c configuration and use if needed:

     #Uncomment this option when "500 Server failed" is returned and Apache's log contains the following error: 
     #"This function has not been implemented on this platform: AH01277: LDAP: Unable to add rebind cross reference entry. Out of memory?"
     #LDAPReferrals Off 
   
  f) Optional, but recommended for increased performance: Update the "MaxKeepAliveRequest" property to 10000 in the 
     [INSTALL]\bundled\apache\conf\extra\httpd-default.conf file.

  g) Start Apache, PostgreSQL and Polarion server. If prompted on login, re-activate Polarion using your license key and check that 
     everything works as expected. 

  h) Compare the apache_old configuration files and the updated configuration files and add any customization changes done to the 
     the updated files.
  
  i) Delete [INSTALL]\bundled\apache_old.


II. Updating Polarion older than Version 3.3.0
    Updating a system running a version older than 3.3.0 involves a number of issues in addition to updating third-party software. 
    We recommend that you seek assistance from Polarion Technical Support via the Siemens Global Technical Access Center (GTAC),
    http://www.siemens.com/gtac