Got this model from an Telelogic Employee and his permission to distribute ... to be honest ... it's pretty cool

You want to realize an interaction between distributed applications which is independend of the underneth transport layer ? ... take a look of the DistributedCommsFactory Example - realized with Winsock and UDP but can be extended to any other (Shared Memory, Pipes whatever)

Example:
Two Components (Application) on one host are communicating by exchanging events via UDP
One Component on Windows Host is communicating with another component on Linux Target.

Have fun

Hi Hatevista ...I am having rhapsody 7.1.1 but it is showing that there is some version incompatiblity with this one....can you please upload a model which works in 7.1.1

The Model is for Rhapsody 7.2 ... download the latest version

I've been studying this sample for a couple days now. Please correct me if I'm wrong, but isn't the point of the Factory pattern to allow the user to create the concrete class by only accessing the Abstract class? I would expect a static parameterized constructor in the abstract class that returns a pointer to the concrete class. Where is the constructor? Without the ability to create the concrete object via the abstract class, the user still has to create the concrete object specifically. Am I missing something?

I haven't downloaded it but it looks familiar. There's probably a static instance() method in the factory that gets implemented by each concrete. Therefore the way to access the factory methods would be via the instance method, e.g.

itsIOXFServerRx = DistributedCommsFactory::instance()->CreateServerRx(...);

This is the same pattern that is used to implement the OSAL (operating system adapter layer). See the OXF model in <rhapsody>/share/langcpp/oxf/model or os.h (generated from that model) in <rhapsody>/share/langcpp/oxf.