Meldware Installation Guide v 1.0M6
From Buni.org
Overview
Buni Meldware is our communication suite enabling Email, Calendaring, and Webmail. Meldware consists of both server-side and web-delivered client-side components. Combined with clients such as Mozilla Thunderbird or Microsoft Outlook, Meldware is a complete email and scheduling solution.
Feature Overview
Suite
Meldware Communication Suite is made up of distinct components. These can be installed separately (in 1.0M6 this requires a bit of effort) as stand-alone products. However, together they form a more robust experience with some features unique to the integrated set.
Meldware Mail
Meldware Mail supports both common mail clients and the Meldware Webmail rich client. Mail supports open protocols such as IMAP, POP and SSL. User authentication integrates with common directory solutions via LDAP such as Microsoft Active Directory, Novell Directory Server, and OpenLDAP or by using database driven authentication. Additionally, Meldware Mail provides extension points for less common authentication methods. Meldware Mail goes beyond the common mail server with its unique support for [Mail Based Application]s and integration with Meldware Calendar.
Meldware Calendar
Meldware Calendar service enables users to manage personal calendar entries and addressbooks.
The calendar entries are accessable from:
- ICal readers using WEBDAV(HTTP) with ThuderBird, Mac OsX ICal, Evolution.
- WebMail client.
- email with schedule mail alias commands
Meeting and schedule managment:
- ICal/WebDAV publishing.
- WebMail client.
- email with schedule mail alias commands
Addressbook/Contacts are managed:
- Webmail.
- LDAP.
The open API's and JMS based audit framework make meldware an ideal solution to integrate workflows and Enterprise applications that need to intergrate with user contacts, messaging and event scheduleing or management.
Meldware Webmail
Meldware Webmail is a rich web-based user interface (UI) for reading email and scheduling events. It is based on Adobe's Flash 9 technology and is available on all major client operating systems including Microsoft Windows, Linux and OS X. Meldware supports major browsers including Mozilla Firefox and Microsoft Internet Explorer. Meldware Webmail allows users to read and compose emails, manage folders, as well to schedule and to accept events in a rich and responsive graphical user interface.
Getting Meldware Communication Suite
Download
The Meldware Communication Suite is available for download at this URL. There are both Java Webstart and traditional installation packages available. See the "Installing Meldware" section of this guide for instructions.
Source
The source code for Meldware products is available via the Buni.org hosted [Concurrent Versions System] installation. See the [Source_Repository] page on the Buni.org wiki for more information.
Licensing
Meldware Communication Suite is both open source and free software. It is freely distributable under the LGPL license which allows allows commercial embedding. Reciprocation is required in the event that the source code in the org.buni.** packages are modified and subsequently distributed. Contact licensing@buni.org for more information on opportunities to use Buni software commercially or in ways that extend beyond the LGPL license.
Note: this explanation is not intended to supersede or to augment the license but, rather, to summarize its terms for descriptive purposes. Please consult the LGPL license text for the actual legal terms.)
Installing Meldware
Graphical Installation Walkthrough
This installation walkthrough assumes that the user is installing via the graphical installation tool either using Java Webstart or by downloading the jar and manually installing the software. It does not cover manual or development-build deployment (via ant or otherwise). A developer's guide will be provided later for this purpose.
Starting the Installer
via Webstart
If you click on one of the Java Webstart based installations here, the following screen will come up:
Milestone builds are signed with a free certificate. Accept the certificate and disregard the warning provided that you downloaded this from the buni.org website with the instructions above.
via Download
If you downloaded one of the regular install jar files then you must first install the Java Runtime Environment. There are several available. If you are on Linux, Windows or Solaris, Bunisoft recommends either Sun JDK 5 or BEA JRockit 5. If you are on another platform you will need to consult Bunisoft or the vendor on the best available Java 5 compatible Runtime Environment for your platform.
From a command prompt change to the directory where you downloaded the Meldware installation jar and type "java -jar JARNAME.JAR". You may need to make sure that the java command is in your path. See Java 5 installation help for more information.
Welcome
The welcome screen just gives you some credits. Click next.
Readme
The readme gives you important information about this release. Following install the README is available in the installation directory. You may wish to copy and paste it for reference during the install process. After you have read the information press next.
GNU Lesser General Public License
Buni Meldware Communications Suite is available under the LGPL free/open source license. See the License section for more details.
Installation Directory
Choose the base installation directory for Meldware Communications Suite. A popup will tell you that the directory must be created. The rest of these instructions refer to this directory as $INSTALL Click next.
Packs Screen
The next screen asks you to select from a list of required and optional packages. If you are using one of the databases listed (MySQL and PostgreSQL) then ensure that database is selected. If you use a different database then you will need to download the "Java Database Connectivity" package for that database to the $INSTALL/server/default/lib directory. Base and JBoss Application Server are required for MCS. We recommend that you also install the calendar server if you wish to utilize the webmail functionality. Once you've selected the right mix of packs for your installation click next.
SMTP Service
SMTP is the protocol used to send emails. The installer allows you to configure one instance of regular SMTP for both incoming and outgoing email. Ensure "enable SMTP" is checked and that the port is 25 if you wish to allow the Internet to send your mail server email.
If you will use this (rather than SMTP/SSL) same port for your local mail server users to send mails to the Internet or each other then you may wish to utilize a combination of the next three options. TLS is basically SSL encryption initiated by the client rather than via a dedicated port (ala SMTP/SSL). "TLS enabled" means that clients have the ability to request TLS encryption. "TLS required" means that ALL clients MUST request TLS (do not use this if you wish to allow incoming emails from other servers over this port). "TLS required for authentication" means that local users who wish to send mail out must first require TLS authentication. Unfortunately, not all email clients support this standard.
Authentication allowed when checked allows local users to authenticate to send mail to the Internet and to each other via this port. If you intend to require local users to use SMTP/SSL then you may wish to uncheck this to prevent them from sending mail on this port. (Meldware Mail does not allow unauthenticated users to send mail)
Verify Identity means that the server prevents the "From" on emails from being forged by authenticated users. This makes the server a bit picky on "who" you can send mail as. Generally this is a useful option to enhance security.
Once you've selected the options that you require for regular SMTP click next.
SMTP/SSL
SMTP over SSL is a dedicated encrypted instance of SMTP. It can only be used for local users to send outgoing mail. If you wish to provide this service check "Enable SMTP/SSL". Port 465 is the traditional port.
Verify Identity means that the server prevents the "From" on emails from being forged by authenticated users. This makes the server a bit picky on "who" you can send mail as. Generally this is a useful option to enhance security.
Once you've selected the options that you require for SMTP/SSL click next.
SMTP Relaying
By default Meldware Mail does not allow unauthenticated users to send mail except to local users (as happens when they receive mails from the Internet), however, you can configure it to allow unauthenticated emails to be relayed to a set group of domains. The Installer allows you to configure up to four domains, however, more are possible through manual configuration. If you wish to make use of this option select "Allow relaying by domain" and enter the domains you wish to allow relaying to. Click next when you are finished.
SMTP Route
If you wish to require all mails from your server to travel through a gateway sever then check "Enable SMTP Routing" and enter the gateway server address or IP.
Additionally, you can require ONLY emails to certain domains to go through the gateway. In that case check "Route only the below domains" and enter the domains that you require to go through the gateway (the installer allows you to have 4, but more are possible via manual configuration after installation).
Click next when you are finished.
POP3 Service
POP3 allows users to download their email from the server for offline viewing. Traditionally this service is provided on port 110. It can be considered an augment or alternative to IMAP which allows users to read mails on or off the mail server. If you wish to provide POP then check "Enable POP".
POP can also allow or allow and require TLS. Most mail clients do not yet support POP/TLS (Thunderbird does). As an alternative you can enabled POP/SSL (next). Once you have selected your desired options click next.
POP/SSL
POP/SSL provides POP service on a dedicated encrypted port (traditionally 995). If you wish to provide this service check "enable POP/SSL" and click next.
IMAP Configuration
IMAPv4rev1 provides robust mailbox services to local users allowing them to have multiple folders on the server and read mails both on and off of the server. IMAP is also a very heavy protocol with inconsistent support among various mail clients. IMAP is traditionally provided on port 143. Note that in this release IMAP is considered BETA or ALPHA quality and has only been tested extensively with Mozilla Thunderbird.
If you wish to provide IMAP services then check "Enable IMAP" and click next.
DNS Configuration
Your mail server will need to contact DNS servers to determine the location of various mail servers to send mail to. On UNIX operating systems if you do not fill this screen out then your "default route" will be used instead. On Windows you MUST fill this screen out or you will not be able to send outbound mail. The installer allows you to configure 4 DNS servers, more are configurable manually (though that would be uncommon). Enter your DNS servers (or not) and click next.
Server Name Configuration
Meldware Mail supports virtual hosting. Users are allowed to have multiple email addresses for different domains. Secondly you can have the same address on different domains refer to a different user. The installer allows you to configure 6 domains. More are possible via manual installation. Note that "mail.buni.org" is treated separately from "buni.org". The server will reject incoming mail sent to any domain that is not in this list regardless of user aliases.
You must also enter the server's name.
You must also enter the bind address (or leave the default 0.0.0.0). The installer configures all services to listen on this bind address. 0.0.0.0 means ALL addresses. On multi-homed machines with multiple network interface cards this allows you to configure mail services on one IP address and not the other. You may also only wish to configure IMAP, POP, and SMTP/SSL on the LAN and straight unauthenticated SMTP for the Internet. This is possible via manual configuration.
Finally, you must configure a postmaster address. Various notices will be delivered to this address (traditionally "postmaster" prefixing your primary domain).
Click next when you have properly configured your server name, bind address and domains.
Datasource
Meldware Communication Suite stores mailbox and calendar data in the database. These require a datasource configuration. For testing purposes you can use the Java database "Hypersonic" although it is NOT recommended for production purposes. In that case just click next without changing any options (do NOT select generate datasource).
If you are using one of the databases noted then click "Generate datasource" and select that database and name it something other than "DefaultDS". You must also enter the account details (database user, password, host and the instance name). If you are using a different database than those supported by the installer, select the "closest one" and edit the $INSTALL/server/default/deploy/"postgres-ds.xml" for instance, manually after installation.
Click next when you are happy with your datasource configuration.
FileStore
Meldware Mail is able to use your database for both mailbox data as well as the actual emails themselves. These are generally stored as Binary Large Objects (BLOBs) in the database. Some databases support blobs better than others and have better performance with BLOBs. (MySQL, for instance, has especially poor blob support). Meldware Mail is also able to store your mail on the filesystem. If you prefer filesystem mail part storage select File and enter a base directory. Note that the installer does not create this directory for you. You must manually create it post installation or you will get an error when starting the server (the default is $INSTALL/server/default/data which IS created on server start). If you prefer the database to store all of your data then select Database instead.
Note: The filestore is experimental and makes its first appearance in this release.
SSL key
If you enabled any SSL or TLS services in the screens above you will need a keystore and certificate. The installer can generate one for you, however, it will be a self-signed certificate and clients will warn users that it is not from a trusted key vendor (i.e Thawt or Verisign). Generally this is okay for internal use (such as SMTP/POP is). However, you can go buy a certificate and install it (post installation).
If you wish to generate the store:
- Leave the name to the default
- enter a different keystore password
- ensure "Generate Keystore" is checked.
- Fill in the rest of the requested information
Click next when you are finished configuring the keystore information.
Accounts
The installer configures MCS with a text-based account repository and a set of initial accounts which you can provide here. While this is great for evalIt is suggested that you change this to database or LDAP based authentication post installation. You can enter up to 4 account/password combos here. Many more are possible. Click next when you have configured your initial accounts.
Calendar
The calendar server can create email notification events when appointments are scheduled, accepted or rejected. If you wish to utilize this feature click "create calendar notification account" and select a name and password for the calendar mail user. Select the email type for the notification events (note in this release the webmail does not render HTML mail so you may wish to take that into account). You must then configure the URL root for the notification events. For instance if the server name is www.crashalot.com and the HTTP listener is on Meldware's default HTTP port 8080 then it would be http://www.crashalot.com:8080.
Click next when you are finished configuring calendar notification mails.
Fetchmail
For personal mail servers sometimes it is useful to retrieve mail from another server via POP and put it in the local server's mailboxes for a user. The installer allows you to set up one instance of fetchmail for one user (many more are possible by copying the example configuration created). If you wish to utilize this feature click "Enable Fetchmail" and enter the address of the external pop3 server, its port (usually 110), the external server's mail user for the account you wish to retrieve the mail from and its password.
Next enter the local user's email address.
Next, select whether you will retrieve the email and then delete it from the external server or just retrieve it.
Finally, enter how often you wish to poll the external server (default = 2 minutes aka 120 seconds).
Click next.
Pack Installation
Next you'll see the packs installed. Once it completes successfully click next.
Congrats
The Congrats screen tells you to come to this manual for more information and how to run the software. Click next.
Final
The final screen allows you to generate a headless install script and tells you where the uninstall script is for when you wish to upgrade. Click next.
Post Installation
After installation there are a number of things that you might want to do in order to create a production instance.
- Allocate more memory to MCS
- Switch to database or LDAP security
- Install a JDBC driver
- Install a different datasource
- Secure the JBossAS
- Change JMS persistence settings
Configuring Meldware
Configuration File Overview
The primary Meldware configuration file is located at $INSTALL/server/default/deploy/mail.ear/mail.sar/META-INF/jboss-service.xml. It contains nearly all of the configuration necessary to configure MCS. All Meldware Mail components are MBean and are configured using the JBoss JMX Microkernel. Refer to the JBoss Application Server Guide for more information on JBoss JMX.
Message Persistence
The Meldware Mail Server splits its persistence into 2 areas, the main persistent store built on the EJB3 persistence API, used for folders, mailboxes and the like, and the streaming store, used for storing mail bodies. There are a number of different implementations of the Store, including file and database persistence options.
Configuring EJB3 Persistence
The configuration for the main EJB3 persistent store is held in the in the $INSTALL/server/default/deploy/mail.ear/mail.par/META-INF/persistence.xml. A typical configuration will look like the following.
<persistence>
<persistence-unit name="mail">
<jta-data-source>java:/DefaultDS</jta-data-source>
<properties>
<property name="jboss.entity.manager.jndi.name"
value="java:/EntityManagers/mail"/>
<property name="hibernate.dialect"
value="org.hibernate.dialect.HSQLDialect"/>
<property name="hibernate.hbm2ddl.auto"
value="update"/>
</properties>
</persistence-unit>
</persistence>
The most important options are jta-data-source which define which datasource to use when connecting to the database. If the datasource is changed such that a different database product is being used then the hibernate.dialect option should also be updated. Consult the Hibernate Documentation for more information on the persistence options.
Store Options
There are 4 options for the Store:
- File Store, file based persistence.
- Paged Store, generic database store for database without good BLOB/Locator support (Hypersonic SQL, MySQL).
- JDBC3 Store, uses the JDBC Blob class (Oracle)
- PG Store, uses the PostgreSQL specific Large Object API.
Common Configuration Options
| Option | Type | Description |
|---|---|---|
| PageSize | Integer | The size of the page used for buffering within the store input/output streams. |
| Compress | Boolean | Whether to compress the items in the store. |
| CompressBufferSize | Integer | The size of the buffer used for compression. |
| StartIndex | Integer | The value to start reading from. Some stores (Oracle JDBC) start at 1 rather than 0. |
| Hashed | Boolean | Set to false, this will be used in a later release. |
Configuring File Store
The configuration for the File Store MBean looks like the following.
<mbean code="org.buni.meldware.mail.store.file.FileStoreImpl"
name="meldware.mail:type=MailServices,name=FileStore"
mbean-dd="META-INF/FileStore-xmbean.xml">
<attribute name="Path">${jboss.server.dir}/server/default/data</attribute>
<attribute name="AttemptsPerAllocate">1</attribute>
<attribute name="PageSize">65535</attribute>
<attribute name="Compress">true</attribute>
<attribute name="CompressBufferSize">65535</attribute>
<attribute name="StartIndex">0</attribute>
<attribute name="Hashed">false</attribute>
</mbean>
| Option | Type | Description |
|---|---|---|
| AttemptsPerAllocate | Integer | The number of attemps made to create a file. |
| Path | String | The location on disk to store the data |
Configuring Paged Store
The configuration for the PagedStoreMBean looks like following
<mbean code="org.buni.meldware.mail.store.paged.PagedStore" name="meldware.mail:type=MailServices,name=PagedStore"> <attribute name="PageSize">65535</attribute> <attribute name="Compress">true</attribute> <attribute name="CompressBufferSize">65535</attribute> <attribute name="StartIndex">0</attribute> <attribute name="Hashed">false</attribute> </mbean>
There are no specific options for the paged store.
Configuring JDBC3 Store
The configuration for the JDBC3 Store looks like the following
<mbean code="org.buni.meldware.mail.store.jdbc3.JDBC3Store"
name="meldware.mail:type=MailServices,name=JDBC3Store,db=Oracle">
<attribute name="PageSize">32384</attribute>
<attribute name="Compress">false</attribute>
<attribute name="CompressBufferSize">8192</attribute>
<attribute name="ReadStatement">
SELECT ID, DATA FROM BLOB_MAIL_STORE WHERE ID = ?
</attribute>
<attribute name="WriteStatement">
SELECT ID, DATA FROM BLOB_MAIL_STORE WHERE ID = ? FOR UPDATE
</attribute>
<attribute name="IdColumn">ID</attribute>
<attribute name="BlobColumn">DATA</attribute>
<attribute name="UseStreams">false</attribute>
<attribute name="Connected">false</attribute>
<attribute name="StartIndex">1</attribute>
</mbean>
| Option | Type | Description |
|---|---|---|
| ReadStatement | String | The SQL to execute to read from the JDBC3 Blob |
| ReadStatement | String | The SQL to execute to write to the JDBC3 Blob, note that most DB implemenations (including Oracle) require an exclusive lock. |
| IdColumn | String | The name of the column holding the id. |
| BlobColumn | String | The name of the column holding actual blob |
| UseStreams | Boolean | Whether the store should create a stream, rather than do block based writing to the blob. |
| Connected | Boolean | If set to true the store will hold open the stream to the blob during the entire transaction. |
Configuring PG Store
The configuration for the Postgres Store looks like the following
<mbean code="org.buni.meldware.mail.store.postgresql.PostgreSQLStore" name="meldware.mail:type=MailServices,name=PostgreSQLStore"> <attribute name="Disconnected">true</attribute> <attribute name="DataSource">java:/PostgresDS</attribute> <attribute name="PageSize">131072</attribute> </mbean>
| Option | Type | Description |
|---|---|---|
| DataSource | String | The name of the datasource to use. |
Configuring Security
Security in Meldware is managed through the UserRepository module, which can have a number of different implemenations.
Options
The currently supported UserRepository imeplemenations are:
- Static User Repository, where users are specified in the MBean configuration.
- JAAS User Reposotory, which reuses the standard java security mechanism.
JAAS User Repository
The JAAS User Repository uses the JAAS support provided by the JBoss Appplication Server. JBoss provied the following mechanisms for supporting JAAS:
- Properties files
- Database tables
- LDAP
The JAAS User Repository is configured as follows:
<mbean code="org.buni.meldware.mail.userrepository.jaas.JaasUserRepository" name="meldware.mail:type=MailServices,name=UserRepository,uimanageable=true"> <depends>jboss.security:service=JaasSecurityManager</depends> <depends>meldware.mail:type=SecurityConfig,name=LoginConfig</depends> <attribute name="SecurityDomain">meldware</attribute> </mbean>
Properties
The default configuration of Meldware uses properies files to hold the username/password pairs, it is as follows:
<mbean code="org.jboss.security.auth.login.DynamicLoginConfig"
name="meldware.mail:type=SecurityConfig,name=LoginConfig">
<attribute name="PolicyConfig" serialDataType="jbxb">
<jaas:policy
xsi:schemaLocation="urn:jboss:security-config:4.1
resource:security-config_4_1.xsd"
xmlns:jaas="urn:jboss:security-config:4.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<jaas:application-policy name="meldware">
<jaas:authentication>
<jaas:login-module
code="org.jboss.security.auth.spi.UsersRolesLoginModule"
flag="required">
<jaas:module-option
name="usersProperties">meldware-users.properties</jaas:module-option>
<jaas:module-option
name="rolesProperties">meldware-roles.properties</jaas:module-option>
<jaas:module-option
name="unauthenticatedIdentity">nobody</jaas:module-option>
</jaas:login-module>
</jaas:authentication>
</jaas:application-policy>
</jaas:policy>
</attribute>
<depends optional-attribute-name="LoginConfigService">
jboss.security:service=XMLLoginConfig
</depends>
<depends optional-attribute-name="SecurityManagerService">
jboss.security:service=JaasSecurityManager
</depends>
</mbean>
The important attribute is "userProperties" as it holds the username/password pairs. Meldware does not use the "rolesProperties" as it does not use JAAS roles.
Database
Edit $INSTALL/server/default/deploy/mail.ear/mail.sar/META-INF/jboss-service.xml. Find a section that looks like this:
<mbean code="org.jboss.security.auth.login.DynamicLoginConfig"
name="meldware.mail:type=SecurityConfig,name=LoginConfig">
<attribute name="PolicyConfig" serialDataType="jbxb">
<jaas:policy
xsi:schemaLocation="urn:jboss:security-config:4.1 resource:security-config_4_1.xsd"
xmlns:jaas="urn:jboss:security-config:4.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>
<jaas:application-policy name="meldware">
<jaas:authentication>
<jaas:login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule"
flag="required">
<jaas:module-option name="usersProperties">meldware-users.properties</jaas:module-option>
<jaas:module-option name="rolesProperties">meldware-roles.properties</jaas:module-option>
<jaas:module-option name="unauthenticatedIdentity">nobody</jaas:module-option>
</jaas:login-module>
</jaas:authentication>
</jaas:application-policy>
</jaas:policy>
</attribute>
<depends optional-attribute-name="LoginConfigService">
jboss.security:service=XMLLoginConfig
</depends>
<depends optional-attribute-name="SecurityManagerService">
jboss.security:service=JaasSecurityManager
</depends>
</mbean>
and remove it. Add a section that looks like this in its stead:
<mbean code="org.jboss.security.auth.login.DynamicLoginConfig"
name="meldware.mail:type=SecurityConfig,name=LoginConfig">
<attribute name="PolicyConfig" serialDataType="jbxb">
<jaas:policy
xsi:schemaLocation="urn:jboss:security-config:4.1 resource:security-config_4_1.xsd"
xmlns:jaas="urn:jboss:security-config:4.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>
<jaas:application-policy name="meldware">
<jaas:authentication>
<jaas:login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule"
flag="required">
<jaas:module-option name="dsJndiName">java:/PostgresDS</jaas:module-option>
<jaas:module-option name="principalsQuery">SELECT PASSWD FROM MAIL_USERS WHERE USERID=?</jaas:module-option>
<jaas:module-option name="rolesQuery">SELECT ROLEID, 'Roles' FROM MAIL_ROLES WHERE USERID=?</jaas:module-option>
</jaas:login-module>
</jaas:authentication>
</jaas:application-policy>
</jaas:policy>
</attribute>
<depends optional-attribute-name="LoginConfigService">
jboss.security:service=XMLLoginConfig
</depends>
<depends optional-attribute-name="SecurityManagerService">
jboss.security:service=JaasSecurityManager
</depends>
<depends>jboss.jca:service=ManagedConnectionFactory,name=PostgresDS</depends>
</mbean>
Replace PostgresDS with YOUR datasource name. Replace the queries with ones appropriate for your database. Ensure that you have created the tables mentioned in the query. On postgresql you would execute queries that looked like this in order to match the above structure:
CREATE TABLE mail_users (
userid character varying, passwd character varying
);
CREATE TABLE mail_roles (
roleid character varying, userid character varying
);
Note that a user must have at LEAST one role in order to authenticate. Generally:
INSERT INTO mail_roles (roleid, userid) VALUES ('calendaruser', 'acoliver');
Refer to the JBoss Application Server Guide for more details on configuring JAAS database configuration.
LDAP
Refer to the JBoss Application Server Guide to configure JAAS LDAP configuration.
Manually Configuring Datasources
Datasources a creating using a *-ds.xml file, e.g. postgres-ds.xml. As a convenience the JBoss Application Server supplies templates that can be useful when configuring Meldware for different databases. Look at the $INSTALL/docs/examples/jca directory. The files are name by <database>-ds.xml. Copy the file specific the database that you are moving to to $INSTALL/server/default/deploy/meldware-ds.xml. Edit the meldware-ds.xml and add the configuration setting for your database.
