Object Storage

By industry standards, an object is a self-sufficient entity that contains data as well as the structures and functions that are used to manipulate the data. An object is also a reusable entity that is based on software specifications. A specification is a complete description of a system object. Each object has one or more of its own specifications.

The system stores objects in four formats:

• Central objects are stored in a relational database format.

  Objects are stored in a central location to enable deployment and development. Central objects consist of object specifications for each JD Edwards EnterpriseOne object and C components for code-generated objects. Central object specifications are stored in a relational database on a data server.

• Package objects, or replicated objects, are stored in XML format in a relational database.

  Package objects are created during the package build process. You can specify the database data source in which to build the shared spec repository. This shared repository usually exists on a data server. Several enterprise servers and web servers can share this repository.

• Serialized objects are stored in database tables and used by web clients at runtime.

  Web servers use on-demand generation to create serialized objects from the shared spec data source. The generator converts specs into Java code, which enables you to access the JD Edwards EnterpriseOne applications in HTML. The system stores the objects in a relational database and retrieves them at runtime.

• File objects .c,.h,.hxx, and .jar, associated with business functions, tables, UBE, Business view and Business Services are stored in a Par file in the F98780R Repository table and F98780H Repository History table.

  Also, for every Application with a bit map, these are also stored in a Par file in this table. Every path code has one Central Objects table where these are stored. During package build these are retrieved from the F98780R and used in the package.