The installer has a few steps and it would be great to know the consequences of the choices you make and if things can be added and configured later. Such as Git Installation, what benefits, requirements etc. The Enable Admin for for the Editor and Admin API, i assume this is the system admin account but should it be the service account, what issues arise if you install as your admin account and run under another. There is not a link to a guide to review while you are installing.
Hello @decrabtree,
I would like to recommend you to take a look at the information documented on the webpage Installation - OL Connect Automate 1.0 Help.
Please feel free to reply to the current forum post if you have any remaining questions.
Hi Decrabtree,
Thanks for reaching out. Here are some clarifications:
Working with Projects/Git integration
The Git-based Project feature enables version control and supports collaboration across teams. It also streamlines promoting solutions through a DTAP pipeline. When projects are configured with Environment Variables, they become even easier to relocate, no need to modify flows or expose machine-specific paths or credentials when moving between environments as each environment will have it’s on env variable values.
Information on this topic will soon become available.
Enabling authentication for the Editor and Admin API
This option secures access to the flow editor and Admin API by requiring credentials. By default, these credentials are stored (encrypted) in the olca.settings.json file. Alternative authentication methods, like SAML, OAuth, or OIDC (e.g., Azure AD), are also supported and documented in our online help.
Configuring the application to run at system startup
The service can run under either a virtual service account or an existing Windows user account. By default, the installer configures a virtual service account named NT Service\OLConnect_Automate.
One the challenge you may face when running under a service account is using SSH for remote Git repositories, we experienced some challenges setting up and using SSH keys for that user, in those scenarios HTTPS+Private Access Token seems to be the better solution. Another item to validate for that user is filesystem permissions.
Some of this information is available in the installation guide included with the installer. Our online documentation is not yet linked directly from the installer, but we plan to add this in a future release. We will continue to expand and refine the documentation where needed, and your feedback is both welcome and valuable in helping us improve the product and its supporting materials.
Here is the link to the online documentation: OL Connect Automate Online Help
Erik