SailPoint IIQ 8.4p2 - MessageBusConfiguration.xml

Which IIQ version are you inquiring about?

8.4p2

Hello! I am working on installing the p2 patch to our 8.4 instance of IIQ. Previously, we installed the p4 patch to our 8.3 installation via Azure DevOps, which was pretty straightforward, but when trying to get 8.4 to p2, I’m seeing the below error message regarding the MessageBusConfiguration file when attempting to run the pipeline in ADO. This message wasn’t present before during previous pipelines, so I’m wondering if p2 removed the MessageBusConfiguration file, or at least removed the ‘brokerType’ entry?

Please share any images or screenshots, if relevant.

image

Please take a look at line 49 of that file. It looks like you are specifying a value which is not allowable. Can you provide the contents of the file (redacting anything private)?

1 Like

Here’s the entry as a whole (including line 49) from the MessageBusConfiguration file:

I assume that ‘BrokerType’ on 49 is what is upsetting ADO. Because the value type isn’t one of any number of expected types, we see the error.

My line of thinking was that since this would pass the validation check prior to adding the 8.4p2 jar file to our ADO repository that something with p2 changes/removed that entry from the file or removed the file entirely.

I unpacked the p2 jar but didn’t find anything obvious.

So the thing with 8.4p2 is that it removed the dependency to have an embedded broker. It will now utilizes task threads to populate your access history events. Since it looks like you were previously using the embedded, I think you can just ignore that file from your repo.

https://community.sailpoint.com/t5/Technical-White-Papers/IdentityIQ-8-4p2-Removal-of-ActiveMQ-for-Access-History-and/ta-p/261842

1 Like

Great! That was my main worry - if it was something I needed to keep around.

I appreciate the advice!

2 Likes

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