====
* MOSS is a portal server from Microsoft.
* A "portal" is a central web site which is used to organize and share company information.
* MOSS is based on WSS (Windows SharePoint Services) 3.0.
Exploring MOSS
--------------
1) Portal Features
- User Profiles
- Audiences
- Content Targeting
- My Site
- Enhanced Notification Services
- Enterprise Search
2) Business-critical Needs
- Portals - BI, Intranet/extranet
- Content Management
- Document Management
- Policy and Records Management
- Collaboration
- Process Automation
3) Collaboration Features
- Wikis and Blogs
- Configurable alerts to users and groups
- Workflow
- Content review and approval
4) Document Management
- Records management
- Document and folder-level security
- Content Management
Creating a Web Application
--------------------------
1) Open 'SharePoint 3.0 Central Administration'.
2) Click on 'Application Management' tab.
3) Click on 'Create or extend web application'.
4) Click on 'Create a new web application'.
5) Type a description, port number, and path (optional).
6) Select the "Security Configuration" options.
7) Specify the "Application Pool" details.
8) Specify the database name and authentication details.
9) Click 'OK'.
Creating a Site Collection
--------------------------
1) Open 'SharePoint 3.0 Central Administration'.
2) Click on 'Application Management' tab.
3) Click on 'Create site collection'.
4) Select a web application from the combo box.
5) Type a title and description.
6) Select a template.
7) Specify the primary and secondary administrators.
8) Select a quota template.
9) Click 'Ok'.
Creating a Quota Template
-------------------------
1) Open 'SharePoint 3.0 Central Administration'.
2) Click on 'Application Management' tab.
3) Click on 'Quota templates'.
4) Select 'Create a new quota template'.
5) Optionally, select a template to start from.
6) Type a name for the new template.
7) Set the storage limit values.
Applying a Quota Template to an Existing Site Collection
--------------------------------------------------------
1) Open 'SharePoint 3.0 Central Administration'.
2) Click on 'Application Management' tab.
3) Select a site collection.
4) Click on 'Site collection quotas and locks'.
5) Select a site lock information.
6) Select a quota template.
MOSS Site
---------
* A MOSS site is a collection of "Lists" and "Libraries".
Lists
-----
1) Announcements
2) Contacts
3) Discussion Board
4) Links
5) Calendar
6) Tasks
7) Project Tasks
8) Issue Tracking
9) Survey
10) Custom List etc.
Libraries
---------
1) Document Library
2) Form Library
3) Picture Library
4) Wiki Page Library etc.
Creating a List
---------------
1) Open the site collection home page.
2) Click on 'Site Actions' combo box on the top right.
3) Select 'Create'.
4) Select a list and create it.
Creating a Custom List
----------------------
1) Site Actions -> Create.
2) Select 'Custom List'.
3) Type a name and description.
4) Select whether to display on the quick launch.
5) Click on 'Create' button.
Adding New Columns to a List
----------------------------
1) Open the list.
2) Click on 'Settings -> Create Column'.
3) Type a column name.
4) Specify additional column settings.
Adding Records to a List
------------------------
1) Open the list.
2) Click on 'New -> New Item'.
3) Type in the column values.
Modifying Columns
-----------------
1) Open the list.
2) Click on 'Settings -> List Settings'.
3) Click on the column name.
4) Modify the column settings.
Creating a Custom List from an Excel File
-----------------------------------------
1) Site Actions -> Create.
2) Select 'Import Spreadsheet'.
3) Type a name and description.
4) Browse and open the .XLS file.
5) Click on 'Import' button.
6) Select 'Range of Cells' from the 'Range Type' combo box.
7) Click on the '-' button.
7) Select the cells.
8) Click on the red arrow.
9) Click on 'Import' button.
Creating a Document Library
---------------------------
1) Site Actions -> Create.
2) Select 'Document Library'.
3) Type a name and description.
4) Select whether to display in the quick launch.
5) Select whether to create versions.
6) Select a default document template.
7) Click on 'Create' button.
Uploading Documents into a Doc Library
--------------------------------------
1) Open the document library.
2) Click on 'Upload -> Upload document'.
3) Click on 'Browse' and select a file, OR click on 'Upload multiple files' and select the files.
4) Select whether to add a new version.
5) Type a version comment.
Checking Out a Document
-----------------------
1) Open the document library.
2) Click on the arrow for a document.
3) Click on 'Check Out'.
Checking In a Document
----------------------
1) Modify the document and save it.
2) Open the document library.
3) Click on the arrow for the document.
4) Click on 'Check In'.
View the Versions
-----------------
1) Open the document library.
2) Click on the arrow for a document.
3) Click on 'Version History'.
4) Click on the arrow for a version.
5) Select 'View', 'Restore' or 'Delete'.
Creating Form Library
---------------------
1) Open Office InfoPath 2007.
2) Select a form.
3) Save the form (.xsn).
4) File menu -> Publish.
5) In the wizard, select 'To a SharePoint server...'.
6) Type the URL of the sharepoint site collection.
7) Select 'Document Library'.
8) Select 'Create a new document library'.
9) Type a name and description.
10) Finally, click on 'Publish' button.
Adding Documents to a Form Library
----------------------------------
1) Open the form library in SharePoint site collection.
2) Click on 'New -> New Document'.
3) Fill in the form.
4) Save the form (.XML).
Web Parts
---------
* A web part is a portion of a web page which can be added, moved, minimized, closed or deleted by the end-users.
* Web parts are placed on a web part page.
* A web part page is divided into many zones.
* Each zone can contain one or more web parts.
* The same web part may appear more than once in the same zone or same page.
* WSS and MOSS have many built-in web parts.
* Custom web parts can be developed using Visual Studio 2005.
Adding a Web Part
-----------------
1) Site Actions -> Edit Page.
2) Click on 'Add a Web Part'.
3) Check the web part(s) to add.
4) Click on 'Add' button.
5) Click on 'Exit edit mode' to finish editing the page.
Adding Web Parts from Galleries
-------------------------------
1) Site Actions -> Edit Page.
2) Click on 'Add a Web Part'.
3) At the bottom of the Web Page Dialog, click on the link 'Advanced Web Part gallery and options'.
4) Drag a web part from the list and drop it on a zone.
Web Part Galleries
------------------
1) Closed Web Parts: Web parts which were closed
2) Site Collection Gallery: Web parts available only in this site collection
3) Server Gallery: Web parts common for all site collections.
Minimize, Close or Delete Web Parts
-----------------------------------
1) Site Actions -> Edit Page.
2) Click on the 'edit' button of the web part.
3) Click on Minimize, Close or Delete.
Changing Web Part Properties
----------------------------
1) Site Actions -> Edit Page.
2) Click on the 'edit' button of the web part.
3) Click on 'Modify Shared Web Part'.
4) The 'Tool Pane' of the web part is opened in the right of the page.
5) Change the property values.
Adding a Web Part Page
----------------------
1) Site Actions -> Create.
2) Click on 'Web Part Page'.
3) Type a name for the aspx file.
4) Select a template.
5) Select a document library where this web part page will be saved.
Connectable Web Parts
---------------------
* Two dissimilar web parts can be connected with each other.
* The web part which is providing the data to another web part is called as the "provider" web part.
* Similarly, the web part which is receiving the data and updating itself is called as the "consumer" web part.
* A web part can be a provider, consumer or both.
Connecting Web Parts
--------------------
1) Site Actions -> Edit Page.
2) For the provider web part, click on 'edit'.
3) Click on Connections -> Provide row/value to.
4) Select a consumer web part.
5) In the Configure Connection dialog box, select the column in the provider web part.
6) Click on 'Next'.
7) Select the column in the consumer web part.
8) Click on 'Finish'.
Removing the Connection
-----------------------
1) Site Actions -> Edit Page.
2) On the provider or consumer web part, click on 'edit'.
3) Click on Connections -> Provide or Get.
4) Select the consumer or provider web part.
5) In the Configure Connection dialog box, click on 'Remove Connection' button.
6) Click 'OK' to remove the connection.
Custom Web Parts
----------------
* Execute WssSDK.exe to install the DLL files required for creating SharePoint web parts.
* Installing VSeWSS.exe (Visual Studio extensions for WSS) will create SharePoint project templates in VS 2005.
Creating a Custom Web Part
--------------------------
1) In VS 2005, create a new project.
2) Select 'Web Part' template under 'SharePoint' group.
3) Type a project name and select a location.
4) Code the web part class with
- Custom properties and methods
- Render method
5) Build the solution.
6) Open the properties window of the project.
7) Click on 'Debug' tab.
8) In the option 'Start browser with URL', type the URL of your top level site collection where the web part must be deployed.
9) Deploy the solution.
Web Part Development
--------------------
* The web part project must refer to 'Microsoft.SharePoint.dll'.
* The web part class must inherit from 'WebPart' class in the 'System.Web.UI.WebControls.WebParts' namespace.
* The web part class also must have a unique GUID.
* The 'Render' method must be overridden to render any controls and/or HTML.
* The web part class may also have custom properties which will be exposed in the Tool Pane.
* The web part may also have a custom tool pane.
Web Part Deployment
-------------------
* The web part project must include a strong name key file.
* The DLL file must be deployed in the GAC.
* The web.config file in the virtual directory of the top-level site collection, where this web part will be deployed, must be modified.
* In the web.config file, the assembly must be marked as a 'Safe Control'.
* Restart IIS.
Rendering Controls
------------------
1) Declare an object for the control class.
2) Instantiate the object.
3) Set the property values for the object.
4) Add the object to 'Controls' collection.
5) Code the necessary event handlers.
6) To render the control, call the 'RenderControl' method by passing the HtmlTextWriter object as a parameter, in the 'Render' method.
Handling Events
---------------
1) Attach an event handler to the event of the control.
2) Code the event handler.
Database Access in Web Parts
----------------------------
1) Add reference to 'System.Data' in the web part project.
2) Import the requied ADO.NET namespaces.
3) Declare and instantiate data-bound controls.
4) Render the data-bound controls.
Debugging Web Parts
-------------------
1) Open the web part project in VS.
2) Set breakpoints.
3) Debug menu -> Attach to process.
4) Select 'w3wp.exe' (WWW Worker Process).
5) Click on 'Attach' button.
6) In the browser, add the web part or fire an event.
Now the breakpoints will work.
Custom Properties
-----------------
* A custom property in a web part must be decorated with the following attributes:
1) WebBrowsable: True or False
2) WebDescription: Descriptive text
3) WebDisplayName: Friendly name
4) WebPartStorage: Storage.Shared / Personal / None
5) SPWebCategoryName: Category under which the property must appear
6) Personalizable: PersonalizationScope.Shared / User
Custom Tool Parts
-----------------
1) Create a class inheriting from 'ToolPart' class.
2) Declare and instantiate the controls to display in the tool part (in constructor or 'CreateChildControls()' method).
3) Render the controls in the 'RenderToolPart()' method.
4) Override the 'ApplyChanges()' method to assign the value(s) of the tool part controls to the properites in the web part.
5) Modify the web part class to inherit from 'Microsoft.SharePoint.WebPartPages.WebPart'.
6) Override the 'GetToolParts()' method.
7) Add an instance of the 'WebPartToolPart' class as the first element to an array of 'ToolPart' class.
8) Add an instance of the custom tool part class as the second element to the array.
9) Return the array from this method.
Web Part Life Cycle
-------------------
* When a web part is loaded for the first time, the following events are fired:
1) OnInit
2) OnLoad
3) CreateChildControls
4) PreRender
5) SaveState
6) Render
7) Dispose
* When a web part is posted back, the following events are fired:
1) OnInit
2) LoadViewState
3) OnLoad
4) CreateChildControls
5) Postback Events
6) PreRender
7) SaveState
8) Render
9) Dispose
Developing Connectable Web Parts
--------------------------------
* For a web part to function as a "provider" or a "consumer", it must implement one or more interfaces which are available in the 'Microsoft.SharePoint.WebPartPages.Communication' namespace.
* For a provider web part, it must implement one of the following interfaces:
1) ICellProvider
2) IRowProvider
3) IListProvider etc.
* For a consumer web part, it must implement one of the following interfaces:
1) ICellConsumer
2) IRowConsumer
3) IListConsumer etc.
* The same web part may implement a provider interface and also a consumer interface, in which case it functions as a provider and consumer.
* When the data that is provided by a provider web part is not compatible with what a consumer is expecting, "transformers" must be coded.
Connection Life Cycle
---------------------
1) User selects to connect web parts.
2) The web part infrastructure gets the available interfaces from the web parts.
* 'RegisterInterface()' method must be executed for each and every interface implemented by the web part.
* The method invocation must be done by overriding the 'EnsureInterfaces()' method.
3) Get the connection option (client or server).
* Override the 'CanRunAt()' method to specify whether to execute in the client or server.
4) The web parts get connected and they are notified by the web part infrastructure.
* Override the 'PartCommunicationConnect()' method.
5) Exchange schema information
* Override the 'PartCommunicationInit()' method.
6) User selects data in the provider web part.
7) Data sent from provider to consumer.
* Override the 'PartCommunicationMain()' method which fires the corresponding event. For example, 'RowReady' event must be fired for providing a row.
Testing the Web Part
--------------------
1) Create a custom list called 'Publishers'.
2) Rename the 'Title' column to 'Publisher'.
3) Add the custom list as a web part on the page.
4) Add some publisher names to the list.
5) Create another custom list called 'Authors'.
6) In addition to the 'Title' column, add one more column called as 'Author'.
7) Add the Authors list also as a web part on the page.
8) Add some records to the list.
9) Add the custom connectable web part to the page and position it inbetween the two custom lists.
10) Connect the custom web part to both the custom lists.
11) Select a publisher from the Publishers web part.
Now the custom web part displays the publications for the select publisher.
12) Select a publication in the custom web part.
Now the Authors web part filters the records according to the selection.
SharePoint Object Model
-----------------------
* Microsoft.SharePoint is the main namespace for working with SharePoint object model.
* Microsoft.SharePoint.WebControls namespace some important classes like 'SPControl'.
* Important classes are:
1) SPWeb
2) SPControl
3) SPSite
4) SPDocumentLibrary
5) SPListItemCollection
6) SPListItem
7) SPUser etc.
SharePoint Web Services
-----------------------
* SharePoint web services can be accessed from a windows application or an ASP.NET web application.
1) Create a Windows or ASP.NET web site.
2) Project menu -> Add Web Reference.
3) Click on the link 'Web services in the local machine'.
4) Select a web service list.
NOTE: The web service must belong to the top-level site which you need to access.
Packaging a Web Part
--------------------
1) Open the web part project in VS 2005.
2) File menu -> Add -> New Project.
3) Select 'Setup and Deployment' under 'Other Project Types'.
4) Select the 'CAB Project' template.
5) In Solution Explorer, right-click on the cab project.
6) Select 'Add -> Project Output'.
7) Select 'Primary Output' and 'Content Files'.
8) Build the solution.
Deploying the CAB File
----------------------
1) Open DOS prompt on the server where you want to deploy.
2) Type the following command:
stsadm -o addwppack -filename filename.cab
Windows Workflow Foundation (WWF)
===========================
* A workflow is an ordered series of steps that accomplish some defined purpose according to a set of rules.
* A workflow can be hosted in:
1) Windows or
2) SharePoint Server
* Workflows can be classified as:
1) Sequential
2) State Machine
* VS 2008 has a built-in designer to design and develop workflows graphically.
* A Workflow consists of 'activities', which are available in the Toolbox.
* "Visual Studio Extensions for Windows Workflow Foundation" must be installed to get workflow templates in VS 2005.
* In VS 2008, workflow templates are built-in.
Workflow Project Templates
--------------------------
1) Sequential Workflow Console Application: To create a sequential workflow and host it in a console application.
2) Sequential Workflow Library: To create a sequential workflow.
3) State Machine Workflow Console Application: To create a state machine workflow and host it in a console application.
4) State Machine Workflow Library: To create a state machine workflow.
5) Workflow Activity Library: To create a custom activity.
Workflow Architecture
---------------------
* 'System.Workflow.Runtime.WorkflowRuntime' class is the runtime engine of workflow foundation.
* 'System.Workflow.Runtime.Hosting' namespace provides the different runtime services.
* 'System.Workflow.Runtime.WorkflowInstance' class is used for creating instances of workflow.
Registered Workflow Services
----------------------------
1) Scheduler service
2) Commit Work Batch service
3) Persistence service (optional)
4) Tracking service (optional)
Passing Parameters to Workflow
------------------------------
1) In the host application, declare and instantiate a 'Dictionary
Dictionary
2) Add the property names and values to the dictionary object.
3) Specify the dictionary object while instantiating the workflow instance using 'CreateWorkflow()'.
WorkflowInstance instance = wfrt.CreateWorkflow(typeof(Workflow.Workflow1), dict);
4) Open the workflow code window (workflow1.cs).
5) Add properties to the workflow class with the same names as mentioned in the dictionary object.
Returning Values from Workflow
------------------------------
1) Design and code the workflow.
2) In the host program, add the parameters to the dictionary collection.
3) In the 'WorkflowCompleted' event handler, use 'e.OutputParameters' collection to read the return values.
Hosting Workflows
-----------------
* Workflows can be hosted in varied applications:
1) EXE (Console/Windows applications)
2) Windows Service
3) ASP.NET Web Application
Conditions
----------
* Conditions in a workflow can be of two types:
1) Code condition
2) Declarative Rule condition
* A code condition is hard-coded in the code window (.cs).
* A declarative rule condition is entered in a 'Rule Condition Editor'.
* Declarative rules are saved in a '.rules' file.
* A rules file contains conditions in XAML (XML Application Markup Language), pronounced as 'Zammel', format.
Custom Activities
-----------------
* Apart from the built-in activities provided by Microsoft, we can create custom activities.
* A custom activity is designed and coded just like a workflow.
* Custom activities can contain .NET properties as well as "Dependency Properties".
* Dependency property of an activiy is one which can be bound to another activity's property.
Creating a Custom Activity
--------------------------
1) Create a new workflow project.
2) Project menu -> Add Activity.
3) Type a name for the activity.
4) Design the activity by placing other activities inside it.
5) Code .NET properties, dependency properties and event handlers.
6) Save and Build the project.
7) Switch to the workflow designer.
Now, the custom activity will be available in the toolbox.
Generating a Dependency Property
--------------------------------
1) Right-click in the code window.
2) Select 'Insert Snippet'.
3) Select 'Other -> Workflow -> Dependency property-Property'.
4) Type a name for the property and press TAB.
5) Type the data type for the property and press TAB.
Activity Library
----------------
* Creating a custom activity in a workflow project will make it available only in that project.
* To use a custom activity in multiple workflow projects, create it in a 'Activity Library' project.
Creating an Activity Library
----------------------------
1) New Project -> Workflow Activity Library.
2) Design and code the custom activity.
3) To include multiple activities, Project menu -> Add Activity.
4) Save and Build the project.
Using an Activity Library
-------------------------
1) Open any workflow project.
2) Right-click on the Toolbox.
3) Select 'Choose Items'.
4) Browse and select the DLL file of the activity library.
Now, the custom activities will be available in the toolbox for all workflow projects.
Debugging a Workflow
--------------------
* If the workflow and the host are separate projects, executing the host will not allow us to debug the workflow.
* To debug the workflow project from the host:
1) Open the project properties window of the workflow project.
2) Click on 'Debug' tab.
3) Under 'Start Action', select the option 'Start external program'.
4) Browse to the folder containing the EXE file of the host and select it.
5) Instead of executing the host, execute the workflow library project. Now, the breakpoints will work.
NOTE: If both the projects are in the same solution, set the Workflow library project as the Startup project.
Hosting in Windows Application
------------------------------
1) Create a workflow using 'Sequential Workflow Library' project template.
2) Design and code the workflow.
3) Add public properties and methods.
4) Save and Build the project.
5) Create a Windows application or service.
6) Add reference to the DLL file of the workflow.
7) Also add references to:
i) System.Workflow.Runtime
ii) System.Workflow.Activities
iii) System.Workflow.ComponentModel
8) Import the workflow namespaces.
State Machine Workflows
-----------------------
* A state machine workflow is made up of multiple 'states'.
* The workflow makes transition from one state to another based on a delay or an external event from the host.
* One of the states must be marked as 'Initial state' from where the workflow starts execution.
Creating a State Machine Workflow
---------------------------------
1) Create a 'State Machine Workflow Library' or 'State Machine Workflow Console Application'.
* Visual Studio automatically adds one 'State' activity to the workflow.
2) Specify a 'Name' for the state.
3) Add multiple State activities to the workflow.
4) Rename all the state activities.
5) Add an interface to the workflow marked with the attribute '[ExternalDataExchange]'.
6) Add the different events which your workflow will be listening to.
7) In each state, optionally add 'StateInitialization' and/or 'StateFinalization' shapes, and add other shapes into them.
8) Add an 'EventDriven' activity inside each state.
9) Inside the EventDriven acitivity, add an 'HandleExternalEvent' activity to listen for the events.
10) Based on the event, change the state by using 'SetState' activity.
11) Alternatively, use a 'Delay' activity instead of 'HandleExternalEvent' activity.
12) In the workflow properties, set the name of the initial state in the 'InitialStateName' property.
13) In the host application, implement the interface in a class and code methods for firing the corresponding events.
SharePoint Workflows
--------------------
* SharePoint workflows are hosted by either WSS or MOSS.
* SharePoint workflows can be created using:
1) WSS/MOSS UI
2) Office SharePoint Designer 2007
3) Visual Studio 2005
Enabling Workflows for a Site
-----------------------------
1) Open 'SharePoint 3.0 Central Administration'.
2) Click on 'Application Management' tab.
3) Click on 'Workflow Settings' link.
4) Select the web application.
5) Select 'Yes' for enabling workflows for the site.
Creating Workflows using SharePoint UI
--------------------------------------
1) Create a document library.
2) Open the document library.
3) Click on 'Settings -> Document Library Settings'.
4) Click on 'Workflow settings' link.
5) Select a workflow template.
6) Type a name for the workflow.
7) Select a 'Task' list and a 'History' list.
8) Check the start option(s).
9) Click on 'Next' button.
10) Specify how tasks are routed to participants.
11) Type the names of the people you want to participate.
12) Optionally, specify a 'Due date'.
13) Optionally, specify when you want to complete the workflow.
14) Click 'OK' to create the workflow.
Starting a Workflow
-------------------
1) Open the document library for which the workflow was created.
2) Click on the down arrow of a document.
3) Click on 'Workflows'.
4) Add the names of the approvers.
5) Type a message to include with your request.
6) Optionally, specify a 'Due date'.
7) Optionally, specify the users who must be notified about this workflow starting.
8) Click 'Start'.
Now, the status of the workflow for the document will be 'In Progress'.
Responding to a Workflow Task
-----------------------------
1) Open the document library.
2) Click on workflow status for the document.
3) Click on the workflow task.
4) Type some comments.
5) Click on 'Accept' or 'Reject.
Now, the status of the workflow for the document will be 'Approved' or 'Rejected'.
Viewing Workflow Reports
------------------------
1) Open the document library.
2) Click on the down arrow of the document.
3) Click on 'Workflows'.
4) Under 'Running workflows' or 'Completed workflows', click on a workflow name.
5) In the workflow status page, click on 'View Workflow Reports'.
6) Click on a link to view the corresponding report.
Office SharePoint Designer 2007
-------------------------------
* SharePoint Designer tool is used for
1) Creating/modifying web pages
2) Applying CSS
3) Creating/modifying workflows
Creating Workflows using SharePoint Designer
--------------------------------------------
1) Open Office SharePoint Designer 2007
2) File menu -> Open Site.
3) Type the URL of the top-level site collection.
4) Click 'Open' button.
5) File menu -> New Workflow.
6) Type a name for the workflow.
7) Select a document library from the combo box, and select the workflow start options.
8) Click on 'Initiation' button located at the bottom of the wizard page.
9) In the 'Workflow Initiation Parameters' dialog, click on 'Add' button.
10) Type a name for the field.
11) Select a data type for the fieled.
12) Optionally, type a default value.
13) Click on 'Finish' button.
14) Repeat steps 9 to 13 for other initiation fields.
15) Finally, click 'OK'.
16) Click 'Next' button in the wizard to add a step.
17) Type a name for the step.
18) Click on 'Condition' button.
19) Click on an option.
20) Select a field, operator and value.
21) Optionally, add multiple conditions.
22) Click on 'Actions' button.
23) Click on an option.
24) Select the required details for the action.
25) Repeat steps 22 to 24 to add multiple actions.
26) Click on 'Add Else If Conditional Branch' to design complex conditions.
27) Click on 'Add Workflow Step' for adding more steps.
28) Finally, click on 'Check Workflow' button at the bottom of the wizard page to validate the steps.
29) Click on 'Finish' button.
Viewing the Workflow in SharePoint
----------------------------------
1) Open the document library.
2) Click on 'Settings -> Document Library Settings'.
3) Click on 'Workflow Settings'.
Starting a Workflow from Office Clients
---------------------------------------
1) Open the document library.
2) Click on the down arrow of the document.
3) Click on 'Edit in...'.
4) From the Office Client application (Word, Excel etc.), open the main menu.
5) Click on 'Workflows'.
6) Click on the 'Start' button for the workflow you want to start.
7) Type the values for the initiation variables.
8) Click on 'Start' button.
Limitations of SharePoint Designer
----------------------------------
1) Even though the wizard is very user-friendly, there is no designer tool available.
2) The workflow created in SharePoint Designer is bound to a specific document library.
3) Only predefined conditions and actions can be used.
4) Only Sequential workflows can be created; not possible to create State Machine workflows.
5) Not possible to write any code.
6) The markup file and rules file are uncompiled and stored in a document library. They are compiled only on demand.
7) Custom forms cannot be created; only the ASP.NET form automatically generated by the wizard can be used.
8) No support for debugging.
Creating SharePoint Workflows using VS 2005
-------------------------------------------
* The following must be installed for creating SharePoint workflows in VS 2005:
1) MS.NET Framework 3.0
2) Visual Studio Extensions for Workflow Foundation
3) Visual Studio Extensions for WSS (VSeWSS.exe)
* Creating a SharePoint workflow in VS 2005 has the following advantages:
1) The 'Workflow Designer' tool can be used to graphically add activities.
2) The project can be saved as a template and can be associated with multiple document libraries/sites.
3) Custom activities and conditions can be created.
4) Apart from Sequential workflows, SharePoint State Machine workflows can also be created.
5) Custom code (properties, methods, event handlers) can be written in the code-behind file.
6) The project can be compiled into an assembly and deployed to any SharePoint server.
7) InfoPath or ASP.NET forms can be used.
8) Debugging is possible using the IDE.
SharePoint Search
-----------------
* The primary steps in implementing SharePoint search are:
1) Indexing content
2) Associating web applications with content indexes
3) Defining scopes
Out-of-the-box Content Source Types
-----------------------------------
1) File share content
2) Exchange server content
3) Lotus Notes server content
4) SharePoint sites content
5) Business Data Catalog content
6) Web sites
Implementing Content Sources
----------------------------
1) Open "Shared Services Provider(SSP) Administration" page.
Central Administration -> Application Management -> Create or Configure this Farm's Shared Services
2) Click on a SSP name.
3) Click on 'Search Settings' link.
4) Click on 'Content sources and crawl schedules'.
5) Click on 'New Content Source' button.
6) Select a content source type.
7) Type the URL.
8) Set the crawl settings and crawl schedules.
9) Check the option 'Start full crawl of this content source'.
Creating Crawl Rules
--------------------
1) Open SSP Administration.
2) Click on 'Search Settings'.
3) Click on 'Crawl Rules'.
4) Click on 'New Crawl Rule'.
5) Type a path affected by this rule.
6) Specify crawl configuration.
Configuring Search
------------------
1) Open SharePoint Central Administration.
2) Click on 'Application Management' tab.
3) Click on 'Manage Search Service'.
4) Click on 'Farm-level search settings'.
5) Type a contact e-mail address.
6) Configure proxy server settings.
7) Set timeout settings.
Defining Search Scopes
----------------------
1) Open SSP Admin.
2) Click on 'Search Settings'.
3) Click on 'View scopes'.
4) Click on 'New Scope' button.
5) Type a scope name and description.
6) Specify a specific search results page.
7) Click on 'Add Rules'.
8) Specify a 'Scope Rule Type'.
9) Select a content source.
10) Select a behavior.
Configuring Crawl Rules
-----------------------
1) Open SharePoint Central Admin.
2) Click on 'Application Management' tab.
3) Click on 'Manage Search Service'.
4) Click on 'Crawler Impact Rules'.
5) Click on 'Add Rule'.
6) Type the name of a site.
7) Specify the 'Request Frequency'.
Backup and Restore
------------------
1) Open SharePoint Central Admin.
2) Click on 'Operations' tab.
3) Click on 'Perform a backup' link.
4) Check the web applications to backup.
5) Click on 'Continue to backup options' button.
6) Select the type of backup (Full or Differential).
7) Type a location to store the backup.
* To restore from a backup.
1) Click on 'Operations' tab in SharePoint Central Admin.
2) Click on 'Restore from backup' link.
3) Specify the backup location.
4) Select a backup.
5) Click on 'Continue Restore Process' button.
6) Check the components to restore.
7) Click on 'Continue Restore Process' button again.
8) Select New configuration or Same configuration.
9) Provider username and password.
10) Optionally, type new names for the URL, application, database server, and database.
MOSS Topologies
---------------
1) Single Server
2) Small Server Farm
3) Medium Server Farm
4) Large Server Farm
Single Server
-------------
* IIS, SQL Server, WSS/MOSS, and shared services(application server) are installed on the same machine.
* This type of installation can support even SQL Express.
* With SQL Express, maximum of 500 users are supported.
* With SQL Server, maximum of 5000 users are supported.
Small Server Farm
-----------------
* The database is installed on one server, and the other components are installed on one or more servers.
* Typically, two to three servers are installed in this topology.
* This type of installation supports maximum of 50,000 users.
Medium Server Farm
------------------
* The database is installed on one server.
* The application server is installed on the second server.
* MOSS is installed on one or two servers.
* Typically, three to four servers are installed in this topology.
* This type of installation supports maximum of 1,00,000 users.
Large Server Farm
-----------------
* The database is clustered on two or more machines.
* The application server is also installed on two or more machines.
* MOSS is also installed on two or more machines.
* Hence, this topology has 6+ servers.
* This type of installation supports maximum of 5,00,000 users.
NOTE: Medium and Large server farm topologies are available only for MOSS installations, and not for WSS.
We collect videos & images from online sites like youtube and some other websites which provide them. And most of the News is also gathered from other online websites. Any material downloaded or otherwise obtained through the use of the service is done at your own discretion and risk and that you will be solely responsible for any damage to your computer system or loss of data that results from the download of any such material. If you feel that the content on the site is illegal or Privacy please contact us at srinuchalla@gmail.com and such videos, images or any Content will be removed with immediate effect.
Appreciate your Initiative ! Never Stop blogging
ReplyDelete