I am using Amazon EC2 Ubuntu 9.04 jaunty AMI built by Eric Hammond.
It was quite quickly installed - finding AMI on AWS, starting, apt-get some current java and that is all.
Exchanging BaseX.jars is quite easy, it only might affect related startup scripts, as there are some slight changes in last releases.
To run it on server as standalone application you are done quickly, to make it working as a service e requires writting some scripts.
Attached are startup scripts, which were created on my other server (dedicated server, managed by Active24.cz).
start/stop/status:
sudo /etc/init.d/basex start
Changing versions of BaseX jar:
/opt/basex/version BaseX-6.3.1.jar
(trick with modifying link BaseXCurrent.jar)
and scripts client and console
BaseX runs under user basex, there must be related records in /etc/sudoers to let me, as sadmin user, do the tasks (I do not have root access to that server)
Hope, this helps
Jan
PS: I have never played with elasticserver.com as it was not accessible at the time of my attempts. Another topic to investigate (I would think of building stack Ubuntu - python 2.6 or 2.7 - Nagios - boto2.x - BaseX - Java SDK...)
Jan:
Would also like an EBS based EC2 AMI available but time constraints
as well.... my main issue in that I have not configured an BaseX
server as stand alone (wrapped in applications). What do I need on
the server (besides the core linux). JRE, Tomcat(?), which baseX
jar? Could use elasticserver.com to generate the AMI (so could be
used for other virtualization platforms as well).
thanks
*P
On 12/15/10 3:09 PM, Jan Vlčinský (CAD) wrote:
I agree.
For better performance, I would recommend EBS based instance
as it has better disk performance, not the traditional instance
store based on S3. I had in past some issues with performance of
PostgreSQL, which was relatively poor.
But I can confirm, that BaseX works on AWS EC2 instance with
@root-device="instance-store" @type="m1.small"
virtualization="paravirtual". I hope to find time to turn it to
EBS based instance store some time.
I think it would be
pretty trivial to setup an Amazon EC2 instance running a
BaseX server. Probably just need a Linux core with Java
installed. This could be shared as a public AMI.
best
*P
On 12/8/10 2:24 AM, Jan Vlčinský (CAD) wrote:
Hi
Option to have service like BaseX in the cloud
would be very nice. I was dreaming about it too.
On the other hand, I understand, that
resources, being available at cloud solutions like
Google Engine, AWS etc. are of quite different
kind, that needed for efficient BaseX. When I see
flashing of HD LED on my notebook, when performing
bigger operations, I know, porting BaseX to any
less disk efficient platform would kill the
performance completely.
For now, the only option in the cloud is sort
of virtual computer (like AWS EC2 etc.)
Jan
PS: Christian - you see, providing great
service creates even bigger demand :-).
I have no idea how much time and effort would
have to be spent to
support the datastore API. In general, we have
spent lots of effort
and thoughts into our own storage
architecture. It's one of the key
factors for the efficiency of BaseX, so I'm
not sure if switching to
another database backend is such a good idea,
not to mention
transaction issues, etc. But I might be wrong.
Christian
On Tue, Dec 7, 2010 at 3:50 PM, Min
Idzelis <min123@gmail.com>
wrote:
> I realize that BaseX can't be used
as-is on the Google App Engine. The
> question I have is how much work
would it be to get it up and running on
the
> App Engine's datastore API instead of
whatever you are using for
> indexing/storage. There is no access
to a filesystem. The datastore does
> have a concept of hierarchical
(parent-child) entities. In the datastore,
> the only operations that are
supported are: get/put by key, inequality
(<,
>>, =) filters, and a way to limit
results that have a common ancestor
> (key). Would this be enough to
support BaseX?
>
> Thanks,
>
> Min
>