Task 2. Install Service Manager Service Portal on all nodes

On each node, install Service Manager Service Portal. For detailed steps, see the "Online installation" section in Install a single instance of Service Manager Service Portal.

The offline installation process will install Service Manager Service Portal on a cluster of Red Hat Linux nodes that have only local area network (LAN) access. Each of the nodes is referred to as an "offline node".

This process still requires a Red Hat Linux machine that has Internet access to download the Service Manager Service Portal installation package. This machine is referred to as "the online host".

The offline installation process consists of the following steps.

Step 1. Download SMSP dependencies on the online host

On the online host, perform the following steps:

1. Log in as the root user to the Red Hat Linux machine that has Internet access.

2. Register your Red Hat Linux system to the Red Hat Subscription service.

   1. Set a proxy if necessary:

      # export http_proxy=http://<proxy_hostname>:<proxy_port>

      # export https_proxy=http://<proxy_hostname>:<proxy_port>

   1. Run the following command followed by the credentials used to log in to Red Hat Customer Portal:

      # subscription-manager register

   2. Run the following command:

      # subscription-manager attach --auto

3. Update the yum.conf file and clean up the yum cache:

   # vi /etc/yum.conf
   keepcache=1
   cachedir=<your_own_yum_cache_directory> 

   Note Changing from the default cache directory is optional. However, you must make sure your cache directory has at least 4GB of free space.

   # yum clean all  

4. Prepare the folder structure:

   # mkdir /opt/hp
   # cd /opt/hp/
   

5. Download the archive (propel_complete_installer.zip) containing the installers and Ansible playbooks to the machine.

6. Unpack the archive:

   # unzip propel_complete_installer.zip

7. Change to the installation directory:

   # cd propel-complete-installer

8. Run the installation script:

   With proxy:

   # ./propel_install.sh --proxy http://<web proxy host>:<port> --no-install-propel

   Without proxy:

   # ./propel_install.sh --no-install-propel

   When prompted, enter the password of the root user.

9. Download two more rpm packages:

   # wget http://www.rabbitmq.com/releases/erlang/erlang-18.2-1.el7.centos.x86_64.rpm -P <your_own_yum_cache_directory> 
   # wget http://www.rabbitmq.com/releases/rabbitmq-server/v3.6.0/rabbitmq-server-3.6.0-1.noarch.rpm -P <your_own_yum_cache_directory> 

   Note All rpm packages located in your own yum cache directory (which is defined in the /etc/yum.conf file) are needed for the Service Manager Service Portal installation.

Step 2. Download distributed deployment required packages on the online host

On the online host, perform the following steps:

1. Unzip the distributed deployment script:

   # unzip /opt/hp/propel_complete_installer/propel-setup.zip -d /opt/hp
   # unzip /opt/hp/propel-setup*/res/contrib-install*.zip -d /opt/hp
   # cd /opt/hp/content/propel-distributed*
   

2. Configure the propeld.yml file for distributed deployment:

   # cd /opt/hp/content/propel-distributed*/group_vars
   # cp propeld.yml.example propeld.yml
   # vi propeld.yml
   

   Set the upload parameter in this file to false:

   packages:
         enabled: true
         # disable and populate `.packages/` for no-internet installation
         download: true
         # disable for no copying of packages to remote nodes
         upload: false
   

3. Create a hosts.default file:

   # cd /opt/hp/content/propel-distributed*/inventory
   # vi hosts.default

   Add the following content to this file (replace <LB node FQDN> with the FQDN of your load balancer node):

   [lb]
   <LB node FQDN>
    
   [internet:children]
   lb
    
   [propeld:children]
   lb

4. Download the required packages:

   # cd /opt/hp/content/propel-distributed*
   # ansible-playbook packages.yml -c paramiko --ask-become-pass   
   # zip packages.zip –r .packages

Step 3: Create a local or LAN yum repository on each offline node

You need to create an offline repository for the offline server.

There are two ways to do this:

• Run a machine as a LAN yum repository server and add this repository to the offline server (that is, the RHEL host without Internet access).

  The following are example steps to add and enable an LAN yum repository:

  # yum repolist all
  # yum-config-manager --add-repo http://<Repo_IP>/downloads/RHEL70/media.repo
  # yum repolist all

  repo id	repo name	status
  MediaRepo	MediaRepo	disabled

  # yum-config-manager --enable InstallMedia

  Note This step might not enable the repo, and thus the next step is to manually edit the repo file.

  # vi /etc/yum.repos.d/media.repo

  [InstallMedia]
  name=Red Hat Enterprise Linux 7.2
  mediaid=1424360759.989
  metadata_expire=-1
  baseurl=http://<Repo_IP>/downloads/RHEL70/
  enabled=1
  cost=500
  gpgcheck=0
  # yum repolist all

  repo id	repo name	status
  MediaRepo	MediaRepo	enabled

• Copy the rpm packages to the offline server and create a local repository for the offline server.

  The following are example steps to add and enable a local yum repository:

  1. Create a directory:

     # mkdir -p /data/mirrors/RHEL/7/os/x86_64/RPMS

  2. Copy all of the rpm packages from the online host to this directory.

  3. Run the following commands:

     # createrepo /data/mirrors/RHEL/7/os/x86_64/
     # cd /etc/yum.repos.d/
     # vi mirrors.repo
     

     Add the following lines:

     [mirrors-base]
     name=RHEL-$releasever - LocalRepo
     baseurl=file:///data/mirrors/RHEL/7/os/x86_64/
     gpgcheck=0
     enable=1
     

     Disable other existing repositories by suffixing the repository names with .bak:

     # yum clean all

     # mv local.repo local.repo.bak
     # yum repolist

Step 4. Install Service Manager Service Portal on each offline node

On each offline node, perform the following steps:

1. Prepare the folder structure:

   # mkdir /opt/hp
   # cd /opt/hp/
   

2. Copy the archive (propel_complete_installer.zip) containing the installers and Ansible playbooks to the machine.

3. Unpack the archive:

   # unzip propel_complete_installer.zip

4. Change to the installation directory:

   # cd propel-complete-installer

5. Run the installation script:

   # ./propel_install.sh --offline

   When the installation is complete, the following message is displayed:

   Propel installation completed!
   Done!

After you have completed the online or offline installation steps on each node, you need to run the Ansible playbooks on each node to finalize the Service Manager Service Portal installation. To do this, follow these steps:

1. Configure LW-SSO:

   Note This step will configure LW-SSO in the following file:

   /opt/hp/propel/idm-service/idm-service.war/WEB-INF/hpssoConfig.xml

   # cd /opt/hp/propel_complete_installer/ansible_content
   # ansible-playbook -i ansible_targets configure_extras.yml --tags "initLWSSO" --extra-vars '{"lwsso_init_string":"Init string must be replaced for producti0n"}' 

   Replace Init string must be replaced for producti0n with your own LW-SSO initString value, which must match the initString value in the lwssofmconfig.xml file located in the Service Manager Server's RUN directory. Additionally, the initString value must contain both numbers and letters and must be 32 characters in length.

2. Enable Chat:

   Important Before you proceed, make sure that you have Service Manager Collaboration successfully deployed.

   # ansible-playbook -i ansible_targets configure_extras.yml --tags "enableChat" --extra-vars '{"toggle_chat":"true","chat_url":"https://<ChatUI_url>"}'

   Note You need to replace https://<ChatUI_url> with https://<Apache server host>/chatui, where <Apache server host> is the FQDN of the Apache server that you installed when deploying Service Manager Collaboration. For example: https://training.sm-demo.com/chatui.

   Important If using SSL, the Apache server and Service Manager Service Portal must use SSL certificates issued by the same Certificate Authority (CA), and the SSL certificates (or the CA) must be trusted by the user's browser.

3. Enable Survey:

   Run the enableSurvey script:

   # ansible-playbook -i ansible_targets configure_extras.yml --tags "enableSurvey" --extra-vars '{"toggle_survey":"on","service_manager_url":"http(s)://<SM_url>"}'

   Note Replace the "service_manager_url" parameter value with your Service Manager Server web service base URL: For example: https://mysmhost.mycompany.net:13443. For security reasons, https is strongly recommended.

   Configure Survey in the distributed mode configuration file:

   # vi /opt/hp/propel/contrib/propel-distributed*/propel/vars/main.yml

   • Add the following lines to the 'propel.ports' property:

     survey-ui: 9980
     survey: 9981

   • Add the following lines to the 'propel.configs_ui' property:

     survey-ui: survey-ui/app.json

   • Add the following lines to the 'propel.lb.sticky' property:

     - survey-ui

   • Add the following lines to the 'propel.configs' property:

     - survey-ui/app.json
     - survey/config.yml

4. Install the Service Manager Service Portal online help:

   # ansible-playbook -i ansible_targets configure_extras.yml --tags "overrideDoc" --extra-vars '{"doc_mode":"sm"}'

5. Enable rebranding:

   # ansible-playbook -i ansible_targets configure_extras.yml --tags "enableServices" --extra-vars '{"toggle_services":"off"}' 

 

Next, verify the installation on each node.

On each node, try logging in to Service Manager Service Portal with both the Consumer and Provider URLs and the corresponding user accounts. If the installation on a node is successful, you should be able to log in to the application on that node.

URL	User account
One of the following: https://<LB node host FQDN>:9000/org/CONSUMER https://<application node 1 FQDN>:9000/org/CONSUMER https://<application node 2 FQDN>:9000/org/CONSUMER https://<master DB node FQDN>:9000/org/CONSUMER https://<slave DB node FQDN>:9000/org/CONSUMER	orgadmin/propel
One of the following: https://<LB node host FQDN>:9000/org/Provider https://<application node 1 FQDN>:9000/org/Provider https://<application node 2 FQDN>:9000/org/Provider https://<master DB node FQDN>:9000/org/Provider https://<slave DB node FQDN>:9000/org/Provider	admin/propel

Related tasks

Set up a distributed Service Manager Service Portal cluster