Resolution:
The basic things you have to do to enable multicast is:

Enable the Server for Multicast
========================
To begin, some general settings must be configured in the EMS server's main configuration file, tibemsd.conf:
¿ Enable multicast in the server by setting multicast=enabled.
¿ Enable multicast in the console trace by setting console_trace=+MULTICAST.
While enabling this trace is not required, it is very useful during the initial deployment, providing multicast-related warnings and errors.
¿ Enable flow control by setting flow_control=enabled.
Under heavy load, it is possible for publishers to feed data into the server faster than the server can multicast the data out. Enabling flow control causes the server to push back on the publishers, slowing them down if the server falls behind. This is not required, but highly suggested because it gives the server some room to minimize loss if this happens.
You should have added the following lines to the tibemsd.conf:
    multicast=enabled
    console_trace= DEFAULT,+MULTICAST
    flow_control=enabled

Configure Multicast Channels
=======================

The next step configures the multicast channels. In this example there are two multicast channels, mcast-1Gb and mcast-100Mb.
The section Sample channels.conf Settings below shows specific settings for these steps:

1. Create the channels.conf file. This file is described in channels.conf .
2. Create two channels in the channels.conf file, [mcast-1Gb] and [mcast-100Mb].
3. Set the address and destination port for each channel, using the address parameter.
4. Set the interface for each channel, using the interface parameter.
   For this example, the server is on a multi-homed machine so we must explicitly specify interfaces for each
   channel. If an interface is not specified, the EMS server uses the default interface. Note that    this is also
    true for the multicast daemon. Use the -ifc command line parameter when running multicast daemons on
     multi-homed machines, described in Command Line Options.
5. Set a maxrate for each channel.
    The maxrate parameter restricts the rate at which the server sends messages over the channel. See Estimating
     the Maxrate below for a discussion of how the maxrate was determined. Sample channels.conf Settings
    When you have completed your channel configuration, the channels.conf file should contain the following lines:
[mcast-1Gb]
    address=239.1.1.1:10
    interface=10.99.99.99
    maxrate=112MB

[mcast-100Mb]
    address=239.1.1.2:10
    interface=10.99.99.100
    maxrate=8MB

Creating a Multicast Consumer
=========================

The EMS client is enabled for multicast by default, and no special configuration is required. To receive multicast data, the
client need only create a multicast consumer by subscribing to a multicast-enabled topic using the NO_ACKNOWLEDGE
mode, as described in Message Acknowledgement. You can also disable multicast in a client, using API calls. For more
information, see the API documentation for your language.


Starting the Multicast Daemon
========================

The multicast daemon is located in your installation_path /bin directory and is a stand-alone executable named
tibemsmcd on UNIX and tibemsmcd.exe on Windows platforms. You have to run this on the machine where you
are running the client. Every client node should be running this daemon.