Has anyone deployed Blaze Advisor 6.9 on a Linux server? If so, are you using virtual servers? Any issues or limitations to be aware when attempting such a deployment?
[Edited to remove spam]
yes and no (some projects are some are not)
I have not deployed on Linux, but have used virtual servers. There are three categories you need to consider for the "deployment" of Blaze.
The first is the production runtime as a compiled ADB file. This will run fine on a virtual machine. Even with deployment manager it is OK as long as the ADB file is pre-compiled somewhere else.
If you deploy with a deployment manager directly from the repository it will not work well. The issue in this case is the Blaze pre-compile. If your project is of any size at all, a batch compile on a virtual machine could either A) chew up a lot of CPU and slow down other VMs (especially if it happens often) or B) the VM capacity team will limit the CPU available to this VM and the precompile will take a noticiably long time.
The second case is for the RMA. Each time a change is made via the RMA, the code is "regenerated" by the app server. If the generated code base is large (or complex), then there will be a spike in CPU usage. Same as above, either the CPU spike will slow down other VMs or the capacity will be constrained and it will take a long time to get a response from the RMA.
The third case is for the development environment. The Blaze IDE is a heavy CPU user. It will bog down either the VM and/or the host, again depending on the capacity settings on the VM and host as well as other loads on the host. I would highly recommend against the IDE on a VM.
I hope this helps,
Business Rules Consulting, Inc.
Retrieving data ...