<\/li>\n<\/ul>\nDownload\u00a0<\/span>unzip<\/span>\u00a0so you can decompress the tarball.<\/span><\/p>\n\n- sudo apt-get install unzip<\/span><\/li>\n
- <\/li>\n<\/ul>\n
The downloaded tarball contains pre-compiled binary files that you need to run OrientDB on your system, so all you need to do now is unzip it.<\/span><\/p>\n\n- unzip orientdb-community-<\/span>2.2.16<\/span>.tar.gz<\/span><\/li>\n
- <\/li>\n<\/ul>\n
The files are extracted into a directory named\u00a0<\/span>orientdb-community-<\/span>2.2.16<\/span>. Now you need to move it into the\u00a0<\/span>\/opt<\/span>directory, renaming it to\u00a0<\/span>orientdb<\/span>\u00a0in the process.<\/span><\/p>\n\n- sudo mv ~\/orientdb-community-<\/span>2.2.16<\/span> \/opt\/orientdb<\/span><\/li>\n
- <\/li>\n<\/ul>\n
OrientDB is now installed. If you’re using a memory-constrained server, you can configure OrientDB to use less RAM in the next step. Otherwise, you can move on to Step 3 to start the server itself.<\/span><\/p>\nStep 2 \u2014 Configuring OrientDB to Use Less RAM (Optional)<\/span><\/p>\nBy default, the OrientDB daemon expects to have at least 2 GB of RAM available, and will fail to start if it finds less. You’ll see an error like this if you try to start it anyway:<\/span><\/p>\nOutput<\/span><\/p>\nubuntu-orientdb server.sh[1670]: Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000aaaa0000, 1431699456, 0) failed; error=’Cannot allocate memory’ (errno=12)<\/span><\/p>\nubuntu-orientdb server.sh[1670]: # There is insufficient memory for the Java Runtime Environment to continue.<\/span><\/p>\nThere’s one configuration change you can make that will let you get away with using a server with as little as 512 MB of RAM. It’s a function of a setting in the\u00a0<\/span>server.sh<\/span>\u00a0file, which can be changed so that the daemon can start with far less RAM.<\/span><\/p>\nOpen the file with\u00a0<\/span>nano<\/span>\u00a0or your favorite text editor.<\/span><\/p>\n\n- sudo nano \/opt\/orientdb\/bin\/server.sh<\/span><\/li>\n
- <\/li>\n<\/ul>\n
Then scroll to the section containing the chunk of code shown in this code block:<\/span><\/p>\n\/opt\/orientdb\/bin\/server.sh<\/span><\/p>\n. . .<\/span><\/p>\n# ORIENTDB memory options, default to 2GB of heap.<\/span><\/p>\n <\/p>\n
if [ -z “$ORIENTDB_OPTS_MEMORY” ] ; then<\/span><\/p>\n \u00a0\u00a0\u00a0ORIENTDB_OPTS_MEMORY=”-Xms2G -Xmx2G”<\/span><\/p>\nfi<\/span><\/p>\n. . .<\/span><\/p>\nThe values you need to change are\u00a0<\/span>Xms<\/span>\u00a0and\u00a0<\/span>Xmx<\/span>, which specify the initial and maximum memory allocation pool for the Java Virtual Machine. By default, they’re set to 2GB.<\/span><\/p>\nYou can set new values that are less than amount of RAM allocated to the server, but make sure\u00a0<\/span>Xms<\/span>\u00a0is at least 128 MB or OrientDB won’t start. For example, the values below set the initial and maximum amount of ram to 128MB and 256MB, respectively.<\/span><\/p>\n\/opt\/orientdb\/bin\/server.sh<\/span><\/p>\n# ORIENTDB memory options, default to 2GB of heap.<\/span><\/p>\n <\/p>\n
if [ -z “$ORIENTDB_OPTS_MEMORY” ] ; then<\/span><\/p>\n \u00a0\u00a0\u00a0ORIENTDB_OPTS_MEMORY=”-Xms<\/span>128m<\/span> -Xmx<\/span>256m<\/span>“<\/span><\/p>\nfi<\/span><\/p>\nSave and close the file. In the next step, you’ll start OrientDB.<\/span><\/p>\nStep 3 \u2014 Starting the Server<\/span><\/p>\nNow that the binary is in place and you’ve optionally configured the server to use less RAM, you can now start the server and connect to the console.<\/span><\/p>\nNavigate to the installation directory.<\/span><\/p>\n\n- cd \/opt\/orientdb<\/span><\/li>\n
- <\/li>\n<\/ul>\n
Then start the server.<\/span><\/p>\n\n- sudo bin\/server.sh<\/span><\/li>\n
- <\/li>\n<\/ul>\n
When starting the server for the first time, you’ll be prompted to specify a password for the\u00a0<\/span>root<\/b>\u00a0user account. This is an internal OrientDB account that will be used to access the server for things like OrientDB Studio, the web-based interface for managing OrientDB. If you don’t specify a password, one will be generated automatically. However, it’s best to specify one yourself, so do so when prompted.<\/span><\/p>\nPart of the output generated from starting the server tells you what ports the server and OrientDB Studio are listening on.<\/span><\/p>\nOutput<\/span><\/p>\n2017-02-04 19:13:21:306 INFO \u00a0Listening binary connections on 0.0.0.0:2424 (protocol v.36, socket=default) [OServerNetworkListener]<\/span><\/p>\n2017-02-04 19:13:21:310 INFO \u00a0Listening http connections on 0.0.0.0:2480 (protocol v.10, socket=default) [OServerNetworkListener]<\/span><\/p>\n. . .<\/span><\/p>\n2017-02-04 19:13:21:372 INFO \u00a0OrientDB Studio available at http:\/\/192.168.0.30:2480\/studio\/index.html [OServer]<\/span><\/p>\n2017-02-04 19:13:21:374 INFO \u00a0OrientDB Server is active v2.2.16 (build UNKNOWN@r98dbf8a2b8d43e4af09f1b12fa7ae9dfdbd23f26; 2017-02-02 07:01:26+0000). <\/span><\/p>\n[OServer]<\/span><\/p>\nWhen you see this, OrientDB is now running in your current terminal. Let’s confirm that the server is listening on the appropriate ports.<\/span><\/p>\nOpen a second terminal and connect to the same server via SSH.<\/span><\/p>\n\n- ssh <\/span>sammy<\/span>@<\/span>your_server_ip<\/span><\/li>\n
- <\/li>\n<\/ul>\n
Then, in that second terminal, confirm that the server is listening on ports\u00a0<\/span>2424<\/span>\u00a0(for binary connections) and\u00a0<\/span>2480<\/span>\u00a0(for HTTP connections) with the following command.<\/span><\/p>\n\n- sudo netstat -plunt | grep -i listen<\/span><\/li>\n
- <\/li>\n<\/ul>\n
The output should contain references to both port numbers, like this:<\/span><\/p>\nOutput<\/span><\/p>\ntcp \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a00 \u00a0\u00a0\u00a0\u00a0\u00a00 0.0.0.0:22 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a00.0.0.0:* \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0LISTEN \u00a0\u00a0\u00a0\u00a0\u00a01160\/sshd \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/span><\/p>\ntcp6 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a00 \u00a0\u00a0\u00a0\u00a0\u00a00 :::<\/span>2480<\/span> \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0:::* \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0LISTEN \u00a0\u00a0\u00a0\u00a0\u00a02758\/java \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/span><\/p>\ntcp6 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a00 \u00a0\u00a0\u00a0\u00a0\u00a00 :::22 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0:::* \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0LISTEN \u00a0\u00a0\u00a0\u00a0\u00a01160\/sshd \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/span><\/p>\ntcp6 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a00 \u00a0\u00a0\u00a0\u00a0\u00a00 :::<\/span>2424<\/span> \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0:::* \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0LISTEN \u00a0\u00a0\u00a0\u00a0\u00a02758\/java<\/span><\/p>\nNow that server is started and you’ve verified it’s running, you’ll connect to the OrientDB console in the second terminal next.<\/span><\/p>\nStep 4 \u2014 Connecting to the Console<\/span><\/p>\nThe OrientDB console is the command line interface for working with the application. To launch it, type:<\/span><\/p>\n\n- sudo \/opt\/orientdb\/bin\/console.sh<\/span><\/li>\n
- <\/li>\n<\/ul>\n
You will see the following:<\/span><\/p>\nOutput<\/span><\/p>\nOrientDB console v.2.2.16 (build UNKNOWN@r98dbf8a2b8d43e4af09f1b12fa7ae9dfdbd23f26; 2017-02-02 07:01:26+0000) www.orientdb.com<\/span><\/p>\nType ‘help’ to display all the supported commands.<\/span><\/p>\nInstalling extensions for GREMLIN language v.2.6.0<\/span><\/p>\n <\/p>\n
<\/p>\n
orientdb><\/span><\/p>\nNow, connect to the server instance. The password required is the one you specified when you first started the server in the previous step.<\/span><\/p>\n\n- connect remote:127.0.0.1 root <\/span>root-password<\/span><\/li>\n
- <\/li>\n<\/ul>\n
You’ll see this output if you successfully connect.<\/span><\/p>\nOutput<\/span><\/p>\nConnecting to remote Server instance [remote:127.0.0.1] with user ‘root’…OK<\/span><\/p>\norientdb {server=remote:127.0.0.1\/}><\/span><\/p>\nIf you don’t, double check that you entered the root password correctly and that OrientDB is still running in your first terminal.<\/span><\/p>\nWhen you’re ready, type\u00a0<\/span>exit<\/span>\u00a0in your second terminal to quit the OrientDB prompt.<\/span><\/p>\n\n- exit<\/span><\/li>\n
- <\/li>\n<\/ul>\n
You’ve just installed OrientDB, manually started it, and connected to it. This means OrientDB is working, but it also means you’ll need to start it manually anytime you reboot the server. In the next few steps, we’ll configure and set up OrientDB to run just like any other daemon on the server.<\/span><\/p>\nStep 5 \u2014 Configuring OrientDB as a Daemon<\/span><\/p>\nAt this point, OrientDB is installed, but it’s just a bunch of scripts on the server. In this step, we’ll configure it to run as a daemon on the system. That involves modifying the\u00a0<\/span>\/opt\/orientdb\/bin\/orientdb.sh<\/span>\u00a0script and the configuration file,\u00a0<\/span>\/opt\/orientdb\/config\/orientdb-server-config.xml<\/span>.<\/span><\/p>\nFirst, type\u00a0<\/span>