EnterpriseOne B73.3.1 Package Management PeopleBook · 2006. 4. 25. · B73.3.1 (6/99) 1–1 Overview of Package Management The Configuration Planning and Setup suite is designed

EnterpriseOne B73.3.1Package Management PeopleBook

June 1999

J.D. Edwards World Source Company

One Technology Way

Denver, CO 80237

Portions of this document were reproduced from material prepared by J.D. Edwards.

Copyright J.D. Edwards World Source Company, 1997 - 1999

All Rights Reserved

SKU B7331CEAPK

J.D. Edwards is a registered trademark of J.D. Edwards & Company. The names of all other products and services of J.D. Edwards used herein are trademarks or registered trademarks of J.D. Edwards World Source Company.

All other product names used are trademarks or registered trademarks of their respective owners.

The information in this guide is confidential and a proprietary trade secret of J.D. Edwards World Source Company. It may not be copied, distributed, or disclosed without prior written permission. This guide is subject to change without notice and does not represent a commitment on the part of J.D. Edwards & Company and/or its subsidiaries. The software described in this guide is furnished under a license agreement and may be used or copied only in accordance with the terms of the agreement. J.D. Edwards World Source Company uses automatic software disabling routines to monitor the license agreement. For more details about these routines, please refer to the technical product documentation.

B73.3.1 (6/99)

Table of Contents

Overview of Package Management

Overview of Package Management 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding OneWorld Roles 1–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CNC Consultant and CNC Administrator 1–3. . . . . . . . . . . . . . . . . . . . . . Custom Solution Consultant and Application Developers 1–3. . . . . . . . . Application Consultants and Application Project Leaders 1–3. . . . . . . . . Hardware, Network, and Third-Party Software Consultants and Administrators 1–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Understanding the Package Management Guide 1–4. . . . . . . . . . . . . . . . . . . . Understanding Packages 1–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the Deployment Methods 1–5. . . . . . . . . . . . . . . . . . . . . . . . .

Understanding Workstation Installation 1–5. . . . . . . . . . . . . . . . . . . . . . . Understanding Package Deployment 1–6. . . . . . . . . . . . . . . . . . . . . . . . . Understanding Server Packages 1–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding Multitier Deployment 1–7. . . . . . . . . . . . . . . . . . . . . . . . .

Package Management Planning and Setup

Package Management Planning and Setup 2–1. . . . . . . . . . . . . . . . . . . . . Package Management Planning and Setup 2–1. . . . . . . . . . . . . . . . . . . . . . . .

Working with the Recommended Path Codes 2–3. . . . . . . . . . . . . . . . . . . . . . . . . Working with the Recommended Path Codes 2–3. . . . . . . . . . . . . . . . . . . . . . Suggested Package Names and Schedule 2–4. . . . . . . . . . . . . . . . . . . . . . . . .

Ensuring the Integrity of the Production Environment 2–5. . . . . . . . . . . . . . . . . . Ensuring the Integrity of the Production Environment 2–5. . . . . . . . . . . . . . . Disabling Just-In-Time Installation 2–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Understanding the Development Processes 2–7. . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the Development Processes 2–7. . . . . . . . . . . . . . . . . . . . . . . . Working with the Normal Development Process 2–7. . . . . . . . . . . . . . . . . . . Developing Short-Term Fixes 2–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Comparing the Deployment Methods 2–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Comparing the Deployment Methods 2–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding Cumulative and Noncumulative Update Packages 2–11. . . . . . Recommendations for Sites Using Partial Packages and JITI 2–11. . . . . . . . . . Recommendations for Sites Using Full Packages without JITI 2–12. . . . . . . . Recommendations for Developers 2–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multitiered Deployment and Just-In-Time Installation 2–12. . . . . . . . . . . . . . . Comparing the Deployment Methods 2–12. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deploying Various Types of Modifications 2–15. . . . . . . . . . . . . . . . . . . . . . . . . . . Deploying Various Types of Modifications 2–15. . . . . . . . . . . . . . . . . . . . . . . .

Package Management

B73.3.1 (6/99)

Deploying Data 2–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploying a New Replicated Local Database 2–21. . . . . . . . . . . . . . . . . . . . . . Deploying a Special Database for Store-and-Forward Users 2–23. . . . . . . . . .

OneWorld Modification Rules

OneWorld Modification Rules 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What an Upgrade Preserves and Replaces 3–3. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Understanding the General Rules for Modification 3–4. . . . . . . . . . . . . . . . . Understanding Interactive Application Rules 3–4. . . . . . . . . . . . . . . . . . . . . . Understanding Report Rules 3–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding Application Text Changes 3–6. . . . . . . . . . . . . . . . . . . . . . . . . Understanding Table Specification Rules 3–7. . . . . . . . . . . . . . . . . . . . . . . . . Understanding Control Table Rules 3–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding Business Views Rules 3–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding Rules for Event Rules 3–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding Data Structure Rules 3–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding Business Functions Rules 3–10. . . . . . . . . . . . . . . . . . . . . . . . . Understanding Version Rules 3–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Object Management

Object Management 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding Object Movement 4–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table (Object Type TBLE) 4–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Business View (Object Type BSVW) 4–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . C Business Function (Object Type BSFN, Source Language C) 4–4. . . . . . . Business Function Data Structure (Object Type DSTR) 4–4. . . . . . . . . . . . . . Embedded Event Rule 4–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Business Function Event Rule (Type BSFN, Source Language NER) 4–5. . . Media Object Data Structure (Object Type GT) 4–6. . . . . . . . . . . . . . . . . . . . Interactive Application (Object Type APPL) 4–6. . . . . . . . . . . . . . . . . . . . . . Batch Application (Object Type UBE) 4–6. . . . . . . . . . . . . . . . . . . . . . . . . . . Data Dictionary Items 4–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Understanding Files Created by the Build Process 4–9. . . . . . . . . . . . . . . . . . . . . Workstation Build 4–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Where Business Functions Are Stored 4–9. . . . . . . . . . . . . . . . . . . . . . . . Files Created by a Business Function Build 4–9. . . . . . . . . . . . . . . . . . . . Files Created by a Business Function Event Rule Build 4–10. . . . . . . . . . Files Created by a Table Event Rule Build 4–10. . . . . . . . . . . . . . . . . . . . .

UNIX Server Build 4–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Files Created by a Business Function Build 4–10. . . . . . . . . . . . . . . . . . . . Where Business Functions Are Stored 4–11. . . . . . . . . . . . . . . . . . . . . . . . Specification Files 4–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Windows NT Server Build 4–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Files Created by a Business Function Build 4–12. . . . . . . . . . . . . . . . . . . . Where Business Functions Are Stored 4–12. . . . . . . . . . . . . . . . . . . . . . . . Specification Files 4–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

B73.3.1 (6/99)

AS/400 Server Build 4–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Files Created by a Business Function Build 4–13. . . . . . . . . . . . . . . . . . . . Where Business Function Source Members Are Stored 4–14. . . . . . . . . . . Specification Files 4–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Correlating Replicated and Central Objects 4–15. . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Backups and Restoring Objects 4–17. . . . . . . . . . . . . . . . . . . . . . . . . . Transferring Objects 4–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Verifying the Transfer 4–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Objects with the SAR System 4–25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying Records Between Data Sources 4–27. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Package Build

Package Build 5–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding Packages and Deployment 5–3. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Understanding Full and Partial Workstation Configurations 5–4. . . . . . . . . . Understanding Just-in-Time Installation 5–6. . . . . . . . . . . . . . . . . . . . . . . . . . Understanding Package Types 5–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Full Packages 5–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Partial Packages 5–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Update Packages 5–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of Creating and Deploying a Package 5–9. . . . . . . . . . . . . . . . . . . How OneWorld Builds a Full Package 5–10. . . . . . . . . . . . . . . . . . . . . . . . How OneWorld Builds a Partial Package 5–11. . . . . . . . . . . . . . . . . . . . . . How OneWorld Builds an Update Package 5–11. . . . . . . . . . . . . . . . . . . .

Considerations for Users of Sun Microsystems, Inc. Platforms 5–12. . . . . . . . Assembling Packages 5–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Understanding the Package Assembly Director 5–13. . . . . . . . . . . . . . . . . . . . Accepting Default Values 5–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Assembling a Package 5–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Objects to a Package 5–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Entering a Foundation Location 5–29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Entering a Help File Location 5–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Entering a Database Location 5–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Activating a Package 5–37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Revising an Existing Package 5–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying a Package 5–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Package 5–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining Package Builds 5–43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the Build Process 5–44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the Package Build Definition Director 5–45. . . . . . . . . . . . . . .

Building Business Functions During Package Build 5–46. . . . . . . . . . . . . Defining a Package Build 5–47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Package Build Processing Options 5–58. . . . . . . . . . . . . . . . . . . . . . . . . . . Revising a Package’s Build Options 5–59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copying a Built Package 5–60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Package Build History and Resubmitting Builds 5–62. . . . . . . . . . . .

Understanding Server Packages 5–63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the Server Package Build Process 5–64. . . . . . . . . . . . . . . . . . .

Package Management

B73.3.1 (6/99)

JDE.INI Settings for Server Package Builds 5–66. . . . . . . . . . . . . . . . . . . . . . . Working with Package Build History and Logs 5–69. . . . . . . . . . . . . . . . . . . . . . . .

Viewing the Package Build History 5–70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Logs 5–71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Where to Find the Error Logs 5–73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Package Statistics Log 5–73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Package Build Log 5–74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Business Functions Errors Log 5–76. . . . . . . . . . . . . . . . . . . . . . . . . . The Missing Business Function Source Errors Log 5–76. . . . . . . . . . . . . . Server Logs 5–77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Resubmitting a Package Build 5–77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Build Status 5–78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Understanding Package INF Files 5–81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sample INF File 5–81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

[Attributes] 5–81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [SrcDirs] 5–83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [DestDirs] 5–84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [Filesets] 5–84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [Components] 5–85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [Typical] 5–85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [Compact] 5–86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [ODBC Data Sources] 5–86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [Access32] 5–86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deployment

Deployment 6–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding Package Deployment 6–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deployment to Workstations without OneWorld 6–3. . . . . . . . . . . . . . . . . . . Deployment to Workstations with OneWorld Already Loaded 6–4. . . . . . . . . Deployment to Servers 6–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment to Tiered Deployment Locations 6–4. . . . . . . . . . . . . . . . . . . . . Deploying to Workstations from CD 6–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining Machines, Locations, and Deployment Groups 6–7. . . . . . . . . . . . . . . . Defining Machines 6–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Locations 6–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Package Deployment Groups 6–16. . . . . . . . . . . . . . . . . . . . . . . . . . .

Revising a Deployment Group 6–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with the Package Deployment Director 6–19. . . . . . . . . . . . . . . . . . . . . .

Understanding the Package Deployment Director 6–19. . . . . . . . . . . . . . . . . . Using the Package Deployment Director 6–21. . . . . . . . . . . . . . . . . . . . . . . . .

Revising a Scheduled Package’s Deployment Options 6–31. . . . . . . . . . . . Activating the Package 6–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a Scheduled Package 6–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deploying Server Packages 6–35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling a Server Package for Deployment 6–35. . . . . . . . . . . . . . . . . . . . .

Using Push Installation 6–39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How Push Installation Works 6–39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the Enterprise Server for Push Installation 6–40. . . . . . . . . . . . . . . .

Table of Contents

B73.3.1 (6/99)

Preparing Workstations for Push Installation 6–41. . . . . . . . . . . . . . . . . . . . . . Installing the Listener 6–42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Listener via Silent Installation 6–45. . . . . . . . . . . . . . . . . . . Stopping the Listener 6–47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstalling the Listener 6–47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Default Parameter Settings 6–48. . . . . . . . . . . . . . . . . . . . . . . . .

Scheduling a Package for Push Installation 6–49. . . . . . . . . . . . . . . . . . . . . . . . Scheduling the Push Installation Batch Application 6–50. . . . . . . . . . . . . . . . . Running the Push Package Installation Results Report 6–54. . . . . . . . . . . . . . .

Push Installation Status Codes 6–55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Final Considerations 6–56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing OneWorld Workstations from CD 6–57. . . . . . . . . . . . . . . . . . . . . . . . . . Defining the CD Writer Location 6–57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploying a Package to the CD Writer Location 6–59. . . . . . . . . . . . . . . . . . .

Before You Begin 6–60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating the OneWorld Installation CD 6–62. . . . . . . . . . . . . . . . . . . . . . . . . .

Multitier Deployment

Multitier Deployment 7–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding Multitier Deployment 7–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Multitier Deployment Features 7–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multitier Deployment Terminology 7–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Example: Two-Tier Deployment Strategy 7–5. . . . . . . . . . . . . . . . . . . . . Multitier Implementation 7–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining Deployment Locations 7–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a New Deployment Server Definition 7–7. . . . . . . . . . . . . . . . . . . . . Revising an Existing Deployment Server Definition 7–10. . . . . . . . . . . . . . . .

Scheduling Packages for Deployment Locations 7–13. . . . . . . . . . . . . . . . . . . . . . . Distributing Software to Deployment Locations 7–15. . . . . . . . . . . . . . . . . . . . . . .

Distributing Software Through Package Deployment 7–16. . . . . . . . . . . . . . . Distributing Software Through the Multitier Deployment Batch Process 7–17Copying Workstation Installation Programs to Deployment Locations 7–19. .

Installing Workstation Packages From Deployment Locations 7–21. . . . . . . . . . . . Understanding a Multitier Deployment Case Study 7–23. . . . . . . . . . . . . . . . . . . .

Glossary

Index

Package Management

B73.3.1 (6/99)

B73.3.1 (6/99) –7


Package Management

–8 B73.3.1 (6/99)

B73.3.1 (6/99) 1–1


The Configuration Planning and Setup suite is designed for use by ConfigurableNetworking Computing (CNC) specialists, OneWorld system administrators, andnetwork/server administrators. The assumption throughout these guides is that theinitial OneWorld installation is complete and the standard data sources, path codes, andenvironments are defined. These guides tells you how to make changes or additions tothe configuration setup after the initial installation.

The Configuration Planning and Setup suite consists of the following guides:

� ��

!�� " �� !��

� �� !��

� �� "�� " ��

��

� ��

� �� !��

� ��

� �� "��

� �� !�� " ��

�"�� !��

� ��

� ��

� �� !��

� ��

� �� "

� �� !�� !�� " ��

� �� " � ��

� ��

� �� !��

� �� !��

� ��

� ��

Package Management

1–2 B73.3.1 (6/99)

� �� $ �&�� $ (#�%%� "#��#��) �!# ��!#��

$)$%�� $%#�%!#$ � � !%��#$ (�! �� &$%!� �!��%�! $ %! %��

��!#�� '�#! �� %$� �� ! %�� $ %�� !��!(� �%!"��$�

� �� % "�� $�%&"

� ��!#�� !��%�! #&��$

� ��% �� %

� �� &��

� ��"�!)�� %

� �&�%�%��# ��"�!)�� %

� �� $ �&�� $ (#�%%� "#��#��) �!# �%(!#� �� $%#�%!#$ � � �! %�� $ %�� !��!(� � %!"��$�

� � ��#$%� �� "$�!% ��&�%�� % � $%��#�

� ��#'�# �� $%#�%�!

� �#!&��$�!!%� � %�� (!#�$%�%�!

� �#!&��$�!!%� � %�� $�#'�#

Although every attempt has been made to organize the information in theConfiguration Planning and Setup guides according to related tasks, you may find thatthe information needed to perform the various duties for a position is described in morethan one guide. For example, the person who is responsible for setting up path codes,environments, and data sources (described in the Configurable Network ComputingImplementation Guide) might also be responsible for building and deploying packages(described in the Package Management Guide).

The Configuration Planning and Setup suite is the central location for all CNC-relatedtasks except:

� �%�� $%��%�! !� ��!#�� %��

� ��!#�� &"�#�� &�&��%�'� &"��%�$� �� %��

� ��%(!#� � �#�$%#&�%&#� � � %��#�*"�#%) $!�%(�#� $�%&" � � �� %� � ��

��$ � �!#��%�! �$ "#!'�� ) %�� ""�� $!�%(�#� !# ��#�(�#�

'� �!#� �� (�#�$ �!�$ !% "#!'�� !�&�� %�%�! �

You do not need a complete understanding of the installation process to performconfiguration planning and setup tasks. However, in order to use the ConfigurationPlanning and Setup guides it is important that you understand what the installationaccomplishes.

B73.3.1 (6/99) 1–3

Understanding OneWorld Roles

The OneWorld implementation methodology defines specific roles:

� ��

� ��

� ��

� ��

��

Each of these roles is performed by a consultant and a customer. After implementation,the role of the consultant is diminished. Therefore it is critical that the customer ensuresthat adequate training occurs for each of the roles to be assumed by their personnel.

CNC Consultant and CNC Administrator

The CNC consultant and CNC administrator are involved with installing OneWorld andsetting up environments, users, security, distributed processing, and data replication.They are also responsible for setting up version control and testing various CNCconfigurations. The CNC consultant and CNC administrator control the deployment ofOneWorld software throughout the company.

Custom Solution Consultant and Application Developers

OneWorld custom solution consultants resolve business issues by developingapplications. Their primary responsibilities include designing the modifications withupgrades in mind, and developing, testing, and introducing the customized software.While the CNC administrator performs the version control functions that build anddeploy software, the customer solution consultant must help develop the internalprocedures for application development cycle for your business.

Application Consultants and Application Project Leaders

After OneWorld is installed, configured, and rolled out, the application consultantscontinue in their role as product experts. Although application consultants do notimplement the CNC configurations, they must understand how OneWorld handlesdistributed processing, data replication, environments, and so on, because theseapplication issues influence the CNC decisions. In addition, application consultantsmust become very good at troubleshooting potential problems.

Hardware, Network, and Third-Party Software Consultants andAdministrators

Implementing OneWorld includes many tasks that are outside the scope of J.D.Edwards services. Third-party consultants provide these services as well as

Package Management

1–4 B73.3.1 (6/99)

supplementing our staff as CNC consultants, network architects, custom modificationconsultants, and so on.

Understanding the Package Management Guide

This guide describes how to set up and maintain processes to develop and deploycustom modifications created with the OneWorld Tools.

Included in this guide are the following topics:

� ��

� ��

� ��

� ��

� ��

� ��

The first several sections of this guide describe how to set up an environment in whichyou can deploy custom modifications made with the OneWorld toolset. This includessuch concepts as OneWorld modification rules, transferring objects, checking outdevelopment objects, and working with the data dictionary.

If you have already set up such an environment or are comfortable with these concepts,you can skip to the sections that describe how to create and schedule packages, andhow to deploy to workstations and servers.

Understanding Packages

The purpose of a package is to group OneWorld software modifications so that they canbe deployed to workstations. A package describes where to find the components youwant to deploy to workstations. A package can contain everything needed to runOneWorld (as in an initial installation for a new workstation), or only updates orchanges to existing applications.

B73.3.1 (6/99) 1–5

There are three package types:

� ��

� ��

� ��

The full package includes all OneWorld applications and is the same as the formerStandard package. Users who need the full suite of OneWorld applications shouldreceive this type of package.

The partial package is a minimum configuration of OneWorld. Its chief advantage isthat it saves a tremendous amount of disk space. A user who installs this type ofpackage can subsequently load at runtime only the applications needed, rather thanreceiving many unused OneWorld applications with the initial installation.

The main purpose of an update package is to enable you to update, add to, or refreshyour existing full or partial package with changed objects. You can only deploy anupdate package on top of or to a workstation that already has OneWorld loaded. Theobjects in the update package replace those objects on the workstation. All otherobjects on the workstation are left untouched.

The advantage of this type of package is that you can deploy software fixes orenhancements quickly.

Understanding the Deployment Methods

OneWorld offers several deployment methods, each with its own specific purpose andadvantages. The method you select depends mainly on the type of package you want todeploy.

� ��

� ��

� ��

Understanding Workstation Installation

The Workstation Installation program is used to deploy full and partial packages.Update packages cannot be deployed using Workstation Installation.

Workstation Installation retrieves the items specified in the package. A full or partialpackage is like a bill of materials or a kit with instructions; to pull all of the necessarycomponents the Workstation Installation program deploys to the local computer.Workstation Installations are always initiated by the user.

Package Management

1–6 B73.3.1 (6/99)

DeploymentServer

Windows NT Workstation

Windows 95 Workstation

Understanding Package Deployment

Package Deployment enables the OneWorld administrator to specify the date and timewhen a package is made available to the affected users or groups. The administrator canspecify whether the package is mandatory or optional. If a package is mandatory, userswho receive the package will be unable to access OneWorld until they load thepackage.

Users who receive a scheduled package are given the opportunity to load the packageimmediately after they sign on to OneWorld on the specified date. If they opt to loadthe package, the installation routine launches, and the package loads. The user can alsoopt to load the package later, or decline installation altogether (unless the package ismandatory).

Alternatively, the push installation feature enables the administrator to schedule apackage that will be automatically “pushed” from the deployment server to theworkstations at the scheduled time, without requiring any interaction with the user.

Update packages always use Package Deployment. The full and partial package typesare normally deployed via Workstation Installation, although you can use packagedeployment for a full or partial package in cases where OneWorld has already beenloaded on a machine and you want to redeploy.

Understanding Server Packages

All OneWorld application development takes place on a workstation with objects storedin a central location. OneWorld allows you to partition business applications to anenterprise server. Developers and system administrators can push objects, called aserver package, from the central objects data source to a replicated server path code.

A server package is a group of OneWorld objects you have grouped together with acommon SAR number or any version control tracking number. Objects consist ofspecification records, source files, and header files. Compiled objects are created on theenterprise servers. When you define a package, you can install it to multiple servers andmultiple path codes.

Although server packages are not the same as the workstation packages , they are builtand deployed using the same applications: Package Assembly, Package Build, and

B73.3.1 (6/99) 1–7

Package Deployment. When you create an update package for workstations, you shouldcreate a corresponding server package to ensure that you are deploying the sameobjects to your enterprise server that you deploy to workstations.

Understanding Multitier Deployment

Multitier deployment enables OneWorld workstations to install software from morethan one deployment location and more than one deployment machine. J.D. Edwardsrecommends that you consider multitier deployment if your site has more than 50workstations performing OneWorld software installations per day, or if you aredeploying OneWorld software across a WAN connection.

Package Management

1–8 B73.3.1 (6/99)

Package Management Planning andSetup

Package Management

1–10 B73.3.1 (6/99)

B73.3.1 (6/99) 2–1



This section contains recommendations, suggestions, and considerations before youdeploy software modifications. You should familiarize yourself with this entire guidebefore considering your own software deployment strategy.

Managing modifications can be more difficult than the actual programming changes. Itis important to have a solid version control plan for tracking changed objects. You canavoid many software problems by tracking changed objects.

You should build and deploy packages only as often as necessary. Doing so excessivelywould be a huge strain on your version control group, and would become a logisticalnightmare as far as planning and tracking your development. If you perform manydevelopment changes, when you first start you should build and deploy packages on aset schedule. It is very important to keep a schedule, so that everyone involved knowswhen objects are due, and when you build and deploy the package.

To give you an idea of how version control might work, at J.D. Edwards we haveseveral hundred developers and an extremely complex Configurable NetworkComputing (CNC) configuration. For that number of developers, our Product VersionControl group consists of the following:

� ��

� ��

��

� � � ��

� ��

��

��! ��

� ��

��

For information about planning and setup, see the following:

� ��

� �� ! ��

� ��

Package Management

2–2 B73.3.1 (6/99)

� ��

� ��

� ��

B73.3.1 (6/99) 2–3

Working with the Recommended Path Codes

Working with the Recommended Path Codes

If you are not planning any development projects, you need only three path codes:CRPB733, PRODB733, and PRISTB733. You should create a development path codeif you plan to do extensive software modification.

The fewer path codes you use, the better. With each additional path code comes versioncontrol maintenance that is not worth the effort unless there is a true reason for theadditional path code. Even when making extensive software modifications, you shouldhave only four path codes (sets of central objects):

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

DEVB733ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Use this path code for “normal” development. Upon successfultesting, transfer the objects to your CRPB733 path code usingObject Transfer, and distribute to your users via the packagebuild deployment process.

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

CRPB733ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

This path code contains a practice set of objects that are testedduring conference room pilot before transferring objects toproduction. It is for deploying quick fixes or making minormodifications that you will quickly transfer to production. Itcan also be used as a place to test modifications that were donein the development path code before taking the risk oftransferring them to the production path code.

PRODB733 This is your production path code. Just-in-time installs comedirectly from this location, and production server objects arealso deployed from here. After testing software changes inCRPB733, transfer them to PRODB733 and then deploy thechanges to your enterprise servers and workstations.

PRISTB733 This is the set of pristine objects shipped from J.D. Edwards.You should not make changes to this path code other thanpaper fixes from J.D. Edwards. This path code is used tocompare J.D. Edwards standard software to any customsolutions you have implemented in other path codes. Youshould keep a copy of this path code so that you have a “clean”copy of OneWorld in case you need to refresh anything.

Package Management

2–4 B73.3.1 (6/99)

All path codes share the same Object Librarian tables and the same system data source,and normally the same data dictionary. The only distinct tables across path codes arethe central objects/specifications (F987*), the version list (F983051), the processingoptions text (F98306), and the user overrides (F98950).

Suggested Package Names and Schedule

At J.D. Edwards we have found that each package should have an A and B version, soyou can alternate between these when you build packages. That is, each time you builda package, you alternate into which package you build.

If you are using both full and partial packages, you would have four packages per pathcode. This setup gives you two full packages (A and B) for production, and two partialpackages (A and B) for production. For example:

PRODB733FA Standard Production Full A

PRODB733FB Standard Production Full B

PRODB733PA Standard Production Partial A

PRODB733PB Standard Production Partial B

Update packages might be named as follows:

PRODB733UA Production Update Package 1

PRODB733UB Production Update Package 2

PRODB733UA Production Update Package 3

PRODB733UB Production Update Package 4

B73.3.1 (6/99) 2–5

Ensuring the Integrity of the Production Environment

Ensuring the Integrity of the Production Environment

As soon as you transfer objects into your PRODB733 path code, these changes can beaccessed by end-users immediately. Therefore, you must make sure to test the modifiedobjects before transferring them to production.

There are two ways that objects transferred into the production path code can beimmediately deployed to end-users:

� )! � &$� � �&$%*� *%�� $%��%�! �� (�! &$�$ � �""��%�! �!#

%�� #$% %�� (�� '� %��% �""��%�! � $%�� #!� %�� %#�� !��%

��%� $!&#�� $ � ��&��$ "�!"�� (�! �#� &$� � � "�#%�� "�� !#

� )! � (�! ��$ #��'�� &"��%� "�� ! %�� ""��%�!

(�%�!&% $"��%�! $� !# �!#� � �!#��%�! ��!&% �&$%*� *%�� $%��%�! �

$��

� �� )!& �&�� &"��%� !# "�#%�� "�� ! � �&$� �$$ �& �%�! �&��

�!# %��% "�� %�� &$� �$$ �& �%�! � ��&�� %��% "�� $ �&��%�

%�� !��) �� (�%� �� !%��# �&$� �$$ �& �%�! $ � %�� "�%� �!��$

��*� �!��%�! �

The only way you can ensure that modifications transferred to your production pathcode are not immediately available to end-users is to avoid using partial packages orupdate packages containing applications without specifications. Also, do not transferbusiness functions into the production path code until you are ready to deploy, becausea global build of business functions done during a package build will automaticallyinclude the new functions. You can be assured that when you transfer changes into theproduction path code they will not be available until you build a full or update package.

Disabling Just-In-Time Installation

There are two methods for disabling just-in-time installation:

� ��#!&�� '�#! �� % ��$%�# �� )!& �� $�� !# %��

� '�#! �� %� ��% �$� � )! � (�! $�� $ ! %! %��% � '�#! �� % � �

�!�$ �% ��'� $"��%�! $ �!# � �""��%�! (�� !% �� %! #�%#��'�

%�� &$� �� $ %&# �� !�� (�#�$ #��!�� $ %��% )!& &$�

%��$ �� &#� � %�� &�&��%�'� � $%��%�! "#!��$$ (�� )!& &"��%� )!&#

"#!�&�%�! �� %#�� !��%$ (�%� %�� ( �� (�#�$ �� $� ) &$�#

(�! ��$ � $%�� "�#%�� "�� !# #��'�� &"��%� "��

Package Management

2–6 B73.3.1 (6/99)

�� "�� "��

�� "��

� � �� !��

�� #� ��

�� "�� "��

�� !��

�� !�� !��

�� !�� # ��

�� # �� $�� "��

��

Even if you disable JITI, data dictionary items will still be copied viaJust-in-Time-Installation to the global tables. This is due to the data dictionary structureand cannot be disabled.

B73.3.1 (6/99) 2–7

Understanding the Development Processes


You should understand the development processes that J.D. Edwards recommends. Forinformation about developing long-term enhancements and short-term fixes, see thefollowing:

� ��

� ��

Working with the Normal Development Process

The following provides an overview of how you should perform your normaldevelopment cycle.

In the DEVB733 Path Code:

1. Make modifications

2. Test modifications

3. Transfer objects to CRPB733

In the CRPB733 Path Code:

4. Build package

5. Schedule package

6. Deploy server objects to the enterprise server’s CRP path code and test

7. Schedule package

8. Transfer objects to PRODB733

In the PRODB733 Path Code:

9. Build package

10. Schedule package

11. Deploy server objects to the enterprise server’s PRODB733 path code and test

Package Management

2–8 B73.3.1 (6/99)

DEVB733 Path Code

CRPB733 Path Code

Make modifications

Test modifications

Transfer objects to CRPB733

Build package

Test modifications

Deploy server objects to the enterpriseserver’s CRP path code and test

CRPB733 Path Code

PRODB733 Path Code

Schedule package

Transfer objects to PRODB733

Build package

Schedule package

Deploy server objects to the enterpriseserver’s PRODB733 path code and test

To work with a normal development process


� �� $)( ,$)& $��(' �&$" (�� %�(� �$�� $��, (��

$��('� (�'( (��"� �#� �� (��" �� #�

� �'� (�� ','(�" �$& �#, #)"��&�#� ','(�"� ($ (&�� ,$)&

��#��' �!+�,' �� # (�� $��(' +�(� � �� #)"��&�


� �� (��' $��( #��' ($ �� $# (�� !$�� '�&*�&� (&�#'��& (�� $��( ($

(�� '�&*�&�' �� %�(� �$�� '( (�� $��( ��#'( (�� '�&*�&�

3. Transfer objects


B73.3.1 (6/99) 2–9

� �&� � �� "(!��% *�'� ��' �%�"&��% '# '%�"&��% '�� #��' '# '��

�� $�'� �#�� &� '�� -#(' #� '# �#"��%! '�� '%�"&��%

�#$'�#"� �� & #��' �& "#' �" $%#�(�'�#"� �(' �' �& "#* �)��

�#% +#( '# �(� � � '�&' $�� " '�� $�'� �#��

4. Build a package

� �(� � � $�� ( � $�%'�� #% ($��'��


� ��&' '�� "�* + �(� '� �(' ("%� ��&�� $�� " '�� $�'�

�#�� +#( ��" #" + '�&' ��"&' *#%�&'�'�#" $%#��&&�&� "#' &�%)�%

$%#��&&�&�� !�!��%� �)�" '�#(�� '�� "�!� #� '��& $�� *�

$%#�� + �� ($��'� $�� "(!��% � �#% '��

$�'� �#�� ' �& � ,'�&'� $�� %��' "#* ��(&� +#( ��)� "#'

%� ��&�� ' '# +#(% (&�%&�

� ��( � '�� ($��'� $�� '# � '�&' !��"� �"� '�&' �" �"

�")�%#"!�"' (&�"� �� #��'& *�'� �� '��

6. Deploy server objects

� �$ #+ &�%)�% #��'& '# '�� $�'� �#�� #" '�� "'�%$%�&�

&�%)�% �"� '�&'� �� +#( $%��%� +#( ��" �(� � '�� &�%)�% $�� "�

&��( � ��$ #+!�"' �' '�� &�!� '�!� +#( �(� � �"� &��( � '��

*#%�&'�'�#" $��

7. Schedule the new package to CRP users

8. Transfer objects

� �&� � �� "(!��% *�'� ��' �%�"&��% '# '%�"&��% '�� #��' '# '��

�� $�'� �#�� &� '�� -#(' #� '# �#"��%! '�� '%�"&��%

�#$'�#"� �� & #��' �& "#* �" $%#�(�'�#"� �' �& "#* �)�� #%

+#( '# �(� � � $�� " '�� $�'� �#��

Note: If just-in-time installation is enabled, the objects could be accessedimmediately.

9. Build a package

� �(� � � � ��"' *#%�&'�'�#" $�� ( � $�%'�� #% ($��'��

� ��%�#%! � &�%)�% $�� (� �� $'�#"� +� +#( ��" '%�"&��% '��

&�%)�% $�� "#* #% *��' ("'� �' ��& ��" '�&'�� #" �

*#%�&'�'�#"��

10. Schedule the new package to production users’ workstations.

11. Deploy server objects

� �$ #+ &�%)�% #��'& '# '�� $�'� �#�� #" '�� "'�%$%�&�

&�%)�% �"� '�&'� �� +#( $%��%� +#( ��" �(� � '�� &�%)�% $�� "�

&��( � ��$ #+!�"' �' '�� &�!� '�!� +#( �(� � �"� &��( � '��

*#%�&'�'�#" $��

Package Management

2–10 B73.3.1 (6/99)

Developing Short-Term Fixes

Sometimes you will want to make a simple change to an application that is undergoingmajor enhancement work in the DEVB733 path code. When objects have beenmodified in the DEVB733 path code, it might be too risky to make a simple change andget it deployed quickly. Therefore, you should make the change in CRPB733 so thatyou can quickly get the fix to users. Do not forget to make the change to the CRPB733and the DEVB733 path codes.

To develop a short-term fix


� �� #(' +#(% #��'& �%#! '�� $�'� �#�� #��+ '��

#��'&� '�&' '��!� �"� �� '��! �� "�

� �&� '�� &+&'�! �#% �"+ "(!��%�"� &+&'�!� '# '%�� +#(%

��"��&� � *�+& �� " '�� #��'& *�'� � �� "(!��%�

2. Transfer objects

� �&� � �� "(!��% *�'� ��' �%�"&��% '# '%�"&��% '�� #��' '# '��

�� $�'� �#�� &� '�� #(' #� '# �#"��%! '�� '%�"&��%

�#$'�#"� �� & #��' �& "#* �" $%#�(�'�#"� ' �& "#* �)�� #%

+#( '# �(� � � $�� " '�� $�'� �#��

Note: If just-in-time installation is enabled, the objects could be accessedimmediately.

3. Build a package

� (� � � $�� ( � $�%'�� #% ($��'��

4. Schedule the new package to production users’ workstations.

B73.3.1 (6/99) 2–11

Comparing the Deployment Methods


After you have made software changes, the method you use to deploy those changes toworkstations on your enterprise depends on the type of package you typically build, aswell as other factors. For example, developers have different needs than productionusers, and therefore require a different type of package.

Understanding Cumulative and Noncumulative Update Packages

If you use a cumulative update package strategy, you have one package that you add to,rebuild, and rerelease to users, instead of creating a new package every time you have amodification you want to deploy. To use a cumulative package, you would need tofollow these steps:

� � ��

� � � � ��

� ��

If you use a noncumulative strategy, you would create and deploy a different packageevery time instead of using the same package. For example, if you deploy onemodification per week for 10 weeks, there would be 10 different packages with onlythe software changes for that week.

Recommendations for Sites Using Partial Packages and JITI

J.D. Edwards recommends that you adopt a noncumulative update package strategy.Each week that you build a new update package, if you have a modification to deploythat cannot be done via just-in-time installation (such as business function changes), werecommend that you also rebuild the partial package for that week to ensure that thepartial package contains the latest changes. If you follow this recommendation, whenyou want to load a new workstation (or completely refresh any machine), you simplyneed to install the partial package; you don’t need to install any update packages.

Package Management

2–12 B73.3.1 (6/99)

Recommendations for Sites Using Full Packages without JITI

J.D. Edwards recommends that you adopt a cumulative update package strategy. Eachweek that you need to deploy a change, add that object to the existing update package,and then rebuild and schedule it. The advantage of this strategy is that you do not needto rebuild your full package each week. By using this strategy to load a newworkstation (or to completely refresh any machine) you will need to install the fullpackage and the one cumulative update package.

The disadvantage of using this strategy is that the update package may become so bigthat deployment time is increased. You will need to determine your threshold for whento rebuild the full package that new workstations will load, while existing users willinstall the new update package.

Recommendations for Developers

Developers must use full packages. You may deploy update packages to them, butdevelopers do not use partial packages since partial package machines never receivedevelopment objects.

When installing a full or update package, machines with compilers will automaticallyreceive development objects. When installing an update package, machines withcompilers will automatically receive development objects. Developers receive source,headers, and libraries. The installation process builds the object into the businessfunction library and DLL (dynamic link library), and thereby preserves any businessfunction changes the developer made. For more information about package types, see�� .

Multitiered Deployment and Just-In-Time Installation

Just-in-time installation (JITI) can be used in remote locations that are using multitiereddeployment to install packages. However, you might find that performance time for thejust-in-time install is unacceptable. In this case you may wish to use full packages anddeploy software changes through update packages.


Each deployment method has its strengths and limitations. To help you decide whichmethod is right for your needs, here are some key points about the different methods:

� � ��

��

��

� ��

��


B73.3.1 (6/99) 2–13

� �� '"��&� "��% �'%& '%� �� "�!*�� & &! �� %��'�� &!

)!$�%&�&�! % ' ��%% *!' �$� '%� � &�� '%� %&��&�! ��&'$��

� �� '�� "�$&�� "��% �� %! '%� �� "�!*�� & ��

� ��!$�� % ��$��* �� !�� ! � �� !' �� '%� &�� '%�

%&��&�! ��&'$� &! ��"�!* &! � �� &��& �!�% !& ��(� � ��!$��

� %&��

� � )!$�%&�&�! ��%� %"�� % � �! %��$�&�! � �! %��$ ��"�!*� � � "�$&��

"�� &��& "$!(��% &�� '� �! ��'$�&�! !� � ��!$�� *�&

��!)% '%�$% &! �!�� ! �* &�� ""�� !$�� ""��&�! %� &��%

%�&'�&�! *!' �!'�� '%� ��&��$ �!$�%&�&�! %&��&�! !$ ��

�"�!*�� & &! ��"�!* &�� "�$&�� "��

� �%� �� & %&��&�! &! %'��& � �!$�%&�&�! %&��&�! $�#'�%& &�$!'��

�!�� $�'�� &%� ! !& '%� �� & %&��&�! �!$ � � �&��

� %&��&�! �

� �%� �'�&�&��$ �"�!*�� & &! � %&�� $!� �!$� &�� ! � ��"�!*�� &

�!��&�! � �!' %�!'�� ! %��$ &��% ��&�!� �� *!' ��(� �!$� &��

)!$�%&�&�! % "�$�!$�� !$�� %!�&)�$� � %&��&�! % "�$ ��*�

� �%� �� "�!*�� & )�� *!' �� &! "'%� !��&% � � %�$(�$

"�� $!� &�� &$�� !��&% ��&� %!'$�� &! � &�$"$�%� %�$(�$%�

Package Management

2–14 B73.3.1 (6/99)

B73.3.1 (6/99) 2–15

Deploying Various Types of Modifications


It is important that you understand which types of objects (and therefore modification)can be deployed through each package type.

Partial packages include the following:

� �## �&%)&# ��*�� +) %�)) �+%�* &% �.%�$ � # %"�� # �(�( �) ��)�

� �'�� * &%) �&( &%#. *�&)� �''# ��* &%) %��))�(. *& ) �% &% �%� ��* *&

�%��&(#� -'#&(�(

� �## �&%)

� ��#')� ��*�� %� �&+%��* &%

The following illustrates which types of changes are installed with a full package, anupdate package with specifications, and an update package with no specifications.

��

� ��

� ��

��

$�� ,�%* �+#�) � � �

�&�� ,�(( ��) �� *�-*� � � �

�*� �*(+�*+(� � � �

�(&��)) �'* &%) ��'&(*� � � �

��

� ��%�+�� &+(�� %�#+��!��* � � *��(� ) ��&$' #�(�

� �

�&%)&# ��*�� ) � �

�*� �*(+�*+(� � �

��#� � � �

��$��

Package Management

2–16 B73.3.1 (6/99)

��

��

��

� ��

��('*, � � �

%�� !& ��('*, � � �

��('*, ��,� �,*-�,-*� � � �

��('*, �'�� .�**!��+ � � �

��('*, �*'��++!&� �(,!'&+ � � �

��*+!'&+ �&� �*'��++!&� �(,!'& ��$-�+ ��2(�&�+ '& (*'��++!&� '(,!'&+�

� � �

%�� !& ��*+!'&+ � � �

�*'��++!&� �(,!'& ��%($�,�+ � � �

��

!�$�+ �� &��

��

�,*-�,-*� �+(��!�!��,!'&+� � �

&��0�+ � �

�'!&+ � �

��

��$(+ �,'*�� '& , � ��*.�*

��$(+ �,'*�� '& , � �'*#+,�,!'& � �

��&�*!� ��0, ��,� �,*-�,-*� � �

��,� �!�,!'&�*1 ,�%+ �+�� !& , � ��

'-&��,!'& �'�� '-&��,!'& !+ *�)-!*�� '* �-$$�&� (�*,!�$ (��#��+� �&� '(,!'&�$ �'* -(��,�(��#��+�

� � �

'*�!�& ��&�-��+ � � �

�'&2�&��'*$� ��"��,+ ��-+,'% !,�%+ ��& ��($'1�� , *'-� �&1 (��#�� ,1(��

� � �

��($!��,�� '��$ ��,� ��,� !+ *�)-!*�� '* �-$$�&� (�*,!�$ (��#��+� �&� '(,!'&�$ �'* -(��,�(��#��+�

� � �

��/ �'&+ � �


B73.3.1 (6/99) 2–17

For a full package or an update package with object (O) types, the following changesare installed:

Applications:

� � ��

� �"�� (�$$��% �� &�)&�

� ��&� �&$'�&'$�

� �$"��%% �#&�"!% ��#"$&�

Business Functions:

� � �!�'�� "'$��!��'��& �� &��$� �% � �" #��$�

� �"!%"��&�� %

� ��&� �&$'�&'$�

� ��

� ��

Batch Applications:

� ��#"$&

� � �� % ��#"$&

� ��#"$& ��&� �&$'�&'$�

� ��#"$& �"�� (�$$��%

� ��#"$& �$"��%%�!� �#&�"!%

� ��$%�"!% �!� �$"��%%�!� �#&�"! ��'�% ��#�!�% "! #$"��%%�!�

"#&�"!%�

� � �� ! ��$%�"!%

� �$"��%%�!� �#&�"!�� #��&�%

Business Views:

� ��% ��!��

Tables:

� �&$'�&'$� �%#��&�"!%�

� �!��)�%

� �"�!%

Package Management

2–18 B73.3.1 (6/99)

Miscellaneous:

� ��"&) �*%(�� %$ *�� (,�(

� ��"&) �*%(�� %$ *�� %(!)*�*�%$

� ��$�(�� .* ��*� �*(+�*+(�

� ��*� ��*�%$�(/ *�#) �)�� *� ��*�%$�(/ ��#�$�)*(�*�%$�

� %+$��*�%$ �%�� %+$��*�%$ �) (�'+�(�� %( �+"" �$� &�(*��"

&��!��)� �$� %&*�%$�" �%( +&��*� &��!��)�

� %(��$ ��$�+��)

� �%$0�$��%("� �� *) ��+)*%# �*�#) ��$ �� &"%/�� *�(%+�� $/

&��!�� */&��

� ��&"��*�� %��" ��*� ��*� �) (�'+�(�� %( �+"" �$� &�(*��" &��!��)�

�$� %&*�%$�" �%( +&��*� &��!��)�

� ��- �%$)

For an update package with JITI (Just-in-time-installation) types, the following changesare installed:

Applications:

� #��

� �%�� ,�((��) �� *�.*�

� ��*� �*(+�*+(�

� �(%��)) �&*�%$) ��&%(*�

Batch Applications:

� ��&%(*

� #�� ) ��&%(*

� ��&%(* ��*� �*(+�*+(�

� ��&%(* �%�� ,�((��)

� ��&%(* �(%��))�$� �&*�%$)

� ��()�%$) �$� �(%��))�$� �&*�%$ ��"+�) ��&�$�) %$ &(%��))�$�

%&*�%$)�

� #�� $ ��()�%$)

Business Views:

� ��"�) ��$��


B73.3.1 (6/99) 2–19

Miscellaneous:

� ��!�� !�� !�� !��

� �� !��

� �� ! ��

� ��#�� !� �� "�� !�� "

� �� "��

� �� !�� !��

�� !��

Package Management

2–20 B73.3.1 (6/99)

B73.3.1 (6/99) 2–21

Deploying Data

This chapter describes how to deploy a new replicated local database, and a specialdatabase for store-and-forward users.

Deploying a New Replicated Local Database

Normally, you do not need to deploy a new Microsoft Access database because datareplication takes care of pushing changes to end-users. The database in the packagecannot be set up as a subscriber because it is a snapshot in time of your database.Therefore, if you want to keep the database in sync with the publisher tables, you needto refresh the data periodically.

You should consider keeping the database in sync with the publisher tables. When anexisting OneWorld machine does a complete refresh by installing a full or partialpackage, it receives old data. It is not marked as out of sync, so data replication has noway of knowing that the machine reinstalled OneWorld with an out-of-date MicrosoftAccess database.

If a new machine is set up, the administrator would have to set up the user as asubscriber, and that machine will be marked as out of sync. Then, when signing on tothat new machine for the first time, the user will be prompted to receive the changeddata.

To refresh an existing package with a new database

1. Take a Microsoft Access database from a subscriber machine that has receivedall data changes.

2. Copy that database to the data location for that package.

3. Choose Package Assembly (P9601) from the Package and Deployment Toolsmenu (GH9083). The Work With Packages form appears.

Package Management

2–22 B73.3.1 (6/99)

4. Select the package and choose Define Build from the Row menu.

5. Proceed through the Package Assembly Director forms until you reach theCompression Options form.

6. On the Compression Options form, choose only the Compress Data option. Thiswill recompress the database, and from this point on anyone who installs thispackage will get current data.

Deploying Data

B73.3.1 (6/99) 2–23

To verify that compression was successful, check the size and date of the JZ file underOneworld/B733/pathcode/package/data. If the size is only 1KB, this means thecompression failed.

Deploying a Special Database for Store-and-Forward Users

Store-and-forward users require Microsoft Access databases that are much larger thannormal users. Therefore, you will want to build an update package that has one lineitem for the special Access database. Store-and-forward users must take full packagesbecause they will not be connected to the network to install their application viajust-in-time installation.

For this reason, they should use an environment that has Just-In-Time-Installationturned off. Instruct your store-and-forward users to install the normal full package, andthen install the update package created for store and forward users. See Working withStore-and-Forward in the Configurable Network Computing Implementation Guide formore detail.

To deploy a database for store-and-forward user

1. Define the update package with one line for a database. Ensure that the specialdatabase that you have created for store-and-forward users actually resides in thesource destination defined through Database Item Revisions.

2. Choose Package Assembly (P9601) from the Package and Deployment Toolsmenu (GH9083).

3. Select the package and choose Define Build from the Row menu.

4. Proceed through the Package Assembly Director forms until you reach theCompression Options form.

5. On the Compression Options form, choose only the Compress Data option.

6. Schedule the package to all machines that will be doing store-and-forwardtransactions.

Package Management

2–24 B73.3.1 (6/99)


Package Management

2–26 B73.3.1 (6/99)

B73.3.1 (6/99) 3–1


Because the OneWorld Tools are comprehensive and flexible, you can customizecertain aspects of business solutions and applications without making custommodifications. J.D. Edwards refers to this concept as “modless mods,” which aremodifications that you can perform easily without the help of a developer. You canperform modless mods on the following:

� �� "��

� ��

� ��! ��"��

� �� $

� �� " �!��

� � �� % ��! ��

� ��# ��

This kind of flexibility improves efficiency and provides distinct advantages, such asthe ability to do the following:

� �$�� !�� $��

��

� ��!�� !��

� ��

� �� !�� % !��

However, even with the full commitment of J.D. Edwards to making the tools asflexible and robust as possible, if the need does arise to modify OneWorld, there arecertain rules and standards to ensure that software modifications perform like modlessmods for a seamless and predictable upgrade to the next release level.

You should prepare for the upgrade before making any custom modifications to ensurea smooth upgrade. If you plan modifications properly, you will have minimal work todo following an upgrade. This should result in the least amount of disruption to yourbusiness and a reduction in the overhead cost involved during an upgrade because theupgrade time is reduced.

OneWorld keeps track of all custom modifications as you check them into the server.Using this feature, you can run the Object Librarian Modifications (R9840D) reportprior to a merge to see a list of the changed objects.

Package Management

3–2 B73.3.1 (6/99)

OneWorld consists of control tables (such as menus, user defined codes, versions, andthe data dictionary) and transaction tables (such as Address Book and the Sales OrderFile). J.D. Edwards ships the control tables with data that you can modify, whiletransaction files contain your business data.

Both of these kinds of tables go through an automatic merge process during an upgradewhere control tables are merged with new J.D. Edwards data, while transaction files areconverted to the new specifications, keeping your existing data. For the objectspecification merges (such as business view, tables, data structures, processing options,event rules, and applications), there are processes in place that merge the specificationsor overlay them depending upon the rules defined under �� .

B73.3.1 (6/99) 3–3

What an Upgrade Preserves and Replaces

If your business needs require custom modifications, observe the following generalrules for OneWorld modifications to help ensure a smooth and predictable upgrade.These rules describe which of your modifications the upgrade process preserves andwhich modifications it replaces.

� %��!�� $ ��

$� � �� "�� " �� "�� "��

�� $� �� $� � ��

�� "�� $� � �� "��

�� $� �� "��

�"�� "� ��

� %�� $�� "�� $� � �� "��

��

J.D. Edwards provides you with the Object Librarian Modifications (R9840D) report,which you can run before the upgrade process to identify objects that you modified.

For details about what OneWorld preserves and replaces during an upgrade, see thefollowing:

� ��

� �� !� ��

� ��

� �� #� ��

� ��

� ��

� �� !��"� � ��

� �� !��

� ��

� ��

� �� !��

Package Management

3–4 B73.3.1 (6/99)

Understanding the General Rules for Modification

The following general modification rules apply to all OneWorld objects:

� �!�' ��"' '�/ (�#��,+� -+� +1+,�& �(��+ �� 4 �� '��(*%� -+�+

*�+�*.�� +1+,�& �(��+ ,!�, �'��%� ", ,( ��,� (*"2� �"��*�', �))%"��,"('+

�'� .�*,"��% *(-)+� 1 -+"' +1+,�& �(��+ �� 4 �� (* 1(-* �-+,(& -+� ��

�'��(*%� �(�+ '(, (.�*%�1 1(-* &(�"�"��,"('+ /",! �� /�*�+

�))%"��,"('+�

� �( '(, �*��,� �-+,(& (* '�/ .�*+"(' '�&�+ ,!�, �� "' /",! �� (*

�� !�+� �*� *�+�*.�� )*��"0�+ �(* +,�'��*� .�*+"(' ,�&)%�,�+ ,!�,

�� /�*�+ +�'�+ (-, �(* 1(- ,( �()1� ,( �*��,� '�/ ,�&)%�,�+ (*

.�*+"('+� �+"' ,!�+� )*��"0�+ �(�+ '(, )*�+�*.� 1(-* �-+,(& .�*+"('+ "'

��+� (� � '�&"' �('�%"�,�

� (* -) *��+� 1(- +!(-%� �-"%� � )��$� � �*(& ,!� %�+, &(�"�"�� ',*�%

(�#��,+ +�, �'� )�*�(*& ��$-)+ (� 1(-* ��.�%()&�', +�*.�*� ��',*�%

(�#��,+� �'� ��#��, �"�*�*"�' ��,� +(-*��+ +( 1(- ��' ��++ ,!(+�

+)��"�"��,"('+ �(* �(&)�*"+(' (* �(* ,*(-�%�+!((,"' )-*)(+�+� �� ,!�

�� (* "'�(*&�,"('�

Understanding Interactive Application Rules

Do not delete controls, grid columns, or hyperitems on existing OneWorld applications;instead, hide or disable them. OneWorld might use these for calculations or asvariables, and deleting them might disable major functionality.

What an Upgrade Preserves

An upgrade preserves custom changes to the following:

� ��/ �))%"��,"('+� �� 1(- '�� ,( �*��,� �' �))%"��,"('� ,!�*� �*� ,/( /�1+

,( ��(&)%"+! ",� �(- ��' �*��,� �' �))%"��,"(' �*(& +�*�,�!� (* 1(- ��'

�()1 �' �0"+,"' �))%"��,"('� �(- ��' �()1 �' �))%"��,"(' -+"' ,!�

�))%"��,"(' ��+" ' �"��+ 3()1� ��,-*� ,( �()1 ,!� �))%"��,"('� �!"+

�%%(/+ 1(- ,( �()1 �%% (� ,!� �))%"��,"(' +)��"�"��,"('+� "'�%-�"' �.�',

*-%�+�

Use the Copy feature only to create a completely new application. If you use itto copy an existing application for some modifications, your new applicationdoes not receive any J.D. Edwards updates during an upgrade. For example, youcould use Copy to make a copy of the Sales Order Entry (P4211) application,renaming it to P4211X. However, while the upgrade process replaces the SalesOrder Entry (P4211) application, your P4211X application does not receive anychanges that J.D. Edwards might have made to this application.


B73.3.1 (6/99) 3–5

� ��% ��"! "� �&�!"�� %� �! �� !� ��!� ��#��

� ��% �'�� "��!

� ��% ��" ��!

� ��% � �� #��!

� ��' !"'�� !� !#�� ! ��"! �� !� ��% �� %� �! ��" ��!

��$� "�� !"�� !� ��"��!� !� �� '�# ��$� ��#!"�� "�� !"'�� '�#

�� "� �� "�� !�� ' ��% ��" ��! �� "� �� "��

� ��' ��)�� "� �$� ��!

� ��"� ��"�� ' �$� ��!

� ��"�� !�(� ��! �� " ��!� �� %� �! ��! "� ��

��% ��" �� "�� % ��!� �� "�� !��"%� � �� "�� !�� '�# ��$�

�� #!"�� " �� "�� " ��! ��!��' �� "�� "�� !

��! ��" ��" "�� $��" #��! � "�� #��"��"' �� "�� "�� "�

"�� #�� '�# �� "��!� ��" ��! #!�� "�� !��

��

� ��#�� ! �� "��! � ��#��!� �� #�� !! ��! ��%

�� %� �! ��" ��! "� "�� '�# �#!"�� "�� !��#�� # ��

�$��% "�� "�� !��#�� "� �� #��

What an Upgrade Replaces

An upgrade replaces custom forms on existing OneWorld applications. To create acustom form, you must create a custom application using system codes 55 - 59, andplace the custom form on that custom application. From a performance standpoint thereis no difference if an external application is called from a row exit or a form within theapplication. You can add custom form exits and row exits to J.D. Edwards applications;these custom exits can call your forms within your custom applications.

Understanding Report Rules

These rules apply to Report Design Aid specifications.

Do not delete objects on existing OneWorld reports; instead, hide them. OneWorldmight use these for calculations or as variables, and deleting them might disable majorfunctionality.


An upgrade preserves the following changes:

� ��% �� "!� �� '�# � ��"� � �� "� "�� "%� %�'! "� ��!� �"�

�� ! "� � ��"� � �� " � �� !� �"�� "�� "�� ! "� ��' �� &�!"��

Package Management

3–6 B73.3.1 (6/99)

!� �!#� ��$ �� ( � !� �!# $"�� !# �"�� " *�� (� ��#$!� #�

�� ( #�� !� �!#� ��" ��&" (�$ #� �� ( �� #�� !� �!# " ��#��"�

��$�� %��# !$��"�

Use the Copy feature only to create a completely new report. If you use it tocopy an existing report for some modifications, your new report does not receiveany J.D. Edwards’ updates during an upgrade. For example, you could use SaveAs to make a copy of the Print Pick Slips (R42520) report, renaming it toR42520X. However, while the upgrade process replaces the Print Pick Slips(R42520) report, your R42520X report does not receive any changes that J.D.Edwards may have made to this report.

� ��& ��#" #� �'�"#�� &�!�" !� �!#"� ��"� ��$��

� ��"#��#"

� �� %�!��"

� �$��!�� %�!��"

� �#� %�!��"

� �$� #�� %�!��"

� �#��"� %�!��"

� ��#��!( %�!��"

� ��( "#(�� "� "$�� " ��#" �� !"� ��& �� &�!�" ��#!��"

��%� #�� "#��!� ��"� ��#��"� "� �� (�$ ��%� ��$"#�� #�� "#(�� (�$

�� #� �� #�� "�� ! ��( ��& ��#!��" �� #� � !� �!#

� ��#�� "�)� ��" ��! ��#"� �� &�!�" ��" #� ��

��& ��#� "$�� " � ��#!�� #�� & !��"� �� #�� "��#&�!� �� #��

"�� (�$ ��%� �� $"#�� #� #�� #" ��" ��( !��# ��'#

#� �� #��!� ��" ��" ��# ��# #�� %��# !$��" �! #�� $��#��#( ��

#�� !� �!# �� ( &�(� ��#�! #�� $ �!�� !��!!�� #��"� ��#!��" $"��

�� !# �"��

� �#� ��#��!( �%�!!��"


An upgrade replaces custom sections on existing OneWorld reports. Use ReportInterconnect instead and connect to a new custom report that uses system codes 55 - 59.There is no difference in the performance of a report being called through reportinterconnections.

Understanding Application Text Changes

An upgrade preserves overrides done in Application Design Aid, Report Design Aid, orInteractive or Batch Vocabulary Overrides.


B73.3.1 (6/99) 3–7

Understanding Table Specification Rules

An upgrade merges your table specifications from one release level to the next.



� ��% "��!

� #!"�� ! "� �� %� �! "��!


An upgrade replaces columns added or removed from existing J.D. Edwards tables.This includes changing field length, field type, and decimal position.

Instead of adding a new column to an existing J.D. Edwards table, use a tag file withsystem codes 55 - 59. For custom tag files, be aware of data item changes in the J.D.Edwards data dictionary. From one release to the next, J.D. Edwards might changecertain data item attributes, such as data item size, which can affect data integrity andhow data is stored in the database.

For this reason, you might need to use the Table Conversion tool to convert the tag filedata to the new release level. For base J.D. Edwards files, the upgrade process takescare of the data dictionary changes by upgrading the OneWorld database to the newrelease level. An upgrade preserves custom indices over the custom tag files.

Understanding Control Table Rules

Control tables contain user defined codes (UDCs), menus, and data dictionary items.An upgrade merges your control tables from one release level to the next using theChange Table process, which uses your control tables, not J.D. Edwards tables, as thebasis to do the data merge.



� �"� ��"�� ' �#!"�� !� !#�� ! ��! "� �%� ��#��

��!!� ' "�&"� �� #�� !! #!�! '�# ��"� ��"�� ' �! "�� !��

�� !� �� " %�"� �� %� �! ��"� �"��!� '�# ��!

�$� �� "� ��% ��"� �"��! #!�� !'!"�� ! �� ( ��

� �!� �� !� �� #�� !! �� ! ��' ��% �� (��

�� %� �! $��#�!� ��#�! �%�� ' �� %� �! � � !'!"��

��$�� $�� !! ��!� �� "! ��' �� %� �!

�� (�� $��#�! "��" ��" %�"� '�# �#!"�� $��#�!�

Package Management

3–8 B73.3.1 (6/99)

� ��%#� �� #� � � � ��$ '�$� �� '�"�# ��#� ��%#� ) %" �%#$ �

��# &�""��


An upgrade replaces columns added or removed from existing J.D. Edwards controltables.

Understanding Business Views Rules

Do not remove columns from existing business views. Changing business views thatapplications use can cause unpredictable results when you run the application. If youneed to hide columns, do so at the application design level using either ApplicationDesign Aid or Report Design Aid. There is not much of a performance gain by deletinga few columns from a business view.



� ��' �%#$ � �%#��## &��'#

� ��' � �%��#� � ��#� " ��# $ $�� (�#$�� "�� %#��## &��'#


An upgrade replaces columns removed from J.D. Edwards business views.

Understanding Rules for Event Rules


� �%#$ � �&��$ "%��# � " $�� '�� %#$ � ��$#�

� �!!��$� �#

� ��! "$#

� ��#

� �%#��## %��$� � �&��$ "%��#

� �%#$ � �&��$ "%��# � � ��' �%#$ � � �$" �

� " �� '�"�# �!!��$� �#� "�! "$#� $��#� �� %#��## �%��$� �

�&��$# $��$ �� &� ��) �� '�"�# �&��$ "%��# �$$�� $ $�� #��

�&��$


B73.3.1 (6/99) 3–9

� #% �� *�%�& �$$ ��'�#"&� %�$#%'&� '�� &� �"� �(&�"�&& �("�'�#"

�)�"'& '��' ��)� �+�&'�"� �)�"' %( �& �''�� " ($�%�� &�� & �"�

�$$�"�& ,#(% �(&'#! �)�"' %( �& '# '�� "� #� '�� )�"' %( �&� �� !�%��

$%�"'& � %�$#%' �� '# "#'��, ,#( #� �", �)�"' %( �& '��' '�� ($�%��

$%#��&& ��&��

To restore your custom event rules to J.D. Edwards objects, highlight and dragthe event rules back to the proper place in the event and enable them. Prior to anupgrade perform the following:

� �(" '�� ' ��%�%��" �#��'�#"& �� %�$#%' '# ��"'��,

!#�� $$ ��'�#"&

� �%�"' '�� )�"' %( �& �#% '�� !#�� $$ ��'�#" &# '��' ,#( ��"

&�� '�� #�� "� '�� )�"' *��" %�&'#%�"� �(&'#! �)�"' %( �&

Understanding Data Structure Rules


An upgrade preserves all the following custom data structures:

� #%!&

� �%#��&&�"� #$'�#"&

� ��$#%'&

� (&�"�&& �("�'�#"&

� ��"�%�� '�+'


An upgrade replaces the following custom modifications to J.D. Edwards datastructures:

� #%!&

� �%#��&&�"� #$'�#"&

� ��$#%'&

� (&�"�&& �("�'�#"&

� ��"�%�� '�+'

To bring your custom modifications to J.D. Edwards data structures forward to the nextrelease level, run the Object Librarian Modifications (R9840D) report to list all of themodified data structures, and use this report as a guide for manually refitting datastructure changes.

Package Management

3–10 B73.3.1 (6/99)

Understanding Business Functions Rules

For any new custom business functions, create a new (custom) parent DLL to storeyour custom modifications. See the OneWorld Development Tools Guide for details.


An upgrade preserves new custom business function objects.


An upgrade replaces modifications that you made to existing J.D. Edwards businessfunctions and any business functions added to existing J.D. Edwards business functionobjects. To bring your custom changes forward to the next release level, run the ObjectLibrarian Modifications (R9840D) report to list all of the modified business functions,and use this report as a guide for manually refitting the business function changes.

Always use the standard API (jdeCallObject) to call other business functions fromwithin a business function. Not following this and all other standards will causeproblems.

To determine modifications to the source of existing base J.D. Edwards businessfunctions, use a third-party source-compare tool, such as Microsoft WinDiff. Todetermine modifications to APIs within business functions, see the OneWorld onlinehelp feature for the most current APIs.

Understanding Version Rules

For new custom versions, create a new version with a name that does not begin withXJDE or ZJDE. See the OneWorld Foundation Guide for details.


An upgrade preserves the following:

� ��

� ��

� ��


B73.3.1 (6/99) 3–11


An upgrade replaces the following:

� ��

� ��

In addition, processing option data is copied but not converted for non-JDE versionsusing JDE processing option templates. A warning is issued at runtime, and some datamay be lost.

Also, event rule modifications for custom versions on JDE templates are not reconciledwith the JDE parent template.

Package Management

3–12 B73.3.1 (6/99)

Object Management

Package Management

3–14 B73.3.1 (6/99)

B73.3.1 (6/99) 4–1

Object Management

By industry standards, an object is a self-sufficient entity that contains data as well asthe structures and functions used to manipulate the data. In OneWorld, an object is areusable entity that is based on software specifications. A specification is a completedescription of a OneWorld object. Each object has its own specification, which is storedon both the server and the workstation.

OneWorld stores objects in two places:

� � '��" ��(!"� �� !� $� � %�� &�# �� &�# ��" �� "!� ��

��$�� ! �#" � ��" �� "� �" �! ��"�� "�� %� �!"�"��

"�� $� "�� "� � ��" �� " %�� "�� $�� ! �"

��

� '�� $� �� #�!�� %�� %�#�� %� �!"�"��! �� !� $� !�

��!� � � ��"�� "!� �" �! ��"�� "! "��" &�# � � ��"#��&

#!�� %�� &�# #� ��

For information about managing OneWorld objects, see the following:

� �� !"�� " ��$��"

� �� !"�� ! � ��"�� & "�� #�� !!

� �� "�� "�� " �� "!

� � �� #�! �� !"� �� "!

� ��!�� "!

� �� "! %�"� "�� !&!"��

� ��&�� ! ��"%�� "� !�# ��!

Package Management

4–2 B73.3.1 (6/99)

B73.3.1 (6/99) 4–3

Understanding Object Movement

This chapter describes the movement of objects between the central objects locationand the object destination when you use each of the following processes:

� "��% �(��.- �(� ��$��- �+�(, �+

� �)+%,-�-#)( �(,-�&&�-#)(

For information about object movement, see the following:

� ��&� ��$��- �2*� ��

� .,#(�,, �#�0 ��$��- �2*� ��

� .,#(�,, .(�-#)( ��$��- �2*� � �� ).+�� (!.�!� �

� .,#(�,, .(�-#)( ��-� �-+.�-.+� ��$��- �2*� ��

� �'�� /�(- �.&�

� .,#(�,, .(�-#)( �/�(- �.&� ��$��- �2*� � �� ).+�� (!.�!� ��

� ��#� ��$��- ��$��- �2*� ��

� �(-�+��-#/� �**&#��-#)( ��$��- �2*� ��

� �-�" �**&#��-#)( ��$��- �2*� ��

� ��-� �#�-#)(�+2 �-�',

Table (Object Type TBLE)

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Check In/Out and ObjectTransfer

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

With Check In/Out and Object Transfer, the following objectsmove:

� ��&� �(� -��&� �/�(- +.&� ,*��# #��-#)(,

� �).+�� #&�, ��

� ��&� "��+ #&�, ��"�

� ��$��- #&�, ��)�$�

� ��&� �/�(- +.&� #(�&.�� #&�, ��"11�

Package Management

4–4 B73.3.1 (6/99)

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Workstation InstallationÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

See “Workstation Installation” under Interactive Application(Object Type APPL) for information.

The table header is not the same as the actual table residing in a database. The tableitself is created through table design aid when you generate. Workstation Installationbrings down the table if it is stored in Microsoft Access.

Business View (Object Type BSVW)

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

With Check In/Out and Object Transfer, specifications move.




C Business Function (Object Type BSFN, Source Language C)

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


� ��

� ��

� � � � ��

� ��




Business Function Data Structure (Object Type DSTR)

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


� ��

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Workstation Installation ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ



B73.3.1 (6/99) 4–5

Embedded Event Rule

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

There are two types of event rules: embedded event rules andbusiness functions. You can check out business function eventrules (object type NER), but you cannot check out embeddedobjects.

Embedded event rules are moved when the object into whichthe event rule is embedded is checked out. For example, ifthere are embedded event rules attached to a table, interactiveapplication, or batch application, when you move them thespecifications for the embedded event rule moves with them.

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ



Business Function Event Rule (Type BSFN, Source LanguageNER)

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

There are two types of event rules: embedded and businessfunction. Business function event rules (object type BSFN) canbe checked out. When business function event rules arechecked out, the .h file moves to the include directory, the .cfile moves to the source directory, the .obj moves to the objdirectory, and the local specifications are updated.

Embedded event rules are moved when the object the eventrule is embedded into is checked out. For example, if there areembedded event rules attached to a table, interactiveapplication, or batch application, when you move them theembedded event rule moves with them.


� ��

� ��

� � � � ��

� ��

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ



Package Management

4–6 B73.3.1 (6/99)

Media Object Data Structure (Object Type GT)



ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

With Check In/Out and Object Transfer, data structurespecifications move.




Interactive Application (Object Type APPL)



ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

With Check In/Out and Object Transfer, the followingspecifications move, which include the following:

� ��

� ��

� ��

� ��


Workstation Installation ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

With Workstation Installation all objects and the MicrosoftAccess database, which contains replicated data, are copiedfrom the package to the workstation. (This does not apply toobjects in the package for which you do not includespecifications. In this case objects are not replicated, butinstalled on the workstation via just-in-time installation.)

Batch Application (Object Type UBE)

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

With Check In/Out and Object Transfer, report and event rulespecifications move. You must check in/out the versionseparate from the report.




Batch applications are interpretive and therefore do not have a DLL.


B73.3.1 (6/99) 4–7

Data Dictionary Items

The data dictionary resides in relational files on a server. This is the publisher datadictionary where you would make all data dictionary changes you want replicated toservers and workstations. OneWorld stores the publisher data dictionary in thefollowing tables:

� ��,� �,�& ��+,�* ��

� ��,� �"�%� �"+)%�0 ��/, ��

� ��,� �,�& �%)!� ��+�*"),"('+ ��

� ��,� �"�,"('�*0 �**(* ��++� � �'�(*&�,"(' ��

� ��,� �"�%� �)��"�"��,"('+ ��

� ��,� �"�,"('�*0 �&�*, �"�%�+ ��

� ��"� ��#��, ��,�"% ��

When you change data dictionary items, make sure you replicate those changes acrossyour enterprise. In a coexistence configuration, also make sure your WorldSoftware andOneWorld data dictionaries are synchronized.

There are two methods of replicating data dictionary changes:

� �+� ,!� ��,� ��)%"��,"(' �� ))%"��,"(' ,( *�)%"��,� ��,�

�"�,"('�*0 �!�' �+ ,( .(*$+,�,"('+� �� ,!� �� +��,"(' "' ,!�

��

� �+� ,!� ��,�! *�)%"��,"(' &�,!(� ,( *�)%"��,� ��,� �"�,"('�*0 �!�' �+ ,(

(,!�* +�*-�*+�

Package Management

4–8 B73.3.1 (6/99)

B73.3.1 (6/99) 4–9

Understanding Files Created by the Build Process

For information about the files created by the build process, see the following:

� � !�"#�#� � $��

� � �� !%�! $��

� �� &" � ��!%�! $��

� �� !%�! $��

Workstation Build

Where Business Functions Are Stored

Business function dynamic linked libraries (DLLs) on workstations are grouped byrelated business functions. This grouping limits the size and number of procedurescontained in each DLL. It prevents memory allocation problems and avoidsplatform-specific limits of exported procedures per DLL.

Beneath the environment PRODB733 directory is the bin32 directory. This directorycontains the DLLs that are created on the workstation. All of the business functionsource files are in the PRODB733/source directory.

Files Created by a Business Function Build

When you build a single business function through the Object Librarian, the BusinessFunction Builder program (Busbuild.exe) is used.

The Business Function Builder program uses the make (*.mak) file that you provide,builds the business functions into their respective DLLs, and creates the following files:

� � $!��

� ��! ��

� ��# ��

When calling a business function from a business function, you must use thejdecallobject API to do so.

Package Management

4–10 B73.3.1 (6/99)

See Creating and Specifying a Custom DLL in the OneWorld Development Tools Guidefor details about how to build business functions into the custom DLL.

Files Created by a Business Function Event Rule Build

Business function event rules create the following files:

� ��

� ��

� ��

Files Created by a Table Event Rule Build

Table event rules create the following files:

� ��

� �� $$

� ��

UNIX Server Build


When building business functions, the following groups of source files are actuallycompiled:

� �" �� "��!�� #��! �"��

� �� #��! �"��

� � �" �� "��!�� #��! �"��

When building business functions, the following file types are supplied to the buildprocess:

� ��"��

� �� $$�

When building business functions, the build process creates the following file types:

� ��! ��

� ��

� ��


B73.3.1 (6/99) 4–11

Business function shared libraries (equivalent to a Windows NT workstation’s DLLs)are consolidated. Therefore, one shared library is created for each parent DLL found inthe Object Librarian Detail file (F9861). If you are creating custom business functions,make sure you use a custom parent DLL instead of one of J.D. Edwards’ parent DLLs.


Business function shared libraries on UNIX platforms are grouped by related businessfunctions. This grouping limits the size and number of procedures contained in eachshared library. It prevents memory allocation problems and avoids platform-specificlimits of exported procedures per shared library. Beneath the environment PRODB733directory is a source directory. This source directory contains subdirectories for eachshared library that is created on the enterprise server. The directory structure looks likethe following:

PRODB733 source CAEC CALLBSFN CCORE CDESIGN CDIST CFIN CHRM CMFG JDBTRIG

Beneath each directory are all the business function source files belonging to the sharedlibrary. All shared libraries are installed in the PRODB733/bin32 directory, and havethe same name as the shared library subdirectories with a prefix of lib and a suffix of .sl(HPUX) or .so (AIX).

Specification Files

Specification files must be consolidated into individual files before being transferred toa UNIX server for translation. A specification file is a collection of two files, groupedby the same prefix (RDATEXT for example). The two suffixes, which comprise acomplete specification file, are .ddb (the data file) and .xdb (the index file).

Package Management

4–12 B73.3.1 (6/99)

Windows NT Server Build



� � �� !��

� �� !��

� � � �� !��


� � ��

� �� ""�


� ��

� ��

� ��

Business function DLLs are consolidated as they are on the UNIX platform orworkstation. Therefore, one shared library is created for each parent DLL found in theObject Librarian Detail file (F9861). If you are creating custom business functions,make sure you use a custom parent DLL instead of one of J.D. Edwards’ parentDLLs.


Business function DLLs on Windows NT platforms are grouped by related businessfunctions. This grouping limits the size and number of procedures contained in eachDLL. It prevents memory allocation problems and avoids platform-specific limits ofexported procedures per DLL.

Beneath the environment PRODB733 directory is a source directory. This sourcedirectory contains subdirectories for each DLL that is created on the enterprise server.


B73.3.1 (6/99) 4–13

The directory structure looks like the following:

PRODB733 source CAEC CALLBSFN CCORE CDESIGN CDIST CFIN CHRM CMFG JDBTRIG

Beneath each directory are all of the business function source files belonging to theDLL. All DLLs are installed in the PRODB733\bin32 directory, and have the samename as the DLL subdirectories with the .dll suffix.

Specification Files

Specification files must be consolidated into individual files before being transferred toa Windows NT server for translation. A specification file is a collection of two files,grouped by the same prefix (such as RDATEXT, for example). The two suffixes, whichcomprise a complete specification file, are .ddb (the data file) and .xdb (the index file).

AS/400 Server Build



� ��

� ��

� � ��


� ��

� ��

Package Management

4–14 B73.3.1 (6/99)


� ��!�� #��

� �� #��

� ��"�� #��

Business function service programs (equivalent to a Windows NT workstation’s DLLs)are consolidated. Therefore, one service program is created for each parent DLL foundin the Object Librarian Detail file (F9861). If you are creating custom businessfunctions, make sure you use a custom parent DLL instead of one of J.D. Edwards’parent DLLs.

Where Business Function Source Members Are Stored

Shared libraries on AS/400 platforms are grouped into service programs of relatedbusiness functions. This grouping limits the size and number of procedures containedin each service program. It prevents memory allocation problems and avoidsplatform-specific limits of exported procedures per service program.

Beneath the environment PRODB733 directory are three groups of files: the serviceprogram file, the H file for include files, and the HXX file for event rule header files.The PRODB733 library should have the following files:

PRODB733 CAEC CALLBSFN CCORE CDESIGN CDIST CFIN CHRM CMFG H HXX JDBTRIG

Included in the PRODB733 library but not listed above are the modules for all businessfunctions.

Beneath each service program file are the business function source members. Allservice programs are installed in the PRODB733 library, and have the same name asthe service program files above, with a type of *SVRPGM.

Specification Files

Specification files must be consolidated into individual files before being transferred toan AS400 server for translation. A specification file is a collection of two files groupedby the same prefix (RDATEXT for example). The two suffixes, which comprise acomplete specification file, are .ddb (the data file) and .xdb (the index file).

B73.3.1 (6/99) 4–15

Correlating Replicated and Central Objects

The following table shows the correlation between replicated objects stored inspecification tables and central objects stored in a relational database that has a binarylarge object (BLOB).

Replicated Object Central Object and Description

DDTABL F98710, Table Header. One record for each table.

DDCLMN F98711, Table Columns. One record for each column in a table.

DDPKEYH F98712, Primary Index Header. One record for each tableindex.

DDPKEYD F98713, Primary Index Detail. One record for each column inan index.

BOBSPEC F98720, Business View Specifications. One record for eachbusiness view.

GBRLINK F98740, Event Rules Link. One record for each event that hasevent rules for applications, reports, or tables (Named EventRule links are stored in the Business Function F9862).

GBRSPEC F98741, Event Rules Specifications. One record for each lineof event rules.

DSTMPL F98743, Data Structure Templates. One record for eachbusiness function, processing option, form interconnection,report interconnection data structures.

FDATEXT F98750, Form Design Aid text. Override text for applications.

FDASPEC F98751, Form Design Aid Specifications. One record for everycolumn, grid line, button, hyperitem, control, and so on, in theapplication.

ASVRHDR F98752, FDA/SVR Header Information. One record for eachapplication (if the application has processing options, thatinformation is also stored in the record).

Package Management

4–16 B73.3.1 (6/99)

Replicated Object Central Object and Description

ASVRDTL F98753, FDA/SVR Detail Information. One record for eachform (includes references to the data structures).

RDATEXT F98760, Report Design Aid Text. Override text for batchreports.

RDASPEC F98761, Report Design Aid Specifications. One record for eachsection, column, sort, constant, and so on, in Batch Reports andVersions.

JDEBLC F98762, Business Function Source Information. One record foreach function in BSFN.

CGTYPE Stored in specification format only. Code Generator FormTypes.

DDDICT: One record foreach Data Dictionary itemthat has been just-in-timeinstalled

DDINDEX: obsolete inB73.2 – indexes fordictionary

DDTEXT: Data Dictionarytext

� ��

� �� " ��!

� ��

� �� " ��

� ��

NEXTID F98701, Next IDs Table. Local record of next IDs assigned toeach workstation.

GLBLTBL Cache Information From Data Dictionary and TableSpecifications. Runtime table and override information. Builtdynamically the first time a table is used.

SMRTTMPL Data structure required field information.

B73.3.1 (6/99) 4–17

Performing Backups and Restoring Objects

You can back up development objects on workstations and servers as frequently as youneed. This does not apply to business data.

J.D. Edwards recommends the following:

� 0 '*+ , �*,&-.�.$*) ��&/+-� 0 '*+ ,- �. �� 1�,�- �* )*. ��&

/+ .# $, �) �*,'� �$, �.*,3 .* .# - ,0 , � ��/- *! - ,0 ,5-+��

�*)� ,)-� �)-. �� .# 3 �# �& $) .# *�% �.- .# 3 �, 1*,&$)" *) 0 ,3

$"#. #*/,-� *, #*1 0 , *!. ) ) � � .* �0*$� , 1*,&�

Unless you have unlimited disk space on a file server to allow developers toback up their entire path code directory, you must use the check-in process asyour backup method. If you follow the recommended development process,developers will know that they are allowed to check in unfinished or brokenapplications into the DEV path code.

� �)� �- , �*,&-.�.$*) ��&/+-� �)� /- ,- -#*/'� )*. #�0 )*), +'$��. �

��.� *) .# $, (��#$) - 2� +. �.*, �)� �*,1�,� .,�)-��.$*)- .#�. #�0

)*. 3 . � ) /+'*�� .* .# .,�)-��.$*) .��' -� �*/ -#*/'� -.��'$-# �

+*'$�3 .#�. �'' �.*, �)� �*,1�,� /- ,- (/-. /+'*�� .# $, .,�)-��.$*)-

� !*, .# 3 ' �0 !*, .# ��3� �! .# 3 ��))*. �* -*� 3*/ -#*/'� #�0 �

+,*� �/, 1# , .# 3 ��& /+ .# $, '*��' ��.��- .* � !$' - ,0 , 1$.#

.# $, )�( �- � -/��$, �.*,3�

� 0 '*+( ). � ,0 , ��&/+-� �. �� 1�,�-� */, �� +�,.( ). ��&-

/+ �*.# */, � 0 '*+( ). !$' - ,0 , �)*,(�''3 3*/, � +'*3( ). - ,0 ,�

�)� ) � --�,3 ��.��- - �� ).,�' *�% �.-� ��% �. �$�,�,$�)� �)� ��.�

�$�.$*)�,3�� # ) -*( *) ) �- .* , -.*, � +�,.$�/'�, *�% �. !,*(

��&/+-� */, ��.��- ��($)$-.,�.*,- , -.*, .# 2+*,. .* � +�.# �*�

��'' � 4� -.*, �� 0 '*+ , 1*/'� .# ) �# �& .# *�% �. */. !,*(

� -.*, � )-/, .#�. .# *�% �.- �, �- 2+ �. �� )� �# �& $).* .#

)*,(�' � 0 '*+( ). +�.# �*� �

� +'*3( ). � ,0 , ��&/+-� �# ).$, - ,0 , �* - )*. ) � .* �

��& � /+ )$"#.'3� �# *)'3 �$, �.*,$ - .#�. ($"#. �#�)" *) � ��$'3 ��-$-

�, �

� �# �� +�.# �*� $! 3*/ �, (*�$!3$)" *�% �.-� �/$'�$)" ) 1

+��&�" - *, /+��.$)" .# �� -- ��.��- � '$0 , � �/,$)" �

1*,&-.�.$*) $)-.�''�.$*)�

� �� $! 3*/ �, (*�$!3$)" # '+ !$' -�

� �� $! 3*/, ( �$� *�% �.- �, , -$�$)" *) .# � +'*3( ).

- ,0 ,� �) �*,'� ��.� -*/,� - $) �,��' *, �� ,0 , -#*/'� �

Package Management

4–18 B73.3.1 (6/99)

�� ($ "��' , �� ,#(% &,&'�! ��'� #% �", #'��% �!$#%'�"' ��'� �&

&'#%�� #" '�� $ #,!�"' &�%)�%�

� �"'�%$%�&� ��%)�% ��($&�

� �#( &�#( � �� ($ �� "��' ,� �� *�%�& %��#!!�"�& (&�"�

'�� ($ '## $%#)�� , '�� )�"�#%�

� �� ($ �"��#% � #��'& �, ��"� ($ '�� "'�%� �"��#% �

��%��'#%,� #*�)�%� ,#( �# "#' "�� '# �� ($ �", ��%��'#%��&

#'��% '��" '�� "� �� $�'� �#��& �"� '�� '�

�#��& �%� ($��'�� , '�� %&�#" �#"'%# ��!�"�&'%�'#% *��"

��$ #,�"� �" #��' !#�� , ��)� #$�%& *�# �%� �('�#%�-�� '#

��&& '�� %)�% �� $$ ��'�#"� �"� �, �"� (&�%& *�# �%��'�

"�* ��'�� )�%&�#"& '# �� +��('�� #" '�� &�%)�%�

For more information about backing up and restoring, see the Server and WorkstationAdministration Guide.

B73.3.1 (6/99) 4–19

Transferring Objects

The Object Transfer application enables OneWorld administrators to transfer objectsjust as the Object Librarian does. However, Object Transfer transfers objects from thecentral objects for one path code to the central objects for another path code, whereasthe Object Librarian transfers objects from the workstation to the central objectslocation, and vice versa.

Any time you create or change a batch report or template, you should use ObjectTransfer to transfer both the report and version. This transfer will copy the report andversion specifications as well as the version data (F986051 record) and the processingoption text (F98306). If you change the processing option template (T986110), youmust transfer that object separately. This will copy the specification as well as the textfrom F98306.

If you modify an interactive application and do not change the processing optiontemplate (T0004A), you need to transfer only the application. If you change theprocessing option template you must transfer that object separately and transfer allcorresponding versions. If you change only processing option values (data stored inF983051), you must transfer the version but do not need to transfer the application orthe processing option template.

When you transfer an application or version, user overrides are automaticallytransferred for *PUBLIC and all groups. (No individual user override records will betransferred.)

If you transfer an application, only its override records will be transferred, not itsversions. Conversely, when you transfer an application’s version, its override recordsare not transferred.

Before You Begin

� �� !� �� " �� " �� $�� !��! �� "!��!% !�

�� !�� #�� !�� !��! ��!�� !�� !� �"��

!�� ! �� $�� !� !�� "�� !��!�� !��

��! � �� #��! %�" �� !� �" ! ��#� � ��!� �"�� !��!

��!�� "��

Package Management

4–20 B73.3.1 (6/99)

To transfer objects

From the Object Management menu (GH9081)

1. Choose Object Transfer (P98604).

2. On the Work With Object Transfer form, find the records you want to transfer.

3. Enter the location path code the objects are transferred to in the Destination PathCode field at the bottom of the form.

Do not perform a transfer unless the objects in the grid of the Work With ObjectTransfer form exactly match the objects listed on the Members Affected form (Crecord) of the SAR. Or if you use your own tracking system, ensure that you aretransferring the correct objects. Research any discrepancies with the applicationdeveloper.

4. Choose the records you want to transfer, and choose Transfer from the Rowmenu.

Next, transfer versions, if applicable. Always transfer batch applications with atleast one version. Interactive applications do not always have processingoptions, and therefore do not always have versions. Before you can transferversions, the batch or interactive application object (the report) must alreadyexist in the destination central object location.

5. To transfer versions, choose an object, and choose Versions List from the Rowmenu.


B73.3.1 (6/99) 4–21

6. On the Work With Versions form, choose the version to transfer, enterinformation into the Destination Path Code field, and click Select.

Only the transfer of applications displays “Complete” in the status bar. All otherobjects are no longer highlighted after the transfer is complete.

7. When finished transferring versions, click Close.

Verifying the Transfer

The object transfer process is extremely reliable because Object Transfer uses the samecode as Object Librarian check in/out. The reasons that an object does not transfercorrectly include the following:

� �!� .,�+ )�+�(+&"' -!� -+�',��+ �(�, '(- !�/� �.-!(+"-2 -( -!� -�+ �- )�-!

�(��

� �!� .,�+ �(�, '(- -+�',��+ � '�� (�#��-

� �!� '�-0(+$ �(''��-"(' !�, ��' %(,- �'� '��, -( �� +��,-��%",!�� 2

%( "' ��$ "'-( �"'�(0,

Use one or more of these methods to verify that the transfer went as planned:

� ��"'*."+� �'� /�+"�2 -!� ��-� �(�"�"�� "�%� (� -!� ��,-"'�-"(' +��(+�

� ��/"�0 -!� !��$ �.- �( � �' -!� ��#��- ��'� �&�'- &�'. ��

�!((,� !��$(.- �( ��

� �(+ (�#��-, -!�- �+� '(- ,-(+�� "' -!� ��'-+�% (�#��-, ��-� ,(.+�� 2(. ��'

.,� �"�+(,(�- �1)%(+�+ -( �!��$ -!� ��-��-"&� (� -!� (�#��- "' -!�

Package Management

4–22 B73.3.1 (6/99)

" ��!�� &"� ��"�� !� ��"! � ��

�� "��

� ��" �� !��%! �� " "�� #!� �� "�� #!� $��

#��"�� "�� " �� "�� "� "�� #!� #��"�� "�� "�

� �� #" "�� " � �� "�� " ��!�� "� ��"��

� ��$ "�� "� ��!# � "��" "�� ! �#� "� ��

!�� #"�� "%� ��# �#!" �� "��! �� "��% ��#!� ��

�� !��! "��! �� "�� %�# !�� "� "�� !%!"��

Field Explanation

Status Code This code determines the status of the software in thedevelopment cycle.

Name The name of a unit which consists of attributes and sometimesdata. The name of anything that exists in and occupies space instorage, and on which operations can be performed.

Description The description of a record in the Software VersionsRepository file. The member description is consistent with thebase member description.

Location For World, the Location indicates the machine (server orclient).

For OneWorld, the Location or Machine Key indicates thename of the machine on the network (server or workstation).

Path Code The Path Code is a pointer to a set of OneWorld objects, and isused to keep track of sets of objects and their locations withinOneWorld.

SAR An abbreviation for Software Action Request (SAR). Thisnumber is used by the J.D. Edwards project control system tokeep track of all charges and activity by individual SARnumber.

User For World, the IBM-defined user profile.

For OneWorld, the identification code for a user profile.

Date Modified The date that the object, such as a DREAM Writer version,Software Versions Repository Record, and so on, was lastmodified.

Object Type The type of object with which you are working. For example, ifyou are working with tables the object type is TBLE, orbusiness functions is BSFN.

Destination Path Code The Path Code is a pointer to a set of OneWorld objects, and isused to keep track of sets of objects and their locations withinOneWorld.


B73.3.1 (6/99) 4–23

Field Explanation

Program ID The name of the OneWorld batch or interactive application(interactive or batch object). For example, the name of theSales Order Processing interactive application is P4210, andthe name of the Print Invoices batch process report is R42565.

The name of the program ID is a variable length value. Thisvalue is assigned according to a structured syntax in the formTSSXXX where:

T The first alphabetic character of the program nameidentifies the type such as P for Program, R forReport, and so on. For example, the value ’P’ in thename P4210 indicates that this is a program.

SS The second and third numeric characters of theprogram name identifies the system code. Forexample, the value ’42’ in the name P4210 indicatesthat this program belongs to System 42, which is theSales Order Processing system.

XXX The remaining numeric characters of the programname identify a unique program or report. Forexample, the value ’10’ in the name P4210 indicatesthat this is the Order Entry application.

Version A version is a user-defined set of specifications. Thesespecifications control how applications and reports run. Youuse versions to group and save a set of user-defined processingoption values and data selection and sequencing options.Interactive versions are associated with applications (usually asa menu selection). Batch versions are associated with batchjobs or reports. To run a batch process, you must choose aversion.

Version Title A description of the version that appears next to the versionnumber. The version title is different from the report title.

This field should describe the use of a version. For example, anapplication for generating pick slips might have a versioncalled Pick Slips - Accounting and another version called PickSlips - Inventory Management.

Server Specs OneWorld: This field indicates the availability of a batchversion.

Y Version is available for installation from the server.N Version is not available for installation from the

server.

Version List Mode OneWorld: This identifies the type of application. Valid valuesare:

1 interactive2 batch

Package Management

4–24 B73.3.1 (6/99)

Field Explanation

Prompt Options This code specifies how processing options will be executedbased on user defined code table 98/CR. Valid values are:

Blank Disables the processing options for the version.1 The application will use existing processing option

without prompting the user. This is sometimesreferred to as blind execution.

2 The application will prompt the user for processingoptions at runtime.

Last Change Indicates the last time an application or version was modifiedby the specified user.

Server Update This is the date the application or version was checked in to theserver.

Report ID The unique numeric value that identifies the batch orinteractive application. Typically, this is useful for OneWorlddevelopers or customer support.

Version ID For batch report versions, the unique numeric value that thesystem assigns to identify the version.

For interactive versions, this value is 0.

Processing Option GroupIdentifier

For World, the processing option group identifier uniquelyindentifies the processing option group for client based menus.

For OneWorld, this number identifies the processing optiondata associated with a version.

In Devl Indicates the availability of a version for checkout. Only oneuser may have the version checked out.

Y Version is currently checked out.N Version is not currently checked out.

Last Modified Identifies the user ID of the user who last modified theapplication or version.

Owner For World, the IBM-defined user profile.


B73.3.1 (6/99) 4–25

Managing Objects with the SAR System

You can manage change control any way you want. At J.D. Edwards, we use thesoftware action request (SAR) system. Currently, the SAR system exists only in WorldSoftware; in the future it will be available in OneWorld.

Any numbering system will work for change control (you can even use a paper systemwith assigned numbers if you want), but we suggest you follow the steps below:

To manage objects with the SAR system

1. Create a SAR for each bug or enhancement.

Every object a developer checks in should have a SAR number associated withit. The Object Librarian [Application Design Aid] form shows the SAR number.

2. When you are ready, use Object Transfer to move objects to a production pathcode by SAR number. Use the Members Affected record type in the SAR torecord all objects that developers have modified.

3. Print each SAR, saving them in a folder, and turn in the SAR folder to theversion control person.

Package Management

4–26 B73.3.1 (6/99)

When transferring objects, version control compares the objects that come up onObject Transfer by SAR number to the objects listed in the Members Affectedrecord of the SAR. The transfer form must indicate which path code the objectswill be transferred from and transferred to. For more information abouttransferring objects, see � �� .

B73.3.1 (6/99) 4–27

Copying Records Between Data Sources

You can use the Record Copy application to copy control table records from one datasource to another. For example, you might maintain a separate set of UDCs, menu, orData Dictionary for your production and CRP environments. Each change you make tothe CRP environment that you also want made to the production environment can becopied through this application.

The Processing Option Copy section is for J. D. Edwards internal use only and shouldnot be used, because all processing options are moved from one environment to anotherthrough the Object Transfer application.

The Data Dictionary Copy section should not be used, because J.D. Edwards stronglyrecommends that you maintain only one Data Dictionary. However, if you do have aseparate Data Dictionary for your development and production path codes, you shoulduse this to copy items from development into production.

This task explains how to copy control table records from one data source to anotherdata source. You can copy the following control table records:

� ��

� � ��

� ��

To copy records between data sources

From the Object Management menu (GH9081)

1. Choose Record Copy (P9864).

Package Management

4–28 B73.3.1 (6/99)

2. On the Record Copy Utility form, complete the following fields:

� �� %��"

� �" � ��$� � %"��

� � ��$� � %"��

3. Complete the following fields depending upon what you want to copy, and thenclick OK:

� �" ��##�� !$� � ��%�# �� "#$'�� "#� � �"��#��" ��#�

� �" �"��

� ��"#� �

� �#�" �� # �� !&� ��#�

� �&#$��

� ��

� ��%��

� ��$� ��$� ��"& � !& ��

� ��$� $��

� ��% � ��% � !&� ��

� ��% �

� ��$ ��"�"�� !&� ��

� ��$ ��"�"��

Enter the Processing Option Values and First Time Version Transfer fields onlyif you want to copy the processing option values for a version from one data

Copying Records Between Data Sources

B73.3.1 (6/99) 4–29

source to another, or if you need to copy a version record to a data source for thefirst time.

4. Click Cancel when you have finished copying.

Field Explanation

SAR Number An abbreviation for Software Action Request (SAR). Thisnumber is used by the J.D. Edwards project control system tokeep track of all charges and activity by individual SARnumber.

From Data Source The data source name.

To Data Source OneWorld uses this data source if the primary data source orthe data item in the primary data source cannot be located.

Program The name of the OneWorld batch or interactive application(interactive or batch object). For example, the name of theSales Order Processing interactive application is P4210, andthe name of the Print Invoices batch process report is R42565.

The name of the program ID is a variable length value. Thisvalue is assigned according to a structured syntax in the formTSSXXX where:

T The first alphabetic character of the program nameidentifies the type such as P for Program, R forReport, and so on. For example, the value ’P’ in thename P4210 indicates that this is a program.

SS The second and third numeric characters of theprogram name identifies the system code. Forexample, the value ’42’ in the name P4210 indicatesthat this program belongs to System 42, which is theSales Order Processing system.

XXX The remaining numeric characters of the programname identify a unique program or report. Forexample, the value ’10’ in the name P4210 indicatesthat this is the Order Entry application.

Version Identifies a specific set of data selection and sequencingsettings for the application. Versions may be named using anycombination of alpha and numeric characters. Versions thatbegin with ‘XJDE’ or ‘ZJDE’ are set up by J.D. Edwards.

System A user defined code (98/SY) that identifies a J.D. Edwardssystem.

UDC A code that identifies the table that contains user definedcodes. The table is also referred to as a code type.

Language A user defined code (01/LP) that specifies a language to use informs and printed reports.

Before any translations can become effective, a language codemust exist at either the system level or in your user preferences.

Package Management

4–30 B73.3.1 (6/99)

Field Explanation

Menu ID The menu name, which can include up to nine characters. J.D.Edwards standards are:

� ��!' !' ��$% �$� #$�� )�&� � � #$��*�

� �� &)" ��$��&�$% �"��")�!� &�� #$��* �$� &��

%+%&� �"��

� �� !�*& ��$��&�$% �'$&��$ ��!&��+ &�� !'�

� �� &� ��$��&�$ %#��% � %#�� %�� (��

� �� &� ��$��&�$ ��%&�!�'�%��% &)" �!'% "� &��

%� � %+%&� )�&� &�� %� � %�� (��

For example, the menu identification G0911 specifies thefollowing:

G Prefix09 System code1 Display level/skill level1 First menu

Object Librarian The OneWorld architecture is object-based. This means thatdiscrete software objects are the building blocks for allapplications, and that developers can reuse the objects inmultiple applications. Each object is stored in the ObjectLibrarian. Examples of OneWorld objects include:

� ��&�� ##��&�"!% �%'�� % $�#"$&%�

� !&�$��&�(� �##��&�"!%

� �'%�!�%% ��)%

� �'%�!�%% �'!�&�"!%

� �'%�!�%% �'!�&�"!% �&� �&$'�&'$�%

� (�!& �'��%

� �� & �&� �&$'�&'$�%

Package Build

Package Management

4–32 B73.3.1 (6/99)

B73.3.1 (6/99) 5–1

Package Build

As OneWorld applications, business functions and other objects change, you will needa means of making the changes available to users within your enterprise. You may alsoneed to set up a new workstation with OneWorld software.

Packages allow you to deploy software changes and new applications to your users, orto install OneWorld on a workstation for the first time. After you have defined and builta package, you can deploy it using the Client Workstation Installation or PackageDeployment applications.

This section contains the following:

� �� !��

� ��

� ��

� ��

� �� ! ��

� ��

Package Management

5–2 B73.3.1 (6/99)

B73.3.1 (6/99) 5–3

Understanding Packages and Deployment

There are several instances in which you will need to update or set up a workstation oran enterprise, logic, or application server with OneWorld software. Following are someof the more common reasons:

� � "�� "�� " ��

��

� � �� $ � �� $ ��

� � ��!� �� " �� !�� $�

�� $ ��

� � �� $ ��$ � ��"�� # ��

��

� �� " �� $� � "�� $� ��

�� !��

�� "��

� � �� $� � ��!�� "�� $� �!�

��!��

J.D. Edwards provides solutions that can help you meet all of these needs. First,OneWorld provides the means to create a package describing where to find thenecessary components that need to be distributed to your workstations. In order todeploy these components, you must define and build a package.

To provide maximum flexibility, there are three different package types to choose from:full, partial, and update. Partial packages are available only for workstations. Thepackage type you choose depends on your needs.

After you have defined and built your package, it is ready for distribution. Dependingon the package type, you can deploy packages through the Client WorkstationInstallation or Package Deployment applications.

Package Deployment enables you to specify the workstations and servers that receivethe package, as well as when the package is made available. Packages can be deployedto all machines within the enterprise, a select group of machines, or individualmachines. If you wish, you can schedule a package to be “pushed” from thedeployment server to workstations. Push installation requires no interaction with theworkstation user.

Package Management

5–4 B73.3.1 (6/99)

This chapter contains the following topics:

� ��

� �� $��$ ��

� �� #��

� !��!��" �� #��

� �� #��

Understanding Full and Partial Workstation Configurations

Before you begin assembling and building packages, you should have an understandingof the two types of workstation configurations available in OneWorld: full and partial.These terms refer mainly to the amount of disk space the installed package takes on theworkstation. Having a good understanding of these two configurations will help youdetermine the suitable package type (full, partial, or update) for the workstations inyour enterprise.

A full workstation configuration requires a larger amount of disk space, and installationtimes can be longer. A typical full workstation installation takes more than 1.4 GB ofdisk space and can take 10 to 30 minutes to install, depending on network traffic.

A partial workstation configuration represents a minimum configuration of OneWorldand requires significantly less disk space compared to a full workstation. InitialOneWorld installation times are also dramatically faster for a partial workstation. Atypical partial workstation takes around 165 MB of disk space and takes 3 to 10minutes to install, again depending on network traffic. However, because OneWorldadds applications to the minimum configuration as the user needs them, users withWAN access may find that performance for a partial workstation is unacceptably slow.

The main difference between the full and partial workstation configurations is theamount of specifications resident on the workstation. A full workstation contains thefull suite of OneWorld applications, including those you rarely or never use. Thebenefit of a full workstation is that all applications are available immediately. Thedisadvantage is the disk space it requires on a workstation.

J.D. Edwards recommends that production users use partial workstations, becausepartial packages are much easier to administer and maintain. Production users shoulduse full workstations only if just-in-time installation performance is unacceptable onyour network’s configuration.

J.D. Edwards recommends that development users use full workstations, because fullpackages contain development objects not found in partial packages.


B73.3.1 (6/99) 5–5

There are advantages to both full and partial workstation configurations, and you mustevaluate your needs before determining which is best for your enterprise. Thefollowing summarizes the benefits and disadvantages of full and partial workstationconfigurations:

Full Workstation Advantages:

� ��$��" #�� $�� "$�#� �� !�� #��"

�� "��#��" �� $��#��"�� %��!" ��%�

�� "" #� �� !�� #"�

� ��#�! ��#�� # &�!�"#�#�� "#��#�� #&�!�

#!�� " ��&�! #�� &�#� � ��!#�� &�!�"#�#��

��$!�#�� $"� �� #��" �!� ��"#�� #

��

Disadvantages:

� � $�!�" � ��!��! ��$�# �� "� "�� #��

&�!�"#�#��

� ��#�� "#��#�� #�� " �$�� ! ��!�� #� �

��!#�� &�!�"#�#�� $!�#��

Partial Workstation Advantages:

� � $�!�" �$�� "" ��"� "�� #�� &�!�"#�#��

��!�� #� � �$�� &�!�"#�#�� $!�#��

� ��#�� "#��#�� #��" �!� �$�� "#�! ��! � ��!#��

&�!�"#�#��

� ��' #��"� ��#" !� $�!�� #� �� $"�� !��

�!� ��'�� $!�� # &�!�"#�#�� "#��#��

�#��! ��#��" �!� ��%�!�� #�!�$�� $"#(��(#��

��"#��#�� &�� #�� $"�! ��!"# ��#�!" �� #��

Disadvantages:

� ��# ��!��"� �� #&�!� #!�� &�� !"#(#�� $"�!"

�� #��"�

� ��!��!�� ! �$"#(��(#�� "#��#�� %�! � ��

��# �� "��&�! #�� %�! � ��

� ��%��!" ��# $"� ��!#�� "� "��

��%��# ��#" �!� ��# ��%�!��

Package Management

5–6 B73.3.1 (6/99)

Understanding Just-in-Time Installation

A partial workstation doesn’t have any applications resident. Instead, applications areretrieved at runtime and loaded on the workstation the first time a user selects thatapplication from the OneWorld Explorer menu. Loading happens only once; the nexttime the user selects the same application, it will still be loaded on the workstation.

This process is called “just-in-time installation” (JITI). Applications are loaded themoment you need them rather than requiring them to be resident on your workstation.JITI applies only to applications; business functions cannot be installed through JITI.

JITI works both when there are no applications installed and when your workstationreceives a partial or update package that does not contain specifications. Update andpartial packages that contain specifications do not require the JITI process.

When you make a menu selection from OneWorld Explorer, the runtime engine checksto see if application specifications reside on your workstation. If local specifications donot exist (and the Environment Master just-in-time installation flag is set to Y, and yoursecurity profile allows the application to be installed), the specifications are transferredfrom the central objects data source for the path code associated with yourenvironment. In this way, needed applications are installed “just-in-time” rather thanwhen the user receives the package or at initial installation time.

The process for an update package works almost the same way. When you receive anupdate package that contains a changed application without the new specifications,OneWorld first checks to see if that application’s specifications are resident on yourworkstation. If so, it deletes from your workstation old versions of that application.Then, the next time you select that application from the OneWorld Explorer menu,OneWorld loads the new version of that application.

When a package includes applications without specifications, at the time of executiononly the following related objects are deployed:

� ��

� ��

� ��

The following objects are not deployed, and therefore must be included in the packageif they have been modified:

� ��

� ��

� ��


B73.3.1 (6/99) 5–7

� ��

� ��

Understanding Package Types

After you determine whether you want to have a full or partial workstationconfiguration, you can build the following types of packages:

� ��

� ��

� ��

Full Packages

Full packages are static, point-in-time snapshots of the central objects for the path codethe package is based on. A full package contains everything developers need to run anddevelop in OneWorld. Specifically, this includes a full set of TAM specification files, afull set of DLLs, all of the .c and .h files for business functions and tables, and an INFfile that defines where the foundation, data, helps, and packages are located. Select thispackage type when you want to create a full workstation configuration.

The main advantage of a full package is that users have every OneWorld applicationavailable for which they are licensed. Also, because specifications are resident on theworkstation, network traffic is lower compared to a machine with a partial packageinstalled. This is because a full package does not require the just-in-time installationprocess. Some specifications and tables may still be installed just-in-time when youdeploy a full package, but the impact on network performance is insignificant.

Full packages are primarily for initial OneWorld installations and are normallydeployed via the Client Workstation Installation application. You can also use PackageDeployment to install a full package on a machine that already has OneWorld installed.

Full packages can also include development objects such as business function sourcefiles, object files, and header files). A user who needs to load development objects willbe given the option to do so at deployment time.

Partial Packages

This package type is a minimum configuration of OneWorld. Use this package typewhen you want to create a partial workstation configuration. A partial packageessentially contains only the specifications that allow users to launch OneWorldExplorer. Specifically, a partial package starts with an empty set of TAM files, and thenadds the specifications for the objects that are included in the package. Also included ina partial package are a full set of DLLs and an INF file that defines where thefoundation, data, help files, and package objects are located.

Package Management

5–8 B73.3.1 (6/99)

Applications are loaded through just-in-time installation the first time the user selectsan application from the OneWorld Explorer menu. That is, the selected application isloaded from the central objects data source for that path code.

Like full packages, partial packages are primarily for initial OneWorld installations andare normally deployed via the Client Workstation Installation application, although youcan use Package Deployment to install a partial package on a machine that already hasOneWorld installed.

Update Packages

An update package enables you to update, add to, or refresh an existing full or partialpackage with changed objects such as a database, application objects, a foundation, orhelp files. This package type is well-suited for quickly deploying software changes andfixes.

Unless a package includes applications that do not have specifications, the updatepackage is a point-in-time copy of your central objects for a particular path code. If theupdate package contains an application without specifications, only that application isdynamic; the rest of the package is static. Dynamic means the applications are pulleddirectly from the central objects data source at the moment the application is firstselected.

When a user receives an update package, OneWorld loads on the user’s workstation allobjects in the package after the user signs on. The objects in an update package replacethose same objects on the workstation. All other objects on the workstation are leftuntouched.

If an application in the package doesn’t pertain to a particular user, that application canbe secured through Security Workbench, which checks to determine if the user haspermission to install an application. Only users authorized to load the application areable to do so. Therefore, your update package can contain a varying assortment ofapplications going out to several diverse users or groups, but only the authorized usersor groups can receive the applications that apply to them.

Like full packages, update packages can include development objects such as businessfunction source files, object files, and header files. Update package recipients will begiven the option to load development objects at deployment time.

Keeping in mind how just-in-time installation works, performance across a WAN maybe slow if the partial or update package contains only applications withoutspecifications. Users on a WAN may find that performance is better if they include anapplication’s specifications in the package.

All update packages require a corresponding “parent package” on which the updatepackage is based. The parent package is a full package that subsequent update packagesupdate. All objects in the update package are merged into the parent package.


B73.3.1 (6/99) 5–9

Business function objects in the update package are linked to the corresponding parentpackage’s objects, and new DLLs are created. Similarly, specifications from the updatepackage are merged into the parent package’s specifications.

The parent package concept applies to both workstations and servers. Parent packagesfor workstations are kept on the deployment server, while server parent packages arekept in the enterprise server’s build area.

Overview of Creating and Deploying a Package

The following is an overview of the steps involved in creating and deploying apackage:

1. Assemble the package.

The initial step involves specifying the type of package you are building andproviding a name, path code, and package description. Next, you assemble yourpackage by specifying the objects you want to include in the package. If you arebuilding a partial or update package, you can specify individual objects toinclude.

The process of assembling the package is simplified by the Package AssemblyDirector, which displays a series of forms that guide you through the steps ofnaming your package and assembling the objects you want to include in thepackage.

See �� in this section for details on how to assemble apackage.

2. Define the package build.

After you assemble the package, you must define the build before you candeploy the package to your workstations and servers. In this step you specifybuild options, business functions build options, and compression options. Youalso need to specify whether the package is for a workstation, server, or both. Ifthe package is for servers, you must specify which servers should receive thepackage.

Again, to simplify the build process, the Package Build Director displays a seriesof forms that guide you through the steps of specifying where to build thepackage, whether to include specifications, whether to compress or buildbusiness functions, and so on.

See �� in this section for information on how to define apackage build.

Package Management

5–10 B73.3.1 (6/99)

3. Build the package.

During the actual build process, OneWorld takes the information you providedwhen you assembled and defined the package, and copies and converts centralobjects to the package. It also performs a global build of the business functionsincluded in the package, and then compresses the package.

4. Schedule the package for deployment to workstations.

If you build an update package (or if you want to redeploy a full or partialpackage to a workstation that already has OneWorld), you must specify the dateand time to deploy the package. When you schedule the package you can makepackage installation mandatory or optional.

At this same time you can specify whether you want the package to be deployedvia push installation, which requires no interaction with the package recipient.

See �� for information on how to schedule a package. Forinformation on push installation, see �� .

5. Deploy the package to deployment and enterprise servers.

Use Package Deployment to move any changed objects to the enterprise server.

If you specify a server during the package build definition process, OneWorldautomatically creates a corresponding server package in the correct format. Ifyou do not specify a server and define only a workstation package, you shouldcreate a corresponding server package. The process is nearly identical to creatinga workstation package.

See �� for information.

How OneWorld Builds a Full Package

1. Creates the package build directories

2. Creates the INF file

3. Copies the following directories and files from the check-in location to thepackage name directory:

� ��

� ��

� ��

� ��

� ��

� ��


B73.3.1 (6/99) 5–11

� ��

� ��

If you choose to build business functions with the package build, OneWorld doesnot copy bin32, lib32, and object (.obj) files, because the BusBuild programcreates them.

4. Builds the TAM specification files from the information in the relationaldatabase

5. Runs the BusBuild function to compile and link the business functions thatcreate the DLLs in the bin32 directory, the objects in the obj directory, and thelibraries in the lib32 directory

6. Compresses the directories

How OneWorld Builds a Partial Package



3. Builds an empty set of TAM specification files

4. Copies the following directories and files from the check-in location to thepackage name directory:

� ��

� ��

� ��

� ��

� ��

If you choose to build business functions with the package build, OneWorld doesnot copy bin32 and lib32 files, because the BusBuild program creates them.

5. Builds the specifications for the objects in the *LITE record

6. (Optional) Runs the BusBuild function to compile and link the businessfunctions that create the DLLs in the bin32 directory, the objects in the objdirectory, and the libraries in the lib32 directory.

7. (Optional) Compresses the directories

How OneWorld Builds an Update Package



3. For each object in the F9631 table, gets the information out of the relationaldatabase and add it to the TAM specification files

Package Management

5–12 B73.3.1 (6/99)

4. Builds the specifications for the objects in the *LITE record

5. Runs the BusBuild function to update the DLLs in the bin32 directory, theobjects in the obj directory, and the libraries in the lib32 directory

Considerations for Users of Sun Microsystems, Inc. Platforms

If you develop custom modifications on Sun servers that use the Solaris operatingsystem, there is one important step you might need to take before assembling, defining,and building packages that contain your modifications. This step ensures that thepackage build process completes successfully.

The Sun compiler expects a newline character at the end of every source code file itcompiles. If the compiler does not find this newline character, it rejects the line anddisplays a warning message. In some cases, this line rejection and message could causethe package build to fail.

To ensure that this does not happen, before you assemble the package that will containyour custom modifications, you must ensure that this newline character is present in thecompiled source code.

There are some cases where the newline character is automatically added, and you willnot need to take this extra step. If you edit source code in the UNIX environment usingan editor such as VI or emacs, these editors automatically add the newline character.Also, J.D. Edwards has added a process to ensure that the newline character is added toall business function source code files shipped with OneWorld.

However, if you edit source code on a PC workstation and then transfer the file to theserver for compiling, be aware that PC workstation editors typically do not add thenewline character. In this situation you should check your source code and verify thatthe newline character exists.

B73.3.1 (6/99) 5–13

Assembling Packages

The first step in building and deploying a package is to assemble the package, whichentails selecting the type of package you want to build, providing a package name anddetailed description, and assembling the objects you want to include in the package.This same package name and description appears during Workstation Installation whenthe user chooses a package to install.

This package assembly process is greatly simplified by the Package Assembly Director,which displays a series of forms that step you through the process.

During package assembly, the status will always be either In Definition or DefinitionComplete. Once package assembly definition is complete you can then define thepackage build as explained in �� .


� ��

� ��

� ��

� ��

� ��

� ��

Understanding the Package Assembly Director

The Package Assembly Director’s forms guide you through the process of specifying orconfirming the location where package components can be found, as well as indicatingthe objects to include in the package.

Throughout the package assembly process you always have the option of going to theprevious or next screen by clicking Previous or Next. Also, regardless of where you arein the process, you can always cancel the assembly process by clicking Cancel.

Package Management

5–14 B73.3.1 (6/99)

The following summarizes each of the Package Assembly Director’s forms and theirfunction:

Welcome form View this form for a description of the PackageAssembly Director.

Package Informationform

Use this form to enter the package name, description, andcorresponding path code.

Package Type Selectionform

Indicate on this form whether you are creating a full,partial, or update package.

When you create an update package, you must also indicate the“parent package” on which the update package is based. Forexample, if you are creating a package to update your originalpartial package called APPL_B, you would enter “APPL_B” asthe parent package for your update package.

You also have the option of including object specifications inan update or partial package. If you do not includespecifications, the application is installed via just-in-timeinstallation the first time you select that application. That is, theapplication specifications are pulled dynamically from thecentral objects data source the first time you select theapplication after receiving the package.

Foundation Componentform

Enter a foundation location on this form. A OneWorldfoundation is the code required to run all OneWorldapplications. It is required for all full and partialpackages. If you do not specify a foundation path for fulland partial packages, the default foundation path will beused. Update packages use the parent package’sfoundation unless one is specified.

Help Component form Enter a help location on this form. The help componentdetermines where the system looks for the help filesassociated with the package. For full and partialpackages, if you do not specify a helps location, thedefault help file path will be used. Update packages donot require helps.

Including a helps component in a package does not mean helpsare installed on a user’s workstation. The help component tellsOneWorld where to find the help files that are associated withthe package.

Assembling Packages

B73.3.1 (6/99) 5–15

Database Componentform

Specify on this form the location of the database that willbe included in the package. For full and partial packages,if you do not specify a database location, the defaultdatabase path will be used. Update packages do notrequire a database.

Default ObjectComponent form

(For full packages only.) Use this form to verify thedeployment data source. When you build a full package,the objects included in the package will be pulled fromthe deployment data source that is associated with thepath code you have specified for the package.

Object Component form (For partial and update packages only.) Specify on thisform the individual objects you want to include in thepackage. You can add any of the following objects:

� ��

Language Componentform

Use this form to include in your package languagespecifications for a language other than English, which isthe default language.

Package ComponentRevisions form

Review your selections or default values for theFoundation, Helps, Database, Objects, and Languageforms you entered previously. You can modify any or allof your selections from this form.

Accepting Default Values

Many of the Package Assembly Director’s forms have a default value and, after makingsure you want to use the displayed value, you can advance to the next form withoutentering anything.

Forms determine the default values based on the following:

� ��

��

� ��

��

� ��

��

Package Management

5–16 B73.3.1 (6/99)

� ��

��

� ��

On forms that have a default value, even if you change or clear the field you can alwaysrestore the original default value by clicking the Default button. The PackageComponent Revisions form also has a Set Default option accessible from the Formmenu that accomplishes the same thing.

If you are building a full or partial package and do not need to specify the objects inthat package, the fastest way to define the package is to accept the default locations forthe foundation, database, helps, and language. This method applies only to full andpartial packages. For an update package, if you accept the defaults but do not includeany objects, you will have an empty package.

As you view the forms displayed by the Package Assembly Director, you can acceptthe displayed default selections by clicking Next. If necessary, you can always makechanges at the final Package Component Revisions form.

Assembling a Package

The following task describes how to assemble a package using the Package AssemblyDirector.

To assemble a package

From the Package and Deployment Tools menu (GH9083)

1. Choose Package Assembly (P9601). The Work with Packages form appears.

Assembling Packages

B73.3.1 (6/99) 5–17

Any previously assembled packages will be displayed on this form. As on anyother parent/child form, you can expand or compress by clicking the plus (+) orminus (–) symbols to show more or less information.

For any previously assembled packages, underneath the package name you canview the package properties (including package type and current status,) as wellas the selections for foundation, database, help, and language.

2. To assemble a new package, click Add. The Package Assembly Directorlaunches.

Package Management

5–18 B73.3.1 (6/99)

3. From the Welcome screen, click Next. The Package Information form appears.

Complete the following fields:

� ��

� ��

� ��

4. Click Next. The Package Type Selection form appears.

Assembling Packages

B73.3.1 (6/99) 5–19


� ��

� ��

� ��

Be sure to click Include Object Specifications whenever you are assembling anupdate package that will go to one or more servers.

5. Click Next. The Foundation Component form appears.

Accept the displayed default location by clicking Next, or click Browse tospecify another foundation location. To clear the currently displayed location, ifany, click Clear. The Clear option applies only to update packages.

For more information about entering a foundation, see �� .

6. Click Next. The Help Component form appears.

Package Management

5–20 B73.3.1 (6/99)

Accept the displayed default location by clicking Next, or click Browse tospecify another help location. To clear the currently displayed location, if any,click Clear. The Clear option applies only to update packages.

For more information about entering a help location, see �� .

7. Click Next. The Database Component form appears.

Assembling Packages

B73.3.1 (6/99) 5–21

Accept the displayed default location by clicking Next, or click Browse tospecify another database location. To clear the currently displayed location, ifany, click Clear. The Clear option applies only to update packages.

For more information about entering a database location, see �� .

8. If you are assembling a partial or update package, skip this step and proceed tothe next step. Click Next. When you are assembling a full package, the DefaultObject Component form appears.

OneWorld will build your package from the deployment data source associatedwith the displayed default object path. Verify that the correct location isdisplayed. Since you are assembling a full package, skip the following step.

9. Click Next. When you are assembling a partial or update package, the ObjectComponent form appears. This form allows you to specify the individual objectsyou want to include in your package. When you revise a previously-assembledpackage, objects you added earlier are displayed.

Package Management

5–22 B73.3.1 (6/99)

To add an object, click Browse to display the Object Component Selection form.Use this form to locate and select the objects you want to include in yourpackage. When you are finished adding objects, click Close to return to theObject Component form.

For more information about adding objects, see �� .

10. Click Next to display the Language Component form. This form allows you toadd to your package language specifications for a language other than English.

Assembling Packages

B73.3.1 (6/99) 5–23

The Select Languages Only option enables you to display only the languagescurrently selected for the package. This applies to situations where you arerevising a previously assembled package, not to when you are assembling apackage for the first time.

If you add a language to your package, only that language will be included. Forexample, if you add French, English will not be included even though it is thedefault language. If you want two languages (such as French and English,) youmust include them both in your package. For more information about installingOneWorld in multiple languages, see the OneWorld Installation Guide.

11. Click Next to display the Package Component Revisions form. This form allowsyou to see at a glance the current foundation, help, and database locations, aswell as the objects in the package and any language selection.

To change any of these package components, click the icon for the componentyou want to change. The form for that package component appears.

12. When you are finished assembling the package, click End to exit from thePackage Assembly Director. At this point you are ready to change the package’sstatus to [assembly] Definition Complete as described in ��

Package Management

5–24 B73.3.1 (6/99)

Field Explanation

Package Name A package describes where on the server to find thecomponents you want to deploy to workstations. There arethree package types:

Full: Contains the full suite of OneWorld applications (allspecifications).

Partial: A minimum configuration of OneWorld. This packagetype allows users to load the desired applications at run-timerather than initially installing all applications.

Update: OneWorld objects contained in this type of packageare loaded after the workstation receives the package and theuser signs on to OneWorld. If the update package includesobjects without the corresponding specifications, old versionsof the application are deleted from the workstation andreplaced by the current version the next time the user accessesthat application. Update packages are always deployed on thedate and time specified by the OneWorld administrator.

Description A description of the package.


Assembling Packages

B73.3.1 (6/99) 5–25

Field Explanation

Indicate what type ofpackage you are assembling

Full and partial packages are primarily for initial OneWorldinstallations, and allow you to create a full or partialworkstation configuration on machines that do not haveOneWorld installed. These packages are normally deployed viathe Workstation Installation application. Update packages arefor deploying changes, additions, or enhancements to userswho already have OneWorld installed, or can be used as acomplete replacement of an existing package. Update packagesare always installed through the Package Deployment Director.

Full package:This is a full package that contains all specificationsand foundation code needed to run and develop inOneWorld.

Partial package:This package type is a minimum configuration ofOneWorld that contains only the specifications thatallow users to launch OneWorld Explorer.Applications can then be loaded throughjust-in-time-installation the first time the user selectsan application.

Update Package:This package type enables the OneWorldadministrator to create a package containing specificitems which can then be deployed to specific users.An update package enables administrators to includein the package any item type (such as any OneWorldobject, help file, OneWorld foundation, and so on).For this reason, this package type is well-suited fordeploying software changes and fixes quickly. Whena user is scheduled to receive an update package,OneWorld loads the package the next time the usersigns on to OneWorld.

Include Object Specs When you include individual objects in an update package, youhave the option of including a corresponding set ofspecifications for those objects. When you includespecifications, a “snapshot” of the specifications will beincluded in the package after it is built. When the package isdeployed, the package recipient receives those objectspecifications.

If you do not include object specifications in the package, theold specifications for the objects in the package will be deletedfrom the workstation when the package is deployed. Then, thenext time the package recipient attempts to use the object, anew set of specifications for it will be transferred to theworkstation via just-in-time-installation.

Parent Package Since an update package includes only a subset of objects, youmust indicate the parent package on which the update packageis based or related to. This information is used by the system todetermine how to build business functions.

Package Management

5–26 B73.3.1 (6/99)

Field Explanation

Selected Languages Only When this box is checked, only languages that have beenselected for inclusion in the package will be loaded in the grid.

Language A list of valid codes for a specific user defined code list.

Adding Objects to a Package

If you are assembling an update or partial package, you can select individual objects toinclude in the package. When you are finished adding objects, those objects will bedisplayed on the Package Assembly Director’s Object Component form, as well as thePackage Component Revision form and the Work with Packages form.

The following task describes how to add objects to a partial or update package. Theprocedure is the same whether you are adding objects for the first time or revising apreviously assembled package.

To add objects

1. Display the Object Component [Selection] form by doing one of the following:

� ��

� ��

��

2. Find and choose the object you want to include in the package, and then clickSelect.

Assembling Packages

B73.3.1 (6/99) 5–27

3. If you are adding a batch application, the Version Selection form appears so youcan specify the appropriate version.

According to your preference, click All Versions or JDE Versions, or selectspecific individual versions you want to include. The list of versions appears.Note that only versions that have been checked in are displayed.

When you are finished, click Close to return to the Object Component Selectionform.

4. Repeat this process until you have finished adding objects to your package.When you are finished, click Close to return to the place from which youaccessed the Object Component Selection form.

Field Explanation

SAR Number An abbreviation for Software Action Request (SAR). Thisnumber is used by the J.D. Edwards project control system tokeep track of all charges and activity by individual SARnumber.

Package Management

5–28 B73.3.1 (6/99)

Field Explanation

Object Name The OneWorld architecture is object-based. This means thatdiscrete software objects are the building blocks for allapplications, and that developers can reuse the objects inmultiple applications. Each object is stored in the ObjectLibrarian. Examples of OneWorld objects include:

� ��

� ��

� ��

� ��

� ��

� ��

� ��

Description The description of a record in the Software VersionsRepository file. The member description is consistent with thebase member description.

Object Type The type of object with which you are working. For example, ifyou are working with tables the object type is TBLE, orbusiness functions is BSFN.

Status Code This code determines the status of the software in thedevelopment cycle.

User For World, the IBM-defined user profile.


Merger Option The Merge Option denotes whether a customer’s OneWorldobject will be merged in with the J.D. Edwards OneWorldobject. The Merge Option can be set at the Path Code level sothat all objects checked into that path will carry the sameMerge Option as the Path Code.

Date Modified The date that the object, such as a DREAM Writer version,Software Versions Repository Record, and so on, was lastmodified.

Time Modified The time the object was last checked in.

System Code A user defined code (98/SY) that identifies a J.D. Edwardssystem.

Reporting System A code that designates the system number for reporting andjargon purposes.

See UDC 98/SY.

All Versions Indicate if all of the versions for the UBE selected should beinclude in the package.

JDE Versions Indicate if just the J.D. Edwards versions (XJDE and ZJDE)for the UBE selected should be included in the package.

Assembling Packages

B73.3.1 (6/99) 5–29

Field Explanation

Version A version is a user-defined set of specifications. Thesespecifications control how applications and reports run. Youuse versions to group and save a set of user-defined processingoption values and data selection and sequencing options.Interactive versions are associated with applications (usually asa menu selection). Batch versions are associated with batchjobs or reports. To run a batch process, you must choose aversion.

Version Title A description of the version that appears next to the versionnumber. The version title is different from the report title.

This field should describe the use of a version. For example, anapplication for generating pick slips might have a versioncalled Pick Slips - Accounting and another version called PickSlips - Inventory Management.

Entering a Foundation Location

The default foundation location is determined through the release associated with thepackage’s path code. This is normally the system directory at the same directory levelas your path code.

The following task describes how to change the foundation location from the defaultlocation displayed on the Foundation Component form.

To enter a foundation location

1. Display the Foundation Component Selection form by doing one of thefollowing:

� ��

� ��

��

Package Management

5–30 B73.3.1 (6/99)

2. Find and choose the foundation you want to use in your package. If you want touse a new foundation, see the following step.

3. To add a new foundation, click Add. The Foundation Item Revisions formappears.

4. On the Foundation Item Revisions form, complete the following fields and thenclick OK:

� ��

� ��

Assembling Packages

B73.3.1 (6/99) 5–31

� ��"�� !�� !��

� ��

� �� #��

� �!�� #��

� ��!�� !�� !�

� �� !��

� �� !��

� ��!�� #

� ��!��

Field Explanation

Foundation Name A OneWorld foundation is the code required to run allOneWorld applications. A foundation ID is required for all fulland partial packages. For full and partial packages, if you donot enter a foundation line, the default foundation will be used.The default foundation is determined through the releaseassociated with the path code for the package. This is normallythe system directory at the same directory level as your pathcode. The foundation must be compressed when built.

Service Pack Number forOW Foundation

A service pack is an update to the foundation code that isdelivered between major releases and cumulative releases ofthe OneWorld software.

Release Number For World, the release number as defined in the SoftwareVersions Repository.

For OneWorld, the release number as defined in the ReleaseMaster.

Form-specific information. . . . . . . . . . . . . . . . . . . . . . . . . . . .

On this form, Release Number is the OneWorld major releasewith which this foundation is associated.

Platform Type Host Machine Type.

Build Type Indicate the compiler configuration to use for the softwarebuild.

Foundation Build Status Describes the current status of the build process for OneWorldfoundation.

Date Built The date the software build completed.

Time of Build The time at which the software build completed.

Package Management

5–32 B73.3.1 (6/99)

Field Explanation

Foundation Machine Key For World, the Location indicates the machine (server orclient).



On this form, the Machine Key is the name of the deploymentserver where your custom foundation resides.

Foundation Path For World, the Server Share Path Field is used by theenvironment to determine the location of the current server.

For OneWorld, this field indicates the shared directory for thispath code. The objects that are stored on a file server will befound in this path.


On this form, enter the exact path from which this item shouldbe copied. All files in the last directory specified will beincluded in the package.

Entering a Help File Location

For all package types, if there is no help location, the package build creates an INF thathas help mapped to the default location as defined in Release Master (one set of helpper release). If a help file location is defined for a package, the package build copies thehelp file from the location defined in Help Item Revisions to the package directory.

The package INF will indicate that help files are located in the package itself, instead ofthe default location. Regardless, Workstation Installation installs help to theworkstation based on the user’s deployment preference of client or server. WorkstationInstallation updates the JDE.INI file according to the package INF help location and thedeployment preferences help location.

The following task describes how to change the help location from the default locationdisplayed on the Help Component form.

To enter a help location

1. Display the Help Component Selection form by doing one of the following:

� ��

� ��

Assembling Packages

B73.3.1 (6/99) 5–33

2. Find and choose the help location you want to use in your package. If you wantto use a new location, see the following step.

3. To add a new help location, click Add. The Help Item Revisions form appears.

Package Management

5–34 B73.3.1 (6/99)

4. On the Help Item Revisions form, complete the following fields, and then clickOK:

� ��

� ��

� ��

� ��

Field Explanation

Help Item Name A OneWorld foundation is the code required to run allOneWorld applications. A foundation ID is required for all Fulland Partial packages. For full and partial packages, if you donot enter a foundation line, the default foundation will be used.The default foundation is determined through the releaseassociated with the path code for the package. This is normallythe system directory at the same directory level as your pathcode. The foundation must be compressed when built.

Source Machine Key For World, the Server Share Path Field is used by theenvironment to determine the location of the current server.



On this form, enter the exact path from which this item shouldbe copied. All files in the last directory specified will beincluded in the package. Source Machine Key and Source areused together to define the item’s location.

Source For World, the Server Share Path Field is used by theenvironment to determine the location of the current server.


Entering a Database Location

For full and partial packages, if you do not specify a database location, the defaultdatabase path will be used. Update packages do not require a database.

The following task describes how to change the database location from the defaultlocation displayed on the Database Component form.

Assembling Packages

B73.3.1 (6/99) 5–35

To enter a database location

1. Display the Database Component Selection form by doing one of the following:

� ��

� ��

2. Find and choose the database location you want to use in your package. If youwant to use a new location, see the following step.

3. To add a database, click Add. The Database Item Revisions form appears.

Package Management

5–36 B73.3.1 (6/99)

4. On the Database Item Revisions form, complete the following fields, and thenclick OK:

� ��

� ��

� ��

� ��

Field Explanation

Database Item Name A OneWorld foundation is the code required to run allOneWorld applications. A foundation ID is required for all fulland partial packages. For full and partial packages, if you donot enter a foundation line, the default foundation will be used.The default foundation is determined through the releaseassociated with the path code for the package. This is normallythe system directory at the same directory level as your pathcode. The foundation must be compressed when built.

Source Machine Key For World, the Location indicates the machine (server orclient).


Assembling Packages

B73.3.1 (6/99) 5–37

Field Explanation

Source For World, the Server Share Path Field is used by theenvironment to determine the location of the current server.



On this form, enter the exact path from which this item shouldbe copied. All files in the last directory specified will beincluded in the package. Source Machine Key and Source areused together to define the item’s location.

Activating a Package

After you have assembled a package, the status remains [assembly] In Definition,which means the package is inactive, until you specifically change it to [assembly]Definition Complete, which means the package is active. An assembled package cannotbe built until the status has been changed to Definition Complete. Changing apackage’s status to Complete indicates to the system that you are finished assemblingthe package and are ready to begin the build definition process.

You can change the package’s status at any time until you start the build definitionprocess. That is, even after you have changed a package’s status to Complete, you canstill change the status back to In Definition if you need to revise the assembledpackage.

To activate a package



2. From the Work with Packages form, select the package you want to activate.Packages that are currently In Definition are identified by an open box icon,while packages that have a Complete status have a closed box icon.

3. Choose Active/Inactive from the Row menu.

You can use this same process to change a Complete package back to In Definition.

When you are ready to define the package’s build, follow the steps described in�� .

Package Management

5–38 B73.3.1 (6/99)

Revising an Existing Package

Once you have assembled a package, you can easily revise any of that package’scomponents by using the Package Component Revision form. You do not need to gothrough all of the Package Assembly Director’s forms to revise a package.

Before You Begin

You cannot revise a package unless the package status is In Definition. If you try torevise a package whose definition is Complete, you will receive an error message. Ifnecessary, before you select the package to revise, choose Active/Inactive from theWork with Packages form’s Row menu to change the package status.

To revise an existing package



2. Find the package you want to revise, either by using the Find function or byclicking the Packages plus sign (+) to expand the displayed tree.

3. When the package you want to revise is selected, choose Package Revisionsfrom the Row menu. The Package Component Revisions form appears. All ofthe information for the selected package’s components is displayed.

4. To change the foundation, helps, or database location, click on the appropriateicon to display the form where you can make your changes. Likewise, click theObjects icon to add objects to the package, or click the Language icon to specifya language other than English.

5. To change the description or parent package name, choose Property Revisionsfrom the Form menu.

6. When you are finished revising the package definition, click OK to return to theWork with Packages form.

If any build information exists for the package, when you make changes you will begiven the option to delete the existing build information. If you do not delete existingbuild information after making changes, you should update the build information sothat it reflects the changes you made.

Copying a Package

In some cases it may be easier to copy an assembled package rather than creating a newone entirely from scratch. In addition, when you make a copy of a package that hasbeen built (that is, has a Build Complete status,) the original package’s definitionrecords are copied and added to the new package. Directories (including serverdirectories) from the old package are also copied to the new package.

Assembling Packages

B73.3.1 (6/99) 5–39

To copy a package



2. Find and choose the name of the package you want to copy, and then click Copy.The Package Information form appears.

3. Enter the new package’s name, description, and path code.

If the package you are copying has been built (that is, the package has a status ofBuild Complete), the Copy Build Information option will be available. Whenyou turn on this option, all of the package definition records, directories, andserver directories from the original package are copied into the new package.

4. Click OK to return to the Work with Package form, where you can selectPackage Revisions from the Row menu to review and change any of the packagecomponents.

Package Management

5–40 B73.3.1 (6/99)

Field Explanation





Description A description of the package.


Copy Build Information If you are copying a package, indicate if you would like thepackage directories copied as well as the package definition. Ifyou copy the package directories, the new package does notneed to be built before it is deployed to users, since it is anexact copy of the original package.

Deleting a Package

The Work With Packages form contains an option that allows you to delete existingpackages, provided that they are not currently in the process of building. You cannotdelete packages that are being built.

When you choose a package and click Delete, all information for that package in thePackage Header and Detail tables (F9603 and F9631) is deleted. In addition, if thepackage has been built, all specifications for that package will be deleted on all servers,as well as information in the Package Build Header and Detail tables (F96021 andF9622). Deployment records, if any, will also be deleted.

Assembling Packages

B73.3.1 (6/99) 5–41

To delete a package



2. Find and choose the name of the package you want to delete.

3. Click Delete.

4. Confirm the deletion by clicking OK when the warning message appears.

Package Management

5–42 B73.3.1 (6/99)

B73.3.1 (6/99) 5–43

Defining Package Builds

After you assemble a package, you must then define the package build before you candeploy it to your workstations. The build process reads the central objects data sourcefor the path code you defined in the package. This information is then converted from arelational format to replicated objects, which are put in the package itself.

To help explain the flow of information that occurs during the build process, the B733(release name) directory structure looks similar to this, with check-in locationsidentified by an asterisk:

B733

PRODB733 (path code name)

PACKAGE

PackageA (package name)

bin32

include

lib32

make

obj

res

source

spec

work

*bin 32

*include

*lib32

make

*obj

*res

*source

work

When you build a package, the directories under the package name are populated.Information for the source and include directories is copied from the check-in locationunder the path code on the deployment server. Information for all other directoriescomes from the central objects data source. The bin32, lib32, and obj directories arepopulated with the output of the business function build.

Package Management

5–44 B73.3.1 (6/99)


� ��"#$�� $�� %�� !" ��##

� ��"#$�� $�� %�� $� � �"��$ "

� �� !�� %��

� ��&�#�� !��# �%�� !$� �#

� � !(�� %��$ !��

� ��'�� !�� %�� #$ "( �� "�#%��$$�� %��#

Understanding the Build Process

The following is a checklist of the processes you need to complete when you perform abuild. This entire process can take several hours. For this reason, J.D. Edwardsrecommends that you initiate the actual package build at the end of the working day, ifpossible.

� �"��#��" ��$#

Ensure that all the objects you want to include in the build have been transferredto the appropriate path code.

See � �� .

� �#%"� $��$ $�� " # �$ ��## ��$��#� � " $�� !�� # $�� #$

�%""��$ "�!��$�� $��

See Data Replication in the System Administration Guide.

� �%�� !��

Build a package over the path code to which objects were transferred. Thisprocess is described in this chapter.

� ��!$� �� "� "� � �" ##)"��"�� %��

Perform a cross-reference build to make sure your changed objects are in syncwith cross-reference information. This process takes up to 15 hours to complete.You can deploy your package before the cross-reference build has completed.

See Cross Reference Facility in the OneWorld Development Tools Guide.


B73.3.1 (6/99) 5–45

� �$ #, (�� '#�(+�&� (# (�� # #+�"��

� �#&�'(�(�#"' �"� '�&*�&'

� ��&�� $ #,!�"( #��(�#"'

See ��.

Understanding the Package Build Definition Director

Like the Package Assembly Director, the Package Build Definition Director simplifiesand expedites the build definition process by displaying a series of forms that guide youthrough the process.

As with the Package Assembly Director, you always have the option of going to theprevious or next screen by clicking Previous or Next. Also, you can always cancel thebuild definition process by clicking Cancel.

The following summarizes each of the Package Build Definition Director’s forms andtheir function:

� �� + (��' �#&! �#& � ��'�&�$(�#" #� (�� )� �

��"�(�#" �&��(#&�

� �� '� (��' �#&! (# '� ��( (�� "�� $�� ,#)

+#) � �� (# �)� �� $��' '(�()' !)'( �� ''�!� ,� ��"�(�#"

#!$ �(��

� �� "��(� +��(��& ,#) +#) � �� (# �)� �

(�� $�� #& (�� "( +#&�'(�(�#"� #"� #& !#&� '�&*�&'� #& �#(� � ��"('

�"� '�&*�&'�

� � �� $��, (�� '�&*�& #��(�#"� � �%)�&�� +��" ,#)

�)� � � $�� #& � '�&*�&��

� �� '� (��' �#&! (# '$��, (��

'$��(�#" (�� ' ,#) +�"( (# �"� )�� " (�� $�� '$��(�#"

(�� '� #& #" , '� ��(�� (�� '� �� #$(�#" (# �)� � �"��*��)� '$��(�#"'

�' )'��) �� )� � �� ' �"� ,#)& $�� &&#& #� �"��(�' (��( �"

�"��*��)� '$��(�#" �� "��' (# �� &��)� (�

� �� '� (��' �#&! (# �"� )��

'� ��(�� (�� ' #" , �" (�� $��

� �� '� (��' �#&! (# �)� � �)'�"�''

�)"�(�#"'� �#) ��" � '# '$��, (�� )� � !#�� (�� '�*�&�(, �*� �( +��

(# �"(�&&)$( (�� )� � $&#��''� +��(��& (# �)� � �)'�"�'' �)"�(�#"

�#�)!�"(�(�#"� �"� +��(��& (# � ��& (�� #)($)( ��'(�"�(�#" ��#&�

�)� ��"��

Package Management

5–46 B73.3.1 (6/99)

� �� #� $��# � "� $ #!��( !��

� �!"�##� �� #��$ !$� �# $ � �!"�## ��"��$ "��# �� " ��&��%��

��$�� !#� �� %��$� ��

� �� $ � $��# � "� $�� &��%��

��"��$ "��# ( % '��$ $ � �!"�##�

� �� #� $��# � "� $ "�&��' " �� ( �

$�� !$� �# ( % ��&� #!�� " ( %" !��

Building Business Functions During Package Build

As part of the build definition process, you can specify whether you want to buildbusiness functions. If so, a global build of business functions takes place during thepackage build process.

You should always build business functions for full and partial packages, and forupdate packages that include a business function object.

When you build business functions as part of the package build, it is the same processas if you manually executed the BusBuild program (selected Build from the GlobalBuild menu) after the package was built.

Source and header information is gathered from the package (from the source andinclude directories), compiled, and put into the bin32, obj, and lib 32 directories.Business functions are built in the package, not on the workstation. After businessfunctions are built, they are compressed, provided that you turn on the CompressPackage option.

OneWorld makes certain assumptions about path code, foundation, and destination forthe business function build. In particular:

� �� %�� %#��## �%��$� �#� ( % �%�� " � $�� !�$� � �� ( %

�� $�� !��

� �� %��$� � �# ��$��" $�� #�� # $�� %��$� � ��%�� $��

!�� "� � " �� %!��$� !�� $�� !�"��$ !��# � %��$� ��

� %�� %$!%$ �# ��"��$�� $ $�� "��$ "��# � $��

!�� $#��

� �� %�� %�� " !�"$�� !�� " �� %!��$� !�� $��$

��%��# � �%#��## �%��$� �� ( % #� %�� '�(# �%�� %#��## �%��$� �#�

$��"'�#�� $�� # ��$�� # ��%�� $�� !�� '�� $ ��

�%""��$�

For update packages, a single build is performed for each business functiondefined in the package. After the individual business function is built, a globallink is performed for that object and all other objects that are in the sameconsolidated DLL. The global link process uses the objects found in the check-inlocation for that package’s path code.


B73.3.1 (6/99) 5–47

Similarly, any business functions defined in a partial package are builtindividually and then linked with all objects in the check-in location. The onlydifference with a partial package is that all consolidated DLLs are delivered, notjust the ones that may or may not be defined in the package itself.

Check-in location directories will not be updated with the build’s output.

For more information about the BusBuild program, see the Business Functions sectionin the OneWorld Development Tools Guide.

Defining a Package Build

The following task describes how to define a package build using the Package BuildDefinition Director.

Before you build the package, you may want to verify that the Object ConfigurationManager (OCM) mappings are correctly set for the the Package Build Report (R9621)and Server Package Build Report (R9622) that are generated as part of the packagebuild process.

For example, if you want the reports to run locally, you should make sure the OCMmappings point to Local for the environment in which the package build is running. Formore information about setting OCM mappings, see Object Configuration Manager inthe Configurable Network Computing Implementation Guide.

Before You Begin

� �!!�� %�# ��

� �� % �� ! �� "�� #�� " �� $�

�� #�� " ��

To define a package build

There are two ways to access the Package Build Definition Director: from the PackageAssembly function’s Work with Packages form, or from the Package Build function’sWork with Package Build Definition form.

The advantage of accessing the director from the Work with Packages form is that thepackage name and other information is automatically entered for you. If you access thedirector from the Work with Package Build Definition form you will need to manuallyspecify the name of the package you want to build.

Regardless of how you access the Package Build Definition Director, remember thatthe assembled package must have a status of Definition Complete before you candefine the package build.

Package Management

5–48 B73.3.1 (6/99)

1. To access the Package Build Definition Director from the Work with Packagesform, select a defined package that has a Definition Complete status, and thenchoose Build Director from the Row menu.

To access the director from the Package and Deployment Tools menu (GH9083),choose Package Build (P9621). The Work with Package Build Definition formappears.

Any previously built packages will be displayed on this form. As on any otherparent/child form, you can expand or compress by clicking on the plus (+) orminus (–) symbols to show more or less information.

If you have any previously-built packages, you can view the package’sproperties, build options, business function options, and compression options. Inother words, you can review all of the options and information you specifiedwhen you created the package.


B73.3.1 (6/99) 5–49

2. Click Add to launch the Package Build Definition Director. The Package BuildDefinition Director form appears.

If you accessed the director from Work with Packages, skip the following step.

3. If you accessed the director by clicking Add, clicking Next from the PackageBuild Definition Director form displays the Package Selection form.

On the Package Selection form, find and select the defined package you want tobuild.

Package Management

5–50 B73.3.1 (6/99)

If the package’s definition is still In Definition, before you can build the packageyou must change the status to Definition Complete. To do so, select the packageand choose Activate from the Row menu.

4. Click Next. The Package Build Location form appears. Specify whether youwant to build a package for client workstations, one or more servers, or bothclients and servers. (If you are building a partial package, you will not beallowed to build the package for a server.)

Be sure to choose Server(s) if you the package you are building goes to one ormore servers.

If you are building a package for workstations only, skip the following stepwhich applies only to server package builds.

5. Click Next. If you are building a package for a server and chose Server(s) on thePackage Build Location form, the Server Selection form appears.


B73.3.1 (6/99) 5–51

This form enables you to select the servers on which you want to build thepackage. To select a server, click Find, and then double-click in the column tothe left of the server name. A checkmark indicates your selection. Repeat theprocess to select multiple servers.

6. Click Next. The Build Options form appears.

Package Management

5–52 B73.3.1 (6/99)


� �"�� !�� !��

� �� !�� #��"�� !��

� �!��%�"�� !��

� �� !��"! �"�� #�� "�� $�

� �� "��!� �� $�

The Stop-Build option on this form allows you to indicate the point at whichOneWorld should stop the build: Continue building on all errors; Stop buildingon specification errors; Stop building on business function errors; or Do notcompress if there are errors.

If you select All Specification Tables, all of the tables listed on the IndividualSpecification Selection form will be included in the package. If you are buildingall specification tables, skip the following step.

When you build a server package, the Transfer Without Building option allowsyou to transfer table specifications to the server without building them.

If the package you are building goes to a server, make sure to choose BuildOptions and All Specification Tables.

7. Click Next. If you elected to build individual specification tables, the IndividualSpecification Selection form appears.

Select each specification table you want to build.


B73.3.1 (6/99) 5–53

8. Click Next. The Business Function Options form appears.


� ��

� ��

� ��

� ��

� ��

There are three build modes: Debug, Optimize, and Performance. Debug andPerformance are for J.D. Edwards developers only. Users should select theOptimize mode.

This form’s Stop-Build Option field allows you to indicate the point at whichOneWorld should stop building business functions: Continue building on allerrors; Stop building on the first error; or Stop building on DLL failure.

The Build BSFN Documentation option allows you to create an online list ofbusiness function documentation. This list is created after you submit the build,and is saved in the PrintQueue folder beneath the B7 folder that contains yourother OneWorld files. In order to read the files produced you will need anInternet web browser or another application capable of displaying HTML files.For more information about building business function documentation, see theOneWorld Development Tools Guide.

The Clear Output Destination First option allows you to clear the outputdirectories (bin32, lib32 and obj) before building business functions so that oldbusiness functions are not included when the package is created. If you do not

Package Management

5–54 B73.3.1 (6/99)

clear the output and a function fails to process, the global link process will usethe old libraries and objects to create the consolidated DLL file. This can resultin the creation of an inaccurate global package.

If the package you are building goes to a server, be sure to choose BuildFunction Options.

9. Click Next. The Compression Options form appears.


� ��

� ��

� ��

� ��

� ��

When you compress directories, the application objects included in the packageare automatically compressed. OneWorld also creates an entry in the packageINF file that indicates whether that the following items are compressed:foundation, helps, data, and application objects.

Compress All Directories or Individual Directories are the only options thatmodify the package INF. All other compression options perform only the actualcompression.

Compress Data compresses the Microsoft Access database associated with thispackage, Compress Foundation compress the foundation associated with your


B73.3.1 (6/99) 5–55

package, and Compress Helps compresses the help files associated with yourpackage.

If you select compress All Directories, all of the directories listed on theIndividual Directory Selection form will be compressed. If you are compressingall directories, skip the following step.

If the package you are building goes to a server, there are only situations whenyou would want to choose Compress Options: 1) when you are building thesame package for both the workstation and server and want to create compressfiles for the workstation package, or 2) if you plan to build the package on oneenterprise server and deploy it to another enterprise server.

To enable creating compressed files on the server, check the jde.ini file on theworkstation that is running the package build application. Under the BSFNBUILD section, verify that the DoCompression setting is 1 to enablecompression. If this setting is incorrect, compressed files will not be created onthe server.

10. Click Next. If you elected to compress individual directories, the IndividualDirectory Selection form appears.

Select each directory you want to compress.

11. Click Next. The Package Build Revisions form appears.

Package Management

5–56 B73.3.1 (6/99)

This form allows you to see at a glance the current build options, businessfunction options, and compression options you have specified for the package.

To change any of these options, click the tab for the type of option you want tochange.

When you are finished reviewing or changing your build options, click End toexit from the Package Build Definition Director. The Work with Package BuildDefinition form appears.

12. When you are ready to initiate the package build, choose Submit Build from theRow menu.

13. Choose a destination for the build report, and click OK:

� � ��

� � ��

The form automatically closes and OneWorld begins building the package. Buildtime varies, depending on the number and size of the items in your package. Abuild could take five minutes for a small package, or several hours for a fullpackage containing all applications. When the build is finished, the report willeither display or print, depending on the destination you specified.

14. Review the report to make sure that all components in your package weregenerated successfully. If the report indicates any errors, review the error logsfor more detail.

If the package build completes successfully, you can schedule the package fordeployment as described in ��.


B73.3.1 (6/99) 5–57

After the package is successfully built, you must activate the package as described inActivating the Built Package. Activating the package makes it available for installationthrough the Workstation Installation application. If you do not activate the package, thepackage will not be included in the list of available packages that displays whenWorkstation Installation is launched.

Field Explanation

Server Name The data source name.

Data Source Type The type of database.

Database Name The name assigned to the database during installation, such asHPDEVORAP or HP9000.

Build Options Select Build Options to take the package definition and copyand convert objects from the central data source to thereplicated format used by workstations. Also, enter optionspertaining to the build process.

All Specification Tables Indicate if you want to build all specification tables into thepackage, or if you would rather select individual tables toinclude in the package.

Stop–Build Option This option enables you to specify what action OneWorldshould take if an error occurs during the package buildingprocess.

Replace JDE.INI Indicate if you want a new JDE.INI file delivered with thepackage. You should leave this unchecked unless your JDE.INIfile has changed. For example, your JDE.INI may change whenyou perform upgrades or when you reconfigure in releasemaster.

Build Functions Options Select Build Functions Options to perform a global build of allbusiness functions included in this package, and to enteroptions pertaining to the business function build process.

Build Mode Indicate the compiler configuration to use for the softwarebuild.

Stop–Build Option This option enables you to specify what action OneWorldshould take if an error occurs during the business functionbuilding process.

Transfer Do Not Build This option enables you to transfer to the server thespecification tables you have selected. (The tables you want totransfer must be built before you can use this option.) In mostcases, if you elect to include the specification tables in yourpackage they are automatically transferred to the server duringthe build process. However, if something causes the transfer tofail during the build process (such as the server being down),you can use this option to move the tables to the server withoutfirst rebuilding them. This option applies only to packages forthe server.

Package Management

5–58 B73.3.1 (6/99)

Field Explanation

Build BSFN Documentation Indicate whether you want to build business functiondocumentation during the package build process. For a fullpackage, the documentation will be built for all businessfunctions. For a partial or update package, documentation willbe built for only those functions included in the package.

Clear Output DestinationBefore Build

When building business functions, you should normally clearthe output directories (bin32, lib32 and obj) so that oldbusiness functions are not included when the package iscreated. If you do not clear the output and a function fails toprocess, the global link process will use the old libraries andobjects to create the consolidated DLL file. This can result inan inaccurate global package.

Compress Options Select Compress Options to compress the applications includedin the package, and to specify options for the compressionprocess.

All Directories Indicate whether you want to compress all directories in thepackage, or if you would rather select individual directories forcompression.

Individual Directories Indicate whether you want to compress all directories in thepackage, or if you would rather select individual directories forcompression.

Compress Data Indicate whether to compress the data in a package after thepackage is created.

Compress Foundation Indicate whether to compress the foundation files in thepackage after the package is created.

Compress Helps Indicate whether to compress the help files in a package afterthe package is created.

Package Build Processing Options

The Package Build Definition Director (P9621) has a processing option that controlsthe amount of changes you can make for individual servers.


B73.3.1 (6/99) 5–59

Enter a ’1’ to allowchanges to the builddefinitions by individualserver. If blank changeswill only be allowed at thepackage level and willapply to all serversselected.

When you enter a 1 at this field, OneWorld allows you tochange the build definition for individual servers. If this field isblank, any revisions you make to the build options andinformation you enter will be applied to all of the servers forwhich you want the package built.

For example, if you set this option to one, on the Work withPackage Build Definition form you will be allowed to makechanges to an individual server’s properties, build options,business function options, and compression options. If thisprocessing option is blank, you will not be able to make thesechanges to an individual server, but at the package level only.The changes will apply to all of the servers for that build.

Revising a Package’s Build Options

Once you have entered a package’s build options, you can easily revise any of thoseoptions by using the Build Component Revision form. You do not need to go throughall of the Package Build Definition Director’s forms to revise build options.

Package Management

5–60 B73.3.1 (6/99)

To revise a package’s build options


1. Choose Package Build (P9621). The Work with Package Build Definition formappears.

2. Find the package you want to revise, either by using the Find function or byclicking on the Packages plus sign (+) to expand the displayed tree.

3. If the package is active (as indicated by the “closed package” icon,) chooseActive/Inactive from the Row menu.

4. When the package you want to revise is selected, choose Build Revisions fromthe Row menu. The Package Build Revisions form appears. All of the buildinformation for the selected package is displayed.

5. Click on the appropriate tab to change the package’s build options, businessfunction options, or compression options. When you are finished, click OK toreturn to the Work with Package Build Definition form.

6. Activate the package by choosing Active/Inactive from the Row menu.

7. If you are ready to begin the build process, choose Submit Build from the Rowmenu.

Copying a Built Package

After you build a package, you can copy the package definition, which includes thepackage record, header, and detail files.

There are two ways to copy a package:

� ��

��

� ��

��

To copy a package build definition from a server



2. Find the package you want to copy. Under that package, select the server whosedefinition you want to copy.

3. Click Copy. The Copy Package Build Definition form appears.


B73.3.1 (6/99) 5–61

4. The package name, path code, and server name from which you are copying willbe displayed, as well as the destination package name and path code (which arethe same).

Enter the name of the server to which you want to copy the package.

To copy the package to the workstation instead of to a server, choose Client.

5. Click OK to return to the Work with Package Build Definition form.

To copy a package to a new package



2. Find and select the package you want to copy.

3. Click Copy. The Copy Package Build Definition form appears.

Package Management

5–62 B73.3.1 (6/99)

4. The package name, path code, and server name from which you are copying willbe displayed.

Enter the new package name and server name.

If you want to copy to the client workstation instead of to the server, selectClient.


Viewing Package Build History and Resubmitting Builds

After you submit the package for building, you can track the build status by using thePackage Build History (P9622) application. This application also enables you to viewlogs associated with the build process to determine if any errors occurred during thebuild process.

If the build did not complete successfully, you can resubmit the package and resumebuilding from the point where the build stopped. Alternatively, you can change thepackage’s build status and build the package again.

For information about the Package Build History, viewing logs, resubmitting builds,and changing the package build status, see �� .

B73.3.1 (6/99) 5–63


All OneWorld application development takes place on a workstation with objects storedon a deployment server through Object Librarian. OneWorld allows you to partitionbusiness applications to an enterprise server. In order to ensure that modifications andenhancements developed on the workstation are reflected on the server, you must builda server package containing those modifications and enhancements.

Through the same Package Assembly and Package Build applications that enable youto create workstation packages, developers and system administrators can assemble,define, and build a server package that pushes objects from the central objects locationto enterprise servers. After you define and build a server package, you can install it toenterprise, logic, or application servers by using the Package Deployment application.

In a development environment, developers can create server packages whenever theycreate or modify an object and there is a need for that object to be on the enterpriseserver. In a production environment, a OneWorld system administrator should createserver packages.

A server package is a group specification records, source files, and header files.Compiled objects are created on the enterprise servers. A server package is essentiallythe same thing as a client workstation package, with the following exceptions:

� ��!%�! ��" �� # ��$�� !�� !��#�� ! � ��!�"��#

��"" ��#��"�

� �$��#�� " ��# #( ��( �� (�� " �!# �� "�!%�! ��

��"#�� # �" �$��# �� #�� #�!�$�� #��! ��"�"�

� �� "�#" �� #�� "" ��#� " ��#��" "$�� " �!�

�"�� #��# �"� ��#�!��#�%� �� " ��#��"�� !� ��# $"�� "�!%�!"

�� #��!��!� �!� ��# ��$�� "�!%�! ��

� �� $"��"" �$��#��" �!� ��# �$��# �� #�� "�!%�!� �� #��!��!� �!� ��#

��$�� "�!%�! ��

� ��!#�� " �!� ��# �%�� ! "�!%�!"�

There are three main reasons you need to create a separate server package thatcorresponds to the workstation package:

� �$"��"" �$��#��" �!� ��# �� #�� !�"" ��#��!�"� �! �'��

�$"��"" �$��#�� &�!�"#�#�� &�� # !$� �� "�!%�!�

��"�� # �� $"��"" �$��#��" �!� �� #�� "�!%�!��

� �#� ��# �" ��!��# ��!�"" ��#��!�"� �� " �$�� #��

&�!�"#�#�� &��# !$� �� #�� "�!%�!� �� " ��#��" �$"# �� %�!#��

Package Management

5–64 B73.3.1 (6/99)

�!# %�� $�#'�#� �$!� � %��# #�"#�$� %�%�! �%�� (�) &��#$ �#�

#��!� �*�� %�� $ ��#� % ! $�#'�#$ %�� ! %�� (!#�$%�%�! �

� �� %! �� ! '�#$�! �&$% %�� "�� !# %��

In addition, there are differences between server platforms. For example, eachenterprise server platform has its own internal storage for specifications which are notcompatible across platforms. Also, each enterprise server platform uses differentcompilers and has different object representation, so business functions are notcompatible across platforms.

For information about server packages, see the following:

� � ��#$%� �� %�� $�#'�# "�� &�� "#!��$$

� �� $�%%� �$ �!# $�#'�# "�� &��$

Understanding the Server Package Build Process

Although creating a server package is identical to creating a client workstationpackage, the purpose for creating server packages is different. The main purpose of theserver package build process is to enable OneWorld administrators to build TAMspecifications and business functions on the enterprise servers.

The Package Build application provides the following benefits in terms of serverpackage builds:

� �#!'��$ �!�"��%� � %��#�%�! (�%� �� % (!#�$%�%�! "�� &��$

� ��!($ �� $%#�%!#$ %! �&�� "�� ! �&�%�"�� $�#'�#$

$��&�%� �!&$�)

� ��$ �� $%#�%!#$ %! �&�� '��&�� "�� !�"! � %$

$��&�%� �!&$�) ! %�� $�#'�#

� �&""!#%$ %�� %) %! �&�� "�� ! ! � � %�#"#�$� $�#'�# � �

��"�!) %! � !%��# $�#'�# !� %�� $�� %)"�

� �#��%�$ ��$%!#) #��!#�$ %��% � �� ! �%!#� � �#!� %�� % (!#�$%�%�! �

$! %�� $%#�%!# �$ �� %! ��%�#�� (��% ��$ �� &��%

� �#��%�$ �!�"#�$$�� $ � � �!��$ %�� ! %! %�� "�!)�� % $�#'�# �!#

��$��# ��$%�#� � %! ��

� �&""!#%$ �!%� �&�� &"��%� "��$

� �#!'��$ #�$%�#% ��"��%��$ �!# �&��$ %��% �! !% �!�"��%� $&��$$�&��)

You can install the following objects on an enterprise server:

� &$� �$$ �& �%�! $

� &$� �$$ '��($


B73.3.1 (6/99) 5–65

� ��-� ,-+.�-.+ ,

� ��& , �$(,-�&&�-$)( �) , ()- �+ �- -# -��& $( � ��-��, $- )(&1 *.,# ,

-# ,* �$!$��-$)(, �(� -��& # �� + !$& , -) -# , +/ +�

� ��-�# �**&$��-$)( ,* �$!$��-$)(, ��)-# - '*&�- , �(� / +,$)(,�

� �**&$��-$)( ,* �$!$��-$)( + �)+�,

Since server packages are assembled and defined in the same way as client workstationpackages, you can assemble a server package (using Package Assembly) and build theserver package (using Package Build) at the same time you assemble and build clientworkstation packages.

The following describes what actually happens during the build process after you haveassembled the server package and defined the package build:

1 After the build process starts, OneWorld creates packed TAM files.

2 A server package batch application is submitted locally.

3 This batch application calls a business function, which in turn calls the serverpackage engine.

4 The build engine uses records created by the Package Assembly Director andPackage Build Director to do the following:

� �($-$�&$2 �$+ �-)+$ , )( ��# , +/ +

� � "$( -+�(,! ++$(" *��% � �� !$& ,� �, ��# *��% � !$& $,

-+�(,! ++ �� ( .(*��% *+)� ,, ,-�+-, )( -# , +/ +�

� �+�(,! + �&& �.,$( ,, !.(�-$)( ,).+� �(� # �� + !$& , -) -# , +/ +�

�- -#$, -$' -# �.$&� ("$( + ��, -# �� -��& -) � - +'$( -#

�� $( 0#$�# ��# ')�.& � &)(",� ��)+ -# �� &$�+�+1� �

,* �$�& !.(�-$)( $, ��&& � -) �$+ �- -# -+$"" + &$�+�+1 $( 0#$�# -#

')�.& � &)(",� �( -#$, ��, -# �� -��& $, ()- ., ��

� �-�+- � �.$&� '�,- + *+)� ,, )( -# , +/ + 0# ( �&& �.,$( ,, !.(�-$)(

,).+� $, -+�(,! ++ �� #$, �.$&� '�,- + ,-�+-, )( )+ , / +�&

$(�$/$�.�& �.$&� *+)� ,, , ,$'.&-�( ).,&1� ��# �� #�, $-, )0(

�.$&� *+)� ,,� �# (.'� + )! *+)� ,, , -#�- +.( ,$'.&-�( ).,&1 $,

� - +'$( � �1 � �� !$& , --$("�

� �)/ -# *+)� ,, -) �()-# + , +/ +� $! )( 0�, ,* �$!$ � �.+$(" -#

*��%�" �.$&� *+)� ,,� �# *+)� ,, -+�(,! +, �(� �.$&�, �&&

�)'*)( (-, )( -#�- , +/ +�

� # �% -# ,-�-., )! ��# �.$&� *$ � )( ��# , +/ + �!- + -# �.$&�

*+)� ,, #�, � ".( )( �&& , +/ +,� �$,-)+1 + �)+�, �+ .*��- � �, -#

,-�-., , �#�(" �

� )'*+ ,, -# *��%�" �)'*)( (-, �(� *.- -# �)'*+ ,, � !$& , )(

-# � *&)1' (- , +/ + 0# ( �.$&�$(" $, �)'*& - � ��#$, #�** (,

)(&1 $! �)'*+ ,,$)( 0�, ,* �$!$ � 0# ( -# *��%�" 0�, �.$&-

-#+)."# -# ��%�" �.$&� �**&$��-$)(�� #$, *+)� ,, $, + * �- � !)+

�&& , +/ +,�

Package Management

5–66 B73.3.1 (6/99)

JDE.INI Settings for Server Package Builds

If your server package includes business functions, the BSFN BUILD section of theJDE.INI file applies to the package. The following example illustrates a typical entry:

[BSFN BUILD]BuildArea=/u17/j5482820/b73.3/appdev/packagesOptimizationFlags=+O2DebugFlags=–g –y –D_DEBUG –DJDEDEBUGInliningFlags=DefineFlags=–DKERNEL –DPRODUCTION_VERSION –DNATURAL_ALIGNMENTompilerFlags=–Aa +w1 +z –cOSRleleaseLevel=+DAportableLinkFlags=–b –zLinkLibraries=SimultaneousBuilds=0

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�;02+ �8,(�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�;98�54,=582+�) �6(*1(.,9ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

"/, 25*(:054 54 :/, 9,8<,8 =/,8, :/, 6(*1(., =022

), );02:�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�6:030@(:054 �2(.9�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�� +,-(;2: -58 ��

B� �+,-(;2: -58 !�� (4+

!;4�

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�(*/04, +,6,4+,4:� "/,9, *53602, -2(.9 (8, ;9,+

=/,4 );02+04. );904,99 -;4*:0549 04 A ,2,(9,�

35+,� &5; 9/5;2+ 45: */(4., :/,9, -2(.9�

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�,);.�2(.9� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

B. B? B�'��#�

'��#� �+,-(;2: -58

��

B. B7-;26(:/ B7+),>:8(

B�'��#� B��#�

�+,-(;2: -58 !��

B. B�'��#� B��#�

�+,-(;2: -58 !;4�

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�(*/04, +,6,4+,4:� "/,9, *53602, -2(.9 (8, ;9,+

=/,4 );02+04. );904,99 -;4*:0549 04 A�,);.�

35+,� &5; 9/5;2+ 45: */(4., :/,9, -2(.9�

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�420404.�2(.9� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

)2(41 �+,-(;2:� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

&,9 :;849 54 0420404. 54 :/, �!�� 5 :;849 0: 5--�

"/09 ,4:8? 09 )2(41 -58 454B�!�� 9,8<,89�

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�,-04,�2(.9� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

B��

B�� #�"��'$� !��

B��"# ��'��"

B�'��#%B!�# �� +,-(;2: -58

��

B��

B�� #�"��'$� !��

B��"# ��'��"

�+,-(;2: -58 !��

B��

B�� #�"��'$� !��

B��"# ��'��"

B�'!#�B!�# �� +,-(;2: -58

!;4�

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ


B73.3.1 (6/99) 5–67

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�:8;470=�7,2>�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

F�, �B �E F. �/01,@7? 1:=

�#��

F<,7429�9,?@=,7 F<17,2�� F.

�/01,@7? 1:= $%��

F<>;477��

F84>,7429 ��#�� /01,@7? 1:=

%@9�

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

,.3490 /0;09/09?� ',74/ .:8;470= 17,2>�

&30 >;477 17,2 >0?> ?30 >?,.6 >;,.0 B309 -@>490>>

1@9.?4:9> ,=0 .:8;470/� �� /B,=/> 3,> 1:@9/

?3,? � 4> ,/0<@,?0 ?: .:8;470 ?30 /074A0=0/

-@>490>> 1@9.?4:9>�

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

"%$070,>0�0A07� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

��;:=?,-70

�<�� 1:= ��)�

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

$070,>0 70A07 D:@ ,=0 .:8;47492 ?:� *:@ >3:@7/ 9:?

.3,920 ?30>0 17,2>�

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�496�7,2>�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

F- FE �/01,@7? 1:= �#��

F-7��D:@= >D>?08

/4=0.?:=D��-49��1@9.?74>?�48;

F- �%$� F-0C;,77 F-=?7 F7.

F-909?=D F�� @>=��D:@= >D>?08

/4=0.?:=D��74- F75/074- F75/06=97

F75/090? F-7:,/8,;�7:,/8,;

�/01,@7? 1:= $%��

F� ��"$��+�" ��74-

�/01,@7? 1:= %@9�

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

,.3490 /0;09/09?� &30>0 17,2> ,=0 @>0/ B309

7496492 -@>490>> 1@9.?4:9>� *:@ >3:@7/ 9:? .3,920

?30>0 17,2>�

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�496�4-=,=40>� ÑÑÑÑÑÑÑÑÑÑ

ÑÑÑÑÑÑÑÑÑÑ-7,96 �/01,@7?� ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ�4-=,=40> ?: B34.3 -@>490>> 1@9.?4:9> ,=0 74960/�

�(49/:B> !& ,9/ �%� >0=A0=> :97D��ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

%48@7?,90:@>�@47/>�ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�@97484?0/� �/01,@7?�

,9D 49?020= �9@8-0= :1

>48@7?,90:@> -@47/>�

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

�9/4.,?0> ?30 9@8-0= :1 ��> ?3,? .,9 -0 -@47? ,? ,

?480� " 80,9> ?3,? ,77 B477 -0 -@47? >48@7?,90:@>7D�

For more information about the JDE.INI file, see the System Administration guide.

Package Management

5–68 B73.3.1 (6/99)

B73.3.1 (6/99) 5–69

Working with Package Build History and Logs

The Package Build History application allows you to view information pertaining to thebuild process, including the options and objects you specified when you created thebuild definition.

This application provides the following build information:

� ��

� ��

� ��

� ��

� ��

� ��

� ��

� ��

In addition, the Form menu’s View Logs option allows you to view four logscontaining additional information about the build process. These logs are useful in theevent that the build does not complete successfully and you need to know the errorsthat occurred during the build.

If a build does not complete successfully, you can use the Resubmit Build option toresume the build from the point where the process stopped. Only the business functionsand objects that did not build successfully will be built; the entire package will not berebuilt.

In some cases, if a build is interrupted or otherwise unable to complete, you may needto reset the build status from Build Started to Build Definition Complete. Unlike theResume Build feature which continues the build from the point where it failed,resetting the status enables you to start the build process from the beginning.


� ��

� ��

� ��

� ��

Package Management

5–70 B73.3.1 (6/99)

Viewing the Package Build History

OneWorld maintains a history of the package build in the F96225 Build Detail Historytable. This table contains details about any package components that failed to buildsuccessfully.

If you encountered errors during the build process and your package failed to buildsuccessfully, you can resubmit the package and continue building at the point at whichthe build failed. In this situation, OneWorld checks the F96225 table and rebuilds onlythe business functions or other package components that have a status of “Not Built” or“Error.”

In other words, OneWorld builds only the package components that failed to buildsuccessfully, not the entire package. This feature can save you a tremendous amount oftime, especially if only a few package components failed to build successfully.

If you originally specified package compression, when you resubmit the package toresume building, directories are automatically compressed after building successfully.

To view package build history


1. Select Package Build History (P9622). The Work with Package Build Historyform appears.


B73.3.1 (6/99) 5–71

2. Select CLIENT or the server name to display information about the current buildstatus for those machines. You can also expand the tree to view the followinginformation:

� ��

� ��

� ��

� ��

These options and objects are the ones you specified when you created thepackage’s build definition. For example, if you elected to build only selectedspecifications, you can determine the status for each specification, as well asother pertinent information.

3. When you are finished viewing build history information, click Close.

Viewing Logs

After you build your package, you can view logs that list any errors that occurredduring the build process. In particular, you can view the following logs:

� � ��

� � ��

� ��

� ��

Each log contains a header which includes the package name, date, build machine, andpath code.

To view a log

On the Package Build (GH9083) menu


2. Choose View Logs from the Form menu. The View Logs form appears.

Package Management

5–72 B73.3.1 (6/99)

3. Click any of the following log options:

� ��

� ��

� ��

� ��

4. Click OK. Each log you selected will be generated when building is complete.

5. Click Cancel to return to the Work with Package Build History form.

Field Explanation

Package Statistics This option allows you to view count and size statistics for thepackage directories that were built.

Package Build Log This option allows you to view errors that may have occurredduring a package build. These errors could have occurred whilebuilding the specification files or the objects for the package.

Business Function Errors This option allows you to view the results of the businessfunction build for this package. Both errors and warningsdisplay in this report. A summary appears at the end of thereport that indicates how many errors and warnings occurredfor each dll. Use this information to determine if a rebuild isnecessary.


B73.3.1 (6/99) 5–73

Field Explanation

Missing Business FunctionSource

This option lists all source members that were not availablewhen the business function was created. The programattempted to find these members because each had a record inthe Object Librarian table (F9860). However, a matchingsource could not be found in the source directory. To resolvethese errors, either delete the Object Librarian record orprovide a source member.

Where to Find the Error Logs

Error logs are stored on the deployment server in directories beneath the package itself.The Package Build log is stored in the package directory. The Package Statistics log,Business Function Source Errors log, and Missing Business Function Source Errors logare stored in the package’s work directory.

You can view the error logs by going to the appropriate directory and opening the logwith Microsoft’s Notepad or a similar application that allows you to display text files.

In the following examples, PRODB733FA is used as the package name. To determineyour actual directory, substitute your package name for “PRODB733FA.”

� �� "��!��

� �� !�� !��

� �!�� !�� "��!�� #

� �� !�� !�� !�� "��!�� #

The Package Statistics Log

The Package Statistics log summarizes the outcome of the package build, showingstatistics for the directories in the package, including the size and file count of eachdirectory. This report also shows a breakdown of the files in the spec directory and thesize of each spec file, as well as the total count and size. The purpose of this report isnot only to provide information, but to verify that the package was built successfully.

Package Management

5–74 B73.3.1 (6/99)

The Package Statistics log looks similar to this:

The Package Build Log

The Package Build log can be found in the package name directory. This log lists thesteps executed in building the package, as well as any errors that occurred during thepackage build process. It also describes the steps involved in building the package. Thefinal page of the log tells you whether the package was successfully built.

The Package Build log looks similar to this:


B73.3.1 (6/99) 5–75

Error and warning messages are preceded with the word “ERROR” and “WARNING”respectively. All other messages are informational messages that describe the steps inthe build process. If the build process fails, you can use this log as a troubleshootingtool to determine the last step that executed before the failure.

For example, following are some steps from the log and some troubleshootingsuggestions to follow if the build fails during or after the step:

� �&�� #��%!#��$ �!# �� !�"��%�

A failure at this point means that the directories in the package could not bebuilt. If this occurs, make sure the server did not go down. Also, make sure youhave authority to create directories in the package directory.

� �&�� %�! ��$%

This step builds a list of all items defined in the package. If the build fails at thisstep, make sure the package is defined in the F9886 table.

� �#��%� �"%( �� $"��$

This step creates the local workstation specifications (TAM tables) in thepackage directory under the specs directory. If you get a failure here, make surethe server didn’t go down. Also, make sure you have permission to createdirectories in the spec directory.

� �!"( �� $!&#�� &�� !�� '!#� �!# �&�� "��

This step copies the lib32, source, include, obj, make, and work directories fromthe check-in location to the package directory. If you receive a failure at thispoint, make sure that each of these directories exist in the check-in location andunder the package directory.

� �!"( �� '!#� �!# ��#%�� "��

This step copies the lib32, make, and work directories form the check-in locationto the package directory. If you receive a failure at this point, make sure thateach of these directories exist in the check-in location and under the packagedirectory.

� �"�� &

� �"�� $��

These two message go together. If you receive the “begun” message but not the“finished” message, this means the spec file was not built. After the package isfinished you need to build just the one TAM spec file that failed. (There willprobably be an entry in the log that there was an error building that TAM specfile.)

Package Management

5–76 B73.3.1 (6/99)

The Business Functions Errors Log

The Business Functions Errors log allows you to view any errors that occur whilebusiness functions are being built. The final page of the log describes whether thebusiness functions were successfully built or built with errors. Business functions inthis report could be business functions that are still in development and have not yetbeen checked in. If they have never been checked in, they will not have source andtherefore will be listed in the missing source log.

The Business Functions Errors log looks similar to this:

The Missing Business Function Source Errors Log

The Missing Business Function Source Errors log describes any business functions inthe package that are defined in the Object Librarian and have a record, but could not bebuilt because there was no source.


B73.3.1 (6/99) 5–77

The Missing Business Function Source Errors log looks similar to this:

Server Logs

All compile logs for the enterprise server are located on the server itself in the sourcedirectory of the DLL that the object belongs to. For example, suppose you want to seethe log for the Sales Order Entry master business function (B4200310) in the packagePACKAGE1 on an HP9000 whose BuildArea is /u02/OneWorld/packages. Therewould be a file called/u02/OneWorld/packages/PACKAGE1/source/CDIST/b4200310.log, since B4200310is in the CDIST.DLL.

If there were a problem with the linking of the CDIST.DLL (shared library) on theHP9000, there would be a file called/u02/OneWorld/packages/PACKAGE1/obj/CDIST/CDIST.log.

On the AS/400, logs for business functions that failed to compile are members in a filecalled FAILED in the package library. Using the previous example, you would look atmember B4200310 of the FAILED file in library PACKAGE1.

Resubmitting a Package Build

The following task describes how to resubmit a package build in the event that allobjects or business functions did not build successfully.

Package Management

5–78 B73.3.1 (6/99)

To resubmit a package build



2. Find and select the package you want to resubmit. When doing this you can havetwo options:

� �� " ��

� �� " �� !��

3. Choose Submit Build from the Row menu.

4. Choose a destination for the build report, and click OK:

� � ��

� ��

The form automatically closes and OneWorld begins building the package. Buildtime varies, depending on the number and size of the items in your package.When the build is finished, the report will either display or print, depending onthe destination you specified.

5. Review the report to make sure that all components in your package weregenerated successfully. If the report indicates any errors, review the error logsfor more detail.

If the package build completes successfully, you can schedule the package fordeployment as described in ��.

Changing the Build Status

In some cases, you may need to attempt rebuilding the package rather than trying toresume the build from the point where the build failed. Before you can do so, you mustfirst change the package’s build status from Build Started to Build DefinitionComplete.

When you reset the package’s build status, you have the option of resetting status forthe server only, or for all servers and client workstations for which you want to buildthe package.


B73.3.1 (6/99) 5–79

To change the build status



2. Find the package whose status you want to reset. Underneath the package name,select the server or servers and client workstation for which you want to buildthe package.

3. Choose Advanced from the Work with Package Build Definition form’s Rowmenu. The Advanced Revisions form appears.

4. Click Reset to change the package’s build status from Build Started to BuildDefinition Complete.


6. If desired, select the package name and choose Submit Build from the Workwith Package Build Definition form’s Row menu.

Package Management

5–80 B73.3.1 (6/99)

B73.3.1 (6/99) 5–81

Understanding Package INF Files

The Package INF file is essentially the interface between the package build andWorkstation Installation. The INF file defines the components included in the package,the source and destination paths for those components, and the attributes needed toinstall the package.

The INF file is created during the package build process and is stored in its own“package_inf” directory based off of the release master directory. WorkstationInstallation reads the INF file for the package it is installing to determine whichcomponents are loaded to a workstation, as well as location.

Sample INF File

The following is a typical INF file for package PRODB733FA, which is full package Afor the PRODB733 path code.

[Attributes]

This section contains information about the current OneWorld release, global tables,specification and help files, and the JDE.INI file.

Item Purpose

PackageName=STEST Indicates the name of the package.

PathCode= Indicates the path code for which the package isbeing built.

Built= Indicates the package’s status. A status of 50 or 70means the package is ready for installation.

PackageType=Full Indicates the package type: full, partial, or update.

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Release=B733ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Indicates the current OneWorld release, whichdetermines which setup.inf file to use in building thejde.ini for the workstation. The release is also usedto determine paths for system and helps.

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

SystemBuildTypeÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Indicates the type of build: DEBUG or RELEASE.ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

MFCVersionÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Indicates the version of the MFC compiler.

Package Management

5–82 B73.3.1 (6/99)

Item Purpose

SpecFilesAvailable=Y Indicates that specification files are available tomerge or copy. This flag is always Y for full orpartial packages. For update packages, this flag is Yonly if there are objects in the package.

DelBlblTbl=Y Indicates whether to delete global tables wheninstalling. This flag will be set to Y for full or partialpackages. For update packages, this flag is Y only ifthe objects include a table object.

ReplaceIni=Y Determines whether to delete the existing jde.ini filewhen installing, and then create a new one. This flagis set to Y for full and partial packages. For updatepackages, the user must specify during packagebuild definition whether to replace the jde.ini file.

AppBuildDate=Mon Jul 20 11:22:221998

Indicates the date and time the package was built.Full and partial packages always have this date. Thisis blank when there are no objects included in thepackage.

FoundationBuildDate=Wed Jun 0315:08:34 1998

Indicates the date and time the foundation(oexplore.exe) was built. Full and partial packagesalways have this date. This is blank when there are isno foundation location specified in the package.

DataBuildDate=Wed Jun 03 15:08:341998

Indicates the date and time the database (locdata.jz,the compressed data file,) was built. Full and partialpackages always have this date. This is blank whenthere are is no database location specified in thepackage.

HelpBuildDate=Wed Jun 03 15:08:341998

Indicates the date and time the help (help.jz, thecompressed help file,) was built. Full and partialpackages always have this date. This is blank whenthere are is no help location specified in the package.

DeploymentServerName Indicates the machine name of the deploymentserver.

Location Indicates the location of the machine (deploymentserver).

DeploymentStatus= Indicates the package deployment status.

PackageDescription= Indicates the package description.

Icon Description A description of the desktop icon.

Default Environment Indicates the default environment.

Spec Indicates the name of the spec file specified in theFile set.


B73.3.1 (6/99) 5–83

Item Purpose

ServerHelpPath Indicates the path to the help files.

[SrcDirs]

Workstation Installation uses these settings to determine the source path from whichinformation is copied. A package build compresses these directories. WorkstationInstallation copies the compressed directories to workstations.

Item Purpose

S<Pathcode>=\\MachineName\ONEWORLD\B733\PACKAGE\PRODB733FA

Indicates the location of the package that thepackage build will compress for WorkstationInstallation. This path automatically defaults to thepath code directory over which you built thepackage. You may change this setting if you want adifferent package pulled down.

��

Indicates the location of the system directory that thepackage build will compress for WorkstationInstallation. This path automatically defaults to thesystem directory associated with the path code overwhich you built the package. Normally this would beunder the release share name (B733). This itemappears only when included in the package.

S<Pathcode>DATA=\\MachineName\ONEWORLD\B733\PRODB733\PACKAGE\DATA

Indicates the location of the Microsoft Accessdatabase that the package build will compress forWorkstation Installation. This path automaticallydefaults to the data directory beneath the path codeover which you built the package. This item appearsonly when included in the package.

SHELP=\\MachineName\ONEWORLD\B733\HELPS

Indicates the location of the help files that thepackage build will compress for WorkstationInstallation. Users may not want to take up the diskspace to have helps on their workstation. When youbuild a package this setting defaults to the helpdirectory under the release share path (B733). Youmay change this setting if you want to change thelocation in which helps will reside. This itemappears only when included in the package.

Package Management

5–84 B73.3.1 (6/99)

[DestDirs]

Workstation Installation uses these settings to determine the destination paths on theworkstation. The process replaces “%INSTALL” with the user’s machine configurationthat is set up in user profiles (F00921) and Configuration Path Detail (F00051).

Item Purpose

D<Pathcode>=%INSTALL\<pathcode>

Indicates the destination directory for the package.

DSYS=%INSTALL\system Indicates the destination directory for system files.This item appears only when included in thepackage.

D<Pathcode>DATA=%INSTALL\<path code>\data

Indicates the destination directory for the database.This item appears only when included in thepackage.

DHELP=%INSTALL\helps Indicates the destination directory for help files. Thisitem appears only when included in the package.

[Filesets]

This section lists the various source and destination directories under the path code forthe package. Y=compressed, and N=not compressed. The source and destinationdirectory names are preceded by an S and D respectively.

Item Purpose

<Pathcode>1=Y, $S<pathcode>\bin32,$D<pathcode>\bin32

Indicates the bin32 directory under the pathcode.

<Pathcode>2=Y, $S<pathcode>\res,$D<pathcode>\res

Indicates the res directory under the path code.

<Pathcode>3=Y, $S<pathcode>\spec,$D<pathcode>\spec

Indicates the spec directory under the pathcode.

<Pathcode>4=Y, $S<pathcode>\include,$D<pathcode>\include

Indicates the include directory under the pathcode.

<Pathcode>5=Y, $S<pathcode>\lib,$D<pathcode>\lib

Indicates the lib directory under the path code.

<Pathcode>6=Y, $S<pathcode>\obj,$D<pathcode>\obj

Indicates the obj directory under the path code.

<Pathcode>7=Y, $S<pathcode>\source,$D<pathcode>\source

Indicates the source directory under the pathcode.


B73.3.1 (6/99) 5–85

Item Purpose

<Pathcode>8=Y, $S<pathcode>\work,$D<pathcode>\work

Indicates the work directory under the pathcode.

<Pathcode>9=Y, $S<pathcode>\make,$D<pathcode>\make

Indicates the make directory under the pathcode.


<Pathcode>DATA=Y,$S<pathcode>DATA\data.CAB,$D<pathcode>DATA


Indicates the compressed Microsoft Accessdatabase that the package build generates.

HELP=Y, $SHELP\Helps.CAB, $DHELP Indicates the compressed helps file.

[Components]

These settings indicate the location of the foundation, production and developmentobjects, the database, and help files.

Item Purpose

ProdObj=APPL_PKG1, APPL_PKG2,APPL_PKG3

Indicates the location of production objects.

DevObj=APPL_PKG4, APPL_PKG5,APPL_PKG6, APPL_PKG7,APPL_PKG8, APPL_PKG9

Indicates the location of development objects.

Foundation=SYS Indicates the foundation location.

Data=<pathcode> DATA Indicates the database location.

Help=HELP Indicates the helps file location.

[Typical]

This section describes a typical development user’s settings.

Item PurposeÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Name=DevelopmentÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Indicates that the package is for a development user.

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Description=Install the developmentobjects

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Indicates package description.


Components=ProdObj, DevObj,Foundation, Data

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Indicates that the package should contain bothproduction and development objects, as well as thedatabase and foundation. See the “Components”settings to determine the location of thesecomponents.

Package Management

5–86 B73.3.1 (6/99)

[Compact]

This section describes a typical production user’s settings.

Item PurposeÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Name=ProductionÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Indicates that the package is for a production user.

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Description=Install the productionobjects

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Indicates package description.


Components=ProdObj, Foundation,Data

ÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑÑ

Indicates that the package should contain onlyproduction objects, as well as the database andfoundation. See the “Components” settings todetermine the location of these components.

[ODBC Data Sources]

This section describes the ODBC data source.

Item Purpose

Access32=Microsoft Access Driver(*.mdb)

This line will be included in the ODBC data sources.

This setting is determined by two registry settings onthe build machine: LocalDS (the local data sourcename), and DataByPathCode (1=true, 2=false). If theDataByPathCode setting is set to 1 (true), the itemname for this setting is <LocalDS> – <Pathcode>.

[Access32]

This section contains information about the local data source. The name of this sectioncorresponds to the local data source name in the ODBC Data Sources section. Forexample purposes, the local data source name used is Microsoft Access 32 database.

Item Purpose

Driver=odbcjt32.dll Indicates the name of the driver.

DefaultDir=C:\ACCESS Indicates the default directory.

DriverId=25 Indicates the driver ID number.

FIL=MS Access Required attribute setting for Microsoft Access.


B73.3.1 (6/99) 5–87

Item Purpose

JetIniPath=odbcddp.ini Required attribute setting for Microsoft Access.

UID=admin Required attribute setting for Microsoft Access.

Driver32=odbcjt32.dll Indicates the ODBC driver for Microsoft Access.

DBQ=$DAPPL_PGFDATA\jdeb7.mdb

Indicates the path code for the Microsoft Accessdatabase.

Package Management

5–88 B73.3.1 (6/99)

Deployment

Package Management

5–90 B73.3.1 (6/99)

B73.3.1 (6/99) 6–1

Deployment

After you have assembled, defined, and built a package, there are several ways todeploy the package to workstations and servers.

This section contains the following topics about deploying changes to bothworkstations and servers:

� ��

� � ��

� ��

� � ��

� ��

� ��

Package Management

6–2 B73.3.1 (6/99)

B73.3.1 (6/99) 6–3


After you build a package there are several methods available for deploying thepackage to workstations and servers throughout your enterprise. For workstations, themethod you select depends on whether OneWorld is installed.


� ��

� ��

� ��

� ��

� ��

Deployment to Workstations without OneWorld

If a workstation does not currently have OneWorld loaded, you can deploy the packagethrough the Workstation Installation program. Workstation Installation is used todeploy only full and partial packages; you cannot use Workstation Installation todeploy an update package to a workstation that doesn’t have OneWorld installed.

Workstation Installation retrieves the items specified in the package. A package is likea bill of materials or a kit with instructions for where to pull all of the necessarycomponents the Workstation Installation program deploys to the local workstation. Thisprogram can be run interactively (initiated by a person at a workstation) or in silentmode and scheduled through the push installation feature. For more information aboutthe Workstation Installation application, see the OneWorld Installation Guide.

You can use Package Deployment to deploy the package if you use the push installationfeature. Push installation enables the OneWorld administrator to “push” a package fromthe deployment server to workstations without requiring any user interaction. In orderto use this feature, the push installation “listener” must be installed on the workstation,and the machine must be defined through the Machine Identification application(P9654A). For more information about push installation, see �� in this section.

Package Management

6–4 B73.3.1 (6/99)

Deployment to Workstations with OneWorld Already Loaded

To reload a new package (full, partial, or update) on workstations that already haveOneWorld installed, use one of two methods: Workstation Installation or PackageDeployment.

After you assemble and build a package, use Package Deployment to schedule thepackage for deployment to individual workstations or to selected groups. On thespecified deployment date, when the users scheduled to receive the package sign on toOneWorld, they are given the opportunity to load the package.

Unless you are using the push installation feature, Package Deployment requires thatOneWorld be already loaded on the workstation. You can schedule either a new full orpartial package to replace the existing package, or an update package to be merged withthe existing package on the workstation.

There are advantages to both deployment methods. Workstation Installation is a goodmethod to use when you want to install a package immediately or soon after it is built,without having to schedule the package. On the other hand, Package Deployment isuseful if you need to control when the package becomes available, if you want to makethe package installation mandatory, or if you want to deploy the package to servers aswell as workstations.

Deployment to Servers

Servers receive the same package you build for the workstation, but in a differentformat. When you assemble the package and create the package build definition, youcan specify the servers to which you want to deploy the package. Deployment isaccomplished via the Package Deployment application, which uses the same schedulingmechanism used to deploy packages to workstations. In fact, you can easily scheduledeployment to both client workstations and servers on the same form. (Note that youcannot use the push installation feature for deploying to servers.)

Deployment to Tiered Deployment Locations

Multitier deployment allows you to install software on workstations from more thanone deployment location and more than one deployment machine. Use this deploymentmethod if your site has more than 50 workstations performing OneWorld softwareinstallations per day, or when workstation installations over your WAN are too slow.For information about multitier deployment, see � �� .

Deploying to Workstations from CD

If your system has a CD writer, you can define the CD writer as a deployment location.Doing this essentially defines the CD writer as a pseudo deployment server from which


B73.3.1 (6/99) 6–5

you can copy a OneWorld package onto a blank CD. You can then use this CD to installOneWorld on workstations by using the Workstation Installation program contained onthe CD.

The process of deploying to workstations from CD consists of the following steps:

� ��

� ��

� ��

� ��

For more information about deploying from CD, see �� .

Package Management

6–6 B73.3.1 (6/99)

B73.3.1 (6/99) 6–7

Defining Machines, Locations, and Deployment Groups

Before you deploy packages, you should make sure that the workstations, servers,groups, or locations that will receive your package are defined. Doing so ensures thatwhen you are ready to schedule packages via the Package Deployment Director, themachines, groups, or locations you want to receive your package will be available aspackage recipients.

A deployment group is a group of workstations classified by a criterion such as jobfunction, team, or any other grouping you specify. For example, you might have asoftware development group, a testing group, a production group, and so on.

A location is a group of workstations and servers that corresponds to a literal location.For example, you might have locations for Corporate and Branch, or for Building 5 andBuilding 7. Locations are also useful if you use multitier deployment or deploy across awide area network. In this case you might have a location defined for each of yourgeographic locations.

The Machine Identification application enables you to define or revise machines andlocations in your enterprise.

The Machine Group Identification application enables you to define or revise groupscomprised of several workstations.

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

When you enter a machine definition you are really defining its usage. For example, adeployment server can be used as a data server. When you enter machine definitions,keep in mind the following recommendations from J.D. Edwards:

� � ��

� ��

� � � ��

� � � ��

� � � ��

��

Package Management

6–8 B73.3.1 (6/99)

This chapter contains the following tasks:

� �� $

� �� !��%�! $

� �� "�� "�!)�� % �#!&"$

Defining Machines

Before you use the Package Deployment Director to deploy a package to individualclient workstations, make sure that each machine that will receive the package has arecord in the machine master table (F9650).

There are two ways to populate this F9650 table:

� �� &��)� �$� %�� %��%�! �""��%�! %! �� &��) � %�#

�� ( �� %��% ��$ �'�# $�� ! %! � ��!#��

� &%!��%��)� � ��!#�� &%!��%��) �#��%�$ � #��!#� � %�� %��

(�� &$�# ! � �( �� $�� $ ! %! � ��!#�� !# %�� #$% %��

�� %�� $ ��$! &"��%�� %�� "�#$! $�� $ ! %! %��

(!#�$%�%�! ��

The simplest way to populate the F9650 machine master table is to have all users onnew machines sign on to OneWorld. In cases where you need to deploy a packagebefore this can happen, you must manually enter machine information as described inthe following task. The Machine Identification application enables you to do just that.

In addition to defining workstations, you can also use the Machine Identificationapplication to enter or revise definitions for the following machines:

� �"�!)�� % $�#'�#$

� � %�#"#�$� $�#'�#$

� �%� $�#'�#$

� ��'� �""��%�! $�#'�#$

� �� !($ %�#�� $�#'�#$

You can define a machine to be a single usage machine and a data server (or as a dataserver only), but no other combinations are allowed. For example, you cannot define amachine as a workstation and a deployment server.

You can enter or revise definitions for these machines in multiple locations, includingremote locations. For more information about setting up locations rather than machines,see �� .


B73.3.1 (6/99) 6–9

To define a machine


1. Choose Machine Identification (P9654A). The Work With Locations andMachines form appears.

2. Underneath the appropriate location, select the type of machine you want to add:

� ��

� ��

� ��

� ��

� ��

� ��

3. Click Add to add a new machine. The Machine Revisions form appears. Thisform displays different fields depending on the type of machine you are adding.

Package Management

6–10 B73.3.1 (6/99)

4. On the Machine Revisions form, complete the following fields:

� ��

� ��$�#�"%�!

� ��$�

� �!$% �)"� � !# �(��"�� %�� $! ! �

� �#��#) �$�# �� !� %�� $ "#��#) &$�#��

5. The tab corresponding to the type of machine you are defining displaysautomatically. Enter the fields for the machine you are defining:

Workstation:

� ��"�!)�� % ��#'�# �� $"��)*! �) ��

Deployment [Server]:

� �#��#) ��"�!)�� % ��#'�#

� ��#'�# ��#� ��%�

If you have set up a primary deployment server, the Primary DeploymentServer field will not be accessible when you define a new deploymentserver. This field can be modified only when you are revising the theprimary deployment server definition, or when you change your primarydeployment server to a secondary server. In this case you could specify adifferent server as your primary deployment server.


B73.3.1 (6/99) 6–11

Enterprise [Server]:

� ��

� ��

� ��

� � ��

� ��

� � ��

Data [Server]:

� ��

JAS [Server]:

� ��

WTS (Windows Terminal Server):

� ��

When you define an enterprise server, Form menu options enable you togenerate installation scripts, generate and populate server map tables, and use theObject Configuration manager (OCM) to update the workstation server map. Foran enterprise server you can also display the machine environment anddescription.

When you define a deployment server, Form menu options enable you to selectpath codes, data items, foundation modules, and help items for the deploymentserver.

6. Click OK to return to the Machine Revisions form. Click OK again to return tothe Work with Locations and Machines form.

7. To exit, click Close at the Work with Locations and Machines form.

The process for revising existing machine definitions is similar to adding a newdefinition. Instead of clicking Add on the Work with Locations and Machines form,find and select the machine whose definition you want to revise and click Select. Thesame revision form appears and allows you to change the machine’s definition.

Package Management

6–12 B73.3.1 (6/99)

Field Explanation

Machine Usage The purpose for this machine. For example: database server,logic server, TSE server, and so on.

Machine Name For World, the Location indicates the machine (server orclient).


Release For World, the release number as defined in the SoftwareVersions Repository.


Host Type Host Machine Type.

Location The name of the deployment location.

Primary User The primary user for the listed machine.

Server Map Data Source The data source name.

Deployment Server Name The name of the specific server that is being used fordeployment.

Primary Deployment Server This field specifies whether a deployment server is the primarydeployment server for a specific location.

Database Type The type of database.

Logical Machine Name The logical machine name assigned to this unique machine andport. A machine can be a workstation. Because you can havemore than one instance of OneWorld running on a givenmachine, you must assign a logical machine name thatidentifies the unique physical machine name and port wherethis instance runs. J. D. Edwards recommends that the logicalmachine name represent the release and purpose of themachine, such as Financial Data Server-B73.3 or DistributionLogic Server-B73.3.

Package Date / Time The date and time a full package was deployed to a specificworkstation.


B73.3.1 (6/99) 6–13

Field Explanation





System Update Date / Time The date and time the current system was deployed to thespecified workstation.

Package Update Date / TimeThis field represents the date and time of the most recentupdate package installation on the specified workstation.

Package Update Name This field represents the name of the most recent updatepackage that has been deployed to the specified workstation.

Port Number Identifies the port for a given instance of OneWorld. Becausethe JDE.ini file controls the port to which a workstation willconnect, for workstations this port number is for referenceonly.

Server Share Path For World, the Server Share Path Field is used by theenvironment to determine the location of the current server.

For OneWorld, this field indicates the shared directory for thisPath Code. The objects that are stored on a file server will befound in this path.

Defining Locations

In some cases, an enterprise may span several buildings, cities, or even countries. Inthese situations it is often easier to deploy a package to a location rather than toindividual workstations and servers. Then, a secondary deployment server at thelocation 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 tolocations. If you use multitier deployment to deploy packages to remote locations, theconcept of locations is crucial. (For more information about defining locations formultitier deployment, see � �� .)

Package Management

6–14 B73.3.1 (6/99)

In OneWorld terms, a location is essentially a user defined group of machines,databases, and environments. In some cases the location is an actual physical locationconnected by a wide area network (WAN), such as when you have remote offices thatare geographically separate from your main office.

For example, a location could be a floor in your office building, a separate building onyour corporate campus, a branch office across town, or a facility in another city.

Once you have created a new location you can add workstations and servers for thatlocation by defining the machine names associated with that location.

The topmost location that is displayed when you launch the Machine Identificationapplication is the base location. You cannot change or remove this base location, butyou can create or revise locations beneath it.

When you create a location beneath another location, the original location is known asthe parent location, and the location beneath as the child location. For example, if youhave a location called “Seattle” and then create a location called “Redmond” underSeattle, Seattle is the parent location and Redmond is the child location.

To define a location



2. Select the current location under which you want the new location to reside. Forexample, if you are adding a new remote location, select the Remote Locationsicon.

3. Click Add to add a new location. The Location Revisions form appears.


B73.3.1 (6/99) 6–15

On the Location Revisions form, enter the following fields:

� ��

� ��

� ��

� ��

4. After selecting the location, click Close to return to the Location Revisions form.Click OK to return to the Work with Locations and Machines form.

5. Click Close to exit from the Work with Locations and Machines form.

The process for revising existing locations is similar to adding a new location. Insteadof clicking Add on the Work with Locations and Machines form, find and select thelocation you want to revise and click Select. The same revision form appears andallows you to change the location.

Field Explanation

Location The name of the deployment location.

Location Code This field represents the current location for OneWorlddeployment.

Parent Location The name of the parent location.

Package Management

6–16 B73.3.1 (6/99)

Defining Package Deployment Groups

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

Package deployment groups are particularly useful in large enterprises where it wouldbe very time-consuming to schedule a package for deployment to several individualworkstations. In these environments it is much faster to create deployment groups.

A group can contain a subgroup (or group within a group). For example, you mighthave a group called “QA” within a larger “Development” group.

It will be helpful to the person who builds and schedules packages if deploymentgroups have easily identifiable names. For example, if you have a testing deploymentgroup composed of quality assurance specialists and programmers who are responsiblefor testing, it is better to name this deployment group “Testing” rather than “GreenTeam.”

The following task describes how to create a package deployment group.

To define a package deployment group


1. Select Machine Group Identification (P9652A). The Package DeploymentGroups form appears.


B73.3.1 (6/99) 6–17

2. To add a new deployment group, click Add. The Deployment Group Revisionsform appears.

3. Enter the deployment group name and description.

4. Enter the the workstations or deployment groups you want to include in thegroup. You can do this by manually typing the workstation name or group namein the Workstation field or Deployment Group field, or by using the visual assistfeature.

When you use the visual assist at the Workstation field, the Machine Select formappears. When you use the Deployment Group field’s visual assist, the PackageDeployment Group Search form appears.

5. Click OK when you are finished adding workstations or deployment groups. Youreturn to the Package Deployment Groups form.

6. Click Close to exit from the the Package Deployment Groups form.

Field Explanation

Deployment Group Name A profile used to classify users into groups for securitypurposes. Some rules for creating a User Class/Group are asfollows:

� ��

��

� ��

��

Deployment GroupDescription

The description for the selected deployment group.

Package Management

6–18 B73.3.1 (6/99)

Field Explanation

Workstation For World, the Location indicates the machine (server orclient).


Workstation Description A user defined name or remark.

Deployment Group This field represents a group that is defined to be part of aparent group.

Deployment GroupDescription

The description for the selected deployment group.

Revising a Deployment Group

The following task describes how to revise an existing package deployment group.

To revise a package deployment group


1. Select Machine Group Identification (P9652A). The Package DeploymentGroups form appears.

2. Choose the desired group and click Select. The Deployment Group Revisionsform appears.

3. When you revise an existing group you cannot change the group name, but youcan change the description.

4. Select the last row (the empty one) and enter the name of the workstation ordeployment group you want to add to the group. You can do this by manuallytyping the name in the Workstation or Deployment Group field, or by using thevisual assist at those fields.

When you use the visual assist at the Workstation field, the Machine Select formappears. When you use the Deployment Group field’s visual assist, theDeployment Group Search form appears.

5. Click OK when you are finished adding workstations or deployment groups. Youreturn to the Package Deployment Groups form.

6. Click Close to exit from the the Package Deployment Groups form.

B73.3.1 (6/99) 6–19

Working with the Package Deployment Director

After you define and build a package, use Package Deployment to schedule thepackage for deployment to individual workstations, deployment servers, or enterpriserservers. On the specified deployment date, users who are scheduled to receive thepackage are given the opportunity to load the package when they sign on to OneWorld.

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


� ��

� ��

� ��

� ��

Understanding the Package Deployment Director

The Package Deployment Director is designed to simplify and expedite the process ofscheduling built packages to workstations and servers. The director displays a series offorms that allow you to specify the package you want to deploy, the deploymentdestinations, and the deployment time.

After specifying the package you want to deploy, you specify any of the followingdestinations:

� ��

� ��

� � ��

OR

� � ��

� ��

Package Management

6–20 B73.3.1 (6/99)

You can deploy a package either to specific workstations and servers, or you canschedule the deployment based on deployment groups or location. You cannot do both;you must choose one method or the other.

On the specified deployment date, users who are scheduled to receive the package aregiven the opportunity to load the package when they sign on to OneWorld.

You also have the option of making the package mandatory, which means users cannotaccess OneWorld until they have installed the package. If the package is optional, userswill be given the option of installing the package every time they sign on to OneWorlduntil they either install or decline the package.

In addition, you can specify a “push installation,” which means the package can bepushed from the deployment server to the workstations you specify, without requiringany interaction from the user. For more information on push installation, see �� in this guide.

The Package Deployment Director requires that OneWorld be already loaded on theworkstation, unless you are using push installation. You can schedule either a new fullor partial package to replace the existing package, or an update package to be mergedwith the existing package on the workstation.

The Package Deployment Director uses the following tables:

� �� !%� ��)*�(

� �� !%� ��*�!#

� �� '#&.$�%* �(&+' ��(

� �� '#&.$�%* �(&+' ��*�!# ��!%!*!&%)

� �� '#&.$�%* �&��*!&% ��!%!*!&%)

� �� "�� '#&.$�%* �%�&($�*!&%

� �� "�� '#&.$�%* &% ��(,�()

� �� &�*-�(� ��"�� (

The following summarizes each of the Package Deployment Director’s forms and theirfunction:

� �� !�- * !) �&($ �&( � ��)�(!'*!&% &� * � ��"��

��'#&.$�%* �!(��*&(�

� �� )� * !) �&($ *& �!%� �%� )�#��* * � '��"��

.&+ -�%* *& ��'#&.�

� �� )� * !) �&($ *& )'��!�. * �

��)*!%�*!&% �&( .&+( '��"�� &+ ��% )�#��* !%�!,!�+�# �#!�%* -&(")*�*!&%)�

��'#&.$�%* )�(,�()� �%� �%*�('(!)� )�(,�()� &( .&+ ��% ��'#&. * �

'��"�� *& � ��'#&.$�%* �(&+' &( #&��*!&%�


B73.3.1 (6/99) 6–21

� ��

�� $�! #�� $�� $ #��

�� $ � �� !� �� $ �"��$ ��

#�� $�! #�� !�� !�� $ ��

�� ! �!��

� ��

�� #�� #�� "� ��

� ��

��$�� "�� #�� "� ��

� ��

�� "�� #�� "� ��

� �� $ ��

��$�� #�� "� $�!� ��

� �� $ ��

��$�� !�� #�� #�� "� $�!� ��

� �� "��# �� "��

�� $�! �� !�� $��

��

Using the Package Deployment Director

Once you have assembled and built your package, defined all machines, and verifiedyour deployment groups, you are ready to use the Package Deployment Director tospecify package recipients and schedule the package for deployment.

Throughout the deployment process, you always have the option of going to theprevious or next form by clicking Previous or Next. Also, regardless of where you arein the process, you can always cancel the deployment process by clicking Cancel.

When you access the Package Deployment Director, the Work with PackageDeployment form enables you to view deployed package information according to oneof the following four different ways: machines, deployment groups, locations, orpackages.

Depending on your display selection, the tree displays different information as youexpand the tree. The following describes the information displayed as you expand thetree level by level:

� ��

Level One: Client Workstation, Deployment Server, and Enterprise Serverheadings

Level Two: Specific machines under each of the above three headings

Level Three: Specific packages deployed to the machine, if any

Package Management

6–22 B73.3.1 (6/99)

� ��

Level One: Specific groups

Level Two: Members of those groups

Level Three: Specific packages deployed to the group member

� ��

Level One: Specific locations

Level Two: Client Workstation, Deployment Server, Enterprise Server, andRemote Locations headings

Level Three: Specific machines under the Client Workstation, DeploymentServer, and Enterprise Server headings

Level Three under Remote Locations only: Defined remote locations

Level Four: Specific packages deployed to each machine, if any

Level Four under Remote Locations only: Client Workstation, DeploymentServer, and Enterprise Server headings

Level Five under Remote Locations only: Specific machines under the ClientWorkstation, Deployment Server, and Enterprise Server headings

Level Six under Remote Locations only: Specific packages deployed to eachmachine, if any

� ��

Level One: Package names

Level Two: Client Workstation, Deployment Server, and Enterprise Serverheadings

Level Three: Package deployment dates and times for each heading

Level Four: Specific machines that have deployed that package for that date andtime


B73.3.1 (6/99) 6–23

The following task describes how to schedule a package for deployment.

To schedule a package for deployment


1. Choose Package Deployment (P9631). The Work with Package Deploymentform appears.

2. Click Add to launch the Package Deployment Director. The PackageDeployment Director form appears.

Package Management

6–24 B73.3.1 (6/99)

3. Click Next. The Package Selection form appears. Select the package you want todeploy.


B73.3.1 (6/99) 6–25

4. Click Next. The Package Deployment Targets form appears.

Indicate the type of machines to which you want to deploy your package:

� ��

� ��

� � ��

If you want to deploy to deployment groups or locations instead of toindividually specified machines, select either Deployment Group or Locationsinstead of selecting Client Workstations, Deployment Servers, or EnterpriseServers.

Your entry on this form determines which forms subsequently display. Forexample, if you are deploying only to a server, the forms that apply to the clientworkstation will not display.

5. Click Next. The Package Deployment Attributes form appears.

Package Management

6–26 B73.3.1 (6/99)


� ��

� ��

� ��

� ��

Select the Enable Push Installation field if you want to deploy the package usingpush installation, which “pushes” the package to workstations from thedeployment server. For more information about push installation, see �� in this guide.

If you are deploying to a deployment group or location, skip the next three steps.

6. Click Next. If you are deploying to workstations, the Deployment ClientWorkstation Selection form appears. (If you are not deploying to workstations,skip this step.)


B73.3.1 (6/99) 6–27

Find and select the workstations to which you want to deploy the package.Select a workstation by double-clicking in the column to the left of the ClientWorkstation column.

7. Click Next. If you are deploying to a deployment server, the Deployment ServerSelection form appears. (If you are not deploying to a deployment server, skipthis step.)

Find and select the deployment server to which you want to deploy the package.

Package Management

6–28 B73.3.1 (6/99)

8. Click Next. If you are deploying to an enterprise server, the Enterprise ServerSelection form appears. (If you are not deploying to an enterprise server, skipthis step.)

Find and select the enterprise server to which you want to deploy the package.Select a server by double-clicking in the column to the left of the EnterpriseServer Name column.

Skip the next two steps, which apply only to deploying to groups or locations.

9. Click Next. If you are deploying to groups, the Deployment Groups Selectionform appears.


B73.3.1 (6/99) 6–29

Find and select the deployment group you want to receive the package. Select agroup by double-clicking in the column to the left of the Deployment Groupcolumn. Skip the next step, which applies only to location deployment.

10. Click Next. If you are deploying to a location, the Deployment LocationSelection form appears.

Find and select the deployment location you want to receive the package. Selecta location by double-clicking in the column to the left of the DeploymentLocation column.

Package Management

6–30 B73.3.1 (6/99)

11. Click Next. The Work with Package Deployment form appears.

This form enables you to review your deployment option selections. To changeany of your selections, click Prev to return to the appropriate previous form.

12. When you are finished viewing or changing your deployment selections, clickEnd.

13. If you are deploying a server package, you must find and select the serverpackage on the Work with Package Deployment form, and then choose Deployfrom the Row menu. For more information about this step, see �� .

After you schedule your package for deployment, at the specified time on the date youspecified, the package will be deployed to workstations. This package will be madeavailable when the user signs onto OneWorld.

If you are using Push Installation, the package will be automatically installed at thetime you specify through the Scheduler application. For more information, see �� .


B73.3.1 (6/99) 6–31

Field Explanation






Mandatory Installation Indicates 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 When this field is selected, the package can be installedthrough Push Installation.

Date/Time Date to deploy updated objects to the listed machine.

Revising a Scheduled Package’s Deployment Options

After you have scheduled a package for deployment, you can later revise theinstallation status, deployment date and time, enable push installation flag, or themandatory installation flag.

To revise deployment options



2. Choose Machines and click Find to display information according to machinename.

Package Management

6–32 B73.3.1 (6/99)

3. Find and select the deployed package whose options you want to modify, andthen choose Properties from the Row menu. The Deployment PropertiesRevisions form appears.

4. Revise any of the following fields:

� ��

� ��

� ��

� ��

5. When you are finished making revisions, click OK to return to the Work withPackage Deployment form.

Activating the Package

After a package deployment is successfully defined, you must activate the package so itis available for installation via the Workstation Installation application. If you do notactivate the package, it will not be included in the list of available packages when youlaunch Workstation Installation.

There may also be situations where you need to control which packages are availablefor installation. If, for example, you have a package that is for the testing group only,you would want to make that package inactive so it is not available for installationthrough Workstation Installation. This package could then be scheduled for deploymentto the members of the testing group through Package Deployment.

The following task describes how to activate or inactivate a built package.


B73.3.1 (6/99) 6–33

To activate a package



2. Click the Packages button at the upper right of the form, and then click Find.

3. Select from the list the packages you want to activate or inactivate.Alternatively, you can enter the package name at the Package field.

4. Choose Active/Inactive from the Row menu.

Installing a Scheduled Package

When your OneWorld administrator schedules you to receive a package, you will begiven the opportunity to install the package when you sign on to OneWorld on or afterthe date the administrator scheduled the deployment to take place.

If the package is mandatory, you will be unable to access OneWorld until you load thepackage.

If the package is optional, you can decline the package or decide whether to load thepackage now or later. If you decide to load later, OneWorld Explorer launches, and youwill be given the opportunity to install the package the next time you sign on.

If a package scheduled for push installation fails to load for some reason (such as if thescheduled user neglected to leave the workstation switched on during the time thepackage was scheduled to deploy), that package will be included in the list of availablepackages when you sign on to OneWorld.

To install a scheduled package

1. Sign on to OneWorld the same way you normally do.

When you are scheduled to receive a package, the Just In Time Installationprogram launches and the Scheduled Packages form appears.

Package Management

6–34 B73.3.1 (6/99)

2. The Row menu’s selections allow you to decline the installation or list all itemsin the package:

� ��

� ��

If the package is optional you can do one of the following:

� �� !�

� �� !��

� ��

If the package is mandatory, you can do one of the following:

� �� !�

� ��

�� !��

3. To load the package, choose the package you want to install (if there are morethan one), and then click Select.

The Workstation Installation program loads the package. When the installation iscomplete, OneWorld Explorer starts.

B73.3.1 (6/99) 6–35

Deploying Server Packages

The process for deploying a server package is nearly identical to deploying a packageto a workstation. In both cases you need to assemble, define, build, and schedule thepackage for deployment by using the Package Assembly, Package Build, and PackageDeployment applications.

For more information about any of these steps, see �� , �� , and�� . For general information aboutserver packages, see �� .

After you schedule a server package for deployment, you will need to perform anadditional step to launch the batch application that enables you to deploy to servers.You must perform this task whenever you deploy a package to an enterprise server ordeployment server. This task is described in �� .

Deploy server packages only when necessary, because the enterprise server is notavailable to process business applications and batch processes during the installationprocess. The enterprise server does not actually shut down during package installation.Instead, OneWorld queues any jobs submitted to the enterprise server and runs them assoon as the installation finishes. For this reason, J.D. Edwards recommends that youschedule enterprise server packages to be deployed after hours to minimize impact onusers. (Before you deploy a package to an enterprise server, make sure that theOneWorld services will be up and running during the deployment.)

To further minimize impact on the network and users, if your developmentenvironment is on the same enterprise server as your production environment, considernot allowing developers to move their own objects through server packages. Instead,require that they go through an administrator.

Scheduling a Server Package for Deployment

Server packages are deployed by choosing the Deploy function from the Work withPackage Deployment form’s Row menu. This is the same function used to deploypackages to deployment servers during multitier deployment.

Package Management

6–36 B73.3.1 (6/99)

OneWorld determines which batch applications to call based on what is currentlyselected on the Work with Package Deployment form when you choose the Deployfunction from the Row menu:

� �� %��! ��#�� !�� % ��"�� !��

�� "�!�!�� %��! ��!�� !��

� �� !�� %��! ��#�� !�� % ��"�� !��

�� !�� !�� #��% ��%��! ��#�� !��! ��

��"��

� �� !�� #�� !�� % ��"�� !��

�� !�� #�� %��! ��!�� !��

� �� !�� !�� #�� !�� % ��"�� !��

�� !�� !�� #��% ��!�� #�� !��! ��

��"��

� �� $�� !�!�� !�� !�!�� !�� !�� %

��!�� "��#��

� �� !�� % ��"�� !��

�"�!�!�� %��! ��!�� !�� !�� !�� !��

��#�� %��! ��!�� !�� !�� !��

� �� %�" ��! �% �� !�� %��! �� !��

��% ��"�� !� !�� !�� !��

��

When a batch application launches for all servers or all packages, deployment does notoccur unless the package has been previously scheduled for a specific server.

The following task describes how to schedule a server package for deployment.

Before You Begin

� � �� !�� #��

� �� !�� #��

� �"�� !�� #��

� ��"�� !�� %��! !� !�� !� ��#��

To deploy a server package


Deploying Server Packages

B73.3.1 (6/99) 6–37


2. On the Work with Package Deployment form, find and select the server packageyou want to deploy. Alternatively, select the enterprise server (or the EnterpriseServers folder if the package is scheduled to more than one server).

3. Choose Deploy from the Row menu.

Package Management

6–38 B73.3.1 (6/99)

B73.3.1 (6/99) 6–39

Using Push Installation

Push installation is the only deployment method that provides automatic andunattended package deployment. This means the OneWorld system administrator canschedule a package (or several packages) to a workstation or group without requiringany action from workstation users.

For example, an administrator might schedule a package to a particular group fordeployment after hours. When members of that group report to work the followingmorning, that package will be available for immediate use.

Push installation is particularly useful in situations where you need to quickly deploypackages with a minimum of intrusion or impact upon your normal production anddevelopment routines.

By planning and scheduling package deployment judiciously, administrators can alsominimize the impact upon network performance that can accompany large numbers ofpackage deployments.

Administrators can also use push installation to install OneWorld on a workstation forthe first time. This ability can greatly minimize downtime and provide maximumdeployment flexibility.


� ��

� ��

� ��

� ��

� ��

� ��

� ��

How Push Installation Works

Push installation is so named because package contents are pushed from thedeployment server to the workstation. (For a partial package or an update package that

Package Management

6–40 B73.3.1 (6/99)

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

In contrast to push installation, the Workstation Installation program pulls packagecontents from the deployment server to the workstation. Installations set up to usePackage Deployment for scheduled packages that are not “push enabled” also pullpackages.

In terms of deployment, the end result is the same regardless of whether packagecontents are pushed or pulled. However, the advantage of a push installation is that noaction is required from the workstation user other than to leave the workstationswitched on during the time when the package is scheduled to deploy.

The following list summarizes the steps in the push installation process:

� �)-.�'' � +/-# $)-.�''�.$*) 4�$-. ) ,� *) ��# 1*,&-.�.$*) .#�. 1$'' , � $0

+/-# � +��&�" -� �#$- �$-. ) , (*)$.*,- .# +,*", -- *! .# �/-#

�)-.�''�.$*) ��.�# �++'$��.$*) �� ,/))$)" *) .# - ,0 , �)� + ,!*,(-

!/)�.$*)- -/�# �- (*)$.*,$)" $)-.�''�.$*) -.�./-� �# �$-. ) , ��) ,/) �-

$.# , � '*��' - ,0$� *, � ) .1*,& - ,0$� �

� ��# �/' .# +��&�" �3 /-$)" ��&�" � +'*3( ). �� # �/-#

�)-.�''�.$*) ��.�# �++'$��.$*) , ��- !,*( .# -�# �/'$)" .��' �)� - )�- �

( --�" .* .# �$-. ) , *) �'' �!! �. � 1*,&-.�.$*)- .#�. � +��&�" #�-

� ) -�# �/' � !*, � +'*3( ).�

� �- .# ��# �/' , �++'$��.$*) �� .* '�/)�# .# ��.�# �++'$��.$*) *)

.# ). ,+,$- - ,0 ,� �#$- �++'$��.$*) )��' - 3*/ .* -+ �$!3 .# %*�

)�( � 0 ,-$*)� -.�,. ��. �)� .$( � �)� , �/,, )� �

� �. .# -+ �$!$ � -.�,. .$( � .# ��# �/' , '�/)�# - .# �/-# �)-.�''�.$*)

��.�# �++'$��.$*)� 1#$�# $)$.$�. - .# +��&�" $)-.�''�.$*) +,*� -- !,*( .#

� +'*3( ). - ,0 ,� �# �$-. ) , �)� .# ��.�# �++'$��.$*) $). ,��. �/,$)"

.# +,*� -- /).$' $)-.�''�.$*) $- �*(+' . � �*� - �, +�-- � !,*( .#

�$-. ) , .* .# ��.�# �++'$��.$*) .* $)�$��. .# $)-.�''�.$*) -.�./- �!*,

2�(+' � !�$' �� -/�� --!/'� $) +,*", --� �)� -* *)��

� �# ) .# $)-.�''�.$*) $- !$)$-# �� ) �*,'� - )�- �) 5(�$' ( --�" .*

.# 1*,&-.�.$*)�- +,$(�,3 /- ,� �#$- ( --�" $)!*,(- .# /- , 1# .# , .#

$)-.�''�.$*) 1�- -/�� --!/'�

If the push installation is not successful, when the user signs on to OneWorld thestandard scheduling screen appears. At this point the user can either accept themandatory package or exit OneWorld.

Preparing the Enterprise Server for Push Installation

In order to set up your server for push installation, you must first install and configurethe Microsoft Domain Name Service (DNS) that is included with Microsoft WindowsNT Server 4.0. If you don’t already have a domain name service set up, you can install


B73.3.1 (6/99) 6–41

Microsoft DNS by selecting the Network icon in the Control Panel, selecting theServices tab, and then adding Microsoft DNS Server.

After you have added Microsoft DNS, you will need to configure the DNS byspecifying your domain name and servers.

UNIX and AS/400 Considerations

In an environment configured for Dynamic Host Configuration Protocol (DHCP), thereis no client workstation address resolution capability from a non–Microsoft server,because the address is dynamically assigned.

In order to enable name resolution you need to configure your servers to resolve theirIP address lookup through a Microsoft DNS server, which must in turn be configured tolook at the WINS database when DHCP is enabled in the network domain.

Configuring your servers in this way ensure that the following process flow occursduring the push installation process:

1. From the host server on which the Push Installation batch application runs, abusiness function attempts to retrieve the machine host address by looking at theDNS server.

2. Since the DNS server does not contain IP address, it looks to the WINS serverfor the address.

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 Listener on the client workstation and sendsworkstation installation information.

6. The workstation installation process starts.

Preparing Workstations for Push Installation

Before you can push an installation to a workstation, you must set up each workstationto which you want to schedule and deploy a package. This entails installing a“Listener” on the workstation that interacts with the batch application running on theserver.

You must install this Listener on all workstations that you want to be enabled for pushinstallation, regardless of whether you want to deploy packages to a machine that hasOneWorld installed, or if you are installing OneWorld for the first time.

The Listener runs continuously on the Windows NT workstation as a service (and on aWindows 95 machine as a pseudo–service), and can be monitored by administratorsusing the Task Manager. The Listener communicates with the batch application on theserver, receiving and sending messages during the installation process. The Listener

Package Management

6–42 B73.3.1 (6/99)

also monitors the progress of the installation and saves the installation completioncode.

For more information, see the following topics:

� ��"#�� #�� "#��!

� �#� �� #�� "#��!

� ��"#�� #�� "#��!

� �� $�# �!��#�! "�##��"

Installing the Listener

When you install the Listener on your enterprise’s workstations, you specify whether torun a local service or a network service. If you run the service locally on theworkstation, the user must be logged on to receive a package that has been scheduledfor push installation.

If you run the service on the network, the Listener runs as a network account and theuser does not have to be logged on to receive a package through push installation. Thenetwork service must have an administrator’s user ID.

The disadvantage of running the service on the network is that it can be difficult toadminister for all users on the enterprise. For example, because the Listener’sparameters would apply to every user on the network, push installation users would berequired to install OneWorld to and from the same locations. (One user could not haverelease B733 on drive C and another user have the same release on drive D.) Also,every time users change their logon password the system administrator would have toupdate the Listener service with the new passwords in order for the service to work forthose users. For these reasons, J.D. Edwards recommends installing the Listener locallyon each workstation.

Whether you run a local service or network service, the workstation must be switchedon to receive a scheduled package.

There are four main ways to install the Listener on a workstation:

� �"�� #��!�) �!#( "��#&�!� ��"#!��$#�� "("#�� "$�� " #�� %��

��# �%�!��# �� #&�!� �"#!��$#�� ("#�� ! #��

��!�"��# �("#�� # ��!%�! �� "��#&�!�

� �"#!��$#�� '��$#�� "#��#�� !��!�� "�#$ ��'� �� #��

�� (�� !( ��" %�� #!��# &�� "�#�

� �"�� &" �� "�!� #" �� # �� #� �� !��!��

� ��"#�� !�� #�� !��&�� #�� #�!��#

If the Listener is not installed and running on the workstation (or if the workstation isswitched off) the push installation cannot occur. After you schedule a package, be sureto remind package recipients to leave their workstations on and the Listener service


B73.3.1 (6/99) 6–43

running, even during off–hours. If you set up the Listener to run as a local service, alsoremind users to remain logged on.

Before You Begin

Before you install the Listener on the workstation, J.D. Edwards recommends that youdo the following:

� ��

� ��

��

��

To install the Listener on workstations

The following task describes how to install the Listener by launching an installationprogram (that is, a “setup.exe” program). You can distribute this program to users onyour enterprise by sending them either the program or a shortcut via e-mail, or bypointing them to the program location on your server.

If you have an old version of the Listener already installed, the installation programremoves the old version before copying the new version to your workstation.

1. Launch the installation program by double-clicking on the setup.exe icon. Thefirst installation form appears.

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

Package Management

6–44 B73.3.1 (6/99)


� �� #�� ! ��

��

� � �� #��

� �� #�� !��

��

� �� # �� !�� #�� ! ��

��

� ��

�� "�� !

��

� � �� # ��

�� # �� !�� #��

!��


B73.3.1 (6/99) 6–45

3. Click Next to proceed to the next installation form:


� ��

��

��

� ��

��

4. Click Finish to complete the installation.

After you have successfully installed the Listener on the workstation, a small “ear” iconappears on the Windows taskbar, indicating that the Listener has been loaded. Byright–clicking this icon, you can start or stop the Listener, or change the defaultparameter settings as explained in �� .

Installing the Listener via Silent Installation

In some cases it might be more convenient to install the Listener on workstations viasilent installation. Using this method, the OneWorld administrator enters configurationsettings for all workstations and distributes a batch file that automatically initiates theListener installation the next time the user signs on to the workstation.

The advantage of using silent installation to install the Listener is that the process istransparent to workstation users, and each user is not required to enter configurationinformation or step through the installation process.

Package Management

6–46 B73.3.1 (6/99)

The following task describes how to install the Listener via silent installation. This taskwould typically be performed by the OneWorld administrator.

Installing the Listener via silent installation

1. Edit the following settings in the listen_silent_setup.inf file:

� �!,0%�!�3+!� �).!, �*��' *, �!.1*,&� !+!) %)# *) 1$!,! 3*/

1�). .* ,/) .$! �%-.!)!, -!,0%�!�

� �*,&-.�.%*)�%,��.$� �).!, .$! '*��.%*) *) .$! 1*,&-.�.%*) 1$!,!

3*/ 1�). .* %)-.�'' .$! �%-.!)!, +,*#,�( �) ,!'�.! "%'!-� �*,

!2�(+'!� ��,*#,�( �%'!-��)!�*,' �'%!). �%-.!)!,�

� �!'!�-!� �).!, .$! �)!�*,' ��-! ,!'!�-!� �*, !2�(+'!� � �*

)*. !).!, � �/(/'�.%0! /+ �.! ,!'!�-!� -/�$ �- ��

� �)-.�''��.$� �).!, .$! '*��.%*) *) .$! 1*,&-.�.%*) 1$!,! �)!�*,'

%- %)-.�''! � �*, !2�(+'!� ��

� ��/)�$��.$� �).!, .$! -!,0!, '*��.%*) ",*( 1$%�$ .$! %)-.�''�.%*)

+,*#,�( 1%'' ,/)� �*, !2�(+'!�

�� '%!).�-!./+�!2!�

� �/.*�.�,.� �).!, � .* !)��'! .$! �/.*-.�,. "!�./,! *) 1*,&-.�.%*)-�

��/.*-.�,. �/.*(�.%��''3 -.�,.- .$! �%-.!)!, -!,0%�! 1$!) .$!

1*,&-.�.%*) -.�,.- /+�� ).!, � %" 3*/ *)�. 1�). �/.*-.�,. !)��'! �

� �)%)-.�''��&�#!� �).!, � %" 3*/ 1�). .* �/.*(�.%��''3 /)%)-.�''

+,!0%*/- 0!,-%*)- *" �)!�*,' �!"*,! %)-.�''%)# � )!1 "/'' +��&�#!�

�).!, � %" 3*/ *)�. 1�). �/.*(�.%� /)%)-.�'' !)��'! �

2. Create or modify a batch file to include the silent installation parameter “ /s”(without quotation marks) for the ListenSetup.exe program. The batch file mustreside in the same location as the ListenSetup.exe program.

For example, your batch file might contain the following line:

start \\servername\b733\client\misc\ListenSetup.exe /slisten_silent_setup.inf

3. Distribute the inf file and the batch file to workstation users. You can distributethese files or by place them on a network server where workstation users cancopy the files to their workstation.

4. Instruct users to restart their workstation to run the batch file and load theListener via silent installation.

After workstation users have successfully installed the Listener, the Listener icondisplays on the Windows taskbar. Users can click this icon to start and stop the Listeneror change Listener settings as described in �� .

You cannot change the name of the Listener silent installation file shipped withOneWorld. The filename must be listen_silent_setup.inf.


B73.3.1 (6/99) 6–47

Stopping the Listener

The only reason you would need to stop the Listener is if you are certain you do notwant to use push installation to install OneWorld packages. If you change your mindlater, you can always start the Listener again.

The easiest way to stop the Listener is to right–click the Listener icon on the Windowstaskbar and choose Stop Listener.

Alternatively, you can stop the Listener by following these steps:

To stop the Listener

1. Open the Control Panel.

2. Choose Services.

3. Choose OneWorld Client Listener.

4. Click Stop.

Uninstalling the Listener

If you need to uninstall the Listener from the workstation, you can do so by followingthese steps: double-clicking on the Control Panel’s Add/Remove Programs icon. Select“OneWorld Client Listener” and click Remove All Components.

Package Management

6–48 B73.3.1 (6/99)

To uninstall the Listener

1. Open the Control Panel.

2. Choose Add/Remove Programs.

3. Choose OneWorld Client Listener.

4. Click Remove All Components.

Changing Default Parameter Settings

The Listener’s “ear” icon that appears at the far right side of the Windows taskbarenables you to change the default parameter settings you entered when you initiallyinstalled the Listener. You can specify the following:

� ��

� ��

� ��

��

To change default parameter settings

1. Right–click the Listener icon on the the Windows taskbar.

2. In the popup window, choose Change Default Parameters. The OneWorld PushInstall form appears.


B73.3.1 (6/99) 6–49

3. Complete the following fields:

� �� $� "��

��

� �� $� ��

�� $�� !�� "��

�� $� ��

�� "�� !��

� �� $� ��$ �� !� "�� $� "��

��

� �� !�� "�� $� "��

��!�� $� ��

�� $ �� #��

�� " � ��

� � ��$ ��!�� !�� % ��

$� "�� !�� $ �� "��

�� "��

4. Click OK when you are finished making changes.

Scheduling a Package for Push Installation

After you have installed the Listener on your workstations, you can schedule a packagefor deployment.

The process for scheduling a package for push installation is identical to scheduling apackage using the Package Deployment application. When you schedule the packagethrough this application, make sure to turn on the Enable Push Installation option onthe Package Deployment Attributes form. If you do not turn on this option, the packagewill be deployed through normal scheduled deployment.

Package Management

6–50 B73.3.1 (6/99)

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 ispopulated when users sign on to OneWorld. Alternatively, you can enter machinenames manually via the Machine Identification application (P9654A). For moreinformation about defining machine names and scheduling packages for deployment,see ��.

Scheduling the Push Installation Batch Application

After you have installed the Listener on all affected workstations and scheduled thepackage through the Package Deployment application, you must use the Schedulerapplication to run the Push Installation batch application (R98825) on the server.

Before You Begin

Before you run the batch application, make sure you have done the following:

� ��

��

� ��

� ��

To schedule the Push Installation batch application

On the Job Scheduler menu (GH9015)


B73.3.1 (6/99) 6–51

1. Choose Schedule Jobs (P91300). The Work with Versions form appears.

2. Choose the time zone that applies to your setup. The Work with Scheduled Jobsform appears.

3. Click Add to enter a new job. The Scheduling Information form appears.

Package Management

6–52 B73.3.1 (6/99)

4. Choose Batch as the job type and complete the following fields:

� � ��

� � ��

� � ��

Type R98825 into this field

� � ��

(for example, XJDE0001)

� � ��

5. To set the job recurrence (that is, to specify how frequently the job runs) chooseRecurrence from the Form menu. The Recurring Scheduling InformationRevisions form appears.


B73.3.1 (6/99) 6–53

If you do not specify a recurrence by completing the fields on this form, the jobruns only one time. J.D. Edwards recommends that you set recurrence for thePush Installation batch application to run every 30 minutes.

6. Click OK to return to the Scheduling Information form.

7. To enter any overrides, resubmission, or expiration options, choose AdvancedFunctions from the Form menu. The Scheduling Advanced Functions formappears.

Package Management

6–54 B73.3.1 (6/99)

8. Click the tab corresponding to the information you want to enter or revise:

� ��

� ��

� ��

� ��

For more information about using the Scheduler application, see SchedulingJobs in the System Administration guide.

9. Click OK.

After scheduling the job you may want to use Object Configuration Manager(P986110) to verify that the server on which the Push Installation batch application isrunning points to the same Package Scheduling (F98825) and Machine Master (F9650)tables that the Package Deployment application uses.

Field Explanation

Scheduled Job Name A name that uniquely identifies to the system and the user ascheduled job. Use this name to indicate the job function, suchas Monthly Close or Nightly Back Up.

Scheduled Job Status The current status of the scheduled job. As long as the status isactive, the Scheduler determines if the job should be submittedto the server for execution. When the scheduled end date forthe job has been reached, the status changes to Not Active. Tostop the Scheduler from considering the job for submission,you can change the status to Not Active (or suspended) at anytime prior to the end date. You can reactivate the job if youwant the scheduler to include the job again, but you canreactivate a job only if the end date is in the future.

Scheduled Batch ApplicationThe object name of the report that the Scheduler submits to theserver.

Scheduled Version The version of the report scheduled to run. A version identifiesa specific set of data selections and sequencing settings thebatch job uses.

Scheduled Start Date/Time The next date on which the Scheduler submits the scheduledjob to the server for execution.

Running the Push Package Installation Results Report

The Package and Deployment Tools menu contains a batch application (or report)called Push Package Installation Results (R98825B). You can use this feature togenerate a report showing the push installation results. This report essentially providesthe same information you get when you run the Push Installation batch application(R98825).


B73.3.1 (6/99) 6–55

The report includes the following information:

� ��

� ��

� ��

� ��

� ��

� ��

� ��

You can run this report by choosing Push Package Installation Results (R98825B) fromthe Package and Deployment Tools menu (GH9083).

Push Installation Status Codes

The following lists the status codes and descriptions used by the Push Installationapplication. Codes marked with an asterisk indicate conditions in which the PushInstallation application will continue attempting installation the next time the PushInstallation batch application runs.

Status Code Description

200* Scheduled

210* In Progress

220 Successful Install

230 Install Failed

240* Install Running

250* OneWorld Running

260* Listener Not Started/Installed

270 General Error

280 Already Installed

290 Invalid Package

Package Management

6–56 B73.3.1 (6/99)

300 Install Attempted

310 Machine Down

Final Considerations

After you schedule the package and launch the Push Installation batch application,OneWorld automatically starts the Workstation Installation program at the specifiedtime. The package is installed on every workstation you specified, provided that theListener has been properly installed and that the workstation is switched on.

When the installation process is finished, an e-mail message will be sent to eachworkstation scheduled to receive a package via push installation. These messagesinform the package recipients whether the process was successful. E-mail notificationworks only if the package recipient is listed in the F9650 table and has an e-mailaddress in the profile.

If the push installation fails for some reason (for example, if the package recipientneglected to leave the workstation powered on,) the installation status will change toFailed. If you want to reschedule the installation you must first delete the row with thefailed job, and then schedule the job again.

B73.3.1 (6/99) 6–57

Installing OneWorld Workstations from CD

If your system includes a CD writer (also known as a CD burner,) you can build anddeploy packages to the CD writer location. After copying the package to a CD, you canthen use the CD as a “portable” deployment tier from which to perform workstationinstallations. That is, you can run from the CD the setup.exe program that launches theOneWorld Workstation Installation program.

This chapter outlines the steps necessary to set up your enterprise so you can deploypackages to the CD writer and install OneWorld from a CD.

There are three main tasks involved in setting up installation from CD:

� � � ��

� ��

� ��

Defining the CD Writer Location

The first step in the process of configuring your system for deployment from CD is todefine the CD writer location, if it is not already defined. In this step you are essentiallycreating a pseudo deployment server from which you will later drag package data ontothe CD by using your CD writer’s software.

The process for defining this location is identical to defining any other new deploymentserver. For more information about adding a new server definition, see ��.

To define the CD writer location



Package Management

6–58 B73.3.1 (6/99)

2. Underneath the appropriate location, select Deployment server.

3. Click Add to add a new machine. The Deployment Server Revisions formappears.

4. On the Deployment Server Revisions form, complete the following fields:

� ��

� ��

� ��


B73.3.1 (6/99) 6–59

� ��

� � ��

� ��

5. If you want to specify a location for data, a foundation, or helps, do so bychoosing Data, Foundation, or Helps from the Form menu. If you do not specifya location for data, foundation or helps, the default locations will be used.

6. Click OK to return to the Work with Locations and Machines form.

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

8. In Windows Explorer, locate the folder OneWorld Client Install. Copy this folderby dragging the folder to the CD writer location. (The location is the servershare path you entered on the Deployment Server Revisions form.)

Field Explanation








Deploying a Package to the CD Writer Location

After you have defined the CD writer as a deployment server, you are ready to deploy apackage to the CD writer location you specified. This step involves two procedures.

The first task is to deploy to the CD writer location the package you want to write tothe CD. For more information about deploying packages, see ��.

The second task is to modify the Install.inf and Package.inf files in preparation forwriting the package contents to the CD.

Package Management

6–60 B73.3.1 (6/99)

Before You Begin

� ��

��

To deploy the package to the CD writer location


1. Choose Package Deployment Scheduling (P9631). The Work With PackageDeployment form appears.

2. Click Add. The Package Deployment Director launches.

3. Complete the Deployment Director’s forms as you would for any other package.(For more information about deploying packages, see �� .)

4. From the Work with Package Deployment form, find and select the package youjust scheduled for deployment. Choose Deploy from the Row menu to deploythe package.


B73.3.1 (6/99) 6–61

After you deploy the package to the CD writer location, the directory structure for thatlocation will look similar to the following:

Multitier\package_inf\Appl_B.infMultitier\systemcomp\system.cabMultitier\datacomp\data.cabMultitier\helpscomp\helps.cabMultitier\Appl_pgf\Package\Appl_BMultitier\OneWorld Client Install

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

The server share path name is not included when you copy folders to the CD. Using theprevious example, the items copied to the CD would be \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 containingthe package you deployed. This folder will have the name you entered at theServer Share Path field on the Deployment Server Revisions form when youdefined the CD writer location. (In the previous example, the server share pathname was “Multitier.”)

2. Open the folder OneWorld Client Installation, and then open the file Install.inf.(That is, double-click the file’s icon to launch the Microsoft Notepadapplication.)

3. Under the section [FileLocations], modify the line so that two periods and abackslash (\) precede the “package_inf” entry. The line should look like thefollowing after modification:

[FileLocations]PackageInfs=..\package_inf

4. Similarly, open the Package_inf folder and open the <package name>.inf file. Inthe previous example, this file would be named Appl_b.inf.

5. Under the section [SrcDirs], modify each of the lines so that two periods and abackslash (\) precede each entry. After modification, the [SrcDirs] section shouldlook similar to the following:

[SrcDirs]SAPPL_PGF=..\APPL_PGF\package\APPL_BSSYS=..\systemcompSAPPL_PGFDATA=..\datacompSHELP=..\helpscomp

Package Management

6–62 B73.3.1 (6/99)

Creating the OneWorld Installation CD

After you have deployed the package to the CD writer location and modified theInstall.inf and Package.inf files, you are ready to copy the package contents to the CD.This process is accomplished with the software that came with your CD writer, andtypically involves dragging the package contents to the CD. Check the documentationthat came with your CD writer for more information about this process.

When you copy the package to the CD, you must copy the contents of the folder at theCD writer location. In the previous example, this folder was called “Multitier” and isthe same name you entered at the Server Share Path field on the Deployment ServerRevisions form.

This folder should contain the following folders:

� ��

� ��

� ��

� ��

� ��

� ��

Actual folder names may not be the same as those listed, since there may be differencesfor each system.


Package Management

6–64 B73.3.1 (6/99)

B73.3.1 (6/99) 7–1


OneWorld software is normally distributed to workstations from a centralized location.In many cases you can minimize the performance impact on a single deployment serverby using systematic scheduling for software installations. For example, if your site hasmore than 50 workstations requiring a package installation but you release softwareonly four times a year, you can effectively schedule the installations over a weekend, atnight, or during off-peak hours.

While this distribution method is the simplest approach for software deployment,configurations that have either multiple remote sites or large numbers of users at asingle site are constrained during the actual installation by network capacity. Forexample, software installations to workstations connected to the centralizeddeployment location by a 56KB circuit can take 4 to 6 hours to run.

Multitier deployment provides sites the flexibility of installing packages ontoworkstations and servers from more than one deployment location and more than onedeployment machine. These additional deployment locations and machines are referredto as deployment tiers. Hence, multitier deployment simply means deploying frommore than one deployment tier.

Specifically, instead of installing multiple workstations across a WAN circuit, multitierdeployment enables you to transfer a compressed package from the centralized locationto the remote workgroup server that acts as a second deployment tier.

For example, you might have one deployment server at your main location, and asecond deployment server that serves a remote location. Since the server (or tier) at theremote location is responsible for deploying to workstations and servers at thatlocation, you aren’t required to deploy packages from the main deployment serveracross a wide area network (WAN) as you would in a single tier deploymentconfiguration.

Workgroup servers can also be used as second tier deployment locations in a LANenvironment where large numbers of workstations need to install software concurrently.(J.D. Edwards recommends that you consider implementing multitier deployment ifyour site has more than 50 workstations performing OneWorld software installationsper day.)

Package Management

7–2 B73.3.1 (6/99)

There are two main reasons to consider implementing a multitier deploymentconfiguration:

� ��

��

� ��

� ��

Normally, you will decide to implement multitier deployment during CNCimplementation. Although you can enable this function at any time, typically you willset it up after you have already installed OneWorld and are preparing your productionsites to go live.

To set up multitier deployment you will need to enable the function in the ReleaseMaster properties or in the Simple Installation Planner. Then, you must define themachines (and their associated path codes) that are used for deployment. In addition,you can use a scheduler function to define when software should be pushed to thetiered deployment location.

You must also define individual user characteristics for multitier deployment. Normallythis is done by modifying the user profiles to indicate the deployment location fromwhich a user will pull a package.

This section describes the following tasks:

� ��

� ��

� � ��

� ��

� ��

� ��

B73.3.1 (6/99) 7–3


The primary function of multitier deployment is to reduce network traffic (and theresultant delays that come with heavy traffic) by enabling enterprises with more thanone physical location to deploy from a secondary deployment server at the remote site.

That is, instead of installing packages across the WAN from the deployment server toworkstations at a remote location, you can copy the package and the package.inf filefrom the deployment server at the primary location to the deployment server at theremote location. This server at the remote location can then copy the package to theworkstations and servers at that location.

There are two main reasons to consider implementing a multitier deploymentconfiguration:

� �� " !��

�� !�� !��

� �� !�� " �� "��

�� " ��

Normally, you will decide to implement multitier deployment during CNCimplementation. Although you can enable this function at any time, typically you willset it up after you have already installed OneWorld and are preparing your productionsites to go live.

To set up multitier deployment you must define the machines (and their associated pathcodes) that are used for deployment. In addition, you can use a scheduler function todefine when software should be pushed to the tiered deployment location.

You must also define individual user characteristics for multitier deployment. Normallythis is done by modifying the user profiles to indicate the deployment location fromwhich a user will pull a package.

Multitier Deployment Features

Multitier deployment offers the following features:

� �� " !�� " �� "��

� �� " �� "�� "��

�� !� ��

��!� !��

Package Management

7–4 B73.3.1 (6/99)

� �� !� �� #��

� ��! �� "��

��$��

� ��! �� $ ��!�� #�� $��

� !� � �� $�� $��

�� $�� $ �� $��

��% �� !��

Multitier Deployment Terminology

The following describes multitier deployment terms:

� ��$ ��$��

The primary or base deployment location is where the package to be deployed tosecondary or remote locations is built. OneWorld requires at least onedeployment server for installing and maintaining the software. The server at theprimary deployment location should be dedicated solely to deploying andoperating OneWorld, and should not be used for any other purposes in yourcompany. See the OneWorld Installation Guide for this machine’s hardware andsoftware requirements.

� �� $��

Tier deployment locations (also know as remote or secondary locations,) haveone or more deployment servers that allow you to install OneWorld softwareonto the workstations at that location. These servers receive their packages fromthe deployment server at the primary or base location. Machines at the tierdeployment locations will not be able to use Object Librarian functions such asobject check-in and check-out. These machines are designed for deployment useonly, and are not designed to be used for remote development. The number oftiered locations depends on the network and server capacity.

� ��

Tier workstations are workstations that connect to a tier deployment location forsoftware installation. The number of workstations per deployment locationdepends on the network and machine load. All tiered workstations must alsohave a Windows NT domain connection that enables them to connect to, read,and copy files from the shared drives of their respective deployment location.See the OneWorld Installation Guide for the hardware and softwarerequirements of these machines.


B73.3.1 (6/99) 7–5

Example: Two-Tier Deployment Strategy

The following illustrates a typical two-tier deployment strategy:

Tier 1Workstation

Tier 2Workstation

Tier 2Workstation

Tier 1Workstation

Tier 2Workstation

Tier 2Workstation

DeploymentServerDenver

DeploymentLocationChicago

DeploymentLocationAtlanta

WANConnections

LANConnections

LANConnections

Shared Drive Connection

Shared Drive

Connection

Multitier Implementation

Packages are always built on the deployment server at the primary location. Once youhave built the package you want to deploy to remote locations, you must do the followthese steps to implement multitier deployment.

Package Management

7–6 B73.3.1 (6/99)

1. Define Deployment Locations

You must define each physical location to which you want to deploy. Forexample, if your main office is in Denver and you want to deploy to your branchoffice in Seattle, you would need to define the Seattle deployment location. Forinformation, see �� .

2. Create Deployment Server Definitions

You must also define the deployment server at each remote location. For moreinformation, see �� .

3. Schedule the Package

The next step in the process is to schedule the package for deployment using thePackage Deployment application (P9631). The process of scheduling a packagefor multitier deployment is identical to scheduling any other package. For moreinformation, see �� .

4. Deploy the Package to Workstations

Once you have deployed the package to the deployment server at the remotelocation, that server can deploy to the workstations at that location.

Before You Begin

Before you begin implementing multitier deployment you should do the following:

� ��#%"� $��$ )�% ��&� � $��"�%�� %��"#$�� $# $��$ '��

��' )�% $� �� $ ��#� '�"�#$�$�� #$��$��#�

�$� ��#� ��$"�� $#� "� ��$�� $#� �� %#�" "��#�

� ��#%"� $��$ $��"� �# ��!%�$� ��#� # �� $�� #� �"�&� ��" $��

)�% '�� %#�� # � $��" �� )��$ ��$�� " ��"� ��"��$��

��%$ ��%� ��#� # �� "�!%�"��$# ��" � �� )��$ #�"&�"� #��

�� $�� #� �� $��$ �� %�� )�% �� ) '��

� "�(��$��) �� $�� "$�� '��

� "�(��$��) �� %�$ �� "�!%�"�� #� # �� '�� &�")�

�� $�� %�$ �� $� )�% "� ��$� $� � ��"�#��$ ��##

��$��#��

B73.3.1 (6/99) 7–7

Defining Deployment Locations

Use the Machine Identification application (P9654A) to create a record in theDeployment Locations Definition table (F9654) for each deployment location. Thisapplication also enables you to either add a new deployment server definition ormodify an existing definition. Each server at each deployment location must bedefined.

Typically, there will be one record for the primary deployment server and one recordper deployment location for each release. If you are running multiple releases ofOneWorld, you must create multiple records for each deployment location.

For each deployment server at each deployment location you must define propertiessuch as the following:

� ��

� ��

� ��

� ��

� ��

Only the last two fields are specific to deployment servers. The other fields must alsobe entered for all other types of machine, such as workstations, enterpriser servers, anddata servers. (If you are defining a workstation or enterprise server, you must alsospecify the host type.)

Adding a New Deployment Server Definition

The following task describes how to add a definition for a new deployment server. Youwould need to do this, for example, if you open a branch office in another city and needto define a secondary deployment server that can handle deployment to theworkstations at that location.

Before You Begin

� ��

��

��

Package Management

7–8 B73.3.1 (6/99)

J.D. Edwards recommends that you do not define deployment locations with aDEV path code. This is because the DEV path code is normally associated withdevelopment staff that is not located at remote locations.

To add a new deployment server definition


1. Choose Machine Identification (P9654A). The Work with Locations andMachines form appears.

2. Find the location where the deployment server resides, and expand the tree, ifnecessary, to display the different machine types. Choose the Deployment Serverheading and then click Add. The Deployment Server Revisions form appears.


B73.3.1 (6/99) 7–9

3. On the Deployment Server Revisions form, complete the following fields:

� ��

� ��

� ��

� ��

� ��

4. Click OK.

Field Explanation



Description A user defined name or remark.




Package Management

7–10 B73.3.1 (6/99)

Field Explanation



Revising an Existing Deployment Server Definition

There may be situations in which you need to modify the definition for a deploymentserver you already defined. For example, you would need to change the definition if theserver share path or OneWorld release changes, or if you want to designate a differentserver as your primary deployment server.

The procedure for revising an existing deployment server definition is very similar toadding a new definition.

To revise an existing deployment server definition


1. Choose Machine Identification (P9654A). The Work with Locations andMachines form appears.

2. Find the deployment server whose definition you want to modify, and then clickSelect. The Deployment Server Revisions form appears.

3. On the Deployment Server Revisions form, you can modify the following fields:

� ��

� ��

� ��

� ��

If you are modifying the primary deployment server, you can also change thePrimary Deployment Server. For any other server you will be unable to changethis field. A 1 at this field indicates that the deployment server is the primarydeployment server. You can have only one primary deployment server.

4. Choose Path Code from the Form menu. The Machine Path Code Revisionsform appears.


B73.3.1 (6/99) 7–11

5. On the Machine Path Code Revisions form, enter the path code for the primaryor base location from which the secondary location will receive the package.When you enter the path code, the server share path will default to the baseserver share path for that machine.

You must specify the path code for each deployment server at all secondarylocations. If you do not indicate the path code, multitier deployment may notwork.

6. If your package includes a user-defined foundation, data, or helps, specify thoseitems by selecting Foundation, Data, or Helps from the Form menu.

7. On the Deployment Server Revisions form, click OK.

For more information about defining machines, locations, and deployment groups, see�� .

Package Management

7–12 B73.3.1 (6/99)

B73.3.1 (6/99) 7–13

Scheduling Packages for Deployment Locations

You can define which packages your primary deployment server distributes to yourdeployment locations. You can also define when and where the packages are deployed.

Workstations that install from tier deployment locations will access the tier deploymentserver for the help files unless you choose to deploy the help files to the workstation.

After you have created or modified a deployment location, you can schedule packagesfor deployment by using the Package Deployment application (P9631). The process forscheduling packages to a secondary deployment server is identical to scheduling apackage to a primary server. Be sure to specify the secondary server location when youschedule the package.

When you are creating a distribution schedule, keep in mind that you cannot schedulemultiple packages to deploy at the same time.

For more information about scheduling packages for deployment, see �� .

Before You Begin

� �� % �� $�� %�� %�� "��

�� !�� #� � ��

��

� � ��

Package Management

7–14 B73.3.1 (6/99)

B73.3.1 (6/99) 7–15

Distributing Software to Deployment Locations

The process of distributing software to deployment locations is handled through a thePackage Deployment application (P9631) or the Multitier Deployment batch processreport (R98825C). Use the Package Deployment application to define the schedulingparameters or deploy the package immediately. Otherwise, use a version of theMultitier Deployment batch process report to distribute the software to deploymentlocations.

Whether you push or pull the software depends on the machine on which you run thescheduling application’s deployment function or batch process report. You will bepushing the software if you run the application or report on the primary deploymentserver or from a workstation. Conversely, you will be pulling the software if you runthe application or report from a workstation at the tier deployment location. In eithercase, make sure to execute the application or report on the primary deployment servermachine for push, or the destination deployment location for pull.

If you push the software you must have full read and write privileges for bothdeployment servers (that is, the primary deployment server and the tier deploymentlocation or destination machine), even if you do not run the batch application. If you donot have read and write authority on both servers, the deployment will fail.

After the package software has been automatically distributed through the schedulingapplication or batch process report, you will have to manually copy (also calleddrag-and-drop) the workstation installation programs from the primary deploymentserver to the tier deployment location. These programs are located in the client portionof the base installation directory.

This chapter describes the following tasks:

� ��

� ��

� ��

See Also

� ��

Package Management

7–16 B73.3.1 (6/99)

Distributing Software Through Package Deployment

Use this method if you want to distribute software immediately after you define adeployment schedule. If you choose this option, the software will be distributedimmediately regardless of the timing parameters you specify in the scheduling fields.

To distribute software through Package Deployment (P9631)



2. Choose the Machines option at the upper right of the form, and then click Find.Select the deployment server to which you want to deploy.

If you have scheduled packages to more than one deployment server, you canselect the Deployment Server folder to deploy to all applicable servers, ratherthan deploying to each individual server.

3. From the Row menu, choose Deploy. This launches the R98825C batchapplication that enables you to deploy to deployment servers.

This same Deploy option is also used to launch a batch application that deploysenterprise server packages, so if you select an enterprise server name or theEnterprise Server folder on the Work With Package Deployment form, theenterprise server deployment batch application will be launched, not the


B73.3.1 (6/99) 7–17

multitier deployment batch application. When you select a workstation, theDeploy option is not available.

Distributing Software Through the Multitier Deployment BatchProcess

Use this method if you want to distribute software that has been previously defined andscheduled through the Package Deployment application (P9631). Running the reportdeploys the software if the scheduled date and time have already passed.

For example, if you schedule a report to run at 1300 hours on June 1, 1999, running thereport at 1300 hours on May 31, 1999 will have no effect. In this example, in order todistribute the software you must run the batch process report at some time after 1300hours on June 1, 1999.

To distribute software through the Multitier Deployment batch processreport (R98825C)

From the System Administration Tools menu (GH9011)

1. Choose Batch Versions (P98305). The Work with Batch Versions form appears.

2. Enter R98825C at the Batch Application field.

3. Find and select the Multitier Deployment version you want to use. The VersionPrompting form appears.

Package Management

7–18 B73.3.1 (6/99)

4. From the Form menu, choose Submit. The Report Output Destinations formappears.

5. On Report Output Destinations, click one of the following options:

� ��

� ��

The output is directed to the Adobe Acrobat Reader application. This outputshould indicate that the report was successfully completed.


B73.3.1 (6/99) 7–19

Copying Workstation Installation Programs to DeploymentLocations

Regardless of which method you use to distribute the package, you mustmanually copy the setup programs from the tier 1 deployment server to the tier 2deployment locations.

To copy workstation installation programs to deployment locations

Connect to each deployment location and use Windows Explorer to drag thefollowing client directory to the tier 2 workstation:

\\Tier1DeploymentServerName\B733\CLIENT

Remember to update the package.inf and setup.inf files if you are specifyingdeployment locations.

Package Management

7–20 B73.3.1 (6/99)

B73.3.1 (6/99) 7–21

Installing Workstation Packages From DeploymentLocations

The process for installing packages to workstations from deployment locations is verysimilar to that of a normal package installation. Basically, it consists of running thesetup.exe program.

In the case of multitier deployment, this program is resident on the tier deploymentlocation in the \client subdirectory that is under the base installation directory. Theworkstation attached to the deployment location must have read access to this directoryon the deployment location.

For more information about the Workstation Installation program, see the OneWorldInstallation Guide.

Package Management

7–22 B73.3.1 (6/99)

B73.3.1 (6/99) 7–23

Understanding a Multitier Deployment Case Study

This chapter presents a case study for a two-tiered deployment environment. As thiscase study shows, it is generally not efficient to deploy OneWorld packages toworkstations using WAN connections. Instead, you should deploy from a primarydeployment server to tier deployment locations. After that, you can install packages toLAN-attached workstations from the local deployment location.

For OneWorld package installations, a remote deployment location functions as a fileserver. You cannot build packages at a remote deployment location, since packagesmust be built at the primary deployment location.

While locally attached workstations can pull packages from the tier deploymentlocation, these workstations still require OneWorld enterprise server and databaseserver connectivity.

Package Management

7–24 B73.3.1 (6/99)

The following diagram presents an illustration of this case study.

WANConnections

Shared Drive Connection

Shared Drive

Connection

HOME1Enterprise ServerLogic and Data

15 CRP Workstations

15 Production Workstations

LANConnections

LANConnections

LANConnections

LANConnections

15 CRP Workstations15 Production Workstations

Tier 1 Deployment Location

Geographic LocationPhysical Machine NamePath code

DenverDENSVR1

CRPB733PRODB733

– CRP– Production


AtlantaATLSVR1PRODB733


ChicagoCHISVR1

CRPB733PRODB733

– CRP– Production




B73.3.1 (6/99) 7–25

The following table shows the assumptions used by the Tier 1 location in this casestudy.

Denver (home office, Tier 1 deployment location)

Characteristic Setting

Enterprise server name HOME1

Deployment server name Denver DENSVR1

Atlanta ATLSVR1

Chicago CHISVR1

CRP workstations Denver 15

Atlanta 0

Chicago 15

Production workstations Denver 0

Atlanta 15

Chicago 15

OneWorld release B733

Deployment tier Denver 1

Atlanta 2

Chicago 2

Path codes Denver PRODB733

CRPB733

Atlanta PRODB733

Chicago PRODB733

CRPB733

Package Management

7–26 B73.3.1 (6/99)

The following summarizes the steps necessary to configure your system for multitierdeployment.

To configure multitier deployment

On the deployment server (DENSVR1 in this example)

1. Define the Deployment Locations.

Use the Machine Identification application (P9654A) to define all deploymentlocations. See �� .

For this case study, you would define three locations: one for each deploymentlocation (Denver, Atlanta, and Chicago). Values for the fields on the LocationRevisions form are summarized in the following table.

Field Value

Location Enter the name of the deployment location.

In this case study, you would assign names for each physicaldeployment location:

Denver

Atlanta

Chicago

Description Enter a description (any value up to 30 characters) for eachdeployment location.

For example:

Denver: Denver – Tier 1

Atlanta: Atlanta – Tier 2

Chicago: Chicago – Tier 2

Location Code Enter the current location for OneWorld deployment.

For example, DEN.

Parent Location Enter the name of the parent location for the location you areadding.

For example, Corporate.


B73.3.1 (6/99) 7–27

2. Create Deployment Server Definitions.

Use the Machine Identification application (P9654A) to create a definition foreach deployment server at the deployment locations you created. For this casestudy, you would need to define a deployment server for Atlanta and Chicago.(The deployment server in Denver would already be defined since it is theprimary, tier 1 server.) See �� .

For this case study, you would complete the fields on the Deployment ServerRevisions form as shown in the following table.

Field Value

Machine Name Enter the name of the physical machine.

In this case study, you would enter the following values:

Denver DENSVR1

Atlanta ATLSVR1

Chicago CHISVR1

Description Enter a description (any value up to 30 characters).

For example, Multitier Deployment - Denver.

Release Enter the OneWorld release.

For example, B733.

Primary User Enter the primary user for the machine you entered.

Server Share Path Enter the name of the shared directory for the path code wheresystem files and other files reside.

For example, \B733.

3. Schedule the Package.

Schedule the package to be deployed from the tier 1 deployment server to thetier 2 deployment servers through the Package Deployment application (P9631)or a batch process report (R98825C). See �� .

Package Management

7–28 B73.3.1 (6/99)

Glossary

Package Management

B73.3.1 (6/99)

B73.3.1 (6/99)

Glossary

action message. With OneWorld, users can receivemessages (system-generated or user-generated) thathave shortcuts to OneWorld forms, applications, andappropriate data. For example, if the general ledgerpost sends an action error message to a user, thatuser can access the journal entry (or entries) in errordirectly from the message. This is a central featureof the OneWorld workflow strategy. Actionmessages can originate either from OneWorld orfrom a third-party e-mail system.

alphabetic characters. Characters on the keyboardincluding letters of the alphabet and all othersymbols (such as *, &, #), but excluding numerals 0through 9. For example, “ABC*” is a string ofalphabetic characters, but “ABC123” is not. Alsoreferred to as an alpha character. Contrast withalphanumeric characters and numeric characters.

alphanumeric characters. The complete set ofcharacters on the keyboard including letters of thealphabet, symbols, and numerals. For example,“ABC*123” is a string of alphanumeric characters.Contrast with alphabetic characters and numericcharacters.

alternate language. A language other than English,which is designated in the user profile. A languagepreference code is used to set the preferred languagefor each user to display data for online and printedoutput.

applet. A small application, such as a utilityprogram or a limited-function spreadsheet. It isgenerally associated with the programming languageJava, and in this context refers to Internet-enabledapplications that can be passed from a Web browserresiding on a workstation.

application. A computer program or set ofprograms used to accomplish a task. In OneWorld,there are interactive applications and batchapplications. Interactive applications are made up ofa set of forms through which the user interacts withOneWorld. Interactive application identifiers beginwith “P.” For example, Address Book Revisions(P01012) is an interactive application. Batchapplications run without user interaction. Reportsand table conversions are examples of batch

applications. Batch application identifiers begin with“R.” For example, the Print Mailing Labels report(R01401) is a batch application.

application programming interface (API). Asoftware function call that can be made from aprogram to access functionality provided by anotherprogram.

application server. A server in a local area network(LAN) that contains applications used by networkclients.

application workspace. The area on a workstationdisplay in which all related forms within anapplication appear.

architecture. The underlying design of a computerthat defines data storage methods, operations, andcompatibility requirements with other systems andsoftware. It also refers to specific components of acomputer system, the way they interact with eachother, and the type of CPU chip that is used as thebasis of a computer system.

AS/400 common. The AS/400 library that typicallycontains WorldSoftware control files. Can also referto as an AS/400 Common data source used inOneWorld.

AS/400 COMMON. A data source that resides onan AS/400 and holds data that is common to thecoexistent library allowing OneWorld to shareinformation with World.

asynchronous. A method of running tableconversions in which starting one conversion doesnot rely on another conversion’s successfulcompletion.

audit trail. The detailed, verifiable history of aprocessed transaction. The history consists of theoriginal documents, transaction entries, and postingof records and usually concludes with a report.

automatic accounting instruction (AAI). A codethat refers to an account in the chart of accounts.AAIs define rules for programs that automaticallygenerate journal entries, including interfacesbetween the Accounts Payable, AccountsReceivable, Financial Reporting, and General

Package Management

B73.3.1 (6/99)

Accounting systems. Each system that interfaceswith the General Accounting system has AAIs. Forexample, AAIs can direct the General Ledger Postprogram to post a debit to a specific expense accountand a credit to a specific accounts payable account.

base release. The first generally available softwarefor a OneWorld release. See also release, releaselevel.

batch. A group of similar records or transactionsthat the computer treats as a single unit duringprocessing. For identification purposes, the systemusually assigns each batch a unique identifier knownas a batch number.

batch application. A single task or groups of tasksthat the system treats as a single unit duringprocessing. The computer performs batchapplications (jobs) with little or no user interaction.Printing reports and purging files are examples.

batch control. A feature that verifies the number oftransactions and the total amount in each batch thatyou enter into the system.

batch input. A group of transactions loaded from anexternal source.

batch job. A task or group of tasks you submit forprocessing that the system treats as a single unitduring processing, for example, printing reports andpurging files. The system performs a batch job withlittle or no user interaction.

batch processing. A method by which the systemselects jobs from the job queue, processes them, andsends output to the outqueue. Contrast withinteractive processing.

batch server. A server on which OneWorld batchprocessing requests (also called UBEs) are runinstead of on a client, an application server, or anenterprise server. A batch server typically does notcontain a database nor does it run interactiveapplications.

batch type. A code assigned to a batch job thatdesignates to which system the associatedtransactions pertain, thus controlling which recordsare selected for processing. For example, the PostGeneral Journal program selects for posting onlyunposted transaction batches with a batch type of O.

batch-of-one immediate. A transaction method thatallows a client application to perform work on aclient workstation, then submit the work all at onceto a server application for further processing. As abatch process is running on the server, the client

application can continue performing other tasks. Seealso direct connect, store-and-forward.

binary large object (BLOB). A database field thathas no maximum size limit and holds any digitizedinformation. This field is often used to store objects,such as graphical representations or data structures,rather than standard alphanumeric data.

binary string (BSTR). A length prefixed stringused by OLE automation data manipulationfunctions. Binary strings are wide, double-byte(Unicode) strings on 32-bit Windows platforms.

broadcast message. 1) An e-mail message that yousend to multiple recipients. 2) A message thatappears on a form instead of in your mailbox.

browser. A client application that translatesinformation sent by the Worldwide Web. A clientmust use a browser to receive, manipulate, anddisplay Worldwide Web information on the desktop.Also known as a Web browser.

business function. An encapsulated set of businessrules and logic that can normally be reused bymultiple applications. Business functions canexecute a transaction or a subset of a transaction(check inventory, issue work orders, and so on).Business functions also contain the APIs that allowthem to be called from a form, a database trigger, ora non-OneWorld application. Business functions canbe combined with other business functions, forms,event rules, and other components to make up anapplication. Business functions can be createdthrough event rules or third-generation languages,such as C. Examples of business functions includeCredit Check and Item Availability.

business function event rule. Encapsulated,reusable business logic created using through eventrules rather than C programming. Contrast withembedded event rule. See also event rule.

business view. Used by OneWorld applications toaccess data from database tables. A business view isa means for selecting specific columns from one ormore tables whose data will be used in anapplication or report. It does not select specific rowsand does not contain any physical data. It is strictly aview through which data can be handled.

Business View Design Aid (BDA). A OneWorldGUI tool for creating, modifying, copying, andprinting business views. The tool uses a graphicaluser interface.

Glossary

B73.3.1 (6/99)

category code. A type of user defined code forwhich you can provide the title. For example, if youwere adding a code that designated different salesregions, you could change category code 4 to SalesRegion, and define E (East), W (West), N (North),and S (South) as the valid codes. Sometimes referredto as reporting codes. See also user defined code.

central objects. Objects that reside in a centrallocation and consist of two parts: the central objectsdata source and central C components. The centralobjects data source contains OneWorldspecifications, which are stored in a relationaldatabase. Central C components contain businessfunction source, header, object, library, and DLLfiles and are usually stored in directories on thedeployment server. Together they make up centralobjects.

Central Objects merge. A process that blends acustomer’s modifications to the objects in a currentrelease with objects in a new release.

central processing unit (CPU). Computercomponent which carries out the logic, calculationand decision–making functions. Interprets andexecutes instructions upon receipt.

character conversion. The process of convertingcharacters of the same language from one encodingscheme to another while sending and receiving datain a heterogeneous environment.

character set. An ordered set of charactersrepresenting any particular language.

chart. OneWorld term for tables of information thatappear on forms in the software. See forms.

chart of accounts. The structure for general ledgeraccounts. The chart of accounts lists types ofaccounts, describes each account, and includesaccount numbers and posting edit codes.

check-in location. The directory structure locationfor the package and its set of replicated objects. Thisis usually \\deploymentserver\release\path_code\package\packagename. The subdirectories under thispath are where the central C components (source,include, object, library, and DLL file) for businessfunctions are stored.

child. See parent/child form.

client. 1) A workstation or PC in a client/serverenvironment. 2) The receiving end of the spectrumin a request/supply relationship between programs.

client workstation. The computer on which a useroperates OneWorld software applications.

client/server. A relationship between processesrunning on separate machines. The server process isa provider of software services. The client is aconsumer of those services. In essence, client/serverprovides a clean separation of function based on theidea of service. A server can service many clients atthe same time and regulate their access to sharedresources. There is a many-to-one relationshipbetween clients and a server, respectively. Clientsalways initiate the dialog by requesting a service.Servers passively wait for requests from clients.

cluster. A group of two or more servers withidentical configurations used to provide protectionagainst failure. If one server fails, the other cancontinue processing.

code page. An ordered set of characters in which analphanumeric value (code point) is associated witheach character set.

code point. The numeric identifier assigned to acharacter. Its value is usually expressed in ahexadecimal notation.

coexistence. An AS/400 configuration of J.D.Edwards software that allows shared data interfaceoperation to occur between OneWorld andWorldSoftware.

commit. A process that ensures that all databasechanges for a single transaction occursimultaneously. The changes are treated as a singleunit; either all changes occur or none of the changesoccur, thereby maintaining the integrity of thedatabase.

common object request broker architecture. Anobject request broker standard endorsed by theObject Management Group.

component object model (COM). A specificationdeveloped by Microsoft for building softwarecomponents that can be assembled into programs oradd functionality to existing programs running onMicrosoft Windows platforms. COM componentscan be written in a variety of languages, althoughmost are written in C++, and can be unplugged froma program at runtime without having to recompilethe program.

Conference Room Pilot environment. AOneWorld environment used as a stagingenvironment for production data, which includesconstants and masters tables, such as company

Package Management

B73.3.1 (6/99)

constants, fiscal date patterns, and item master. Usethis environment along with the test environment tomake sure your configuration works before yourelease changes to end–users.

configurable client engine. Allows user flexibilityat the interface level. Users can easily movecolumns, set tabs for different data views, and sizegrids according to their needs. The configurableclient engine also enables the incorporation of Webbrowsers in addition to the Windows 95- andWindows NT-based interfaces.

Configurable Network Computing (CNC). Anapplication architecture that allows interactive andbatch applications, composed of a single code base,to run across a TCP/IP network of multiple serverplatforms and SQL databases. The applicationsconsist of reusable business functions and associateddata that can be configured across the networkdynamically. The overall objective for businesses isto provide a future-proof environment that enablesthem to change organizational structures, businessprocesses, and technologies independently of eachother.

constants. Parameters or codes that you set and thatthe system uses to standardize the processing ofinformation by associated programs.

control. Any data entry point allowing the user tointeract with an application. For example, checkboxes, pull-down lists, hyper-buttons, entry fields,and similar features are controls.

Control Table Workbench. During the InstallationWorkbench process, Control Table Workbench runsthe batch applications for the planned merges thatupdate the data dictionary, user defined codes,menus, and user overrides tables.

Control Tables merge. A process that blends acustomer’s modifications to the control tables withthe data that accompanies a new release.

cumulative update. A version of OneWorldsoftware that includes fixes and enhancements madesince the last release or update.

custom gridlines. A grid row that does not comefrom the database, for example, totals. To display atotal in a grid, sum the values and insert a customgridline to display the total. Use the system functionInsert Grid Row Buffer to accomplish this.

custom installation. One of the two types ofinstallations you can set up in the InstallationPlanner application. A custom installation gives the

customer flexibility in creating a plan with Java andWindows terminal servers, custom environments,and custom data sources. See also typicalinstallation.

custom modifications. Changes customers make toOneWorld to make the software run more efficientlyfor them or to meet their particular requirements.

customer. The company that purchases and usesOneWorld. A customer contains individual users.

data dictionary. A database table that OneWorlduses to manage the definitions, structures, andguidelines for the usage of fields, messages, andhelp text. J.D. Edwards has an active data dictionary,which means that it is accessed at runtime.

Data Dictionary merge. A process that updates acustomer’s data dictionary tables with the data thataccompanies a new release.

data mart. Department-level decision supportdatabases. They usually draw their data from anenterprise data warehouse that serves as a source ofconsolidated and reconciled data from around theorganization. Data marts can be either relational ormultidimensional databases.

data only upgrade. A process that preservescustomer business data when moving from aprevious release of OneWorld to a new release. Thisshortens the upgrade process by eliminating the needto perform the merges and table conversions thatincorporate J.D. Edwards data into a customer’sexisting data.

data replication. In a replicated environment,multiple copies of data are maintained on multiplemachines. There must be a single source that “owns”the data. This ensures that the latest copy of data canbe applied to a primary place and then replicated asappropriate. This is in contrast to a simple copyingof data, where the copy is not maintained from acentral location, but exists independently of thesource.

data server. A machine required for AS/400 userswho need to put central objects in SQL Server orOracle. Putting central objects on a data server tellsOneWorld they are not on the enterprise server.

data source. A specific instance of a databasemanagement system running on a computer. Datasource management is accomplished through ObjectConfiguration Manager (OCM) and Object Map(OM).

Glossary

B73.3.1 (6/99)

Data Source Workbench. During the InstallationWorkbench process, Data Source Workbench copiesall data sources that are defined in the installationplan from the Data Source Master and Table andData Source Sizing tables in the Planner data sourceto the System – release number data source. It alsoupdates the Data Source Plan detail record to reflectcompletion.

data structure. A group of data items that can beused for passing information between objects, forexample, between two forms, between forms andbusiness functions, or between reports and businessfunctions.

data warehouse. A database used for reconcilingand consolidating data from multiple databasesbefore it is distributed to data marts fordepartment-level decision support queries andreports. The data warehouse is generally a largerelational database residing on a dedicated serverbetween operational databases and the data marts.

database. A continuously updated collection of allinformation that a system uses and stores. Databasesmake it possible to create, store, index, andcross-reference information online.

database administrator. The person who hasspecial skills or training in one or more types ofdatabase software, for example, SQL Server orOracle.

database driver. Software that connects anapplication to a specific database managementsystem.

database management system (DBMS). Acomputer program that manages data by providingcentralized control, data independence, and complexphysical structures for efficient access, integrity,recovery, concurrence, control, privacy, and security.

database server. A server that stores data. Adatabase server does not have OneWorld logic.

default. A code, number, or parameter that thesystem supplies when the user does not specify one.

default. A value that the system assigns when theuser does not enter a value. For example, if thedefault value for an input is N and nothing is enteredin that field, the system assumes the default is an Nvalue.

deployment environment. A OneWorldenvironment used to run OneWorld on thedeployment server. This environment administers

information for the system data source, such as userprofiles, packages, and environments.

deployment server. The computer used to install,maintain, and distribute OneWorld software to oneor more enterprise servers and client workstations.

detail. The specific information that makes up arecord or transaction. Contrast with summary.

detail area. An area of a form that displays detailedinformation associated with the records or data itemsdisplayed on the form. See also grid.

development environment. A OneWorldenvironment used to test modified developmentobjects before transferring them to the conferenceroom pilot environment.

direct connect. A transaction method in which aclient application communicates interactively anddirectly with a server application. See alsobatch-of-one immediate, store-and-forward.

director. A OneWorld user interface that guides auser interactively through a OneWorld process.

disk. A direct access storage device.

distributed computing environment (DCE). A setof integrated software services that allows softwarerunning on multiple computers to perform in amanner that is seamless and transparent to theend-users. DCE provides security, directory, time,remote procedure calls, and files across computersrunning on a network.

distributed database management system(DDBMS). A system for distributing a database andits control system across many geographicallydispersed machines.

Do Not Translate (DNT). A type of data source thatmust exist on the AS/400 because of BLOBrestrictions.

double–byte character set (DBCS). A method ofrepresenting some characters using one byte andother characters using two bytes. Double-bytecharacter sets are necessary to represent somecharacters in the a Japanese, Korean, and Chineselanguages.

double–byte enabled. A data storage feature thatallows a computer to store ideographic charactersfrom Asian languages. J.D. Edwards codingtechniques accommodate both ideographic andalphabetic characters, making it easier to translate anapplication into another language.

Package Management

B73.3.1 (6/99)

driver. A program or portion of a program thatcontrols the transfer of data from an input or outputdevice.

duplicated database. A decision support databasethat contains a straightforward copy of operationaldata. The advantages involve improved performancefor both operational and reporting environments. Seealso enhanced analysis database, enterprise datawarehouse.

dynamic link library (DLL). A set of programmodules that are designed to be invoked fromexecutable files when the executable files are run,without having to be linked to the executable files.They typically contain commonly used functions.

dynamic partitioning. The ability to dynamicallydistribute logic or data to multiple tiers in aclient/server architecture.

Electronic Data Interchange (EDI). The paperless,computer-to-computer exchange of businesstransactions, such as purchase orders and invoices,in a standard format with standard content.

embedded event rule. An event rule that is specificto a particular table or application. Examples includeform-to-form calls, hiding a field based on aprocessing option value, and calling a businessfunction. Contrast with business function event rule.See also event rule.

Employee Work Center. This is a central locationfor sending and receiving all OneWorld messages(system and user generated) regardless of theoriginating application or user. Each user has amailbox that contains workflow and other messages,including Active Messages. With respect toworkflow, the Message Center is MAPI compliantand supports drag and drop work reassignment,escalation, forward and reply, and workflowmonitoring. All messages from the message centercan be viewed through OneWorld messages orMicrosoft Exchange.

encapsulation. The ability to confine access to andmanipulation of data within an object to theprocedures that contribute to the definition of thatobject.

end user. An individual who uses OneWorldsoftware.

enhanced analysis database. A database containinga subset of operational data. The data on theenhanced analysis database performs calculationsand provides summary data to speed generation of

reports and query response times. This solution isappropriate when external data must be added tosource data, or when historical data is necessary fortrend analysis or regulatory reporting. See alsoduplicated database, enterprise data warehouse.

enterprise. Every server, PC, and database that is onan organization’s network.

enterprise data warehouse. A complex solutionthat involves data from many areas of the enterprise.This environment requires a large relational database(the data warehouse) that is a central repository ofenterprise data, which is clean, reconciled, andconsolidated. From this repository, data martsretrieve data to provide department-level decisions.See also duplicated database, enhanced analysisdatabase.

enterprise server. A database server and logicserver. See database server. Also referred to as host.

Enterprise Workflow Management. A OneWorldsystem that provides a way of automating tasks,such as notifying a manager that a requisition iswaiting for approval, using an e-mail-based processflow across a network.

environment. A path code with a set of ObjectConfiguration Manager (OCM) mappings that allowa user to locate data and a specific set of objects.Examples include Conference Room Pilot (CRP),development, production, and pristine.

Environment Checker. An application you can runbefore installing or upgrading OneWorld to diagnoseconfiguration and setup issues that may exist at theoperating system level.

Environment Workbench. During the InstallationWorkbench process, Environment Workbench copiesthe environment information and ObjectConfiguration Manager tables for each environmentfrom the Planner data source to the System releasenumber data source. It also updates the EnvironmentPlan detail record to reflect completion.

Ethernet. A commonly used, shared media LANtechnology, which broadcasts messages to all nodeson the network segment. Ethernet connects up to1,024 nodes at 10MB per second over twisted paircable, coaxial cable, and optical fiber.

event. An action that occurs when an interactive orbatch application is running. Example events aretabbing out of an edit control, clicking a pushbutton, initializing a form, or performing a pagebreak on a report. The GUI operating system uses

Glossary

B73.3.1 (6/99)

miniprograms to manage user activities within aform. Additional logic can be attached to theseminiprograms and used to give greater functionalityto any event within a OneWorld application or reportusing event rules.

event rule. Used to create complex business logicwithout the difficult syntax that comes with manyprogramming languages. These logic statements canbe attached to applications or database events andare executed when the defined event occurs, such asentering a form, selecting a menu bar option, pagebreaking on a report, or selecting a record. An eventrule can validate data, send a message to a user, calla business function, as well as many other actions.There are two types of event rules:

1 Embedded event rules.2 Business function event rules.

executable file.

A computer program that can be run from thecomputer’s operating system. Equivalent terms are“application” and “program.”.

facility. An entity within a business for which youwant to track costs. For example, a facility might bea warehouse location, job, project, work center, orbranch/plant. Sometimes referred to as a businessunit.

field. 1) An area on a form that represents aparticular type of information, such as name,document type, or amount. 2) A defined area withina record that contains a specific piece ofinformation. For example, a supplier record consistsof the fields Supplier Name, Address, and TelephoneNumber.

file. A set of information stored under one name.See also table.

file transfer protocol (FTP). A set of TCP/IPcommands used to log on to a network, listdirectories, and copy files. FTP is also acommunications protocol used to transmit fileswithout data loss.

find/browse. A type of form used to:1 Search, view, and select multiple records

in a detail area.2 Delete records.3 Exit to another form.4 Serve as an entry point for most

applications.

firewall.

A set of technologies that allows an enterprise totest, filter, and route all incoming messages.Firewalls are used to keep an enterprise secure.

fix/inspect. A type of form used to view, add, ormodify existing records. A fix/inspect form has nodetail area.

form. The element of the OneWorld graphical userinterface by which the user exchanges data withinteractive applications. Forms are made up ofcontrols, such as fields, options, and the grid. Thesecontrols allow the user to retrieve information, addand revise information, and navigate through anapplication to accomplish a task.

Form Design Aid (FDA). The OneWorld GUIdevelopment tool for building interactiveapplications and forms.

form interconnection. Allows one form to accessand pass data to another form. Forminterconnections can be attached to any event;however, they are normally used when a button isclicked.

form type. The following form types are availablein OneWorld:

1 Find/browse.2 Fix/inspect.3 Header detail.4 Headerless detail.5 Message.6 Parent/child.7 Search/select.

fourth generation language (4GL).

A programming language that focuses on what youneed to do and then determines how to do it.Structured Query Language is an example of a 4GL.

general release. See release.

generic text structures. See Media Storage Objects.

graphical user interface (GUI). A computerinterface that is graphically based as opposed tobeing character-based. An example of acharacter-based interface is that of the AS/400. Anexample of a GUI is Microsoft Windows.Graphically based interfaces allow pictures andother graphic images to be used in order to givepeople clues on how to operate the computer.

grid. A control that displays detail information on aform. The grid is arranged into rows, whichgenerally represent records of data, and columns,

Package Management

B73.3.1 (6/99)

which generally represent fields of the record. Seealso detail area.

header. Information at the beginning of a table orform. Header information is used to identify orprovide control information for the group of recordsthat follows.

header detail. A type of form used to add, modify,or delete records from two different tables. Thetables usually have a parent/child relationship.

headerless detail. A type of form used to work withmultiple records in a detail area. The detail area iscapable of of receiving input.

host. In the centralized computer model, a largetimesharing computer system that terminalscommunicate with and rely on for processing. Itcontrasts with client/server in that those users workat computers that perform much of their ownprocessing and access servers that provide servicessuch as file management, security, and printermanagement.

hypertext markup language (HTML). A markuplanguage used to specify the logical structure of adocument rather than the physical layout. Specifyinglogical structure makes any HTML documentplatform independent. You can view an HTMLdocument on any desktop capable of supporting abrowser. HTML can include active links to otherHTML documents anywhere on the Internet or onintranet sites.

index. Represents both an ordering of values and auniqueness of values that provide efficient access todata in rows of a table. An index is made up of oneor more columns in the table.

inheritance. The ability of a class to recieve all orparts of the data and procedure definitions from aparent class. Inheritance enhances developementthrough the reuse of classes and their related code.

install. To load a full or partial set of OneWorldsoftware on a machine that has existing ornonexisting OneWorld software, such as installOneWorld for the 0first time, install an upgrade, orinstall an update.

installation. The process of putting OneWorldsoftware on your computer for the first time. Anexample of an installation is B73.2. As in OneWorldInstallation Guide.

Installation Planner. OneWorld program that runson the deployment server as a system administrationtool. Installation Planner guides you through the

installation setup process, including defining theenterprise server and deployment platforminformation, setting up environments, and definingdata sources.

Installation Workbench. OneWorld systemadministration program that allocates and configuressoftware and resources on servers and workstationsaccording to the plan you created in InstallationPlanner.

installer. The person who can perform most tasksand processes during a OneWorld installation,upgrade, or update.

integrated toolset. Unique to OneWorld is anindustrial-strength toolset embedded in the alreadycomprehensive business applications. This toolset isthe same toolset used by J.D. Edwards to buildOneWorld interactive and batch applications. Muchmore than a development environment, however, theOneWorld integrated toolset handles reporting andother batch processes, change management, andbasic data warehousing facilities.

integration. A situation in which J.D. Edwardssoftware and the software of another companyaccess the same database.

integrity test. A process used to supplement acompany’s internal balancing procedures by locatingand reporting balancing problems and datainconsistencies.

interactive processing. Processing actions thatoccur in response to commands that you enterdirectly into the system. During interactiveprocessing, you are in direct communication withthe system, and it might prompt you for additionalinformation while processing your request. Contrastwith batch processing.

interactive processing. A job the computerperforms in response to a command. Duringinteractive processing, the user communicatesdirectly with the computer, which may prompt theuser to input additional information during theprocessing of a request.

Internet. The worldwide constellation of servers,applications, and information available to a desktopclient through a phone line or other type of remoteaccess.

Internet address. A specified path used to send andreceive messages on the Internet. The parts of theaddress identify the contact, company, and type ofbusiness.

Glossary

B73.3.1 (6/99)

interoperability. The ability of different computersystems, networks, operating systems, andapplications to work together and share information.

intranet. A small version of the Internet usuallyconfined to one company or organization. Anintranet uses the functionality of the Internet andplaces it at the disposal of a single enterprise.

IP. A connectionless communication protocol thatby itself provides a datagram service. Datagrams areself-contained packets of information that areforwarded by routers based on their address and therouting table information contained in the routers.Every node on a TCP/IP network requires anaddress that identifies both a network and a localhost or node on the network. In most cases thenetwork administrator sets up these addresses wheninstalling new workstations. In some cases, however,it is possible for a workstation, when booting up, toquery a server for a dynamically assigned address.

IServer Service. Developed by J.D. Edwards, thisInternet server service resides on the Web server,and is used to speed up delivery of the Java classfiles from the database to the client.

J.D. Edwards Database. See JDEBASE DatabaseMiddleware.

Java. An Internet executable language that, like C,is designed to be highly portable across platforms.This programming language was developed by SunMicrosystems. Applets, or Java applications, can beaccessed from a Web browser and executed at theclient, provided that the operating system or browseris Java-enabled. (Java is often described as ascaled-down C++). Java applications are platformindependent.

Java application server. A server through which auser can interact with OneWorld applications using aWeb browser.

Java Database Connectivity (JDBC). The standardway to access Java databases, set by SunMicrosystems. This standard allows you to use anyJDBC driver database.

JDBNET. A database driver that allowsheterogeneous servers to access each other’s data.

jde.ini. J.D. Edwards file (or member for AS/400)that provides the runtime settings required forOneWorld initialization. Specific versions of thefile/member must reside on every machine runningOneWorld. This includes workstations and servers.

JDE.LOG. The main diagnostic log file ofOneWorld. Always located in the root directory onthe primary drive. Contains status and errormessages from the startup and operation ofOneWorld.

JDEBASE Database Middleware. J.D. Edwardsproprietary database middleware package thatprovides two primary benefits:

1. Platform-independent APIs formultidatabase access. These APIs areused in two ways:

a. By the interactive and batch engines todynamically generate platform-specificSQL, depending on the data sourcerequest.

b. As open APIs for advanced C businessfunction writing. These APIs are thenused by the engines to dynamicallygenerate platform-specific SQL.

2. Client-to-server and server-to-serverdatabase access. To accomplish thisOneWorld is integrated with a variety ofthird-party database drivers, such asClient Access 400 and open databaseconnectivity (ODBC).

JDECallObject. An application programminginterface used by business functions to invoke otherbusiness functions.

JDEIPC. Communications programming tools usedby server code to regulate access to the same data inmultiprocess environments, communicate andcoordinate between processes, and create newprocesses.

JDENET communications middleware. J.D.Edwards proprietary communications middlewarepackage for OneWorld. It is a peer-to-peer,message-based, socket based, multiprocesscommunications middleware solution. It handlesclient-to-server and server-to-servercommunications for all OneWorld supportedplatforms.

job. A single identifiable set of processing actionsthat user directs the computer to perform. Jobs areinitiated by selecting menu options, enteringcommands, or pressing designated function keys.

job queue. A group of jobs waiting to be batchprocessed. See also batch processing.

just in time installation (JITI). OneWorld’smethod of dynamically replicating objects from thecentral object location to a workstation.

Package Management

B73.3.1 (6/99)

just in time replication (JITR). OneWorld’smethod of replicating data to individualworkstations. OneWorld replicates new records(inserts) only at the time the user needs the data.Changes, deletes, and updates must be replicatedusing Pull Replication.

landscape. A printer orientation for a page withgreater width than height. Contrast with portrait.

language preference code. An abbreviation thatidentifies the preferred language to be used for thetext for online and printed output. This code is usedin the user profile to designate the user’s preferredlanguage(s).

local area network (LAN). A short distancenetwork consisting of workstations, servers, a NOS,and a communications link. It is distinguished by theabsence of telecommunications service.

location. The method by which OneWorld managesthe organizational entities within an enterprise. Thedifferentiation between locations can be physical(for example, New York and Tokyo) or virtual (forexample, Headquarters and Accounting). A locationis identified by a three-character location code,which is set up during OneWorld installation.

Location Workbench. During the InstallationWorkbench process, Location Workbench copies alllocations that are defined in the installation planfrom the Location Master table in the Planner datasource to the System data source.

log files. Files that track operations for a process orapplication. Reviewing log files is helpful fortroubleshooting problems. The file extension for logfiles is .LOG.

master table. A database table used to store dataand information that is permanent and necessary tothe system’s operation. Master tables might containdata, such as paid tax amounts, supplier names,addresses, employee information, and jobinformation.

media storage objects. Files that use one of thefollowing naming conventions that are not organizedinto table format: Gxxx, xxxGT or GTxxx.

menu masking. A security feature that lets youprevent individual users from accessing specifiedmenus or menu selections.

menu merge. A process that blends a customer’smodifications to the menu tables with the data thataccompanies a new release.

merge. A OneWorld process that takes a customer’scustom modifications and blends them into the datathat accompanies a new release.

Messaging Application Programming Interface(MAPI). An architecture that defines thecomponents of a messaging system and how theybehave. It also defines the interface between themessaging system and the components.

middleware. A general term that covers all thedistributed software needed to support interactionsbetween clients and servers. Think of it as thesoftware that’s in the middle of the client/serversystem or the “glue” that lets the client obtain aservice from a server.

modal. A restrictive or limiting interaction createdby a given condition of operation. Modal oftendescribes a secondary window that restricts a user’sinteraction with other windows. A secondarywindow can be modal with respect to it’s primarywindow or to the entire system. A modal dialog boxmust be closed by the user before the applicationcontinues.

modeless. Not restricting or limiting interaction.Modeless often describes a secondary window thatdoes not restrict a user’s interaction with otherwindows. A modeless dialog box stays on the screenand is available for use at any time but also permitsother user activities.

multitier architecture. A client/server architecturethat allows multiple levels of processing. A tierdefines the number of computers that can be used tocomplete some defined task.

named event rules (NER). Also called businessfunction event rules. Encapsulated, reusablebusiness logic created using event rules, rather thanC programming.

National Language Support (NLS). Mechanismsprovided to facilitate internationalization of bothsystem and application user interfaces.

network addresses. A unique position assigned to anode operating in a network that other nodes usewhen communicating with it. For Ethernet andToken Ring network adapters, unique addresses areassigned at the factory and consist of a 6-byteaddress. Half of this address identifies the board’smanufacturer, while the last half is unique to theboard and is assigned when the board ismanufactured. Communication errors are prevented,because no two Ethernet or Token Ring NICs willhave identical addresses.

Glossary

B73.3.1 (6/99)

network computer. As opposed to the personalcomputer, the network computer offers (in theory)lower cost of purchase and ownership and lesscomplexity. Basically, it is a scaled-down PC (verylittle memory or disk space) that can be used toaccess network-based applications (Java applets,ActiveX controls) via a network browser.

network computing. Often referred to as the nextphase of computing after client/server. While itsexact definition remains obscure, it generallyencompasses issues such as transparent access tocomputing resources, browser-style front-ends,platform independence, and other similar concepts.

next numbers. A feature used to control theautomatic numbering of items such as new G/Laccounts, vouchers, and addresses. Next numbersprovides a method of incrementing numbers.

node. A termination point for two or morecommunications links. A node can serve as thecontrol location for forwarding data among theelements of a network or multiple networks, as wellas perform other networking and, in some cases,local processing.

normalized. In database management,normalization applies a body of techniques to arelational database in order to minimize theinclusion of duplicate information. Normalizationsignificantly simplifies query and updatemanagement, including security and integrityconsiderations.

numeric characters. Digits 0 through 9 that areused to represent data. Contrast with alphanumericcharacters.

object. A self-sufficient entity that contains data aswell as the structures and functions used tomanipulate the data. For OneWorld purposes, anobject is a reusable entity that is based on softwarespecifications created by the OneWorld toolset. Seealso Object Librarian.

Object Configuration Manager (OCM).OneWorld’s object request broker and the controlcenter for the runtime environment. It keeps track ofthe runtime locations for business functions, data,and batch applications. When one of these objects iscalled, the Object Configuration Manager directsaccess to it using defaults and overrides for a givenenvironment and user.

object embedding. When an object is embedded inanother document, an association is maintainedbetween the object and the application that created

it; however, any changes made to the object are alsoonly kept in the compound document. See alsoobject linking.

Object Librarian. A repository of all versions,applications, and business functions reusable inbuilding applications. It provides check-out andcheck-in capabilities for developers, and it controlsthe creation, modification, and use of OneWorldobjects. The Object Librarian supports multipleenvironments (such as production and development)and allows objects to be easily moved from oneenvironment to another.

Object Librarian merge. A process that blends anymodifications to the Object Librarian in a previousrelease into the Object Librarian in a new release.

object linking. When an object is linked to anotherdocument, a reference is created with the file theobject is stored in, as well as with the applicationthat created it. When the object is modified, eitherfrom the compound document or directly throughthe file it is saved in, the change is reflected in thatapplication as well as anywhere it has been linked.See also object embedding.

object linking and embedding (OLE). A way tointegrate objects from diverse applications, such asgraphics, charts, spreadsheets, text, or an audio clipfrom a sound program. See also object embedding,object linking.

object-based technology (OBT). A technology thatsupports some of the main principles ofobject-oriented technology: classes, polymorphism,inheritance, or encapsulation.

object-oriented technology (OOT). Bringssoftware development past procedural programminginto a world of reusable programming that simplifiesdevelopment of applications. Object orientation isbased on the following principles: classes,polymorphism, inheritance, and encapsulation.

OneWorld. A combined suite of comprehensive,mission-critical business applications and anembedded toolset for configuring those applicationsto unique business and technology requirements.OneWorld is built on the Configurable NetworkComputing technology, J.D. Edwards’ ownapplication architecture, which extends client/serverfunctionality to new levels of configurability,adaptability, and stability.

OneWorld application. Interactive or batchprocesses that execute the business functionality ofOneWorld. They consist of reusable business

Package Management

B73.3.1 (6/99)

functions and associated data that are platformindependent and can be dynamically configuredacross a TCP/IP network.

OneWorld object. A reusable piece of code that isused to build applications. Object types includetables, forms, business functions, data dictionaryitems, batch processes, business views, event rules,versions, data structures, and media objects. See alsoobject.

OneWorld process. Allows OneWorld clients andservers to handle processing requests and executetransactions. A client runs one process, and serverscan have multiple instances of a process. OneWorldprocesses can also be dedicated to specific tasks (forexample, workflow messages and data replication)to ensure that critical processes don’t have to wait ifthe server is particularly busy.

OneWorld Web development computer. Astandard OneWorld Windows developer computerwith the additional components installed:

� �("�& ��

� ��

� ��"�%�'#% �� *�'� ��"�%�'#%��)�

�"� ��

� � *�'� �"'�%$%�'�)� �"� �$ ��'�#"

�#"'%# &��#%!�

open database connectivity (ODBC). Defines astandard interface for different technologies toprocess data between applications and different datasources. The ODBC interface is made up of a set offunction calls, methods of connectivity, andrepresentation of data types that define access todata sources.

Open Systems Interconnection (OSI). The OSImodel was developed by the International StandardsOrganization (ISO) in the early 1980s. It definesprotocols and standards for the interconnection ofcomputers and network equipment.

operating system (OS). The software that runs onthe hardware. For example, AIX 4.1 is a version ofan operating system.

Oracle. A relational DBMS from Oracle. Runs on abroad variety of computers, which allows data to beentered and maintained on multiple hardwareplatforms.

output queue. See print queue.

package. OneWorld objects are installed toworkstations in packages from the deploymentserver. A package can be compared to a bill ofmaterial or kit that indicates the necessary objects

for that workstation and where on the deploymentserver the installation program can find them. It is apoint-in-time “snap shot” of the central objects onthe deployment server.

package location. The directory structure locationfor the package and its set of replicated objects. Thisis usually \\deploymentserver\release\path_code\package\ package name.The subdirectories under this path are where thereplicated objects for the package will be placed.This is also referred to as where the package is builtor stored.

Package Workbench. During the InstallationWorkbench process, Package Workbench transfersthe package information tables from the Planner datasource to the System - release number data source. Italso updates the Package Plan detail record to reflectcompletion.

parallel release. A configuration of OneWorldsoftware that lets multiple release or update levelsrun in separate environments on the same machinefor testing, training, or development purposes. Forrelease levels running in parallel, no tables or dataare shared. For cumulative update levels running inparallel, system and server map data are shared.

parameter. A number, code, or character string youspecify in association with a command or program.The computer uses parameters as additional input orto control the actions of the command or program.

parent/child form. A type of form that presentsparent/child relationships in an application on oneform. The left portion of the form presents a treeview that displays a visual representation of aparent/child relationship. The right portion of theform displays a detail area in browse mode. Thedetail area displays the records for the child item inthe tree. The parent/child form supports drag anddrop functionality.

partitioning. A technique for distributing data tolocal and remote sites to place data closer to theusers who access. Portions of data can be copied todifferent database management systems.

path code. A pointer to a specific set of objects. Apath code is used to locate:

1. Central objects.2. Replicated objects.

plan. Refers to an installation plan. A plan is thestandard means for installing, upgrading, orupdating a OneWorld configuration. Plans, whichare used in various phases of installation, contain

Glossary

B73.3.1 (6/99)

information about data sources you will use,environments you will install, and packages.

planner environment. A OneWorld environment inwhich you prepare the main components of aOneWorld configuration.

platform. The hardware, operating system, anddatabase on which your software is operating, forexample, an HP 9000 processor using HP-UX as theoperating system and Oracle as the database.

platform independence. A benefit of open systemsand Configurable Network Computing. Applicationsthat are composed of a single code base can be runacross a TCP/IP network consisting of variousserver platforms and SQL databases.

polymorphism. A principle of object-orientedtechnology in which a single mnemonic name canbe used to perform similar operations on softwareobjects of different types.

port number. A numeric code that identifies aunique process for which a service can be providedon a machine.

portability. Allows the same application to run ondifferent operating systems and hardware platforms.

portrait. The default printer orientation for a pagewith greater height than width. Contrast withlandscape.

primary key. A column or combination of columnsthat uniquely identifies each row in a table.

print queue. A list of tables, such as reports, thatyou have submitted to be written to an outputdevice, such as a printer. The computer spools thetables until it writes them. After the computer writesthe table, the system removes the table identifierfrom the print queue.

pristine environment. A OneWorld environmentused to test unaltered objects with J.D. Edwardsdemonstration data or for training classes. You musthave this environment so you can compare pristineobjects that you modify.

process. A complete unit of work with a definedstart and end, which a computer performs. Someoperating systems, such as Windows NT, HP-UX,and AIX, track processes by assigning identifiers tothem. In Windows NT, a process is a runninginstance of an executable file.

processing option. A feature that allows you todirect the functions of a program. For example,processing options allow you to specify defaults for

certain forms, control the format in whichinformation prints on reports, and change howinformation appears on a form or in a report.

production environment. A OneWorldenvironment in which users operate OneWorldsoftware.

protocol. A set of formalized rules specifying howhardware and software on a network should interactwhen transmitting and receiving information.

published table. Also called a “Master” table, thisis the central copy to be replicated to othermachines. Resides on the “publisher” machine. theData Replication Publisher Table (F98DRPUB)identifies all of the published tables and theirassociated publishers in the enterprise.

publisher. The server that is responsible for thepublished table. The Data Replication PublisherTable (F98DRPUB) identifies all of the publishedtables and their associated publishers in theenterprise.

pull replication. One of the OneWorld methods forreplicating data to individual workstations. Suchmachines are set up as pull subscribers usingOneWorld’s data replication tools. The only timepull subscribers are notified of changes, updates, anddeletions is when they request such information. Therequest is in the form of a message that is sent,usually at startup, from the pull subscriber to theserver machine that stores the Data ReplicationPending Change Notification table (F98DRPCN).

purge. The process of removing records or datafrom a system table.

push. Technology used to force information from acentralized server to another server or client.

push installation. A process that allows a systemadministrator to schedule the automatic installationof OneWorld on workstations.

push replication. A server-to-server method of datareplication that notifies subscriber machines when achange is made to the publisher table. If thesubscriber machine is not running when thenotification is sent, the subscriber receives themessage at startup.

query by example (QBE). Located at the top of adetail area, it is used to search for data to bedisplayed in the detail area.

queue. A stored arrangement of computer data orprogram waiting to be processed in the order in

Package Management

B73.3.1 (6/99)

which they were submitted. A queue may refer to aprint queue, job queue, or message queue.

record. A collection of related, consecutive fields ofdata that the system treats as a single unit ofinformation.

redundancy. Storing exact copies of data inmultiple databases.

referential integrity. Ensures that a parent recordcannot be deleted from the database when a childrecord for exists.

refresh. To modify OneWorld software, or subset ofit, such as a table or business data, so that itfunctions at a new release or cumulative updatelevel, such as B73.2 or B73.2.1.

regenerable. Source code for OneWorld businessfunctions can be regenerated from specifications(business function names). Regeneration occurswhenever an application is recompiled, either for anew platform or when new functionality is added.

relationship. Links tables together and facilitatesjoining business views for use in an application orreport. Relationships are created based on indexes.

release. A release of OneWorld regardless of anyupdates that might be applied. For example, the termRelease B73.2 refers generically to B73.2, B73.2.1,and B73.2.2. Sometimes referred to as a generalrelease. See also base release, release level.

release level. A specific level of OneWorldsoftware. A release level is achieved by installing abase release and applying one or more updates. Arelease level also can be installed directly. See alsobase release, release.

release/release update. A “release” contains majornew functionality, and a “release update” contains anaccumulation of fixes and performanceenhancements, but no new functionality.

replicated object. A copy or replicated set of thecentral objects must reside on each client and serverthat run OneWorld. The path code indicates thedirectory where these objects are located.

replication. A copy of an object, usually a table in arelational database, which is placed in anotherlocation. As part of replication, the object mayundergo a transformation from one type of table,such as an Oracle table, to another, such as a TAMfile on a client machine.

Report Design Aid (RDA). The OneWorld GUItool for operating, modifying and copying reportbatch applications.

retrofitting. The process of integrating a customer’smodifications into a new release of OneWorld.

rollback. A process which changes data back to aprevious state after it has been committed to adatabase.

runtime objects. Packages of objects that aredeployed to any machine that will run OneWorld.

scalability. Allows software, architecture, network,or hardware growth that will support software as itgrows in size or resource requirements. The abilityto reach higher levels of performance by addingmicroprocessors.

scripts. A collection of SQL statements that performa specific task.

search/select. A type of form used to search for avalue and return it to the calling field.

security server. A dispatched kernel processrunning on a server for security validation. Asecurity server protects computer resources usingsecurity applications and redundant functionality.

server. Provides the essential functions forfurnishings services to network users (or clients) andprovides management functions for networkadministrators. Some of these functions are storageof user programs and data and managementfunctions for the file systems. It may not be possiblefor one server to support all users with the requiredservices. Some examples of dedicated servers thathandle specific tasks are backup and archive servers,application and database servers.

Server Administration Workbench. A OneWorldapplication that provides the server administratorwith vital statistics about the internal functions ofOneWorld.

Server Workbench. During the InstallationWorkbench process, Server Workbench copies theserver configuration files from the Planner datasource to the System release number data source. Italso updates the Server Plan detail record to reflectcompletion.

service. A type of Microsoft Windows NT processthat does not require anyone to be logged on to theoperating system. Examples are jdesnet.exe andjdesque.exe.

Glossary

B73.3.1 (6/99)

servlet. Servlets provide a Java-based solution usedto address the problems currently associated withdoing server-side programming, includinginextensible scripting solutions. Servlets are objectsthat conform to a specific interface that can beplugged into a Java-based server. Servlets are to theserver what applets are to the client.

single–byte character set (SBCS). An encodingscheme in which each alphabetic character isrepresented by one byte. Most Western languages,such as English can be represented using asingle-byte character set.

socket. A communications end point through whichan application sends or receives packets of dataacross a network. Also known as Berkley Socket,developed by the University of California atBerkley.

software action request (SAR). An entry in theAS/400 database used for requesting modificationsto J.D. Edwards software.

Specification merge. The Specification merge iscomprised of three merges: Object Librarian merge,Versions List merge, and Central Objects merge.The merges blend customer modifications with datathat accompanies a new release.

Specification Table Merge Workbench. During theInstallation Workbench process, Specification TableMerge Workbench runs the batch applications thatupdate the specification tables.

specifications. A complete description of aOneWorld object. Each object has its ownspecification, or name, which is used to buildapplications.

specifications. A description of a OneWorld object,such as a table’s width and depth, placement offields, and fonts used.

spool. The function by which the system storesgenerated output to await processing.

static text. Short, descriptive text that appears nextto a control variable or field. When the variable orfield is enabled, the static text is black; when thevariable or field is disabled, the static text is gray.

store-and-forward. A transaction method thatallows a client application to perform work and, at alater time, complete that work by connecting to aserver application. This often involves uploadingdata residing on a client to a server. See alsobatch-of-one immediate, direct connect.

structured query language (SQL). A fourthgeneration language used as an industry standard forrelational database access. It can be used to createdatabases and to retrieve, add, modify, or deleta datafrom databases. SQL is not a complete programminglanguage because it does not contain control flowlogic.

subscriber. The server that is responsible for thereplicated copy of a published table. Such serversare identified in the Subscriber Table.

subscriber table. The Subscriber table(F98DRSUB), which is stored on the PublisherServer with the Data Replication Publisher table(F98DRPUB) identifies all of the subscribermachines for each published table.

summary. The presentation of data or informationin a cumulative or totaled manner in which most ofthe details have been removed. Many systems offerforms and reports that summarize information storedin certain tables. Contrast with detail.

synchronous. A method of running processes inwhich one process must finish before the next onecan begin.

system. A group of related applications identified bya name and a system code. For example, the AddressBook system code is 01. All applications, tables, andmenus within a system can be identified by thesystem code.

system administrator. The person who has accessto perform tasks such as issue signon names ormaintain security.

system code. A code that identifies a system, forexample, 01 for the Address Book system and 31 forthe Shop Floor Management system.

system function. A program module, provided byOneWorld, available to applications and reports forfurther processing.

table. In database environments, a two-dimensionalentity made up of rows and columns. All physicaldata in a database are stored in tables. See also file.

table. A two-dimensional entity made up of rowsand columns. All physical data in a database arestored in tables. A row in a table contains a record ofrelated information. An example would be a recordin an Employee table containing the Name, Address,Phone Number, Age, and Salary of an employee.Name is an example of a column in the employeetable.

Package Management

B73.3.1 (6/99)

table. A file in OneWorld software.

table access management (TAM). The OneWorldcomponent that handles the storage and retrieval ofuser defined data. TAM stores information such asdata dictionary definitions; application and reportspecifications; event rules; table definitions;business function input parameters and libraryinformation; and data structure definitions forrunning applications, reports, and businessfunctions.

table conversion. During an upgrade or update, thisprocess changes OneWorld technical and applicationtables to the format for the new release.

Table Conversion Workbench. During theInstallation Workbench process, Table ConversionWorkbench runs the table conversions that changethe technical and application tables to the format forthe new release of OneWorld. It also updates theTable Conversions and Controls detail records toreflect completion.

Table Design Aid (TDA). A OneWorld GUI tool forcreating, modifying, copying, and printing databasetables.

table event rules. Use table event rules to attachdatabase triggers (or programs) that automaticallyrun whenever an action occurs against the table. Anaction against a table is referred to as an event.When you create a OneWorld database trigger, youmust first determine which event will activate thetrigger. Then, use Event Rules Design to create thetrigger. Although OneWorld allows event rules to beattached to application events, this functionality isapplication specific. Table event rules provideembedded logic at the table level.

TCP/IP. Transmission Control Protocol/InternetProtocol. The original TCP protocol was developedas a way to interconnect networks using manydifferent types of transmission methods. TCPprovides a way to establish a connection betweenend systems for the reliable delivery of messagesand data.

TCP/IP services port. Used by a particular serverapplication to provide whatever service the server isdesigned to provide. The port number must bereadily known so that an application programmercan request it by name.

technical data. A type of OneWorld data source thatcontains information about how OneWorld operates.

technical tables. Tables used for technical processessuch as installation and upgrade of OneWorld, incontrast with tables used by applications.

Telnet. A terminal emulation protocol frequentlyused on the Internet that allows a user to log on andrun a program from a remote computer. Telnet ispart of the TCP/IP communications.

test environment. A OneWorld environment usedalong with the Conference Room Pilot environmentto test OneWorld software or the modificationsmade in the development path code before yourelease changes to the end user.

third generation language (3GL). A programminglanguage that requires detailed information abouthow to complete a task. Examples of 3GLs areCOBOL, C, Pascal and FORTRAN.

third–party. Describes other software that is used inconjunction with J.D. Edwards software.

token. A bit configuration circulated amongworkstations, which lets workstation send data to thenetwork.

token ring. A LAN access mechanism in which allstations attached to a bus wait for a broadcast tokento be passed to them before they are able to transmit.However, though token-passing technology is in aphysical ring, the next receiving station might not bethe next physical station.

TP monitor. Transaction Processing monitor. Amonitor that controls data transfer between local andremote terminals and the applications that originatedthem. TP monitors also protect data integrity in thedistributed environment and may include programsthat validate data and format terminal screens.

trace. A process that helps the user troubleshootproblems.

trigger. Allow you to attach default processing to adata item in the data dictionary. When that data itemis used on an application or report, the trigger isinvoked by an event associated with the data item.OneWorld also has three visual assist triggers:calculator, calendar and search form.

typical installation. One of the two types ofinstallations you can set up in the InstallationPlanner application. A typical installation is thequickest way to create an installation plan, becauseit uses all of the J.D. Edwards default informationfor environment and data sources. See also custominstallation.

Glossary

B73.3.1 (6/99)

uniform resource locator (URL). Names theaddress of a document on the Internet or an intranet.The following is an example ofURL:http://www.jdedwards.com. This is J.D.Edwards Internet address.

unnormalized. Data that is a random collection ofdata elements with repeating record groups scatteredthroughout. Also see Normalized.

update. The process of refreshing OneWorldsoftware to a new release level, such as from B73.2to B73.3.

upgrade. The process of refreshing OneWorldsoftware to a new release level, such as from B73.2to B73.3.

user. An individual who uses OneWorld software.

user defined code (UDC). A code that users candefine, assign code descriptions, and assign validvalues. Examples of such codes are unit-of-measurecodes, state names, and employee type codes.

user defined code type. The identifier for a table ofcodes with a meaning that you define for the system,such as ST for the Search Type codes table inAddress Book. OneWorld provides a number ofthese tables and allows you to create and definetables of your own.

User Defined Codes merge. The User DefinedCodes merge blends a customer’s modifications tothe user defined code tables with the data thataccompanies a new release.

user display preferences. A set of values thatrepresents a user’s preferred language, date format,decimal format, and other country specificconventions.

User Overrides merge. The User Overrides mergeadds new user override records into a customer’suser override table.

user profile. The predefined characteristics requiredfor each user. The user profile includes a library list,default print queue, and default job queue, as well asseveral other characteristics.

Versions List merge. The Versions List mergepreserves any non-XJDE and non-ZJDE versionspecifications for objects that are valid in the newrelease as well as their processing options data.

visual assist. Forms that can be invoked from acontrol to assist the user in determining what databelongs in the control.

vocabulary overrides. A feature that you can use tooverride field, row, or column title text on forms andreports.

wchar_t. Internal type of a wide character. Used forwriting portable programs for international markets.

Web client. Any workstation that contains aninternet browser. The Web client communicates withthe web server for OneWorld data.

Web server. Any workstation that contains theIServer service, SQL server, Java menus andapplications, and Internet middleware. The Webserver receives data from the web client, and passesthe request to the enterprise server. When theenterprise server processes the information, it sendsit back to the Web server, and the Web server sendsit back to the Web client.

wide area network (WAN). A network that extendsbeyond an area served by the dedicatedcommunication lines of a LAN and is capable ofcovering long distance. It is distinguished by therequirement that a phone company ortelecommunications provider be part of thetransmission.

workflow. According to the Workflow ManagementCoalition, worlflow means “the automation of abusiness process, in whole or part, during whichdocuments, information, or tasks are passed fromone participant to another for action, according to aset of procedural rules.”.

workgroup server. A remote database serverusually containing subsets of data replicated from amaster database server. This server does notperformance an application or batch processing. Itmay or may not have OneWorld running (in order toreplicate data).

WorldSoftware Architecture. The broad spectrumof application design and programming technologythat J.D. Edwards uses to achieve uniformity,consistency, and complete integration throughout itssoftware.

Worldwide Web. A part of the Internet that cantransmit text, graphics, audio, and video. TheWorldwide Web allows clients to launch local orremote applications.

z file. For store and forward (network disconnected)user, OneWorld store-and-forward applicationsperform edits on static data and other criticalinformation that must be valid to process an order.After the initial edits are complete, OneWorld stores

Package Management

B73.3.1 (6/99)

the transactions in work tables on the workstation.These work table are called Z files. When a networkconnection is established, Z files are uploaded to theenterprise server and the transactions are editedagain by a master business function. The masterbusiness function will then update the records inyour transaction files.

Glossary

B73.3.1 (6/99)

Index

B73.3.1 (6/99)

B73.3.1 (6/99)

Index

A

AdministratorsCNC, 1–3hardware, network, and third-party software,1–3

APPL. See Interactive applicationApplication

consultant, 1–3developers, 1–3project leaders, 1–3

Application Design Aid form, 4–25Application text modification rules, 3–6AS/400 server, build

business functions, 4–13specification files, 4–14

B

b732sys. See systemBacking up, objects, 4–17Batch application

Check In/Out and Object Transfer, 4–6moving, 4–6Workstation Installation, 4–6

Buildbusiness functions

on a UNIX server, 4–10on a Windows NT server, 4–12on the AS/400, 4–13

specification fileson a UNIX server, 4–11on an NT server, 4–13on the AS/400, 4–14

workstation files, 4–9Build process at a glance, 5–44Building Business Functions, 5–46BusBuild, 5–46Business function

buildon a UNIX server, 4–10on a Windows NT server, 4–12

on the AS/400, 4–13Check In/Out and Object Transfer, 4–4event rule, 4–5moving, 4–4Workstation Installation, 4–4

Business function data structureCheck In/Out and Object Transfer, 4–4Workstation Installation, 4–4

Business Function Errors log, 5–76Business function event rule

Check In/Out and Object Transfer, 4–5Workstation Installation, 4–5

Business function modification rules, 3–10Business view

Check In/Out and Object Transfer, 4–4moving, 4–4Workstation Installation, 4–4

Business view modification rules, 3–8

C

C business function, moving, 4–4Check In/Out

business function, 4–4business function data structure, 4–4business function event rule, 4–5business view, 4–4embedded event rule, 4–5interactive application, 4–6table, 4–3

CNCadministrator, 1–3consultant, 1–3

Comparing deployment methods, 2–12Consultant

application, 1–3CNC, 1–3custom solution, 1–3hardware, network, and third-party software,1–3

Control table modification rules, 3–7CRP, 2–3crpdta. See business data–CRP

Package Management

B73.3.1 (6/99)

Custom solution consultant, 1–3

D

Data dictionary, Storing, 4–7Data Dictionary Items, moving, 4–7Data dictionary tables, 4–7Data structure modification rules, 3–9Database Component Selection form, 5–35Database Item Revisions form, 5–35Database Location, 5–34Defining a Package Build, 5–47Defining a software distribution schedule, 7–13Defining deployment locations, 7–7Defining Machines, 6–8Deploying a server package, 6–35Deployment

For Multitiered Locations, 6–4For Servers, 6–4multitier, 7–1

case study, 7–23features, 7–3terminology, 7–4

On Workstations with OneWorld, 6–3On Workstations Without OneWorld, 6–4two tier, 7–5

Deployment locationsdefining, 7–7

software distribution schedule, 7–13distributing software, 7–15

Deployment methodscomparing, 2–12understanding, 1–5

Deployment Server, definition, 7–4Deployment Server Revisions form, 7–8DEV, 2–3, 2–7Developers, application, 1–3Developing short-term fixes, 2–10Development process, working with, 2–7Distributing software through the schedulingapplication, 7–16Distributing software to deployment locations,7–15

E

Embedded event rule, 4–5Check In/Out and Object Transfer, 4–5Workstation Installation, 4–5

Ensuring the integrity of the productionenvironment, 2–5Event rule

business function, 4–5embedded, 4–5

Event rule modification rules, 3–8

F

FormsApplication Design Aid, 4–25Database Component Selection, 5–35Database Item Revisions, 5–35Deployment Server Revisions, 7–8Foundation Component Selection, 5–29Foundation Item Revisions, 5–30Help Component Selection, 5–32Help Item Revisions, 5–33Location Revisions, 6–14Machine Revisions, 6–9Object Component Selection, 5–26Package Assembly Director, 5–17Package Build Director, 5–49Package Deployment Director, 6–23Package Deployment Targets, 6–25Package Information, 5–18Package Selection, 5–49, 6–24Record Copy Utility, 4–27Report Output Destination, 7–18Scheduled Packages, 6–33Version Prompting form, 7–17View Logs, 5–71Work With Batch Versions Deployment,7–17Work With Locations and Machines, 6–9,6–14, 6–57Work with Locations and Machines, 7–8Work with Object Transfer, 4–20Work With Package Build Definition, 5–48Work with Package Deployment, 6–23Work With Packages, 5–16Work with Versions, 4–21

Foundation Component Selection form, 5–29

Index

B73.3.1 (6/99)

Foundation Item Revisions form, 5–30Foundation Location, 5–29Foundations, 5–29Full package, 1–5

G

GT. See Media object

H

Hardwareadministrators, 1–3consultants, 1–3

Help Component Selection form, 5–32Help Item Revisions form, 5–33Help Location, 5–32

I

Interactive application, Check In/Out andObject Transfer, 4–6Interactive application modification rules, 3–4Interactive applications, moving, 4–6

J

JITI. See just installationJust-in-time installation, Understandingjust-in-time installation, 5–6

L

Location Revisions form, 6–14Logs

Business Function Errors, 5–76Missing Business Function Source Errors,5–76Package Build, 5–74Package Statistics, 5–73

M

Machine Revisions form, 6–9Machines, defining, 6–8Managing, objects, 4–1Media object

Check In/Out and Object Transfer, 4–6Workstation Installation, 4–6

Media objects, moving, 4–6Missing Business Function Source Errors log,5–76Modification rules

Application text, 3–6business functions, 3–10business views, 3–8control tables, 3–7data structure, 3–9event rules, 3–8interactive applications, 3–4Reports, 3–5table specifications, 3–7understanding

OneWorld, 3–4report specifications, 3–5

versions, 3–10Moving

batch applications, 4–6business function, 4–4business view, 4–4C business function, 4–4Data Dictionary Items, 4–7interactive applications, 4–6media objects, 4–6tables, 4–3

Multitier deployment, 7–1case study, 7–23features, 7–3terminology, 7–4

N

NER. See Business function event ruleNetwork

administrators, 1–3consultants, 1–3

NT server, build, specification files, 4–13

Package Management

B73.3.1 (6/99)

O

Object Component Selection form, 5–26Object Transfer

batch application, 4–6business function, 4–4business function data structure, 4–4business function event rule, 4–5business view, 4–4embedded event rule, 4–5interactive application, 4–6media object, 4–6table, 4–3

Objectsbacking up, 4–17managing, 4–1restoring, 4–17transferring, 4–19

OneWorldroles, understanding, 1–3understanding modification rules, 3–4

P

Packagebuild, copying, 5–60build definition, 5–47full package, 1–5installing a scheduled package, 6–33overview, 5–9partial package, 1–5understanding packages, 1–4update package, 1–5

Package Assembly Director, 5–17Package Build Director, 5–49Package Build History, 5–69Package Build log, 5–74Package Build Logs, 5–69Package Deployment Director, 6–19Package Deployment Director form, 6–23Package Deployment Targets form, 6–25Package Information form, 5–18Package Selection form, 5–49, 6–24Package Statistics log, 5–73Package Types, 5–7

Full Package, 5–7Partial Package, 5–7Update Package, 5–8

Partial package, 1–5Path code

CRP, 2–3DEV, 2–3development process, 2–7PRIST, 2–3PROD, 2–3

Path codes, working with the recommended,2–3Preserve and replace with an upgrade, 3–3PRIST, 2–3pristdta. See business data–JDEPROD, 2–3, 2–7proddta. See business data–PRODProduction environment, ensuring integrity of,2–5Project leaders, application, 1–3Push Installation, using, 6–39

R

Record Copy Utility form, 4–27Replace and preserve with an upgrade, 3–3Report modification rules, 3–5Report Output Destination form, 7–18Restoring, objects, 4–17

S

Scheduled Packages form, 6–33Scheduling application, distributing software,7–16Server package, deploying, 6–35Server Packages, understanding, 1–6Setup, package management, 2–1Short–term fixes, developing, 2–10Software

distributing, through the schedulingapplication, 7–16distributing to deployment locations, 7–15

Software distribution schedule, defining fordeployment locations, 7–13Specification files, build

on a UNIX server, 4–11on an NT server, 4–13on the AS/400, 4–14

Storing the data dictionary, 4–7

Index

B73.3.1 (6/99)

T

TableCheck In/Out and Object Transfer, 4–3Data Dictionary, 4–7moving, 4–3Workstation Installation, 4–4

Table specification modification rules, 3–7Third-party software

administrators, 1–3consultants, 1–3

Tier Deployment Location, definition, 7–4Tier Workstations, definition, 7–4Transferring Objects, 4–19Two tier deployment, 7–5

U

UBE. See Batch applicationUnderstanding

deployment methods, 1–5full vs. partial workstation, 5–4modification rules, report specifications ,3–5OneWorld modification rules, 3–4OneWorld roles, 1–3package deployment, 6–3packages and deployment, 5–3Server Packages, 1–6Workstation Installation, 1–5

UNIX server, buildsbusiness functions, 4–10specification files, 4–11

Update package, 1–5Upgrade preserve and replace, 3–3Using Push Installation, 6–39

V

Version modification rules, 3–10Version Prompting form, 7–17View Logs form, 5–71

W

Windows NT Server, build, specification files,4–12Work With Batch Versions form, 7–17Work With Locations and Machines form, 6–9,6–14, 6–57Work with Locations and Machines form, 7–8Work with Object Transfer form, 4–20Work With Package Build Definition form,5–48Work with Package Deployment form, 6–23Work With Packages form, 5–16Work with Versions form, 4–21Working with the normal development process,2–7Workstation Build, files, 4–9Workstation Installation

batch application, 4–6business function, 4–4business function data structure, 4–4business function event rule, 4–5business view, 4–4embedded event rule, 4–5media object, 4–6table, 4–4understanding, 1–5

Documents

EnterpriseOne B73.3.1 Package Management PeopleBook · 2006. 4. 25. · B73.3.1 (6/99) 1–1 Overview of Package Management The Configuration Planning and Setup suite is designed