Enterprise Manager (Beta) Initial Boot

Enterprise Manager (Beta) Initial Boot

  
WARNING! This is from my own personal experience and I was able to recreate and resolve on two different servers....

The initial bootstrap when you log in as admin/admin is supposed to read the EnterpriseManager.xls file from http://<servername>/EnterpriseManager/EnterpriseManager.xls to build up the initial configuration.

It appears that you must copy the file manually from the EnterpriseManagerBoot Source directory to the \program files\outsystems\Hub Server\running\EnterpriseManager directory AFTER compile and publish of the EnterpriseManager but BEFORE any log on attempts!

Ken
Hello Ken,

I didn’t understand from your post if you really had problems in bootstrapping EnterpriseManager or not, but you are right when you say that the initial bootstrap is supposed to read the EnterpriseManager.xls file from http://<servername>/EnterpriseManager/EnterpriseManager.xls to build up the initial configuration, when you log in as admin/admin. But it’s not supposed to move any file manually.

The EnterpriseManager.xls file is a resource of EnterpriseManagerBoot extension, and as you can see in integration studio the “Compile Action” of this resource is set to “Copy to Application Directory”. The value of the Compile Action property indicates where the resource is stored when the eSpace that added a reference to the extension is published. “Copy to Application Directory” value indicates that the resource is copied to the directory where the eSpace is published, for more information about Compile Action property refer to integration studio online help.

This means that if the installations steps where executed in the correct order the EnterpriseManagerBoot extension was published before the EnterpriseManager oml, and when EnterpriseManager oml is compiled the EnterpriseManager.xls file is automatically copied to http://<servername>/EnterpriseManager/EnterpriseManager.xls directory.

If any problem occurs during bootstrap you can force it to be re-executed by setting the DoBootStrap site property value to true on Service Center (for more information on EnterpriseManager bootstrap see the “OutSystems Enterprise Manager - Technical Note.mht” file).

I hope to have answered your question.

Best regards,

Susete Henriques
Thank You. I didn't know about the "Copy to Application" property. I actually didn't know I could double click on the resource to get to that property sheet!

I checked and my EnterpriseManager.xls file was NOT set to copy to the application directory; hence the problems I had.

I assuming that if it happened to me twice on two different OS environments, then others would have the problem as well, and tried to give some insight. Anyway, these posts may be helpful if any others have bootstrap issues!

Thanks
Ken