The UI, community elements and workflow are very much in flux at the moment - things are changing on a weekly basis as the platform gets refined to be more intuitive and to make it easier for people to connect and get their questions answered.  If you have time to play around and provide feedback, feel free!  But if you don't (and it's understandable) then you can continue to hang out in the Google Groups.  We won't be moving content and users over to the Developer Community until product management feel like it would be an advantageous move and that people will get all of the value that they get from the Google Groups.  

Note that there is a subcommunity which is specifically for providing feedback on the Developer Community so if you see something that you think could be improved, please make a post about it!

Scott - have you looked at %Installer?  That should be the first place that you start for trying to create a deployment from scratch.  This is how Ensemble, HealthShare and TrakCare instances get initialized by the installer and I know a lot of customers have used this with great success.

Also, the Enterprise Manager which is coming out in 2016.2 may be of interest in this area as well.


You might be running into some security issues (check the audit DB to confirm).  Or, you might not have it working because you have "Lock CSP Name" set to "Yes" in one of the web applications (ref: http://docs.intersystems.com/cache20152/csp/docbook/DocBook.UI.Page.cls?KEY=GCSP_config#GCSP_lockcsp).

I just did a quick test as follows in my 2015.1 instance:

1) Created a SAMPLES2 namespace with new SAMPLES2 DB

2) Package mapped "csp" from SAMPLES namespace to SAMPLES2 namespace

3) Edited /csp/samples2 web application as follows:

- added Unauthenticated

- added %DB_SAMPLES Application Role

- Unchecked "Lock CSP Name" AND "Autocompile" (this should be done in both /csp/samples and /csp/samples2)

- pointed "CSP Files Physical Path" to c:\intersystems\e20151\csp\samples\ 

After this I was then able to see /csp/samples2/form.csp (although with errors because I didn't map the Samples.* package to the Samples Namespace).

So it appears to work - you just need to figure out which of the above pieces you missed :)



I asume since you used MyPage.csp in your example you are doing tag-based and not class-based CSP development?   

Remember that tag-based .csp files compile into classes within the namespace (by default these are csp.* classes).  So you could package-map csp.* (or whatever package you configure your CSP pages to compile into) from your Readonly namespace to the XYZ namespace, and then you could point the /csp/xyz application to the source directory holding the csp pages.  I think this is likely to do what you want (although I haven't tested it).