Informatica Ultra Messaging


 

You must log in or register to view this page

Product description

Informatica Ultra Messaging enables you to move high-performance real-time data between distributed applications on-premises and in the cloud.

Architecture

The examples of the product components and patterns interaction are displayed in the following table.

Software pattern summary

The following table gives an overview of the pattern characteristics:

Product component

OS type

Versioning

Pattern depth

Informatica Ultra Messaging Desktop ServicesUNIX, WindowsNoneInstance-based
Informatica Ultra Messaging Dynamic Routing OptionUNIX, WindowsFileInstance-based
Informatica Ultra Messaging StoreUNIX, WindowsPathInstance-based
Informatica Ultra Messaging SourceUNIXPathInstance-based
Informatica Ultra Messaging ReceiverUNIXPathInstance-based
Informatica Ultra MessagingUNIX, WindowsGets versioning from the contained SoftwareInstance nodesInstance-based

Platforms supported by the pattern

The pattern discovers Informatica Ultra Messaging components on UNIX and Windows systems.

Identification

To run a discovery of the product, the pattern must be triggered. This section describes conditions under which the pattern can be triggered.

Software instance triggers

The following table gives details about the pattern triggers:

PatternTrigger nodeAttributeConditionArgument
DesktopServicesDiscoveredProcess

cmd

matches

regex "\bumdsd$" or regex "(?i)\bumdsd\.exe$"

DynamicRoutingOption

DiscoveredProcess

cmd

matches

regex "\btnwgd$" or regex "(?i)\btnwgds?\.exe$"
StoreDiscoveredProcesscmdmatchesregex "\bumestored$" or regex "(?i)\bumestoreds?\.exe$"
SourceDiscoveredProcesscmdmatchesregex "\blbmm?src$" or regex "\bumqsrc$"
ReceiverDiscoveredProcesscmdmatchesregex "\blbmw?rcv$" or regex "\bumqrcv$"
UltraMessagingSoftwareInstancetypein["Informatica Ultra Messaging Store",
 "Informatica Ultra Messaging Source",
 "Informatica Ultra Messaging Receiver"
]

Simple identification mappings

The following components/processes are identified by using the simple identity mappings that map the product's known processes:

Name

Condition

Informatica Ultra Messaging Lbm Resolver Daemonregex "\blbmrd$"
Informatica Ultra Messaging Lbm Resolver Daemonregex "(?i)\blbmrds?\.exe$"
Informatica Ultra Messaging Sourceregex "\blbmm?src$"
Informatica Ultra Messaging Sourceregex "\bumqsrc$"
Informatica Ultra Messaging Receiverregex "\blbmw?rcv$"
Informatica Ultra Messaging Receiverregex "\bumqrcv$"
Informatica Ultra Messaging Gateway Daemonregex "\btnwgd$"
Informatica Ultra Messaging Gateway Daemonregex "(?i)\btnwgds?\.exe$"
Informatica Ultra Messaging Desktop Servicesregex "\bumdsd$"
Informatica Ultra Messaging Desktop Servicesregex "(?i)\bumdsd\.exe$"
Informatica Ultra Messaging Manager Daemonregex "\bummd$"
Informatica Ultra Messaging Persistent Store Daemonregex "\bumestored$"
Informatica Ultra Messaging Persistent Store Daemonregex "(?i)\bumestoreds?\.exe$"
Informatica Ultra Messaging Monitoring Collector Serviceregex "(?i)\bmcsds?\.exe$"
Informatica Ultra Messaging Stateful Topic Resolution Serviceregex "(?i)\bsrsds?\.exe$"

Versioning

Version information for the product is collected by using the file and path versioning methods.

File versioning

The DynamicRoutingOption pattern reads the <filepath>.[cfg|xml] file to extract the full path to a log file from which the version is extracted from its contents by parsing against the following regular expression:

Gwd\-7136\-1\: Ultra Messaging Gateway version (\d+(?:\.\d+)*)

Path versioning

The Store pattern attempts to extract the version from the trigger process path by parsing against the following regular expression:

[\\/]UMP_(\d+(?:\.\d+)*)[\\/]

The Source and Receiver patterns attempt to extract the version from the trigger process path by parsing against the following regular expression:

[\\/](?:UMP|UMQ|UMS)_(\d+(?:\.\d+)*)[\\/]

Relationship creation

The Source and Receiver patterns attempt to create a Client:Server communication link to the Apache ActiveMQ broker SI.

The UltraMessaging pattern creates a second-order SI and attempts to ascertain the product's edition.

Subject matter expertise

Inputs from subject matter experts are welcome on any other potential approaches not discussed in this topic.

Testing

The patterns have been tested against the provided customer data on the UNIX platform.

Open issues

There are no known open issues with this pattern.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*