Old Release

This documentation relates to an old version of VIVO, version 1.12.x.
Looking for another version? See all documentation.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Summary

This document presents the process required to develop a new language to be integrated into VIVO and Vitro. It is intended for any developer who wishes to develop a new integrated language. The development process requires a good knowledge of the VIVO internal structure and its internal working mechanisms. This document describes the development cycle of new languages as well as the components required for this development.

Development Cycle


Vivo's internationalization process is a five-step cycle:

  1. At the beginning of the cycle, the first step is to compile, deploy, and run the Vivo instance on the local computer.
  2. The second step is to test and identify problems related to internationalization.
  3. If everything works properly this ends the development cycle.
    1. When a problem is identified it is necessary to search the code to find the problem.
    2. This involves doing a lot of pattern managing search activities.
  4. In fourth place, comes the stage of correcting the problem.
    1. Once the problem has been identified, the professional must edit the concerned file to make correction.
  5. In step five certain databases need to be initialized depending on the type of correction made.
    1. Then back to step one of recompiling and running vivo.

Starting Step

This step consists in setting up the software elements necessary to run an VIVO instance on a local host.

VIVO's software infrastructure installation

Tomcat

The VIVO host application is Apache Tomcat. You will find here Installing VIVO#ConfigureandStartTomcat its installation procedure.



  • No labels