Deploying Dynamics Applications Thomas Hansen Director app Solutions

Deploying Dynamics Applications Thomas Hansen – Director, app. Solutions a|s thomas@app-solutions. com http: //www. app-solutions. com

app. Solutions a|s ? o Many years PROGRESS technology experience n o Dynamics Framework n n o Tech Support, Consulting, Training, Design & Development Active in initial and existing development of POSSE & Progress Dynamics™ Experience in developing and deploying Dynamics based applications Roundtable TSMS™ n Evaluation, implementation, training, customization, support & sales © 2003 http: //www. app-solutions. com

app. Solutions a|s. . . o Computer Associates Premium Partner n o E-olas Distributor n o All. Fusion™ Modelling Suite (ERwin) sales and consulting Progress based BI & Data Analysis tool . . . © 2003 http: //www. app-solutions. com

Agenda o o o Deployment pre-requisites Preparing for deployment Deployment using Dynamics tools Deployment with Roundtable Questions ? © 2003 http: //www. app-solutions. com

o o o Deployment pre-requisites Preparing for deployment Deployment Scenarios Deployment using Dynamics tools Deployment with Roundtable Questions ? © 2003 http: //www. app-solutions. com

Deployment Considerations o Dynamics Site numbers n n n o Must be unique for all ICFDB databases Use site numbers from Site Number Allocator on POSSE – http: //www. possenet. org Central ”master” database to store all data and make deployments from Data versioning n n Must be enabled for all tables to be deployed Set in Dynamics Entity Control © 2003 http: //www. app-solutions. com

Deployment Considerations. . . o Naming Conventions n n o Source code names Directory names Product Module and Directory Structure n Use to partition application into product and object types / target partition © 2003 http: //www. app-solutions. com

o o o Deployment pre-requisites Preparing for deployment Deployment Scenarios Deployment using Dynamics tools Deployment with Roundtable Questions ? © 2003 http: //www. app-solutions. com

Preparing for deployment o Deployment Configurations n Servers o o n Clients o o o App. Server & Web. Speed Web Server Web. Client-Server Data. Sets n n n Pre-defined Data. Sets Custom Data. Sets Remember Data. Set definitions ! © 2003 http: //www. app-solutions. com

Preparing for deployment. . . o Source Code & Static Files n n o Framework Files & Application Files Static Objects Dynamic Objects Configuration Files Deployment Source & Targets n n Multiple development repositories End users © 2003 http: //www. app-solutions. com

o o o Deployment pre-requisites Preparing for deployment Deployment Scenarios Deployment using Dynamics tools Deployment with Roundtable Questions ? © 2003 http: //www. app-solutions. com

Deployment to a New Site Master Application Repository . df . ado’s Master Application Database app seqvals static objects New Site # © 2002, Progress Software Corporation © 2003 http: //www. app-solutions. com

Deployment to a New Site … . df . ado’s app seqvals static objects New Site # © 2002, Progress Software Corporation © 2003 http: //www. app-solutions. com New Application Repository New Application Database

Revision/Release to Existing Site Master Application Repository delta. df . ado’s Master Application Database static objects Repositories must have existing unique site numbers © 2002, Progress Software Corporation © 2003 http: //www. app-solutions. com Receiving Application Repository Receiving Application Database

Merging Development Tracks n n n Requires Master Application Repository Independent developers’ repositories require unique site numbers Each repository may serve many developers o Such deployments require identifying related groups of changes based on functionality © 2003 http: //www. app-solutions. com

Merging Development Tracks Developer A static Repository objects Developer B Repository Developer C Repository © 2002, Progress Software Corporation © 2003 http: //www. app-solutions. com . ado’s Master Application Repository master static objects All repositories must have existing unique site numbers

Merging Development: Option 2 (POSSE technique) Developer A Repository Developer B Repository Developer C Repository © 2002, Progress Software Corporation © 2003 http: //www. app-solutions. com . ado’s static objects Master Application Repository master static objects All repositories must have existing unique site numbers

Merging Development: Option 1 Developer A static Repository objects Developer B Repository Developer C Repository © 2002, Progress Software Corporation © 2003 http: //www. app-solutions. com . ado’s Master Application Repository master static objects All repositories must have existing unique site numbers

o o o Deployment pre-requisites Preparing for deployment Deployment Scenarios Deployment using Dynamics tools Deployment with Roundtable Questions ? © 2003 http: //www. app-solutions. com

Deployment Tools n Dynamics Deployment Tools o o o Deployment Dataset Control Dataset Export Dataset Import Deployment Destinations Deploy Static Objects Redundant ADO Listing © 2003 http: //www. app-solutions. com

Demo © 2003 http: //www. app-solutions. com

o o o Deployment pre-requisites Preparing for deployment Deployment Scenarios Deployment using Dynamics tools Deployment with Roundtable Questions ? © 2003 http: //www. app-solutions. com

Deployment with Roundtable o o Automated version control (check-out) from Dynamics n Handled by triggers n Using RTB API and normal checks for concurrent check-outs etc. Version control of Data using XML n Automated creation and update of. ado (XML) files for Dynamic Objects n Enables version control and Configuration Management of any data as XML n XML integration allows for Export / Import between RTB and Dynamics repositories o n Useful for loading existing applications Deployment of Data (Data. Sets) handled as part of Configuration Management © 2003 http: //www. app-solutions. com

Deployment with Roundtable. . . o Dynamics extensions to the normal deployment process in Roundtable n n n Generates controlled and versioned deployment of static & dynamic objects Source Code Deployments Allows for Application Partioning – Post Deployment © 2003 http: //www. app-solutions. com

Deployment Configuration © 2003 http: //www. app-solutions. com

RTB Deployment Processing o o Use RTB supplied install programme _update. w Possibly in combination with Dynamics Configuration Utility (DCU) © 2003 http: //www. app-solutions. com

Deployment Partitioning o After compile of source deployment, build various partitions, . pl files and Web. Client package © 2003 http: //www. app-solutions. com

Demo © 2003 http: //www. app-solutions. com

© 2003 http: //www. app-solutions. com