![tibco gems download tibco gems download](https://tibtechtutorial.files.wordpress.com/2020/02/image-28.png)
Tibco gems download code#
Wherever differences exist between SDC and PDC code, an EAR file (representing the code base) will be exported from PDC and used to deploy the application in DC1 this will mitigate the issue of not having the same code to test against the production environment.Reasons for why PDC is not cloned: TIBCO domain names of production environment will be in used DC1/DC2 Changing of TIBCO domain names is strongly discouraged by the Vendor Same TIBCO domain names cannot be used when migration of PDC components take place when we are migrating the TIBCO Prod environment in DC1/DC2 No test environment to verify the approach in totality
![tibco gems download tibco gems download](https://www.jbrandsma.com/wordpress/wp-content/uploads/2019/01/383404a5bc8ea8829f470023830b6c93.png)
The code base used for the migration is taken from SDC. Key DecisionThe Staging environment will be cloned for the migration, and made available to SAP Project.
Tibco gems download upgrade#
Upgrade of iProcess from 10.2 to 11.1 prior to migration (due to go-live by end of August.) Support extension of the TIBCO components including Business Works 5.3 The TIBCO Upgrade Project will be put on hold during the migration. The SDC/PDC environment remain intact during migration. My understanding is that the Solution Management has confirmed opinion that this approach is practical in EA environment. The viability of the Migration approach that has been handed over to the EAI team by the Solution Management as a directive from Ed. Support extension has been procured from vendor (TIBCO) until 2012 Key Dependencies Infrastructure Availability in-time so that the SAP Upgrade project timelines can be met.(11 LPARs and 1 Wintel servers are required in new data centre for creating a staging environment)
![tibco gems download tibco gems download](https://www.researchgate.net/profile/Mohammad-Aziz-4/publication/267179927/figure/fig11/AS:341512132022298@1458434246326/Flow-diagram-for-Analysis-Strategy-AThe-entire-analyses-is-categorized-into-fours.png)
The initial time lines from the SAP Upgrade project was that we need to migrate the GEMS applications by mid-September 2010 We need to provide the rest of the applications interfacing with SAP by midOctober 2010 Step 2 : Migrate the rest of the applications across to the new data centre For this, we will migrate all applications that are interfacing with SAP. ScopeThe TIBCO Migration stream of project has been logically divided into two Steps: Step 1 : Provide a TIBCO UAT Environment for the SAP Upgrade project. Overview Scope Key Dependencies Key Decision Risks Current Status Migration Solution Technical details TIBCO Middleware MigrationMigration SolutionDevelopment Services