JD Edwards EnterpriseOne stores these objects in a database (in serialized object tables F989998 & F989999), and retrieves them at runtime.ĮGenerator requires a specific machine configuration. The JD Edwards EnterpriseOne forms and applications that you generate, either manually from eGenerator, or automatically using on-demand generation, are serialized Java objects. The eGenerator allows manual control over the process that turns JD Edwards EnterpriseOne specifications into Java code, which enables you to access JD Edwards EnterpriseOne applications in HTML. eGenerator is also an optional path for generating any set of objects, including a complete set of objects. It is the only method for generating FDA-created portlets, so is required if you installed a JD Edwards EnterpriseOne Portal. The tasks described in this appendix are only valid for the JD Edwards EnterpriseOne 8.12 application.ĮGenerator can still be used to manually generate serialized objects. If you are running JD Edwards EnterpriseOne application version 8.9, 8.10, 8.11, or 8.11 SP1 with the 8.96 Tools Release, refer to the 8.95 version of the guide to install and configure eGenerator.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |