TechBytes

Components Deployment in MOSS:: What are the various types of components that can be developed and deployed in a MOSS environment? Infrastructure :: Infrastructure components are developed by software developers using typical development Tools. •Site Definition & Templates •Web Parts •User Controls •List Definitions •Master Pages & Page Layouts •Custom Assemblies •Custom Actions •Modules with Custom Pages •Content Types & Fields •Workflow •CSS & XSL Content : Content is developed by Knowledge Workers using Brower or Office Apps •Documents •List Items •Text •Images •Any other Resources •Pages (Postings) MOSS deployment standards:: • Baseline/define the deployment process –Package all the components as Solutions (including Features) –Package the assets using MSI (delivered beyond SharePoint Sites) •Define a workflow for the deployment process –Communication process between vendor and client. –Steps to be followed during deployment –Responsibilities •Each build must be

Move Sites Across Content Databases in MOSS using STSADM Content Databases of web sites in MOSS can get reach their maximum storage limit at times. In a real world scenario there may arise a need to move a Site from one Content Database to another to accommodate the proper functioning and performance which can be directly dependent on the available storage limit of the Content Database. Hence it is always advised that you change the Sites Content database. The STSADM tool provides the functionality of performing this operation with ease. Steps: 1)At the Command Prompt use STSADM and Pipe the results into an XML file Example : stsadm -o enumsites -url http://MySite/ >c:\MySite.xml 2)Modify the ‘xml’ file to contain only the details of the ‘MySite’ 3)Move the ‘MySite’ from “WSS_Content_InfyDB” to new DB Example : stsadm -o mergecontentdbs -url http://MySite/ -sourcedatabasename WSS_Content_InfyDB -destinationdatabasename WSS_Content_NewInfyDB -operation 3 -filename c:\MySite.xml Succe

Using InfoPath forms in Custom Workflows for MOSS 1) Never clone an InfoPath form it is not a good practice. InfoPath has a unique internal ID that will also copy over to new form and can create issues when both forms are used in a WF set up. 2) Always ensure that " network " published InfoPath forms (*.xsn) listed under Metadata section of "workflow.xml" (part of WF solution) exists and are under the correct folder location. Delete the references of forms not being used from "workflow.xml" which otherwise will lead to errors like "Form is closed". 3) Ensure that with every change done to the InfoPath form is acknowledged by publishing the InfoPath form to the network. 4) Ensure that every change made to the project will be accounted by redeploying the *.dll in GAC. 5) Uninstall/Install the feature. Workflows that are already in progress will be updated with the new changes. Keep this is mind before applying the changes. Accordingly wait for &qu

1) Create a directory with the name of the project in the c:\programfiles\commonfiles\MicrosoftShared\webserver extensions\12\Template\Features\ 2)Copy the worklfow and feature xml files to the folder that you have created above 3)Copy any InfoPath forms that are there also to this folder 4)Copy any ASPX forms to the c:\programfiles\commonfiles\MicrosoftShared\webserver extensions\12\Template\Layouts\ 5)Drag drop the Workflow "*.dll" file into the assemply folder in the c:\ 6)Use the STSADM tool and install and activate the Workflow.

Workflows basically comes in two flavours: 1) Human-Centric : People are the prime participants and completers of tasks 2) Machine -Centric : Computers are the prime participants and completers of tasks Now that you have understood the flavours of workflows now let me help you understand the Types of Workflows: 1) Sequential Workflows : The process has a beginning , a definite path and an end. 2) StateMachine Workflows : The process involvesa lot of complex activities and human intervention. It works around two concepts States,Events. a) State : A condition that represents the curent status of the workflow b) Event : manages the movement of the worklfow from one state to another OOB Workflows in MOSS : All workflows that come along with the MOSS are 2 step workflows and cover some basic workflow scenarios CUSTOM Workflows : Custom workflows can be developed using either the SHAREPOINT DESIGNER or the MICROSOFT VISUAL STUDIO THUMBRULE for Workflows 1) Custom workflows that are sequ