Version: 4.3
Related Product: SAP Data Services v4.3.x
Overview
This is another cycle of IPS v4.2 -> 4.3 upgrade again, and the same issues happened last time 10+ year ago for IPS v4.1 -> 4.2 is happening again this time. This is due to no SAP IPS v4.3 upgrade document, and it is based on SAP KB that only those who have paid SAP Support account can see it.
This post is to highlight all the known issues which SAP IPS team think this is the "normal" process that customer should aware of. My objective is to address the frustration in both IPS v4.3 and Data Services v4.3 upgrade.
Issues Highlight
1. SAP IPS v4.3 fresh installation does not required to enter license key by using InstallIPS.exe (Windows) or InstallIPS (Linux(, but if you perform in-place upgrade, then you need to enter IPS v4.3 license key which SAP document doesn't say (there is no IPS upgrade doc)
2. When doing IPS v4.2 -> v4.3 in-place upgrade, both InstallIPS.exe and setup.exe will not pass the IPS v4.3 license key into the IPS v4.2. So you must enter SAP IPS v4.3 license key into it after completed IPS v4.3 upgrade
3. SAP KB title will use the word "BIP 4.3" instead of "IPS 4.3" so it is not easy to find SAP KB to tell you that you need to use their license request page to generate IPS v4.3 license key (SAP's desire process)
4. SAP admin who has SAP Support access is not able to see the IPS product in the license key request page in SAP Support homepage (which in another SAP KB for IPS v4.1 to tell you to raise SAP ticket)
5. To leverage the bundled IPS v4.3 license key, you need to fully uninstall IPS v4.2
6. For those who plan to uninstall IPS
6.1 if you have multiple IPS v4.2 patches installed in the machine (Windows only), the Windows uninstall method might break the IPS v4.2 before you fully uninstall all IPS product patches. So the Windows machine will not be able to completely uninstall IPS v4.2
6.2. if you didn't select "Reset database" during IPS installation, and reuse your IPS v4.2 DB, then InstallIPS.exe installer still won't register the IPS v4.3 license kehy
7. SAP Support actually recommends fresh IPS and BODS installation instead of in-place upgrade. Any in-place upgrade issues will get their recommendation to perform fresh IPS & BODS installation
8. IPS v4.3 license key should be entered in CMC > License Key screen immediately after IPS v4.3 installation. Some people proceeds with SAP BODS v4.3 installation without entering IPS v4.3 key, and causes IPS 4.3 and BODS 4.3 to be broken
9. After BODS v4.3 is broken, entering IPS v4.3 license key will not automatically fix it. It only allows IPS daemons to be able to start
10. SAP BODS v4.2 and v4.3's ATL file is not compatible, but SAP DS Designer v4.2 will allow to import v4.3 ATL file. For Designer v4.3, it will display a warning of incompatibility, but allows user to proceed to import atl
11.. SAP Data Services v4.2 will get a false login failed message when trying to login to BODS v4.3, which often confuse admin and developer that the credential is wrong, or there is a network issue
12. If developers are doing development in BODS v4.2 and v4.3, then it is a length process to clone BODS v4.2 repo to another DB, runs repoman (Linux) to upgrade it, and finally register into CMC v4.3. This has to repeat many times until all developers moved to v4.3
Manually Getting IPS v4.3 License Key
1. InstallIPS.exe or InstallIPS contains the IPS v4.3 license key even you can't open the executable file
2. Uses Linux to remove all binary data: strings InstallIPS.exe > /tmp/installips_key.txt
3. Uses Linux to display the IPS v4.3 license key: grep "ProductKey" /tmp/installips_key.txt
Reminder:
1. If you IPS v4.2 is currently not healthy, upgrading to v4.3 won't automatic fix a broken IPS
2. If you installed SAP BODS v4.3 over IPS v4.3 without license key, entering IPS v4.3 license key later might not make BODS fully functional. This is version specific, so I can't tell for all the IPS and BODS patches
Recommendation for Upgrade
Performs fresh IPS and BODS v4.3 installation instead of in-place upgrade. Takes the opportunity to upgrade your Windows OS, or RHEL OS, MS SQL Server, Oracle, DB drivers.
Recommended procedure:
1. Backup your both IPS v4.2 and BODS v4.2 repositories
2. Creates a new empty BODS repositories to be used for v4.3
3. You can reuse IPS v4.2 repositories, but BODS v4.2 repositories can be re-use (manually register into SAP CMC > Data Services)
4. Perform fresh IPS v4.3 installation using either old or new IPS DB
5. If you are re-using IPS v4.2 DB, then enable checklist "Reset database" in the installer wizard
6. After installation (~ 1 hr), login to CMC, and ensures License Key screen show the license is valid
7. Proceeds with SAP BODS v4.3 installation, but uses the newly created BODS repository DB
8. After SAP BODS v4.3 installation completed, checks in CMC > Data Services to ensure you are seeing 1 repository
9. Run "Repository Manager" (Windows) or repoman (Linux) and choose "Upgrade" option to upgrade each of the BODS v4.2 repositories. You need to do this multiple round, as you can only specify 1 DB to upgrade its table content v4.2 -> v4.3
10. Login to CMC v4.3 to register each of the BODS v4.2 (upgraded to v4.3 now). You should not get version conflict
11. Run Server Manager (Windows) or svrcfg (Linux), and register each of the BODS repositories you added to CMC just now
12. Login to SAP DSMC, and generate new password files
13. In SAP DSMC, create new schedules
14. In SAP DSMC (Linux only), create Excel adapter, if you leverage xls file operations in Dataflow
15. In SAP CMC, configures user/group permission, such as allow user to retrieve BODS repositories credential (DS Designer won't show add'l prompt to ask for BODS repository password)
16. For Windows, if you want to start the Windows service with specific account (service account), then configures Windows Services startup properties
17. If you enable SSL, then repeat the SSL configuration for DB, IPS, Tomcat, BODS, DS Designer
No comments:
Post a Comment