Page tree
Skip to end of metadata
Go to start of metadata
Product

MainView Middleware Administrator

Version

9.1.00

Date

 

BMC is announcing the release of MVMA 9.1.00.A Fix Pack, which includes enhancements for the MainView Middleware Administrator (MVMA) product.

Overview of the enhancements

This section describes the enhancements available in MVMA 9.1.00.A Fix Pack.

MVMA has migrated to OpenJDK 14.0.2

MVMA now uses an OpenJDK 14.0.2–based JRE. For details about JRE migration during the installation see the installation instructions.

MVMA now enables retrieving connections with permissions assigned to users or groups 

You can now retrieve connections with permissions assigned to users or groups when you run MVMA if the users and groups are maintained from within MVMA. Users and groups can access this new functionality by selecting the permissions entry added to the Operations menu. For more information, see  Managing users and groups

Note

This enhancement is available only when running MVMA with one of the following security models:

  • ADMIN_ADMIN
  • LDAP_ADMIN
  • PREAUTH_ADMIN

Selecting a time range when searching for messages

You can now restrict the search for IBM MQ or TIBCO EMS messages to the time range in which, the messages were put into the selected queue.

You can use the Advanced Search Details window, to select the date and time to limit your search to a time range within which messages were created.

MVMA is enhanced to copy a user including assignments to groups and projects

In the Admin Console, the copy user function  is enhanced to create the new user with the same associations, permissions, and roles as apply to the origin user. For more information, see  Managing users and groups

Note

This enhancement is available only when running MVMA with one of the following security models:

• ADMIN_ADMIN
• LDAP_ADMIN
• PREAUTH_ADMIN

Enhanced support for IBM MQ

MVMA is enhanced to ensure toleration and support for IBM MQ 9.1.5. 

This included enhancing support for IBM MQ Queue objects adding availability of the MAXFSIZE attribute on local and model queues under the display name 'Max Queue File Size' and the queue status attributes CURFSIZE (displayed as 'Current Queue File Size) and CURMAXFS (displayed as 'Current Max Queue File Size').

Fixed issues

Tracking IDIssue
DRX81-1744QM001807745 - Changed filtering in Scheduled Tasks view to relate to connection name instead to task ID
DRX81-1774QM001820948 - Removed unrelated filtering from Product Administrators view in the Admin Console
DRX81-1786Improve documentation with regards to configuring an SSL secured MQ connection
DRX81-2196Fixed the issue where "Request Only" attribute for MQ Subscriptions could not be altered
DRX81-2803

Fixed an issue where the description of an MQ Channel Authentication Record was blanked out after altering the channel authentication record

DRX81-2865Fixed a vulnerability CVE-2019-17571
DRX81-2849

Fixed an issue where the MQ import\export wasn't displayed when disabling MQ Authority Records by applying Properties Filter

DRX81-2863Fixed a vulnerability CVE-2019-12401
DRX81-2898

Fixed an uncaught NPE causing Error 'undefined' in the UI when executing administrative operations after deleting the product key

DRX81-2963Fixed a regression where uploading the same message file to EMS was failing reporting a 'File Upload error'.
DRX81-2964Fixed the user name not being set to blank when copying a user from within the Admin Console
DRX81-2992Enabled administration of MVMA common settings through the JavaScript API 
DRX81-2993Enabled administration of MVMA security settings through the JavaScript API
DRX81-2996Enabled administration of MQSC console administrators through the JavaScript API
DRX81-3012Fixed an issue where an NPE was thrown when searching for MQ messages
DRX81-3017MQ queue property 'Harden Backout Count' now shown under the 'Storage' category
DRX81-3023Lowering visibility of log messages related to deleting scheduled tasks.
DRX81-3053

Fixed a regression causing MVMA non-admin users to no longer be able to format messages from within the message editor by selecting from configured message format scripts or from message format rules.

Installing the Fix Pack

Use the following procedures to install the Fix Pack.

To install on Linux

  1. Stop the MVMA service.
  2. Ensure MongoDB is not running, stop it if necessary.
  3. To accelerate the upgrade process, the contents of the work/ directory can be deleted.
  4. Make a backup copy of your MVMA installation directory. 

    Note

    The default installation directory is /opt/BMC/MVMA.

  5. Unzip the file mvma-9.1.00.A-linux-x86-64.zip into the MVMA installation directory. Your unzip client may prompt you to overwrite some files - click Yes to all of them.
  6. Verify that after the zip has extracted you have fixpacks/mvma-9.1.00.A/ in your installation directory. 
  7. From a command prompt, cd to the installation directory and run: bin/updatejava
    Confirm that the update procedure says that the java aliases were created successfully.
  8. From a command prompt, cd to the installation directory and run: bin/admin --update fixpacks/mvma-9.1.00.A/
  9. Confirm that the update procedure says it was successful.
  10. Restart the MVMA service.

To install on Windows:

  1. Stop the MVMA service.
  2. Ensure MongoDB is not running, stop it if necessary.
  3. To accelerate the upgrade process, the contents of the work/ directory can be deleted.
  4. Make a backup copy of your MVMA installation directory. Note that the default installation directory is c:\Program Files\BMC Software\MVMA
  5. Unzip the file mvma-9.1.00.A-windows-x86-64.zip into the MVMA installation directory. Note that your unzip client may prompt you to overwrite some files - click Yes to all of them.
  6. Verify that after the zip has extracted you have fixpacks\mvma-9.1.00.A\ in your installation directory.
  7. From a command prompt, cd to the installation directory and run: bin\updatejava.bat
    Confirm that the update procedure says that the java aliases were created successfully.
  8. From a command prompt, cd to the installation directory and run: bin\update.bat fixpacks\mvma-9.1.00.A
  9. Confirm that the update procedure says it was successful.
  10. Restart the MVMA service.

After the installation of the update, users should clear their browser cache.

To clear the browser cache for Firefox

  1. Click the menu button. and select Options.
  2. Select the Privacy & Security panel.
  3. In the Cookies and Site Data section, click Clear Data...
  4. Remove the check mark in front of Cookies and Site Data. ...
  5. With Cached Web Content check marked, click the Clear button.

To clear the browser cache for Internet Explorer

  1. Click the Settings icon (top right corner) and click Safety.
  2. Click Delete browsing history.
  3. Check the Temporary Internet files and website files option.
  4. Click Delete. A confirmation message should appear

To clear the browser cache for Google Chrome

  1. At the top right, click More More.
  2. Click More tools and then Clear browsing data.
  3. At the top, choose a time range. To delete everything, select All time.
  4. Next to Cached images and files, check the box.
  5. Click Clear data.

If you have questions, call BMC Support. If outside the United States, use the Select Another Country drop-down list to search for local phone numbers.