Full Package - Normal Package Deployment:

  1. Set the F9651 field mdmchrcdnm=50 to prepare the server for Deploy.

  2. (Prior to Tools Release 9.2.6.0) Process sleeps for 1 minute which allows the JAS server polling to see there is a package to deploy. The JAS server will put a lock on the web applications to wait for the deploy to finish. The JAS server will poll every 5 seconds checking the F9651 table to see if it is done with the deploy. It looks for mdmchrcdnm=30. There are no effects to user already in the application only if the users try to bring up a new application will they have to wait.

  3. (Prior to Tools Release 9.2.6.0) Sets the F9651 field mdmchrcdnm=10 to indicate deployment is happening.

  4. (Prior to Tools Release 9.2.6.0) Enterprise Server sends message to all kernels to lock. This will prevent any UBE from being submitted.

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

  6. (Prior to Tools Release 9.2.6.0) Once UBEs are finished running:

    1. Opens the <pathcode>/spec.ini file and changes the <pathcode>_Package setting to the new package name:

      DV920_Package=DV920FA
      
    2. Copies the .dll/.so/sl/SVRPGM from the package directory to the "Live Area" which is <pathcode>\bin32/bin64" or the SVRPGM library.

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

    4. Deletes the Runtime cache from the <pathcode>/runtimeCache directory.

    5. Releases the kernel locks.

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

  7. Opens the <pathcode>/spec.ini file and changes the <pathcode>_Package setting to the new package name: DV920_Package=DV920FA.

  8. Sends a broadcast message that a package change was performed.
  9. Sets the F9651 mdmchrcdnm field value to 30 to indicate deployment is complete.
  10. Updates the record in the F96511 table with Enterprise Server information, port number, pathcode, package name, and type 30 to indicate this is the deployed package.
  11. (Starting with Tools Release 9.2.5.0) If the package is also a client package, insert a record in the F98825 table with these details:
    • MKEY=”CLIENT"
    • UPJDEPKGNM=<package name>
    • UPPATHCOD=<pathcode>
    • UPINPKST=’20’
    • Date and time
    For the previously deployed package with the details MKEY=”CLIENT” and UPINPKST=’20’, update the status to UPINPKST=’30.