Deploying to Servers

Servers receive the same package that you build for the workstation, but in a different format. When you assemble the package and create the package build definition, you can specify the servers to which you want to build and deploy the package. To deploy the package, you use the JD Edwards EnterpriseOne Deployment Director application (P9631/P9631W), which uses the same scheduling mechanism to deploy packages to workstations. In fact, you can easily schedule deployment to both client workstations and servers on the same form.

If you are deploying an update package that contains only UBEs, otherwise known as batch applications, the system marks the package as a "UBE only" package. The system deploys a UBE-only package immediately, rather than waiting for the EnterpriseOne HTML server and waiting for all UBEs to finish. When the package is deployed, the system checks to see if the UBE in the package is currently being processed. If so, a lock is placed on that individual UBE so that the deployment can update the specifications. If not, the package deployment moves forward. This happens automatically and provides a faster deployment time for packages that contain only UBEs.

If you are deploying an update package that contains only APPs (interactive applications), the system marks the package as an "APP-only" package. The system deploys the APP-only package, waits for the EnterpriseOne HTML server (for one minute), and then deploys it immediately without waiting for any UBEs to finish.

If you are deploying an update package that contains only UBEs and APPs, the system marks the package as a "UBE/APPs only" package. In this case, the system waits for the EnterpriseOne HTML server (for one minute), and then follows the same logic as the UBE-only deployment.

All three of these scenarios happen automatically and provide a faster deployment time for packages that contain only UBEs, only APPS, or only UBEs and APPs.

Beginning with Release 9.2.7.0, table conversions are run after the deployoment of the server package. For a full package build, the TC UBE runs all tables listed in the F98405 table. For update package, table conversions run only if tables are included at objects. For update packages, table conversion runs only if objects in the package are tables.