Ultra Messaging® Quick Start Guide

2.1. Binary Quick Start on Microsoft® Windows®

The following steps assume that the windows package is installed on all test machines in the standard place:

C:\Program Files\29West\rel-id\Win2k-i386

where rel-id is the release identifier. It is also assumed that the \bin directory is included in the windows PATH environment variable. This is needed so that the .EXE and .DLL files can be found.

1. Open a command prompt window on the machine you want to use for receiving messages and enter the command lbmrcv topic to start a receiver. Note that topic can be any string. You should see output that looks something like this:

   1.006 secs.   0.0 Kmsgs/sec.   0.0 Kbps
   1.019 secs.   0.0 Kmsgs/sec.   0.0 Kbps
   1.010 secs.   0.0 Kmsgs/sec.   0.0 Kbps
   

   A new line will be printed about once per second showing the elapsed time, messages received, and data received. As long as there are no sources yet running on topic, the number of messages received will continue to be zero.

2. Open a command prompt window on the machine you want to use for sending messages and enter the command lbmsrc topic to start sending messages. The receiver will automatically discover the source, at which time its output will change to something like this:

   1.010 secs. 451.9 Kmsgs/sec.  90.4 Mbps
   1.010 secs. 451.4 Kmsgs/sec.  90.3 Mbps
   1.010 secs. 445.1 Kmsgs/sec.  89.0 Mbps
   

3. With no options given, the source will send 10,000,000 small (25 byte) messages. If you would like to test different size packets or number of packets sent, you can set options. Enter lbmsrc -h at the command line, you will get a list of options you can control.

4. Press Ctrl-C to kill the source or receiver.

2.2. Binary Quick Start on Unix

The following steps assume that the Unix package is installed on all test machines under a normal user account:

/home/user-id/lbmeval/rel-id/platform-id

where rel-id is the release identifier and platform-id describes the ABI (Application Binary Interface - e.g. Linux-2.4-glibc-2.2-i686). It is also assumed that the /bin directory is included in the PATH environment variable and the /lib directory is in the appropriate loader library search path environment variable (e.g. LD_LIBRARY_PATH for Linux; see http://bhami.com/rosetta.html for equivalences in other flavors of Unix).

1. Open a command prompt window on the machine you want to use for receiving messages and enter the command lbmrcv topic to start a receiver. Note that topic can be any string. You should see output that looks something like this:

   1.006 secs.   0.0 Kmsgs/sec.   0.0 Kbps
   1.019 secs.   0.0 Kmsgs/sec.   0.0 Kbps
   1.010 secs.   0.0 Kmsgs/sec.   0.0 Kbps
   

   A new line will be printed about once per second showing the elapsed time, messages received, and data received. As long as there are no sources yet running on topic, the number of messages received will continue to be zero.

2. Open a command prompt window on the machine you want to use for sending messages and enter the command lbmsrc topic to start sending messages. The receiver will automatically discover the source, at which time its output will change to something like this:

   1.010 secs. 451.9 Kmsgs/sec.  90.4 Mbps
   1.010 secs. 451.4 Kmsgs/sec.  90.3 Mbps
   1.010 secs. 445.1 Kmsgs/sec.  89.0 Mbps
   

3. With no options given, the source will send 10,000,000 small (25 byte) messages. If you would like to test different size packets or number of packets sent, you can set options. Enter lbmsrc -h at the command line, you will get a list of options you can control.

4. Press Ctrl-C to kill the source or receiver.

2.3. Binary Evaluation Notes

1. There are many other example programs available. See doc/example/index.html for documentation on all of them.

2. For general information on measuring performance, see the UM Knowledgebase article Performance Testing.

3. For information on testing the LBT-RM (multicast) transport, see the following UM Knowledgebase articles:

   • Testing with LBT-RM

   • Interpreting LBT-RM Source Statistics

   • Tuning LBT-RM

4. Microsoft has batching issues in its networking stack, so the performance results can vary. We have a work around if this is an issue for you.

5. The Linux version was compiled on Fedora Core 1.

6. The Windows version was compiled on Windows XP with Microsoft Visual C++ version 7.

3.1. Minimal Ultra Messaging Source Implementation

This is a source code listing of a minimal source (sender) program. You may find it helpful to download the source code (most browsers let you right-click on the link and use the save link target function, or some variation). We also have equivalent Java and C# programs available in source form. See MinSrc.java and MinSrc.cs.

/*file: minsrc.c - minimal source (sender) program.
 *
 * Copyright (c) 2005-2014 Informatica Corporation. All Rights Reserved.
 * Permission is granted to licensees to use
 * or alter this software for any purpose, including commercial applications,
 * according to the terms laid out in the Software License Agreement.
 */

#include <stdio.h>

#if defined(_MSC_VER)
/* Windows-only includes */
#include <winsock2.h>
#define SLEEP(s) Sleep((s)*1000)
#else
/* Unix-only includes */
#include <stdlib.h>
#include <unistd.h>
#define SLEEP(s) sleep(s)
#endif

#include <lbm/lbm.h>

main()
{
    lbm_context_t *ctx;    /* pointer to context object */
    lbm_topic_t *topic;    /* pointer to topic object */
    lbm_src_t *src;        /* pointer to source (sender) object */
    int err;               /* return status of lbm functions (true=error) */

#if defined(_MSC_VER)
    /* windows-specific code */
    WSADATA wsadata;
    int wsStat = WSAStartup(MAKEWORD(2,2), &wsadata);
    if (wsStat != 0)
    {
        printf("line %d: wsStat=%d\n",__LINE__,wsStat);
        exit(1);
    }
#endif

    err = lbm_context_create(&ctx, NULL, NULL, NULL);   
    if (err)
    {
        printf("line %d: %s\n", __LINE__, lbm_errmsg());
        exit(1);
    }

    err = lbm_src_topic_alloc(&topic, ctx, "Greeting", NULL);   
    if (err)
    {
        printf("line %d: %s\n", __LINE__, lbm_errmsg());
        exit(1);
    }

    err = lbm_src_create(&src, ctx, topic, NULL, NULL, NULL);   
    if (err)
    {
        printf("line %d: %s\n", __LINE__, lbm_errmsg());
        exit(1);
    }

    SLEEP(3);   

    err = lbm_src_send(src, "Hello!", 6, LBM_MSG_FLUSH | LBM_SRC_BLOCK);   
    if (err)
    {
        printf("line %d: %s\n", __LINE__, lbm_errmsg());
        exit(1);
    }

    /* Finished all sending to this topic, delete the source object. */
    SLEEP(2);   
    lbm_src_delete(src);

    /* Do not need to delete the topic object - LBM keeps track of topic
     * objects and deletes them as-needed.  */

    /* Finished with all LBM functions, delete the context object. */
    lbm_context_delete(ctx);

#if defined(_MSC_VER)
    WSACleanup();
#endif
}  /* main */

Notes:

3.2. Minimal Ultra Messaging Receiver Implementation

This is a source code listing of a minimal receiver program. You may find it helpful to download the source code (most browsers let you right-click on the link and use the save link target function, or some variation). We also have equivalent Java, C#, and C++ programs available in source form. See MinRcv.java MinRcv.cs and minrcv.cpp.

/*file: minrcv.c - minimal receiver program.
 *
 * Copyright (c) 2005-2014 Informatica Corporation. All Rights Reserved.
 * Permission is granted to licensees to use
 * or alter this software for any purpose, including commercial applications,
 * according to the terms laid out in the Software License Agreement.
 */

#include <stdio.h>

#if defined(_MSC_VER)
/* Windows-only includes */
#include <winsock2.h>
#define SLEEP(s) Sleep((s)*1000)
#else
/* Unix-only includes */
#include <stdlib.h>
#include <unistd.h>
#define SLEEP(s) sleep(s)
#endif

#include <lbm/lbm.h>

/*
 * A global variable is used to communicate from the receiver callback to
 * the main application thread.
 */
int msgs_rcvd = 0;

int app_rcv_callback(lbm_rcv_t *rcv, lbm_msg_t *msg, void *clientd)   
{
    /* There are several different events that can cause the receiver callback
     * to be called.  Decode the event that caused this.  */
    switch (msg->type)
    {
    case LBM_MSG_DATA:    /* a received message */
        printf("Received %d bytes on topic %s: '%.*s'\n",   
               msg->len, msg->topic_name, msg->len, msg->data);

        /* Tell main thread that we've received our message. */
        ++ msgs_rcvd;
        break;

    case LBM_MSG_BOS:
    printf("[%s][%s], Beginning of Transport Session\n", msg->topic_name, msg->source);
    break;

    case LBM_MSG_EOS:
    printf("[%s][%s], End of Transport Session\n", msg->topic_name, msg->source);
    break;
    
    default:    /* unexpected receiver event */
        printf("Received lbm_msg_t type %x [%s][%s]\n", msg->type, msg->topic_name, msg->source);
        break;
    }  /* switch msg->type */

    return 0;
}  /* app_rcv_callback */


main()
{
    lbm_context_t *ctx;    /* pointer to context object */
    lbm_topic_t *topic;    /* pointer to topic object */
    lbm_rcv_t *rcv;        /* pointer to receiver object */
    int err;               /* return status of lbm functions (true=error) */

#if defined(_MSC_VER)
    /* windows-specific code */
    WSADATA wsadata;
    int wsStat = WSAStartup(MAKEWORD(2,2), &wsadata);
    if (wsStat != 0)
    {
        printf("line %d: wsStat=%d\n",__LINE__,wsStat);
        exit(1);
    }
#endif

    err = lbm_context_create(&ctx, NULL, NULL, NULL);   
    if (err)
    {
        printf("line %d: %s\n", __LINE__, lbm_errmsg());
        exit(1);
    }

    err = lbm_rcv_topic_lookup(&topic, ctx, "Greeting", NULL);   
    if (err)
    {
        printf("line %d: %s\n", __LINE__, lbm_errmsg());
        exit(1);
    }

    err = lbm_rcv_create(&rcv, ctx, topic, app_rcv_callback, NULL, NULL);   
    if (err)
    {
        printf("line %d: %s\n", __LINE__, lbm_errmsg());
        exit(1);
    }

    while (msgs_rcvd == 0)
        SLEEP(1);

    /* Finished all receiving from this topic, delete the receiver object. */
    lbm_rcv_delete(rcv);

    /* Do not need to delete the topic object - LBM keeps track of topic
     * objects and deletes them as-needed.  */

    /* Finished with all LBM functions, delete the context object. */
    lbm_context_delete(ctx);

#if defined(_MSC_VER)
    WSACleanup();
#endif
}  /* main */

Notes:

5.1. Configure Your Environment to Run Ultra Messaging JMS Examples

5.2. Microsoft Windows or Unix

All source for the following example applications is Java.

• If you are running on Microsoft Windows you will execute a .bat file.

• If you are running a Unix system, you will execute a .sh file.

5.3. Demonstrating Request/Reply

Follow the steps below to demonstrate Ultra Messaging JMS request/reply. This demonstration uses Reply.java and Request.java source files and requires a UME server.

1. Open a command prompt window and enter the command reply.sh or reply.bat for Microsoft Windows.

2. Open a second command prompt window and enter the command request.sh or request.bat for Microsoft Windows.

3. You will see output that indicates the message has been sent back and forth. Press Ctrl-C to kill either application.

5.4. Demonstrating Synch and Async Reads

Follow the steps below to demonstrate Ultra Messaging JMS synchronous and asynchronous message delivery. This demonstration uses AsyncConsumer.java, Producer.java and SyncConsumer.java source files.

1. Open a command prompt window and enter the command AsyncConsumer.sh or AsyncConsumer.bat for Microsoft Windows.

2. Open a second command prompt window and enter the command Producer.sh or Producer.bat for Microsoft Windows.

3. Open a third command prompt window and enter the command SyncConsumer.sh or SyncConsumer.bat for Microsoft Windows.

For the Producer, you will see output similar to the following.

Sent ********* This is a test *********** 
Sent ********* This is a test *********** 
Sent ********* This is a test *********** 
Sent ********* This is a test *********** 
Sent ********* This is a test *********** 
Sent ********* This is a test *********** 
Sent ********* This is a test *********** 
Sent ********* This is a test *********** 
Sent ********* This is a test *********** 
Sent ********* This is a test *********** 
   

For the AsyncConsumer and the SyncConsumer, you will see output similar to the following.

Received message: ********* This is a test ***********
Received message: ********* This is a test ***********
Received message: ********* This is a test ***********
Received message: ********* This is a test ***********
Received message: ********* This is a test ***********
Received message: ********* This is a test ***********
Received message: ********* This is a test ***********
Received message: ********* This is a test ***********
Received message: ********* This is a test ***********
Received message: ********* This is a test *********** 
   

Press Ctrl-C to kill any application.

5.5. Demonstrating A Durable Consumer

Follow the steps below to demonstrate Ultra Messaging JMS durable consumer messaging. This demonstration uses DurableConsumer.java and DurableProducer.java source files and requires a UME server.

1. Open a command prompt window and enter the command DurableConsumer.sh or DurableConsumer.bat for Microsoft Windows.

2. Open a second command prompt window and enter the command DurableProducer.sh or DurableProducer.bat for Microsoft Windows. The DurableProducer sends 20 messages.

3. In the command prompt window for the DurableConsumer, you should see output similar to the following.

   Reading message: This is message 1
   Reading message: This is message 2
   Reading message: This is message 3
   Reading message: This is message 4
   Reading message: This is message 5
   Reading message: This is message 6
   Reading message: This is message 7
   Reading message: This is message 8
      
   

4. After message 8, press Ctrl-C to kill the DurableConsumer. Then restart the consumer. The remaining 12 messages sent by the DurableProducer appear in the window.

   Reading message: This is message 9
   Reading message: This is message 10
   Reading message: This is message 11
   Reading message: This is message 12
   Reading message: This is message 13
   Reading message: This is message 14
   Reading message: This is message 15
   Reading message: This is message 16
   Reading message: This is message 17
   Reading message: This is message 18
   Reading message: This is message 19
   Reading message: This is message 20
      
   

5.6. Demonstrating UMQ

Follow the steps below to demonstrate Ultra Messaging JMS queuing. This demonstration uses QueueReceiver.java and QueueSender.java.java source files and requires a UMQ server.

1. Open two command prompt windows and in each window, enter the command QueueReceiver.sh or QueueReceiver.bat for Microsoft Windows.

2. Open a third command prompt window and enter the command QueueSender.sh or QueueSender.bat for Microsoft Windows. The QueueSender sends 15 messages; odd numbered messages go to the QueueReceiver in Window 1 and even numbered messages to QueueReceiver in Window 2.

   Output for QueueReceiver in Window 1.

   Reading message: This is message 1
   Reading message: This is message 3
   Reading message: This is message 5
   Reading message: This is message 7
   Reading message: This is message 9
   Reading message: This is message 11
   Reading message: This is message 13
   Reading message: This is message 15
      
   

   Output for QueueReceiver in Window 2.

   Reading message: This is message 2
   Reading message: This is message 4
   Reading message: This is message 6
   Reading message: This is message 8
   Reading message: This is message 10
   Reading message: This is message 12
   Reading message: This is message 14 
      
   

Press Ctrl-C to kill any application.

5.7. Other Example Applications

1. MyExceptionListener.java

2. MyListener.java

3. Ping.java

   To achieve lower latency for this example application, you should change the value of implicit_batching_minimum_length from 2000 to 1 in the config.xml file.

4. Pong.java

   To achieve lower latency for this example application, you should change the value of implicit_batching_minimum_length from 2000 to 1 in the config.xml file.

5. SimpleBytePublisher.java

6. SimpleByteSubscriber.java

7. SimpleDestinationPublisher.java

8. SimpleDestinationSubscriber.java

9. SimpleMapPublisher.java

10. SimpleMapSubscriber.java

11. SimpleObjectPublisher.java

12. SimpleObjectSubscriber.java

13. SimpleTopicPublisher.java

14. SimpleTopicSubscriber.java

15. Version.java

6.1. Ultra Messaging JMS Synchronous Consumer Implementation

This is a source code listing of a simple synchronous consumer program. You may find it helpful to download the source code (most browsers let you right-click on the link and use the save link target function, or some variation).

/*file: SimpleSyncConsumer.java
 *
 * Copyright (c) 2005-2014 Informatica Corporation. All Rights Reserved.
 * Permission is granted to licensees to use
 * or alter this software for any purpose, including commercial applications,
 * according to the terms laid out in the Software License Agreement.
 */
package examples;

   
import javax.jms.*;
import javax.naming.*;

public class SyncConsumer implements ExceptionListener {

    public static void main(String[] args) {
        new SyncConsumer();
    }

    public SyncConsumer() {
        Context jndiContext = null;

        try {   
            jndiContext = new InitialContext();
        } catch (NamingException e) {
            System.out.println("Could not create JNDI API "
                    + "context: " + e.toString());
            e.printStackTrace();
            System.exit(1);
        }

        try {   
            ConnectionFactory factory = (ConnectionFactory) jndiContext.lookup("uJMSConnectionFactory");
            Connection connection = factory.createConnection();

            // Create a Session
            Session session = connection.createSession(false,
                    javax.jms.Session.AUTO_ACKNOWLEDGE);

            // set the exception listener callback
            connection.setExceptionListener(this);

            // Create a topic destination
            Destination destination = session.createTopic("TOPIC.1");

            // create the consumer
            MessageConsumer msgConsumer = session.createConsumer(destination);
            connection.start();

            while (true) {
                System.out.println("Received message " + msgConsumer.receive());
            }

        } catch (Exception ex) {
            ex.printStackTrace();
        }
    }

// The exception listener
    public void onException(JMSException e) {
        // print the connection exception status
        System.err.println("Exception occurred: " + e.getMessage());
    }
}

Notes:

6.2. Ultra Messaging JMS Asynchronous Consumer Implementation

This is a source code listing of a simple asynchronous consumer program. You may find it helpful to download the source code (most browsers let you right-click on the link and use the save link target function, or some variation).

/*file: SimpleAsyncConsumer.java
 *
 * Copyright (c) 2005-2014 Informatica Corporation. All Rights Reserved.
 * Permission is granted to licensees to use
 * or alter this software for any purpose, including commercial applications,
 * according to the terms laid out in the Software License Agreement.
 */
package examples;   

import javax.jms.*;
import javax.naming.*;

public class AsyncConsumer implements MessageListener, ExceptionListener {

    public static void main(String[] args) {
        new AsyncConsumer();
        while (true) {
            try {
                Thread.sleep(1000000);
            } catch (Exception ex) {
                ex.printStackTrace();
            }
        }
    }

    public AsyncConsumer() {
        Context jndiContext = null;

        try {   
            jndiContext = new InitialContext();
        } catch (NamingException e) {
            System.out.println("Could not create JNDI API "
                    + "context: " + e.toString());
            e.printStackTrace();
            System.exit(1);
        }

        try {   
            ConnectionFactory factory = (ConnectionFactory) jndiContext.lookup("uJMSConnectionFactory");
            Connection connection = factory.createConnection();

            // Create a Session
            Session session = connection.createSession(false,
                    javax.jms.Session.AUTO_ACKNOWLEDGE);

            // set the exception listener callback
            connection.setExceptionListener(this);

            // Create a topic destination
            Destination destination = session.createTopic("TOPIC.1");
            // create the consumer
            MessageConsumer msgConsumer = session.createConsumer(destination);

            // set the message listener callback
            msgConsumer.setMessageListener(this);
            // start the connection
            connection.start();
        } catch (Exception ex) {
            ex.printStackTrace();
        }
    }

// The exception listener
    public void onException(JMSException e) {
        // print the connection exception status
        e.printStackTrace();
    }

// The message listener callback
    public void onMessage(Message msg) {
        try {
            System.err.println("Received message: " + msg);
        } catch (Exception e) {
            System.err.println("Exception occurred: " + e.getMessage());
            System.exit(-1);
        }
    }
}

Notes:

6.3. Ultra Messaging JMS Simple Producer Implementation

This is a source code listing of a simple producer program. You may find it helpful to download the source code (most browsers let you right-click on the link and use the save link target function, or some variation).

/*file: SimpleProducer.java
 *
 * Copyright (c) 2005-2014 Informatica Corporation. All Rights Reserved.
 * Permission is granted to licensees to use
 * or alter this software for any purpose, including commercial applications,
 * according to the terms laid out in the Software License Agreement.
 */
package examples;

import javax.jms.*;   
import javax.naming.*;

public class Producer {

    public static void main(String[] args) {
        new Producer();
    }

    public Producer() {
        Context jndiContext = null;

        try {   
            jndiContext = new InitialContext();
        } catch (NamingException e) {
            System.out.println("Could not create JNDI API "
                    + "context: " + e.toString());
            e.printStackTrace();
            System.exit(1);
        }

        Connection connection = null;   
        try {
            ConnectionFactory factory = (ConnectionFactory) jndiContext.lookup("uJMSConnectionFactory");
            connection = factory.createConnection();
            Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
            connection.start();
            Destination destination = session.createTopic("TOPIC.1");
            MessageProducer producer = session.createProducer(destination);
            TextMessage message = session.createTextMessage();
            for (int i = 0; i < 10; i++) {
                ((TextMessage) message).setText("********* This is a test *********** ");
                producer.send(message);
                Thread.sleep(10);
                System.out.println("Sent " + message.getText());
            }
        } catch (Exception e) {
            System.out.println("JNDI API lookup failed: "
                    + e.toString());
            e.printStackTrace();
            System.exit(1);

        } finally {
            if (connection != null) {
                try {

                    connection.close();
                    System.exit(0);
                } catch (Exception e) {
                    e.printStackTrace();
                }
            }
        }
    }
}

Notes:

7.1. Ultra Messaging Gateway

The UM Gateway bridges disjoint topic resolution domains by forwarding multicast and/or unicast topic resolution traffic across gateways. Before installing and starting a gateway daemon (tnwgd) clear objectives and proper planning are very important. Approach this planning with the consideration that a gateway condenses your network into a single process. You must be clear about the traffic you expect to forward through a gateway. The following highlights some other specifics.

1. Know your Topic Resolution Domains. See Topic Resolution Domain.

2. Consider the size and quality of network paths into and out of your gateways. Obviously, gateways cannot efficiently forward message from a 1 GB path to a 100 MB path.

3. Fully examine any use of Late Join, taking care to configure retransmission options correctly.

4. All remote stores must be named stores.

7.2. UMM Daemon

The UMM Daemon stores UM XML configuration information defined in the GUI as well as user and license information. It serves license and configuration information to UM applications. The UMM Daemon requires either a MySQL™ or Oracle® database installation. Informatica does not supply MySQL or Oracle nor any licensing to use them. For additional information about the steps in this process, see UM Manager Daemon.

1. Install MySQL or Oracle according to the user documentation.

2. Create a database. (You provide the UMM Daemon with the database name, username and password at start up. This user name and password should be kept secure.)

3. Log into the database.

4. From the database's command line or home page, execute the /UMM/install_tables_oracle.sql or source /UMM/install_tables_mysql.sql script. (This script installs the tables required by UMM.)

5. From the database's command line or home page, load /UMM/oracle_templates.txt or /UMM/mysql_templates.txt. (This script loads the example configuration templates for low latency and high throughput. These templates appear in the UMM GUI under Templates in the object tree in the left pane.

   • For Oracle, load /UMM/oracle_templates.txt.

   • For MySQL, run LOAD DATA INFILE 'mysql_templates.txt' INTO TABLE TEMPLATE;.

6. From the database's command line or home page, load /UMM/oracle_application_jms.txt or /UMM/mysql_application_jms.txt. (This script loads the ConnectionFactories and Destinations required to run the example JMS applications. These templates appear in the UMM GUI under JMS/ConnectionFactory and JMS/Destination in the object tree in the left pane.)

   • For Oracle, load /UMM/oracle_application_jms.txt into the Application table.

   • For MySQL, run LOAD DATA INFILE 'mysql_application_jms.txt' INTO TABLE APPLICATION;.

7. Modify the /UMM/umm.properties to indicate the database username, password and driver to reflect your configuration database.

8. Edit the ummd.bat or ummd.sh file that starts UMM Daemon. The appropriate driver jar file name must be added to the classpath. Specify your certificate file or Java keystore information if using SSL certificates. The ummd.bat or ummd.sh provided with installation appears below.

   java -cp .;mysql-connector-java-5.0.8-bin.jar;UMMD_1.6.0_02.jar -Xms512m -Xmx1024m umm.ummd.Server
              
   

9. Start the UMM Daemon with /UMM/ummd.bat or /UMM/ummd.sh.

10. Edit the umm.bat or umm.sh file that starts the UMM GUI. The appropriate driver jar file name must be added to the classpath. The umm.bat or umm.sh provided with installation appears below.

    java -cp .;mysql-connector-java-5.0.8-bin.jar;UMM_1.jar; -Xms256m -Xmx1024m umm.gui.MainFrame
               
    

11. Start the UMM GUI with /UMM/umm.bat or /UMM/umm.sh.

12. Log into the UMM GUI with username, default and password default. Either change the default user's password or create new administrative user and delete the default user. See Managing Users

13. To enable your UM applications to be served configuration information by UMM Daemon, set the following environment variable for every application/user combination.

    export LBM_UMM_INFO=<application_name>:<user_name>:<password>@<ip>:<port>
               
    

    For example:

    export LBM_UMM_INFO=lbmrcv:lbmrcv:default:default@10.29.3.95:21273
               
    

7.3. Persistent Store and Queue Daemon

The daemon, umestored, provides persistent store and queue services. Follow the steps below to start umestored.

1. Create the cache and state directories. $ mkdir umestored-cache ; mkdir umestored-state

2. Create a simple umestored XML configuration file (see Configuration Reference for Umestored) or use a sample configuration, ume-example-config.xml or q-example-config.xml

3. Start the daemon. $ umestored config.xml

   See also Manpage for umestored.