There are several ways to ride rasdaman - installing from source, installing prefabricated RPM packages, or downloading a preconfectioned Virtual Machine. Make your choice below!
Any questions on installation or operation? Use the rasdaman mailing lists!
Alternative 1: Source Code
Download and compile rasdaman. This is the most flexible alternative; you are guided you through the compilation steps, hence it requires just minimal system administration skills.
Alternative 2: Packages
Alternative 3: Virtual Machine
By downloading a Virtual Machine (VM) you get a fully configured system with rasdaman installed and ready to run. This alternative does not require any system administration skills other than starting the VM and working with the rasdaman services, e.g., via the OGC standards based geo service interface.
There are several security measures available, which should be considered seriously. Among them are the access right mechanisms found in Tomcat, web server, rasdaman, and PostgreSQL. We highly recommend to make use of these.
For Tomcat, Web server, and PostgreSQL we refer to the pertaining documentation. For rasdaman, we recommend to change the default user passwords in rasdaman (rasguest/rasguest for read-only access, rasadmin/rasadmin for read-write and administrator access) to not run into the Oracle "Scott/tiger" trap. Even better, add separate, private users. For all these actions, the rascontrol utility is your friend (cf. installation guide). Along the same line we recommend to configure petascope access to rasdaman using a read-only login which is different from the default one provided in the petascope.properties file.
The servlet is safe against SQL injection attacks - we are not aware of any means for the user to send custom queries to the PostgreSQL server or the rasdaman server. XSRF and XSS represent no danger to the service because there is no user generated content available.
Once the rasdaman service is up and running you may be interested in clients available.