Starting with JD Edwards EnterpriseOne release 8.12, EnterpriseOne specs are delivered in XML format. The new format enables the specs to be stored in database tables instead of the TAM files, and is called Shared Object Configuration. In this configuration, both Enterprise Servers and HTML Servers access the same database for the same set of specs.
Before release 8.12, whenever a new package was deployed to the Enterprise Server, you had to install the package on a development client and manually generate serialized objects for the HTML Server. With release 8.12, however, manual generation is now optional. Instead, the JD Edwards EnterpriseOne now automatically generates objects on the fly if they do not exist in the serialized object tables.
When you deploy a package to the Enterprise Server, the HTML Server automatically discovers the new package and purges all serialized records impacted by the package. If a full package is deployed, the HTML Server deletes all serialized object records. If an update package is deployed, the HTML Server deletes only those records that are included in the update package. It also removes the impacted objects from in-memory cache. After the package deployment is complete, when a user accesses an EnterpriseOne object, this object is generated on the fly using the new specs delivered in the package.
To ensure the integrity of the specs, the HTML Server must be configured so that:
Each EnterpriseOne HTML Server instance includes only one path code and one package within the path code.
All users accessing a JD Edwards EnterpriseOne HTML Server instance access only one package.
Serialized object databases are not shared among multiple EnterpriseOne HTML Server instances, unless all these instances run on the same path code and same package.
This section describes these topics:
During package deployment, the HTML Server stops responding to user requests until the package is deployed and serialized objects are purged. During this process, user will not able to log in. Users that are already logged in prior to the package deployment will not be able to launch new forms until the package deployment is complete.
Each package now contains a package manifest. The manifest is a record in a new table that is created every time a package is built. The package manifest contains a date/time stamp for the package build and information about the package content. For update packages, it also contains a list of objects included in the package.
Each serialized object table now contains a serialized object manifest. This manifest indicates what specs are used to generate the serialized objects. For example, the manifest includes the name of the package used to generate the serialized objects. To ensure the integrity of the system, all serialized objects are generated from the same package.
When the HTML Server detects a package deployment, it compares the package manifest with the serialized object manifest. If a new package is deployed, the package manifest will be different than the serialized object manifest. The HTML Server purges the serialized objects table of objects listed in the package manifest. The HTML Server then updates the serialized object manifest so it is consistent with the package manifest. This entire process is automatic and does not need administrator involvement.
If you decide to generate objects manually using the eGenerator, you must generate the manifest manually for the discovery process to work. For instructions on how to generate the manifest, see Section A.4, "Generating the Serialized Object Manifest" in Appendix A, "Generating JD Edwards EnterpriseOne Serialized Objects".