Patching IdentityIQ Environment
Patching is when at Base version and to move with new update release. For Example :
To Upgrade from 7.0p1 and to implement p5 :
7.0p1 ---------------------> p5
so the recommend approach would be go ahead with the sequence as :
go with patch2 first then to implement patch3 and then implement patch4 and finally implement patch5 in the prod env.
p2,p3,p4 ---------------------> p5
Steps for Patching :::---------------------------------------------
- Download patch jar file. e.g identityiq-7.3p2.jar this is an executable jar file which is leveraging.
- Put the jar file on top of the base version means inside the identityiq folder in webapps. As base version identityiq.war file is present in webapps so for patching it is required to keep under identityiq folder and not in webapps where identityiq.war file is kept.
- Extract the jar file. Command is : jar -xvf identityiq-7.3p2.jar
- Need to Patch the Database as well with the iiq schema command to generate the scripts to update database. Navigate to WEB-INF/bin folder : in bin folder to get console access with the help of iiq.bat And if run this bat we can see so many different types of usable command. But for Patch we need the iiq schema command to update the database with the new database scripts generated.
- To Execute these upgrade scripts need to login to database for example in mysql. using source command pointing to DB Scripts.
So Now Login to MySQL Console.
6. Run Final Patch iiq patch 7.3p2 Command in WEB-INF/bin folder to data upgrade post release.
Note : Sometimes Error comes as Patch could not be found
for this Error need to check if jar extract command is not executed successfully
jar -xvf filename.jar -----------> failed
this extraction is not done properly and where this patch file exists after extraction.
WEB-INF/Config/Patch folder
Verify the Patch : using iiq console about command
