1. Package Management Guide
  2. Deployment of Update Package that Includes All Types of Objects:

Deployment of Update Package that Includes All Types of Objects:

  1. Sets the F9651 field mdmchrcdnm=50 to prepare the server for deployment.

  2. Process sleeps for 1 minute which allows the JAS server polling to see there is a package to deploy. The JAS server puts a lock on the web application to wait for the deployment to finish. The JAS server polls every 5 seconds, checking the F9651 table to see if it is done with the deployment. It looks for mdmchrcdnm=30. There are no effects to users already in the application, only if the users try to bring up a new application.

  3. Sets the F9651 field mdmchrcdnm=10 to indicate deployment is happening.

  4. Enterprise Server sends message to all kernels to lock. This will prevent any UBEs from being submitted.

  5. Process waits for all running UBEs to complete. It will only wait as long as the setting in the jde.ini indicates - "DeployWaitInMinutes=x" or default to 30 minutes. If time has expired, it will release the locks without deploying the package.

  6. Once UBEs are finished running:

    1. Merges the update package tables with the current database tables to which the spec.ini points.

    2. Copies the .dll/.so/sl/SVRPGM from the update package directory to the "Live Area": <pathcode>\<packagename>\bin64" or the package name SVRPGM library.

    3. Deletes the ddict, ddtext, and glbtbl specs from the <pathcode>/spec/<package name> directory.

    4. Deletes only the directories of the UBEs that are in the package from the runtime cache directory, <pathcode>/<package name>/runtimeCache.

  7. Releases the locks and submits any UBE in the queue.

  8. Sets the F9651 field mdmchrcdnm= 30 to indicate deployment is finished.

  9. (Starting with Tools Release 9.2.5.0) If the package is a client package, on the Deployment Server, copy the bin32 ,(64) obj, lib32(64), include, include64, source and source64 to the parent package.