We have been using it with a number of different data sources already. IBM provides a number of different interfaces to enterprise systems such as IBM Director, MQ Series, Tivoli OmegaMon, and Enterprise Workload Manager.
While these standard interfaces are available, the advantage of the HEI is that it is capable of integrating easily with the EOLUS VWCI solution, so from that perspective it would be a shared infrastructure component.
Then once the data is in-world we have communications gear actually in-world that provide in-world messaging services such as decryption, routing along network links to different machines or equipment, so that’s also kind of a shared infrastructure. The way that the HEI middleware component works is we have a special protocol that’s used so that we don’t have any specific reliance on one protocol or another but it’s meant specifically for virtual world integration.
The protocol can be thought of as an inter-dimensional protocol, if you will, between 2d and 3d. But it can also be used exclusively in the 3d environment. We have machines in there that will generate these protocol messages whose recipients are other machines in-world. So we get some very rich interaction patterns there.
Blogged with Flock
Keine Kommentare:
Kommentar veröffentlichen