Quick Start Guide
|
The UM Router bridges disjoint topic resolution domains by forwarding multicast and/or unicast topic resolution traffic. Before installing and starting a UM Router daemon (tnwgd) clear objectives and proper planning are very important. Approach this planning with the consideration that a UM Router condenses your network into a single process. You must be clear about the traffic you expect to forward through a UM Router. The following highlights some other specifics.
Know your Topic Resolution Domains. See Topic Resolution Domains.
Consider the size and quality of network paths into and out of your UM Routers. For example, UM Routers cannot efficiently forward messages from a 1GB path to a 100MB path.
The UMM Daemon manages 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 the Ultra Messaging Manager Guide.
Install MySQL or Oracle according to the user documentation.
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.)
Log into the database.
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.)
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.
Modify the /UMM/umm.properties to indicate the database username, password and driver to reflect your configuration database.
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
Start the UMM Daemon with /UMM/ummd.bat or /UMM/ummd.sh.
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
Start the UMM GUI with /UMM/umm.bat or /UMM/umm.sh.
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 the Ultra Messaging Manager Guide.
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
The daemon, umestored, provides persistent store services. To start umestored, perform the following steps:
Create the cache and state directories.
$ mkdir umestored-cache ; mkdir umestored-state
Create a simple umestored XML configuration file or use a sample configuration, ume-example-config.xml or q-example-config.xml. See the Ultra Messaging Guide for Persistence.
$ umestored config.xml
See also Umestored Man Page.