diff --git a/cocome-maven-project/doc/Deployment Setup.md b/cocome-maven-project/doc/Deployment Setup.md index 65e516f4..1158bcfa 100644 --- a/cocome-maven-project/doc/Deployment Setup.md +++ b/cocome-maven-project/doc/Deployment Setup.md @@ -14,14 +14,15 @@ multiple domains with server, all deployable containers can be put on one server each in its own domain. However in this document, we use five different nodes with one Glassfish server. -For each part, the following parameters are relevant and are set in the settings.xml +For each part, the following parameters are relevant and are set in the **settings.xml** for `cocome-maven-project` and `cocome-cloud-jee-service-adapter`: -- ip address (and hostname) -- http port (port used by the services in a deployment) -- admin port (port used by the admin console) -- domain (Glassfish domain) -- admin user name (name of the admin user) -- admin password (password of the admin user) + +* host (usually "localhost", can be ip adress when you deployed parts of cocome on a different machine) +* http port (port used by the services in a deployment; portbase + 80) +* admin port (port used by the admin console; portbase + 48) +* domain (Glassfish domain, ex.: registry) +* admin user name (name of the admin user; usually: admin) +* admin password (password of the admin user; usually no password ) ## Important notice - In each case you need to start the glassfish domains before you can actually deploy @@ -33,20 +34,21 @@ for `cocome-maven-project` and `cocome-cloud-jee-service-adapter`: ## Maven based Deployment As the deployment is now performed with the cargo maven plug-in, the -specification of a password file is no longer an option and a local -Glassfish installation is not necessary. Instead the password field in the +specification of a password file is no longer an option. Instead the password field in the settings.xml can be left empty. -You can either deploy all parts of CoCoME in one go, or each part separately. +You can either deploy all parts of CoCoME in one go(which is recommended!), or each part separately. To deploy CoCoME as a whole, execute the following commands in the `cocome-maven-project` folder. To deploy one of the sub-projects, execute the commands in its corresponding folder: + - `cloud-web-frontend` for the frontend part - `enterprise-logic-ear`, `store-logic-ear` for the enterprise and store logic parts - `cloud-registry-service` for the registry. ### Command Line Deployment On command line you may deploy CoCoME or one of the above sub-projects as follows: + - Enter the project folder to deploy CoCoME and run `mvn -s settings.xml install` @@ -55,6 +57,7 @@ On command line you may deploy CoCoME or one of the above sub-projects as follow ### Eclipse Deployment To deploy CoCoME or one of the above sub-projects from within Eclipse, do the following: + - Right-click on cocome-maven-project -> Run As -> Build... - Set the following values: - Goals: install @@ -62,6 +65,7 @@ To deploy CoCoME or one of the above sub-projects from within Eclipse, do the fo - User Settings: Use your settings.xml from the actual project To undeploy CoCoME or a sub-project: + - Right-click on cocome-maven-project -> Run As -> Build... - Set the following values: - Goals: clean post-clean diff --git a/cocome-maven-project/doc/Development Setup.md b/cocome-maven-project/doc/Development Setup.md index 3aee1e68..fb97f15c 100644 --- a/cocome-maven-project/doc/Development Setup.md +++ b/cocome-maven-project/doc/Development Setup.md @@ -61,13 +61,14 @@ domains or you have configured you Glassfish servers with different admin and http ports, then you have to set these values properly. -- In the `service-adapter` project, proceed in a similar way (You should to add a Glassfish domain for this one). Therefore +- In the `service-adapter` project, proceed in a similar way (You should have added a Glassfish domain for this one too). Therefore read the [README](https://github.com/cocome-community-case-study/cocome-cloud-jee-service-adapter) in the cocome-cloud-jee-service-adapter project. -<<<<<<< 0af5575f29912bbf758ba19a66bf9dadc3104756 + + - Make sure you refer to the same domain for `service adapter` in this setting file and in the setting file of the service-adapter. -======= + Notice: the domain 'adapter' you propably created during glassfish setup is supposed to be the domain for the service-adapter project. ->>>>>>> 5fc8f1dce60fadb70749b4fc50e5265114c9bf84 + ## Building CoCoME diff --git a/cocome-maven-project/settings.xml.template b/cocome-maven-project/settings.xml.template index ca6bd4d9..866ed32e 100644 --- a/cocome-maven-project/settings.xml.template +++ b/cocome-maven-project/settings.xml.template @@ -9,53 +9,53 @@ http - cocome - 192.168.48.236 - 8080 - 4848 + registry + localhost + 8480 + 8448 admin - admin + org.cocome.cloud.logic.registry.stub - + http - cocome - 192.168.48.236 - 8080 - 4848 + store + localhost + 8180 + 8148 admin - admin + org.cocome.cloud.logic.stub http - cocome - 192.168.48.232 - 8080 - 4848 + enterprise + localhost + 8380 + 8348 admin - admin + - cocome - 192.168.48.206 + web + localhost 8080 - 4848 + 8048 admin - admin + http - 192.168.48.224 - 8080 - 4848 + localhost + 8280 + 8248 admin - admin + /de.kit.ipd.cocome.cloud.serviceadapter/Services @@ -63,4 +63,4 @@ cocome-context - + \ No newline at end of file