Tips for Effective Migration to SharePoint 2013

In the recent times, with Microsoft launching SharePoint 2013, a large number of businesses are considering migration to this new edition to enhance their business processes. In fact, this new version of SharePoint is anticipated to revolutionize the way in which companies are building links amongst their knowledge workers, business processes as well as business-related content worldwide. This platform includes novel features such as enhanced document management capabilities with respect to sharing and contributing content, enhanced social features along with a renewed search experience. SharePoint 2013 is speedily positioning itself as one of the much sought after technology for the introduction of crucial organizational initiatives in the areas of social collaboration, enterprise content management and web content management.

SharePoint developers

The advanced features of Sharepoint make it vital for organizations to take certain points into consideration prior to adopting this latest platform. Let us discuss some of the guidelines that should be followed in order to achieve effective migration to SharePoint 2013.

1. Take care of hardware requirements: In case of SharePoint 2013 servers, minimum of 8 GB RAM and four 64-bit cores is needed for small environments while medium environments require 16 GB RAM. For every server operating in SharePoint 2013, location within a single data center is essential.

2. Operating system requisites: The ideal operating system incorporates 64-bit edition, R2 SP1 Windows Server 2008. The 2012 Windows Server operating system can also be utilized. You must consider migration to 64-bit servers before any other upgrade or migration.

3. Decide upon the destination before starting off: Doing this gives you a clear-cut idea of where you are heading to and this allows you to go for proper channelization of the resources at hand. For example, if you are using SQL 2012, use Windows 2012 along with an Office Web Application Server.

4. Divide current customizations into categories: It is advisable to categorize the customizations into three categories. The first category constitutes items such as custom authentication provider that would stop the project. You need to have solutions for this, or else the migration would not be a success. The second category comprises items that would not put a halt to the project but are required to be completed. It is good to address them once the migration is completed. Items that need to be eliminated make up the third category.

5. Realize environmental alterations: When you are deciding to go for Windows 2012, the environmental change that takes place needs to be taken into consideration. The SMTP server role has been deprecated by Windows 2012 and depending on the information, decision needs to be taken as to whether to use a more intricate configuration or go for installation of the deprecated feature.

6. Get every migration step scripted: This task involves restructuring site hierarchy, mounting content databases.

7. Conduct dry runs: While performing dry runs, you must follow a sequential guide. Through the dry runs, it is quite convenient to identify the disk space and timing requirements.

8. Go for proper space and time planning: Once the disk space and the upgrade time required are identified depending upon the dry runs, you can take necessary action. For instance, by adjusting the SQL server memory, the time for mounting as well as upgrading SharePoint can be decreased.

9. Follow dry runs with test: The only thing that separates a live run from a dry run is that the data is not updated, hence the end result should simulate the live migration. Taking this into account, through utilization of an alternate access mapping, it can be opened up to selected end users for testing, in order to validate the overall usability and the basic functionality.

10. Set up destination environment: It is advisable to configure and prepare to the maximum extent prior to migration. Once the configuration of the environment is done, the same will ensure smoother migration.

The above mentioned tips would go a long way in helping you plan your SharePoint 2013 migration. They will definitely help you enhance the overall efficiency of your SharePoint application development team.

We provide custom SharePoint development services. If you would like to know more about the expertise of our expert SharePoint developers, please get in touch with us at Mindfire Solutions.

Steps to create a SharePoint 2013 App with Ruby on Rails

The SharePoint model is quite new to everybody and the recent launch of the 2013 version had made it even more ambiguous to developers around the world. Now, when it comes to creating an application pertaining to the software with Ruby on Rails, most developers seem to have a tough time in embracing the appropriate approach. Well, here is a guide for all Rails developers looking forward to creating an app successfully on the particular framework. However, please note that this particular guide should never be used as the best practice of Ruby on Rails development.

SharePoint 2013 mobile developmentWell, before beginning the process, you must register a new application in Office 365. Ensure that a Site Collection has been created by making use of the Developer Site Template. This can be done from the Office 365 admin screens. Following the creation of the same, browse site collection and register the SharePoint application with Office 365 as well as Azure Access Control Services (ACS). For any sort of development purpose, the registration of the new app can be easily done through appregnew.aspx page present within Office 365. Since there is no such link available for the actual page, you need browse the URL directly.

Always remember that since the registration of the application is done through appregnew.aspx, the secret of the particular app will only be known by the ACS and you. Therefore, the series of characters that will be generated will be specifically used for decoding information coming from ACS/SharePoint. Always make sure to take note of the id of the app, as you will not be having any access of the same again.

Since the application will be only used for testing and development purposes, registering it through appregnew.aspx comes across as a wise choice. If there arises a need of making the app thoroughly and widely available or list in the official store of SharePoint, then an account must be registered at the Seller Dashboard.

1. Visual Studio

The next step of work rests with Visual Studio where an application package must be created, which would eventually be uploaded to SharePoint. To make this happen, you need to follow the following steps:

  • Open Visual Studio (through ‘Run as Administrator’) for creating a new project. Go for project creation using the template ‘App for SharePoint 2013’. You will find this under the SharePoint /Office project node.
  • Following this, you will be asked about the type of SharePoint app that you would like to create. Always remember to offer your app a similar name to that you have given in the appregnew.aspx and submit the URL of the Developer site collection. Ensure choosing an application type of Provider – hosted as the hosting model.
  • In the last screen, leave the top option by selecting ‘Use a client secret’. Once, you click on the button OK, you will get to see the creation of 2 projects in Solution Explorer.
  • It is to be noted that the first project usually implies to the SharePoint App that generates the application package. This particular app will be uploaded.
  • The following step requires you to double click AppManifest.xml that consists of all the details related to the app. Upon opening the Manifest Designer, you need to remember to insert some specific values.

Always remember that the application needs to take permissions for being able to read and write data to the SharePoint site where the application is installed. This can be easily done through the permission tab. All you need to do is request just the permission that is actually needed. Always note that the more permission the app would request, the more it will run the risk of not being installed as users will be concerned about the security risk. Always remember to save and then close the AppManifest designer.

2. Ruby on Rails and Apple MacOS

To be able to work with SharePoint 2013, there stands a requirement of installing Ruby Gems to make things easier. Here is a look at the needs:

  • jwt – this helps in decoding the JSON web token that emerges from the application software
  • rest-client – this enables placing rest requests
  • nokogiri – a library that helps querying XML that is usually returned from the SharePoint

the next step of action lies in creating a new application based on Ruby on Rails in your preferred code folder. All you need to do is type into Terminal. Rails is now ready for getting a MVC web application.

Open the gemfile and under the gem stated as ‘jquery-rails’, integrate the gems that were downloaded as pre-reqs.

  • gem ‘jwt’
  • gem ‘rest-client’
  • gem ‘nokogiri’

This particular step is quite similar to the task of adding new reference in Visual Studio assembly.

3. Https Configuration

You must have noticed that while registering the application in appregnew.aspx, a Redirect URL is set that is https://localhost:3001. The app will be making use of the OAuth for being able to authorize the user and the application. Remember, that the for ensuring OAuth specification, both ends of communication must be https. After all, you would definitely not want any poor interception of unencrypted tokens to be transmitted over the Internet and have an access to the Office 365 or SharePoint site. Rails usually make use of WEBric, which is developed in web server. This is quite similar to the IISExpress of the Visual Studio.

To get the SharePoint 2013 mobile development right, you would have to follow the steps above. Then hopefully, you will be able to successfully create a SharePoint app with Ruby on Rails.

We provide SharePoint portal development services. If you would like to know more about the expertise of our expert SharePoint developers, please get in touch with us at Mindfire Solutions.