Understanding the Deployment Director

After you define and build a package, use the JD Edwards EnterpriseOne Deployment Director program (P9631//P9631W) to schedule the package for deployment to individual workstations, deployment servers, or enterprise servers. On the specified deployment date, users who are scheduled to receive the package can load the package when they sign in to JD Edwards EnterpriseOne.

Alternatively, you can schedule the package to deployment groups or locations instead of specific machines. Deployment groups are useful in large enterprises that routinely deploy packages to many workstations and servers.

The JD Edwards EnterpriseOne Deployment Director program (P9631/P9631W) simplifies and expedites the process of scheduling and deploying built packages to workstations and servers. The director displays a series of forms that enable you to specify the package that you want to deploy, the deployment destinations, and the deployment time.

After specifying the package that you want to deploy, you specify any of these destinations:

• Client workstation.

• Enterprise Server.

• Deployment Server or Deployment groups.

• Locations.

You can deploy a package either to specific workstations and servers, or you can schedule the deployment based on deployment groups or location. You cannot do both; you must select one of these methods.

You can make the package mandatory, which means that users cannot access the software until they have installed the package. If the package is optional, users will be given the option of installing the package every time that they sign in until they either install or decline the package.

Note: The Mandatory Installation option is applicable to client packages only.

The JD Edwards EnterpriseOne Deployment Director requires that JD Edwards EnterpriseOne already be loaded on the workstation. You can schedule a new full package to replace the existing package, or an update package to be merged with the existing package on the workstation.

The JD Edwards EnterpriseOne Deployment Director uses these tables:

• F9650

• F9651

• F9652

• F9653

• F9654

• F98825

• F988251

• F98826

• F9603

• F96031

• F98826H

• F988259

This table summarizes the function of each form in the JD Edwards EnterpriseOne Deployment Director:

Form Name	Form Usage
Package Deployment Director form	View this form for a description of the JD Edwards EnterpriseOne Deployment Director.
Package Selection form	Use this form to find and select the package that you want to deploy.
Package Deployment Targets form	Use this form to specify the destination for the package. You can select individual client workstations, deployment servers, and enterprise servers, or you can deploy the package to a deployment group or location.
Package Deployment Attributes form	Use this form to enter the date and time that you want to deploy the package. Also specify whether the package is mandatory (that is, it must be installed by every package recipient).
Deployment Client Workstation Selection form	Use this form to select each of the client workstations that will receive the package.
Deployment Server Selection form	Use this form to select each of the deployment servers that will receive the package.
Enterprise Server Selection form	Use this form to select each of the enterprise servers that will receive the package.
Deployment Location Selection form	Use this form to specify the deployment location that will receive the package.
Deployment Groups Selection form	Use this form to specify the deployment groups whose members will receive the package.
Build Selection form	For multitier deployment, use this form to specify the server or client package that you want to deploy to the destination deployment server.
Work with Package Deployment form	Use this form to review and revise the locations and package recipients that you entered through the JD Edwards EnterpriseOne Deployment Director.