Understanding the Platform Pack Installation

Rather than transferring all the software from the Deployment Server, the Platform Pack installs the code and database directly to the Enterprise Server. This more direct installation method increases performance during this part of the process. It is especially beneficial in situations in which the Enterprise Server is connected to the Deployment Server using a wide area network (WAN). Since the Deployment Server and Platform Pack have separate Installers, they can be running concurrently which decreases the overall installation time (assuming the Installers are run on different machines).

However, new for Tools and Application Releases for 9.2, customers must build a full package after the Platform Pack completes. Customers will not be able to build an update package out of the box. This is due to changes in Server Only Package Build, which was introduced with Tools Release 9.1.5).

Note: Although the Platform Pack will no longer deliver packages, it still delivers the Package Repository and the package definition records because these are needed in order to run services. The Platform Pack will not deliver the source and include files (for example, obj and lib) for the package. The directories are delivered in the path code on the Deployment Server, just not as a package.