D
dbeavon
Guest
I don't know if it helps, but this question came up three years ago and at the time there wasn't any way to control abl applications individually within pasoe. The best management options are available via load-balancing. If you have multiple applications, it is likely that you will also need high-availability via load-balancing. See those comments here... Multiple ABL Apps in PASOE - Forum - OpenEdge General - Progress Community ... starting from ... "How does one control the starting and stopping of one ABL application under a PAS instance. Lets just say I want to add an additional ABL application while the instance is running... is this possible and can you then startup this ABL application without stopping and starting the PAS instance" >> We need to empty persistent procedures that are running when they have been changed For anything that is changing within the AVM, the "resetting" can be done at the *ABL-Session* level. You don't need to mess with the ABL application as a whole, nor even the msagent process. (Stopping the msagent process would do the trick but it is overkill.) You would just need to clear away the individual, inactive ABL sessions that predate your changes. You can do this via the oemanager interface with REST. For example here is a similar thread where Irfan was helping me to trim away the ABL sessions which (because of -q) had not picked up a new deployment of r-code : PAS - Pick up new r-code - Forum - OpenEdge Development - Progress Community Again, the better option is to use load-balancing and migrate clients to another server, so you can have an entire server to yourself for maintenance purposes. Hope this is clear.
Continue reading...
Continue reading...