Understanding the Feature Build and Deployment Process

A feature is a set of files or configuration options, such as registry settings, that is copied to a workstation or server to support an application or other functions. Like objects, features are built into a package and deployed to the workstations and servers that require the feature components.

Note: Oracle's JD Edwards EnterpriseOne web development clients require a specific feature component to develop web-based objects.

Note: Oracle's JD Edwards EnterpriseOne machines that run Microsoft Windows, use business functions built with a Microsoft Visual C++ 2008 or higher level compiler, and do not have the same level Microsoft Visual C++ compiler installed locally, require a specific feature that installs the appropriate Microsoft Visual C++ Compiler runtime libraries.

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

You might also want to include any of these features when you build a package:

• ActiveX controls.

  The Application Design Aid tool enables you to include ActiveX controls in applications. If ActiveX controls are delivered with the software, you need a way to copy these controls to the workstation.

• Open Data Access (ODA) data sources.

  ODA requires that additional ODBC data sources be created on any workstation or server that uses ODA.

• Sales Force Automation databases.

  The Sales Force Automation feature requires that you install a separate Supported Local Database on the workstation so that it can be disconnected from the network during offline operation. You must also write a registry setting that indicates that the machine is used offline.

• GenCorba, GenCom, and other third-party interfaces or products.

  Each of these products and interfaces requires additional components on the workstation and server in order to function. As functionality expands to support additional third-party products and interfaces, these products will each have their own set of supporting files.

For software releases prior to JD Edwards EnterpriseOne 8.10, custom programming was required to add feature components to the workstation and server. You can now use familiar tools such as the JD Edwards EnterpriseOne Package Assembly Director and Package Build Definition Director to create a package that contains the feature, and then you can deploy it using the JD Edwards EnterpriseOne Package Deployment Director or multitier deployment.

Because feature components are not objects, the process for incorporating feature components into a package is slightly different from the normal package build process. Specifically, you must first define the feature before you can add it to a package.