Deployment of an Update Package that Contains Only UBE and Application Objects:
Set sthe F9651 field mdmchrcdnm=50 to prepare the server for deployment.
The process sleeps for one minute, which allows the JAS Server polling to see that there is a package to deploy. The JAS Server puts a lock on applications to wait for deployment to finish. It starts polling every 5 seconds checking the F9651 table to see if it is done with deployment. It looks for mdmchrcdnm=30. There is no effect to users already in the application. If starting an application, there will be a wait until deployment finishes.
Sets the F9651 field mdmchrcdnm=10 to indicate deployment is happening.
Places a lock on only the UBEs in the package. If there is a submit to run a UBE in the package, it is inserted into the F988259 table and held until the package is complete.
Merges the update package tables with the current database tables to which the spec.ini points.
- Releases the locks and submits any UBE in the queue.
Sets the F9651 field mdmchrcdnm=30 to indicate deployment is finished.
(Starting with Tools Release 9.2.5.0) If the package is a client package, on the deployment server, copy, include, include64, source and source64 to the parent package.
Submits the list of UBEs in the F988259 to run.