I love vRealize Automation but have some question and complain as follows:
In the following URL, the DEM Orchestrator is separately installed from Model Manager.
However, DEM Orchestrator is automatically installed with Model Manager as we can also see here:
The Orchestrator is automatically installed on the machine that also runs a Model Manager.
Which is true?
By the way, the subtopics of the following URL such as IaaS Website and DEM is old information.
For example, "vCloud Automation Center Manager Service" should be written as Manager service because that's expression is old.
There is a lot of improved points I found on vRA documents. Is there anyone who pointed out about vRA documents like me? Or don't you have complains because consulting with PSO Consultants?
Actually, the first link shows the model manager *data* on the Web Server box.
The manager service and the DEM Orchestrator should be installed together.
As for the naming, you will typically hear "manager service" used, but the service is listed as "vCloud Automation Center Manager Service" if you look in the services console in Windows.
The DEM information is correct, I'm not sure what you think is out of date here? The Web Server information is correct, but the line is a bit more blurry when it comes to understanding how it interacts with the appliance to deliver services.
Hope that helps.
Grant
Really thanks for your reply.
>Actually, the first link shows the model manager *data* on the Web Server box.
Yes. That's same understanding as me.
>The manager service and the DEM Orchestrator should be installed together.
I think "can" is more appropriate rather than "should".
If this is correct, the following sentence should be revised, right?
Distributed Execution Managers
>As for the naming, you will typically hear "manager service" used, but the service is listed as "vCloud Automation Center Manager Service" if you look in the services console in Windows. The DEM information is correct, I'm not sure what you think is out of date here?
OK. In this case, it's better to change the service name as latest name like "vRealize Automation Manager Service". However, it's acceptable for me not to change it because customers can guess the correct name somehow.
> The Web Server information is correct, but the line is a bit more blurry when it comes to understanding how it interacts with the appliance to deliver services.
As you said, there is blurry expression and it's painful to understand it. At least, it is feasible to write explicitly about Model Manager data or web and how this is interacted with other components, I think.
So it's appreciated if a person in charge could make clear it as far as he can. Writing it in informal site such as VMware blog is OK. If this is improved, it's helpful for more selling vRA to my customers.