DOCSLIB.ORG

TCF IPMS Technical Specification Document

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Technical Specification for Industry Portability Management System Telecommunications Carriers' Forum Prepared by: Ken Julian & Allister Georgeson Application Services Global Delivery Jade Software Corporation 5 Sir Gil Simpson Drive, Burnside Christchurch 8053 Ph: +64 3 365 2500 Date Prepared: 24 Oct 2017 Technical Specification Project ID No.: NZ1-00232 Document Information Project Name: Industry Portability Management System Project Manager: Peter Smith (Jade) Document Version No: 4.19 Document Version Date: 21 February 2020 Prepared By: Edmond Tso (Jade) Preparation Date: 21 February 2020 Reviewed By: Denise Spiers (Jade) Review Date: Distribution Lists From Date Phone Application Services Global Delivery 29 August 2012 03 962 5700 To Action* Due Date Phone/Fax Rob Clarke – TCF PSWP Review * Action Types: Approve, Review, Inform, File, Action Required, Attend Meeting, Other (please specify) Version History Ver. No. Ver. Date Revised By Description Filename 0.1 26 Nov 2004 Rex Neville, Tony Verdellen Initial version for discussion at TCF IPMS Technical Technical Specification workshop Specification 0_1.doc 2/12/04 0.2 15 Dec 2004 Rex Neville, Tony Verdellen Updated version after discussion at TCF IPMS Technical Technical Specification workshop Specification 0_2.doc 2/12/04 0.3 11 Jan 2005 Rex Neville, Tony Verdellen Draft version including Web browser TCF IPMS Technical screens Specification 0_3.doc 1.0 01 Feb 2005 Rex Neville, Tony Verdellen First full version of specification TCF IPMS Technical Specification 1_0.doc 1.5 11 Mar 2005 Rex Neville, Tony Verdellen, Interim release – no HP internal TCF IPMS Technical Ralph Edinger quality review Specification 1_5.doc 2.0 15 Mar 2005 Rex Neville, Tony Verdellen, Second full version of specification TCF IPMS Technical Ralph Edinger Specification 2_0.doc 3.0 04 Apr 2005 Rex Neville, Tony Verdellen, Third full version of specification TCF IPMS Technical Ralph Edinger Specification 3_0.doc 4.0 07 Dec 2005 Rex Neville Updated for Change Request TCF IPMS Technical CR0003 - multiple Gaining Carriers Specification 4_0.doc and/or Losing Carriers per Port. 4.1 17 Feb 2006 Rex Neville Corrections after review of v4.0. TCF IPMS Technical Includes clarifications not related to Sepecification 4_1.doc CR0003 4.2 15 May 2006 Alan Monnox Updated to reflect changes in API TCF IPMS Technical WSDL. Specification 4_2.doc 4.2.1 12 Jun 2006 Alan Monnox Tech. Spec unchanged, document- NA wrapper version of WSDL released. 4.2.2 22 Jun 2006 Alan Monnox Version 4.2 accepted with wording TCF IPMS Technical change from TCF Specification 4_2.doc 4.3 16 Jul 2006 Tony Verdellen Changes for PCR004, PCR005, TCF IPMS Technical PCR009. Also correct minor Specification 4_3.doc specification errors identified during software development 4.3.1 28 Jul 2006 Alan Monnox Guidelines for API usage. Minor TCF IPMS Technical specification corrections. Specification 4_3.1.doc Page 2 of 237 Template (Version 1/25-Feb-2003) TCF IPMS Technical Specification 4_20 (002) Last changed: 21 February 2020 at 08:53 Technical Specification Project ID No.: NZ1-00232 Ver. No. Ver. Date Revised By Description Filename 4.3.2 21 Aug 2006 Rex Neville Minor specification corrections. TCF IPMS Technical Specification 4_3_2.doc 4.3.3 27 Sep 2006 Rex Neville Remove “urn:tcf:” from web service TCF IPMS Technical names. Minor specification Specification 4_3_3.doc corrections. 4.3.4 20 Oct 2006 Rex Neville Very small changes TCF IPMS Technical Specification 4_3_4.doc 4.4 29 Jan 2007 Aimee Hills, Rex Neville Changes for PCRs 11 and 12. TCF IPMS Technical Includes new web service API for Specification 4_4.doc downloading reports. Corrections for defects 678 882, 1763, 1774 4.5 24 May 2007 Mark Golebniak, Changes for PCRs 13, 15 and 17. TCF IPMS Technical Nick Foote, Also additional minor specification Specification 4_5.doc Rex Neville clarifications 4.6 20 July 2007 Mark Golebniak Changes for PCR 14 and 20 TCF IPMS Technical Specification 4_6.doc 4.7 21 Nov 2007 Andrew Doney Changes for PCR 26 TCF IPMS Technical Specification 4_7.doc 4.8 20 Feb 2008 Rex Neville PCR 31: Add Audit Details extract TCF IPMS Technical Specification 4_8.doc 4.9 23 Oct 2008 Andrew Doney Changes for PCR 36B TCF IPMS Technical Specification 4_9.doc 4.10 19 May 2009 Andrew Doney Changes for PCR 30 TCF IPMS Technical Specification 4_10.doc 4.11 13 Jan 2010 Ken Julian Changes for PCR 42 TCF IPMS Technical Specification 4_11.doc 4.12 20 Apr 2010 Ken Julian Changes for PCR35 & 43 TCF IPMS Technical Specification 4_12.doc 4.13 1 Sept 2011 Ken Julian Changes for PCR49 TCF IPMS Technical Specification 4_13.doc 4.14 29 Aug 2012 Ken Julian / Allister Changes for PCR50 TCF IPMS Technical Georgeson Specification 4_14.doc Ver. No. Ver. Date Revised By Description Release version 4.15 28 Feb 2017 Edmond Tso (Jade) IPMS-318 2.9.219 Adding validation rule to 4.6.11 ( Gaining carrier id is required ) 4.16 15 Mar 2017 Edmond Tso (Jade) IPMS-263 3.0.1 Adding validation rules to 4.6.11 and 4.6.25 IPMS-293 Page 52: An error was added to General Errors for the OVERRIDE_UNAUTHORISED Page 56: An error was added to the requestPort section for the OVERRIDE_UNAUTHORISED Page 76: Errors were added to the requestApprovedPortChange section for the OVERRIDE_UNAUTHORISED and RFS_NOTICE_PERIOD Page 3 of 237 Template (Version 1/25-Feb-2003) TCF IPMS Technical Specification 4_20 (002) Last changed: 21 February 2020 at 08:53 Technical Specification Project ID No.: NZ1-00232 Ver. No. Ver. Date Revised By Description Release version Page 102: New errors were added to the Application Security section for LSP Override Allowed and Fast Port Allowed Page 182 and 183: New images were added for the updated User Profiles page. Page 219: New error was added to the API Errors section for OVERRIDE_UNAUTHORISED. 4.17 07 Sep 2017 Anton Mather (Jade) IPMS-261 3.1.1 4.9. Emergency Return Request Access noted as disabled. 4.6.30: Emergency Return Request API call noted as disabled. 4.17 24 Oct 2017 Mo Yakubu (Jade) IPMS-192 Upgrade from Axis to 3.1.1 Jax-WS 3.5.26. Added a new entry to the system parameter table for rfsToDateDefault. Added another new entry to the system parameter table for enableQBNRChecking. 3.5.3. Added “Active” column to Company table, its purpose and impact. 3.5.4. Added “Active” column to ServiceProvider table, its purpose and impact. 4.6.1. Added report to the list of available web services. 4.6.11. Updated requestPort API call to indicate indicate that it should return an error if a disabled LSP is used for port request. 4.6.2. Updated the service versioninig section with the details of the newly added Apache CXF Jax-WS package. 4.6.12. Added additional parameters to the getRequestedPorts. 4.6.17. Added additional parameters to the getApprovedPorts api call. Page 4 of 237 Template (Version 1/25-Feb-2003) TCF IPMS Technical Specification 4_20 (002) Last changed: 21 February 2020 at 08:53 Technical Specification Project ID No.: NZ1-00232 Ver. No. Ver. Date Revised By Description Release version 4.6.23. Added additional parameters to the getNetworkUpdates api call. 4.6.26. Added additional parameters to the getApprovedPortChangeRequest api call. 4.6.34. Added a new API call for sOMStatusEnquiry. 4.9. Added a new entry to the access table for SOM Status Enquiry. 6.3.1. Updated the online login help page section to describe change to the list of companies. 6.4.1. Updated the GSP PortRequest page section to describe the change to the list of service providers. 6.6.6 Updated the User Maintenance section of the help documentation. 9. In Appendix A, a new entry was added to the IPMS API Errors table for error code SOM_TYPE_INVALID. 4.17 03 Nov 2017 Edmond Tso (Jade) IPMS-428 3.1.1 4.6.11 Added a new rule to the requestPort, some fields in the requestPort will be trimmed if they are over-length in the Jax-WS implementation. Add handset referenece validations , padding and trimming logic to the API call 4.6.13 Added the trimming rule for over- length fields, which is only applicable to the Jax-WS version. 4.6.25 Add handset referenece validations , padding and trimming logic to the API call 4.17 26 Dec 2017 Mo Yakubu (Jade) 4.6.36 3.1.1 Page 5 of 237 Template (Version 1/25-Feb-2003) TCF IPMS Technical Specification 4_20 (002) Last changed: 21 February 2020 at 08:53 Technical Specification Project ID No.: NZ1-00232 Ver. No. Ver. Date Revised By Description Release version Added emailAddress field format validation error. 4.17 16 Jan 2018 Edmond Tso (Jade) 7.3.16 3.1.1 Added extra fields for SLA network update report. 4.18 28 May 2018 Edmond Tso (Jade) 3.5.26 3.1.7 Add extra system parameter 2.2 Physical Design Specifications updates 4.18 6 Jun 2018 Edmond Tso (Jade) 4.6.14 3.1.7 Change description on the validation rules for field ‘gspRFSDateTimeStart’ 3.5.30 Add section 3.5.30 for new audit table. 4.19 20 Aug 2018 Callum Gubb (Jade) 3.5.5 3.1.8 Added “ACTIVE” column to the Carrier table and described its purpose. Retrospectively added an entry for the addition of the “LEFTMOSTSTANDARDSIM” column. 4.19 28 Aug 2018 Callum Gubb (Jade) 9 3.1.8 Added new “NUMBER_RANGE_PORTING” error into the table along with its description. 4.6.40 Updated error table to include the condition for the new NUMBER_RANGE_PORTING error 4.20 16 Jan 2019 Callum Gubb (Jade) 9 3.1.17 Added new “NUMBER_LENGTH_INVALID” error into the table along with its description.
Recommended publications
  • Laravel Create Schema from Database

    Laravel Create Schema from Database

    Laravel Create Schema From Database Littery and heteromorphic Rudolf diabolise his Auberon horse-collar crash buzzingly. Andrew stubbed lispingly as rubbery Erek sneezed her cognomens disforest doubtless. When Mathias quarrels his xerography enervating not frontward enough, is Rab Pickwickian? We unleash practically unlimited flexibility All generators now generate files for Laravel 5 Laravel 42 is. What is inserted into web application using administrator privileges to import wizard allows laravel from database schema from our case. Laravel create dynamic database. How this change tables structures with migration without losing. Tinyint equivalent column types are continuously updated during scrolling before, see an external tools that will insert some fake data in. In reality, Laravel can be used with any kind several database engines because check the underlying Eloquent ORM. Indicate that teaches us visualize at what does not include them you can mark users with caution when your production database, tables in order of. How grepper helps you from creating foreign key constraints on in development. This button an automatic process. Laravel Migration Generator helps you to generate laravel migration file from your. Unclaimed databases will have a length of course equally good. Before it lets us, so in isolation by hand over competing brands, saw this way is accessible, using this happens, consist of content from database schema state before actual smart media initiative and. In your tables as create laravel schema from database will. We can plenty of migrations as a version control system into database schema, which allows us to go track of changes made in regular database schema.
  • 3.2 Administrator Guides

    3.2 Administrator Guides

    Elgg Documentation Release master Various Jan 23, 2020 Contents 1 Features 3 2 Examples 5 3 Continue Reading 7 i ii Elgg Documentation, Release master Elgg( pronunciation) is an open source rapid development framework for socially aware web applications. It is a great fit for building any app where users log in and share information. Contents 1 Elgg Documentation, Release master 2 Contents CHAPTER 1 Features • Well-documented core API that allows developers to kick start their new project with a simple learning curve • Composer is the package manager of choice that greatly simplifes installation and maintenance of Elgg core and plugins • Flexible system of hooks and events that allows plugins to extend and modify most aspects of application’s functionality and behavior • Extendable system of views that allows plugins to collaborate on application’s presentation layer and built out complex custom themes • Cacheable system of static assets that allows themes and plugins to serve images, stylesheets, fonts and scripts bypassing the engine • User authentication is powered by pluggable auth modules, which allow applications to implement custom authentication protocols • Security is ensured by built-in anti CSRF validation, strict XSS filters, HMAC signatures, latest cryptographic approaches to password hashing • Client-side API powered by asynchronous JavaScript modules via RequireJS and a build-in Ajax service for easy communication with the server • Flexible entity system that allows applications to prototype new types of content and user interactions
  • Elgg Documentation Release Master

    Elgg Documentation Release Master

    Elgg Documentation Release master Various Sep 24, 2021 Contents 1 Features 3 2 Examples 5 3 Continue Reading 7 i ii Elgg Documentation, Release master Elgg( pronunciation) is an open source rapid development framework for socially aware web applications. It is a great fit for building any app where users log in and share information. Contents 1 Elgg Documentation, Release master 2 Contents CHAPTER 1 Features • Well-documented core API that allows developers to kick start their new project with a simple learning curve • Composer is the package manager of choice that greatly simplifes installation and maintenance of Elgg core and plugins • Flexible system of hooks and events that allows plugins to extend and modify most aspects of application’s functionality and behavior • Extendable system of views that allows plugins to collaborate on application’s presentation layer and built out complex custom themes • Cacheable system of static assets that allows themes and plugins to serve images, stylesheets, fonts and scripts bypassing the engine • User authentication is powered by pluggable auth modules, which allow applications to implement custom authentication protocols • Security is ensured by built-in anti CSRF validation, strict XSS filters, HMAC signatures, latest cryptographic approaches to password hashing • Client-side API powered by asynchronous JavaScript modules via RequireJS and a build-in Ajax service for easy communication with the server • Flexible entity system that allows applications to prototype new types of content and user interactions
  • Easy Laravel 5 a Hands on Introduction Using a Real-World Project

    Easy Laravel 5 a Hands on Introduction Using a Real-World Project

    Easy Laravel 5 A Hands On Introduction Using a Real-World Project W. Jason Gilmore This book is for sale at http://leanpub.com/easylaravel This version was published on 2015-08-11 This is a Leanpub book. Leanpub empowers authors and publishers with the Lean Publishing process. Lean Publishing is the act of publishing an in-progress ebook using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do. ©2014 - 2015 W. Jason Gilmore Also By W. Jason Gilmore Easy Active Record for Rails Developers Easy E-Commerce Using Laravel and Stripe Easy React Dedicated to The Champ, The Princess, and Little Winnie. Love, Daddy Contents Introduction ............................................ 1 What’s New in Laravel 5? ................................... 2 About this Book ......................................... 2 Introducing the TODOParrot Project .............................. 5 About the Author ........................................ 5 Errata and Suggestions ..................................... 6 Chapter 1. Introducing Laravel ................................. 7 Installing Laravel ........................................ 7 Creating the TODOParrot Application ............................. 14 Configuring Your Laravel Application ............................. 19 Useful Development and Debugging Tools .......................... 22 Testing Your Laravel Application with PHPUnit ....................... 30 Conclusion ............................................ 33 Chapter 2. Managing
  • Micro Focus Fortify Software Security Center User Guide

    Micro Focus Fortify Software Security Center User Guide

    Micro Focus Fortify Software Security Center Software Version: 19.2.0 User Guide Document Release Date: December 2019 Software Release Date: November 2019 User Guide Legal Notices Micro Focus The Lawn 22-30 Old Bath Road Newbury, Berkshire RG14 1QN UK https://www.microfocus.com Warranty The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Restricted Rights Legend Confidential computer software. Except as specifically indicated otherwise, a valid license from Micro Focus is required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Copyright Notice © Copyright 2008 - 2019 Micro Focus or one of its affiliates Trademark Notices Adobe™ is a trademark of Adobe Systems Incorporated. Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation. UNIX® is a registered trademark of The Open Group. Documentation Updates The title page of this document contains the following identifying information: l Software Version number l Document Release Date, which changes each time the document is updated l Software Release Date, which indicates the release date of this version of the software This document was produced on December 12, 2019.
  • KANA Response Live Server Installation Guide

    KANA Response Live Server Installation Guide

    This is the most recent version of this document provided by KANA Software, Inc. to Genesys, for the version of the KANA software products licensed for use with the Genesys Multimedia products. Click here to access this document. KANA Response Live Server Installation Guide KANA Response Live Version 10R3 July 2008 KANA Response Live Server Installation Guide All contents of this documentation are the property of KANA Software, Inc. (“KANA”) (and if relevant its third party licensors) and protected by United States and international copyright laws. All Rights Reserved. © 2008 KANA Software, Inc. Terms of Use: This software and documentation are provided solely pursuant to the terms of a license agreement between the user and KANA (the “Agreement”) and any use in violation of, or not pursuant to any such Agreement shall be deemed copyright infringement and a violation of KANA's rights in the software and documentation and the user consents to KANA's obtaining of injunctive relief precluding any further such use. KANA assumes no responsibility for any damage that may occur either directly or indirectly, or any consequential damages that may result from the use of this documentation or any KANA software product except as expressly provided in the Agreement, any use hereunder is on an as-is basis, without warranty of any kind, including without limitation the warranties of merchantability, fitness for a particular purpose, and non-infringement. Use, duplication, or disclosure by licensee of any materials provided by KANA is subject to restrictions as set forth in the Agreement. Information contained in this document is subject to change without notice and does not represent a commitment on the part of KANA.

  • Andrew “"1 333328125 3%: ‘$315 $6615 6E 21' 383/335 Peters’ Sammamlsh’- WA (Us) 8,438,532, , B2 * 5/2013 Foxee Et Ea1

    US008600925B2 (12) Ulllted States Patent (10) Patent N0.: US 8,600,925 B2 Vickers et a]. (45) Date of Patent: Dec. 3, 2013 (54) OBJECT-RELATIONAL MAPPED DATABASE 7,089,583 B2 8/2006 Mehra etal. INITIALIZATION 7,277,435 B2 * 10/2007 Keller ......................... .. 370/390 7,421,436 B2 9/2008 Salo et a1. (75) Inventors: Arthur John Cerdlc. Vlckers,. Redmond, 7,676,4937,657,505 B2 * 3/20102/2010 PiZJZOHe'lsber et ‘i1’ et al. .... .. 707/999.002 WA (US); Dlego Bernardo Vega, 7,734,659 B2 * 6/2010 Lori ............................ .. 707/802 Sammamish, WA (US); Rowan Miller, 7,788,275 B2 * 8/2010 Warren et a1. .. 707/763 Kirkland’ WA (Us); Andrew “"1 333328125 3%: ‘$315 $6615 6E 21' 383/335 Peters’ Sammamlsh’- WA (Us) 8,438,532, , B2 * 5/2013 FOXee et ea1. a ..................... .. 717/101 2009/0024652 A1 1/2009 Th t l. (73) Assignee: Microsoft Corporation, Redmond, WA 2010/0100427 A1 4/2010 M32331; :1‘ US ( ) OTHER PUBLICATIONS ( * ) Notice: Subjeqw any (gsglaimeé’. the germdof?gig “Productivity Improvements for the Entity Framework”, Retrieved Patent 15 exten e Or a Juste un er from <<http://blogs.msdn.com/b/efdesign/archive/2010/06/2 l/pro U'S'C' 15403) by 201 days‘ ductivity-improvements-for-the-entity-framework. (21) Appl NO _ 13/179 598 aspx?PageIndex:2>>, Jun. 21, 2010, 7 Pages. .. , (Continued) (22) Filed: Jul. 11, 2011 P rzmar' y Exammer ' * M'1c h ae l B H o l mes (65) Prior Publication Data (74) Attorney, Agent, or Firm * Ogilvie LaW Firm US 2012/0331013 A1 D .27 2012 e0 ’ (57) ABSTRACT Related US, Application Data A balance is provided betWeen automation of repetitive data _ _ _ _ _ base creation and con?guration efforts, on the one hand, and (63) E10 gtmuejnongl'gg? 10f apphcanon NO‘ 13/166’825’ ?exibility to depart from prior con?gurations, on the other e on 1111' ’ ' hand, to assist developers With aspects of database initializa (51) IntCl t1on.'AnPPl' a 1cat1on ' d oma1n1nc"ldd u es ata context mstances,' Got'sF 7/00 (2006 01) database connections, object models mapped by an object G06N 5/02 (200601) relational mapper, and database initialiZers.
  • Fortify 360 Server Installation and Configuration Guide

    Fortify 360 Server Installation and Configuration Guide

    Fortify® 360 Server Installation and Configuration Guide Fortify 360, Version 2.6 May 2010 Copyright© 2010 Fortify® Software, Inc.June 14, 2010 12:21 pm All Rights Reserved. Printed in the United States of America. Fortify Software, Inc. 2215 Bridgepointe Pkwy Suite 400 San Mateo, CA 94404 Fortify Software, Inc. (“Fortify”) and its licensors retain all ownership rights to this document (the “Document”). Use of the Document is governed by applicable copyright law. Fortify may revise this Document from time to time without notice. THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND. IN NO EVENT SHALL FORTIFY BE LIABLE FOR INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY KIND ARISING FROM ANY ERROR IN THIS DOCUMENT, INCLUDING WITHOUT LIMITATION ANY LOSS OR INTERRUPTION OF BUSINESS, PROFITS, USE OR DATA. FORTIFY RESERVES THE RIGHT TO MODIFY OR REMOVE ANY OF THE FEATURES OR COMPONENTS DESCRIBED IN THIS DOCUMENT FROM THE FINAL PRODUCT, WITHOUT NOTICE. Fortify is a registered trademark of Fortify Software, Inc. Brand and product names in this Document are trademarks of their respective owners. Part number: 1‐151‐2010‐05‐26‐1 Contents Contacting Fortify Software. viii Technical Support . viii Corporate Headquarters. viii Web Site . viii About the Fortify 360 Documentation Set . viii Overview of Fortify 360 Server Installation. 1 How to Use this Guide . 1 The Central Role of Fortify 360 Server . 1 Overview of the Fortify 360 Server Installation Environment. 2 Preparing to Install Fortify 360 Server . 3 Preparing the Application Server . 3 Preparing the Fortify 360 Server Database. 4 Preparing the Optional LDAP Server .
  • A Comparative Look at Entity Framework Code First Casey Griffin La Salle University, Griffinc4@Student.Lasalle.Edu

    A Comparative Look at Entity Framework Code First Casey Griffin La Salle University, [email protected]

    La Salle University La Salle University Digital Commons Mathematics and Computer Science, Department Mathematics and Computer Science Capstones of Spring 5-17-2013 A Comparative Look at Entity Framework Code First Casey Griffin La Salle University, [email protected] Follow this and additional works at: http://digitalcommons.lasalle.edu/mathcompcapstones Part of the Databases and Information Systems Commons Recommended Citation Griffin,as C ey, "A Comparative Look at Entity Framework Code First" (2013). Mathematics and Computer Science Capstones. 11. http://digitalcommons.lasalle.edu/mathcompcapstones/11 This Thesis is brought to you for free and open access by the Mathematics and Computer Science, Department of at La Salle University Digital Commons. It has been accepted for inclusion in Mathematics and Computer Science Capstones by an authorized administrator of La Salle University Digital Commons. For more information, please contact [email protected]. A Comparative Look at Entity Framework Code First Submitted to the Department of Computer Information Science By: Casey Griffin Date: May 1, 2013 La Salle University MS Computer Information Science/MS Information Technology Leadership APPROVALS Agree to Advise: Stephen A. Longo, Ph.D. (Project Advisor) Date Submitted: May 1st, 2013 Approved by: Stephen A. Longo, Ph.D. (MS in CS Committee) Date Approved: May 3rd, 2013 1 La Salle University MS Computer Information Science/MS Information Technology Leadership Contents 1. Abstract ......................................................................................................................
  • Migrating Data-Centric Applications to Windows Azure

    Migrating Data-Centric Applications to Windows Azure

    Migrating Data-Centric Applications to Windows Azure Kun Cheng, Selcin Turkarslan, Norberto Garcia, Steve Howard, Shaun Tinline-Jones, Sreedhar Pelluru, Silvano Coriani, Jaime Alva Bravo Contributors: James Podgorski, Rama Ramani Reviewers: Paolo Salvatori, Stuart Ozer, Drew McDaniel, Jason Chen, Ganesh Srinivasan, Lindsey Allen, Evgeny Krivosheev, Valery Mizonov, Avilay Parekh, Christian Martinez, Shawn Hernan, Mark Simms, Adrian Bethune, Bill Gibson, Adam Mahood Summary: The guide, Migrating Data-Centric Applications to Windows Azure, provides experienced developers and information technology (IT) professionals with detailed guidance on how to migrate their data-centric applications to Windows Azure Cloud Services, while also providing an introduction on how to migrate those same applications to Windows Azure Virtual Machines. By using this guide, you will have the planning process, migration considerations, and prescriptive how to’s needed for a positive migration experience. Capturing the best practices from the real-world engagements of CAT and the technical expertise of the SQL Database Content team, Migrating Data-Centric Applications to Windows Azure can help you simplify the migration process, provide guidance on the most appropriate migration tools, and drive a successful implementation of your migration plan. Category: Guide Applies to: Windows Azure Source: MSDN Library (link to source content) E-book publication date: June 2012 Copyright © 2012 by Microsoft Corporation All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. Microsoft and the trademarks listed at http://www.microsoft.com/about/legal/en/us/IntellectualProperty/Trademarks/EN-US.aspx are trademarks of the Microsoft group of companies.