Ticket #349 (closed Feature Request: fixed)

Opened 8 years ago

Last modified 8 years ago

DM Enterprise Distribution based on Apache Karaf

Reported by: jri Owned by: jri
Priority: Major Milestone: Release 4.1
Component: DeepaMehta Standard Distribution Version: 4.0.12
Keywords: Cc: dgf, Malte, JuergeN, DanielP
Complexity: 3 Area: Runtime Environment
Module:

Description

This would make starting/stopping/monitoring a DM server installation more comfortable. Plus we get a remote OSGi shell.

It is already realized by dgf. Merging his branch should be sufficient.

Change History

comment:1 Changed 8 years ago by Jörg Richter

Enterprise distro based on Apache Karaf (#349).

We have 2 DeepaMehta distributions now:

The latter one is based on Apache Karaf.

Build the Enterprise Distribution:

    mvn clean install -P dist

The distro is created here:

modules/dm4-assemblies/dm4-server/distribution/target/dm4server-4.0.13-SNAPSHOT.tar.gz

To run it unpack it and change to its home directory.

Run DM in forground:

bin/karaf

You enter the interactive Karaf shell.

The DM Webclient start URL is (not changed):

http://localhost:8080/de.deepamehta.webclient/

The DM logfile is at

data/log/dm4.log

Shutdown Karaf (from Karaf shell):

shutdown

Run DM in background:

bin/start

Stop DM background process:

bin/stop

The DeepaMehta Enterprise Distribution is provided by dgf.
Thanks to dgf!

See ticket 349.

Last edited 8 years ago by jri (previous) (diff)

comment:2 Changed 8 years ago by Jörg Richter

Enterprise distro based on Apache Karaf (#349).

We have 2 DeepaMehta distributions now:

The latter one is based on Apache Karaf.

Build the Enterprise Distribution:

    mvn clean install -P dist

The distro is created here:

modules/dm4-assemblies/dm4-server/distribution/target/dm4server-4.0.13-SNAPSHOT.tar.gz

To run it unpack it and change to its home directory.

Run DM in forground:

bin/karaf

You enter the interactive Karaf shell.

The DM Webclient start URL is (not changed):

http://localhost:8080/de.deepamehta.webclient/

The DM logfile is at

data/log/dm4.log

Shutdown Karaf (from Karaf shell):

shutdown

Run DM in background:

bin/start

Stop DM background process:

bin/stop

The DeepaMehta Enterprise Distribution is provided by dgf.
Thanks to dgf!

See ticket 349.

Last edited 8 years ago by jri (previous) (diff)

comment:3 Changed 8 years ago by Jörg Richter

Adapt enterprise distro to Neo4j 1.8 (#349).

The Karaf based DM enterprise distribution is assembled with Neo4j Mehtagraph 1.8

See ticket 349.

comment:4 Changed 8 years ago by Jörg Richter

Enterprise distro: strip start levels (#349).

In the Karaf-based DM Enterprise Distribution all DM plugins run at the default start level.
The individual start levels are stripped for the sake of reduced complexity.

Note:
All existing DM plugins do not rely on specific start levels.
If they would -- possibly in the future -- we must establish the start levels in

a) the development environment (Pax Runner-based)
b) in the (binary) DM Standard Distribution

as well.

See ticket 349.

comment:5 Changed 8 years ago by jri

Hi dgf!
Regarding the possible trouble with 2 HTTP Services deployed (1 from Karaf, 1 from DM's HTTP Jetty): could we just drop DM's HTTP Jetty and rely on Karaf's one instead?

comment:6 Changed 8 years ago by jri

  • Status changed from new to closed
  • Resolution set to fixed

comment:7 Changed 8 years ago by Jörg Richter

Adapt enterprise distro to Neo4j 1.8 (#349).

The Karaf based DM enterprise distribution is assembled with Neo4j Mehtagraph 1.8

See ticket 349.

comment:8 Changed 8 years ago by Jörg Richter

Enterprise distro: strip start levels (#349).

In the Karaf-based DM Enterprise Distribution all DM plugins run at the default start level.
The individual start levels are stripped for the sake of reduced complexity.

Note:
All existing DM plugins do not rely on specific start levels.
If they would -- possibly in the future -- we must establish the start levels in

a) the development environment (Pax Runner-based)
b) in the (binary) DM Standard Distribution

as well.

See ticket 349.

Note: See TracTickets for help on using tickets.