SRM 6.0.0.0 | Automated Script to Copy MYSQL libraries to System Directories and Copy apg-services script file to systemd

Summary :    This script will copy the required MySQL Libraries and apg-services script file to System directories for SRM/SMR Binary Linux ( RHEL and SUSE ) deployments  . The script should be executed at  SRM/SMR Pre-upgrade level.

1. Steps to Execute the Script on 4VM or Scaled Linux Application 
   

• Copy the script to the Frontend server - Linux_Binary_MySql_Systemd_Automated_Script.zip to <APG-INSTALLED-PATH>/opt
• Navigate to <APG-INSTALLED-PATH>/opt
• Execute the below commands and see the README.txt for more information.
  • unzip Linux_Binary_MySql_Systemd_Automated_Script.zip
  • chmod +x Linux_Binary_MySql_Systemd_Automated_Script.sh
  •  Execute the command - ./Linux_Binary_MySql_Systemd_Automated_Script.sh  -i
    • First time execution reads all the SRM servers and enter the password to establish ssh connection  
  •  Re-run the command - ./Linux_Binary_MySql_Systemd_Automated_Script.sh  -i
    • Second time execution it copies the MySQL libraries to system directories (lib and lib64) and apg-services script file to Systemd .
      

1. Steps for 1VM SRM And SMR Linux Application 
   

• Copy the script to the server
  •   SMR_SRM_AIO_Linux_Binary_MySQL_Systemd_Script.zip to <APG-INSTALLED-PATH>/opt/
• Navigate to the directory
  • cd <APG-INSTALLED-PATH>/opt
    
• Unzip the script package
  •  unzip SMR_SRM_AIO_Linux_Binary_MySQL_Systemd_Script.zip
• Move into the extracted folder
  • cd SMR_SRM_AIO_Linux_Binary_MySQL_Systemd_Script
    
• Contents of this folder include:
  • SMR_SRM_AIO_Linux_Binary_MySQL_Systemd_Script.sh, libraries, README.txt
• Provide execute permission to the script:
  • chmod +x SMR_SRM_AIO_Linux_Binary_MySQL_Systemd_Script.sh
    
• Execute the script:
  • bash SMR_SRM_AIO_Linux_Binary_MySQL_Systemd_Script.sh
• Enter the Installed Directory
  • Enter installation directory [default: /opt/APG]:
    

• This script performs the following actions:

  • Copies MySQL shared libraries (.so files) to system directories (/lib and /lib64)

  • Copies the apg-services script to Systemd.




• Post SMR Upgrade Steps - After completing the SMR upgrade, restore the environment variables

                        export LD_LIBRARY_PATH="$OLD_LD_LIBRARY_PATH"
                        unset OLD_LD_LIBRARY_PATH

Important Notes

• Automated scripts handles the scaled additional backend nodes (which are scaled at pre_upgrade level)
• Post Upgrade to SRM 6.0.0.0 : Scaling any additional backend doesn't required execution of script.

• Related Articles

• ViPR SRM Windows binary 5.x: Backend services may fail to start automatically

  Summary: Backend services may fail to start automatically due to elongated start-up times of the MySQL service. Add the mysql service as a dependency to the APGBackendApg1 service to fix the issue. Detailed Article Symptoms: The Backend (apg) service ...

• SRM 5.x :: How do I configure SRM to change authentication from LDAP to LDAPS

  Summary: What are the steps to configure SRM to change the authentication from LDAP to LDAPS Detailed Article Instructions Below are the steps to configure SRM to change the authentication from LDAP to LDAPS over SSL port 636 1. Log in to the SRM ...

• SRM 6.0.0.0 | Fresh vAPP - PowerCycle and Reboot

  Issue Description: APG services remained in a stopped state after a power cycle or reboot of the VM. Summary: The APG service softlink was removed during the latest security updates. This caused the service to be set to a disabled state, preventing ...

• SRM 6.0.0.0 | CIAM Environment Setup Configuration for Single sign-on (SSO)

  Summary: Steps to generate a secret key and configure the CIAM server environment for Linux (vApp and Binary) and Windows Binary SRM deployments. Instructions Follow the steps below on the SRM Frontend CLI/PuTTY to configure and start the CIAM ...

• HCLSRM - Automation for Increasing Boot Partition Size by Migrating to a New Partition

  Detailed Article Pre-Requisite: "In the vSphere client, provision an additional disk of at least 1 GB for each SRM VM that requires increased boot space." Symptoms Legacy SRM installations, such as those starting from SRM 3.x and subsequently ...