You can install MainView Middleware Administrator (MVMA) on a Windows or Linux operating system.
Installing MVMA is a straightforward procedure that assumes you have purchased the product and received a product key. Installation can be accomplished using a GUI wizard or through a console installation available for installations on Linux.
The topics in this section apply to all customer sites and configurations.
If you have special site requirements or preferences, please contact BMC Support (http://www.bmc.com/support).
Be aware of the following points:
- Evaluate MVMA licensing needs based on the current number of IBM WebSphere MQ queue managers and/or TIBCO EMS servers.
- MVMA supports only 64-bit Windows or Linux operating systems.
- Installing MVMA includes the implementation of a default security model (the ADMIN_ADMIN model) with the application. The security model implements authentication and authorization security functionality. It is supplied with the product and is fully operational from your first access to the application. To learn more about security, refer to Security policy settings.
- MVMA by default installs MongoDB with authentication turned off. In the default configuration, this enables unauthorized access to the MVMA database from (only) the same host but not from any other host in the network. Be aware that a consequence of configuring high availability replication (see Configuring high availability replication) would be enabling network access to the MVMA database. To protect MongoDB from unauthorized access you need to enable authentication within the MongoDB and MVMA configuration. For enabling authentication for database access within MVMA, please contact BMC Support.
- MVMA by default installs MongoDB with its default logging settings, which may cause MongoDB to add diagnostic log entries referring to data records maintained within MongoDB. To meet any related security concerns, MongoDB logging can be configured to be run in a quiet mode from within the MongoDB configuration file in etc/data.conf; note that MongoDB explicitly does not recommend this for production as it may make tracking problems during particular connections more difficult. Refer to the MongoDB product documentation for more details on this topic.