Installing and Deploying MMC to WebSphere

Mule Management Console (MMC) was deprecated in December 2015. Its End of Life is July 15, 2019. For more information see the MMC Migrator Tool or contact your Customer Success Manager to determine how you can migrate to Anypoint Runtime Manager.

This document describes how to install the production version of Mule Management Console to WebSphere. Note that you can also deploy Mule to a variety of other application servers or containers, such as Tomcat or JBoss. See Installing the Production Version of MMC for full details.

Please contact the MuleSoft Support team with any questions about downloading and deploying Mule Management Console.

Follow these instructions to install and configure your mmc.war file on WebSphere.

  1. Log in to the WebSphere server.

  2. Go to Applications > WebSphere Enterprise Applications, then click Install.

  3. Select Local file system, click Browse, select the mmc.war file to deploy, then click Next.

  4. Select Detailed to show all the installation options, then click Next.

  5. Review the Application Security Warnings, then click Continue.

  6. WebSphere presents a nine-step installation process. In Step 1, click Next.

  7. In Step 2, select the mmc module, then click Next.

  8. In step 3, click Next.

  9. In Step 4, select both boxes as shown, then click Next.

  10. In Step 5, again select both boxes as shown, then click Next.

  11. In Step 6, click Next.

  12. In Step 7, select the web module, then click Next.

  13. In Step 8, complete the context root (i.e : /mmc), then click Next.

  14. In Step 9, click Finish.

  15. WebSphere displays an installation screen.

  16. If the installation was successful you will see something like the following screen with a message that the application was installed successfully. Click Save in order to save it to the master configuration.

  17. After you have saved, you can see the application installed in Enterprise Applications, but it is not running. Before starting the application, additional configuration is needed. Click on the application.

  18. Click Class loading and update detection.

  19. Under Class loader order select the option Classes loaded with local class loader first (parent last), then click Apply.

  20. Click Save to apply the changes directly to the master configuration.

  21. If you didn’t configure the context root during the installation process, select the application and under Web module properties click Context root for Web Modules. Assign the value you want, then click OK.

  22. Your application status is now started.


Note that if you want to configure MMC to persist data on external databases, you should follow the instructions for the specific database, as described in the following pages:

In the above pages, the paths of the directories where configuration files reside are based on an example Tomcat installation. When working with config files, you should change the directory paths to suit your Websphere installation. The table below lists examples of config file locations, using the MS SQL Server for illustration.


C:\Program Files\IBM\WebSphere\AppServer1\profiles\AppSrv01\installedApps\w2k3wasNode01Cell\mmc-console-sqlserver-3_4_2_war.ear\mmc-console-sqlserver-3.4.2.war\WEB-INF\web.xml


C:\Program Files\IBM\WebSphere\AppServer1\profiles\AppSrv01\installedApps\w2k3wasNode01Cell\mmc-console-sqlserver-3_4_2_war.ear\mmc-console-sqlserver-3.4.2.war\WEB-INF\classes\META-INF\databases\tracking-persistence-mssql.properties


C:\Program Files\IBM\WebSphere\AppServer1\profiles\AppSrv01\installedApps\w2k3wasNode01Cell\mmc-console-sqlserver-3_4_2_war.ear\mmc-console-sqlserver-3.4.2.war\WEB-INF\classes\META-INF\databases\mmc-mssql.properties

Copy the sqlserver.jar into the following directory

C:\Program Files\IBM\WebSphere\AppServer1\profiles\AppSrv01\installedApps\w2k3wasNode01Cell\mmc-console-sqlserver-3_4_2_war.ear\mmc-console-sqlserver-3.4.2.war\WEB-INF\lib

sqlserver.jar is the ConnectJDBC type 4 driver for Microsoft SQL Server provided by IBM. If you use sqlserver.jar as described above, you do not need to use the JDBC driver provided by Microsoft (sqljdbc4.jar). For details, see Persisting MMC Data to MS SQL Server and the IBM documentation for data source minimum required settings for Microsoft SQL Server.

See Also

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub