This chapter contains the following topics:
The first step in building and deploying a package is to assemble the package. This includes entering a package name and detailed description, selecting the type of package that you want to build, and assembling the objects, data, foundation, and features that you want to include in the package. The package name and description appear during workstation installation when the user selects a package to install.
The Package Assembly Director, which you access from Oracle's JD Edwards EnterpriseOne Package Assembly program (P9601), steps you through the process. During package assembly, the build status is always either In Definition or Definition Complete. After you assemble the package, you can then define its build process.
The Package Assembly Director guides you through the process of specifying or confirming the location where package components can be found, as well as indicating the objects to include in the package. The director always gives you the option to either continue to the next form or go back to the previous form. Also, you can always cancel the assembly process.
You can enter default information on each of the main forms of the Package Assembly Director, or you can access subforms from each of the main forms to configure the information. The steps are the same whether you are adding components for the first time or revising a previously assembled package.
You can also access any previously assembled packages and view information about these packages by clicking the plus (+) symbol of the package on the Work with Packages form. For any previously assembled packages, underneath the package name you can view the package properties (including package type and current status), as well as the selections for foundation, database, and language.
When you finish adding the selected components to a package, those components appear on the specific form for that component, the Package Component Revision form, and the Work with Packages form of the Package Assembly Director.
This table summarizes the function of each form in the Package Assembly Director:
|Package Assembly Directory form||Use this form to review introductory information about the Package Assembly Director.|
|Package Information form||Use this form to enter the package name, description, and corresponding path code.|
|Package Type Selection form||Use this form to indicate whether you are creating a full or update package.
When you create an update package, you must also indicate the parent package on which the update package is based. For example, if you were creating a package to update your original package called APPL_B, you would enter APPL_B as the parent package for your update package.
|Foundation Component form||Use this form to enter the location of the foundation. A foundation is the code that is required to run all applications. It is required for all full packages. If you do not specify a foundation path for full packages, the system uses the default foundation path. Update packages use the foundation for the parent package unless you specify another foundation.|
|Database Component form||Use this form to specify the location of the database to be included in the package. For full packages, if you do not specify a database location, the system uses the default database path. Update packages do not require a database.|
|Default Object Component form (for full packages only)||Use this form to verify the deployment data source. When you build a full package, the system retrieves the objects that are included in the package from the deployment data source that is associated with the path code that you specified for the package.|
|Object Component form (update packages only)||Use this form to specify the individual objects that you want to include in the package. You can add any of these objects:
|Features Component form||Use this form to include features in your package. A feature is a set of files or configuration options, such as registry settings, that must be copied to a workstation or server to support an application or another feature.|
|Language Component form||Use this form to include in your package language specifications for a language other than English.|
|Package Component Revisions form||Use this form to review the information that you entered on the previous forms. You can modify any or all of your selections on this form.|
Many of the forms in the Package Assembly Director have default values and, after verifying that you want to use the default value, you can advance to the next form without entering anything.
Forms determine the default values based on these criteria:
The default foundation location is the server share path under the path code for the package.
The default database location is the server share path under the path code for the package.
The default location for full packages is the deployment data source.
The default language is English.
On forms that have a default value, even if you change or clear the field you can always restore the original default value by clicking the Default button. The Form menu of the Package Component Revisions form also has a Set Default option that restores default values.
If you are building a full package and do not need to specify the objects in that package, the fastest way to define the package is to accept the default locations for the foundation, database, and language. This method applies only to full packages. For an update package, if you accept the defaults but do not include any objects, the system creates an empty package.
As you view the forms in the Package Assembly Director, you can accept the default selections by clicking Next. If necessary, you can always make changes at the final Package Component Revisions form.
This section provides an overview of the process to verify a path code and discusses how to verify a path code for package assembly.
The verification process tests the environment, machines, and tables before a package is submitted. By verifying your environment, you eliminate the chance that your package build will fail due to configuration issues. This verification can save many hours in building a package.
During the verification process, the program verifies these items:
Disk space is adequate.
Central objects and package build tables are accessible.
User has permissions to create directories on the deployment server and enterprise server.
Required service pack is installed.
Required Microsoft Data Access Components (MDAC) are installed.
Machine tables are set up.
Required compiler version is installed.
Enterprise Server port is accessible.
Debug levels of the jde.ini files are adequate for the client and enterprise server.
|Work with Batch Versions - Available Versions||W98305A||System Administration Tools, Package and Deployment Tools, Package Assembly
Select Build Verification from the Form menu.
|Verify the path code for package assembly.|
Access the Work with Batch Versions - Available Versions form.
Select a version and click Select.
On Version Prompting, click Submit.
Complete the Processing Options fields, and click OK.
On Printer Selection, select the desired printer, and click OK.
Assembling a package in Director mode can involve configuring additional components, such as a foundation location, database location, or features. A feature is a set of files or configuration options, such as registry settings, that is copied to a workstation or server to support an application or other function. Like objects, features are built into a package and deployed to workstations and servers.
Note:Assembling a package in Express mode, rather than Director mode, is recommended in order to simplify and speed up the assembly process. Director mode can be used if you are unfamiliar with the process and would like to walk through each form consecutively. However, Express mode is the default mode for the Package Assembly application. This default behavior can be changed with a processing option.
This section discusses how to:
Use Director mode to assemble a new package.
Add a new foundation location.
Add a database location.
Add features to a package.
Review the package assembly selections.
On the Work with Packages form, click Add, and then on the Package Assembly Director form, click Next.
On the Package Information form, complete the Package Name, Description, and Path Code fields.
Note:The name of the package cannot be longer than eight characters.
Note:You can build a single foundation package to deploy to all path codes by entering *ALL in the Path Code field. This option enables you to create an update package for service packs that can be installed to any path code. If you enter *ALL in the Path Code field, the application does not enable you to select, build, or deploy any objects (such as specs, business functions, and so on) in the package; you can only deploy a foundation. The package is built to a directory called all_packages, which is located under the release path (for example, e900/all_packages). This package can be deployed to any path code.
Before you can use this option, you must define the *ALL path code in the Path Code Master application.
Select the Director option, and click Next.
On Package Type Selection, complete these fields, and click Next:
|Full||Select to create a full package that contains all specifications and foundation code.|
|Update||Select to create an update package with specific items that can be deployed to specific users. If you are building a foundation package to the *ALL path code, the application automatically selects an update package.|
|Parent Package||Indicate the parent package that the update package is based on or related to. This information is used by the system to determine how to build business functions.|
On the Foundation Component form, perform one of these actions:
For full packages, accept the default location by clicking Next, or click Browse to specify another foundation location.
For an update, click Clear unless the package includes a foundation, and then click Next.
On the Database Component form, perform one of these actions:
For full packages, accept the default location, or click Browse to specify another database location.
For an update, click Clear unless the package includes a foundation.
Complete one of these actions:
If you are assembling a full package, click Next.
For a full package, the system builds your package from the deployment data source that is associated with the default object path. Verify that the correct location appears on the form, and proceed to the next step.
If you are assembling an update package, click Next on the Database Component form, and then proceed to the next step.
On the Object Component form, to add an object, click Browse.
The Object Component form only appears when you are assembling an update package. If you are assembling a full package, the Default Object Component form appears and you cannot add objects.
On the Object Component Selection form, locate and select the objects that you want to include in your update package, and then click Close to return to the Object Component form.
When you revise a previously assembled package, objects that you added earlier also appear on the Object Component Selection form.
On the Object Component form or Default Object Component form, click Next.
The Features Component form appears, on which you can specify the features that you want to include in your package. When you revise a previously assembled package, the system displays the features that you added earlier.
To add a feature, click Browse.
On the Feature Component Selection form, click Find to display a list of features, select one or more features, and then click Select to add the features that you want to include in your package.
To select multiple features, press the Ctrl or Shift key while clicking features, and then click Select.
Click Close to return to the Features Component form.
On the Feature Component form, click Next.
On the Language Component form, click Next if English is the only language that you want to configure.
To add a language to the language specifications for your package, double-click its row header in the detail area, and click Next.
If you add a language to your package, only that language will be included. For example, if you add French, English will not be included even though it is the default language. To include two languages (such as French and English), you must select the detail records for both languages.
Continue with the task Reviewing the Package Assembly Selections.
Enter a foundation ID in the Foundation Name field.
This is the code that is required to run all applications. A foundation ID is required for all full packages. For full packages, if you do not select a foundation, the default foundation is used. The default foundation is determined through the release that is associated with the path code for the package. This is normally the system directory at the same directory level as your path code. The foundation must be compressed when built.
Enter a service pack number in the Service Pack Number field, if appropriate.
A service pack is an update to the foundation code that is delivered between major releases and cumulative releases of the software.
Enter the release number with which this foundation is associated in the Release field.
Enter the host machine type in the Platform Type field.
Enter the compiler configuration to use for the software build in the Build Type field.
Enter the current status of the build process for foundation in the Foundation Build Status field.
Enter the date that the software build finished in the Date Built field.
Enter the time at which the software build finished in the Time of Build field.
Enter the name of the deployment server where your custom foundation resides in the Foundation Machine Key field.
Enter the exact path from which this item should be copied in the Foundation Path field.
All files in the last directory that is specified will be included in the package. Source Machine Key and Source are used together to define the item's location.
Click Add to add a new database component.
Enter the name of the database component in the Database Name field.
Enter the name of the machine on the network (server or workstation) in the Source Machine Key field.
Enter the shared directory for this path code in the Server Share Path field.
Note:For full packages, if you do not specify a database location, the system uses the default database path (\pathcode\Packages\Data). Update packages do not require a database.
Find and select the existing features that you want to include in the package, and then click Select.
To select multiple features, press the Ctrl or Shift key.
If the feature that you want to include has not been defined, you can create the feature definition by clicking Add.
Oracle's JD Edwards EnterpriseOne Feature Based Deployment Director launches. You can use this director to create the new feature.
Repeat steps 1 and 2 until you have finished adding features to your package.
When you are finished, click Close to return to the form from which you accessed the Feature Component Selection form.
Review the current foundation, database locations, objects, features, languages, and business services that exist for your package.
To change any of the package components, click the button for the component that you want to change.
The form for that package component appears.
When you are finished assembling the package, click End to quit the Package Assembly Director.
Continue with the task Activating an Assembled Package.
This section provides an overview of Express mode and lists the forms used to assemble a package using Express mode.
Express mode enables you to accept default values for the package assembly and then selectively choose which forms to view and modify. This may be preferable if you are familiar with the JD Edwards EnterpriseOne Package Assembly application and do not want to view and click Next through all of the Package Assembly forms.
When you select Express mode, you access the Package Component Revisions form, from which you can access the appropriate forms for the components that you want to update.
The JD Edwards EnterpriseOne Package Assembly application (P9601) is in Express mode by default. This can be changed to Director mode through a processing option.
|Package Information||W9601F||Package and Deployment Tools (GH9083), Package Assembly
Click Add, and then click Next.
|Assemble a new package.|
|Package Component Revisions||W9601B||Select Express, and click Next on the Package Information form.||Review and revise the components in your package.|
|Foundation Component Selection||W9601H||Click the Foundation button on the Package Component Revisions form.||Add an existing foundation location to your package.
Locate the existing foundation location that you want to use in the package, and click Select.
|Foundation Item Revisions||W9883D||Click Add on the Foundation Component Selection form.||Add a new foundation location to the package.|
|Database Component Selection||W9601N||Click the Database button on the Package Component Revisions form.||Add an existing database location to the package.
Locate the existing database location that you want to use in the package and click Select.
|Database Item Revisions||W9883K||Click Add on the Database Component Selection form.||Add a new database location to the package.|
|Object Component Selection||W9601D||Click the Objects button on the Package Component Revisions form. Click Browse.||Add an object to the package.|
|Feature Component Selection||W9601AB||Click the Features button on the Package Component Revisions form. Click Browse.||Add a feature to the package.|
After you have assembled a package, you can use the Package Component Revision form to revise any of the components in the package. You do not need to complete all of the forms in the Package Assembly Director to revise a package.
Verify that the status of the package is In Definition. If you try to revise a package that has a status of Assembly-Definition Complete, the system displays an error message. To change the status of a package, select Active/Inactive from the Row menu on the Work with Packages form. You cannot revise or delete a package that has already been deployed.
|Package Component Revisions||W9601B||Package and Deployment Tools (GH9083), Package Assembly
Select the package that you want to revise, and then select Package Revisions from the Row menu.
|Revise an existing package.|
Access the Package Component Revisions form.
Make any necessary changes to the package components.
When you are finished revising the package definition, click OK to return to the Work with Packages form.
If any build information exists for the package, the system warns you that the changes will delete the existing build information.
Click one of these buttons:
Accept the revisions and delete the existing build information. If you accept the revisions, you should update the build information so that it reflects the changes that you made.
Delete the revisions and save the existing build information.
After you have assembled a package, the package status remains at Assembly. While you define the package, it is inactive. You must activate the package to change the package status to Assembly-Definition Complete. An assembled package cannot be built until the status has been changed to Assembly-Definition Complete. The Assembly-Definition Complete status indicates that you are finished assembling the package and are ready to begin the build definition process.
You can change the package status at any time until you start the build definition process. That is, even after you have changed a package status to Assembly-Definition Complete, you can change the status back to In Definition if you need to revise the assembled package. When you are ready to define the build for the package, follow the steps described in Defining Package Builds.
|Work with Packages||W9601L||Package and Deployment Tools (GH9083), Package Assembly
Select the package that you want to activate, and select Active/Inactive from the Row menu.
|Activate the package.
You can use this same process to change the status of a complete package back to In Definition.