Sailpoint IIQ 8.3p4 Upgrade to 8.4

Which IIQ version are you inquiring about?

8.3p4

Share all details about your problem, including any error messages you may have received.

We’re planning to perform an upgrade from 8.3p4 to 8.4. I’ve read the installation/upgrade guide and it seems pretty straightforward, but I am a bit lost on where we would re-apply our customizations (i.e., applications, workflows, rules, etc.). I believe those are in a custom folder (identityiq > web-inf > config > custom), but as the identityiq folder is deleted as part of the process, would I simply drop in the custom folder from backup and run the import customizations to re-import everything after installing the upgrade?

We recently upgrade to 8.3 from 8.1 (recently being two years ago), but I was left out of the majority of that upgrade and I can’t find any kind of step-by-step documentation.

Hi @RSanders,

in every case you delete and reinstall the identityiq folder you must save you customziation(logs, css, etc…). If you have save in a project and you use ssb you can re-deploy your pj, but you need to save everything you have of UI customization

An upgrade/patch upgrade consists of 2 parts:

  • Updated files
  • Updated objects in the database
    Both parts will overwrite all Out-Of-The-Box (OOTB) files and objects, but not the additional objects.

So if one follows the rules of customization of IdentityIQ (IIQ) an upgrade following the Installation Guide will generate no issue.
During the upgrade the standard objects in the database (like applicaties, identities, bundles) will be updated when needed (additional/changed attributes) for the newer IIQ version.

Before upgrading you must read the upgrade considerations section in the Installation Guide.

My advice: Always use the SSB for customizations and maintaining your IIQ environment(s).
All customizations will be (re-)deployed when building using the SSB.

– Remold


Rules of customization of IdentityIQ
One of the most important rules is to not change any OOTB objects, but copy them before modifying and update the reference to the objects.

For example:
When changing the access request to configure manager approval, copy the ‘LCM Provisioning’-Workflow, set the manager approval in this new workflow and update the Workflow for Request Access (Gear->Lifecycle Manager->Business Processes->Request Access)

1 Like

So, I read the install guide a little more, and there’s actually some info in there regarding customizations, so I think I have that part figured out (custom apps, iiq.properties, etc.).
We have a SandBox environment I’m performing the upgrade on, and I think things are going fairly well, except I’m seeing a couple of errors I just can’t pin down that are preventing the application from starting (as well as console):

Disregard the name of the identityiq folder - it was a leftover from when outside consultants performed an upgrade from 8.1 to 8.3. We repurposed it to serve as a SandBox environment.
image
I’m sure there’s a log4j config or properties file that we had made changes to that could be causing this error. I’ve compared files between what came with 8.4 and what we have currently in our 8.3p4 install, but I’m seeing no significant differences.

image
I can’t even wager a guess as to where this is coming from. This seems to be preventing the application from running, including console.

And insight would be appreciated! I know I’m close - just have to figure out these two errors and I think we’ll be in business.

Scratch the first part - the log4j2.properties file had a line in there where level = debug,file. Changing it to debug resolved the problem.

And scratch the second part. This was due to the htmlSanitizerPolicies in the SystemConfiguration file. For some reason, the DB had the old config, but modifying directly from the debug page solved the issue.

For anyone else that encounters this, it seems that STYLE_ELEMENTS is not a valid sanitizer policy in 8.4, so if you’re upgrading from 8.3 to 8.4, make sure to remove that from your system configuration file. It doesn’t stop the application from running, but it’s a good idea to update it (assuming, of course, you have a custom system config file).

I have a similar situation: We are upgrading from 8.3p1 to 8.4p2 using the SSB.
Will the following sequence work?

  1. Put the identityiq8.4.zip in the base/ga directory,
  2. Put identityiq-8.4p2.jar in the base/patch directory,
  3. Run the appropriate database scripts, and
  4. Deploy the SSB to our application server

I played it a bit safe and first installed 8.4, verified the install, then installed p2, but yes, 8.4.zip went into base/ga, and p2 went into base/patch.