Update Client Packages

The update package enables you to update, add to, or refresh the existing full package with changed objects. You can deploy an update package only to a workstation that already has JD Edwards EnterpriseOne installed on it. When the update package is deployed to a server, the objects are replaced in the Central Objects package database which enables the user to have access to those objects. When a user takes the update package and changes the objects in the update package, the system displays the application with the changed objects and asks if the user would like to delete the specs of the object. The user can delete the user specs and will be able to see the updates for that object. All other objects on the workstation are left unchanged. The advantage of this type of package is that users can quickly deploy software changes or enhancements.

When a user signs into JD Edwards EnterpriseOne and if an update package has been scheduled for that user, a list of available update packages appears. If the user decides to take one or more of these packages, the user spec application will appear if the user has user specs for the objects in the update package. The user can decide to delete the user specs. EnterpriseOne will then use the specs in central objects that was deployed or keep the user specs and then use the changes made by the user. All other objects on the workstation remain will the same.

Like full packages, update packages can include development objects such as business function source files, object specs, and header files. Update package recipients can load the development objects at deployment time.

All update packages require a full package on which the update package is based. This full package is called the parent package. While deploying to the server, the parent package is updated by the update package. When this occurs, all objects in the update package are merged into the parent package.

Business function objects in the update package are linked to the corresponding objects in the parent package, and new DLLs are created. Similarly, specs from the update package are merged into the specs in the parent package.

The parent package concept applies to both workstations and servers. Parent packages for workstations reside on the deployment server, while server parent packages are kept in the build area for the enterprise server.