Configurable Network Computing Fundamentals
3-6
JD Edwards EnterpriseOne Tools Configurable Network Computing Implementation Guide
3.3.5.1 Central Objects
You store objects in a central location to enable for these:
Deployment
Redeployment
Development
Central objects consist of object specifications for each JD Edwards EnterpriseOne
object and C components for code-generated objects. Store the central object
specifications in a relational database on either a deployment server or an enterprise
server, depending on available resources. Store C components for code-generated
objects in directories on the deployment server.
To deploy objects out to the enterprise, you define a package that JD Edwards
EnterpriseOne creates from central objects. Each package contains a copy of the central
objects. This copy consists of object specifications, and linked and compiled C
components.
3.3.5.2 Package Objects
A package contains the necessary specifications and function libraries to run the
business applications. Win32 clients have their own dedicated packages while servers
share a single package. For example, to execute the Address Book application on a
workstation, the workstation needs the object specifications and the compiled dynamic
link library for the Address Book application and for any object that the application
uses, such as data dictionary items, tables, and business views. The workstation and
Enterprise server will store the compiled libraries on its file system. The object
specifications will be stored in a Spec package.
A JD Edwards EnterpriseOne server shares a spec package contained in an enterprise
RDMS with other JD Edwards EnterpriseOne servers and other web servers. A JD
Edwards EnterpriseOne workstation now has a local database instead of TAM files.
3.3.5.3 Serialized Objects
The web server uses on-demand generation to create serialized objects from the shared
object package when needed at runtime. The generator turns JD Edwards
EnterpriseOne specifications into Java code, which enables you to access JD Edwards
EnterpriseOne applications in HTML. The JD Edwards EnterpriseOne forms and
applications that are generated are HTML objects. JD Edwards EnterpriseOne stores
the objects in the local database and retrieves them at runtime. The serialized objects
serve the function of a persistent cache.
3.3.6 Object Deployment
Deploy JD Edwards EnterpriseOne to the workstations and servers using any of these
methods:
Initial installation, for workstations and servers.
Workstation installation, for workstations.
Application installation, for workstations.
Just-in-time installation, for workstations.