Starting the Netcool Agile Service Manager core services

You start the Agile Service Manager services using the asm_start.sh command.

Before you begin

Note: The Agile Service Manager core installation includes the probe and gateway containers, as well as the discovery services containers. You only start Agile Service Manager once you have completed all installation tasks for your optional components (that is, one or more of the probe and gateway, application discovery, or network discovery services).

About this task

Restriction: Do not start or stop the on-premise version of Agile Service Manager using Docker commands, as that may result in errors when retrieving required environment variables from the $ASM_HOME/.env file.

Table 1. Agile Service Manager commands
Action	Agile Service Manager command
Verify services	`asm_status.sh`
Start services	`asm_start.sh`
Stop services	`asm_stop.sh`
Restart services	`asm_restart.sh`
Tip: If you make changes to your environment variables, image tags or other configuration elements, use the `asm_start.sh` command to implement them. This command re-evaluates all dependencies by performing a 'docker compose up -d' action, thereby implementing them. The `asm_restart.sh` command on the other hand only performs a 'docker-compose restart' action, which restarts the containers but does not re-evaluate their dependencies, and therefore does not pick up any such changes.

Procedure

Start the Agile Service Manager services on the Agile Service Manager server by running the asm_start.sh command from the home directory.

$ASM_HOME/bin/asm_start.sh

Note: If you are deploying the discovery services, the start command will first create and configure the required database, before starting the services. This may take some time.

Example system output:

On-prem

Creating network "asm_default" with driver "bridge"
Creating asm_postgres_1
Creating asm_zookeeper_1
Creating asm_cassandra_1
Creating asm_kafka_1
Creating asm_kafkarest_1
Creating asm_topology_1
Creating asm_noi-probe_1
Creating asm_dns-observer_1
Creating asm_layout_1
Creating asm_ui_1
Creating asm_rest-observer_1
Creating asm_noi-gateway_1
Creating asm_kubernetes-observer_1
Creating asm_ui-api_1
Creating asm_merge_1
Creating asm_inventory_1
Creating asm_file-observer_1
Creating asm_docker-observer_1
Creating asm_nginx_1
Creating asm_observer_1

OCP

Creating network "asm_default" with driver "bridge"
Creating asm_elasticsearch_1
Creating asm_zookeeper_1
Creating asm_cassandra_1
Creating asm_kafka_1
Creating asm_kafkarest_1
Creating asm_topology_1
Creating asm_noi-probe_1
Creating asm_dns-observer_1
Creating asm_layout_1
Creating asm_ui_1
Creating asm_rest-observer_1
Creating asm_noi-gateway_1
Creating asm_kubernetes-observer_1
Creating asm_ui-api_1
Creating asm_merge_1
Creating asm_search_1
Creating asm_file-observer_1
Creating asm_docker-observer_1
Creating asm_proxy_1
Creating asm_observer_1

Tip: You can check the status of the discovery services.

Check application discovery status

To view the status of the application discovery services, see the logs.

Check the database status:

$ tail -f /opt/ibm/netcool/asm/logs/db2/create_database.log

Check the database schema status:

$ grep DbInit /opt/ibm/netcool/asm/logs/app-disco-pss/pss/wlp.log

Check the storage status:

$ docker exec -ti asm_app-disco-primarystorage_1 /opt/IBM/taddm/dist/bin/control status

Check the discovery services status:

$ docker exec -ti asm_app-disco-discovery_1 /opt/IBM/taddm/dist/bin/control status

Check network discovery status

To view the status of the network discovery services, launch the Consul UI on port 8501, for example:

https://<your-deployment>:8501/ui/sherpa/services

Results

You can also check the state of the Agile Service Manager deployment using the asm_status.sh command.

/opt/ibm/netcool/asm/bin/asm_status.sh

Example system output:

On-prem

          Name                         Command               State                   Ports
----------------------------------------------------------------------------------------------------------
asm_cassandra_1             /opt/ibm/start-cassandra.sh      Up ()
asm_cem-users_1             /bin/bash /cem-users/cemUs ...   Up ()   6002/tcp
asm_couchdb_1               tini -- /couchdb/couchdbEn ...   Up ()   4369/tcp, 5984/tcp, 9100/tcp
asm_dns-observer_1          sh -c /opt/ibm/$APPNAME/st ...   Up ()   9106/tcp, 9107/tcp
asm_docker-observer_1       sh -c /opt/ibm/$APPNAME/st ...   Up ()   9086/tcp, 9087/tcp
asm_file-observer_1         sh -c /opt/ibm/$APPNAME/st ...   Up ()   9098/tcp, 9099/tcp
asm_inventory_1             sh -c /opt/ibm/$APPNAME/st ...   Up ()   9178/tcp, 9179/tcp
asm_jenkins-observer_1      sh -c /opt/ibm/$APPNAME/st ...   Up ()   9146/tcp, 9147/tcp
asm_kafka_1                 /app/entrypoint.sh /opt/ka ...   Up ()   :19093->19093/tcp, 9092/tcp, 9093/tcp
asm_kafkarest_1             /app/entrypoint.sh /opt/ka ...   Up ()
asm_kubernetes-observer_1   sh -c /opt/ibm/$APPNAME/st ...   Up ()   9108/tcp, 9109/tcp
asm_layout_1                sh -c /opt/ibm/$APPNAME/st ...   Up ()   7084/tcp, 7085/tcp
asm_merge_1                 sh -c /opt/ibm/$APPNAME/st ...   Up ()   7082/tcp, 7083/tcp
asm_nginx_1                 /opt/ibm/netcool/asm/bin/s ...   Up ()   :80->8080/tcp, :443->8443/tcp
asm_observer_1              sh -c /opt/ibm/$APPNAME/st ...   Up ()   7086/tcp, 7087/tcp
asm_postgres_1              /var/lib/postgresql/docker ...   Up ()   5432/tcp
asm_redis_1                 bash /redis/redisEntrypoint.sh   Up ()   6379/tcp
asm_rest-observer_1         sh -c /opt/ibm/$APPNAME/st ...   Up ()   9104/tcp, 9105/tcp
asm_status_1                sh -c /opt/ibm/$APPNAME/st ...   Up ()   9084/tcp, 9085/tcp
asm_topology_1              sh -c /opt/ibm/$APPNAME/st ...   Up ()   8080/tcp, 8081/tcp
asm_ui-api_1                sh -c ./start.sh                 Up ()   3080/tcp
asm_ui_1                    /app/asmEntryPoint.sh            Up ()   8080/tcp
asm_zookeeper_1             /opt/app/entrypoint.sh /op ...   Up ()   2181/tcp, 2888/tcp, 3888/tcp

OCP

CONTAINER ID  IMAGE                                   COMMAND                  CREATED              STATUS              PORTS                          NAMES
22090abaa914  nasm-nginx:1.14.1.41                    "/opt/ibm/netcool/..."   57 seconds ago       Up 54 seconds       0.0.0.0:443->8443/tcp          asm_proxy_1
0c18fd0d70b7  nasm-file-observer:1.0.13.11613         "sh -c /opt/ibm/$A..."   About a minute ago   Up 57 seconds       9098-9099/tcp                  asm_file-observer_1
6c6f86877a3f  nasm-merge:1.0.6.11649                  "sh -c /opt/ibm/$A..."   About a minute ago   Up 57 seconds       7082-7083/tcp                  asm_merge_1
fe2c78739419  nasm-docker-observer:1.0.12.11614       "sh -c /opt/ibm/$A..."   About a minute ago   Up 57 seconds       9086-9087/tcp                  asm_docker-observer_1
5d821c375e6d  nasm-search:1.0.10.11620                "sh -c /opt/ibm/$A..."   About a minute ago   Up About a minute   7080-7081/tcp                  asm_search_1
de5243327d30  nasm-ui-api:1.0.2-11609                 "sh -c ./start.sh"       About a minute ago   Up 58 seconds       3080/tcp                       asm_ui-api_1
be9b4eb7107f  nasm-kubernetes-observer:1.1.22.11617   "sh -c /opt/ibm/$A..."   About a minute ago   Up 57 seconds       9108-9109/tcp                  asm_kubernetes-observer_1
f1d3c88cdfa7  nasm-noi-gateway:10.0.2.1.15            "/docker-entrypoin..."   About a minute ago   Up 57 seconds       8080/tcp                       asm_noi-gateway_1
bda9dc00a8d7  nasm-rest-observer:1.0.8.11614          "sh -c /opt/ibm/$A..."   About a minute ago   Up 58 seconds       9104-9105/tcp                  asm_rest-observer_1
2761da1495f1  nasm-layout:1.0.5.11635                 "sh -c /opt/ibm/$A..."   About a minute ago   Up 57 seconds       7084-7085/tcp                  asm_layout_1
4df8bdcb8489  nasm-dns-observer:1.0.10.11618          "sh -c /opt/ibm/$A..."   About a minute ago   Up 59 seconds       9106-9107/tcp                  asm_dns-observer_1
1564da02b82d  nasm-noi-probe:10.0.5.0.20              "/docker-entrypoin..."   About a minute ago   Up About a minute   80/tcp, 443/tcp, [...]         asm_noi-probe_1
5d0917ed649a  nasm-topology:1.1.23.11636              "sh -c /opt/ibm/$A..."   About a minute ago   Up About a minute   8080-8081/tcp                  asm_topology_1
75cd0a84d655  nasm-kafkarest:2.1.1.82                 "/opt/kafkarest/st..."   About a minute ago   Up About a minute                                  asm_kafkarest_1
5b79bbf46e0b  nasm-kafka:2.1.1.82                     "/bin/sh -c /opt/k..."   About a minute ago   Up About a minute   9092-9093/tcp, [...]           asm_kafka_1
5e0940bf6fe8  nasm-cassandra:3.11.4.76                "/opt/ibm/start-ca..."   About a minute ago   Up About a minute                                  asm_cassandra_1
e845c711848d  nasm-elasticsearch:6.5.4.89             "/opt/elasticsearc..."   About a minute ago   Up About a minute   9200/tcp, 9300/tcp             asm_elasticsearch_1
05c5f2ccefe2  nasm-zookeeper:3.4.14.56                "/bin/sh -c /opt/s..."   About a minute ago   Up About a minute   2181/tcp, 2888/tcp, 3888/tcp   asm_zookeeper_1
7cf40c300c2b  nasm-observer:1.1.24.11717              "sh -c /opt/ibm/$A..."   About a minute ago   Up 57 seconds       7086-7087/tcp                  asm_observer_1

What to do next

Tip: You can stop the Agile Service Manager service using the asm_stop.sh command.

/opt/ibm/netcool/asm/bin/asm_stop.sh

Example output:

Stopping asm_proxy_1 ... done
Stopping asm_kubernetes-observer_1 ... done
Stopping asm_noi-gateway_1 ... done
Stopping asm_noi-probe_1 ... done
Stopping asm_rest-observer_1 ... done
...