36. Deployment steps
in SharePoint ?
A Solution
Package is a CAB file with WSP extension, which contains all the
files required to implement the Features in your Visual Studio project.
Add
the WSP to the SharePoint Server
The first thing you need to do is
copy over the wsp deployment file. The best things to do is to create a
deployment folder, where all the deployed files are kept.
Copy over the deployment files to: C\Deploy\WSP
Add
the WSP to the SharePoint Farm Solution library
Open “SharePoint 2013 Management
Shell “ as administrator
a. Open the Search on Server 2012
b. Search for “SharePoint 2013
Management Shell”
c. Right click “SharePoint 2013
Management Shell”
d. Select “Run as Administrator”
Run this script:
Add-SPSolution " C\Deploy\WSP \{file name}.wsp"
Deploy
the WSP to the SharePoint Farm Solution library
Open Central Administration
Click “System Settings”
Click “Manage farm solutions”, under “Farm Management”
Click on the {file
name}.wsp package
Click “Deploy Solution”
Deployment settings
Deploy When: Now
Deploy to: All content Web application
Click “OK”
How
to activate the WSP Feature on the Site Collection
Activate
the WSP Feature on the Site Collection
Open the Root Site (the Site
Collection)
Click the cog, in the top right
corner (Site Actions)
Select “Site Settings”
Click “Site collection features”,
under “Site Collection Administrator”
Go to {file
name}
Click “Activate”, to the right
37. STSADM VS PowerShell in SharePoint ?
Stsadm ”stands for SharePoint Team Services
Administration"
It is a Command-line tool used for administration of
Office SharePoint 2007 (or MOSS 2007) servers and sites and even its not Not
limited to administrative needs – can be extremely helpful to developers.
STSADM located under C:\Program Files\Common Files\
shared\web server extensions\12\bin.
Before SharePoint 2010, the only way to manage
SharePoint at the command line was STSADM However, in SharePoint 2010 and later, STSADM was depreciated and replaced by PowerShell.
In SharePoint 2013 Preview, STSADM still there and can be used, however
Microsoft suggests to use PowerShell commands instead.
Therefore if you are still using STSADM , Microsoft released a list of all the STSADM commands and their equivalent in PowerShell
to encourage you to make the switch.
STSADM to Windows PowerShell
mapping in SharePoint 2013
STSADM
It is nothing
but a Command Line tool which is more prevalent in SharePoint 2007 and slowly
depreciating.
Excecuting STSADM commands always return String
Values.
Looping is not Possible.
Accessing Files in the file server and registry operations
are not supported.
Powershell
Next Generation Microsoft Scripting language.
Executing Powershell Commands always returns .Net
Objects. This features really improves the performance since all the SPList,
SPweb objects are .Net Objects inturn.
Looping, Multiple executions are Possible being a
Scripting Language.
We can easily play around with system registry as
well.
38. Difference
between Event Receiver and Workflow ?
Main Differences Between SharePoint Event Receivers
and SharePoint Workflows are:
1. Event handlers Can't be manually initiated -
workflows can be initiated either automatically or manually.
2. Event Handlers can be Synchronous or Asynchronous
- Workflows are always async (They executes after the operation)
3. In Event Receivers we can cancel the operation
(such as add/update/delete) - But in Workflows its not possible.
4. Event handlers execute from a Particular WFE, So
when something goes wrong in that WFE, It may end-up. But Workflow Jobs are
robust and can resume even after
Reboots.
5. Usually Event handlers runs for short period -
Workflows can be longer even for years!
6. There is no User Interface/user Interaction in
Event Receivers - Workflows can have user interactions such as getting user
input in Initiation forms.
7. As the Name indicates, SharePoint Event receivers
are triggered by events like New Item Adding-Added, Updating-Updated,
Deleting-Deleted, etc. - But Workflows triggered only on
Creation/Change/deletion.
8. Event Receivers are created using Visual studio -
Workflows can be via SharePoint user interface, SharePoint Designer, Visio or
Visual studio.
9. Workflows leaves "Workflow History"
logs which we can refer for debugging - Event handler doesn't do such.
10. Event receivers are better for large volume -
Workflows are better for small amount of data.
39. Search
Architecture in SharePoint 2013 ?
There are actually four types of databases for the
search functionality in SharePoint 2013.
Crawl Database
Search Administration Database
Link Database
Analytics Reporting Database
Crawl Database - It stores all the crawl related
information, such as the last crawl time and the last Crawl ID.
Search
Administration Database - It contains the search configuration settings, such
as the search topologies, mapping between the crawled items and the metadata
properties.
Link Database
- It stores information such as the search clicks along with storing
information obtained from the Content Processing Components.
Analytics
Reporting Database - For generating reports on the search related information
and usage analysis, this database is used.
40 User Profile Service in SharePoint ?
The
User Profile Service will allows you for configuring and managing User profile
properties, Audiences, Profile synchronization settings, organization browsing
and management settings, and My Site settings.
Thank you very much
Fahadullah Karimi
SharePoint Specialist
| Previous SharePoint Interview Questions And Answers | Next SharePoint Interview Questions and Answers |
No comments:
Post a Comment