I totally agree with Warlin that it really depends on what you are trying to do and your current setup. My interpretation of your question is that you are trying to migrate your data / user settings to a new server / instance?

I would say to use the server migration guide as a starting point - but definitely test the process since you're crossing versions also which is beyond the scope of that documentation.

What format are you using for your key/cert? Generally, our docs are fairly clear about which format to use - though not always! We're working on it and if you notice something missing, please report that using the "Feedback" button on the right side of the docs page.)

https://docs.intersystems.com/healthconnectlatest/csp/docbook/DocBook.UI.Page.cls?KEY=GCGI_oper_config#GCGI_config_serv

In this case, the example we give is in pem format, not pkcs12. 

It's tough to say without knowing your config and what exactly was done. For the second error at least it seems reasonably clear what could be causing it, maybe that will help to resolve the first error as well? I'm not an Apache expert so take my personal advice with a grain of salt, I just know that many people have found Mark's article to be helpful.
 

https://stackoverflow.com/questions/24060620/error-starting-apache-httpd-configuration-error-more-than-one-mpm-loaded

Hi Scott,

Did you look at Web Servers for UNIX, Linux, and macOS? That page explains how to configure Apache to serve CSP files.

I'm not sure what you mean by calls to the management portal. If you have the standalone Apache / gateway set up appropriately, you can serve the portal through (presumably default) port 80, ex. go to http://<hostname>:80/csp/sys/UtilHome.csp, rather than attempting to use your private web server port.

Really the independent Apache is the main piece, you can consider the standalone web gateway to be a module on that Apache web server.

Hope that helps.