The standalone deployment engine is implemented as a set of Java
libraries and is multi-platform.
The standalone deployment engine uses RMI, which is disabled in SkyVault by default.
CAUTION:
If you enable RMI, ensure that you understand the risks and restrict
use of RMI to trusted hosts.
-
To enable RMI, set the following parameters in your
SkyVault-global.properties file:
SkyVault.jmx.connector.enabled=true avm.rmi.service.enabled=true avmsync.rmi.service.enabled=true authentication.rmi.service.enabled=true repo.rmi.service.enabled=true action.rmi.service.enabled=true deployment.rmi.service.enabled=true monitor.rmi.service.enabled=true email.rmi.service.enabled=true
-
(Windows) To start the standalone deployment engine:
- Open a command prompt, and run the deploy_start script, or
- Select Start Menu > All Programs > SkyVault Standalone Deployment Receiver > Start SkyVault Standalone Deployment Receiver.
The Start menu action is available if you have used the deployment installer to install the Standalone Deployment Engine. This action is calling the deploy_start.bat script.
It is also possible to install the standalone deployment engine as a Windows service, which can automatically start when Windows starts.
-
(Linux) To start the standalone deployment engine, open a command
prompt and run the deploy_start.sh script.
Note: The default shell for this script is sh. You can edit the SkyVault.sh file to change to your preferred shell. For example, change the #!/bin/sh line to #!/bin/bash.
When deploying to a deployment engine running on a multi-NIC
system, it may be necessary to bind the RMI registry to a particular IP
address. To do this, add the following to the Java command in
deploy_start.sh or
deploy_start.bat:
-Djava.rmi.server.hostname=x.x.x.x
Where x.x.x.x is the IP address assigned to the NIC to which you want to bind.