SharePoint 2013 for Developer: Baby Journey (2)

Setting Up SharePoint Farm for SharePoint 2013 Development
1. Setting up Site Collection Host Name Web Application to host all the site collection hosted name

a. Create Site Collection Hosted Name Web Application
b. Create Site Collection with Developer template

Setting up Site Collection Host Name

a. The Site Collection Hosted Name Web Application is really an empty web application which tied to your server url (e.g http://servername). We are using this web application to host all our site collection. For example(http://intranet.company.com or http://developer.company.com).

b. No site collection in it need to be created after creating the Site Collection Hosted Name Web Application at Central Admin.
Note: Site Collection hosted name have in SharePoint 2010 also.

 How
a. Go to Central Admin to create a Web Application



b. Click New

c. Key in
Name: SharePoint – Host
Port: 80




d. Use the Application Pool or create your own Application Pool
c. Database Name: WSS_Content_Host
d. Click [OK] button
e. The new SharePoint Host is created


*Note
You can key in anything that is meaningful don’t have to follow me.




Creating Site Collection using Power Shell
SharePoint 2013 do not provide GUI for creating Site Collection with host name, we have to use Power Shell to do so.

How

a. Open SharePoint 2013 Management Shell

b.  Type the following:
$HostWebApp = Get-SPWebApplication | Where-Object {$_.DisplayName -eq "SharePoint Host"}

c. Create developer site selecting the developer template "DEV#0" by typing the following:


New-SPSite  -Name "Developer Site" -Url "http://developer.companyName.com"  -OwnerAlias "CompanyName\SPAdmin" -HostHeaderWebApplication $HostWebApp -Template "DEV#0"

d. Create Intranet Site by typing the following:

New-SPSite  -Name "Developer Site" -Url "http://intranet.companyName.com"  -OwnerAlias "CompanyName\SPAdmin" -HostHeaderWebApplication $HostWebApp -Template "STS#0"

e. If you are doing programming for Workflow, then you need to create a none-templated root site for Workflow to connect to it.

New-SPSite  -Name "Root Host" -Url "http://serverName"  -OwnerAlias "CompanyName\SPAdmin" -HostHeaderWebApplication $HostWebApp


Conclusion:
We have created our SharePoint environment for testing our solution.

Comments

Post a Comment

Popular posts from this blog

SharePoint 2013: Distributed Cache Services

Image
What is Distributed Cache Services(DCS)? - It is a Platform Service, it runs at the Farm Level.   -- You can decide to run it on all servers in the farm or you can use it to run on a 1 or a couple of servers.   -- Suggest to have dedicate servers for DCS. - It provides in-memory cache for the entire farm. - It is based on Window Server App Fabric Distributed Caching. - It uses to cache Authentication Token(to avoid multiple authentication processes) and MySite Social Feeds. - DCS enable by default and allocate memory based on total memory on your server.   -- You should at least dedicate 50% of RAM or more just to the DCS service for overhead. What is it NOT : - It do not uses Window Azure Cache services and thus it cache on local server (no cloud). - It uses Window Server App Fabric version that comes together with the installer: You are not recommended download any version from Microsoft and upgrade it independently.  - You are not recommende...
Read more

SharePoint 2013 for Developer: Baby Journey (1)

Introduction to SharePoint 2013 for developer (1): Introduction a. SandBox is not the way to go for SharePoint 2013 or SharePoint Online 2013  SharePoint 2013 App Model is the replacement for SandBox but SandBox still exists in SPS2013 for backward compatibility purpose. SharePoint 2013 Farm\SandBox Solution :  -CAB File with a .wsp extension -Container of files distributed as a unit (no change from previous version) -Contains manifest with instruction for installer (no change from previous version) -Use powershell to deployed  Good News : - Nothing changes on Farm\SandBox solution: so 0 relearning - Bad News:  - Because nothing change, 0 enhancement to that as well.   File system in SharePoint 2013  - same path as SharePoint 2010 or MOSS(2007) -c:\program files\ common files\ microsoft shared\web server extension\ NOTE: it contains 2 folders (14 and 15) - 14 : Is for 2010 and 15 is for 2013 WHY? * SharePoint 2013 have ...
Read more

File Structure (Part 1)

Image
There are few ways for people who arrange their folder structures and which i do not wish to invent it. My approach is to arranging my folder structures based on Features not by types What is Type? Angular have alot of types. for example, we have Controller, Services, Directives which are the commonly used. We do not wish to arrange our file structure like this: This file approach is suitable only for SMALL application, for enterprise application, we have tons of Modules and alot of programmers are working on different modules. So before we jump to multiple modules, we should first arrange our file structures by modules. Let say build an intranet application which consists with Employees modules, eTimelog modules and eLeave modules. I would like also to create main folder to stores all my framework (layout, sidebar, navigationbar, footer-bar etc on my site. here is my simple file structure: - common: putting all my modal, services\repositories\utilities class to be...
Read more