There is no direct upgrade option to switch from Classic to High Speed AMD. You must install a new High Speed AMD and transfer your current Classic AMD configuration using the procedure below. 

If your AMD is on Red Hat 6, transferring the Classic AMD monitoring configuration to the High Speed AMD requires a total reinstallation 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 High Speed 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 migrate the Classic AMD to a High Speed AMD, perform the following steps:

  1. Log in to the Classic AMD as user root and stop all Classic AMD traffic monitoring services.

    Use the ndstop command.

  2. Save the applications.xml and applications.xml.defaults files located in the /usr/adlex/config directory.
    Use an appropriate method to save the files to an external medium or another computer.

  3. Install the supported operating system (Red Hat Enterprise Linux 7).

  4. Install the current release of the High Speed AMD software.

    • For High Speed AMD with DLM based licensing execute:

      [root@amdprobe /]#./upgrade-amd-amdos7-x86_64-ndw-12-04-05-1838-b001.bin --licenses-type dlm
      
    • For High Speed AMD with eServices based licensing execute:

      [root@amdprobe /]#./upgrade-amd-amdos7-x86_64-ndw-12-04-05-1838-b001.bin --licenses-type eservices
      

      For more information, see Installing the AMD software.

  5. Perform the post-installation configuration.
    For more information, see Post-Installation Settings.
  6. Reboot, log in as user root and stop all High Speed AMD traffic monitoring services. Use the ndstop command.

  7. Copy the applications.xml file from the external medium used in step 2 to the /usr/adlex/config directory.

  8. Save the applications.xml.defaults file from the external medium used in step 2 to the /usr/adlex/config directory as applications.xml.defaults.upgradesave.

  9. Execute the appxml-tools command with the upgrade parameter to upgrade the configuration to High Speed AMD. This is to make sure the script transfers any changes to your default global configuration settings.

    [root@amdprobe /]# appxml-tools upgrade -olddef=/usr/adlex/config/applications.xml.defaults.upgradesave
  10. Execute the appxml-tools command with the migratetohs parameter to convert the configuration to High Speed AMD:

    [root@amdprobe /]# appxml-tools migratetohs
    

    Example output for successful conversion:

    [root@RHEL]# 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
    

    Example output indicating you should talk with support:

    [root@RHEL]# 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 TCPXML over TCP are converted to Generic with Transactions.
    Oracle Forms over SSLXML over SSL are converted to Generic SSL (not decrypted).
    SOAP is automatically converted to HTTP and should work properly.

     

  11. Once converted, change the converted applications.xml file ownership to compuware:compuware.
    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 compuware. Execute the following command to change the file ownership:

    [root@amdprobe /]# chown compuware:compuware /usr/adlex/config/applications.xml

     

  12. Reboot the AMD and use the RUM Console to add the new High Speed AMD to the devices list and assign it to a report server.

 

  

 

  • No labels

1 Comment

  1. Quick note - DCRUM 2017 chown command should use adlex:adlex - instead of compuware:compuware.