From: Sasha Sherstnev Date: Fri, 4 Oct 2013 14:20:30 +0000 (+0100) Subject: Update information on Jabaws VA X-Git-Url: http://source.jalview.org/gitweb/?a=commitdiff_plain;h=eff4a98cfd1cbfb97694cb73a6d6f124b0af2d1e;p=jabaws.git Update information on Jabaws VA --- diff --git a/website/man_servervm.html b/website/man_servervm.html index 688f12a..1915405 100644 --- a/website/man_servervm.html +++ b/website/man_servervm.html @@ -66,14 +66,15 @@

The JABAWS Virtual Appliance is a way to run JABAWS server locally without the need to connect to the internet or configure JABAWS. What the appliance provides is a 'virtual server machine' (or more simply - virtual machine or VM), -running an installation of the JABAWS Web Application Archive (WAR) on TurnKey Linux. Once this has +running an installation of the JABAWS Web Application Archive (WAR) on +TurnKey Linux 12.1 (Tomcat edition). Once this has started up, it displays a message indicating the IP address of the JABAWS server, allowing any JABAWS client (such as Jalview or the JABAWS command line client) to connect to it.
You can run the appliance with freely available program such as VMware Player, but you will need to install it first. We have tested the JABAWS appliance with VMware Player v 3.1.2 on Windows and Linux, and VMware Fusion on Mac. - However, you are not limited to these virtualization systems and can use the JABAWS appliance with any other virtualization platform. You can use VMware OVF tool to prepare JABAWS image for a different virtualization platform e.g. VirtualBox.

+However, you are not limited to these virtualization systems and can use the JABAWS appliance with any other virtualization platform. You can use VMware OVF tool to prepare JABAWS image for a different virtualization platform e.g. VirtualBox.

When to use the JABAWS Virtual Appliance

The appliance best suits users who would like to use the JABA web services locally. This might be because they do not want to access systems over an internet, or just want to keep their data private. It is also @@ -99,40 +100,39 @@ but for most production environments, the JABAWS WAR distribution will be easie

The VMware Player screen shot below displays JABAWS VM CPU settings.

vmware cpu settings

-

JABAWS appliance configuration:

-

VMware info
- - CPUs : 1
- - RAM : 512 MB
- - Networking : Host only (the VM has no access to the outside network, nothing from the outside network can access the VM)
- - Hard disk : 20 GB (expanding)
- - VMware tools : Installed

-

OS info
- - OS : TurnKey Linux, based on Ubuntu 8.0.4 JEOS (Just-Enough-Operation-System)
- - Installation : Oracle Java 6, Tomcat 7, JABAWS v. 2.0
- - Hostname : tomcat
- - IPv4 address : dhcp
- - IPv6 address : auto
- - DNS name : none
- - Name server : dhcp
- - Route : dhcp
- - Keyboard : US_intl

+

JABAWS Virtual Appliance Configuration:

+

VMware info

+ +

OS information

+

Login credentials
- - Root password: jabaws

-

Services

-

Where VM_IP is the VM IP address. Under VMware Player host only networking, the first VM may have 192.168.227.128 IP address.

- +
  • Root password: jabaws
    • +
  • Tomcat admin password: adminjabaws
    • + +

    Services available at the virtial machine IP (e.g. VM_IP = 172.16.232.149)

    +

    Configuring Jalview to work with your JABAWS VM

    diff --git a/website/ws.css b/website/ws.css index 47fb425..71add17 100644 --- a/website/ws.css +++ b/website/ws.css @@ -1,3 +1,12 @@ +ul, ol { + margin-left:4em; + padding-left:0px; +} + +li { + margin-bottom:0em; +} + #banner { background-color:white;