Configurable Network Computing Fundamentals
JD Edwards EnterpriseOne Tools Configurable Network Computing Implementation Guide
The Spec.ini is a new file that is deployed to the \spec directory when a full package is
installed. This file points to an XML package in a database.
The different deployments by releases are:
Deployment prior to 896:
Specs are in TAM binary format.
Specs are stored on the local file system.
A tool ("eGenerator") is used to convert TAM specs to serialized objects.
Generation is manual and needs to be done every time a package is deployed.
Generation only from a Windows client
Deployment in 896:
TAM Deployment (8.10, 8.11) is still supported. It uses the same deployment
model as prior service packs.
H4A special cases.
XML Deployment (starting with 8.12) for Windows client, Enterprise server,
Deployment in 896 (H4A).
No change. Specs will be generated from the local package, in TAM or XML.
No configuration changes required for Metadata.
Configuration flags in jdbj.ini will be ignored. specGenerateOnDemand is
ignored and considered true.
Deployment in 896 (XML)
For all nodes the Specs are stored in XML in a RDBMS.
The Windows Client uses the local MSDE database with XML specs. The
Spec.ini file is located in the \spec folder and points to the local database. It is
deployed when a full package is installed on the fat client.
The Enterprise Server Spec.ini is deployed to the \spec directory when a full
package is installed and points to an XML package in a database.
Java node (JAS Server, RTE server, and so forth).
220.127.116.11 Java Node auto-discovery
JD Edwards EnterpriseOne Java nodes utilizes a new deployment model called
Discovery Process which enables the system to be in charge of controlling the
deployment. Deployment of a package is fully automated. This process increases
integrity and is best suited for production environments.
The web server Discovery Process will:
Locate the "default" enterprise server. The "default" server is defined as the default
BSFN server for the signed-on user.
Find what package is deployed on that server.
Find the content of the package (including incremental package updates).
Delete any obsolete serialized objects.
Generate serialized objects on demand.
Some of the benefits to the Discovery Process deployment are: