IAS快速入门演示文稿.pptVIP

* The system Objects are call WinPlatforms, AppEngines and Areas. Which ones doe I need first and where do I start. The deployment guide (DG) tells me to start with the plant model. The plant model is a hierarchical collection of Area Objects. So I create an Area. But I now need an place for the area to be executed. Upon further reading in the DG I learn that Areas are executed by AppEngines. So I create an Engine. The engine provides me an execution capability of the objects that comprise my application but it need a computer to run on. Again the DG provides the answer that engines are hosted by WinPlatform objects. These platform objects identify the NodeName of the computer in the Galaxy where all this stuff will be sent or deployed. So I now create a platform object and give it a node name. I then assign my engine to it and the engine hosts the area. But I also need a place for my platforms and engines to live in my model so they need an area also. Usually this is a different area from the one that house my application objects. So how do I organize all this stuff. Is there an example of how to do this? * The answer is Yes. This is one of the things that is provided with the Quickstart. A collection of Templates organized into toolsets. A Plant model that contains an section to organize all the system objects as well as a starting point for designing your plant model. Application Objects that can automatically bind to your devices based on similar structure naming. Or can translate to register addressing on older devices simply and easily though alias tables.. Objects expose the plant model in runtime to assist in visualization and scripting. Objects that can restore their after a deployment cycle. Best practices that have been implemented in a tangible and reusable format. * This is a example of the system object area model with the plant model. It is provided as a starting point. You are free to completely reconfigure it, rename it, or delete all