### Update IBM Installation Manager for RHEL Source: https://www.ibm.com/docs/en/bmp/8.5_topic=pattern-upgrading-existing-instance This script updates the IBM Installation Manager to version 1.8.0 for Red Hat Enterprise Linux (RHEL). It creates a temporary directory, downloads the installer, extracts the archive, and executes the user installation command with root privileges. Verify network connectivity and user permissions. ```shell mkdir /tmp/im180 cd /tmp/im180 curl --insecure https://:@/storehouse/admin/files/vsys/im/agent.installer.linux.gtk.x86_1.8.0.20140902_1503.tar.gz -o ./im180.tar.gz gunzip -c im180.tar.gz | tar xvf - sudo -u virtuser ./userinstc -acceptLicense ``` -------------------------------- ### Update IBM Installation Manager for AIX Source: https://www.ibm.com/docs/en/bmp/8.5_topic=pattern-upgrading-existing-instance This script updates the IBM Installation Manager to version 1.8.0 for AIX operating systems. It downloads the installer, extracts it, and runs the user installation command. Ensure you have the necessary permissions and a stable internet connection. ```shell mkdir /tmp/im180 cd /tmp/im180 curl --insecure https://:@/storehouse/admin/files/vsys/im/agent.installer.aix.gtk.ppc_1.8.0.20140902_1503.tar.gz -o ./im180.tar.gz gunzip -c im180.tar.gz | tar xvf - sudo -u virtuser ./userinstc -acceptLicense ``` -------------------------------- ### Configure IBM Business Monitor Fix Pack Dependency Source: https://www.ibm.com/docs/en/bmp/8.5_topic=pattern-uploading-fix-pack-business-monitor This snippet shows how to configure the dependency for an IBM Business Monitor fix pack within the IBM PureApplication installation manager repository. It specifies the format for defining the relationship between the Business Monitor version and its required WebSphere Application Server version. ```shell com.ibm.websphere.MON*8.5.8000->com.ibm.websphere.ND*8.5.5008 ``` -------------------------------- ### Connect to IBM PureApplication CLI Source: https://www.ibm.com/docs/en/bmp/8.5_topic=pattern-installing-business-monitor-from-local-directory Command to initiate a connection to the IBM PureApplication command-line interface. Requires hostname, userID, and password for authentication. ```bash ../pure.cli/bin/pure -h hostname -u userID -p password -a ``` -------------------------------- ### Upload IBM Business Monitor Pattern Package via CLI Source: https://www.ibm.com/docs/en/bmp/8.5_topic=pattern-installing-business-monitor-from-local-directory Command to upload the IBM Business Monitor Pattern package file to IBM PureApplication using the command-line interface. The path to the .tgz file is provided as an argument. ```python >>>deployer.patterntypes.create('E:\\MONITOR_PATTERN_V857_AIX.tgz') ``` -------------------------------- ### Backup DB2 Database Source: https://www.ibm.com/docs/en/bmp/8.5_topic=cd-cloning-db2-database-embedded-db2-instance-by-running-db2-backup-restore-commands Command to back up a DB2 database. It requires the database name and the path where the backup files will be stored. This is the first step in cloning a database. ```db2 db2 backup database DATABASE_NAME to DB_BACKUP_PATH ``` -------------------------------- ### Python Script Customization for Monitor Config Integration Source: https://www.ibm.com/docs/en/bmp/8.5_topic=cp-customizing-monitor-config-integration-script-package-after-deployment This Python code snippet is part of the Monitor Config Integration script package. It retrieves WAS administrator credentials from environment variables and integrates with BPM or refreshes event sources. Users can insert their custom scripts after the provided 'print' statement to be executed after deployment. ```python if __name__ == '__main__': #get was admin user and password from environment variables(script package parameter keys) was_user = os.environ.get('MON_dmgrAdminUserName') was_password = os.environ.get('MON_dmgrAdminPassword') #config integration with BPM if BPM DE information is provided, otherwise just refresh Event source. integrate_with_bpm(was_user, was_password) #user can put their own customized script here, so they can be executed after DE is deployed. print "Monitor DE with admin user %s is successfully configured!" % was_user ``` -------------------------------- ### Customize Monitor 857 Config Integration Script Package with Python Source: https://www.ibm.com/docs/en/bmp/8.5_topic=cp-customizing-monitor-857-config-integration-script-package-after-deployment This Python code snippet demonstrates how to extend the config.py file within the Monitor 857 Config Integration script package. It shows how to retrieve WAS admin credentials from environment variables and integrate with IBM BPM, or refresh event sources if BPM information is not provided. Users can insert their own customization scripts after the provided integration logic. ```python import os def integrate_with_bpm(was_user, was_password): # Placeholder for BPM integration logic print("Integrating with BPM...") pass if __name__ == '__main__': #get was admin user and password from environment variables(script package parameter keys) was_user = os.environ.get('MON_dmgrAdminUserName') was_password = os.environ.get('MON_dmgrAdminPassword') #config integration with BPM if BPM DE information is provided, otherwise just refresh Event source. integrate_with_bpm(was_user, was_password) #user can put their own customized script here, so they can be executed after DE is deployed. print("Monitor DE with admin user %s is successfully configured!" % was_user) ``` -------------------------------- ### Execute SQL Schema File on Target DB2 Source: https://www.ibm.com/docs/en/bmp/8.5_topic=cd-cloning-db2-database-embedded-db2-instance-by-running-db2move-commands Executes a generated SQL file on the target DB2 environment to create the database schema. It requires the SQL file name and a log file name for recording the execution. The `-tvf` flags ensure the script is executed and verbose output is logged. ```bash db2 -tvf DATABASE_SQL_NAME -l LOG_NAME ``` -------------------------------- ### Import DB2 Database Data with db2move Source: https://www.ibm.com/docs/en/bmp/8.5_topic=cd-cloning-db2-database-embedded-db2-instance-by-running-db2move-commands Imports data into the target DB2 database using the `db2move` command. It requires the database name and an import option (e.g., 'insert'). Note: The order of tables in the `db2move.lst` file might need adjustment to ensure parent tables are imported before child tables due to dependencies. ```bash db2move DATABASE_NAME import -io insert ```