Servers are being removed from Driver Set while installing Identity Application 4.8
The servers are being removed from Driver Set while installing the new Identity Application 4.8. Only main server that Designer Headless deploys drivers remains in the Driver Set.
This may be known issue but I can't find any resolution to rectify it.
We have 30+ drivers running on other server and we can't have downtime while we add the servers back to Driver Set and start them again. How to prevent or resolve this?
Headless designer from experience is used only to deploy the bundled drivers roles and resources driver, user application, DCS and MSG.
Is this a customer without identity apps or reporting previously installed? And you want to add these?
Normally you should be picking upgrade rather than install if you have such components in your environment.
Just to share our experience. We had similar behavior when we upgraded to IDM 4.7.3 from previous versions of IDM, it happened always when we installed "Reporting" RPT application for Identity Application
Deployed drivers manually instead.
Know that is probably not supported. But this sort of stuff should “just work”.
Just curious what is the headless designer? -- i am already thinking if this is scriptable designer then one can build "CI/CD" pipeline for driver automated deployment to multiple enviorenenments using headless desinger scripts.
It is a commandline version of Designer used to deploy driverset and drivers during installation/upgrade.
It was at some point documented, and supposed to be used by end-users. But due to some problems, that idea was abandoned. And now it's an undermentioned featured only used during installation/upgrade.
That's fantastic, we should create feature request to make it available for automated deployments of drivers, this would improve
- scripting naming standards for drivers to different env before their deployments
- settings env specific configuration for drivers for each env.
Netiq should invest into this for clients who has high change rate for their developments with governance and change control processes requirements.
where could one find previous documentation of this?
There is a Brainshare presentation about it, and I think it's in the 4.5 or 4.0.2 documentation where you can find some information about it.
But the use is as far as I know 100% unsupported, and you'll face the same problem as described in this thread ... loos of drivers in your driver set.
I'd just be happy if we could have selectable GCV's depending on environment (without having to add code), that would satisfy me.
You need to have access from IDApps server to IDVault on port 389. Then it works.
Same goes from Designer to IDVault, you need 389 communication otherwise you get alot of issues, specially on Designer 4.8.0. 4.8.1 still has this issue, one is that when you import from IDVault you only get the primary IDVault server.
This is one annoying issue with 4.8.x.
I have experienced this issue with IDM 4.7 and 4.8 with clients who have IDM and wanted to implement Identity App.
The workaround like using port 389 or commenting out Designer in the configuration script may be the only two options.