E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (22)
View Page History
...
{section} Type in the following command: *{{docker pull petals/petals-esb-container:5.1.0}}*
h12. Starting Petals ESB
Type in: *{{docker run -d -p 7700:7700 -p 7800:7800 --name petals petals/petals-esb-container:5.1.0}}*
You can verify the container works with *{{docker ps}}*
{note}
{tip}By default, we publish all the Petals ESB container ports on the host system.
Be careful: ports used by provider components are not exposed. As an example, if you deploy the SOAP BC, whose listening port is 8084, this port will not be reachable from the outside. In such a case, you should launch Petals with an additional option: *-p 8080:8080*. If you forgot the option, it is not possible with Docker to expose a port after the container was launched. So, you would have to kill the container and restart it.{tip}
h1. Connecting to Petals ESB
Be careful: ports used by Petals components are not exposed. As an example, if you deploy the SOAP BC, whose listening port is 8084, this port will not be reachable from the outside. In such a case, you should launch Petals with an additional option: *-p 8084:8084*. If you forgot the option, it is not possible with Docker to expose a port after the container was launched. So, you would have to kill the container and restart it.
{note}
{note}
You can connect with usual tools: [Petals CLI|petalscomponents:Petals CLI 3.0.0+] or Petals Cockpit
You can also use basic tools as JConsole or VisualVM using the JMX URL: *{{service:jmx:rmi:///jndi/rmi://<docker-container-ip>:7700/PetalsJMX}}*, with {{petals/petals}} as credentials.
You can also use basic tools as JConsole or VisualVM using the JMX URL: *{{service:jmx:rmi:///jndi/rmi://<docker-container-ip>:7700/PetalsJMX}}*, with {{petals/petals}} as credentials.
h1. Working with Petals ESB container
h1. Getting Petals logs
h2. Connecting to Petals ESB
Type in *docker logs petals* to watch Petals logs.
You can connect with usual tools: [Petals CLI|petalscomponents:Petals CLI 3.0.0+] or [Petals Cockpit|petalscockpitsnapshot:], or you can also use basic tools as JConsole or VisualVM using the JMX URL: *{{service:jmx:rmi:///jndi/rmi://<docker-container-ip>:7700/PetalsJMX}}*, with {{petals/petals}} as credentials.
h1. Introspecting the container
To get the IP adress of the Docker container, type in: *{{docker inspect petals | grep \"IPAddress\"}}*
Type in *docker exec -ti petals /bin/bash*.
h2. Getting Petals logs
Type in *{{docker logs petals}}* to watch Petals logs.
h2. Introspecting the Docker container
Type in *{{docker exec -ti petals /bin/bash}}*.
Type in *{{docker logs petals}}* to watch Petals logs.
h2. Introspecting the Docker container
Type in *{{docker exec -ti petals /bin/bash}}*.
This will open a console in the container.
h1. Stopping Petals
h2. Stopping and restarting Petals
Use *docker stop petals* to stop the container and *docker start petals* to relaunch it.
Use *{{docker stop petals}}* to stop the container and *{{docker start petals}}* to relaunch it.
h1. Deleting the Docker container
Use *{{docker rm -f petals}}* to stop and delete the Docker container.
{column}
...