Understanding Automatic Pre-Generation of Serialized Objects

Note:

The automatic pre-generation of serialized objects feature supersedes the functionality of the eGenerator function of JD Edwards EnterpriseOne that was available in releases prior to Tools Release 9.2.6.

At some point you must generate JD Edwards EnterpriseOne specifications into Java code to access JD Edwards EnterpriseOne applications in HTML that is delivered using HTML/JAS Web Servers. The JD Edwards EnterpriseOne forms and applications that you generate are serialized Java objects. JD Edwards EnterpriseOne stores these objects in a database (in serialized object tables F989998 & F989999), and retrieves them at runtime.

The automatic pre-generation of serialized objects is optional. If you do not enable this feature to pre-generate serialized objects, then the objects will be generated on demand. If you enable automatic pre-generation of serialized objects, you can further specify which objects to pre-generate.

If you enable automatic pre-generation of serialized objects, and you do not list specific objects, then these objects are generated:

All objects that are not already generated (based on entries in the serialized object tables)
Any objects in a full or update package that are new or changed
All objects that are part of a newly applied Tools Release

Optionally, instead of generating objects as described above, you can specifically list objects to generate in these categories:

Applications To Generate
Reports To Generate
NERs To Generate
Business Views To Generate
Tables To Generate
Data Dictionaries To Generate

When enabled, the process for automatic pre-generation of serialized objects is triggered by a JD Edwards EnterpriseOne HTML Web Server machine restart or by the deployment of a new package (full or update). If multiple HTML/JAS Web Servers are configured to use this function, the system will only generate serialized objects for one server at a time.