Verifying the installation

When you have completed the installation of your IBM Cloud Orchestrator Servers, you can verify the installation by completing the following steps.

1. Verify that the status of the IBM® Cloud Orchestrator components is correct.
   • For a non high-availability installation:
     1. Run the following command on the IBM Cloud Orchestrator Server:

        /opt/ibm/ico/orchestrator/scorchestrator/SCOrchestrator.py --status

     2. Verify that the status of each IBM Cloud Orchestrator component is online, as shown in the following example output:

        ===>>> Collecting Status for IBM Cloud Orchestrator
        ===>>> Please wait ======>>>>>>
        
                Component                      Hostname                      Status
                -------------------------------------------------------------------
                IHS                            192.0.2.84                    online
                bpm-dmgr                       192.0.2.84                    online
                bpm-node                       192.0.2.84                    online
                bpm-server                     192.0.2.84                    online
                db2                            192.0.2.84                    online
                pcg                            192.0.2.84                    online
                swi                            192.0.2.84                    online
        
        ===>>> Status IBM Cloud Orchestrator complete

   • For a high-availability installation:
     1. Run the following command on the IBM Cloud Orchestrator Server:

        lssam

        this is a sample output of the command:

        Online IBM.ResourceGroup:central-services-rg Nominal=Online
                |- Online IBM.Application:bpm-node
                     |- Online IBM.Application:bpm-node:primaryiconode
                     '- Online IBM.Application:bpm-node:secondaryiconode
                |- Online IBM.Application:bpm
                     |- Online IBM.Application:bpm:primaryiconode
                     '- Online IBM.Application:bpm:secondaryiconode
                |- Online IBM.Application:ihs
                     |- Offline IBM.Application:ihs:primaryiconode
                     '- Online IBM.Application:ihs:secondaryiconode
                |- Online IBM.Application:scui
                     |- Online IBM.Application:scui:primaryiconode
                     '- Online IBM.Application:scui:secondaryiconode
                '- Online IBM.ServiceIP:cs-ip
                     |- Offline IBM.ServiceIP:cs-ip:primaryiconode
                     '- Online IBM.ServiceIP:cs-ip:secondaryiconode
        Online IBM.ResourceGroup:pcg-rg Nominal=Online
                '- Online IBM.Application:pcg
                     '- Online IBM.Application:pcg:primaryiconode
        Online IBM.Equivalency:cs-network-equ
                |- Online IBM.NetworkInterface:ens192:primaryiconode
                '- Online IBM.NetworkInterface:ens192:secondaryiconode

   Note: If the status of the services is not shown online, then reboot the node first and then restart the services.
2. Verify that you can access and log in to the following IBM Cloud Orchestrator user interfaces:
   • For a non high-availability installation:
     • Self-service user interface

       https://ico_server_fqdn:443

     • Business Process Manager user interface

       https://ico_server_fqdn:443/ProcessCenter/login.jsp

     where ico_server_fqdn is the fully qualified domain name (for example, host.example.com) of the IBM Cloud Orchestrator Server.
   • For a high-availability installation:
     • Self-service user interface:

       https://virtualIP_fqdn:443

     • Business Process Manager user interface:

       https://virtualIP_fqdn:443/ProcessCenter/login.jsp

     where virtualIP_fqdn is the fully qualified domain name (for example, host.example.com) of the virtual IP address.
   To access each user interface, use the following credentials:

   • Domain: Default
   • User: admin (OpenStack user)
   • Password: The password that you specified with the OPENSTACK_ADMIN_PASSWORD parameter in the response file

   For more information about accessing the IBM Cloud Orchestrator user interfaces, see Accessing the IBM Cloud Orchestrator user interfaces.

   If you cannot access the Self-service user interface, ensure that your firewall is configured to open the ports that are required by IBM Cloud Orchestrator. For information about the required ports, see Ports used by IBM Cloud Orchestrator.

3. Verify that the Self-Service Catalog is populated. In the Self-service user interface, click SELF-SERVICE CATALOG and explore the categories and offerings.
4. Confirm that the IBM Cloud Orchestrator extensions for Horizon are installed:
   1. Log on to the OpenStack Dashboard:

      https://openstack_server_fqdn/

      where openstack_server_fqdn is the fully qualified domain name (for example, host.example.com) of the OpenStack Controller.
   2. Click Identity > Domains, and click Edit a Domain.
   3. Confirm that the Availability Zones tab is visible.

   For more information about installing the extensions, see Installing the IBM Cloud Orchestrator extensions for Horizon.