Preparing for installation
MongoDB
Starting with version 9.2.00 of MVMA, MongoDB is no longer installed when you install MVMA. You must download, install and configure MongoDB as a separate task on the system on which you plan to install MVMA.
You can download MongoDB from the MongoDB Community Server Download webpage. For information about installing and configuring MongoDB, see What is MongoDB topic in MongoDB Manual.
Prepare MongoDB
To prepare MongoDB, create a new empty data directory to receive the MVMA database and set up a directory to receive the MongoDB log files.
For example, create a new directory as the root for MongoDB to maintain this information, which is referred to as <mvma92_db_root>.
Create a data/db sub-directory (that is, first data, then data/db) in the <mvma92_db_root> directory for the MongoDB server to store data for MVMA 9.2. In previous versions of MVMA, the MongoDB database was stored in the data/db sub-directory of the MVMA installation folder by default.
Create a logs sub-directory in <mvma92_db_root> for MongoDB to write its log files. Start the MongoDB server using this configuration by issuing the following command:
<mongodb_installpath> refers to the installation directory of the MongoDB server used with MVMA. To run MongoDB in the background, you can install and start MongoDB as a service on Windows or use the --fork option on Linux. For more information see, MongoDB product documentation.
IBM MQ
Before using the functionality contained in MVMA that pertains to IBM MQ, you must complete some additional IBM MQ related setup tasks on each of the IBM MQ queue managers you plan to administer.
MVMArequires access to a server connection channel on each of the queue managers you plan to manage. It is your responsibility to create or provide this channel.
To define a server connection channel on IBM MQ monitored queue managers
Because MVMA connects as an IBM MQ client and uses an administrative userid, it is necessary to grant middleware administrators the appropriate permissions. In particular, it is necessary to define Channel Authentication (CHLAUTH) objects to permit the connection from MVMA.
An example of such an MQSC command is shown below. This specific command shown would allow connections from any IP address beginning with 192.169 and run those connections under the userid usera.
Such commands should be executed from the MQSC console, although the specifics of this will vary by platform. For example, on Windows or Linux you would execute runmqsc QMgrName where QMgrName is the name of the target MQ queue manager. Then enter the MQSC commands in the displayed prompt. Consult the relevant IBM documentation for details.
DIS CHLAUTH(MVMA.SVRCONN) ALL
CHLAUTH(MVMA.SVRCONN) TYPE(ADDRESSMAP) DESCR( ) CUSTOM( ) ADDRESS(192.169.*) MCAUSER(USERA) USERSRC(MAP) CHCKCLNT(ASQMGR) ALTDATE(2015-05-15) ALTTIME(14.09.46)
The user ID specified in the MCAUSER field must be a member of the 'mqm' group on the platform on which the IBM MQ queue manager runs:
- If MVMA is installed on a Linux platform with the user ID mqm, 'MCAUSER' is not needed.
- In some cases, if the product is installed on Windows, a MCAUSER parameter such as MUSR_MQADMIN must be specified.