How to Unload a runtime Solution from automation in pega 8.0
while running the solution using open span runtime is there a way that the automation logic will check for deployed version if the running version is a old one our automation will unload the current solution from runtime and load the new solution in run time.
The Runtime will check at startup if there is a new version in the location specified (this depends on how you are deploying your solution). If there is a newer version in the deployment location than what is found on the local machine, the new version will be downloaded and run. There is no additional checking while running.
I am using Openspan in Citrix environment and we will not be setting the .os file path in runtime config.xml(startup project.).
we are trying to this scenario:
There will be two deployment packages , one at the agent's home drive (like version 1.3) and other one will be at the shared location which will always be the latest(like version1.4).
Now the agent will manually load the version 1.3 from Runtime software.
Now we want the version 1.3 to check the shared drive location, where we are having greater version than 1.3.
If exist the robot will copy the version 1.4(only one version will placed there) to agent home drive.
Now the challenge is that we want to load the latest version copied from shared drive in agent home drive (like version 1.4) and delete the previous version 1.3 from agent home drive, without existing the runtime.
So that in any case agent will not have two .os files in his home drive.
You cannot load a new package without first exiting the existing one (and closing any applications involved). This process would not be seamless to the agent, which is why we do this check on Runtime startup. You can implement the logic you specified above, however you won't be able to simply unload and re-load a new package. I would suggest you display an alert of some kind to let the agent know there is a new version. Incidentally, the .OpenSpan and .Manifest files are not in-use while Runtime is running, so you can simply copy the new version over them to avoid multiple copies.