Preface
RulePoint
RulePoint Concepts
- RulePoint Concepts Overview
- Understanding RulePoint Entities
Using RulePoint
RulePoint Objects
- RulePoint Objects Overview
- State of RulePoint Objects
Working with Topics
Working with Connections
Working with Sources
Working with Responders
Working with Responses
Working with Watchlists
Working with Analytics
- Analytics Overview
- Analytic Types
- Creating an Analytic
- Copying an Analytic
- Editing an Analytic
- Deleting an Analytic
- Viewing Related Objects
- Predefined Analytics
  - abs
  - average
  - ceil
  - charat
  - clean
  - compareto
  - concat
  - confidence
  - correlation
  - count
  - current
  - date
  - datedifference
  - endswith
  - even
  - floor
  - getcurrentdate
  - getdatefrommillis
  - getdateinmillis
  - geodistance
  - geoinbound
  - geoinsidearea
  - geointersect
  - geooutbound
  - geooutsidearea
  - geopassthru
  - indexof
  - integer
  - isblank
  - isholiday
  - isnum
  - istext
  - isweekday
  - isweekend
  - large
  - list2vars
  - lower
  - max
  - min
  - mod
  - mode
  - mround
  - odd
  - parse
  - past
  - percentile
  - power
  - proper
  - range
  - regex
  - replace
  - round
  - rounddown
  - roundup
  - sign
  - small
  - startswith
  - stdev
  - stringequals
  - stringindexof
  - stringlastindexof
  - stringlength
  - substring
  - sum
  - trim
  - truncate
  - upper
  - xpath
- Predefined Operators
  - contains
  - equalsSet
  - has
  - in
  - match
  - notMatch
  - search
  - unique
  - group by
  - distinct
  - unmatched
- Using the distinct, group by, and ummatched Filters
DRQL
Working with Rules
Working with Alerts
Setting Access Controls
Troubleshooting RulePoint Issues
Connecting to an Ultra Messaging Application
Creating an Ultra Messaging JMS Source

User Guide

6.1
- 6.2
- 6.1.2

Back Next

Configure UM Store or UM Queue

You can install UM Store or UM Queue on a remote box and use it with RulePoint.

Perform the following steps to configure the UM store or UM queue:

Install the 64-bit Informatica UMQ 6.5 bundle.

Set the environment variable LBM_LICENSE_FILENAME to the path of the Ultra Messaging License file.

Set <UMQ_INSTALLATION_DIR>/UMQ_6.5/bin to the path of the environment variable.

Start the lbmrd process. Run the following command:

lbmrd -i <IP_OF_THE_LBMRD_HOST> -p <LBMRD_PORT>

Create the logs directory under the

<UMQ_INSTALLATION_DIR>

directory, create the

cache

and

state

sub-directories within the logs directory.

Copy the sample

lbmstore.xml

file to

<UMQ_INSTALLATION_DIR>

You require the

lbmstore.xml

file to start the UM Store or Queue. The

lbmstore.xml

file contains a reference to the

lbmstore.cfg

file, which contains the UM configurations.

The following snippet is a sample of the

lbmstore.xml

file.

<?xml version="1.0" encoding="UTF-8"?>
<ume-store version="1.2">
    <daemon>
        <lbm-config>C:\workspace\Informatica\um_config\lbmstore.cfg</lbm-config>
        <log>C:\workspace\Informatica\logs\stored.log</log>
        <pidfile>stored.pid</pidfile>
        <web-monitor>*:15704</web-monitor>
    </daemon>
    <stores>
        <store interface="127.0.0.1" name="my-store" port="44000">
            <ume-attributes>
                <option name="disk-cache-directory" type="store" value="C:\workspace\Informatica\logs\cache"/>
                <option name="disk-state-directory" type="store" value="C:\workspace\Informatica\logs\state"/>
                <option name="context-name" type="store" value="remote-store"/>
                <option name="allow-proxy-source" type="store" value="1"/>
            </ume-attributes>
          
	     <topics>                
                <topic pattern="." type="PCRE">
                    <ume-attributes>
                        <option name="repository-type" type="store" value="disk"/>
                        <!-- size threshold is 100Mb and size limit is 200 Mb, can be modified if required -->
                        <option name="repository-size-threshold"
                            type="store" value="104857600"/>
                        <option name="repository-size-limit"
                            type="store" value="209715200"/>
                        <option name="repository-disk-file-size-limit"
                            type="store" value="1073741824"/>
                        <!--
					10 seconds after source became inactive, proxy source is started on store.
					Any new receivers during this 10 seconds inactivity will not be able to
					register with stores and request retransmissions.
				-->
                        <option name="source-activity-timeout"
                            type="store" value="10000"/>
                        <option name="receiver-activity-timeout"
                            type="store" value="604800000"/>
                        <option name="source-state-lifetime"
                            type="store" value="10000000"/>
                        <!--
					Stores generate keep alive traffic to sources and receivers every 0.5 second. This is default and can be removed.
				-->
                        <option name="keepalive-interval" type="store" value="500"/>
                        <!--
					Stores randomly wait 0.5 to 1.5 times proxy-election-interval before starting a proxy source.
				-->
                        <option name="proxy-election-interval"
                            type="store" value="5000"/>
                        <!--
					LateJoin: Maximum number of messages newly registered receiver can rollback (request retransmission).
				-->
                        <option
                            name="receiver-new-registration-rollback"
                            type="store" value="2147483600"/>
                    </ume-attributes>
                </topic>
            </topics>
	    
        </store>
    </stores>
    <queues>
	<queue name="UMQueue" port="14567" group-index="0">
		<ume-attributes>
			<option type="queue" name="dissemination-model" value="SQD"/>
		</ume-attributes>

		<!-- Define the Application Set(s) -->
		<application-sets>
			<application-set name="Set 1">
				<ume-attributes>
					<option type="queue" name="log-audit-trail" value="1"/>
				</ume-attributes>
				<receiver-types>
					<receiver-type id="100"/>
				</receiver-types>
			</application-set>
		</application-sets>

		<topics>
			<!-- Define the topic(s) and the Application Sets for them -->
			<topic pattern="." type="PCRE">
				<application-sets>
					<application-set name="Set 1"/>
				</application-sets>
			</topic>
		</topics>
	</queue>
    </queues>
</ume-store>

Copy the

lbmstore.cfg

file in the <

UMQ_INSTALLATION_DIR

> directory, and update the path in the

lbmstore.xml

file.

The

lbmstore.xml

file consists of a configured store, my-store, which runs on port 44000.

The following snippet is a sample of the

lbmstore.cfg

file:

context fd_management_type wincompport
context resolver_unicast_daemon 127.0.0.1:22000
## Uncomment the following if multicast is enabled in the environment
#context resolver_multicast_interface [MULTICAST_INTERFACE]

To use a port of your choice, edit the port number.

Update the

disk-cache-directory

and

disk-state-directory

in the

lbmstore.xml

file with the path of the

cache

and

state

directories.