Changes between Version 17 and Version 18 of Clients
- Timestamp:
- Dec 18, 2015, 10:17:18 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Clients
v17 v18 95 95 96 96 == rview (deprecated) == 97 rview is a de sktop visualization client component of rasdaman, that communicates with rasdaman via RPC, so rpcbind/portmapper should be installed and running in order to use rview.97 rview is a deprecated desktop visualization client of rasdaman. It is deprecated as it uses an insecure, soon-to-be-replaced client/server protocol based on RPCs. For building clients use [http://rasdaman.org/wiki/Clients one of the Web client or the raswct library] instead. 98 98 99 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. 99 Caveat: This client is fixed to RPC as client/server protocol, hence (i) rpcbind/portmapper must be installed and running and (ii) at least one rasdaman server process using RPC must be up and running; see the rasdaman Installation Guide for details on this. 100 100 101 To start rpcbind in insecure mode: 101 Background: rview is deprecated and unmaintained. Reason is that the wxWindows library has changed so substantially that, despite severe ettempts, it was not possible to adapt the rview code; therefore, only the old binary remains available. In fact, there are strong reasons not to use rview: As highlighted, RPC is '''highly insecure''' and not recommended. Further, RPC communication is deprecated and will soon be replaced (together with HTTP and RNP) by rasnet. 102 103 If you have read the above and still wish to use rview, proceed as follows: start the rpcbind service has to be started in insecure mode (or rasdaman has to be started as root, which is strongly discouraged as well) in order for rview to be able to connect to rasdaman. 104 105 To start rpcbind in insecure mode, edit /etc/init.d/rpcbind (more recently: /etc/init/portmap.conf) and add '-i' to the OPTIONS variable. Start rpcbind. Restart rasdaman. Open rview with 102 106 {{{ 103 107 #!sh 104 # note that the service script location may vary among different Linux distributions105 editor /etc/init.d/rpcbind106 107 # or in recent Ubuntu's108 editor /etc/init/portmap.conf109 110 # then add '-i' to the OPTIONS variable111 }}}112 113 After the rpcbind is restarted, restart rasdaman and then rview can be opened with114 {{{115 #116 108 cd $RMANHOME/bin 117 109 ./rview 118 110 }}} 119 111 120 '''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. 112 == rasgeo (deprecated) == 121 113 114 rasgeo is a client component of petascope that is able to easily import data into rasdaman along with the geo-metadata into petascope, provided that the data can be read by GDAL. This has been now superceded by the [wiki:WCSTImportGuide wcst_import tool]. 122 115 116 To setup rasgeo its configuration file (`~/.rasdaman/rasconnect`) needs to be updated as needed: 117 {{{ 118 #!sh 119 # Example file: 120 ------------------------------------------------- 121 host=localhost 122 rasport=7001 123 pgport=5432 124 rasdbname=RASBASE 125 petadbname=petascopedb 126 127 # RASBASE login 128 rasuser=rasdaman 129 raspassword=rasdaman 130 131 # petascopedb login 132 petauser=petauser 133 petapassword=petapasswd 134 135 # for rasdaman 9.0 136 # rasdaman login 137 rasloginuser=rasadmin 138 rasloginpassword=rasadmin 139 ------------------------------------------------ 140 }}}