ArchestrA Graphics Tips and Tricks Episode 4 - Symbols and Faceplates

In this episode we will explore how to build symbols and faceplates on ArchestrA object standards. We will demonstrate how building standards can greatly shorten the application development effort.

[@gorbulas]

I found this very helpful, thank you

[@babaktirgar]

Hi John,
Thanks for your tutorials.
They are great!
I have a question regarding to this video.
in 11:45 you've Deployed your MyNewEquip.
My question is that in this case in which Platform do we Deploy them?
shouldn't we assign them to any Platform?

[@babaktirgar]

Hi again,
Thanks for your fast Reply.
I understand the System Platform's Distributed System, but the question is that doesn't it mean if I put it in GR Node (for example) all other nodes will be depended on this node? what will happen to other Nodes if the GR node go out of service?

[@babaktirgar]

I don't get how can AppEngine Redundacy help when the Graphic object only can locate in one node and that node is out of reach?!! Actually this is My biggest problem from System Platform 2014 which doesn't let me to use this technic in my solution

[@RaresPlesea]

@@babaktirgar At 11:52 the instances are deployed to AppEngien1 hosted by GRNode. It is likely that he set them as default with right click; as the deployment is not that relevant to this video, he likely glossed over it.
A platform represents a computer in the galaxy. It hosts the Engines which host objects, and it handles node-to-node communications. Obviously if the computer goes down, the platform goes offline. If you have just one platform, that is one computer, everything goes down. If you have multiple platforms, they can do different things.
For redundancy, you can set up what is called a redundant app engine which can be hosted on a 2nd platform; if the first platform goes down then appengine1 goes down, but the redundant one will still work on the 2nd platform (computer).