E1: GEN: Overview and Best Practices for Web Generation / Serialized Object Generation Process, and Known Issues during Generation
(Doc ID 1352463.1)
Last updated on MARCH 12, 2021
JD Edwards EnterpriseOne Tools - Version SP24 and later Information in this document applies to any platform.
With introduction of HTML/Web Clients in EnterpriseOne, a new process called Web Generation or Serialized Object Generation was introduced. With Pre EnterpriseOne Application Release 8.12 and Tools Release 8.96 we had to manually perform the generation which converts the EnterpriseOne standard specifications in TAM format to java objects that can be used on HTML clients.
Starting with application release 8.12, JD Edwards EnterpriseOne specs are delivered in XML format, which allows for on-demand generation of serialized objects from these XML specs. Objects are now automatically generated when the first user accesses an application on web-client, and the only objects not automatically generated are FDA-created portlets. But eGenerator can still be used to manually generate serialized objects. It is the only method for generating FDA-create portlets, so is required if you installed a JD Edwards EnterpriseOne Portal. eGenerator is also an optional path for generating any set of objects, including a complete set of objects.
This document provides you a complete overview of Web Generation / Serialized Object Generation Process, best practices and known issues which can arise while starting/performing generation.
This document is intended for E1 CNC Administrators who create, configure and maintain the Web Generation machines and EnterpriseOne HTML Server (JAS) instances.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!