| 76 | |
| 77 | == rview == |
| 78 | rview is a desktop visualization client component of rasdaman, that communicates with rasdaman via RPC, so rpcbind/portmapper should be installed and running in order to use rview. |
| 79 | |
| 80 | The rpcbind service has to be started in insecure mode, or rasdaman has to be started as root, in order for rview to be able to connect to rasdaman. |
| 81 | |
| 82 | To start rpcbind in insecure mode: |
| 83 | {{{ |
| 84 | #!sh |
| 85 | # note that the service script location may vary among different Linux distributions |
| 86 | editor /etc/init.d/rpcbind |
| 87 | |
| 88 | # or in recent Ubuntu's |
| 89 | editor /etc/init/portmap.conf |
| 90 | |
| 91 | # then add '-i' to the OPTIONS variable |
| 92 | }}} |
| 93 | |
| 94 | After the rpcbind is restarted, restart rasdaman and then rview can be opened with |
| 95 | {{{ |
| 96 | cd $RMANHOME/bin |
| 97 | ./rview |
| 98 | }}} |
| 99 | |
| 100 | '''Important note:''' Rview is deprecated and unmaintained. For building clients use [http://rasdaman.org/wiki/Clients one of the Web client or the raswct library] instead. In fact, there are strong reasons not to use rview: As highlighted using the RPC communication protocol is highly insecure and not recommended. Further, RPC communication is deprecated and will soon be replaced (together with HTTP and RNP) by a new, faster protocol. |
| 101 | |
| 102 | |