Presentation is loading. Please wait.

Presentation is loading. Please wait.

E2G Web Services E2G Scripts and Methods E2G Domain Logic E2G Domain Logic Client Custom Scripts and Methods Client Custom Scripts and Methods E2G Rules.

Similar presentations


Presentation on theme: "E2G Web Services E2G Scripts and Methods E2G Domain Logic E2G Domain Logic Client Custom Scripts and Methods Client Custom Scripts and Methods E2G Rules."— Presentation transcript:

1 E2G Web Services E2G Scripts and Methods E2G Domain Logic E2G Domain Logic Client Custom Scripts and Methods Client Custom Scripts and Methods E2G Rules Engine E2G Interface Layer E2G Interface Layer Windows XP /Vista / Windows 7.Net Framework Windows XP /Vista / Windows 7.Net Framework Windows 2003 / 2008.Net Framework Windows 2003 / 2008.Net Framework Windows 2003 / 2008 SQL Server Windows 2003 / 2008 SQL Server E2G Windows UI E2G Windows UI Client Web UI Client Web Services Client Web Services Client Custom Code Client Custom Code Client Custom Configuration and Data Structures Client Custom Configuration and Data Structures E2G Configuration Data Structures Source Code Management Tool E2G compiled Code and Methods (.dll’s), Scripts Client Custom Code, Methods and Scripts E2G Client Configuration, Base and Customer Data E2G Client Configuration, Base and Customer Data E2G Data Access Layer

2 E2G Web Services E2G Scripts and Methods E2G Domain Logic E2G Domain Logic Client Custom Scripts and Methods Client Custom Scripts and Methods E2G Rules Engine E2G Interface Layer E2G Interface Layer Windows XP /Vista / Windows 7.Net Framework Windows XP /Vista / Windows 7.Net Framework Windows 2003 / 2008.Net Framework Windows 2003 / 2008.Net Framework Windows 2003 / 2008 SQL Server Windows 2003 / 2008 SQL Server E2G Windows UI E2G Windows UI Client Web UI Client Web Services Client Web Services Client Custom Code Client Custom Code Client Custom Configuration and Data Structures Client Custom Configuration and Data Structures E2G Configuration and Data Structures Source Code Management Tool E2G compiled Code and Methods (.dll’s), Scripts Client Custom Code, Methods and Scripts E2G Client Configuration and Data E2G Client Configuration and Data Extensibility Data Access Layer SOA Layer Application Layer Domain Entities

3 Deployment Development Server Prerequisites General Web Services StartUpWS Web Service XlifeUpdate Web Service LifeBO Web Service Apply Folder Settings and Permissions – Configuration of the COM+ Machine folder Configure E2G to run distributed – Configuration of the Loader.config file – Configuration of the SDT.XStartupUI.config file – Configuration of the XLife.config file – Using the ‘Startup Config Update.exe’ Source Control Server – We have to decide on the different source control options so that we can compile documents for the different options Setup XPAY Business Server Initial Setup Install and configure –.net4 Framework – SDT Crystal Reports Set Workstation prerequisites setup Create c:\SDTExergy Copy Loader.exe and Loader.Config from the XLifeUpdate folder on the transaction server to c:\SDTExergy folder Run Loader to synchronise, verify 5.2Configuration Workstation ? 5.3Development Workstation Configure Windows Component Services for E2G (MSDTC) Workstation Setup E2G Deployment Server and backups – What – How often – Where – Restore Requirements – Environment Setup (What is the purpose of this?) Housekeeping – why not in dev doc Backup – LifeBO – Startup Web Service – Xlife Update Ensure all users logged off Copy the following from the Release CD’s COM+ Machine folder to transaction server –LifeBO – Both the bin folder and the web.config should be copied to the LifeBO on the Transaction Server –StartUpWS – All the files from the CD should be copied to the StartUpWS folder on the Transaction ServerUpdate timestamps – XlifeUpdate – Copy all files EXCEPT the.config files from this folder to the XLifeUpdate folder on the Transaction Server – Update the.config files Xlife.config SDT.XStartUp.config – Update the timestamps by running the ‘Startup Config Update.exe’ from the XLifeUpdate folder Database Structure Upgrade Run scripts in CD Scripts Folder – 01_Structure scripts – 02_All – 03_Client specific Code Updates with new releases SQL Server Installation Database Server Prerequisites Database Server MSDTC configuration Database Server Web Quote Business Server Web Quote SQL Server setup and configuration QIS Business Server Integration Server ITP Server MIS Server Optional Component Installation

4 Deployment Test Server Prerequisites General Web Services StartUpWS Web Service XlifeUpdate Web Service LifeBO Web Service Apply Folder Settings and Permissions – Configuration of the COM+ Machine folder Configure E2G to run distributed – Configuration of the Loader.config file – Configuration of the SDT.XStartupUI.config file – Configuration of the XLife.config file – Using the ‘Startup Config Update.exe’ 3 Testing Automation Server – ? At this moment I have no idea if this is a 3rd party app that we are referring to or a tool inside SilverBridge Setup XPAY Business Server Initial Setup Install and configure –.net4 Framework – SDT Crystal Reports Set Workstation prerequisites setup Create c:\SDTExergy Copy Loader.exe and Loader.Config from the XLifeUpdate folder on the transaction server to c:\SDTExergy folder Run Loader to synchronise, verify 5.2Configuration Workstation ? 5.3Development Workstation Configure Windows Component Services for E2G (MSDTC) Workstation Setup E2G Deployment Server and backups – What – How often – Where – Restore Requirements – Environment Setup (What is the purpose of this?) Housekeeping Backup – LifeBO – Startup Web Service – Xlife Update Ensure all users logged off Copy the following from the Release CD’s COM+ Machine folder to transaction server –LifeBO – Both the bin folder and the web.config should be copied to the LifeBO on the Transaction Server –StartUpWS – All the files from the CD should be copied to the StartUpWS folder on the Transaction ServerUpdate timestamps – XlifeUpdate – Copy all files EXCEPT the.config files from this folder to the XLifeUpdate folder on the Transaction Server – Update the.config files Xlife.config SDT.XStartUp.config – Update the timestamps by running the ‘Startup Config Update.exe’ from the XLifeUpdate folder Database Structure Upgrade Run scripts in CD Scripts Folder – 01_Structure scripts – 02_All – 03_Client specific Code Updates with new releases SQL Server Installation Database Server Prerequisites Database Server MSDTC configuration Database Server Web Quote Business Server Web Quote SQL Server setup and configuration QIS Business Server Integration Server ITP Server MIS Server Optional Component Installation

5 Deployment Production Server Prerequisites General Web Services StartUpWS Web Service XlifeUpdate Web Service LifeBO Web Service Apply Folder Settings and Permissions – Configuration of the COM+ Machine folder Configure E2G to run distributed – Configuration of the Loader.config file – Configuration of the SDT.XStartupUI.config file – Configuration of the XLife.config file – Using the ‘Startup Config Update.exe’ Setup XPAY Business Server Initial Setup Install and configure –.net4 Framework – SDT Crystal Reports Set Workstation prerequisites setup Create c:\SDTExergy Copy Loader.exe and Loader.Config from the XLifeUpdate folder on the transaction server to c:\SDTExergy folder Run Loader to synchronise, verify Configure Windows Component Services for E2G (MSDTC) Workstation Setup E2G Deployment Server and backups – What – How often – Where – Restore Requirements – Environment Setup (What is the purpose of this?) Housekeeping Backup – LifeBO – Startup Web Service – Xlife Update Ensure all users logged off Copy the following from the Release CD’s COM+ Machine folder to transaction server –LifeBO – Both the bin folder and the web.config should be copied to the LifeBO on the Transaction Server –StartUpWS – All the files from the CD should be copied to the StartUpWS folder on the Transaction ServerUpdate timestamps – XlifeUpdate – Copy all files EXCEPT the.config files from this folder to the XLifeUpdate folder on the Transaction Server – Update the.config files Xlife.config SDT.XStartUp.config – Update the timestamps by running the ‘Startup Config Update.exe’ from the XLifeUpdate folder Database Structure Upgrade Run scripts in CD Scripts Folder – 01_Structure scripts – 02_All – 03_Client specific Code Updates with new releases SQL Server Installation Database Server Prerequisites Database Server MSDTC configuration Database Server Web Quote Business Server Web Quote SQL Server setup and configuration QIS Business Server Integration Server ITP Server MIS Server Task Manager? Optional Component Installation

6 dsfsdf Development Baseline Major Release Baseline V16 Major Release Baseline V17 Sprint Baseline S69 Sprint Baseline S70 Client Branch Baseline V17.1ClientX Sprint Baseline S71 S69 S70 S71 Sprint Baseline S73 Major Release Baseline V18 CR / defect ClientX S…. to S68S72 Sprint Baseline S72.1 Client Branch Baseline V17.2ClientX EnvironmentClient AClient BClient X DevelopmentS71S72Upgrade to S73 Includes all sprints TestS70V17S72Upgrade to S72.1 Includes all CR / defect ClientX ProductionV17V16V17.1ClientXUpgrade to V71.2ClientX Excludes sprint 71, 71, 73 S73 Sprint Baseline S72 S74 Sprint Baseline S68 Sprint Baseline S73 Daily Development Baselines

7 TFS (Source Code Manager view) Development Daily Labels Sprint Labels Client Branch Labels Development Version Labels A label is created at the highest level and creates a snapshot of the entire environment as at a point in time and represents a baseline version A generic build is done by PCM ( how often) and creates the following: Bin folder Process BO Client process BO (empty) Final builder scheduled daily for dev and automated copy to file server A Client specific build is done by Deployment ( how often) and creates the following Client Specific Process BO How does it get to the file server and is it named according to the label in TFS? Client specific release CD’s are created on request and contain the Bin folder, process BO from the PCM build and the Client Specific Process BO from the Deployment build Where is the integration code included? shaun How is the version structure populated? Both PCM and Deployment use Final Builder to do the builds? Is it possible to compare builds where the client has their own SCMT? (at object level, file size / compile date as a possible means detecting glaring mismatches) A development baseline build is done daily PCM developers check code out from the applicable baseline and check it back into the most recent baseline????? Say a few days elapses before they are finished? The above is applicable to core and custom development Integration What else? Where do the PIC’s configuration, methods live (Client Process BO)? Where do the DB structure and stored procedures live???????? Where so the XML layouts live (Process BO)?


Download ppt "E2G Web Services E2G Scripts and Methods E2G Domain Logic E2G Domain Logic Client Custom Scripts and Methods Client Custom Scripts and Methods E2G Rules."

Similar presentations


Ads by Google