IIQ Properties setup for separate instance of Database server for MSSQL

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

Version 8.3

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

Hello,
We are trying to change the instance of database server from A to B. We were previously connected to Something like this:
dataSource.url=jdbc:sqlserver://serverName.nonprod.domain:1433;databaseName=identityiq;trustServerCertificate=true;encrypt=false;
dataSource.driverClassName=com.microsoft.sqlserver.jdbc.SQLServerDriver
sessionFactory.hibernateProperties.hibernate.dialect=sailpoint.persistence.SQLServerUnicodeDialect
scheduler.quartzProperties.org.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobstore.MSSQLDelegate
scheduler.quartzProperties.org.quartz.jobStore.selectWithLockSQL=SELECT * FROM {0}LOCKS UPDLOCK WHERE LOCK_NAME = ?

We have now setup a database on the same server on seperate instance. The setup on IIQ.properties is:
dataSource.url=jdbc:sqlserver://serverName.nonprod.domainName\\IQTWO:1433;databaseName=identityiq;trustServerCertificate=true;encrypt=false;
dataSource.driverClassName=com.microsoft.sqlserver.jdbc.SQLServerDriver
sessionFactory.hibernateProperties.hibernate.dialect=sailpoint.persistence.SQLServerUnicodeDialect
scheduler.quartzProperties.org.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobstore.MSSQLDelegate
scheduler.quartzProperties.org.quartz.jobStore.selectWithLockSQL=SELECT * FROM {0}LOCKS UPDLOCK WHERE LOCK_NAME = ?

The problem is SailPoint is connecting to the old database instance and not to the new one. Even with the new changes on IIQ.properties file, we have noticed that SailPoint is trying to connect to the serverName.nonprod.domainName and not to the instance seperated by //IQTWO. Is there any other places we need to make the change? or any format? I have tried mixture of format and doesn’t seem to work. Do we need to clear cache or any other settings need change? We have checked and firewall is open on new instance and the credentials are correct as well. Note the new instance is serverName/IQTWO which is why we have separated it with two //. IQConsole says it is trying to connect to the new instance but on database side we can see that it is not trying login at all. Login is being tried on old instance on real time database trace.

2

If you have multiple servers, then make sure you make the change in all the servers and restart the application servers. Other than that, iiq.properties is the only place where you need to make the change.

3

We only have 1 server. Is it to do with cache or memory as it is trying to connect to the parent server and not the instance?

4

restarting should work, so if you haven’t done that already. Also, what do you see when you connect to iiq console and run about command, do you see updated database information?

5

Looks like it was a port issue. The dynamic port was different for new instance. The issue seems to be resolved.

6

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