...
When you use the OpenMI wrapper pattern you will create a new class which implements the ILinkableComponent interface. This component will access your original component in order get and set data. The trick is that all OpenMI specific things can be located in the wrapper, whereas the original component does not depend on anything related to OpenMI. Moreover, the communication between the wrapper and the original component happens in the private area (nobody's business how this takes place). This means that the original component can be located on a remote server (windows, Linux, or whatever).
On figure 2 below you can see an example of a small configuration with two components and a trigger. The configuration runs on the local machine, and the MyLinkableComponent object is communicating with a component on a remote server.
Say you have a database with time series for precipitation you want to make available through OpenMI. You want to keep your database on your server, but want to enable OpenMI components to access the data from other computers. As explained above, you the need to implement a relatively small component/class that implements the ILinkableComponet interface. This component will internally have all information and functionality needed in order to retrieve data from your time series data base on your server. So, users simply download your linkableComponent, add it to their OpenMI configuration, add links between components in the configuration, and runs the configuration, without having to worry about how the data is transferred from the remote precipitation database to the local machine.
...