Enterprise Server Deployment

EnterpriseOne is a multi-tier system that executes "Applications". The applications logic is contained in a "Package". These packages are built and deployed on "Nodes". Nodes are the participants in the system; such as a Windows client, Enterprise server, Java node (for example: HTML server, RTE server), and so forth.

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, Java nodes.

• 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.