...
Code Block | ||||
---|---|---|---|---|
| ||||
Successfully built 6eb71347fa51c39f4bd5fd33 tobi@tobi-VirtualBox:~/Documents/odysseusdocker$ sudo docker images REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE java<none> <none> c39f4bd5fd33 8 c518da75d9f0 6 days 2 minutes ago 642.9686.8 MB <none>java 8 <none> c518da75d9f0 6eb71347fa51 6 days ago 686642.89 MB tobi@tobi-VirtualBox:~/Documents/odysseusdocker$ |
Now we can run the Docker container:
- "sudo docker run -p 127.0.0.1:9700:9669 --name our_odysseus -t 6eb71347fa51c39f4bd5fd33"
Code Block | ||||
---|---|---|---|---|
| ||||
tobi@tobi-VirtualBox:~/Documents/odysseusdocker$ sudo docker run -p 127.0.0.1:9700:9669 --name our_odysseus_open -t 6eb71347fa51c39f4bd5fd33 Starting Odysseus ... Odysseus: Cannot open display: Odysseus: GTK+ Version Check 0 INFO OdysseusConfigurationCore - Read config file from /root/.odysseus/odysseus.conf Current size of heap: 1.0 GB - de.uniol.inf.is.odysseus.core.serverActivator.OdysseusConfiguration.loadPropertiesstart(OdysseusConfigurationActivator.java:8661) 247235 INFO Core - CurrentMaximum size of heap: 1.0 GB - de.uniol.inf.is.odysseus.core.Activator.start(Activator.java:6164) 247741 INFO Core - MaximumFree sizememory of the heap: 1879.04 GBMB - de.uniol.inf.is.odysseus.core.Activator.start(Activator.java:6467) 247952 INFO Core - FreeRunning memory of the heapVM with: 801.1amd64 MB - de.uniol.inf.is.odysseus.core.Activator.start(Activator.java:6770) 24801912 INFO CoreOdysseusConfiguration - RunningRead VMconfig with:file amd64 from /root/.odysseus/odysseus.conf - de.uniol.inf.is.odysseus.core.server.ActivatorOdysseusConfiguration.startloadProperties(ActivatorOdysseusConfiguration.java:7086) osgi> 60994561 WARN LogicalOperatorBuilder - URL for SetTimeProgressMarker not available! - de.uniol.inf.is.odysseus.logicaloperator.LogicalOperatorBuilder.addLogicalOperator(LogicalOperatorBuilder.java:243) 86645699 INFO OdysseusServerApplication - Odysseus application is fully started! - de.uniol.inf.is.odysseus.product.server.starter.OdysseusServerApplication.start(OdysseusServerApplication.java:31) osgi> 9005 INFO SingleSchedulerManager - No Scheduler-Config-File found. - de.uniol.inf.is.odysseus.scheduler.manager.singleschedulermanager.SingleSchedulerManager.activate(SingleSchedulerManager.java:113) 86699030 INFO SingleSchedulerManager - New Scheduler-Config-File created - de.uniol.inf.is.odysseus.scheduler.manager.singleschedulermanager.SingleSchedulerManager.activate(SingleSchedulerManager.java:126) 87189109 INFO SingleSchedulerManager - Active scheduler. class de.uniol.inf.is.odysseus.scheduler.singlethreadscheduler.SimpleThreadSchedulerMSLimitSourcesPerThread - de.uniol.inf.is.odysseus.scheduler.manager.singleschedulermanager.SingleSchedulerManager.activate(SingleSchedulerManager.java:137) 9087 INFO OdysseusServerApplication - Odysseus application is fully started! - de.uniol.inf.is.odysseus.product.server.starter.OdysseusServerApplication.start(OdysseusServerApplication.java:31) 12920 13453 INFO WebServicePublisher - Webservice published at http://0:0:0:0:0:0:0:0:9669/odysseus - de.uniol.inf.is.odysseus.planmanagement.executor.webservice.server.WebServicePublisher.publish(WebServicePublisher.java:106) |
As you can see above, Odysseus started. We also exposed one port the the outside: port 9669 is forwarded to port 9700, wherefore we should be able to see the WebService in our host machine. Just open http://localhost:9700/odysseus?wsdl in a browser on your host machine.You should be able to see an XML-file describing the Odysseus WebService.
...