1. Package Management Guide
  2. Understanding Deployment to Web Servers

Understanding Deployment to Web Servers

Web servers have the ability to determine which package is to be deployed on the default enterprise server and generate serialized objects on demand. The web servers also have the capability to compare the contents of a package with that of a new package and make the necessary adjustments, such as deleting obsolete serialized objects. This is done by using a package manifest.

A package manifest is a spec record that is created by the package build process. The manifest describes the package and its contents. The serialized object generator compares the manifest from the deployed package on the enterprise server to one that is created during the generation process and makes the appropriate changes.

(Prior to Tools Release 9.2.6.0) The process for deploying packages to web servers is:

  1. The web servers check the F9651 and F96511 tables every minute for any change in the package.

  2. The one minute interval is changed to five seconds once the enterprise server is in a Pre Deploy state.

  3. All JD Edwards EnterpriseOne users are prevented from running any applications once the enterprise server is in a Locked state.

  4. The web server compares the package manifest in the F98770 on the enterprise server with the one in its serialized object database after the package is deployed and the enterprise server is in an Available state.

  5. The web server synchronizes the serialized object database with the deployed package.

    The contents of the serialized object database are deleted for a new full package deployment. Only the objects in the update package are deleted for an update package deployment.

Note: Deploying server packages to web servers is supported only in shared spec server packages.You can have only one path code and one package per Java node. Serialized objects should not be shared with nodes running dissimilar packages and path codes.Starting with Tools Release 9.2.6.0, package deployment no longer affects the Web Server. The users will continue to use the package they signed in with. If they sign off and sign in back in, they will be moved to the new package that was deployed.