Deploying Packages

This chapter provides an overview of package deployment and discusses how to:

Click to jump to parent topicUnderstanding Package Deployment

After you assemble and build a package, you can select from several methods of deploying the package to workstations and servers throughout the enterprise. For workstations, the method that you select depends on whether Oracle's JD Edwards EnterpriseOne is already installed on the workstation.

This section discusses:

Click to jump to top of pageClick to jump to parent topicDeploying to Workstations Without JD Edwards EnterpriseOne

If JD Edwards EnterpriseOne is not currently installed on a workstation, you can deploy the package through Oracle's JD Edwards EnterpriseOne Workstation Installation program. You can use JD Edwards EnterpriseOne Workstation Installation to deploy full packages, but you cannot use JD Edwards EnterpriseOne Workstation Installation to deploy an update package to a workstation on which JD Edwards EnterpriseOne is not installed.

JD Edwards EnterpriseOne Workstation Installation retrieves items that are specified in the package. A package is like a bill of materials with instructions that describe from where the system retrieves all of the necessary components that the JD Edwards EnterpriseOne Workstation Installation program deploys to the local workstation. This program can be run interactively (initiated by a person at a workstation) or in silent mode and scheduled through the push installation feature.

If you use the push installation feature, you can use Oracle's JD Edwards EnterpriseOne Package Deployment to deploy the package. Push installation enables the administrator to initiate the installation of a package from the deployment server to workstations without any user interaction. To use this feature, the push installation listener application must be installed on the workstation, and the machine must be defined through Oracle's JD Edwards EnterpriseOne Deployment Locations application (P9654A).

See Also

JD Edwards EnterpriseOne Application Release 9.0 Installation Guide

Click to jump to top of pageClick to jump to parent topicDeploying to Workstations with JD Edwards EnterpriseOne Already Installed

To reload a new package on workstations on which JD Edwards EnterpriseOne is already installed, use one of two methods:

After you assemble and build a package, use JD Edwards EnterpriseOne Deployment Director to schedule the package for deployment to individual workstations or to selected groups. On the specified deployment date, when the users who are scheduled to receive the package sign in, they are given the opportunity to load the package.

Unless you are using the Push Installation feature, JD Edwards EnterpriseOne Deployment Director requires that JD Edwards EnterpriseOne be already 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.

Both deployment methods have advantages. JD Edwards EnterpriseOne Workstation Installation is a good method to use when you want to install a package immediately or soon after it is built, without having to schedule the package. Alternatively, JD Edwards EnterpriseOne Deployment Director is useful if you need to control when the package becomes available, if you want to make the package installation mandatory, or if you want to deploy the package to servers as well as to workstations.

Click to jump to top of pageClick to jump to parent topicDeploying 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), 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. You cannot use the Push Installation feature to deploy to servers.

Click to jump to top of pageClick to jump to parent topicDeploying to Tiered Locations

Multitier deployment enables you to install software on workstations from more than one deployment location and more than one deployment machine. Use this deployment method if your site has more than 50 workstations performing software installations per day, or when workstation installations over your wide area network (WAN) are too slow.

Click to jump to top of pageClick to jump to parent topicDeploying to Workstations from CD

If your system has a CD writer, you can define the CD writer as a deployment location. Essentially, you define the CD writer as a pseudo deployment server from which you can copy a package onto a blank CD. You can then use this CD to install the software on workstations by using the JD Edwards EnterpriseOne Workstation Installation program that is included on the CD.

Click to jump to parent topicDefining Deployment Parameters

This section provides an overview of deployment parameters, provides prerequisites, and discusses how to:

Click to jump to top of pageClick to jump to parent topicUnderstanding Deployment Parameters

Before you deploy packages, you must identify the workstations, servers, groups, or locations that will receive the package. Identifying these ensures that, when you are ready to schedule packages using the JD Edwards EnterpriseOne Deployment Director, the machines, groups, or locations that you want to receive the package will be available as package recipients.

A deployment group is a group of workstations that are classified by a criterion such as job function, team, or any other grouping that you specify. For example, you might have a software development group, a testing group, a production group, and so on. Oracle's JD Edwards EnterpriseOne Package Deployment Groups Revisions program (P9652A) enables you to define or revise groups that include several workstations.

A location is a group of workstations and servers that corresponds to a physical location. For example, you might have locations for Corporate and Branch, or for Building 5 and Building 7. Locations are also useful if you use multitier deployment or deploy across a WAN. In this case, you might define a location for each of your geographic locations. The JD Edwards EnterpriseOne Deployment Locations Application program (P9654A) enables you to define or revise machines and locations in your enterprise.

Both of these applications simplify the deployment process when you need to deploy a package to several users. Rather than requiring you to schedule deployment to each workstation or server, you can schedule deployment according to location or group.

When you enter a machine definition, you are really defining its usage in the configuration. For example, you can use a deployment server as a data server. When you enter machine definitions, consider these recommendations:

Locations

In some cases, an enterprise might span several buildings, cities, or countries. In these situations, you might deploy a package to a location rather than to individual workstations and servers. Then, a secondary deployment server at each location can deploy the package to the workstations and servers at that location.

The larger your enterprise, the more you can benefit from creating and deploying to locations. If you use multitier deployment to deploy packages to remote locations, the concept of locations is crucial.

In JD Edwards EnterpriseOne, a location is essentially a user-defined group of machines, databases, and environments. In some cases, the location is an actual physical location that is connected by a WAN, such as when you have remote offices that are geographically separate from your main office. For example, a location might be a floor in your office building, a separate building on the corporate campus, a branch office across town, or a facility in another city.

After you create a new location, you can add workstations and servers for that location by defining the machine names that are associated with that location.

The topmost location that appears when you launch the JD Edwards EnterpriseOne Deployment Locations Application program (P9654A) is the base location. You cannot change or remove this base location, but you can create or revise locations that are subordinate to it.

When you create a location that is subordinate to another location, the original location is the parent location, and its subordinate location is the child location. For example, if you have a location called Seattle and then create a location called Redmond that is subordinate to Seattle, Seattle is the parent location and Redmond is the child location.

Deployment Groups

You can create a deployment group based on department, team, or function. For example, you might have an administration group, a testing group, a production group, and so on.

Package deployment groups are particularly useful in large enterprises in which scheduling a package for deployment to several individual workstations is very time consuming. In these environments, you can deploy packages much more quickly when you use deployment groups.

A group can contain a subgroup (a group within a group). For example, you might have a group called Quality Assurance that is a subgroup of the larger Development group.

You can help the person who builds and schedules packages by creating easily identifiable names for deployment groups. For example, for a group that includes quality assurance specialists who are responsible for testing, name the group Testing, rather than Green Team.

See Also

Setting Up Multitier Deployment

Click to jump to top of pageClick to jump to parent topicPrerequisites

Before you use the JD Edwards EnterpriseOne Deployment Director to deploy a package to individual client workstations, verify that each machine that will receive the package has a record in the Machine Master table (F9650).

Select one of these ways to populate the F9650 table:

The simplest way to populate the F9650 table is to have all users on new machines sign in. In cases in which you need to deploy a package before the users can sign in, you must manually enter machine information. The JD Edwards EnterpriseOne Deployment Locations application enables you to perform this task.

In addition to defining workstations, you can also use the JD Edwards EnterpriseOne Deployment Locations application to enter or revise definitions for these machines:

You can enter or revise definitions for these machines in multiple locations, including remote locations.

Click to jump to top of pageClick to jump to parent topicForms Used to Define Deployment Parameters

Form Name

FormID

Navigation

Usage

Work with Locations and Machines

W9654AA

Package and Deployment Tools (GH9083), Machine Identification

Click Add to add a new location or machine, or click Select to revise an existing location or machine.

Create or revise deployment locations or machines.

Deployment Group Revisions form

W9652AB

Package and Deployment Tools (GH9083), Machine Group Identification

Click Add to add a new deployment group, or click Select to revise an existing group.

Create or revise package deployment groups.

Click to jump to top of pageClick to jump to parent topicDefining Machines

Access the Work with Locations and Machines form.

  1. Highlight the type of machine you would like to create.

  2. Click Add.

  3. Enter the appropriate values for the type of machine you are creating.

Workstation

Deployment Server Name

Enter the name of the specific server that is being used for deployment.

When you define a secondary deployment server, options on the Form menu enable you to select path codes, data items, foundation modules, and help items. (These options are not available for the primary deployment server.)

Deployment Server

Primary Deployment Server

Specify whether a deployment server is the primary deployment server for a specific location.

If you have set up a primary deployment server, you cannot access the Primary Deployment Server field when you define a new deployment server. You can change the value in this field only when you revise the primary deployment server definition or when you change the primary deployment server to a secondary server. In this case, you can specify a different server as the primary deployment server.

Server Share Path

Enter the shared directory for this path code. The objects that are stored on a file server will be found in this path.

Enterprise Server

Port Number

Identify the port for a given instance of JD Edwards EnterpriseOne. Because the jde.ini file controls the port to which a workstation will connect, for workstations this port number is for reference only.

Logical Machine Name

Enter the logical machine name that is assigned to this unique machine and port. A machine can be a workstation. Because you can have more than one instance of JD Edwards EnterpriseOne running on a given machine, you must assign a logical machine name that identifies the unique physical machine name and port where this instance runs.

The logical machine name should represent the release and purpose of the machine, such as Financial Data Server-E900 or Distribution Logic Server-E900.

Database Type

Enter the type of database.

Server Map Data Source

Enter the name that identifies the data source.

Installation Path

Enter the path on which JD Edwards EnterpriseOne is installed.

Deployment Server Name

Enter the name of the specific server that is being used for deployment.

When you define a secondary deployment server, options on the Form menu enable you to select path codes, data items, foundation modules, and help items. (These options are not available for the primary deployment server.)

Server Availability

This field is visible only in Update mode. Use this field to reset the enterprise server status if a package deployment failed.

Data Server

Data Source Type

Enter the type of database.

HTML Server

Protocol

Specify the method of communication (for example, http).

Server URL

Enter the URL to the web server.

Http Port

Enter the port number of the web server.

Default Login

Enter the login path.

Installation Path

Enter the path on which JD Edwards EnterpriseOne is installed.

Deployment Server Name

Enter the name of the specific server that is being used for deployment.

Crystal Enterprise Web Server

Port Number

Enter the port number for the Crystal Enterprise web server.

Crystal Enterprise CMS

User ID

Enter the user name with which JD Edwards EnterpriseOne will connect to Crystal Enterprise for the purpose of running scheduled reports. This user, along with the associated password, must identify a valid Crystal Enterprise user with the necessary authority to execute reports.

Password

Enter the password that JD Edwards EnterpriseOne will use to connect to Crystal Enterprise for the purpose of running scheduled reports. This password, along with the associated user ID, must identify a valid Crystal Enterprise user with the necessary authority to execute reports.

Password -Verify

Reenter the password.

Business Services Server

The Business Services Server cannot be added through this application. You must use Server Manager to add a new Business Services Server.

See the JD Edwards EnterpriseOne Tools Release 8.98 Server Manager Guide on the Update Center.

Click to jump to top of pageClick to jump to parent topicDefining Locations

Access the Location Revisions form by clicking Add on the Work with Locations and Machines form.

Location

Enter the name of the deployment location.

Location Code

Represent the current location for system deployment.

Parent Location

Enter the name of the parent location.

Click to jump to top of pageClick to jump to parent topicDefining Package Deployment Groups

Access the Deployment Group Revisions form.

Deployment Group Name

Enter a profile to use to classify users into groups for system security purposes. You use group profiles to give the members of a group access to specific programs.

Some rules for creating a profile for a user class or group are:

  • The name of the user class or group must begin with an asterisk (*) so that it does not conflict with any system profiles.

  • The User Class/Group field must be blank when you enter a new group profile.

Deployment Group Description

Enter the description for the selected deployment group.

Workstation

Specify the name of the machine on the network .

Workstation Description

Enter a user-defined name or remark.

Deployment Group

Specify a group that is defined to be part of a parent group.

Click to jump to top of pageClick to jump to parent topicRevising Package Deployment Groups

Access the Deployment Group Revisions form.

Note. When you revise an existing group, you cannot change the group name, but you can change the description.

  1. To add to the group, select the last row (the empty one) and enter the name of the workstation or deployment group to which you want to add members.

  2. Type the name in the Workstation field or the Deployment Group field, or use the search button for those fields.

    When you use the search button for the Workstation field, the Machine Select form appears. When you use the search button for the Deployment Group field, the Deployment Group Search form appears.

Click to jump to parent topicWorking with Package Deployment

This section provides an overview of the JD Edwards EnterpriseOne Deployment Director and discusses how to:

Click to jump to top of pageClick to jump to parent topicUnderstanding the Deployment Director

After you define and build a package, use the JD Edwards EnterpriseOne Deployment Director program (P9631) 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) 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:

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.

In addition, you can specify a push installation, which means that the package can be deployed from the deployment server to the workstations that you specify, without requiring any interaction from the user.

Note. Mandatory and Push Installation options are applicable to client packages only.

The JD Edwards EnterpriseOne Deployment Director requires that JD Edwards EnterpriseOne already be loaded on the workstation, unless you are using push installation. 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:

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

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) and whether you want to use push installation to deploy the package.

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.

Using the Deployment Director

After you have assembled and built the package, defined all machines, and verified the deployment groups, use the JD Edwards EnterpriseOne Deployment Director to specify package recipients and schedule the package for deployment.

Throughout the deployment process, you can select to either proceed to the next form or return to the previous form. Also, regardless of where you are in the process, you can cancel it.

When you schedule a package for deployment to a machine rather than a deployment group or location, you can schedule to deploy the package to client workstations, deployment servers, enterprise servers, or a combination. The forms that appear vary depending on your selection. For example, if you indicate that you want to schedule a package for deployment to client workstations and a deployment server, the forms for selecting specific workstations and deployment servers appear. If you schedule a package for deployment only to client workstations, the server selection form does not appear.

When you access the JD Edwards EnterpriseOne Deployment Director, the Work with Package Deployment form enables you to view deployed package information by either machines, deployment groups, locations, or packages.

Depending on your display selection, the tree displays different information when you expand it. This list describes the information that appears as you expand the tree level by level:

Activating Scheduled Packages

After you successfully define a package deployment, you must activate the package so that it is available for installation using the JD Edwards EnterpriseOne Workstation Installation program. If you do not activate the package, it will not be included in the list of available packages when users launch the JD Edwards EnterpriseOne Workstation Installation program.

In some situations, you might need to control which packages are available for installation. If, for example, you have a package that is for the testing group only, you would want to make that package inactive so that it is not available for installation through the JD Edwards EnterpriseOne Workstation Installation program. Instead, you can use JD Edwards EnterpriseOne Deployment Director program (P9631) to schedule this package for deployment to the members of the testing group.

Installing a Scheduled Package

When users receive a package, they can select to install it when they sign in to JD Edwards EnterpriseOne on or after the scheduled deployment date.

If the package is mandatory, users cannot access the system until they load the package.

If the package is optional, users can decline the package or postpone the installation until later. If they decide to postpone the installation, the software launches, and they will be given the opportunity to install the package the next time that they sign in.

If a package that is scheduled for push installation fails to load for some reason (such as if the power to the workstation was turned off during the time that the package was scheduled to deploy), that package will be included in the list of available packages when the user signs in.

See Also

Scheduling the JD Edwards EnterpriseOne Push Installation Batch Application

Click to jump to top of pageClick to jump to parent topicForms Used to Work with Package Deployment

Form Name

FormID

Navigation

Usage

Work with Package Deployment

W9631J

Package and Deployment Tools (GH9083), Package Deployment

Select the package to deploy and review your selections.

Package Selection

W9631C

Package and Deployment Tools (GH9083), Package Deployment.

Click Add on the Work with Package Deployment form to launch the Deployment Director. Click Next.

Select the package to deploy.

Package Deployment Targets

W9631B

On Package Selection, click Next.

Select the types of machines on which to deploy the package.

Package Deployment Attributes

W9631D

On Package Deployment Targets, click Next.

Select the type of installation and the time.

Deployment Client Workstation Selection

W9631F

On Package Deployment Targets, select Client Workstation and click Next until the Deployment Client Workstation Selection form appears.

Select the workstations to which the package will be deployed.

Deployment Server Selection

W9631G

On Package Deployment Targets, select Deployment Server and click Next until the Deployment Server Selection form appears.

Select the Deployment Servers to which the package will be deployed.

Build Selection

W9631N

On Package Deployment Targets, click Next until the Build Selection form appears.

Select the server package build to deploy to the destination deployment server.

Enterprise Server Selection

W9631E

On Package Deployment Targets, select Enterprise Server and click Next until the Deployment Server Selection form appears.

Select the Enterprise Servers to which the package will be deployed.

Server Package Deployment Properties Revisions

W9631M

Package and Deployment Tools (GH9083), Package Deployment.

Select Machines, and click Find to display information according to machine name. Find and select the deployed package for which you want to modify the options, and then select Properties from the Row menu.

Revise server package deployment options.

Click to jump to top of pageClick to jump to parent topicScheduling a Package for Deployment

Access the Package Selection form.

  1. Select the package that you want to deploy, and then click Next.

  2. On the Package Deployment Targets form, select any of these options to indicate the type of machines to which you want to deploy the package, and then click Next:

  3. On Package Deployment Attributes, complete these fields:

  4. If you want to deploy the package using push installation, which pushes the package to workstations from the deployment server, select the Enable Push Installation option, and then click Next.

    If you are deploying to workstations, the Deployment Client Workstation Selection form appears. If you are not deploying to workstations, bypass the next step.

  5. Find and select the workstations to which you want to deploy the package, and then click Next.

    Select a workstation by double-clicking in its row header. A check mark appears in the row header for each workstation that you select.

    If you are deploying to a deployment server, the Deployment Server Selection form appears. If you are not deploying to a deployment server, bypass the next step.

  6. Find the deployment server to which you want to deploy the package, and then click Next.

    Select a server by double-clicking in its row header. A check mark appears next to each server that you select.

  7. On the Build Selection form, select the server package build that you want to deploy to the destination deployment server, and then click Close.

  8. Click Next.

    If you are deploying to an enterprise server, the Enterprise Server Selection form appears. If you are not deploying to an enterprise server, bypass the next step.

  9. Find and select the enterprise server to which you want to deploy the package, and then click Next.

    Select a server by double-clicking in its row header.

    Note. You can deploy an update package only to servers that have the full parent package deployed.

  10. On Work with Package Deployment, review your deployment selections.

  11. To change any of the selections, click Prev to return to the appropriate previous form.

  12. When you are finished reviewing and changing the deployment selections, click End.

  13. If you are deploying a server package, find and select the server package on the Work with Package Deployment form, and then select Deploy from the Row menu.

After you schedule the package for deployment, at the specified time on the date that you specified, the package deploys to workstations. This package becomes available to the user when the user signs in.

If you are using push installation, the package automatically installs at the time that you specify in Oracle's JD Edwards EnterpriseOne Schedule Jobs program (P91300).

To schedule a package for deployment to a deployment group or location:

  1. On the Package Selection form, select the package that you want to deploy, and then click Next.

  2. On the Package Deployment Targets form, select either Deployment Group or Locations, and then click Next.

  3. On the Package Deployment Attributes form, complete these fields:

  4. If you want to deploy the package using push installation, which pushes the package to workstations from the deployment server, select the Enable Push Installation option.

  5. Click Next.

    If you are deploying to a deployment group, the Deployment Groups Selection form appears. If you are deploying to a location, bypass the next step.

  6. Find and select the deployment group that you want to receive the package, and then click Next.

    Select a group by double-clicking its row header.

  7. If you are deploying to a location, the Deployment Location Selection form appears. Bypass the next step if you are deploying to a deployment group.

  8. Find and select the deployment location that you want to receive the package, and then click Next.

    To select a location, double-click the row header.

  9. On the Work with Package Deployment form, review the deployment selections.

  10. To change any of the selections, click Prev to return to the appropriate previous form.

  11. When you are finished reviewing or changing the deployment selections, click End.

  12. If you are deploying a server package, find and select the server package on the Work with Package Deployment form, and then select Deploy from the Row menu.

After you schedule the package for deployment, at the specified time on the date that you specified, the package deploys to workstations. This package becomes available to the user when the user signs in.

If you are using push installation, the package automatically installs at the time that you specify in the JD Edwards EnterpriseOne Schedule Jobs program (P91300).

See Also

See the following topics in the JD Edwards EnterpriseOne Package Management Guide:

Scheduling the JD Edwards EnterpriseOne Push Installation Batch Application

Scheduling a Package for Push Installation

Understanding the Deployment Director

Click to jump to top of pageClick to jump to parent topicRevising Deployment Options

Access the Server Package Deployment Properties Revisions form.

Package Name

Enter a name for the package.

A package describes the location on the server where components that you want to deploy to workstations or servers reside. Two package types are available:

Full: Contains the full suite of applications (all specifications).

Update: Objects contained in this type of package are loaded after the workstation or server receives the package and the user signs in to the system. If the update package includes just-in-time applications, old versions of the application are deleted from the workstation and replaced by the current version the first time the user accesses that application. Update packages are always deployed on the date and time that are specified by the system administrator.

With the exception of just-in-time applications that are included in an Update package, all packages are a snapshot at a point in time of the central objects for a particular path code. Just-in-time applications are dynamic, not built.

Path Code

Enter the path code.

The path code is a pointer to a set of objects and is used to keep track of sets of objects and their locations.

Mandatory Installation

Indicate whether the package is mandatory or optional.

Valid choices are:

Y: The deployment is mandatory. The user must install the package.

N: The deployment is optional to the user.

Enable Push Installation

Select this option to enable the package to be installed through push installation.

Date

Enter a date to deploy updated objects to the listed machine.

Click to jump to top of pageClick to jump to parent topicActivating the Scheduled Package

Access the Work with Package Deployment form.

  1. Click Find.

  2. Select from the list the packages that you want to activate or inactivate.

    Alternatively, you can enter the package name in the Package field.

  3. Select Active/Inactive from the Row menu.

Click to jump to top of pageClick to jump to parent topicInstalling a Scheduled Package

  1. Sign in to JD Edwards EnterpriseOne.

    When you are scheduled to receive a package, Oracle's JD Edwards EnterpriseOne Just-In-Time Installation program launches and the Scheduled Packages form appears.

  2. Perform one of these steps:

  3. To load the package, select one or more packages that you want to install and click Select.

    The JD Edwards EnterpriseOne Workstation Installation program loads the package. If you selected more than one package, the program installs them sequentially. When the installation is complete, the software launches.

Click to jump to parent topicDeploying a Server Package

This section provides overviews of server package deployment and deployment to web servers, lists prerequisites, and discusses how to deploy a server package.

Click to jump to top of pageClick to jump to parent topicUnderstanding Server Package Deployment

The process for deploying a server package is nearly identical to that for deploying a package to a workstation. In both cases, you need to assemble, define, build, and schedule the package for deployment by using the JD Edwards EnterpriseOne Package Assembly (P9601), Package Build Director (P9621), and Deployment Director (P9631) programs.

After you schedule a server package for deployment, you must complete an additional step to launch the batch program that enables you to deploy to servers. You must perform this task whenever you deploy a package to an enterprise server or deployment server.

Important! Deploy server packages only when necessary, because the enterprise server is not available to process business applications and batch processes during the installation process. The enterprise server does not actually shut down during package installation. Instead, the system queues any jobs that are submitted to the enterprise server and runs them as soon as the installation finishes. For this reason, you should schedule enterprise server packages to be deployed after hours to minimize impact on users. (Before you deploy a package to an enterprise server, verify that the services have been started and no UBEs are active.)

To further minimize impact on the network and users, if the development environment is on the same enterprise server as the production environment, consider preventing developers from moving their own objects through server packages. Instead, require that an administrator perform this function.

To deploy a server package, select Deploy from the Row menu on the Work with Package Deployment form. This is the same function that you use to deploy packages to deployment servers during multitier deployment.

The system determines which of the batch programs to call, based on what is currently selected on the Work with Package Deployment form when you select Deploy from the Row menu:

When the system launches a batch program for all servers or all packages, deployment does not occur unless the package has been previously scheduled for a specific server. A full package can be deployed to all servers. However, an update package can be deployed only to servers that already have the parent package deployed. Also, update packages cannot be deployed if the parent package is an inactive or not-deployed full package.

When the system launches the batch program to deploy a package to an enterprise server, the batch process:

  1. Verifies that the enterprise server deployment location is the same as the Microsoft Windows 2000 client submitting the package.

  2. Changes the enterprise server status to Pre Deploy.

    This is done by changing the MDMCHRCDNM column to 50 in the F9651 table.

  3. Waits for five minutes.

  4. Sends lock messages to all the selected enterprise servers.

  5. Once the servers are locked, the batch process marks them as unavailable.

    This is done by changing the MDMCHRCDNM column to 10 in the F9651 table.

  6. Copies the BSFN executables from the package location to the live path code location.

  7. Sets the spec.ini file to the new package and spec data source.

  8. Sends unlock messages to all the enterprise servers.

  9. Marks the servers as available.

    This is done by changing the MDMCHRCDNM column to 30 in the F9651 table.

  10. Updates the F96511 table with the new package and spec data source information.

    This information is used by the web servers.

Note. If the batch process fails to get a lock on all of the selected enterprise servers, it will not deploy the package.

If a package deployment fails, the servers are marked as unavailable. The system administrator might have to restart the services on the enterprise server to make them available again. He can also reset the status with Oracle's JD Edwards EnterpriseOne Machine Detail application (P9654A).

A deployed package can be deployed multiple times to the same or different servers.

A server package with the specs built in a shared mode can be deployed to a web server. This process of deploying to the web server is automatic and does not require any end user intervention. The web servers pool the package information from the JD Edwards EnterpriseOne logic server. It compares the package manifest from the spec tables to the one in its serialized database and makes the necessary updates.

During server package deployment, the business function (BSFN) dll's, SRVPGMs, .so objects, or .sl objects of the live package are replaced by the objects from the built package. However, if a deployment fails, you may have a mismatched set of BSFNs and specs. With 8.96 JD Edwards EnterpriseOne clients, you can back up the existing BSFN objects. If the deployment fails, you can restore the BSFN objects. The option to back up the live BSFN objects before deployment can be enabled through the Build Settings within Server Manager.

For an AS/400, the BSFN objects in PY900 are copied into the $PY900 library. For Microsoft Windows 2000 and UNIX, the BSFN and spec objects in PY900 are copied to the PY900_BACK folder. Clients can restore BSFN objects by copying the objects from the backup location to the live folder. They can restore the specs by changing the package name to the previous package in the spec.ini file.

Click to jump to top of pageClick to jump to parent topicUnderstanding 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.

The process for deploying packages to web servers is:

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

  2. The five 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.

Click to jump to top of pageClick to jump to parent topicPrerequisites

Before you complete the tasks in this section:

Click to jump to top of pageClick to jump to parent topicForm Used to Deploy Server Packages

Form Name

FormID

Navigation

Usage

Work with Package Deployment

W9631J

Package and Deployment Tools (GH9083), Package Deployment

Select the package to deploy and review your selections.

Click to jump to top of pageClick to jump to parent topicDeploying a Server Package

Access the Work with Package Deployment form.

  1. Locate the server package that you want to deploy.

    Alternatively, select the enterprise server or, if the package is scheduled to deploy to more than one server, the Enterprise Server folder.

  2. Select Deploy from the Row menu.

  3. On Report Output Destination, select On Screen.

  4. Click OK.

Click to jump to parent topicUsing Push Installation

This section provides an overview of Push Installation and discusses how to:

Click to jump to top of pageClick to jump to parent topicUnderstanding Push Installation

Push installation is the only deployment method that provides automatic and unattended package deployment. This means that the system administrator can deploy a package (or several packages) to a workstation or group without requiring any action from workstation users.

For example, an administrator might schedule a package to deploy to a particular group after hours. When members of that group report to work the following morning, that package is available for immediate use.

Push installation is particularly useful in situations in which you need to quickly deploy packages with a minimum of intrusion or impact upon your normal production and development routines. By planning and scheduling package deployment judiciously, administrators can also minimize the impact upon network performance that can accompany large numbers of package deployments. Administrators can also use push installation to install the software on a workstation for the first time. This ability can greatly minimize downtime and provide maximum deployment flexibility.

During push installation, package contents are pushed from the deployment server to the workstation. In contrast to push installation, the JD Edwards EnterpriseOne Workstation Installation program pulls package contents from the deployment server to the workstation. Installations that are set up to use JD Edwards EnterpriseOne Deployment Director (P9631) for scheduled packages that are not push enabled also pull packages.

The end result of the deployment is the same, regardless of whether package contents are pushed or pulled. However, the advantage of a push installation is that no action is required from the workstation user other than to leave the workstation turned on during the time when the package is scheduled to deploy.

For an update package that contains program specifications, the term package contents refers to specifications. For a full package or an update package that does not contain application specifications, package contents refers to objects.

Push Installation Process

This list summarizes the steps in the push installation process:

  1. Install a push installation JD Edwards EnterpriseOne Listener program on each workstation that will receive pushed packages.

    Oracle's JD Edwards EnterpriseOne Listener monitors the progress of Oracle's JD Edwards EnterpriseOne Push Package Installation batch program (R98825) that runs on the server and performs functions such as monitoring installation status. The JD Edwards EnterpriseOne Listener can run as either a local service or a network service.

  2. Schedule the package using the JD Edwards EnterpriseOne Deployment Director program (P9631).

    The JD Edwards EnterpriseOne Push Package Installation batch program reads the scheduling table and sends a message to the JD Edwards EnterpriseOne Listener on all workstations for which a package has been scheduled.

  3. Use the JD Edwards EnterpriseOne Schedule Jobs program (P91300) to launch the batch program on the enterprise server.

    This program enables you to specify the job name, version, start date, start time, and recurrence.

  4. At the specified start time, the JD Edwards EnterpriseOne Schedule Jobs program launches the JD Edwards EnterpriseOne Push Package Installation batch program (R98825), which initiates the package installation process from the deployment server.

    The JD Edwards EnterpriseOne Listener and the batch program interact during the process until installation is complete. Codes are passed from the JD Edwards EnterpriseOne Listener to the batch program to indicate the installation status (such as failed, successful, in progress, and so on).

  5. When the installation finishes, the system sends an email message to the primary user of the workstation.

    This message indicates whether the installation was successful. Email notification works only if the package recipient is listed in the Machine Master table (F9650) and has an email address in the profile.

  6. If the push installation fails for some reason (such as when the package recipient neglects to leave the workstation turned on), the installation status changes to Failed.

    If you want to reschedule the installation, you must first delete the row with the failed job, and then schedule the job again.

If the push installation is not successful, when the user signs on, the standard scheduling screen appears. At this point, the user can either accept the mandatory package or quit the program.

Installing the JD Edwards EnterpriseOne Listener

When you install the JD Edwards EnterpriseOne Listener on the workstations in your enterprise, you specify whether to run a local service or a network service. If you run the service locally on the workstation, the user must be signed in to receive a package that has been scheduled for push installation. If you run the service on the network, the JD Edwards EnterpriseOne Listener runs as a network account and the user does not have to be signed in to receive a package through push installation. The network service must have an administrator's user ID.

The disadvantage of running the service on the network is that it can be difficult to administer for all users on the enterprise. For example, because the parameters of the JD Edwards EnterpriseOne Listener apply to every user on the network, push installation users must install to and from the same locations. One user could have the software on drive C and another user have the same release on drive D. Also, every time users change their sign—in passwords, the system administrator must update the JD Edwards EnterpriseOne Listener service with the new passwords for the service to work for those users. For these reasons, you should install the JD Edwards EnterpriseOne Listener locally on each workstation.

Whether you run the JD Edwards EnterpriseOne Listener as a local service or network service, the workstation must be turned on to receive a scheduled package.

You can select from one of these ways to install the JD Edwards EnterpriseOne Listener on a workstation:

Installing the Listener Using Silent Installation

In some cases, installing the JD Edwards EnterpriseOne Listener on workstations using silent installation might be more convenient than standard installation. Typically, the administrator performs this task. Using this method, the administrator enters configuration settings for all workstations and distributes a batch file that automatically initiates the JD Edwards EnterpriseOne Listener installation the next time that the user signs in to the workstation.

The advantage of using silent installation to install the JD Edwards EnterpriseOne Listener is that the process is transparent to workstation users, and users are not required to enter configuration information or step through the installation process.

Click to jump to top of pageClick to jump to parent topicForms Used to Use Push Installation

Form Name

FormID

Navigation

Usage

Scheduling Information

W91300A

Job Scheduler (GH9015), Schedule Jobs

Select the time zone that applies to your setup and click Select. Click Add to enter a new job.

Schedule the Push Installation Batch Application.

Push Package Installation Results

NA

Package and Deployment Tools (GH9083), Push Package Installation Results

Verify the status of a pushed package.

Click to jump to top of pageClick to jump to parent topicPreparing the Enterprise Server for Push Installation

To set up the server for push installation, you must first install and configure the Microsoft Domain Name Service (DNS) that is included with the Microsoft Windows Server. If you have not yet set up a domain name service, you can install Microsoft DNS by clicking the Network button in the Control Panel, then selecting the Services tab, and then adding Microsoft DNS Server.

After you add Microsoft DNS, you must configure the DNS by specifying the domain name and servers.

UNIX and iSeries Considerations

In an environment that is configured for Dynamic Host Configuration Protocol (DHCP), a server must run Windows Server to resolve workstation addresses because the Windows server dynamically assigns them.

To enable name resolution, you need to configure the servers to resolve their IP address lookup through a Windows DNS server, which, in turn, must be configured to review the WINS database when DHCP is enabled in the network domain.

Configuring the servers in this way ensures that this process flow occurs during the push installation process:

  1. From the host server on which the JD Edwards EnterpriseOne Push Installation batch program (R98825) runs, a business function attempts to retrieve the machine host address from the DNS server.

  2. Because the DNS server does not contain IP addresses, it retrieves the address from the WINS server.

  3. The WINS server returns the address to the DNS server.

  4. The DNS server returns the address to the host server.

  5. The host server finds the JD Edwards EnterpriseOne Listener on the client workstation and sends workstation installation information.

  6. The workstation installation process starts.

Click to jump to top of pageClick to jump to parent topicPreparing Workstations for Push Installation

Before you can push an installation to a workstation, you must install a JD Edwards EnterpriseOne Listener on the workstation, which interacts with a business function that runs on the server. You must install this JD Edwards EnterpriseOne Listener on all workstations that you want to be enabled for push installation, regardless of whether you want to deploy packages to a machine on which JD Edwards EnterpriseOne is already installed or a machine on which you are installing JD Edwards EnterpriseOne for the first time.

The JD Edwards EnterpriseOne Listener runs continuously on the Windows workstation as a service (and on a Windows 95 machine as a pseudo-service), and administrators can monitor it using the Task Manager. The JD Edwards EnterpriseOne Listener communicates with the batch application on the server, receiving and sending messages during the installation process. The JD Edwards EnterpriseOne Listener also monitors the progress of the installation and saves the installation completion code.

Click to jump to top of pageClick to jump to parent topicInstalling the Listener

This task describes how to install the JD Edwards EnterpriseOne Listener by launching an installation program (that is, a setup.exe program). You can distribute this program to users on the enterprise by using email to send them either the program or a shortcut, or by describing where the program is located on the server.

If you have a previous version of the JD Edwards EnterpriseOne Listener already installed, the installation program removes the previous version before copying the new version to the workstation.

Before you begin this task, close any applications that are currently open, and verify that the destination directory where you will be installing the JD Edwards EnterpriseOne Listener has sufficient disk space. You need approximately 2 MB of free disk space to install all of the Listener files and components.

To install the JD Edwards EnterpriseOne Listener on workstations:

  1. Launch the installation program by double-clicking setup.exe.

  2. On the first Client Listener Setup form, click Next.

  3. On the second Client Listener Setup form, enter the release that you want to install through push installation in the Release field.

  4. For the release that you selected, enter the full path name on the deployment server from which to initiate the installation in the Path name field.

  5. Specify the drive on which you want to install the specified release in the Installation drive field.

  6. Select the Uninstall option to uninstall existing versions of the software before installing a new full package.

  7. Select the Autostart option to automatically start the JD Edwards EnterpriseOne Listener service whenever the workstation starts up.

  8. Click Next to proceed to the next installation form.

  9. Select one of these options:

  10. In the Folder field, specify the destination drive and folder in which the Listener files will reside.

  11. Click Finish to complete the installation.

After you have successfully installed the JD Edwards EnterpriseOne Listener on the workstation, a small ear icon appears on the Windows taskbar, indicating that the JD Edwards EnterpriseOne Listener has been loaded. By right-clicking this icon, you can start or stop the JD Edwards EnterpriseOne Listener, or change the default parameter settings.

Click to jump to top of pageClick to jump to parent topicInstalling the Listener Using Silent Installation

 

To install the JD Edwards EnterpriseOne Listener using silent installation:

  1. Edit these settings in the listen_silent_setup.inf file that is included on the software CD:

    File Setting

    Description

    ServiceType

    Enter Local or Network, depending on where you want to run the JD Edwards EnterpriseOne Listener service.

    WorkstationDirPath

    Enter the location on the workstation where you want to install the JD Edwards EnterpriseOne Listener program and related files. For example, C:\Program Files\JDEdwards EnterpriseOne Client Listener.

    Release

    Enter the base release. Do not enter a cumulative update release.

    InstallPath

    Enter the location on the workstation where the software is installed. For example, D:\E900.

    LaunchPath

    Enter the deployment server name and the location from which the JD Edwards EnterpriseOne Client Workstation Installation program runs. For example, \\ server name \b9\OneWorld Client Install\setup.exe.

    AutoStart

    Enter 1 to automatically start the JD Edwards EnterpriseOne Listener service when the workstation starts up. Enter 0 if you do not want to enable Autostart.

    UninstallPackage

    Enter 1 if you want to automatically uninstall previous versions before installing a new full package. Enter 0 if you do not want to enable automatic uninstall.

  2. Create or modify a batch file to include the silent installation parameter /s for the ListenSetup.exe program.

    The batch file must reside in the same location as the ListenSetup.exe program.

    For example, your batch file might contain this line:

    start \\servername\E900\client\misc\ListenSetup.exe /s listen_silent_setup.inf

  3. Distribute the INF file and the batch file to workstation users.

    You can distribute these files or place them on a network server where workstation users can copy the files to their workstations.

  4. Instruct users to restart their workstations to run the batch file and load the JD Edwards EnterpriseOne Listener using silent installation.

After workstation users have successfully installed the JD Edwards EnterpriseOne Listener, the Listener icon appears on the Windows taskbar. Users can click this icon to start and stop the JD Edwards EnterpriseOne Listener or change Listener settings.

Important! You cannot change the name of the Listener silent installation file that is shipped with the software. The file name must be listen_silent_setup.inf.

Click to jump to top of pageClick to jump to parent topicStopping and Uninstalling the Listener

You can stop the JD Edwards EnterpriseOne Listener if you are certain that you do not want to use push installation to install packages. If you change your mind later, you can restart the JD Edwards EnterpriseOne Listener.

The easiest way to stop the JD Edwards EnterpriseOne Listener is to right-click the Listener icon on the Windows task bar and select Stop Listener.

Alternatively, you can stop the JD Edwards EnterpriseOne Listener using these steps:

  1. Open the Control Panel.

  2. Select Services.

  3. Select JD Edwards EnterpriseOne Client Listener.

  4. Click Stop.

To uninstall the JD Edwards EnterpriseOne Listener:

  1. Open the Control Panel.

  2. Select Add/Remove Programs.

  3. Select JD Edwards EnterpriseOne Client Listener.

  4. Click Remove All Components.

Click to jump to top of pageClick to jump to parent topicScheduling a Package for Push Installation

After you have installed the JD Edwards EnterpriseOne Listener on the workstations, you can schedule a package for deployment.

The process for scheduling a package for push installation is identical to the process for scheduling a package using the JD Edwards EnterpriseOne Deployment Director program (P9631). When you schedule the package using this program, select the Enable Push Installation option on the Package Deployment Attributes form. If you do not select this option, the package will be deployed through normal scheduled deployment.

When you use the JD Edwards EnterpriseOne Schedule Jobs program (P91300), you can set recurrence, which determines how frequently the job runs until it finishes successfully. If you do not set recurrence, the job runs only one time. In the case of push installation, recurrence determines the interval of time between installation attempts. After the package is successfully deployed, the job ceases to run.

As with scheduling any other package for deployment, all machine names (that is, package recipients) must be defined in the Machine Master (F9650) table. This table is populated when users sign in. Alternatively, you can enter machine names manually using the JD Edwards EnterpriseOne Deployment Locations Application program (P9654A).

Click to jump to top of pageClick to jump to parent topicScheduling the JD Edwards EnterpriseOne Push Installation Batch Application

After you have installed the JD Edwards EnterpriseOne Listener on all affected workstations and have scheduled the package through the JD Edwards EnterpriseOne Deployment Director program (P9631), you must use the JD Edwards EnterpriseOne Schedule Jobs program (P91300) to run the JD Edwards EnterpriseOne Push Package Installation batch program (R98825) on the server.

Before you begin to schedule the JD Edwards EnterpriseOne Push Installation batch application, complete these steps:

Access the Scheduling Information form:

  1. Enter a name that uniquely identifies a scheduled job in the Scheduled Job Name field.

  2. Enter the current status of the scheduled job in the Scheduled Job Status field.

    As long as the status is active, the JD Edwards EnterpriseOne Scheduler determines whether the job should be submitted to the server for processing. When the scheduled end date for the job has been reached, the status changes to Not Active. To stop the JD Edwards EnterpriseOne Scheduler from considering the job for submission, you can change the status to Not Active (or suspended) at any time prior to the end date. You can reactivate the job if you want the JD Edwards EnterpriseOne Scheduler to include the job again, but you can reactivate a job only if the end date is in the future.

  3. Enter the object name of the report that the Schedule submits to the server in the Scheduled Batch Application field.

  4. Enter the version of the report to run in the Scheduled Version field.

    This is the version of the report scheduled to run. A version identifies a specific set of data selections and sequencing settings that the batch job uses.

  5. In the Scheduled Start Date/Time field, enter the next date on which the JD Edwards EnterpriseOne Scheduler submits the scheduled job to the server for processing.

  6. To set the job recurrence (that is, to specify how frequently the job runs) select Recurrence from the Form menu.

    If you do not specify a recurrence by completing the fields on this form, the job runs only one time. For the JD Edwards EnterpriseOne Push Installation batch program, you should set recurrence to run every 30 minutes.

  7. On the Recurring Scheduling Information Revisions form, click OK.

  8. On the Scheduling Information form, to enter any overrides, resubmissions, or expiration options, select Advanced Options from the Form menu.

  9. Click the tab that corresponds to the information that you want to enter or revise:

  10. Revise the information, and click OK.

After scheduling the job, you can use the JD Edwards EnterpriseOne Object Configuration Manager (P986110) to verify that the server on which the JD Edwards EnterpriseOne Push Installation batch program is running points to the same F98825 and F9650 tables that the JD Edwards EnterpriseOne Deployment Director program uses.

See Also

Working with the Job Scheduler

Click to jump to top of pageClick to jump to parent topicRunning the Package Installation Results Report

Access the Push Package Installation Results form.

This report provides the same information that you get when you run the JD Edwards EnterpriseOne Push Package Installation batch program (R98825).

The report includes this information:

This table lists the status codes and descriptions that the JD Edwards EnterpriseOne Push Package Installation program (R98825) uses. Codes that are marked with an asterisk indicate conditions in which the JD Edwards EnterpriseOne Push Package Installation program continues to attempt the installation the next time that the JD Edwards EnterpriseOne Push Package Installation program runs.

Status Code

Description

200*

Scheduled

210*

In Progress

220

Successful Install

230

Install Failed

240*

Install Running

250*

JD Edwards EnterpriseOne Running

260*

Listener Not Started/Installed

270

General Error

280

Already Installed

290

Invalid Package

300

Install Attempted

310

Machine Down

Click to jump to parent topicInstalling Workstations from CD

This section provides an overview of how to install workstations from CD, lists a prerequisite, and discusses how to:

Click to jump to top of pageClick to jump to parent topicUnderstanding How to Install Workstations from CD

If your system includes a CD writer, you can build and deploy packages to the CD writer location. After copying the package to a CD, you can then use the CD as a portable deployment tier from which to perform workstation installations. That is, you can run from the CD the setup.exe program that launches the JD Edwards EnterpriseOne Workstation Installation program.

You can set up your enterprise so that you can deploy packages to the CD writer and install the software from a CD.

The first step in the process of configuring your system for deployment from CD is to define the CD writer location if it is not already defined. In this step, you essentially create a pseudo deployment server from which you will later copy package data onto the CD by using the software for your CD writer.

When you define the CD writer location in the Machine Identification application, you must also add the correct path codes to the Environments exit.

The process for defining this location is identical to the process for defining any other new deployment server.

Click to jump to top of pageClick to jump to parent topicPrerequisite

Assemble, define, and build the package that you want to write to the CD.

Click to jump to top of pageClick to jump to parent topicForms Used to Install Workstations from CD

Form Name

FormID

Navigation

Usage

Deployment Server Revisions

W9654AC

Package and Deployment Tools (GH9083), Machine Identification

Subordinate to the appropriate location, select Deployment server. Click Add to add a new machine.

 

Work with Package Deployment

W9631J

Package and Deployment Tools (GH9083), Package Deployment

Select the package to deploy and review your selections.

Click to jump to top of pageClick to jump to parent topicDefining the CD Writer Location

Access the Deployment Server Revisions form.

  1. Enter the name of the machine on the network in the Machine Name field.

  2. Enter the release number as defined in the Release Master in the Release field.

  3. Enter the primary user for the listed machine in the Primary User field.

  4. Enter the shared directory for the path code in the Server Share Path field.

  5. If you want to specify a location for data, a foundation, or help files, do so by choosing Data, Foundation, or Helps from the Form menu.

    If you do not specify a location for data, foundation, or helps, the system uses the default locations.

  6. Click OK.

  7. Click Close to quit the Work with Locations and Machines form.

  8. In Windows Explorer, locate the folder named Client Install.

  9. Copy this folder by dragging the folder to the CD writer location.

    The location is the server share path that you entered on the Deployment Server Revisions form.

Click to jump to top of pageClick to jump to parent topicDeploying a Package to the CD Writer Location

After you define the CD writer as a deployment server, you are ready to deploy a package to the CD writer location that you specified. This task involves these two procedures:

Access the Work with Package Deployment form.

  1. Click Add.

  2. Complete the forms in the JD Edwards EnterpriseOne Deployment Director in the same way as you would for any other package.

  3. From the Work with Package Deployment form, find and select the package that you just scheduled for deployment, and then select Deploy from the Row menu to deploy the package.

After you deploy the package to the CD writer location, the directory structure for that location will look similar to this example: 

Multitier\package_inf\Appl_B.inf 
Multitier\systemcomp\system.cab 
Multitier\datacomp\data.cab 
Multitier\helpscomp\helps.cab 
Multitier\Appl_pgf\Package\Appl_B
Multitier\package_inf\Appl_B.inf

In the previous example, Multitier is the name of the server share path. Appl_B is the package name.

Note. The server share path name is not included when you copy folders to the CD. In the previous example, the items that are copied to the CD are \package_inf\Appl_B.inf, \systemcomp\system.cab, and so on.

To modify the Install.inf and Package.inf files:

  1. In Windows Explorer, find the CD writer location and open the folder that contains the package that you deployed.

    This folder has the name that you entered in the Server Share Path field on the Deployment Server Revisions form when you defined the CD writer location. In the previous example, the server share path name is Multitier.

  2. Open the Client Installation folder, and then open the file Install.inf.

    That is, double-click the icon for the file to launch the Microsoft Notepad application.

  3. In the section [FileLocations], modify the line so that two periods and a backslash (\) precede the package_inf entry.

    The line should look like this example after you modify it:

    [FileLocations] 
PackageInfs=..\package_inf

  4. Similarly, open the Package_inf folder and open the package name.inf file.

    In the previous example, this file is named Appl_b.inf.

  5. In the section [SrcDirs], modify each of the lines so that two periods and a backslash (\) precede each entry.

    After modification, the [SrcDirs] section should look similar to this example:

    [SrcDirs] 
SAPPL_PGF=..\APPL_PGF\package\APPL_B 
SSYS=..\systemcomp 
SAPPL_PGFDATA=..\datacomp 
SHELP=..\helpscomp

Click to jump to top of pageClick to jump to parent topicCreating the Installation CD

After you deploy the package to the CD writer location and modify the Install.inf and Package.inf files, you are ready to copy the package contents to the CD. Use the software that came with your CD writer to accomplish this process, which typically involves copying the package contents to the CD. Refer to the documentation that came with your CD writer for more information about this process.

You copy the package to the CD by copying the subdirectories that are subordinate to the server share path directory. The server share path directory is not created on the CD. (In the previous example, the server share path directory is called Multitier, and it is the same name that you entered in the Server Share Path field on the Deployment Server Revisions form.

When you are finished copying the directories to the CD, the CD should contain these directories: