P
Peter Judge
Guest
The relationships are as such - 1 instance has 1 or more ABL applications - 1 instance has 1 or more webapps (URLs) - 1 ABL application has 1 or more webapps - 1 webapp (URL) has 1 and only 1 ABL application I would say the quantities depend on a number of factors - on a developers machine, I'd say one instance with many ABL applications (as long as there are no URL conflicts) - if you want to be able to scale instances out under a load balancer, then I'd have only one ABL application per instance - if you are a SaaS provider, you may have one ABL applications per customer and have 1 or more customers per instance (depending on what they pay for) - if you want to be able move an instance easily from Dev -> test -> prod the fact that you can zip an entire instance and deploy tends to indicate one ABL application per instance. Some of this depends on how you configure your ABL applications. The default PROPATH for an ABL application is $CATALINA_BASE/webapps/ /WEB-INF/openedge + $CATALINA_BASE/openedge + $DLC/tty which means that ALL ABL applications share a common base propath ($CATALINA_BASE is the instance's root/top folder) with specialised paths per webapp. I like the concept of having a whole 'customer application' zippable in the instance directory, so I'd use that default PROPATH or something quite similar. You can, of course, change your PROPATH so that there's no shared entries. I don't know of any case studies done on configs/loads in an instance.
Continue reading...
Continue reading...