
7.2 Exporting State
In order to use the exporter, the Rhino SLEE must be available and ready to accept management commands. The exporter is
invoked using the
$RHINO_HOME/client/bin/rhino-export
shell script. The script requires at least one argument, which
is the name of the directory in which the export image will be written to. In addition, a number of optional command-line
arguments may be specified:
$ client/bin/rhino-export
Valid command line options are:
-h <host> - The hostname to connect to.
-p <port> - The port to connect to.
-u <username> - The user to authenticate as.
-w <password> - The password used for authentication.
-f - Removes the output directory if it exists.
<output-directory> - The destination directory for the export.
Usually, only the <output-directory> argument must be specified.
All other arguments will be read from ’client.properties’.
An example of using the exporter to output the current state of the SLEE to the
rhino_export
directory is shown below:
user@host:~/rhino/client/bin$ ./rhino-export ../../rhino_export
4 deployable units found to export
Establishing dependencies between deployable units...
Exporting file:lib/ocjainsip-1.2-ra.jar...
Exporting file:jars/sip-ac-location-service.jar...
Exporting file:jars/sip-registrar-service.jar...
Exporting file:jars/sip-proxy-service.jar...
Export complete
The exporter will create a new sub-directory specified as an argument, e.g.
rhino_export
and create all the files which are
deployed in the SLEE, and an Ant script called
build.xml
which can be used later to initiate the import process.
user@host:~/rhino$ cd rhino_export/
user@host:~/rhino/rhino_export$ ls -l
total 28
-rw------- 1 user group 4534 Apr 5 14:24 build.xml
-rw------- 1 user group 504 Apr 5 14:24 import.properties
drwx------ 2 user group 4096 Apr 5 14:24 profiles
-rw------- 1 user group 5667 Apr 5 14:24 rhino-ant-management.dtd
drwx------ 2 user group 4096 Apr 5 14:24 units
Open Cloud Rhino 1.4.3 Administration Manual v1.1 52
Comentarios a estos manuales