tibco sdc migration v0.2.ppt

TIBCO Middleware Migration

Migration Solution

Development Services

Overview

• Scope

• Key Dependencies

• Key Decision

• Risks

• Current Status

• Migration Solution Technical details

Dev

elop

men

t Ser

vice

s

Scope

• The TIBCO Migration stream of project has been logically divided into two Steps:– Step 1 : Provide a TIBCO UAT Environment for the SAP Upgrade project. For this, we

will migrate all applications that are interfacing with SAP.

– Step 2 : Migrate the rest of the applications across to the new data centre

• 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 mid-October 2010

Dev

elop

men

t Ser

vice

s

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)

• The viability of the Migration approach that has been handed over to the EAI team by the Solution Management as a directive from Ed. My understanding is that the Solution Management has confirmed opinion that this approach is practical in EA environment.

• The SDC/PDC environment remain intact during migration.• The TIBCO Upgrade Project will be put on hold during the migration.• 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 – Support extension has been procured from vendor (TIBCO) until 2012

Dev

elop

men

t Ser

vice

s

Key Decision

• The Staging environment will be cloned for the migration, and made available to SAP Project. The code base used for the migration is taken from SDC. 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

• The GEMS application will be made available to SAP Project first for their UAT.Reason: The understanding is that GEMS is an application that covers most of the functionalities that are

important from UAT perspective.

• Three TIBCO Resources from the EAI Team will be used for this project who will work in parallel.

Reason: The timeline is so short that it will not be possible to deliver with any less resources.

• TIBCO PSG will be engaged for TIBCO Centric technical review of the migration approach.

• During UAT testing in DC1/2, the code freeze in SDC/PDC cannot be guaranteed. This is due to :

– The possibility of urgent code fixes, – External entities may enforce code changes e.g. Regulatory changes in B2B, GEMS system,

normally every 6 months etc.– Other applications migrating to new DC that may require changes at EAI end, D

evel

opm

ent S

ervi

ces

Risks

• The infrastructure is still not available. Unless the infrastructure is available, it cannot be guaranteed that the SAP Project deadlines will be met.

• The ‘Image copy’ approach has not been tried & tested for TIBCO applications at EA and the TIBCO applications may not behave as expected .

• There is neither enough time, nor a test environment available, to test the approach thoroughly.

• IBM’s opinion is that the Full System Image Copy approach will technically work, but has significant performance and security related concerns associated with it because the image will be AIX5.3. Their strong recommendation was the approach to build the servers to OS level with AIX 6.1 and then copy the TIBCO image across. This approach was presented as Option 2 in our Migration approach document.

• The R3 Adapter patch will need to be installed because ECC6 is not compatible with the current R3 Adapter. That patch cannot be tested at the moment.

• For OMS, currently HACMP is used for failover. There is no HACMP proposed to be used in the new DC.

Dev

elop

men

t Ser

vice

s

Current Status

•Port details of DLD has been submitted, changes are being done pending review. The DLD is sufficient in the current state for IP addresses to be allocated.

•Build sheet for servers have been provided

•Project plan has been finalised.

•Work as per the project plan is in progress:– Proof of concept of reconfiguring TIBCO Admin after image

copy.– Proof of concept of configuring/Deploying TIBCO Application

running on the TIBCO Admin server.– Exported configuration files for Applications (60 Applications)– Modified the configuration files for the new DC.(40

Applications so far). Dev

elop

men

t Ser

vice

s

Major milestone timelines

Provisioning of TIBCO Admin & GEMS server (4 lpars + 1 Wintel) in new DC by IS

14th Sept ’10

Copy image to GEMS serves in new DC by IS

15th Sept ’10

Configure Tibco Admin in DC1AT10503 server

21st Sept ’10

GEMS Application migration 5th Oct ’10

Provisioning of other servers (7 lpars) in new DC by IS

4th Oct ’10

Tibco CMSSTG domain apps migration 5th Nov ’10

Tibco EMARTSTG domain apps migration

15th Nov ’10

Tibco OMSSTG & OMSTST domain apps migration

9th Dec ’10

Dev

elop

men

t Ser

vice

s

Migration Solution Technical details

• Current landscape for Staging

• TIBCO SDC Migration constraints

• Target landscape in new data centre (DC1) – Like to

Like

• Migration Approach

• Questions?

Dev

elop

men

t Ser

vice

s

Current landscape – Staging environment

B

SDC

OMSPrimary

STG

EASDCLPARD19

OMSSecondary

STG

EASDCLPARD18

eMart

STG

EASDCLPARD37

GEMS &

GASMKT

STG

EASDCLPARD24

B2B(iProcess 10.2)

STG

EASDCLPARD26

GEMS

EASDCLPARD12

BPMSTG / EAISTG

EASDCLPARD09

DOMAIN - CMSSTG

DOMAIN - OMSSTG

DOMAIN - EAISTG

DC1

(SAN)

STGESBSESBTESBD

CANON

EASDCLPARD18

HR_CHRIS, WebSales, NFTS,

NEMDnldEAI

DX-ETL

STG

EASDCLPARD23

CreditChk, Gas Wholsle

eForms, EDI(iProcess 10.6)

STG

EASDCLPARD25

Potential DR for WEBSales,

Intech & Expiry Service

EAHOBSRWSP01

STG

EASDCLPARD25

EFROMS

STG

EASDCLPARD37

EMARTS

WEBSales,Intech & Expiry

Service

EAHOBSRWSP02

WEBPRD

STGKCCM,GIS2ESB,

AddrClnsr,EA gateway, File

Server, Web, BAMEASDCLPARD27

Intech, GasDPI, Tibco Admin

STG

EASDCLPARD41

dc1at0820410.34.73.8esbitu1a02A.A.IT.P.01

Test HA/DR

dc1ad0801510.34.73.7esbitd1a01A.A.IT.P.01

Dev

dc2at0821810.48.73.9esbitu1a01A.A.IT.P.01

Test Main DB DB

DOMAIN - ETSITP1 / ETSITU1 / ETSITD1 ( for SSDM )

DOMAIN – WEBDC1 ( for Websales )

Non – Tibco Component

Database Server

TNEMGAST

EAIDCLPARD01(ETSLPARD01 /

ICEBERG)

NEMMCO DI STG

NEMMCOGEMSGAS

ENGYAUSTENERGYAPTCAUSTM

TCAMPGASMKT


SWPROSWUSER

B2BREPRTB2BUSER

B2B EDISTG

EAI

DB

PDC

STG

FTP Gateway

EAPDCBFTPP02

DC2

Dev

elop

men

t Ser

vice

s

Target landscape (SDC to DC1)

OMSPrimary

STG

EASDCLPARD19

OMSSecondary

STG

EASDCLPARD18

eMart

STG

EASDCLPARD37

GEMS &

GASMKT

STG

EASDCLPARD24

B2B(iProcess 10.2)

STG

EASDCLPARD26

GEMS

EASDCLPARD12

BPMSTG / EAISTG

EASDCLPARD09

DOMAIN - CMSSTG

DOMAIN - OMSSTG

DOMAIN - EAISTG

(SAN)

STGESBSESBTESBD

CANON

EASDCLPARD18


NEMDnldEAI

DX-ETL

STG

EASDCLPARD23



STG

EASDCLPARD25

STG

EASDCLPARD25

EFROMS

STG

EASDCLPARD37

EMARTS

STGKCCM,GIS2ESB,




STG

EASDCLPARD41

Database Server


TCAMPGASMKT

ENGYAUSTENERGYAPTCAUSTMSWPRO

SWUSERB2BREPRTB2BUSER

B2B EDISTG

EAI

STG

FTP Gateway

EAPDCBFTPP02

OMSPrimary

STG

DC1AT10497

OMSSecondary

STG

DC1AT10496

eMart

STG

DC1AT10504

GEMS &

GASMKT

STG

DC1AT10499

B2B(iProcess 10.2)

STG

DC1AT10501

GEMS

DC1AT10507

BPMSTG / EAISTG

DC1AT10506

DOMAIN - CMSSTG

DOMAIN - OMSSTG

DOMAIN - EAISTG

(SAN)

STGESBSESBTESBD

CANON

DC1AT10496


NEMDnldEAI

DX-ETL

STG

DC1AT10498



STG

DC1AT10500

STG

DC1AT10500

EFROMS

STG

DC1AT10504

EMARTS

STGKCCM,GIS2ESB,


Server, Web, BAMDC1AT10502


STG

DC1AT10503

Database Server


TCAMPGASMKT


SWPROSWUSER

B2BREPRTB2BUSER

B2B EDISTG

EAI

STG

FTP Gateway

DC1WT10521

SDC DC1PDC

Dev

elop

men

t Ser

vice

s

Migration Approach

SDC CMSSTG TIBCO Domain (Example)

Migrating TIBCO Admin

SDC

GEMS &

GASMKT

STG

EASDCLPARD24

B2B(iProcess 10.2)

STG

EASDCLPARD26

DOMAIN - CMSSTG


NEMDnldEAI

DX-ETL

STG

EASDCLPARD23



STG

EASDCLPARD25

STG

EASDCLPARD25

EFROMS

STGKCCM,GIS2ESB,




EASDCLPARD41

DC1

GEMS

EASDCLPARD12

BPMSTG / EAISTG

EASDCLPARD09

Database Servers


TCAMPGASMKT



B2B EDISTG

EAI

STG


DC1AT10503

Step 1: Create an image copy of current CMSSTG TIBCO Admin server (using mksysb and TSM Backup & Restore), image includes OS and file system

Step 2: Copy image to new built server DC1AT10503

Dev

elop

men

t Ser

vice

s


DC1AT10503

Step 3: Log in into the new TIBCO Admin server DC1AT10503 and ‘su – tibstg’

Step 4: Change directory to /EAI/tibco/tra/5.6/bin

Step 5: Execute the TIBCO utility MoveMachine as follows MoveMachine -domain CMSSTG -oldMachine easdclpard41 –newMachine DC1AT10503

Step 6: Rename vpd.properties.tibco.easdclpard41 to vpd.properties.tibco.dc1at10503 (file found in the user home directory, which is /EAI/tibco/STG)

Changing references from old to new admin server on the new machine

Dev

elop

men

t Ser

vice

s


DC1AT10503

Step 7: Make sure no references to old admin server still exist under the administrator folder by running the following shell scriptfor file in $(grep -iR "easdclpard41" /EAI/tibco/administrator | cut -d\: -f1 |sort |uniq) do echo "Processing file --> " $file cp $file ${file}.bkp cp $file ${file}.tmp sed 's/easdclpard41/DC1AT10503/g' ${file}.tmp > $file rm ${file}.tmp done

Main files are: /EAI/tibco/administrator/5.6/tomcat/webapps/ROOT/index.js /EAI/tibco/administrator/domain/CMSSTG/data/SYS_CMSSTG.dat

Note: As the new admin server machine will be in a different subnet not like the old admin server, MoveMachine tool will not be able to update all required files for old references, and that is why a shell script is used to complete the update.

Continue - Changing references

Dev

elop

men

t Ser

vice

s


DC1AT10503

Step 8: Start Admin and Hawk, verify both started ok by checking logs

Start-up and Verification

Step 9: Verify login to TIBCO Admin via browser

Note: CMSSTG same TIBCO Domain name is maintained

Dev

elop

men

t Ser

vice

s


DC1AT10503

Step 10: Verify machine DC1AT10503 appear with status ok in the list of machines, as well as all applications deployed on the same DC1AT10503 machine appear with status stopped and ok

Continue - Start-up and Verification

Dev

elop

men

t Ser

vice

s

CMSSTG TIBCO Admin Migrated

Dev

elop

men

t Ser

vice

s

Migrating GEMS Applications

SDC

GEMS &

GASMKT

STG

EASDCLPARD24

B2B(iProcess 10.2)

STG

EASDCLPARD26

DOMAIN - CMSSTG


NEMDnldEAI

DX-ETL

STG

EASDCLPARD23



STG

EASDCLPARD25

STG

EASDCLPARD25

EFROMS

STGKCCM,GIS2ESB,




EASDCLPARD41

DC1

GEMS

EASDCLPARD12

BPMSTG / EAISTG

EASDCLPARD09

Database Servers


TCAMPGASMKT



B2B EDISTG

EAI

STG


DC1AT10503

GEMS &

GASMKT

DC1AT10499

KCCM,GIS2ESB,AddrClnsr,

EA gateway, File Server, Web, BAMDC1AT10502

DOMAIN - CMSSTG

GEMS

DC1AT10507


TCAMPGASMKT

Step 1: Create an image copy (using mksysb and TSM Backup & Restore) of easdclpard24, easdclpard27 and easdclpard12 servers. Image includes OS and file system

Step 2: Copy images to new corresponding built servers

Dev

elop

men

t Ser

vice

s

Step 3: On DC1AT10499 Execute the TIBCO utility MoveMachine as follows MoveMachine -domain CMSSTG -oldMachine easdclpard24 –newMachine DC1AT10499

GEMS &

GASMKT

DC1AT10499

KCCM,GIS2ESB,AddrClnsr,

EA gateway, File Server, Web, BAMDC1AT10502

Step 4: On DC1AT10502 Execute the TIBCO utility MoveMachine as follows MoveMachine -domain CMSSTG -oldMachine easdclpard27 –newMachine DC1AT10502

Step 5: Use the same shell script used in TIBCO Admin migration step 7, to find and replace references to easdclpard24 and easdclpard27 in the new admin server DC1AT10503, then restart TIBCO Admin and Hawk on admin server

Step 6: On DC1AT10499 and DC1AT10502, start Hawk, verify Hawk has started on both machines fine and no errors are in logs

Dev

elop

men

t Ser

vice

s

Step 8: Log in into the new TIBCO Admin web page, and verify both machines DC2AT10499 and DC2AT10502 appear with status ok in the list of machines, and also applications deployed on those machine appear also ok and with state equal to stopped

Dev

elop

men

t Ser

vice

s

Step 9: Export GEMS applications xml configurations using AppManage (only configuration and not ear files). Export has to happen from the new admin server.

Step 10: Edit exported xml config files and change all required global variables to point to new end systems (i.e new SAP DEV in DC2, and new database URLs)

Step 11: Re-deploy GEMS applications (with new xml configuration files, without ear files) from the new admin server using AppManage

Step 12: Start applications and verify logs contain no errors

Step 13: Smoke Test GEMS applications (verify no connectivity issues against all end systems – Sanity check )

Note: All required databases for GEMS should have already been copied (image copy) and started on the new servers with new configuration changes, and verified before starting GEMS TIBCO applications

Dev

elop

men

t Ser

vice

s

Questions?

Dev

elop

men

t Ser

vice

s

tibco sdc migration v0.2.ppt

Documents