Nav
You are viewing an older version of this section. Click here to navigate to the latest version.

Configuring the Management Console to Use an External Database

By default, the Mule Management Console for Mule ESB uses its own internal Derby database. However, rather than the embedded Derby database you can configure the console to use an external Oracle database.

This page provides step-by-step instructions to configure the management console with a standalone Oracle database.

The MMC-ORACLE.zip file described in this document is no longer available. Contact MuleSoft’s Forums or MuleSoft Support for more information.
[Mule 3.2] This information applies to management console data only. Mule also stores business event data in a default database. You also have the option to have that data stored in an Oracle database. See Configuring a Database for Business Event Data Persistence for instructions on how to configure an Oracle database for business event data storage and persistence.

Oracle Database Set Up

Before beginning, you should have an Oracle database already installed on your system. These instructions assume the following:

  • An Oracle 10g XE database is already installed. The instructions below use the placeholder host name oracledb.foobar.com, with the port 1521.

  • You should have a username and password set up for a user granted all permissions on this database. The instructions below use placeholders for the username mmc and the password Mule123. You edit an XML file and replace all occurrences of this placeholder username/password with your actual username/password combination.

Given the above set up and placeholders, the JDBC URL for accessing the Oracle database looks like the following:

jdbc:oracle:thin:mmc/Mule123@oracledb.foobar.com:1521:XE

Step-by-Step Configuration Instructions

These instructions require that you download the MMC-ORACLE.zip file, which is attached to this page. Click mmc:here to access this zip file This ZIP file contains a set of XML, SQL, properties, and JAR files that you use for this configuration.

  1. Unzip the MMC-ORACLE.zip file to a separate folder.

  2. Run the mmc-oracle.sql script file that was included in the ZIP file. This script creates a number of database tables, indexes, and triggers, and you should verify that it runs successfully.

  3. Unpack the mmc.war file to your filesystem.

  4. Open the install-directory\apps\mmc\webapps\mmc\WEB-INF\classes\META-INF folder and delete these files: jackrabbit-repo-ee.*.

  5. Edit the jackrabbit-repo-ee.xml supplied in the ZIP file so that it has the correct JDBC URL, user name, and password. Make the following edits to the file:

    1. Replace jdbc:oracle:thin:mmc/Mule123@oracledb.foobar.com:1521:XE with your Oracle URL.

    2. Replace mmc in the line <param name="user" value="mmc"/> with your user name.

    3. Replace Mule123 in the line <param name="password" value="Mule123"/> with your password.

    4. Repeat the above steps for every FileSystem and PersistenceManager entry in jackrabbit-repo-ee.xml.

  6. Copy the updated jackrabbit-repo-ee.xml file to the install-directory\apps\mmc\webapps\mmc\WEB-INF\classes\META-INF folder.

  7. Edit the galaxy-applicationContext.xml supplied in the ZIP file. Replace the url property value of the internalDataSource bean with your database URL.

    
                
             
    1
    2
    3
    4
    5
    6
    7
    
    <bean name="internalDataSource"
     class="org.springframework.jdbc.datasource.SimpleDriverDataSource">
     <property name="driverClass"
       value="org.apache.derby.jdbc.EmbeddedDriver"/>
       <property name="url"
       value="jdbc:derby:${mmc.data}/db;create=true"/>
    </bean>
  8. Copy the edited galaxy-applicationContext.xml file to install-directory\apps\mmc\webapps\mmc\WEB-INF\classes\META-INF and overwrite the existing galaxy-applicationContext.xml file.

  9. Copy the scheduler-ee.properties file supplied in the ZIP file to install-directory\apps\mmc\webapps\mmc\WEB-INF\classes\META-INF and overwrite the existing one, assuming one already exists.

  10. Edit the datasource-ee.properties file supplied in the ZIP file. Replace the datasource.username, datasource.password, and datasource.url properties with your actual username, password, and URL. (Note that a colon (:) in the URL must be escaped with a back slash().)

    
                
             
    1
    
    datasource.username=mmcdatasource.password=Mule123datasource.url=jdbc\:oracle\:thin\:mmc/Mule123@172.16.10.46\:1521\:XE
  11. Copy the edited datasource-ee.properties file to install-directory\apps\mmc\webapps\mmc\WEB-INF\classes\META-INF, overwrite the old file if it exists.

  12. Copy the ojdbc14.jar and quartz-oracle-1.6.6.jar files supplied from the ZIP file to install-directory\apps\mmc\webapps\mmc\WEB-INF\lib.

  13. Repackage the mmc.war file and deploy it.

Once deployment completes, you can run the Management Console and use your standalone Oracle database.