| Purpose |
| Data Dictionary Overview |
| Scope |
| Details |
| Deploying Data Dictionary Changes to Client Workstations |
| Deploying Data Dictionary Changes to the Enterprise Server |
| Deploying Data Dictionary Changes for the Web (HTML) Client |
| For release EnterpriseOne 8.12 and higher |
| For releases prior to EnterpriseOne 8.12 |
| Deploying Glossary Text Changes to the Web Client |
| Deploying Data Dictionary Changes to the Terminal Server (Release 8.10 and prior) |
| Creating a Full Set of Data Dictionary and Global Table Specs (Releases prior to 8.12) |
Since one Data Dictionary (DD) is recommended for all JD Edwards EnterpriseOne software environments, changing the data dictionary in one environment (such as Development) also affects other environments, e.g. Production and Prototype. If data dictionary is implemented by Environment, it must be implemented by Pathcode because data dictionary specs are created per pathcode. If multiple environments share the same path code, they must also share the same data dictionary.
When a change is made to the data dictionary using the Dictionary Design Application (P92001), the change affects the Data Dictionary master tables which are on the Enterprise Server. A change to a data dictionary item includes changes to the description, row description, column title, selection to allow row security, display decimals for the QTYINV Class and QNTY data item, changes to error message text or level, etc. Any data dictionary changes of these types require that the data dictionary be deployed.
A local copy of data dictionary specifications is maintained and used within an environment whenever data dictionary information is needed by interactive or batch applications. When an interactive or batch application is running, DD item specifications are installed just-in-time (JITI) from the master tables on the enterprise server to the local copy of the DD specifications. This JITI occurs only once per data item when the item is referenced within the application. Any subsequent changes made to a previously referenced DD item do not JITI again. When making data dictionary changes, it is therefore necessary to deploy them to verify that all workstations and servers have the current and correct information.
For more information on the Data Dictionary within EnterpriseOne, refer to Overview of EnterpriseOne Data Dictionary
This document details how to deploy Data Dictionary changes within EnterpriseOne.
This document is intended for the Data Dictionary System Administrator who will be deploying Data Dictionary changes.
To deploy data dictionary changes to a client workstation, delete the global table specs and DD table specs - glbltbl, dddict, ddtext (.ddb and .xdb) under each pathcode (a total of six files). The files are located in the /pathcode/spec directory. The next time a user signs on to the EnterpriseOne software, these table specs will JITI (Just in Time Install) current data dictionary information to the local workstation specifications from the DD master tables when DD items are referenced in interactive or batch applications.
Choose of the following methods to delete the global and data dictionary table specs :-
1. Enterprise Server
• End E1 services
• Delete the global and data dictionary table specs (glbltbl, dddict, ddtext - .ddb and .xdb) under each pathcode
• Restart services
2. Starting with tools release 8.98.3.0 with the Quick Package Deployment Functionality Document 1093018.1, the dddict/ddtext/glbltbl files under the pathcode/spec directory are deleted after an Update Package for the pathcode, containing any object type except an interactive application (Pxxxx), is deployed to the Server
3. Deploy Full Package for the pathcode which deletes dddict/ddtext/glbltbl files under the pathcode/spec directory
The global and data dictionary table specs are re-created through JITI as UBEs or business functions run on the server and reference DD items
The deployment process is slightly different for EnterpriseOne 8.12 and higher releases that use metadata (XML); there is no need to run R92TAM and R98CRTGL. The eGenerator does not look at any local TAM specs when running against metadata XML specs, including those built by R92TAM and R98CRTGTL (glbltbl, dddict, and ddtext). All data item information comes from the F92xxx Data Dictionary tables. The location of these Data Dictionary tables is governed by OCM.
Choose one of the following methods when DD items are changed on EnterpriseOne 8.12 and above :
Method 1 Build and deploy a full server package (Preferred Method)
Build and Deploy a full server package. The auto-discovery process or on-demand generation will then occur for the JAS serialized objects to be regenerated automatically.
OR
Method 2 Run manual generation
Run a manual generation of the data dictionary data item. After manual generation, clear serialized objects cache in Server Manager. For information on manual generation review section Setup Generation Machine for Tools Release 8.96 and above in Document 1352463.1 E1: GEN: Generation Process Setup, Best Practices and Known Issues When Starting Generation.
OR
Method 3 Build a server update package
This method applies, starting with tools release 8.98.3.0 with the Quick Package Deployment Functionality Document 1093018.1. Identify the table that has a column based on the particular data item using UTB or Databrowser over the table F98711 Table Columns. Type in the data dictionary alias in the QBE column TDOBND in UTB or in the QBE column Data Dictionary Object Name in Data Browser. Deploy an update package of the identified table to the enterprise server. On-demand generation will occur for the table and the data dictionary items referenced in the table.
A full set of the data dictionary and global table specs should be created and installed on the generation machine to deploy data dictionary changes for the web client environment.
In the HTML environment, data dictionary information is built into the serialized object information for the applications that use the DD items. Therefore, generating only the data dictionary is not enough in the HTML environment when making a data dictionary change. All related objects that use that DD item must also be generated. Rather than attempting to identify all the affected objects, it is easiest to do a full generation or full package build depending on the release level.
On the Web Client, EnterpriseOne looks for the glossary text in the ddtext specs on the enterprise server that is specified in the JAS INI setting "glossaryTextServer=servername:port#" under [SERVER]. The system does not look into the Data Dictionary serialized objects.
When glossary text is changed in the Data Dictionary application, it is necessary to refresh the data dictionary specs for all path codes on the enterprise server by deleting the specs tables: dddict.ddb, dddict.xdb, ddtext.ddb, ddtext.xdb, glbltbl.ddb, glbltbl.xdb.
It is recommended that JITI be disabled in a TSE environment for performance reasons. Without JITI, a full set of global and data dictionary table specs must be installed on the Terminal Server. Once a full set of data dictionary and global table specs have been created, copy these tables specs (glbltbl, dddict, ddtext - .ddb and .xdb) from the fat client workstation where they were created to the Terminal Server for each pathcode.
See below for details on creating a full set of data dictionary and global table specs.
This process is necessary to deploy data dictionary changes to the Terminal Server and HTML web environments prior to release 8.12. The global table specs are built based on the DD spec information; it is important to create the data dictionary table specs before creating the global table specs. The process to build these specs is described below and must be executed on a non-TSE fat client workstation.
Building Data Dictionary Specs
Sign on to an environment, go to Batch Versions, and run the UBE R92TAM version XJDE0001 locally. This UBE creates a new set of replicated data dictionary specs under the b7 or b9 directory. Ensure that there is plenty of disk space on the C or D drive prior to running this process, which will take approximately four hours to complete.
After the UBE completes, there will be 4 table specs (dddict , ddtext - .ddb and .xdb) under the b7 or b9 directory. Move these four table specs on the workstation to the appropriate pathcode/spec directory for the environment signed onto, replacing the old data dictionary spec files.
Building Global Table Specs
Sign on to the environment/pathcode where the new data dictionary table specs have been moved. From Batch Versions, run the UBE R98CRTGL locally to build a full set of global table specs (glbltbl - .ddb and .xdb) in the b7 or b9 \pathcode\spec folder. This process takes a couple of hours to complete. After the UBE completes, verify the size of the glbltbl.ddb which should be around 25k.