Required privileges
The user must have the privileges of the system administrator (superuser).
Before performing this procedure
If any Manager or Enterprise Manager resident processes are running, stop the service by referring to "A.8 How to Start and Stop Resident Processes". Also check that the relevant resident processes have stopped correctly.
Procedure
The procedure is as follows:
The procedure is as follows:Back up files in /var/opt/FJSVssqc/
Back up the files in the /var/opt/FJSVssqc/ directory.
Perform upgrade installation of Agent/Proxy Manager
Start installing the Agent in the same way as for the initial installation, as described in "3.1.2 Installing an Agent/Proxy Manager".
Note that the upgrade installation performs the following steps automatically:
Stops resident processes (as a precaution)
Backs up other definition files (in the /etc/opt/FJSVssqc/ directory)
Uninstalls the package for the previous version
Performs an upgrade installation, inheriting the information that was entered for the prompts during the previous installation
Restores the other definition files that have been backed up
Note
If upgrade has been done from V11 or V12, retention period for log (Troubleshoot) is set as default (7 days).
Refer to "6.7.2 Changing the retention period of log data (Troubleshoot)" when the retention period needs to be changed.
Write the files back to /var/opt/FJSVssqc/
Return the files backed up in "1. Back up files in /var/opt/FJSVssqc/" above to their original path.
Apply the user definitions that have been made to the definition files that were not overwritten.
Files that cannot be rewritten automatically are backed up to /etc/opt/FJSVssqc/ and /opt/FJSVssqc/bin with the name as follows:
"file nameVnnLnn.extension" or "file nameVnnn.extension"
(Where the VnnLnn part indicates the version and level prior to the upgrade)
If a file that was edited prior to the upgrade has been backed up, use the backup file as a basis for editing the file again. The following files are backed up:
DSAconfiguration.txt
template.dat
threshold.sh
udataconf.ini
Point
Backup files are created regardless of whether they have been edited.
Settings after upgrade installation
Execute the setting again when the environment that does the upgrade installation corresponds to the following conditions.
Two-tier Manager operation
Execute setup for Two-tier Manager operation on Agent/Proxy Manager again.
Information
Refer to "2. Set up the Agent" in the "3.6.4 Tasks to perform on the Agent" or "2. Set up the Proxy Manager" in the "3.6.3 Tasks to perform on the Proxy Manager" for detailed procedure.
If Pull/Push communication is switched during operation after installation
Switch Pull/Push communication method on Agent or Proxy Manager again.
Information
Refer to "4.4.3 Switching from Push to Pull" and "4.4.4 Switching from Pull to Push" for detailed procedure.
Collecting SAP NetWeaver performance information after upgrade from V13.4 or earlier
When upgrade installation from V13.4.0 or earlier has been done under the environment that collects SAP NetWeaver performance information, encrypt the password defined in PASSWORD in the connection parameters definition file (sqcGetSAPalertmon.ini) of SAP NetWeaver cooperation.
Information
Refer to "Connection parameters definition file" in the User's Guide for detailed procedure.
Collecting Oracle Database Server performance information after upgrade from V13.5 or earlier
Wnen upgrade installation from V13.5.0 or earlier has been done under the environment that collects Oracle Database Server performance information, encrypt the password defined in PASS in the [ORA] section in the collection template (template.dat) for management settings of Oracle Database Server.
Information
Refer to "How to Set up Oracle Database Server" in the User's Guide for detailed procedure.
Set up the Agent/Proxy Manager
Create and deploy a collection policy as explained in "A.1 Server Resource Information Collection Policy Creation Command".
Start the Agent/Proxy Manager daemon and confirm that it has started normally
Start the daemon by referring to "A.8 How to Start and Stop Resident Processes". Also check that the relevant resident processes have started correctly.
