- Virtuoso Universal Server
- Virtuoso Sponger Middleware & Cartridges (extensible RDFizer covering 30+ different data formats)
- OpenLink Data Spaces (ODS)
- OpenLink Ajax Toolkit (OAT)
- 3rd party PHP applications (WordPress , MediaWiki, phpBB, and Drupal )
- Register for an Amazon Web Services (AWS) account.
- New AWS accounts are automatically signed up for the Amazon S3 and EC2 Web Service. If you already had an AWS account, you may now need to manually sign up for these services.
Follow the steps below to set up and launch your Virtuoso EC2 AMI instance.
- Subscribe to the Virtuoso Universal Server (Cloud Edition) Amazon DevPay service to activate the Virtuoso AMI on your account.
- After successful subscription the DevPay service redirects users back to this page to continue the AMI instantiation as detailed in step 4.
activation key(which is only valid for 60mins) is passed back as part of the redirect URL for use by AWS in instantiating the AMI. Thus should the browser session be shutdown for any reason or the activation key has expired, a new one needs to be generated.
- This can be done from the
Application Activationtab of the Virtuoso Universal Server (Cloud Edition) AMI Application page.
- Then select the
Go to Applicationlinks to get the new key and once again be redirected to this page with the product code and activation key passed in the URL and continue the instantiation as detailed in step 4.
- This can be done from the
- Open the AWS Management Console
From here, you can see a dashboard showing any current instances you may have running and a menu of various areas to control (instances, AMIs, etc.).
You will need to create a new security group (firewall configuration) for the Virtuoso AMI.
- Click on Security Groups at the bottom of the left menu. By default, there is one group called default visible.
- Create a new security group (here called openlink) and, in addition to the default port
22/tcp(SSH), allow connections to port
80/tcp(HTTP) and port
8890/tcp(used by Virtuoso).
- Save it and return to the dashboard.
Now we need to create an instance of the image.
- From the Console, select Launch Instances.
- You need to choose an AMI.
In the Community AMIs tab, type virtuoso to see the relevant images published by OpenLink —
- Virtuoso Release 6 AMIs
Edition ID Manifest file 32-bit
- Virtuoso Release 5 AMIs
Edition ID Manifest file 64-bit
- Virtuoso Release 6 AMIs
- Choose whichever image you prefer, 64-bit (x86_64) or 32-bit (i686) and press Select.
- Enter the Number of Instances (normally 1).
- Select the Instance Type.
- Choose a key-pair or create a new one for the purpose. This will be used as an SSH key to access your instance later.
- Select the openlink security group created earlier.
- Click the Launch button.
You will see a status page saying your instances are in the process of launching, and the next time you visit the dashboard there will be an appropriate instance visible.
OpenLink Virtuoso Cloud Edition is based on a Linux Fedora and Centos Core linux images which you should also update regularly and before using your Virtuoso instance. This can be done as follows:
- Locate the key created above and run the command —
chmod 600 MyKeyPair.pem
- Connect to the EC2 AMI Server with the command —
ssh -i MyKeyPair.pem root@your-ec2-instance-cname
- The Virtuoso EC2 AMI installation is located in
/opt/virtuoso. From this location first run the following commands to shutdown the Virtuoso server instance —
. ./virtuoso-environment.sh virtuoso-stop.sh oplmgr +stop
Update the Virtuoso EC2 AMI installation to the latest OS and Virtuoso versions.
Exact sequence depends on which Virtuoso Release you are running --
Virtuoso Release 5
AMI users must run the following command sequence to first update the OpenLink License Manager (
oplmgr) and license file (
virtuoso.lic), and then update the OS and Virtuoso. DO NOT use this sequence with any other Virtuoso Release! —
yum update oplmgr virtuoso-ami-init yum update
Virtuoso Release 6
AMI users must run the following command sequence to first remove the existing Virtuoso database file (
virtuoso.db) and transaction log file (
virtuoso.trx) , and then update the OS and Virtuoso. DO NOT use this sequence with any other Virtuoso Release! —
cd database rm virtuoso.db rm virtuoso.trx yum update
AMI users with Virtuoso Releases not listed above
should simply update the Virtuoso EC2 AMI installation to the latest OS and Virtuoso versions with the following command.
DO NOT use this sequence with any Virtuoso Release listed above! —
- Virtuoso Release 5 AMI users must run the following command sequence to first update the OpenLink License Manager (
- Edit the Virtuoso configuration file
/opt/virtuoso/database/virtuoso.iniand set the
DefaultHostparameter in the
your-ec2-instance-cname(or whatever external cname the instance will be configured to use). This is required for the correct hostname to be picked up when using the ODS and other applications —
[URIQA] DynamicLocal = 1 DefaultHost = your-ec2-instance-cname:80
- Edit the Virtuoso configuration file
/opt/virtuoso/database/virtuoso.iniand add the line
Load8 = plain, qrcodeto the
[Plugins]section to enable qrcode support in the Virtuoso Server —
[URIQA] [Plugins] LoadPath = ../hosting Load1 = plain, wikiv Load2 = plain, mediawiki Load3 = plain, creolewiki Load4 = plain, im Load5 = plain, wbxml2 Load6 = attach, libphp5.so Load7 = Hosting, hosting_php.so Load8 = plain, qrcode
- The Virtuoso server can then be restarted with the command —
A complete run should look something like this —
$ chmod 600 MyKeyPair.pem $ ssh -i MyKeyPair.pem firstname.lastname@example.org The authenticity of host 'ec2-67-202-24-222.compute-1.amazonaws.com (126.96.36.199)' can't be established. RSA key fingerprint is 58:ae:0b:e7:a6:d8:d0:00:4f:ca:22:53:42:d5:e5:22. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'ec2-67-202-24-222.compute-1.amazonaws.com,188.8.131.52' (RSA) to the list of known hosts. -bash-3.1# cd /opt/virtuoso/ -bash-3.1# ls bin hosting lib virtuoso-environment.csh vsp database install vad virtuoso-environment.sh -bash-3.1# . ./virtuoso-environment.sh -bash-3.1# virtuoso-stop.sh Shutting down Virtuoso instance in [database] -bash-3.1# yum update Loading "installonlyn" plugin Setting up Update Process Setting up repositories core 100% |=========================| 1.1 kB 00:00 extras 100% |=========================| 1.1 kB 00:00 updates 100% |=========================| 1.2 kB 00:00 virtuoso 100% |=========================| 951 B 00:00 Reading repository metadata in from local files primary.xml.gz 100% |=========================| 1.8 MB 00:01 extras : ################################################## 5699/5699 . . . -bash-3.1# vi database/virtuoso.ini -bash-3.1# virtuoso-start.sh Starting Virtuoso instance in [database] -bash-3.1#
While you can, and should, keep the whole operating system up to date with this method, you can also upgrade only the Virtuoso components with the command —
yum update --disablerepo=* --enablerepo=virtuoso
Virtuoso has two system users,
dba (for SQL/relational/system-admin tasks) and
dav (for WebDAV and ODS), with passwords set by default the same as their usernames.
On any live server, it is essential to change these two passwords to something random of your own choosing.
To this end,
- Open the location http://your-ec2-instance/conductor/ in a web browser.
- Log in as dba/dba
- Select System Admin from the menu and then User Accounts from the second level menu.
- Click Edit beside the dba user.
- Enter replacement passwords in both boxes and press the Save button at the bottom to return to the user-list.
Additional VAD application packages are available for the Virtuoso
demo database, documentation and tutorials which can be installed from a
yum install as follows:
[root@domU-12-31-39-00-00-61 virtuoso]# yum install virtuoso-vad-doc virtuoso-vad-demo virtuoso-vad-tutorial Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * extras: mirror.trouble-free.net * updates: mirrors.cmich.edu * base: centos.mbni.med.umich.edu * addons: mirror.skiplink.com Setting up Install Process Parsing package install arguments Resolving Dependencies --> Running transaction check ---> Package virtuoso-vad-doc.x86_64 0:6.0.3123-1.20091016 set to be updated ---> Package virtuoso-vad-demo.x86_64 0:6.0.3123-1.20091016 set to be updated ---> Package virtuoso-vad-tutorial.x86_64 0:6.0.3123-1.20091016 set to be updated --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: virtuoso-vad-doc x86_64 6.0.3123-1.20091016 virtuoso 64 M virtuoso-vad-demo x86_64 6.0.3123-1.20091016 virtuoso 9.1 M virtuoso-vad-tutorial x86_64 6.0.3123-1.20091016 virtuoso 5.2 M Transaction Summary ================================================================================ Install 3 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 69 M Is this ok [y/N]: y Downloading Packages: (1/3): virtuoso-vad-tutorial-6.0.3123-1.20091016.x86_64. | 5.2 MB 00:01 (2/3): virtuoso-vad-demo-6.0.3123-1.20091016.x86_64.rpm | 9.1 MB 00:00 (3/3): virtuoso-vad-doc-6.0.3123-1.20091016.x86_64.rpm | 64 MB 00:04 -------------------------------------------------------------------------------- Total 12 MB/s | 69 MB 00:05 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing : virtuoso-vad-doc [1/3] Installing : virtuoso-vad-demo [2/3] Installing : virtuoso-vad-tutorial [3/3] Installed: virtuoso-vad-doc.x86_64 0:6.0.3123-1.20091016 virtuoso-vad-demo.x86_64 0:6.0.3123-1.20091016 virtuoso-vad-tutorial.x86_64 0:6.0.3123-1.20091016 Complete! [root@domU-12-31-39-00-00-61 virtuoso]#
These VAD packages can then be installed by the Virtuoso Conductor UI from the
System Admin->Packages tab where they will now be listed as available to install.
Using OpenLink Ajax Toolkit (OAT) Applications from your Virtuoso EC2 AMI instance
Install the OAT VAD package via the Admin UI, and then you can use the URL patterns below within your browser:
|Entire OAT Demo Collection||
|OpenLink Data Explorer||
|Interactive SPARQL Query Builder (iSPARQL)||
|SQL Query Builder (iSQL)||
|Forms Builder (for building Meshups based on RDF, SQL, or Web Services Data Sources)||
|SQL DB Schema Designer (a Visual SQL-RDF Mapper is also on its way!)||
|To view the OAT Tree (there are some experimental demos that are not listed in the main demo app)||
license expiration errors be encountered, which may occur due to changes in AMI components, please make a
ssh connection to the Linux virtual machine and perform the following steps to obtain an updated license:
ssh -i MyKeyPair.pem root@your-ec2-instance-cname . ./virtuoso-environment.sh virtuoso-stop.sh yum update virtuoso-ami-init virtuoso-start.sh
- OpenLink Data Spaces Installation
- Pre-configured & Pre-loaded Virtuoso instances (DBpedia, BBC Music & Programmes etc.)
- Creating Your Own Neurocommons Instance
- Creating Your Own Bio2RDF Instance
- Creating Your Own MusicBrainz Instance
- Backup Your Virtuoso EC2 AMI to S3
- Amazon Web Services Simple Monthly Cost Calculator
- Configure your Virtuoso EC2 AMI for use with Amazon Elastic Block Storage (EBS)
- Safeguarding your Virtuoso-hosted SPARQL Endpoint
- SPARQL Endpoint Protection Methods Collection
- Virtuoso documentation
- Virtuoso Tips and Tricks Collection
- SPARUL over SPARQL using the http://cname:port/sparql-auth endpoint
- Virtuoso Authentication Server UI
- Manage a SPARQL-WebID based Endpoint
- Configure Virtuoso instance as an X.509 Certificate Authority and HTTPS listener
- Configure Virtuoso+ODS instance as an X.509 Certificate Authority and HTTPS listener
- WebID Protocol Support in OpenLink Data Spaces.
- Manage ODS Datadspaces Objects WebID Access Control Lists (ACLs):
- ODS Briefcase WebID based ACL Guide
- ODS Feed Manager WebID based ACL Guide
- ODS Calendar WebID based ACL Guide
- ODS Bookmark Manager WebID based ACL Guide
- ODS Addressbook WebID based ACL Guide
- Guide for Set up a X.509 certificate issuer and HTTPS listener and generate ODS user certificates.
- Setting up PubSubHub in ODS
- PubSubHubBub Demo Client Example
- Feed subscription via PubSubHub protocol Example
- Setting Up PubSubHub to use WebID Protocol or IP based control lists
- CA Keys Import using Conductor
- Generate an X.509 Certificate hosted WebID Guide
- Generate an X.509 Certificate (with a WebID watermark) to be managed by host operating system keystore
- Generate an X.509 Certificate (with a WebID watermark) to be managed by a browser-based keystore
- Using Virtuoso's WebID Verification Proxy Service with a WebID-bearing X.509 certificate
- Using Virtuoso's WebID Identity Provider (IdP) Proxy Service with an X.509 certificate
- ODS Briefcase WebID Protocol Share File Guide
- WebID Protocol Specification
- Test WebID Protocol Certificate page
- WebID Protocol Certificate Generation page