6
Custom Package Creation and Installation

The J.D. Edwards OneWorld XE adapter requires a custom package to be installed on the J.D. Edwards OneWorld system. This chapter discusses the following topics:

• Defining a Custom Package

• Custom Package Creation and Installation Prerequisites

• Creating a Custom Package

• Installing the Custom Package ACBREL1

• List of Modules

Defining a Custom Package

ACBREL1 is a custom package, or an automated software update in J.D Edwards' terms, that has business functions to extract metadata and custom functions to test the data types. A custom package is a post release deliverable that provides software changes for specific purposes, such as regulatory changes or enhancements. These custom packages are created for specific functionality. For example, ACBREL1 is created to extract metadata and to test the J.D. Edwards data types. When the ACBREL1 custom package is installed it updates selected modules within the J.D. Edwards OneWorld environment. To update, ACBREL1 objects must be merged into the appropriate OneWorld environment.

See Also: "List of Modules"

Custom Package Creation and Installation Prerequisites

A custom package can be created and installed by the Configurable Networking Computing (CNC) specialists, OneWorld system administrators, or network/server administrators. A custom packages installation requires the following:

• A completely installed OneWorldXE (release B73.3.1 and above) environment with defined standard data sources and path codes.

• A valid J.D. Edwards license and product packaging tools.

• A J.D. Edwards documentation CD.

• A valid userID and password for Knowledge Garden, which is located on the J.D. Edwards site.

Related Documentation

To create a custom package, the following reference documents are required:

• Package Management

• Product Packaging Tips and Techniques

These documents provide a more detailed explanation of the instructions in this chapter.

Retrieving the Package Management Reference Document

The following steps explain how to retrieve the Package Management reference document from J.D. Edwards Documentation CD.

Note: In order to retrieve this document you must have a valid J.D. Edwards Documentation CD.

1. Browse the CD to locate and open the howto.pdf.

2. Click the main menu on the left hand side of the howto.pdf.

3. Locate and click View books in the main menu.

4. Click Technical in the main menu.

5. Click Package Management the main menu.

In the Package Management document the Package Build provides the information for packaging the source files and defining the custom package.

Retrieving the Product Packing Tips and Techniques Reference Document

The detailed step-by-step instructions on how to create the product package and make it portable are described on the J.D.Edwards Product Packaging Tips and Techniques reference document. The following steps explain how to retrieve the document from J.D.Edwards Knowledge Garden.

Note: In order to download the document from J.D. Edwards Knowledge garden site, a valid userID and password for Knowledge Garden is required.

1. Go to http://www.jdedwards.com and click the Knowledge Garden Logon.

   To log on you must be a client with J.D. Edwards with a Knowledge Garden logon ID and password

2. Sign in with your Knowledge Garden user (logon) ID and password.

3. Click Search from the top menu.

   A search criteria window appears with two panes. This window has a textbox where you can enter the search criteria and a group of checkboxes where you can select the documentation.

4. Select all the checkboxes on the left hand side of the screen.

5. Enter the OTM-01-0001 document ID in the search criteria textbox and click Search.

   Search results display in the right pane.

6. Click the Product Packaging Tips and Techniques reference document link.

Creating a Custom Package

Creating a custom package involves packaging the source files and defining the custom package and making the custom package portable.

Basic Steps for Packing the Source Files and Defining the Custom Package

This section provides the basic steps required to pack the source files and create the custom package. Review the Package Management reference document before completing the following steps.

See Also: "Retrieving the Package Management Reference Document"

Note: A compiled version of the source files is required to create a package. You retrieve the source files and the packaged binary files in the following directory: <install_directory>\JDE\ESU

See Also: "Installing the Custom Package ACBREL1"

To pack the source files and create the custom package:

1. Run the package assembly:
   • In the package assembly utility, assign the new package a name, description, and path, and select the language.

     The Package Assembly utility is run from the Package and Deployment Tools. For step-by-step instructions on running the package assembly refer to the Package Build section in the Package Management reference document.

2. Enter the foundation location:
   1. Change the foundation location from the default location displayed in the Foundation Component screen. The default foundation location is determined through the release associated with the package's path code.

      This is normally the system directory at the same directory level as your path code.

   2. Click Foundation on the Package Component Revision dialog and follow the Package Build section's instructions in the Package Management reference document.

3. The package build copies the help file from the location defined in Help Item Revisions to the package directory. Enter the help file location:
   Click Help on the Package Component Revision dialog and follow the instructions in the Package Build section of the Package Management reference document.

   Enter the database location:

   Click Database on the Package Component Revision dialog and follow the instructions in the Package Build section of the Package Management reference document.

   To add an object to the package, you must add the source files. To add objects to the package:

   1. Click Objects on the Package Component Revision dialog to display the Object Component dialog.

   2. Click Browse to examine the source files that you want to add to the package.

   Add features to the package:

   1. Click Features on the Package Component Revision dialog to display the Feature Component dialog.

   2. Click Browse to view the features you want to select.

   Activate an assembled package:

   After the package is assembled, the status remains inactive. To make the status active run the product assembly:

   Select Package Assembly from the Package and Deployment Tools menu and check the active/inactive box for the particular package.

Basic Steps for Making the Custom Package Portable

This section explains how to make the package portable after the package creation process is completed. You require the Product Packaging Tips and Techniques reference document to complete the instructions in this section.

See Also: "Retrieving the Product Packing Tips and Techniques Reference Document"

The Product Packaging tool is required for the following steps.

1. The Product Packaging tool requires an out of the box (pristine) copy of the Data Dictionary for the Data Dictionary changes to be included on the CD. Create a (pristine) Data Dictionary by following the step-by-step instructions explained in section 1 of the Implementation section in the Product Packaging Tips and Techniques reference document.

2. The Product Packaging tool requires an out of the box (pristine) copy of the Control Tables for Control Table changes to be included on an update CD. Create a pristine Control Table set by following the step-by-step instructions in section 2 of the Implementation section in the Product Packaging Tips and Techniques document.

3. The Product Packaging process creates a new access database that is merged into existing environments during the installation of the update CD. This database is created in the TEMP directory on the workstation where the Product Package CD image is mastered. To copy tables into this database, an ODBC data source is created by following the step-by-step explained in section 3 of the Implementation section in the Product Packaging Tips and Techniques document.

4. Product packaging requires a set of tables called Change tables. Change tables are created by following the step-by-step instructions that are explained in section 4 of the Implementation section in the Product Packaging Tips and Techniques document.

5. The package build application must be set in mastering mode in order for an update package to be compressed. To set package build in mastering mode, follow the steps in section 5 of the Implementation section in the Product Packaging Tips and Techniques document.

6. Defining a CD is the process of creating the data that is placed on your update CD. A software master definition establishes a template and package to use, what build steps to follow, and the directory structure of the final master CD. This outline must be defined, validated, and finally mastered. To start this process follow the instructions in section 7 of the Implementation section in the Product Packaging Tips and Techniques document.

7. Validating a CD is the process of validating the software master that was defined to make sure each build step is valid. To start this process follow the instructions in section 8 of the Implementation section in the Product Packaging Tips and Techniques document.

8. Mastering a CD is the process of executing the software master that was defined to create the update CD image on the workstation. To start this process follow the instructions explained in section 9 of the Implementation section in the Product Packaging Tips and Techniques document.

9. Check the existence of the packagename.cab and packagename.exe files in the $TEMP\final directory manually for the successful creation of the package.

Installing the Custom Package ACBREL1

To install the custom package ACBREL1, the Deployment Server Installation Guide and the Installation Workbench Guide are required.

The following steps provide instructions for the installation process:

1. Log on as user JDE on the deployment server.

2. Insert the J.D. Edwards's CD into the Deployment Server CD drive.

3. Create a new folder called ACBREL1 on the Deployment Server ..(root) /B7 folder.

4. Copy ACBREL1.exe and ACBREL1.cab from the ACBREL1 Custom Package CD that was created on the newly created ACBREL1 directory.

5. Execute ACBREL1.exe from the ../B7/ACBREL1 directory.

   The J.D. Edwards Installation Manager automatically starts after the executable file expands.

   Note: If the J.D. Edwards Installation Manager does not display, execute the setup.exe file located in the ..(root)/B7/ACBREL1 directory.

6. Click Next, then click Finish in the OneWorld Deployment Server Setup Type dialog.

   When the installation finishes, a dialog informs you whether the installation was successful.

7. Log on to the JDEPLAN environment as user JDE on the deployment server.

   Note: If the planner update Electronic Software Update (ESU) that includes SAR #4533357 has not been installed on your system. Select Software Updates from the System Installation Tools menu (GH9612). Input 02 for option 1 in the Processing Options panel. If the planner update ESU that includes SAR #4533357 has been installed on your system, select Application Software Update from the System Installation Tools menu (GH9612).

8. Double-click the ACBREL1 update on the Work with Application Update screen and click Next.

9. Double-click the environment(s) where you want the update installed.

10. If you want the software update to run in unattended mode, verify that Unattended Workbench is checked.

11. If you want the backup of the specs (so that the original specs can be restored) check Backup and then click Next.

12. Select the plan for the update you are installing on the Work with Installation Plan dialog and click Select.

13. After the installation is complete, check all the automatically generated PDFs for errors. If errors occur, consult the J.D. Edwards Software Update Guide for troubleshooting tips, or contact J.D. Edwards directly.

14. After installation has completed successfully, build a full package build for the environment(s) you applied to the ACBREL1 update. Consult J.D. Edwards documentation on how to build a full package build.

List of Modules

The Custom Package ACBREL1 creates the following objects in J.D. Edwards:

• ACBCHAR01 - TEST CHAR TYPE 01

• ACBCUST - ACB CUSTOMER ID

• ACBDATE01 - TEST DATE TYPE 01

• ACBDEF - ACB FUNCTION TYPE DEFINITION

• ACBFCNT - ACB FUNCTION NAME LIST COUNT

• ACBFUNC - ACB FUNCTION NAME LIST

• ACBFUNCN - ACB FUNCTION NAME

• ACBINT01 - TEST INTEGER TYPE 01

• ACBLIB - LIBRARY

• ACBMATH01 - TEST MATH TYPE 01

• ACBNEWS - ACB NEW STATUS

• ACBORDER - ACB ORDER NUMBER

• ACBPRC - ACB ITEM PRICE

• ACBPROD - ACB PRODUCT ID

• ACBQTY - ACB ITEM QUANTITY

• ACBRES - ACB RESULT INDICATOR

• ACBSTAT - ACB STATUS

• ACBSTR01 - TEST STRING TYPE 01

• ACBTEST - ACB TEST SCREEN

• ACBTEST2 - ACB TEST SCREEN 2

• ACBTEST3 - ACB TEST SCREEN 3

• B5500900 - SUPPORT MODULE

• D5500900 - DATA STRUCTURE

• D5500900A - DATA STRUCTURE

• D5500900B - FETCH PRICE DATA STRUCTURE

• D5500900C - GET CUSTOMER STATUS DATA STRUCTURE

• D5500900D - SET CUSTOMER STATUS DATA STRUCTURE

• D5500900E - UPDATE SALES ORDER STATUS DATA STRUCTURE

• D5500900F - TEST INTEGER

• D5500900G - TEST STRING

• D5500900H - TEST DATE

• D5500900I - TEST CHAR

• D5500900J - TEST MATH NUMERIC

• D5500900K - TEST DATE 2