Tag Archives: deployment

SharePoint Offers Enterprise Level Info Sharing Platform

SharePoint Offers Enterprise Level Info Sharing Platform

The rich platform of SharePoint helps in the construction of web applications that are ‘multi-tiered’. There are three characteristics that define this development platform- reliability which means its ability for consistent performance, extensibility which enables consolidation with other applications as well as systems and scalability which enables the proper handling of growing work amount. For web application development several frameworks, languages, tools as well as object models can be used. The person who is new to this platform may find it difficult to know what to implement and where. So a developer should first understand his choices and then select the options accordingly to meet his design and architectural goals.


The system of SharePoint Server is equipped with the following capabilities: -Communities- Collaborating through blogs, wikis, etc. -Sites- Websites both outside as well as inside the firewall. -Search- The technologies as well as products include search engines that can be customized according to your needs. -Content- Web content management, publishing along with enterprise content management systems. -Composite applications- Includes infrastructure, processes, user interface as well as data access. -Insights- Business intelligence.

Scalable architecture can be provided by the relevant technologies along with products making it absolutely perfect for several users like employees of a huge corporation. Flexible, scalable websites can be built by its virtue; they can be maintained with ease. When building applications you can customize several capabilities for specific vertical markets.

Role in Application development strategy

While considering the role, three basic strategies are there- enterprise portal, application and intranet along with application. Among these SharePoint viewed as application is the simplest approach. In this, deployment of SharePoint is as it is. Customizations are limited to either no-code customizations or configuring through web browser.

SharePoint may also be utilized as intranet platform as well as application. According to this model, the platform is used for building of intranet applications. This often includes remarkable customizations and partners can be included as well for initial deployment. After completing the deployment, in-house customizations can be limited to configuration through browser or no-code solutions with help of SharePoint Designer.

SharePoint can be adopted as an enterprise portal, acting as a core component of the application development strategy. This model will allow you to have an experienced as well as full-fledged software development team. You along with your development partner can also experience close relationship by virtue of this platform. Other considerations additionally associated with this approach are: -Maintaining the skills necessary within the development team. -Enforcement as well as development of coding standards specific to SharePoint for external development partners along with internal developers. -Robust approach needs to be established for ALM or Application Lifecycle Management like defining the standards, process as well as procedures for creation of SharePoint solutions. They can then be moved through production environments, UAT, integration as well as development. -In case of regional SharePoint farms engaged in global deployment, standards and efforts must be coordinated across diverse development teams.

Right applications for SharePoint

To use SharePoint for application development platform, you should try and determine when SharePoint can be used and when it cannot be used. Every problem can be solved by this platform but it may increase complexities in maintenance along with application development and cost as well. Things may become tricky in case of upgradation to SharePoint’s latest release due to heavy customizations. So some key considerations are: -Management of unstructured information is best suited by SharePoint. -There is no point in using this if things like content, search, insights, communities, composites or sites are not used. -It is best for creation of multiple examples of websites based on common templates.

Thus, in short this platform is not only great for enterprise level information sharing but for lots of features like file-sharing, web-publishing and collaborating, all under a single server. Business efficiency and productivity can be improved with the help of the easy to use and powerful infrastructure which boasts of capabilities for the development of websites, portals, content management systems, intranets and such other business intelligence implementations. You can hire developers from top SharePoint development company in India who can help you build mobile apps within allocated budgets and time schedules.

We provide SharePoint custom solutions development services. If you need to hire SharePoint developer from us, we would be glad to assist you at Mindfire Solutions.


The Failings of Single-Instance ERP

The Failings of Single-Instance ERP

Cost. For a large company, the cost of deploying Oracle or SAP enterprise-wide will run in the millions or tens of millions of dollars.The problem comes when the headquarters installation is finished and the first few major subsidiaries have been brought online.With the core complete, the economics become decreasingly justifiable as you move toward the edges of the organization. At each location there will be hardware and software to be purchased and deployed, an IT team to be dispatched, and a new span on that Golden Gate Bridge needs its own permanent paint crew. Another million dollars just to bring the Singapore subsidiary online? Somehow that cost/benefit doesn’t seem as compelling as it did in the earlier stages of the project.

Time. Single-instance ERP deployments take an enormous amount of time. Global rollouts taking years and years and straddling the tenure of multiple finance and IT personnel are the rule rather than the exception. Again, momentum can fall off significantly the further you get from headquarters or the largest subsidiaries. And each new subsidiary, division, or process added means that the core IT team will be spending a larger and larger portion of its time caring for and feeding the accounting software
systems already installed and have less and less capacity to apply to rolling out to new subsidiaries, divisions, or processes. Then the general manager of one of those far-flung subsidiaries says, “Yes, they’re going to roll it out here as well but I’ve seen the rollout calendar, and I’m scheduled to get it in 2019. I need something now.”

Risk. Cost and time add up to risk. These massive deployments often overshoot on time and cost and subsequently crumple under their own weight. Part of the company may end up live, but that may be where the deployment fizzles and proceeds no further. Because these deployments have been so disruptive, so risky, and simply so much harder than imagined at the outset, companies hesitate to deploy more broadly.

Agility. Worst of all for the single-tier strategy is that, during the years-long global deployment project, neither the world nor the business has stood still. New companies have been acquired or divested, new products and processes have been introduced, and new regulatory and business accounting software requirements have been enacted. Because these systems take so long and cost so much to deploy, they’ve been completely unable to keep pace with the changing environment. The unmanaged change results in patching systems and processes with a variety of point solutions, stand-alone ERP systems, manual processes, and, in general exactly the kind of chaos everyone was trying to avoid with this single-tier strategy in the first place. What does all that mean to the organization? Fundamentally, it’s a failure to achieve those gains that were the original vision of the strategy, namely global visibility, process efficiency, and standardization. The handoffs between those disparate systems also are challenging. Processing orders across subsidiaries, reconciling intercompany charges, and consolidating the books at month-end are complicated when there’s no standardization. Clumsy manual handoffs of information across systems are not only inefficient, but they create opportunities for the introduction of errors and erode confidence in the integrity of the process. Finally, executing change in this environment can be an enormous challenge. More complex changes, such as rolling out a new process because of a change in Generally Accepted Accounting Principles (GAAP), can consume huge amounts of time and resources that are far out of proportion to the real magnitude of the change.

This is the common reality finance faces today. Given the current situation, it makes sense to develop a new strategic approach that will move organizations toward the global standardization and transparency originally envisioned and promised by ERP much more quickly and effectively than the one-system strategy has done. That’s where two-tier ERP comes in.


Understanding Sharepoint 2013 Apps Deployment Models

Understanding Sharepoint 2013 Apps Deployment Models

SharePoint 2013 is one of the best iterations of Microsoft’s document management and collaboration platform. SharePoint is moving to the cloud as per the market trends, and this means that SharePoint is now opting for a software-as-a-service model. The approach is hailed by analysts as a future-oriented move from Microsoft and will work for the benefit of the clients.

SharePoint is supposed to be much more useful when it is completely customized and aligned to the operations within an organization and strategies within a business. SharePoint’s functionality is certainly useful, but to realize the full potential, one needs to have a custom SharePoint setup as their intranet solution. It is a problem if it is hosted since custom code runs in shared environments and if bad code is entered, it has the ability to bring down a server to its knees and affect the existing customers harshly.

SharePoint 2013 now allows customers to build own SP-based solutions without interfering with the hosted model. The new model is called the SharePoint App Model, which does not have server-side code.

There are three deployment models for SharePoint 2013 Apps which include SP hosted. Self-Hosted, Azure Web Application. A SharePoint-Hosted App is based on static files that reside directly in the SharePoint instance. When you add an application, SharePoint deploys files in the App to a new domain where the App lives. The users are redirected to a page in the App domain from which they have the ability to use the App. No server-side code is allowed absolutely in this model.

A Self-Hosted App on the other hand is an application where the app files exist on an external server outside of SharePoint. When the application is accessed, they are redirected to the external server page where the application resides. One can run server-side code through this model, but on an external server. One can’t run custom code on the SharePoint server. The external server does not need to be based on Windows because the redirections are made to a web page, which can run on any operating system and application servers.

The model also gives the user complete control of upgrades. One can deploy updates and have them applied immediately to the clients. When deploying under different models, users have to perform actions to upgrade since there is no access to the server to the hosted app.

An Automatically-Provisioned Azure App is different from other deployment models since it is designed to run only from Microsoft’s hosted SharePoint environment so its clients are mostly SharePoint online customers. The other two App model options can be seen in hosted SharePoint environment as well as a part of the corporate installation.

An Automatically-Provisioned Azure App is designed to be deployed to Azure and hence can run custom code. One can avail all capabilities and server-side code without having to shell out money!

As a Microsoft SharePoint Application development vendor, one needs to make the choice. If one opts for a SharePoint-Hosted App, server side code cannot be run, which also means that you do not have to shell money for the server to host your app.