Google Git
Sign in
eclipse / mdmbl / org.eclipse.mdm.nucleus / 647a621db32699a6b95c8cc0d49f4fee28109880
commit647a621db32699a6b95c8cc0d49f4fee28109880[log] [tgz]
authorViktor Stöhr <viktor.stoehr@gigatronik.com>Tue Feb 07 07:23:09 2017 +0100
committerViktor Stöhr <viktor.stoehr@gigatronik.com>Tue Feb 07 07:23:09 2017 +0100
treeaad31918cbdcb33d9116afbba41c471574c944a3
parent4c4b19f8cbae1f98d934b2008152615d2d86ef26 [diff]
delete typings in *.application/src/main/webapp/typings/
8 files changed
tree: aad31918cbdcb33d9116afbba41c471574c944a3
  1. gradle/
  2. org.eclipse.mdm.application/
  3. org.eclipse.mdm.businessobjects/
  4. org.eclipse.mdm.connector/
  5. org.eclipse.mdm.filerelease/
  6. org.eclipse.mdm.freetextindexer/
  7. org.eclipse.mdm.property/
  8. WebContent/
  9. .gitignore
  10. build.gradle
  11. gradlew
  12. gradlew.bat
  13. README.md
  14. settings.gradle
README.md

minimum requirements

  • JDK 1.8.0_45
  • Gradle 2.13

build dependencies

Before you can install and build the application, you have to checkout and install: (gradlew install)

  • org.eclipse.mdm.api.base
  • org.eclipse.mdm.api.default
  • org.eclipse.mdm.api.odsadapter

build, deploy and configure the application

  1. edit the org.eclipse.mdm.nucleus/org.eclipse.mdm.application/src/main/webapp/app and set the variables host, port and prefix for your deployment (This properties are used to create the rest URLs to communicate with the backend)
  2. build the application (gradlew install) The command gradlew install at org.eclipse.mdm.nucleus creates a ZIP archive named mdm_web.zip at /org.eclipse.mdm.nucleus/build/distributions The ZIP archive contains the backend org.eclipse.mdm.nucleus.war and the configurations /configuration
  3. deploy the backend ( org.eclipse.mdm.nuclues.war file) at your application server
  4. copy the content of the extracted /configuration folder to GLASSFISH_ROOT/glassfish/domains/domain1/config
  5. edit the org.eclipse.mdm.connector/service.xml file to configure the data sources
  6. install and configure the LoginModule (see org.eclipse.mdm.realms - README.md)
  7. restart the application server
  8. visit the main page of the client to make sure everything works fine. The main page of the client should be available under http://SERVER:PORT/APPLICATIONROOT (eg: http://localhost:8080/org.eclipse.mdm.nucleus)

available rest URLs

Business Object: Environment

Business Object: Test

Business Object: TestStep

Business Object: Measurement

Business Object: ChannelGroup

Business Object: Channel

FreeTextSearch

Configuration

  1. start ElasticSearch. ElasticSearch can be downloaded at https://www.elastic.co/products/elasticsearch. For testing purpose, it can be simply started by executing bin/run.bat
  2. edit the configuration (global.properties) to fit your environment. You need an ODS Server which supports Notifications. All fields have to be there, but can be empty. However certain ODS Servers ignore some parameters (e.g. PeakODS ignores pollingIntervall since it pushes notifications).
  3. start up the application. At the first run it will index the database. This might take a while. After that MDM registers itself as NotificationListener and adapts all changes one-by-one.

Run on dedicated server

The Indexing is completely independent from the searching. So the Indexer can be freely deployed at any other machine. In the simplest case, the same steps as in Configuration have to be done. The application can then be deployed on any other machine. All components besides the FreeTextIndexer and its dependencies are not user. Those can be left out, if desired.