1. Package Management Guide (Release 9.2.0.5 and Prior)
  2. Prerequisites

Prerequisites

Before you complete the tasks in this section:

  • Verify that the User ID that is used to perform the package build has drop table and create table rights.

    If you are using a Oracle, SQL, or DB2 for Linux, UNIX, and Windows database, and you are running with security server turned on, you must add a security override so that the package build process can create the metadata repository table in central objects.

    See Adding a Security Override for Package Build.

  • For customers adopting Microsoft Visual C++:

    All JD Edwards EnterpriseOne Windows machines receiving application foundation packages built with Microsoft Visual C++ require the corresponding runtime libraries to be installed.

  • Assemble the package and verify that the status of the assembled package is Assembly-Definition Complete.

  • Verify that Oracle's JD Edwards EnterpriseOne Object Configuration Manager (OCM) mappings are correctly set for the JD Edwards EnterpriseOne Package Build (R9621) and Server Package Build (R9622) programs, which the system generates as part of the package build process.

    For example, if you want the programs to run locally, ensure that the OCM mappings point to Local for the environment in which the package build is running.

  • Verify that logging is turned off during the package build.

    When the jdeproperties.log file is set for logging in the \system\classes folder and a package build is submitted, the build process is slowed down.

  • Modify the jde.ini for package build to work properly.

    Update both the jde.ini on the deployment server (c:\Windows\jde.ini) and the client jde.ini template under <deployment server>\<release>\OneWorld Client Install\misc by adding the "allowedFileExtensions" to the JDENET section of the jde.ini as shown:

    [JDENET]

    allowedFileExtensions=.c;.h;.hxx;.ddb;.xdb;.cab;.Z;.log;.imp;.txt;.spc;.gif;.bmp;.jpg;.avi;.ico;.h_old;.c_old;.inf;.sts;.err;.tpl;NONE;

    Also, through Server Manager, edit the jde.ini on all enterprise servers and make sure that all file types are listed in the entry as shown above. If you change the jde.ini, stop and start services on that server.

See also: