There is a new installation mechanism introduced in SAP BusinessObjects BI 4.2 release called Split Install. The main idea behind this new innovation is to reduce the system downtime by splitting the installation process into two steps:
- Caching the installation: This will cache the install binaries to system directory.
- Resume after Caching : you have two options to resume the installation from the cache:
- Resume after caching and perform the update installation in parallel, when you have multiple nodes or servers in your clustered landscape.
- Resume after caching and perform the update installation sequentially.
In this pattern book, we have performed the installation using new split install feature. Therefore, the update workflow (actual installation), which is captured in this book is divided two parts:
- After caching
- We are providing the users a way to perform caching separately, before the actual installation. This will facilitate the users to reduce the down-time of the system, which we invest in order to cache the deployment units. After the updating the cache, the user can continue to use the system, as the system would still continue to work in the previous (live) state without any update patch. Therefore, the users can continue using the system during the caching process.
- After completing the Cache step, the admin can resume the installation at any point of time. To resume the installation, user needs to update the response file generated during the Cache step with the sensitive information at the respective place holders. Once the install is completed, response file containing the sensitive information can be deleted or reused for similar installation scenarios. You can perform the Resume steps as shown below:
For example, setup.exe –’resume_after_cache’response.ini (You need to provide the response file generated during the Cache step after updating with sensitive information.)
As mentioned above, once you cache the installation, there are two ways to run the actual installation.
- Run the cache sequentially in clustered machines.
- Run the cache in parallel on clustered machines.
In this pattern book, we’ve applied both sequential and parallel method of updating the BI 4.0 and 4.1 systems and captured the steps for your reference. For more information about split installation, see BI 4.2 what’s New guide.
Previous Section: SAP BI Pattern Book - Updating SAP BI 4.x to SAP BI 4.2