Difference between revisions of "Category:NCBO Virtual Appliance"

From NCBO Wiki
Jump to navigation Jump to search
(added Migrated category)
 
(88 intermediate revisions by 5 users not shown)
Line 1: Line 1:
The NCBO Virtual Appliance image contains a pre-installed, pre-configured version of commonly-used NCBO software running on a Linux operating system. The image was created using VMWare and is available for download by contacting support@bioontology.org.
+
[[Category:NCBO Virtual Appliance]]
 +
[[Category:Migrated to GitHub]]
  
The following software is included on the image:
+
'''''Most of this content has been moved!''''' Please find the new content for the 3.0 version of the Virtual Appliance at our new '''[https://ontoportal.github.io/administration/ OntoPortal Virtual Appliance Administration pages]'''.
* BioPortal Ontology Services (BioPortal Core)
 
* BioPortal Web User Interface (including ontology visualization, Flex widgets, Annotator and Resource Index UIs)
 
* BioPortal Admin (a UI for administering BioPortal Ontology Services)
 
* Annotator
 
* Resource Index
 
  
Please see below for how-to documentation for managing the software and running data population for Annotator and Resource Index.
+
== OntoPortal Virtual Appliance Version 3.0 is here! ==
  
== Getting Started ==
+
We are pleased to softly announce our soft release of the OntoPortal Virtual Appliance version 3.0 (3.0.1, to be precise).
* The download is provided as a tar archive containing several files. One of these is an Open Virtualization Format (OVF) file that may need to be converted to work in your environment.
 
** You can use [http://communities.vmware.com/community/vmtn/vsphere/automationtools/ovf VMWare's ovftool] to convert the appliance to work with your virtualization software. For example, to convert the appliance for use in WMWare Player or Workstation, you would run the command: <code>ovftool ncbo-appliance.ovf ncbo-appliance.vmx</code>
 
* You can supply the hostname (machine name) for the virtual machine during the deployment process. Documentation will refer as this hostname as 'example'.
 
* '''Change default passwords'''
 
** Operating System
 
*** Username: <code>root</code>
 
*** Password: <code>changemeNOW</code>
 
** BioPortal Admin User
 
*** Username: <code>admin</code>
 
*** Password: <code>changeme</code>
 
* Add an ontology using the BioPortal Admin User here: http://example/ontologies/new
 
** BioPortal Ontology Services can be configured to automatically process new ontologies every hour at 30 minutes past the hour (see [http://www.bioontology.org/wiki/index.php/Virtual_Appliance_FAQ#When_are_new_ontologies_parsed.3F documentation for enabling the scheduler]). This processing includes:
 
*** Parsing any new, unparsed ontologies
 
*** Calculating a set of metrics for these ontologies
 
*** Indexing these ontologies for use with search
 
* Parsing, indexing, metrics calculation, and ontology deletion can all be manually triggered or re-triggered using the BioPortal Admin user interface, which is available here: http://example:8080/bioportal_admin
 
* REST services are available at the following locations:
 
** BioPortal Ontology Services - http://example:8080/bioportal ([http://www.bioontology.org/wiki/index.php/BioPortal_REST_services documentation])
 
** Annotator - http://example:8080/obs/annotator ([http://www.bioontology.org/wiki/index.php/Annotator_User_Guide documentation])
 
** Resource Index - http://example:8080/resource_index ([http://www.bioontology.org/wiki/index.php/Resource_Index_REST_Web_Service_User_Guide documentation])
 
  
== Population Workflows ==
+
This release includes lots of new capabilities, one of which involves licensing. The good news is that you can download and get started with your Virtual Appliance right away—no need to wait for us to give you access to the right page.  
When storing an ontology using the BioPortal Ontology Services, some amount of processing is done automatically so that the ontologies can be visualized using the Web UI. However, the Annotator and Resource Index require separate, manual data population workflows in order to function with the provided ontologies. Details on running these populations can be found in the "Howto" sections located at the bottom of this page.
 
  
== Image Format and Machine Details ==
+
In order to do this, we had to implement licensing for BioPortal. Most users will find it trivial to obtain a free license, but for commercial users we are evaluating whether license fees could make BioPortal more sustainable.  
The NCBO Appliance image was created using the [http://www.vmware.com/appliances/getting-started/learn/ovf.html Open Virtualization Format], which should allow the machine to be used in a variety of environments.
 
  
The operating system is CentOS 5.5 64-bit running Tomcat 6, Java 6, MySQL 5.x, PHP 5.1.6, Rails 2.3.5, and Ruby Enterprise Edition 1.8.7, and memcached.
+
To learn more about the new OntoPortal Virtual Appliance release, visit our [https://ontoportal.github.io/administration/steps/getting_started/ Getting Started] page.
 +
You may also want to visit our [https://ontoportal.github.io/administration/ OntoPortal Administration Guide],
 +
including the [https://ontoportal.github.io/administration/general/ General Introduction], [https://ontoportal.github.io/administration/general/licensing/ Licensing], and [https://ontoportal.github.io/administration/steps/ Installation] sections.
  
The following applications use these services/runtime environments:
+
== Virtual Appliance Administration Documentation: Moved to GitHub ==
* Tomcat, Java
 
** BioPortal Ontology Services (BioPortal Core)
 
** BioPortal Admin (a UI for administering BioPortal Ontology Services)
 
** Annotator
 
** Resource Index
 
* Rails, Ruby, memcached
 
** BioPortal Web User Interface (including ontology visualization, Flex widgets, Annotator and Resource Index UIs)
 
* PHP
 
** Resource Index UI
 
  
== Basic System Administration ==
+
Our Administration documentation for the OntoPortal Virtual Appliance has been moved to the GitHub pages document at https://ontoportal.github.io/administration/.
* Most of our administration scripts and build environment assume that you will be running as the root user.
+
 
* Helper commands:
+
== Archival ==
** <code>ncbostart</code>: the required services are started on boot automatically, but if they need to be started automatically
+
 
** <code>ncbostop</code>: manually stop services
+
=== OntoPortal Virtual Appliance v2.5 archive is available ===
** <code>ncborestart</code>: manually start/stop services
+
 
* Start individual services:
+
For previous registered users of the v2.5 OntoPortal Virtual Appliance, we maintain an archival copy of this software on our site. While we do not actively support this version because its libraries are outdated, we still make it available to those users who were previously authorized to use it. All new users of the Virtual Appliance should use Version 3 or later of the Appliance.
** <code>/sbin/service httpd start</code>
+
 
** <code>/sbin/service memcached start</code>
+
The OntoPortal Virtual Appliance is the (rebranded) update of the BioPortal Virtual Appliance originally developed by the National Center for Biomedical Ontologies (NCBO). Our current Virtual Appliance software is based on BioPortal's v5.x software infrastructure, including the use of an RDF triplestore as the primary data storage mechanism.
** <code>/sbin/service tomcat6 start</code>
+
 
** <code>/sbin/service mgrep start</code>
+
=== Even older archive ===
* Stop individual services:
+
 
** <code>/sbin/service httpd stop</code>
+
For documentation of previous (v1.0) Virtual Appliances, please see our [http://www.bioontology.org/wiki/index.php?title=Category:NCBO_Virtual_Appliance&oldid=12610 archive].
** <code>/sbin/service memcached stop</code>
 
** <code>/sbin/service tomcat6 stop</code>
 
** <code>/sbin/service mgrep stop</code>
 

Latest revision as of 17:23, 12 June 2020


Most of this content has been moved! Please find the new content for the 3.0 version of the Virtual Appliance at our new OntoPortal Virtual Appliance Administration pages.

OntoPortal Virtual Appliance Version 3.0 is here!

We are pleased to softly announce our soft release of the OntoPortal Virtual Appliance version 3.0 (3.0.1, to be precise).

This release includes lots of new capabilities, one of which involves licensing. The good news is that you can download and get started with your Virtual Appliance right away—no need to wait for us to give you access to the right page.

In order to do this, we had to implement licensing for BioPortal. Most users will find it trivial to obtain a free license, but for commercial users we are evaluating whether license fees could make BioPortal more sustainable.

To learn more about the new OntoPortal Virtual Appliance release, visit our Getting Started page. You may also want to visit our OntoPortal Administration Guide, including the General Introduction, Licensing, and Installation sections.

Virtual Appliance Administration Documentation: Moved to GitHub

Our Administration documentation for the OntoPortal Virtual Appliance has been moved to the GitHub pages document at https://ontoportal.github.io/administration/.

Archival

OntoPortal Virtual Appliance v2.5 archive is available

For previous registered users of the v2.5 OntoPortal Virtual Appliance, we maintain an archival copy of this software on our site. While we do not actively support this version because its libraries are outdated, we still make it available to those users who were previously authorized to use it. All new users of the Virtual Appliance should use Version 3 or later of the Appliance.

The OntoPortal Virtual Appliance is the (rebranded) update of the BioPortal Virtual Appliance originally developed by the National Center for Biomedical Ontologies (NCBO). Our current Virtual Appliance software is based on BioPortal's v5.x software infrastructure, including the use of an RDF triplestore as the primary data storage mechanism.

Even older archive

For documentation of previous (v1.0) Virtual Appliances, please see our archive.

Subcategories

This category has only the following subcategory.