Package Implementation
This is an overview of the steps for creating and deploying a package:
Assemble the package.
During this step, you specify the type of package that you are building and provide a name, path code, and package description. Next, you assemble the package by specifying the objects, foundation, features, and so on that you want to include in the package. If you are building an update package, you can specify individual objects to include.
To simplify the process of assembling a package, Oracle's JD Edwards EnterpriseOne Package Assembly application (P9601/P9601W) includes the Package Assembly Director, which displays a series of forms that guide you through the steps of naming the package and adding the objects that you want to include in the package.
Define the package build.
After you assemble the package, you must define the build before you can deploy the package to the workstations and servers. In this step, you specify:
Build options.
Build specification options.
Business functions build options.
Compression options.
Build features options.
You also need to specify whether the package is for a workstation, a server, or both. If the package is for servers, you must specify the servers for which the package should be built and select the spec database data source.
To simplify the build process, Oracle's JD Edwards EnterpriseOne Package Build Director application (P9621/P9621W) includes the Package Build Definition Director, which displays a series of forms that guide you through the steps of specifying where to build the package, whether to include specifications, whether to compress or build business functions, and so on.
Build the package.
During the actual build process, the system takes the information that you provided when you assembled and defined the package and copies and converts central objects to the package. It also globally builds the business functions that are included in the package and then compresses the package.
Schedule the package for deployment.
After you have defined and built the package, it is ready for distribution. Depending on the package type, you can deploy packages through JD Edwards EnterpriseOne Client Workstation Installation application or Deployment Director application (P9631/P9631W).
JD Edwards EnterpriseOne Deployment Director enables you to specify the workstations and servers that receive the package, as well as when the package is made available. Packages can be deployed to all computers within the enterprise, a select group of computers, or individual computers.
When you schedule the package, you can indicate whether package installation is mandatory or optional.
Deploy the package to deployment, enterprise, and web servers.
Use the JD Edwards EnterpriseOne Deployment Director application to move any changed objects to the enterprise server.
If you specify a server during the package build definition process, the system automatically creates a corresponding server package in the correct format. If you do not specify a server and define only a workstation package, you should create a corresponding server package. The process is nearly identical to creating a workstation package.
Web servers automatically retrieve the package information from their configured business function logic servers.