Upgrading 8.3 to 8.4

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Hi Team,

We are upgrading the Sailpoint iiq 8.3 to 8.4 for that we have cloned existing db and we have changed the db details In the iiq properties files also but it is pointing to old db only, we have copied existing identityiq folder , it is showing original environment if I bringing up the services

2

Hey Suresh,

When upgrading from IdentityIQ 8.3 to 8.4, simply cloning the database and updating the iiq.properties file is not sufficient to complete the upgrade. What you are seeing (the system still pointing to the original environment) is expected because the full upgrade process has not been followed.

To avoid issues and ensure a clean, supported upgrade, it’s important to follow the official best practices and upgrade procedure documented by SailPoint:
https://community.sailpoint.com/t5/Working-With-Services-Knowledge/Upgrade-Best-Practices/ta-p/75139?attachment-id=475

In summary, the recommended process includes (but is not limited to):

  • Reviewing the supported upgrade paths (you must upgrade from a supported source version).

  • Cloning and preparing the database correctly.

  • Deploying a fresh 8.4 IdentityIQ build rather than reusing the old application folder.

  • Running the required database upgrade scripts provided with the 8.4 installer.

  • Validating schema changes, configuration, and customized components after the upgrade.

  • Performing end-to-end testing before bringing the new environment online.

  • Checking compatibility of all dependent software components (JDK, application server, database version, etc.) with IdentityIQ 8.4.

  • Being aware of known issues in IIQ 8.4, such as Fix IIQTC-626 — make sure to confirm whether the patch or hotfix is required in your environment.

I’d recommend redoing the upgrade by carefully following the steps outlined in the guide above. That way, your 8.4 environment will be properly aligned with SailPoint’s supported upgrade methodology and you’ll avoid issues like connections pointing to the wrong database or services showing the old environment.

-Ganesh

3

@ganesh-atikes thanks for the response

We are trying to bringing up the current production environment which is 8.3p3 in another server for that we took the backup of db,the backup db is running on different server no relation with the original db but whenever we start the server and accessing the url it is redirecting to my production url and it is showing original db details. My target is replicate the my current environment in another sandbox for upgrading

4

Hi Suresh,

Yeah now it makes sense.

You menitoned about moving DB to another server, are you new server for application server also?

I would like to see iiq.prop file

-Ganesh

5

Hi @sureshbommareddy98

When you’re planning to set up a new instance similar to production by cloning the production DB, the process is:

  1. Install a new application server with the base version, which is IIQ 8.3.
  2. Deploy patch P3.
  3. Update the following configuration files:
  • iiq.properties
  • .hbm files at ..\WEB-INF\classes\sailpoint\object
  • iiq.cfg
  • iiq.dat
    make sure required driver file placed in the ..\WEB-INF\lib folder.
    environment variable setup, JRE_HOME, JAVA_HOME, CATALINA_HOME, PATH

Example:

set JRE_HOME=C:\Program Files\Java\jdk-17\
set JAVA_HOME=C:\Program Files\Java\jdk-17\
set CATALINA_HOME=C:\Software\Instance8.5\apache-tomcat-9.0.98
set PATH=C:\Program Files\Java\jdk-17\bin\

During the setup, you should perform a step-by-step verification:

  1. Check if Tomcat is up and running.
  2. Check the IIQ console.
  3. Start the application server.
6

It is redirecting due to sso configuration..issue has been fixed

7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.