I am working on upgrading SailPoint IdentityIQ from version 8.3 to 8.4 and have encountered an issue during the process.
So far, I have followed the below upgrade steps,
Download identityiq-8.4.zip from Compass.
Stop the IdentityIQ application.
Take a backup of the DB and jar the IdentityIQ installation directory.
Copy WEB-INF/classes/iiq.properties and log4j.properties to /tmp.
Delete all from /tomcat/webapps/identityiq directory. Unzip identityiq-8.4.zip and copy identityiq.war to /tomcat/webapps/identityiq. jar –xvf identityiq.war
Copy /tmp/iiq.properties and log4j.properties to WEB-INF/classes.
but I am stuck at Step 7. When trying to upgrade the IIQ tables from the command line, the system is unable to open the .sql file. Should I manually execute these SQL queries using a database tool? If so, who this will happen ?
Please let me know if any additional details are needed. Appreciate any guidance!
iiq.properties and log4j.properties ( it should be log4j2.properties)
also in 8.4, you have diffs in iiq.properties and log4j2.properties so you need to update your old properties files. you cannot directly copy paste from 8.3 to 8.4.
In 8.4, we have access history db and it’s entries in properties files.
In 8.4 what are the exact diffs in iiq.properties file. I have compared the both(old and new one) iiq.pro file. As you mentioned the i can the Access history. But not understand completely what need to do with that.
If we simply copy past the existing the iiq.pro and log4j.prof files what will the impact/issue?
What exact changes i need to do new iiq. pro and log4j.pr files and what will be deifies?
I have validated the version compatibility. We have java jdk 11 for that have added the mssql-jdbc-12.8.0.jre11.jar file but still same error we are getting.
Unfortunately, the document you reference has not been updated for upgrading to 8.4. The last upgrade it references is 8.3p2. Since there are database changes in 8.4, the document isn’t really good for upgrading to current.
Can you please share the steps ? is it same as above as below
Download identityiq-8.4.zip from Compass.
Stop the IdentityIQ application.
Take a backup of the DB and jar the IdentityIQ installation directory.
Copy WEB-INF/classes/iiq.properties and log4j.properties to /tmp.
Delete all from /tomcat/webapps/identityiq directory. Unzip identityiq-8.4.zip and copy identityiq.war to /tomcat/webapps/identityiq. jar –xvf identityiq.war
Copy /tmp/iiq.properties and log4j.properties to WEB-INF/classes.
also when u copied the sql jdbc driver ? if possible then share the iiq.properties file.
Related to the access db history that are all changes i need to do. i don’t have added those entry in the new iiq.proererties file. I have attached the iiq.properties file here. iiq.properties (1.8 KB)
I don’t think you can do upgrade without access history db. by default it was disabled so you only need to create access history db and it’s tables.
I will check again and see it was mentioned in doc.
“The Access History feature is enabled by default for new installations but is disabled by default for upgrades, due to configuration requirements. Refer to the IdentityIQ Access History guide for information on how to configure and enable this feature.”
Note: As of 8.4, there is a new identityiqah database, which supports the new Access History feature. The identityiqah database must be created as part of the installation, even if you do not intend to use the Access History feature.
##### Access History ####
##### Data Source Properties for Access History #####
dataSourceAccessHistory.maxWaitMillis=10000
dataSourceAccessHistory.maxTotal=50
dataSourceAccessHistory.minIdle=5
#dataSourceAccessHistory.minEvictableIdleTimeMillis=300000
#dataSourceAccessHistory.maxOpenPreparedStatements=-1
dataSourceAccessHistory.username=identityiqah
dataSourceAccessHistory.password=PWD
also Inside
### MSSQL Server ###
The error java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver means SailPoint can’t find the SQL Server driver. It’s usually expected in /identityiq/WEB-INF/lib.
However, since this is happening in the console (not the main app), something might be off. To check, go to /identityiq/WEB-INF/bin and run: