Installing Magic Software's new uniPaaS development studio is pretty smooth, the only gotcha I encountered is that there is no mention of the fact that if you are not using IIS and instead you are using Apache or Apache as part of the WAMP stack, you'll need to manually configure your httpd.conf file - simple enough.
Here's what you must add to httpd.conf - note that I installed into c:\magic\unipaas and you must make these aliases resolve to whatever you used as your install directory.
### Added for unipaas
ScriptAlias /uniScripts/ "C:/magic/unipaas/scripts/"
<Directory "C:/magic/unipaas/scripts/">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
Alias /uniRIACache/ "C:/magic/unipaas/RIACache/"
<Directory "C:/magic/unipaas/RIACache/">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>
Alias /uniRIAModules/ "C:/magic/unipaas/RIAModules/"
<Directory "C:/magic/unipaas/RIAModules/">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>
Alias /uniRIAProjects/ "C:/magic/unipaas/Projects/"
<Directory "C:/magic/unipaas/Projects/">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>
###
Finally, ensure the InternetDispatcherPath setting in Magic.ini is defined as follows:
InternetDispatcherPath = /uniScripts/mgrqcgi010.exe
Restart Apache after making those changes and you should be good to go. Welcome to the future of RIA development.
---
It's worth mentioning a useful utility that is documented if you find yourself with java issues in this interim period where RC deployment is using java
Assuming you have the uniRIAModules alias set-up as described above or as installed in an IIS environment, open Internet Explorer (!) and access
http://localhost/uniRIAModules/RCDeploymentAssistor.htm
and this should indicate the unipaas-worthiness of your current java install and prompt you to fix it where necessary
If you install to a machine other than your local one, use the server-name in place of localhost, you know the drill
If you have yet to install uniPaaS and don't have specific java requirements for other applications or development tools, I would suggest you install the latest JRE from www.java.com
---
One more thing...
Just walked someone through a fix to their set-up
A useful test, and a dependency, is that you have the requester set-up correctly, that you can, say, access something as simple as
http://localhost/uniScripts/mgrqcgi010.exe
and see the MBSOD (magic blue screen of death)
Here, it's a good thing, it proves the requester
is accessible correctly and RC depends on that.
So a combination of RCDeploymentAssistor, verifying the
requester is available, adding aliases to apache if need be
ought to see you just get it working.