Development Tools and Related Strategies for Public, Private, and Hybrid Environments There have been many improvements as well as options added to Visual Studio 2013 to address the new technology releases of SharePoint 2013 , Office 365 , SharePoint Online , and Microsoft Azure . EPC Group highly recommends that your organization’s developers have both on-premises and cloud development environment tools available so that they can become familiar with them, and also ensure that compatibility of a future architecture, as shown in the image below, is taken into consideration. Visual Studio 2013 and Related Tools and SDK Visual Studio 2013 is the enterprise development tool that should be used on almost any development initiative because the application life-cycle management as well as code repository integration and new SharePoint 2013 integration features make it the only tool available on the market with its capabilities
Understanding REST APIs in Office 365, SharePoint 2013 & Custom Development The REST APIs are very straightforward and easy to use and allow for a platform-agnostic development approach
APIs and Development Options for Data and Resources SharePoint 2013’s APIs allow apps, as well as other elements, to connect and integrate with SharePoint’s core features
" Keeping it straightforward is the name of the game here and when also talking in a "Custom Application or true AppDev situation for a Business Intelligence or Workflow related type efforts, this will help the "technical business analysts" who have to be able to work with the business and translate "business speak" into "technical speak" and an improved overall application development lifecycle and related end user testing or UAT prior to go live with any small bug fixes or updates
Just like other ‘traditional’ on-premise software applications there are now many options to develop advanced technology, yet make the user experience extremely easy and efficient
Hosting SharePoint's infrastructure for a specific workload or combination of workloads such as these: • Application platform for line-of-business (LOB) application • Business intelligence implementations • Collaboration, community, and/or project sites • Internet/intranet publishing portal • Personal sites • Enterprise search SharePoint private clouds have the following features: Scalable, flexible architectures Ability to host many “customers” or tenants Repeatable, predictable automated deployment and provisioning Upgrade, failover, and patching resiliency Note: Many of these items can also be achieved in a hybrid cloud environment . There are several factors that influence an organization’s decision regarding which architecture (that is, on-premises private cloud, public cloud, or hybrid cloud) they are going to design and implement for their short-term and long-term SharePoint roadmap needs, such as these: • The overall size of the organization and user base • Security issues • Legal and compliance issues • Any project or deployment time constraints • Complexity of customers’ current environment • Physical locations • Current identity infrastructure • Current IT infrastructure model and future IT roadmap • Network bandwidth issues • Software/hardware issues • Any vendor service level agreement (SLA) • High-availability/backup issues • Internal resource issues and related training • Support alignment • Service reporting • Standards adoption and management • Development alignment • Infrastructure alignment • Development platform management • Governance User issues Management and tools Development standards creation Information architecture and search Business requirements Infrastructure guidance When you are taking complex environments into consideration, there are also items such as these: • Multitenancy (Office 365 issues when a user goes outside of IT to create a new “environment”) • Multiple farms • Security (FBA, SAML claims, extranets) • Global clients with PHI, PII, Safe Harbor, intellectual property, EU pushback, or NSA concerns due to recent news It is key to also look at your current operations and how well your organization will be able to adapt to change
Some of these capabilities also exist in some very recent releases of Office 365 Enterprise but the time you will spend on the configuration and setup to accomplish the same results will be immensely lower in the ‘private cloud” side of the hybrid SharePoint development. One major concern of organization’s in past releases of SharePoint were how some “Test” or “Development” environments that were not properly implemented, not backed-up or under the organization’s disaster recovery (DR) strategy, or those that duplicated the effort of the organization’s central “SharePoint” deployment quickly became a “Production” like environment. In SharePoint 2010, 2007, or 2003 implementations there is a concern around the risk that these types of environments (i.e. Development environments that quickly became a SharePoint Production environment with a great deal of content) can bring when they are not following the company’s overall IT strategy, SharePoint roadmap and governance policies and causing additional effort, risk, and concern around document security
1 Comment - no search term matches found in comments.
Understanding Isolation Modes in SharePoint 2013 & Office 365 Hybrid Deployments In SharePoint 2013: Each “customer” = one site collection under managed path Similar to today Each Web Application = one app pool Similar to today Each Web Application = one URL Similar to today Exception Process for Host Header named site collections (vanity URL’s) Along Side or in an Office 365 Hybrid Deployment: BYO Servers Leverage existing architecture Hybrid Considerations (Seamless SharePoint 2013 On-Prem \ Office 365 Cloud Search Integration) Scaling Web Front-ends and Understanding When to Scale App Scale and Tipping Points EPC Group’s Nationally Recognized Practice Areas EPC Group leading SharePoint , Office 365 , Infrastructure Design and Business Intelligence Practice areas continue to lead the way in providing our clients with the most up-to-date and relevant information that is tailored to their individual business and functional needs
HBI/MBI/LBI) Automated site placement based on user input & verification Mission Critical Classification Governance Document IT manually creates site in “special” environment Automated site placement bin redundant data-center based on user input & verification Enforcement Scope – How to Enforce (EPC Group Example) Governance Provisioning Tools (EPC Group Example) Object in SharePoint 2013 and/or Office 365 Automatable Create Site Collections Create Sub Webs Create Hierarchy Available on Office 365 People | My Sites | Social ✓ ✓ ✓ ✓ Web Parts | Apps ✓ ✓ List Templates (STP and XML) ✓ ✓ Web Templates (WSP and XML) ✓ ✓ ✓ Site Quotas ✓ ✓ Web Event Receivers ✓ ✓ ✓ SPD Workflows and Actions ✓ ✓ ✓ * ✓ Feature Stapling ✓ ✓ ✓ ✓ * Workflows ✓ ✓ ✓ ✓ Site Definitions ✓ ✓ ✓ ✓ Timer Jobs ✓ ✓ ✓ ✓ Custom Site Provisioning Handlers ✓ ✓ ✓ ✓ Matching the Policy to the Office 365 and/or SharePoint 2013 Scope (EPC Group Example) Policy Type Scope Possible Options Security\ Identity Management Farm Web Application Provisioning workflows Timer Jobs Web application polices DNS/Infrastructure Reactive reporting Farm Web Application Sites/Webs Timer Jobs External Database Event Receivers Proactive Sites/Webs Custom Forms Event Receivers Feature Receivers Custom Field Controls Auditing Farm Web Application Timer Jobs External Database Changes Sites/Web Features Control Delegates Considerations in Complex Environments • Multi-tenancy ( Office 365 Issues when a user goes outside of I.T. to create a new “environment”) • Multiple farms • Hybrid on-premise and off-premise • Security (FBA, SAML claims, Extranets) • Global Clients with PHI, PII, Safe Harbor, Intellectual Property , EU Pushback, NSA Concerns in recent news Frequently Asked Questions of EPC Group • Terms of Service • Common user interface and navigation • Site directory and Office 365 and/or SharePoint 2013 ’s new Layout • Common header and footer content (standardize and creation of governed branding guide) • Structured provisioning with workflow • Site Mapping | Mapping the Owner to Content • BYOD \ "Bring Your Own Device" Strategies (Mobility) • Custom Branding | Responsive Design in Office 365 \ SharePoint 2013 • Site Backup and Restore (DR) and Archival EPC Group’s Nationally Recognized Practice Areas EPC Group leading SharePoint , Office 365 , Infrastructure Design and Business Intelligence Practice areas continue to lead the way in providing our clients with the most up-to-date and relevant information that is tailored to their individual business and functional needs
There is also a new and growing “App” culture that is causing organizations to take a good look at their underlying application and custom development processes, standards, and available environments that directly coincides with the moving pieces described above which can make for a perfect storm of major technology decisions that need to be made that will affect the company for at least the next 3 or 4 years
8403 Colesville Rd #1100Silver Spring, MD 20910USA
Phone: (301) 587-8202Toll free: (800) 477-2446Fax: (301) 587-2711Email: hello@aiim.org
JoinBenefitsLearn More
About UsTerms of Use