Stopping the blueprint designer, cloud discovery service, and engine
To stop the blueprint designer and its associated services, you must stop the cloud discovery service, the blueprint design server, and the engine Heat services.
Stopping the cloud discovery service
Stop the cloud discovery service.
On version 6.1.1.1 and later, the cloud discovery service is installed along with
the blueprint design server.
- On Linux™ systems that manage services with the systemd system
manager, use the systemctl command:
systemctl stop ibm-cloud-discovery.serviceNote: If you started the cloud discovery service with the systemctl command, you must use the systemctl command to stop the cloud discovery service. - On other versions of Linux:
- Using the ps command, find the process IDs of the cloud discovery
service:
For example, the output of the command might look like the following code:ps aux | grep -i -e "cloud" | grep -v "grep"root 1218 0.0 1.5 319048 29932 ? Sl Dec08 0:00 /usr/bin/python /usr/bin/cloud-discovery-service - Using the kill command, stop the processes. For
example:
kill 1218
- Using the ps command, find the process IDs of the cloud discovery
service:
- On Windows™:
- Using the Task Manager program, find the cloud-discovery-service process.
- Right-click the cloud-discovery-service process and click End task.
Stopping the blueprint design server
Stop the blueprint design server:
server_installation_directory/bin/server stopserver_installation_directory. The
default installation directory is /opt/ibm-ucd-patterns on Linux and C:\Program Files\ibm-ucd-patterns on Windows. By default, the command looks like this
code:/opt/ibm-ucd-patterns/bin/server stop