Search This Blog

Showing posts with label Deployment. Show all posts
Showing posts with label Deployment. Show all posts

Thursday, August 22, 2013

Information management - Deployment

This blog is all about Deployment of your solution!

First thing first. Where are we in the process? When we are ready for deployment we already covered (in one form or another):
- Information architecture - Done!
- Logical architecture - Done!
- Physical architecture - Done!
- Installation - Done!

Woohoo! So now we can implement our solution, finally!

You have several options for a SharePoint deployement:
- Manual
- Automated
- Mixed

Manual deployment
A manual deployment is exactly what it is, a manual deployment. You ask somebody to manually, a.k.a using the SharePoint user interface, to create the required objects, like:
  • Web apps
  • Site Collections
  • Sites
  • Content Types
  • Site Columns
  • Libraries
  • SharePoint Groups
  • Activate features
  • Configure (SharePoint) settings
  • etc.
Requirements for a manual deployment:
  • Accurate information architecture
  • Extremely organized and punctual consultant(s)
  • Test environment
  • Time!
One of the key take aways here is having a specific persona in your team. One that is able to replicate exactly what is written in the information architecture and is able to spot mistakes. I have been working with SharePoint more then 7 years and haven't seen a 100% accurate information architecture with matching logical architecture.

Another key aspect if this type of deployment is time. Manually creating and testing all objects can take days or even weeks! This, off course, depends on your implementation. Think about a DMS solution with 1-5 site collections, 40 content types, 20 or so document libraries and content organizer rules that move documents through your system.

Automated deployment
An automated deployment is a deployment where you use pre-configured scripts, compiled code to create the objects mentioned above.

You could create SharePoint features using Visual Studio that deploy webpart, content types, libraries, etc. Another way is by using Powershell scripts.

Requirements for an automated deployment:
  • Accurate information architecture
  • Development team
  • Development environment
  • Test environment
There is a new requirement here Development environment. I personally do not think it it neccesary in a manual deployment but this is very arguable, I agree!

The requirement time isn't on the list. You've been using that during the developement process. Building the features or scripts. Deployment should be a breeze....

Mixed deployment
Off course it is really feasible to use a mixed deployment, e.g.:
Creation of web applications, site collections, content databases, content types, site columns, libraries etc is done using powershell scripts.
Creation of custom webparts is done via custom developed features.
Content organizer rules are created manually.

Requirements for an mixed deployment:
  • Accurate information architecture
  • Development team
  • Development environment
  • Test environment
  • Extremely organized and punctual consultant(s)
  • (Time)
With a mixed deployment you need, off course, all the requirements above!

Saturday, December 31, 2011

Information Management - The Series

SharePoint in the Real World - Information Management

I've been playing around with this new blog and this thing is so complex that I decided to create several blog post for this one. 
  • Information management - Findability & Data
  • Information management - Analysis
  • Information management - Deployment
  • Information management - Maintenance
The above is certainly not carved in stone. I'm not totally convinced that Deployement and Maintance will become different blogs. Maybe I'll group them. maybe I will add more..and maybe the above will prove just about wright!

Findability & Data

Findability & data is all about how users find the data they need, what data it is that they need, how they are going to use it and why. This information is crucial for the steps to come.

Analysis

Analysis is all about analysing the information & business requirements. In this blog I'll write how I go about determining the requirements and validating them to the conceptual, logical and physical architecture. (I think I will also need to explain about the conceptual, logical and physical architecture)

Deployment

Okay, analysis is done! We are ready to create and deploy this stuf! Cool, but how are we going to do that?

Maintenance

As a wise man once said: WHOOHOO we deployed it and everything is fine we can go home and die - or do something else :-). Nooo some user wants to change my beloved configuration! Now what? Maybe we'd better think this through before hand. That's what this blog is going to be about. Planning for change and how change effects your environment, time-2-market and what not.

I really hope you guys and girls appreciate the effort and give me some feedback!

Regards,
GH