Incorporate configuration to Archi.ini file

[vinicius.jlantunes]

Hello all,

New forum member, long time user of Archi and Archimate.

I would like to make a suggestion to the team - can we add to the GUI / settings of the plugin a choice for local / private PKI?

I (as many others here I imagine) work in a corporate environment where IT manages several aspects of the machines we use as well as security settings of the network and etc.

We had issues using coArchi in the past that we could fix by following steps documented here - basically add a couple of lines to the .ini file.

What is inconvenient is that we do not have admin access to our machines per company policy, so changing the INI file requires elevated access with help from IT support. When we upgrade to a new version of Archi, the INI file  is reset and we have to do it again.

So having a way of changing these settings via the application / plugin configuration would help us (and I imagine others that operate in a similarly controlled enterprise IT environment).

Any thoughts? Anyone else with similar issues?

[Phil Beauvoir]

Hi,

it may be possible to expose some of these arguments such as "javax.net.ssl.trustStore" in a preference in coArchi that can then be initialised at plug-in startup. However, as we are now working on coArchi 2 we can look at this later in the dev cycle.

Perhaps you might want to consider creating a custom packaged version of Archi for internal distribution? See https://github.com/archimatetool/archi/wiki/How-to-create-a-packaged-version-of-Archi-(including-configuration-and-plugins) for more info.

Phil

[vinicius.jlantunes]

Ah that seems interesting, thanks! Might be a good idea for upgrading to Archi 5.5, we're currently using 5.4.

The packaging of software and making it available to installation in our PC's is tightly controlled where I work, so I will have to check if me giving them a "custom" packaged version is acceptable. Hopefully I don't run into red tape!

Thanks!