Understanding Package Deployment

After you assemble and build a package, you can select from several methods of deploying the package to workstations and servers throughout the enterprise. For workstations, the method that you select depends on whether Oracle's JD Edwards EnterpriseOne is already installed on the workstation.

Note: After a new client package that was built with Microsoft Visual C++ Compiler "X" is deployed to a workstation, the login will fail from that workstation if the associated runtime libraries are absent. The errors in the log will include, "Business function library load failed." The same error can occur with a server package if the server package is built on a machine with an "X" compiler and then deployed to a server without a compiler. A specific feature that installs the appropriate Microsoft Visual C++ compiler runtime libraries is required.For Tools Release 9.2.3 and above, Visual Studio 2017 runtime redistributables are required.

See "Appendix: Using the Microsoft Visual C++ Compiler" in the JD Edwards EnterpriseOne Administration Guide

This section discusses:

  • Deploying to workstations without JD Edwards EnterpriseOne.

  • Deploying to workstations with JD Edwards EnterpriseOne already installed.

  • Deploying to servers.

  • Deploying to tiered locations.

  • Deploying to workstations from CD.