| == Extended configurations (run & IDE) |
| |
| === Deployment via Eclipse IDE |
| |
| To deploy the nucleus in Glassfish asadmin can be configured as an External Tool in Eclipse: |
| |
| image::images/RunConfig3.png[] |
| |
| === Angular Live Development Server |
| |
| During development a full build of the MDM5 Webclient, which is part of the nucleus, is quite time consuming. It is more efficient to skip the client build entirely by using the parameter -Pheadless, which excludes the JavaScript-Code from being build and included in the war file. For the UI you can start the "NG Live Development Server". |
| It is started by invoking "npm start" in the root path of the angular application (org.eclipse.mdm/nucleus/webclient\src\main\webapp). After successful compilation you are able to see the webclient under http://localhost:4200/. + |
| Changes to the angular application will trigger an incremental compile of the changed sources. + |
| Additionally the the live development server implements a proxy, which forwards all requests to http://localhost:4200/org.eclipse.mdm.nucleus/* to http://localhost:8080/. So if the Glassfish with the MDM5 backend does not run on port 8080, you have to change the proxy configuration in org.eclipse.mdm/nucleus/webclient/src/main/webapp/proxies/development.config.json. |
| To avoid issues with the form based authentication, it is easier to switch to basic authentication by changing the web.xml in this scenario. Otherwise you may get errors for the backend requests, because you are not automatically forwarded to the login page. |
