Since the DC RUM May 2017 release, any AMD utilizing legacy architecture we refer to as Classic AMD.
Legacy architecture AMD releases:
- All AMD 12.4.2 and older
- As an installation option, 12.4.5 - 12.4.15
There is no direct upgrade option to switch from Classic AMD to AMD. You must install a new AMD and transfer your current Classic AMD configuration using the procedure below.
The only supported upgrade path is through the 2017 release. If you wish to upgrade to NAM Probe 2018 or later, you will first need to run the procedure below on an AMD 2017 and then run the software upgrade to the desired release, maintaining the supported upgrade path.
If your AMD is on Red Hat 6, transferring the Classic AMD monitoring configuration to the AMD requires a total re-installation of the operating system.
You need to upgrade your AMD to the officially supported Red Hat Enterprise Linux 7 and the monitoring software to the latest available update of the Classic AMD using the typical upgrade procedure. Then, you can transfer the configuration to the AMD.
Before you begin
- Make sure that you have root access to the Classic AMD that you wish to transfer.
- Make sure that you backup the Classic AMD monitoring configuration in its current state.
Use official backup procedures described in Complete AMD backup and restore.
- Note the IP address of the Classic AMD that you wish to transfer.
- Make sure that you have removable media available for temporary storage of configuration files.
To upgrade the Classic AMD, perform the following steps:
Log in to the Classic AMD as user
root and stop all Classic AMD traffic monitoring services.
applications.xml.defaults files located in the
Use an appropriate method to save the files to an external medium or another computer.
Install the supported operating system (Red Hat Enterprise Linux 7).
If you are using Red Hat Enterprise Linux 6:
Install Red Hat Enterprise Linux 7. For more information, see:
If you are using Red Hat Enterprise Linux 7:
Remove the current monitoring software installation. Use the
upgrade.bin --eraseoption, for example:
[root@AMD ~]#./upgrade-amd-amdos7-x86_64-ndw-17-00-02-0049-b001.bin –-erase
To clear the system completely, after you uninstall the software, remove the AMD specific directories. Use the following commands:
rm -fr /usr/adlex rm -fr /var/log/adlex rm -fr /var/spool/adlex
Install AMD 2017 software.
For AMD with DLM based licensing execute:
[root@AMD ~]#./upgrade-amd-amdos7-x86_64-ndw-17-00-02-0049-b001.bin --licenses-type dlm
For AMD with eServices based licensing execute:
[root@AMD ~]#./upgrade-amd-amdos7-x86_64-ndw-17-00-02-0049-b001.bin --licenses-type eservices
For more information, see Installing the AMD software.
Perform the post-installation configuration.
For more information, see After you install the AMD software.
Reboot, log in as user
root and stop all AMD traffic monitoring services. Use the
applications.xml file from the external medium used in step 2 to the
applications.xml.defaults file from the external medium used in step 2 to the
/usr/adlex/config directory as
appxml-tools command with the
upgrade parameter to upgrade the configuration to AMD. This is to make sure the script transfers any changes to your default global configuration settings.
[root@AMD ~]# appxml-tools upgrade -olddef=/usr/adlex/config/applications.xml.defaults.upgradesave
appxml-tools command (located in
/usr/adlex/tools/appxml) with the
migratetohs parameter to convert the configuration:
[root@AMD ~]# appxml-tools migratetohs
appxml-tools migratetohs T Migrating 'Test_Software_Service_01' application to use DSSL analyzer T Migrating 'Cloud Services Gateway' application to use DSSL analyzer T Migrating 'My Secure' application to use DSSL analyzer T Migrating 'ACCEPT MQ' application to use MQ analyzer T Migrating 'ACCEPT VIP' application to use HTTP analyzer T Migrating 'ACCEPT_Customer001 - PROD' application to use HTTP analyzer D Reading XSD schema D Writing output T Renaming applications.xml.amdhs to applications.xml T Configuration migration to AMD HS performed successfully
appxml-tools migratetohs T Migrating 'SECURE_CONTAINER_APP' application ('XML over HTTP' analyzer) to use HTTP analyzer T Migrating 'AS400_MQ_SERVERS' application ('MQ' analyzer) to use new MQ analyzer
These messages indicate that there were software services found which required migration because of analyzer change. We need to look at such applications to see if their configuration migrated as expected or some further tweaking is required. The particular cases we are aware of are:
- MQ services use default configuration after migration and thanks to the improvements in the analyzer, it should be better than any custom configuration in the old analyzer.
- XML over HTTP services configuration has to be manually recreated using the new HTTP analyzer.
- Oracle Forms over TCP and XML over TCP are converted to Generic with Transactions.
- Oracle Forms over SSL and XML over SSL are converted to Generic SSL (not decrypted).
- SOAP is automatically converted to HTTP and should work properly.
Once converted, change the converted
applications.xml file ownership to
During the conversion process, a new
applications.xml file is created which automatically gets creator ownership, which in this case is user
root . The RUM Console requires the owner of the
applications.xml file to be
adlex . Execute the following command to change the file ownership:
[root@AMD ~]# chown adlex:adlex /usr/adlex/config/applications.xml
Reboot the AMD and use the RUM Console to add the new AMD to the devices list and assign it to a report server.