|JD Edwards EnterpriseOne Tools Product Packaging Guide
|PDF · Mobi · ePub|
This chapter contains the following topics:
Oracle's JD Edwards EnterpriseOne Product Packaging describes the different methods used to package JD Edwards EnterpriseOne objects and data so that they can easily be moved from one machine to another. You can use the Object Packaging Tools or Software Mastering Tools to package and move the objects and data.
The Object Packaging Tools provide a streamlined alternative to using the full set of Software Mastering Tools. There are two methods for using the Object Packaging Tools. The first method uses Object Management Workbench (OMW) to provide a simple way to transfer a single newly-developed or customized object from one machine to another in order to test it or to continue development. The second method uses Configuration Assistant to easily develop and package configurations and reuse the intellectual property that you have developed.
The full set of Software Mastering Tools gives you the ability to create your own software mastering processes. In this capacity, the tools oversee the entire mastering process from defining a software master to mastering a CD. The tools start with the definition process, where you provide as much initial information as possible. After you enter the critical information, the tools provide batch processes to validate the software mastering information before mastering, to master the software, and to validate the final software master image. This process gives you the ability to determine which objects should be shared between locations and create a custom installation that can be burned onto a CD. Then the CD can be used to deploy this custom installation anywhere within the enterprise.
JD Edwards EnterpriseOne standardizes and automates software installation, making many steps transparent to users. Technical setup is preconfigured to meet the requirements of many JD Edwards EnterpriseOne customers. In addition, JD Edwards EnterpriseOne products are preintegrated and share a common database, which reduces the implementation process, minimizes ongoing administration, and provides customers with the flexibility to add new applications, modules, and tools as needed.