E1: ENV: Overview of Specifications (SPEC) in EnterpriseOne
(Doc ID 1142313.1)
Last updated on JANUARY 21, 2022
Applies to:
JD Edwards EnterpriseOne Tools - Version SP23 and Prior and later Information in this document applies to any platform.
Purpose
This document describes concise information on EnterpriseOne specification. Detailed information can be found in the "Package Management Guide" depending on your Tools Release. See references below. Latest Package Management Guide can be found under:
The details covered in this document is in reference to E1 specification which is the attribute of a certain object. In general, an object is made up of 'C Components' and 'SPEC' and this document will focus on specs.
Depending on encoding, location and usage, specs may be called from any of the following:
Object
Description
Central Object
This object implies it is the central repository of specifications.
TAMSpec
This is JDE's specific SPEC format with file extensions of *.xdb & *.ddb
SPEC
The short name for specification
Metadata
In this example, other than Business/Control data it may also be called metadata
Serialized Object
These objects have been generated into JAVA code that the JAS/HTML Server can interpret and use.
Notes:
In Database technology metadata refers to data which can contain for example, glbltbl. But in this document metadata will be used for specification.
Most of time, specification may be referred to as an object and its cache (object cache). In this document, object refers to serialized object rather than object in industry
Repository of specification is on the Database server and the repository of C and H components is on the Deployment server until tools release version 9.2.0.x
Starting with tools release 9.2.1.x a new repository location has been introduced for C and H components and the location of this repository is Database server. Thus, starting with tools release 9.2.1.x the repository of specification will always be on Database Server.
In industry, serialization/marshalling is the conversion of an object (spec in E1) to a series of bytes, so that the object/spec can be easily saved to persistent storage or streamed across a communication link. The byte stream can then be deserialised - converted into a replica of the original object.
Specification can be called,
Physical Data Format
RAWBLOB
RESOLVEDTAM
XML
Data Type (=Spec Repository)
TAM
RDB
FILE (e.g., <spec.zip>)
CACHE (in-memory object cache)
Spec Location
CENTRALOBJECT
LOCALUSER (location/type defined by local package)
REMOTEUSER (remote spec location including spec.zip)
TEMPER (TAM in 'PKG/spec/tempXXX)
Scope
This document is intended for the EnterpriseOne System Administrator or Developer who would like to gain an understanding of the EnterpriseOne specifications.
Details
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
