3.5.1. Using the Deny,Allow Order

The example below allows any transport type except for LBT-IPC or LBT-RDMA.

<option default-value="tcp" name="transport" order="deny,allow">
    <deny>LBT-IPC</deny>
    <deny>LBT-RDMA</deny>
</option>
       

The procedure below shows how to accomplish this in the UMM GUI. Refer to the composite screen image following the procedure.

1. For the source option, transport, click in the Ordering box and select Deny,Allow.

2. Click the Edit button. The Permissions Window appears.

3. Click Add and type LBT-IPC.

4. Click again on Add and type LBT-RDMA.

5. Click OK.

Figure 5. Ordering - Deny,Allow

3.5.2. Using the Allow,Deny Order

You could accomplish the same restriction shown in Using the Deny,Allow Order with the next example.

<option default-value="tcp" name="transport" order="allow,deny">
    <allow>TCP</allow>
    <allow>TCP-LB</allow>
    <allow>LBT-RU</allow>
    <allow>LBT-RM</allow>
</option>
       

The procedure below shows how to accomplish this in the UMM GUI. Refer to the composite screen image following the procedure.

1. For the source option, transport, click in the Ordering box and select Allow,Deny.

2. Click the Edit button. The Permissions Window appears.

3. Click Add and type TCP.

4. Click again on Add and type TCP-LB.

5. Click Add and type LBT-RU.

6. Click again on Add and type LBT-RM.

7. Click OK.

Figure 6. Ordering - Allow,Deny

3.5.3. Setting Permitted and Restricted Values

1. To use the Order attribute for an option, click on the Order field and select either Allow,Deny or Deny,Allow (default).

2. Click on the Edit button in the Permissions column. The Permissions dialog box appears.

3. To add an option value with a specific permission, click Add. A permission row appears.

4. Select the permission from the Allow,Deny column.

5. Enter the option value in the Value column.

6. Repeat Steps 3-5 for each additional option value that requires specific permissions.

7. Click OK. The Permissions dialog box disappears and your entries appear in the Permission column for the option.

8. Click XML View to verify your entries.

9. Right click on the object name in the left pane or click on the File Menu. Then click Save.

3.5.4. Options with Value Ranges

Some options can specify a range of values. You can specify both allow and deny rules to allow one or more values of a larger range. The next example allows a single multicast address out of a range of otherwise allowable addresses.

<options>
  <option name="transport_lbtrm_multicast_address" default_value="239.191.10.11" order="deny,allow">
    <allow>239.191.10.15</allow>
    <deny>239.191.10.12-239.191.10.20</deny>
  </option>
</options>
           

Address 239.191.10.15 matches both an allow and deny rule, but since the order indicates that allow is the default, the value is allowed.

3.6.1. Configuring Sources

You can configure an individual UM source using a topicname or a topic pattern. Configuring a pattern allows you to easily specify option values for all the topics that match the pattern instead of configuring individual topics (topicname) with the same options and values. (You could also apply a template to the context that has all the source scope option values.) When using a topic pattern, the following rules apply.

• Topics that match both a topicname and a topic pattern use the option values from the more specific match, i.e. the topicname.

• If multiple patterns match a given topic, UMM uses the first pattern matched in the XML configuration file. In the example below, when your application creates a source for topic SRM, it will use the LBTRM transport, which is configured for the the first pattern, *R*, and not the TCP transport which is configured for the second pattern, *RM.

      <sources order="deny,allow">
        <topic pattern="*R*" rule="allow">
          <options type="source">
            <option default-value="lbtrm" name="transport"/>
          </options>
        </topic>
        <topic pattern="*RM" rule="allow">
          <options type="source">
            <option default-value="tcp" name="transport"/>
          </options>
        </topic>
      </sources>
           

Use the following procedure to configure options for an individual UM source.

1. Click on the Sources tab on the left of the context pane. An empty Sources window appears.

   Figure 12. Sources Tab

   

2. If needed, change the default Ordering for All Sources to allow,deny. See also Using the Order and Rule Attributes.

3. Click on the Add button. The Source window appears.

   Figure 13. Source Topic Name/Pattern Options List

   

4. Enter the topicname or a topic pattern.

5. Select the Type, Topic Name or Pattern from the drop-down menu.

6. Click on the checkbox next to the desired options for the topic or pattern. Click OK. The Sources window appears with the selected options.

   Figure 14. Topic/Pattern Option Values

   

7. Adjust the option values. See Creating Configuration Templates for more on configuring options.

8. If you wish to apply a template to the source, click on the Templates button and apply the template(s).

9. Set the Rule attribute, if needed.

10. Repeat Steps 3-9 for all topics and topic patterns for the context.

3.6.2. Configuring Receivers

Use the following procedure to configure options for an individual UM receiver.

1. Click on the Receivers tab on the left of the context pane. An empty Receivers window appears.

   Figure 15. Receivers Tab

   

2. If needed, change the default Ordering for All Receivers to allow,deny. See also Using the Order and Rule Attributes.

3. Click on the Add button. The Receiver window appears.

   Figure 16. Receiver Topic Name/Pattern Options List

   

4. Enter the topicname or a topic pattern.

5. Select the Type, Topic Name or Pattern from the drop-down menu.

6. Click on the checkbox next to the desired options for the topic or pattern. Click OK. The Receivers window appears with the selected options.

   Figure 17. Topic/Pattern Option Values

   

7. Adjust the option values. See Creating Configuration Templates for more on configuring options.

8. If you wish to apply a template to the source, click on the Templates button and apply the template(s).

9. Set the Rule attribute, if needed.

10. Repeat Steps 3-9 for all receiver topics and topic patterns for the context.

3.6.3. Configuring Wildcard Receivers

To apply XML configuration to a wildcard receiver, be sure both the pattern and pattern-type match exactly. You may also specify both receiver and wildcard receiver options.

Use the following procedure to configure options for an individual UM wildcard receiver.

1. Click on the Wildcard Receivers tab on the left of the context pane. An empty Wildcard Receivers window appears.

   Figure 18. Sources Tab

   

2. If needed, change the default Ordering for All Wildcard-receivers to allow,deny. See also Using the Order and Rule Attributes.

3. Click on the Add button. The Wildcard Receivers window appears.

   Figure 19. Wildcard Receiver Pattern Options List

   

4. Enter the wildcard receiver Pattern.

5. Select the Pattern Type, pcre, regex or appcb from the drop-down menu. See pattern_type for more information about these option values.

6. Click on the checkbox next to the desired options for the topic or pattern. Click OK. The Wildcard Receivers window appears with the selected options.

   Figure 20. Wildcard Receiver Pattern Option Values

   

7. Adjust the option values. See Creating Configuration Templates for more on configuring options.

8. If you wish to apply a template to the source, click on the Templates button and apply the template(s).

9. Set the Rule attribute, if needed.

10. Repeat Steps 3-9 for all wildcard receiver patterns for the context.

3.6.4. Applying Templates

The Templates dialog box allows you to apply templates to applications or any primitive UM object and also to remove templates or change the order.

Figure 21. Templates List

• To apply a template, click on the Template Name in the left pane and click the Right Arrow. The template appears in the right pane. You can also hold down the Ctrl key to select multiple templates.

• To remove a template already applied, click on the Template Name in the right pane and click the Left Arrow. The template disappears from the right pane.

• To change the order of the applied templates, click on the Template Name in the right pane and click the Up Arrow or Down Arrow to reposition the template.

You can apply multiple templates to applications or any primitive UM object. The order in which you attach templates determines the resolution of conflicting option values. The last instance of an option determines the value used. In the UMM GUI, this means the lowest option instance in the file.

3.7.1. Configuring ConnectionFactories

1. Click on JMS in the object tree in the left pane and then right-click or click on the File Menu.

2. Select New and then select ConnectionFactory from the drop-down menu.

3. Enter the ConnectionFactory Name and click OK. The initial, blank ConnectionFactory window appears.

   Figure 22. New ConnectionFactory Window

   

   The listed ConnectionFactories, uJMSConnectionFactory, TopicConnectionFactory, and QueueConnectionFactory are pre-installed and facilitate running the compiled example JMS applications. See Ultra Messaging JMS Quick Start.

4. If you wish to apply a template to the ConnectionFactory, click on the Templates button. The Templates window appears.

   Figure 23. Templates List

   

   See Applying Templates.

5. Configure the ConnectionFactory's Context.

   • If you wish to apply a template to the Context, click on the Templates button and apply the template(s).

   • Configure the options for the Context by clicking on the Options button and selecting the options. See Creating Configuration Templates for more on configuring options.

   • Configure the Sources. See Configuring Sources.

   • Configure the Receivers. See Configuring Receivers.

   • Configure any Wildcard Receivers. See Configuring Wildcard Receivers.

   • Configure the Factory options. See Configuring Factories.

   • Set the Rule attribute, if needed.

6. Configure options for the types of Destinations used with the ConnectionFactory. See Configuring Destinations.

   • For Destinations with the Type=UMS, click on the UMS tab and configure the appropriate options such as transport options.

   • For Destinations with the Type=UMP, click on the UMP tab and configure the appropriate options such as store configuration options.

   • For Destinations with the Type=UMQ, click on the UMQ tab and configure the appropriate options such as queue configuration options.

7. Right click on the ConnectionFactory name in the left pane or click on the File Menu. Then click Save All.

8. Click on the XML View tab to review the actual XML configuration for the ConnectionFactory. (Template options and values do not appear in this view.)

3.7.2. Configuring Factories

Follow the procedure below to configure Factory options for the ConnectionFactory.

1. Click on the Factory vertical tab and click on the Options button. The Factory Options list appears.

   Figure 24. Factory Options Window

   

2. Select the Factory options by clicking in the checkbox for each desired option. Then click OK.

3. Enter the option values for the selected Factory options.

3.7.3. Configuring Destinations

Follow the procedure below to create Destinations and configure Destination options for the ConnectionFactory.

1. Click on JMS in the object tree in the left pane and then right-click or click on the File Menu.

2. Select New and then select Destination from the drop-down menu.

3. Enter the Destination Name and click OK. The initial, blank Destination window appears.

   Figure 25. New Destination Window

   

   The listed Destinations are pre-installed and facilitate running the compiled example JMS applications. See Ultra Messaging JMS Quick Start.

4. Configure the options for the Destination by clicking on the Options button and selecting the options.

5. Enter the option values for the selected Destination options.

3.8.1. Changing the Default User Password

Use the following procedure to change the default user password.

1. Expand the Users object tree in the left pane.

2. Click on default. The Default User window appears.

   Figure 26. Default User Window

   

3. Click on the Change button. The New Password dialog box appears.

4. Enter the new password and click on OK.

3.8.2. Managing Users

Follow the procedure below to add a new user.

1. Click on Users in the object tree in the left pane and then right-click or click on the File Menu.

2. Select New and then select User from the drop-down menu. The User Name dialog box appears.

3. Enter the User Name and click OK. The user profile dialog box appears.

4. Click in the Password entry box and enter the user's Password. (UMM hides the password after you save the user's record.)

5. Select the type of user, Normal or Admin.

6. Check the Active check box if the user is an active user.

7. Click on the Add button under the Applications entry box. A list of the configured applications appears.

8. Click on the applications this user has permission to run, holding down the Ctrl key to select multiple applications.

9. Select Save from the File Menu.

5.1.1. umm.properties

Contains database information such as the database username, password and driver. The simplest way to configure UMM is to edit this file to reflect your configuration database. The other two batch files or shell scripts automatically look to umm.properties for database information. This file, however, is optional. You could specify database information with options in the UMM Daemon and UMM GUI batch files or shell scripts. The umm.properties provided with installation appears below.

################## mySQL example ##############################
LBM_LICENSE_FILENAME=lbm.lic
database_password=admin
database_jdbc_object=com.mysql.jdbc.Driver
database_username=admin
db_url=jdbc:mysql://10.29.3.112:3306/name
secure=false    #Only used by ummd.
port=15701  #Only used by ummd.
################## Oracle example ##############################
#database_password=admin
#database_jdbc_object=oracle.jdbc.driver.OracleDriver
#database_username=system
#db_url=jdbc:oracle:thin:@//localhost:1521/xe
           

5.1.2. ummd.bat or ummd.sh

Specifies the needed information to run the UMM Daemon. By default, the ummd.bat/sh looks to umm.properties for database information. You can override the umm.properties file settings with ummd options. See Manpage for ummd. 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
           

5.1.3. umm.bat or umm.sh

Specifies the needed information to run the UMM GUI. By default, the umm.bat/sh looks to umm.properties for database information. You can override the umm.properties file settings with ummd options. 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
           

The same options available to the UMM Daemon (Manpage for ummd) are also available for the umm.bat batch file and the umm.sh shell script. The following two options are also available.

• -a UMM username

• -b UMM password

These options allow the UMM GUI user to skip the username and password dialog box when starting the GUI, but limits you to one user. See Managing Users for information about creating users and assigning passwords and applications to them.

5.3.1. Oracle® Considerations

Informatica does not supply an Oracle database or any licensing to use Oracle. You can install an Oracle database either before or after installing UM. Drivers are not shipped with UM. The Oracle driver can be downloaded at http://www.oracle.com/technetwork/database/enterprise-edition/jdbc-10201-088211.html. The appropriate driver jar file name must be added to the classpath of the umm.bat/umm.sh and ummd.bat/ummd.sh scripts.

Configure Oracle with the following steps, which assume you have already installed UM.

1. Install Oracle and 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.)

2. From the Oracle command line or database home page, log into your Oracle database.

3. From the Oracle command line or database home page, load /UMM/install_tables_oracle.sql. (This script installs the tables required by UMM.)

4. From the Oracle command line or database home page, load /UMM/oracle_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.)

5. From the Oracle command line or database home page, load /UMM/oracle_application_jms.txt into the Application table. (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.)

You can now start the UMM Daemon on the command line or with the ummd.bat batch file or the ummd.sh shell script.

5.3.2. MySQL™ Considerations

Informatica does not supply MySQL or any licensing to use MySQL. You can install MySQL either before or after installing UM. Drivers are not shipped with UM. The MySQL driver can be downloaded at http://dev.mysql.com/downloads/connector/j/5.0.html. The appropriate driver jar file name must be added to the classpath of the umm.bat/umm.sh and ummd.bat/ummd.sh scripts.

Configure MySQL with the following steps, which assume you have already installed UM.

1. Install MySQL.

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 MySQL with connect db_name.

4. From the MySQL command prompt, run source /UMM/install_tables_mysql.sql. (This script installs the tables required by UMM.)

5. From the MySQL command prompt, run LOAD DATA INFILE 'mysql_templates.txt' INTO TABLE TEMPLATE;. (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.)

6. From the MySQL command prompt, run LOAD DATA INFILE 'mysql_application_jms.txt' INTO TABLE APPLICATION;. (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.)

You can now start the UMM Daemon on the command line or with the ummd.bat batch file or the ummd.sh shell script.