1. Administration Guide
  2. JD Edwards EnterpriseOne Initialization for UNIX and Linux

JD Edwards EnterpriseOne Initialization for UNIX and Linux

This initialization occurs when you start JD Edwards EnterpriseOne programs, such as the queue kernel, runbatch, and so on:

  • The environment name is passed as a command line argument to the program (such as porttest, runbatch, and so on).

  • This environment can be translated to a different environment, based on the settings in the [SERVER ENVIRONMENT MAP] section of the JDE.INI file.

  • The environment that is used must be a valid entry in the Library List Master File table (F0094). Likewise, it must have a valid corresponding path code in the Environment Detail table (F00941).

  • These JDE.INI settings in the [DB SYSTEM SETTINGS] section are used to determine where the JD Edwards EnterpriseOne server startup tables, such as the Data Source Master (F98611) and the Object Configuration Master (F986101), are located:

    • Base Datasource

    • Object Owner

    • Server

    • Database

    • Load Library

    • Type

  • Using this information, the F986101 table in the specified database on the server is opened.

  • When an override for a given table or the current user exists, that data source (the OMDATP field in the F986101 table) is used for the given object or user and environment. Otherwise, the data source in which OMOBNM=DEFAULT for the given environment is used. Ignore any inactive records (that is, OMSTSO=NA).

    We strongly recommend that you do not have any default records for reports (OMOBNM=DEFAULT and OMFUNO=UBE) on the server. These records might prevent report interconnections (that is, one report calling another report) from starting correctly.

  • Each unique data source in the F986101 table should correspond to one entry in the F98611 table.

  • The corresponding information in the F98611 table must be correct. In particular, the OMDLLNAME field must display the correct library for the database to which the data source points.

  • For an Oracle database, the OMDATB field from the F98611 table maps to an entry in the tnsnames.ora file. This tnsnames.ora file must be set up correctly. (Ask an Oracle database administrator to verify the setup). Starting with Oracle Database 12.1.0.1, a tnsnames.ora entry must be manually added for the pluggable (PDB) database that must match the OMDATB field from the F98611 table. This will have its own SID that is different than the SID for the container database (CDB). For more details, see the "Pluggable Databases in Oracle 12cR1 and Higher" section of the JD Edwards EnterpriseOne Applications Installation Guide for UNIX with Oracle.