Hi,
This is a follow up to the question I asked here... https://community.dataminer.services/question/unattended-installer/
I'm trying to automate the deployment of Dataminer, using Ansible. I've got 28 machines to build very soon, so trying to make my life easier!
I can already build the Cassandra and Opensearch Database clusters with no issue. My question is specifically about deploying the DMA
Using the installer version 10.2 in unattended I can set the DMA ID, but it doesn't support configuring the Database. Using the 10.4 installer, I can run it in unattended mode, but none of the configuration in InstallConfiguration.xml is used. I found manually running the 10.4 installer also doesn't give me an option to specify DMA ID's, just goes straight to the cloud configuration, which we won't be able to use at the time of building, but will be looking to deploy soon after.
So...
1.) Can I use any form of unattended installation, where by I can specify the DMA ID and the Database cluster details?
2.) How do I manually enter the details in the 10.4 installer?
3.) Is there anyway to make the 10.2 installer use the 10.5 install package?
We'll be using 10.5.x Dataminer, so I don't really want to jump strainght from 10.2 to 10.5 if I can avoid it.
Thanks
Answering my own question.....
My process uses Ansible to install the pre-requisites and Dataminer onto an exting, new Windows Server 2025 machine. The install target is already joined to Active Directory, and had any customisations applied as per corporate policy
1.) Yes I can. Dataminer Install 10.4 with Ansible works, but setting the DMA ID and database details has to be done after the installer completes
2.) You can't... But, you can apply changes to the Dataminer.xml and db.xml files once the installer has completed, as you would if switching to a perpetual licence. See https://docs.dataminer.services/dataminer/Getting_started/Installing_a_DMA/Using_the_installer/Switching_from_subscription_mode_to_perpetual_license.html
3.) No idea!
Edit: - You will need a sensible Security.xml file, otherwise you won't be able to log in to your newly deployed system