khasim - Wednesday, December 4, 2013 9:32 AM:
Hi all,
I am new to Aras PLM. I previously worked on Enovia eMatrix. I want to understand the program flow for the process and functionalities. I mean
where are the source code stored and compiled, is it similar to JPOs in enovia.
Where can I find Advanced Programming Guide.
Is UI display and preferences stored in XML structure and displayed using HTML/XSLT ? Where can I find xsl files ? How are the modifications at UI level captured and stored ?t
Regarding Server code, how the business logic is modeled in XML strucuture.. how webservices are invoked for particular event, server functions ? How database updates are done ?
Any documentation that would help me understand ?
Thanks
Khasim
PeterSchroer - Wednesday, December 4, 2013 10:04 AM:
Hello Khasim, welcome to the Aras community. We've collaborated with many former eMatrix programmers, and I beleive you will find the Aras platform very powerful and easy to work with. All of the documentation you need can be found at: http://www.aras.com/support/documentation/
Aras Innovator is conceptually a very different platform than eMatrix (Enovia). Aras is highly customizable, but you won't be writing traditional source code and compiling, releasing etc. The key 1st thing for you to learn is the underlying modeling engine. Aras Innovator is a behavior modeler.... you describe how you want your PLM (or CRM, or MES, or ??) to behave, and the modeling engine will execute the new behaviors for you. New objects, new processes, new lifecycles, new UI's, new rules.... all of these are defined in the Modeling Engine using the IDE, instead of writing code or doing DB admin. More than 2,000 commpanies are running Aras Innovator world-wide, more than 2,000 very different UI's, objects, rules, but everyone is running exactly the same web services (compiled code), the differences are in the modeling, not in the code. This approach (modeling) allows for very rapid development of new applications, very high performance run-times, and unusually easy upgrades. We generally can upgrade a highly customized system wihtin 2 weeks, often much less, because all customers are actually running the same code base. Performance is excellent... we will be publishing a paper soon with details on the benchmark system running 100,000 concurrent users.
You will write some code of course, to extend the exisitng web services, we call these small blocks of code, methods. But you still aren't using a tradtional compile and build process. The methods are stored in the XML model, and compiled on-the-fly at run-time as required. My rule of thumb is that 90% of new application development is the modeling, and the last 10% is just some glue-logic to extend the existinng services and behaviors.
Let us know more about your project, and then community can give you some guidance. There's lots of sample "code" (i.e. models and methods) available within the community.
--peter.
