SMART on FHIR apps for Information exchange (Apache config.)

I reached out to Gary Monger yesterday and asked him how he configured Apache for his SMART on FHIR demo?
See https://learning.intersystems.com/mod/page/view.php?id=2948.
Gary's response was for me to post my question on the Developer Community forum - so that other people can benefit from the answer.

This is what I asked Gary:

I'm after turning a local Health Share instance on my laptop into a SMART on FHIR server.

The *recording about doing all of this is excellent, however, I could do with some instructions on how you configured the Apache web server before running the Cache scripts.
*https://learning.intersystems.com/mod/page/view.php?id=2948

Therefore, before I put lots of effort into trying to figure out how to configure the web services before running the COS scripts - could you please give me any hints or tips before I attempt the install.

I'm running this version of HS:

Cache for Windows (x86-64) 2017.2.1 (Build 801U) Wed Dec 6 2017 09:07:51 EST [HealthShare Modules:Core:16.0.7241 + Linkage Engine:16.0.7241 + Patient Index:16.0.7241 + Provider Directory:15.0.7241 + Clinical Viewer:16.0.7241 + Active Analytics:16.0.7241]

I have already run the HS demo script:

http://localhost:57774/csp/docbook/DocBook.UI.Page.cls?KEY=HESUP_app_dem...

ZN "HSLIB"
do ##class(HS.Util.Installer).InstallDemo()

Plus the script that sets up the FHIR production:

zn "HSLIB"
do ##class(HS.Util.Installer).InstallFHIRServer("FHIRSERVER")

However, because of the unknowns as far as configuring the SSL stuff in Apache - I've held off running the rest of the COS code that you ran to install the rest of the software.

I have a Oracle Virtual Box VM environment that I can run openssl commands in - and my plan is to run these openssl commands to create the certs.
I've run these openssl commands in the past - and I'm hoping the openssl commands are similar to what you ran to configure your laptop before doing the recording.

openssl genrsa -out key.pem​
openssl req -new -key key.pem -out csr.pem
openssl x509 -req -days 9999 -in csr.pem -signkey key.pem -out cert.pem

I've also been told by that the server name in the certificate needs to match the server name - otherwise it won't work!

If you wouldn't mind sending me a copy of your stand alone csp app source code that you demonstrated in your recording - then that would be great as well.

Can you also tell me if Cache can be configured to support SMART backend-services?
See http://docs.smarthealthit.org/authorization/backend-services/.

Many Thanks,
-- Paul.