This section describes how to install MainView Middleware Administrator (MVMA) on both Windows and Linux platforms.

Installing on Windows

Perform the steps below to install MVMA on a 64-bit Windows operating system environment.

Before running the Installer

The MQ Java environment must be loaded before running the Installer. Verify the MQ Java environment is loaded with the following command: dspmqver -p2 

The output should look like this:

Name: WebSphere MQ classes for Java
Version: 8.0.0.2
Level: p800-005-160516.2
Build Type: Production

Ensure the Name field says "WebSphere MQ classes for Java" and that the version is 8.0.0.0 or higher (we recommend 8.0.0.2 or higher).

If the MQ Java environment is not loaded, the following message is displayed: AMQ8351: WebSphere MQ Java environment has not been configured correctly.

To install on Windows

1. Navigate to the directory where the installation files are located.
2. Change directories to .\Disk1\InstData\Windows\VM.
3. Execute install.exe from the directory. A message is displayed indicating that the wizard is being prepared.
4. The Wizard introduction screen is displayed. Select Next to continue.
5. Select the required Install set from Full Administration Install Set, IBM WebSphere MQ Install Set or TIBCO EMS Install Set.
   The installation that you choose reflects your middleware administration infrastructure (IBM WebSphere MQ, TIBCO EMS or both). Depending on which set is selected, resulting installation steps reflect that choice. After selecting the relevant option, click Next.
6. Accept the License Agreement that is displayed in the next Wizard screen. Click Next.
7. Set the installation destination (path). An example of a default path is: C:\BMC\MVMA
   1. To accept the default path, click Next.

   2. To set an alternative path, click Choose. This opens the Windows file directory. Navigate to the desired installation directory, and click Next.
      
      If you are upgrading from version 8.x, click Choose to choose the location of the existing installation and then click Next. Note that the Admin service must be stopped prior to upgrading. In addition, you cannot upgrade an existing 8.2 installation.

      Note

      When changing the default installation directory during installation, ensure your custom TSMA installation directory does not exceed 50 characters in the path length to avoid exceeding the maximum path length limitation of 260 characters on Windows systems (MVMA can exceed this limitation when it is creating its internal directory tree upon starting for the first time).

8. If you selected a Full Administration Install Set or the TIBCO EMS Install Set in Step 5, now set the TIBCO EMS libraries path. The files should already be present; see the following example.
   
   {{code language="none"}}
   C:\tibco\ems\6.0\lib
   {{/code}}

   Note

   When installing TIBCO EMS components, either the server machine must have TIBCO EMS installed or these specific TIBCO files must be copied to the server machine: 

   For TIBCO EMS 8.x:  jms-2.0.jar, tibcrypt.jar, tibjms.jar, tibjmsadmin.jar

   For TIBCO EMS versions prior to 8.x: jms.jar, tibcrypt.jar, tibjms.jar, tibjmsadmin.jar

9. Click Install. Installation progress is displayed onscreen.
10. When the Install Complete screen is displayed, click Done to exit the wizard.

Installing on Linux

This section describes how to install MVMA on Linux, via a Console or GUI. 

Installing with a Linux Console

MVMA can be installed in a supported Linux operating system. Refer to Operating-environments to confirm that your Linux environment matches those supported by MVMA.

Before running the Installer

The MQ Java environment must be loaded before running the Installer. Verify the MQ Java environment is loaded with the following command: dspmqver -p2 

The output should look like this:

Name: WebSphere MQ classes for Java
Version: 8.0.0.2
Level: p800-005-160516.2
Build Type: Production

Ensure the Name field says "WebSphere MQ classes for Java" and that the version is 8.0.0.0 or higher (we recommend 8.0.0.2 or higher). If the MQ Java environment is not loaded, the following message is displayed: AMQ8351: WebSphere MQ Java environment has not been configured correctly.

To load the MQ Java environment, use this command: . /opt/mqm/java/bin/setjmsenv64

Note that loading the MQ environment is only required during the installation, it is not required to add this to the user profiles.

To install the application to Linux using the console option

1. From a console, navigate to the directory where the installation files are located
2. Run the command ./Disk1/InstData/Linux/VM/install.bin –i consoleA console opens to inform you that the installer is being launched.
3. A license screen is displayed. Read the contents and press Enter to continue to the next step.
4. Read the remaining information and type Y to accept licensing terms.
5. Select an Install folder for the application files.
   1. Press Enter to accept the default path;  /opt/BMC/MVMA
   2. Type in an alternate application file location if this fits your installation. If you are upgrading from version 8.x, choose the location of the existing installation. Note that the Admin service must be stopped prior to upgrading. 

6. If TIBCO EMS support is included in your installation, enter a destination folder where EMS files are stored (example: /opt/tibco/ems/<version>/lib, where <version> is the EMS version; for example /opt/tibco/ems/8.0/lib). Press Enter.

   Note

   When installing TIBCO EMS components, either the server machine must have TIBCO EMS installed or these specific TIBCO files must be copied to the server machine: 

   For TIBCO EMS 8.x:  jms-2.0.jar, tibcrypt.jar, tibjms.jar, tibjmsadmin.jar   

   For TIBCO EMS versions prior to 8.x: jms.jar, tibcrypt.jar, tibjms.jar, tibjmsadmin.jar

7. Review the pre-installation summary. Press Enter.
8. The installation is completed.

Refer to the sections on Starting-services-after-installation and Accessing-MainView-Middleware-Administrator-after-installation. These procedures must be followed before you can access MVMA.

Installing with a Linux GUI

To install the application to Linux in a GUI environment, follow the instructions below. Refer to Operating Environments to confirm that your Linux environment matches those supported by MVMA.

Before running the Installer

The MQ Java environment must be loaded before running the Installer. Verify the MQ Java environment is loaded with the following command: dspmqver -p2 

The output should look like this:

Name: WebSphere MQ classes for Java
Version: 8.0.0.2
Level: p800-005-160516.2
Build Type: Production

Ensure the Name field says "WebSphere MQ classes for Java" and that the version is 8.0.0.0 or higher (we recommend 8.0.0.2 or higher). If the MQ Java environment is not loaded, the following message is displayed: AMQ8351: WebSphere MQ Java environment has not been configured correctly.

To load the MQ Java environment, use this command: . /opt/mqm/java/bin/setjmsenv64

Note that loading the MQ environment is only required during the installation, it is not required to add this to the user profiles.

To install on Linux

1. Log in as the MainView Middleware Administrator user.
2. Navigate to the directory where the installation files are located.
3. Change directories to ./Disk1/InstData/Linux/VM.
4. Execute install.bin from the directory. A dialog box is displayed indicating that the wizard is being prepared.
5. The Wizard introduction screen is displayed. Select Next to continue.
6. Select the required Install set from Full Administration Install Set, IBM WebSphere MQ Install Set or TIBCO EMS Install Set.
   The installation that you choose reflects your middleware administration infrastructure (IBM WebSphere MQ, TIBCO EMS or both). Depending on the set selected, the specific installation steps required reflect that choice.
7. Accept the License Agreement that is displayed in the next Wizard screen. Select Next to continue.
8. Set the installation destination (path). The default path is: /opt/BMC/MVMA
   1. To accept the default path, select Next.
   2. If you are upgrading from version 8.x, click Choose to choose the location of the existing installation and then click Next. Note that the Admin service must be stopped prior to upgrading. 
   3. To set an alternative path, select Choose. This opens the file system browser. Navigate to the required installation directory, and select Next.

9. If you select a Full Administration Installation or the TIBCO EMS Installation Set in Step 5, set the TIBCO EMS libraries path. The files should already be present. See the following example for setting the path.
   
   /opt/tibco/ems/<version>/lib, where <version> is the EMS version; for example /opt/tibco/ems/8.0/lib

   Note

   When installing TIBCO EMS components, either the server machine must have TIBCO EMS installed or these specific TIBCO files must be copied to the server machine:

   For TIBCO EMS 8.x:  jms-2.0.jar, tibcrypt.jar, tibjms.jar, tibjmsadmin.jar   

   For TIBCO EMS versions prior to 8.x: jms.jar, tibcrypt.jar, tibjms.jar, tibjmsadmin.jar

10. Select Install. Installation progress is displayed on the graphical wizard.
11. When the Install Complete screen is displayed, select Done to exit the wizard.

You can now start the MVMA service. See Starting-services-after-installation.