Hello,
We are preparing to upgrade our Siebel IP2013 Call Center application to IP2016 including all patch sets (2016.19). This is a technical upgrade (no new functionality included in the upgrade effort) and under normal circumstances would consist of a migration installation followed by an incremental repository merge (IRM), but in our case, because the application is being deployed on all new platforms, we will be doing a new installation followed by an incremental repository merge. Here are the major steps we intend to execute for our DEV upgrade:
1. Install Oracle 12c DB client (32 bit)
2. Install Siebel IP2016 Enterprise (Name Server, App Servers, DB Utilities, SWSE)
3. Configure Siebel IP2016 Enterprise Sever, Name Server and SWSE.
4. Install Siebel IP2016 Tools client on Siebel IP2016 App Server platform
5 Import a copy of the Siebel IP2013 DEV schema (Siebel) to the Siebel IP2016 database platform (Oracle 12c)
6. Import and copy Siebel IP2013 Ancestor Repositories
7. Execute IRM (upgrep)
8. Take DB Backup
9. Run DB Stats
10. Start the IRM - repository merge process using the Siebel IP2016 Tools client
11. Resolve conflicts from the merge process using the Siebel IP2016 Tools client
12. Take DB backup
13. Run IRM (upgphys)
14. Take DB backup
15. Configure Siebel IP2016 App Servers
16. Compile SRF from merged IP2016 Repository using the Siebel IP2016 Tools client
17. Deploy SRF and complete other post-upgrade tasks
18. Test Web Client against Siebel IP2016 Call Center application
19. Install IP2016.19 patch set on all applicable components
20. Apply manual changes for all Siebel IP2016 patch sets
21. Compile SRF from IP2016.19 repository using the Siebel IP2016 Tools client
22. Deploy SRF
23. Test Web Client against Siebel IP2016.19 Call Center application
Based on the scenario we have and the steps above, I have three specific questions I was hoping to get your input on:
1. Is it acceptable to use the Siebel IP2016 Tools client (instead of the Siebel IP2013 Tools client) to execute the Incremental Repository Merge? I know the documentation implies that you would use the Siebel IP2013 Tools client, but I thought that might be a function of doing a migration upgrade (where the IP2013 Tools client is already installed on the server being upgraded) versus a technical requirement. We can install the IP2013 Tools client on the new Siebel IP2016 server platform, but don't want to if it is not necessary.
2. I know the instructions for applying patch sets as part of an upgrade recommend that they be applied immediately following installation of the upgrade software, but we were planning to delay it until we have completed the upgrade installations, IRM and verified the results of the base upgrade. Once we have completed and verified the upgrade to IP2016 base, we would apply the IP2016.19 patch set and manual changes. Is this approach acceptable?
3. For steps 16 and 21, is it still necessary to generate browser scripts with Siebel IP2016?
Thanks for reviewing this item and providing your input.
John L