Me @ TechNet :)

My profile in the homepage of CMS community @ TechNet

http://www.microsoft.com/technet/community/en-us/cmserver/default.mspx

MOSS SP1 now available

The 2007 Microsoft Office Servers Service Pack 1 (SP1)

http://www.microsoft.com/downloads/details.aspx?FamilyID=ad59175c-ad6a-4027-8c2f-db25322f791b&DisplayLang=en

Microsoft Office Share Point Designer 2007 Service Pack 1 (SP1)
http://www.microsoft.com/downloads/details.aspx?familyid=B57C805D-2821-4625-A6F1-80725267F887&displaylang=en

Creating a Custom User Site Provisioning Solution with SharePoint Server 2007 (Part 2 of 2)

Summary: Examine new capabilities built in to the Microsoft Office SharePoint Server 2007 Enterprise Edition, which enable business process automation and simplify the business process. This article is part 2 of 2.

Custom Permission Request Workflow

One of the most innovative features of the new MOSS 2007 Enterprise Edition is the workflow feature. The new workflow capabilities are extensive, including built-in support for the following types of workflow:

• Approval

  
  

• Collect Feedback

  
  

• Collect Signatures

  
  

• Disposition Approval

  
  

• Group Approval

  
  

• Translation Management

  
  

• Issue Tracking

As a site administrator, you can instantiate these built-in workflows on any entity within MOSS with a few simple configuration steps.

However, for the permission request solution, a custom workflow is required to emulate properly the manual business process that the workflow is replacing. The workflow must accommodate sending various e-mail messages throughout the process, and depending on whether the request is approved, generate XML to be processed to add the requestor to the Members group within MOSS.

MOSS also provides a mechanism to create custom workflows. There are two primary developer tools to use for this: Microsoft Office SharePoint Designer 2007 and Microsoft Visual Studio 2005 Extensions for Microsoft Windows Workflow Foundation. Using SharePoint Designer allows a business analyst or a developer to use the workflow activities that come with Windows Workflow Foundation and MOSS. The built-in workflow actions that you can use by default in SharePoint Designer include the following:

• Setting list metadata

  
  

• Creating, copying, deleting, or changing list items (including documents)

  
  

• Checking items in or out

  
  

• Pausing, starting, or stopping the workflow

  
  

• Sending e-mail messages

  
  

• Setting the moderation status of an item

  
  

• Setting an item's metadata

  
  

• Assigning tasks

You can create custom workflows with SharePoint Designer by selecting an existing document library or list within an existing MOSS or Windows SharePoint Services 3.0 site, and then on the File menu, point to New and then click Workflow. The workflow designer wizard appears, allowing you to create a custom workflow without writing a single line of code. The workflow designer allows you to add conditions and actions to the workflow to determine when to execute specific actions.

For example, using the built-in actions mentioned earlier, you could develop a custom workflow that checks a metadata column of a particular document in a document library, and based on the value send an e-mail message or assign a task to the appropriate team member. In any case, SharePoint Designer allows for great flexibility in designing custom workflows without the need to write code.

Using Visual Studio 2005 with the Windows Workflow Foundation add-in allows you to create custom workflow actions and complex custom workflows. The add-in for Visual Studio imports Windows Workflow Foundation activities that are available by default for you to use in designing workflows. These activities are included in a Workflow toolbox and you can drag them to the design surface of the custom workflow. The next section examines this in more detail and describes the development of the custom workflow activity used in the permission request solution.

Figures 13a and 13b show the built-in workflow activities that are included with the Windows Workflow Foundation add-in for Visual Studio in the Workflow toolbox. Figure 13a shows the built-in activities for a custom state-machine workflow project.

Figure 13a. State-machine built-in workflow activity

Figure 13b shows the built-in activities for a custom sequential workflow project. For more information, see the workflow resources in Additional Resources.

Figure 13b. Sequential Workflow built-in workflow activity in Visual Studio 2005 toolbox

Although most of the actions that must be included in this permission request workflow are available as standard workflow activities with Windows Workflow Foundation and MOSS, a custom activity was developed to generate the XML file from the submitted request, which could then be processed on other servers within the SharePoint farm.

The custom workflow activity was developed with Visual Studio 2005 and Windows Workflow Foundation Extensions add-in. The activity was then deployed to the MOSS environment and used within a custom workflow. The custom workflow was developed by using SharePoint Designer.

Read More

Creating a Custom User Site Provisioning Solution with SharePoint Server 2007 (Part 1 of 2)

Summary: Examine new capabilities built into the Microsoft Office SharePoint Server 2007 Enterprise Edition, which enable business process automation and simplify the business process. This article is part 1 of 2.

Overview of a Custom User Site Provisioning Solution

This article examines some of the new capabilities that are built into the Microsoft Office SharePoint Server (MOSS) 2007 Enterprise Edition, which enable business process automation and simplify the business process. This article demonstrates the tight integration between the Office SharePoint Server 2007 portal, including Microsoft Office InfoPath Forms Services and the Business Data Catalog, and the various other 2007 Office system applications and features, such as InfoPath 2007 and Microsoft Office SharePoint Designer 2007. In addition, the solution that accompanies this article shows how accessing and manipulating various SharePoint Server components programmatically—such as the Member group and user permissions, and Business Data Catalog and legacy line-of-business (LOB) data sources—with the built-in SharePoint Server APIs enable this type of business process automation. The automation was developed primarily by using Visual Studio Tools for Office 2007 Second Edition and the Visual Studio 2005 Extensions for Windows Workflow Foundation. Additionally, you can develop traditional .NET Framework console and Windows Forms applications to make use of the SharePoint Server APIs and 2007 Office system APIs that will also facilitate the automation and simplification of business processes within the enterprise.

Employee SharePoint Permissions within the Enterprise

Most organizations have an approval process in place that allows employees’ managers to approve any costs that are associated with using new IT resources implemented in the enterprise. Usually the employee who requires access to the new system initiates the process, which spans several approval cycles by various managers, as well as a long delay and many e-mail messages. This is often a monotonous process, which consumes not only the time of the employee, but also that of the approving manager.

This article presents a solution that integrates Active Directory domain controllers, LOB data, InfoPath Forms Services, and workflow with the 2007 Office system to support the submission and automation of such requests. The solution uses employee information contained within the Active Directory domain controller and the human resources database to support the submission of the request. The data pulled from these two sources provides all the employee’s relevant information and the approving cost center manager’s information. In this scenario, an employee uses a solution based on InfoPath 2007, and the Business Data Catalog and InfoPath Forms Services features of MOSS 2007 Enterprise Edition to submit a request for permission to create SharePoint sites within the enterprise SharePoint portal.

The Business Data Catalog is a new, powerful feature of MOSS, which allows developers to surface LOB data up to MOSS from disparate legacy systems and LOB systems that exist within the enterprise. By default, the Business Data Catalog can connect to Oracle, CRM, and SAP databases, and other systems without extra development. The new and powerful InfoPath Forms Services feature of MOSS is a browser-based, thin-client run-time version of InfoPath, which allows users to read and complete InfoPath forms through the browser when the forms are integrated with MOSS.

The solution also allows the employees’ cost center manager to review the requests submitted, and approve or reject them. After the cost center manager reviews the request, the custom workflow and custom workflow activity, designed with Microsoft Visual Studio 2005 and Visual Studio 2005 Extensions for Windows Workflow Foundation, automatically sends out the appropriate e-mail messages and adds the appropriate permissions for the employee within the SharePoint portal.

To clarify the overall process of this custom permission request solution, the following diagram depicts the entire process flow logically and all of the various pieces and steps that make up the process.

Figure 1. Overview of entire permission request process

The Request InfoPath Form

The main user-centric piece of this process is the employee request form. This request form is an InfoPath form that the employee submits with the relevant data needed to review the request. Many of the fields on the form are pre-populated when the employee creates a request, to ensure data integrity throughout the process and to eliminate the amount of data that the employee is required to provide.

Figure 2 shows the request form that is used by the employees. The form pre-populates the following fields when the user creates a request:

• Employee NT ID

  
  

• Employee Full Name

  
  

• Employee Email

  
  

• Employee Cost Center

  
  

• Cost Center Approver Name

  
  

• Cost Center Approver Email

Read More

Integrating Siebel CRM with Office SharePoint Server 2007

Summary: Learn how to integrate Siebel CRM 7.8 with Microsoft Office SharePoint Server 2007

Introduction to Siebel CRM Integration with SharePoint Server 2007

The enterprise domains of most organizations usually have heterogeneous applications, and key business data is available to the users across the applications such as Siebel CRM, SAP, or PeopleSoft. In such scenarios, there is a need to have the key data available to users in a single-stop Web portal. Microsoft Office SharePoint Server 2007 offers one such portal to organizations around the world.

This article provides prescriptive guidance on the appropriate approach to build an integration solution between Office SharePoint Server 2007 and Siebel CRM 7.8 by using Web services. After integration, Office SharePoint Server 2007 users can view key data from the various modules in the Siebel system.

Integration Scope

The scope of this integration is to provide a read-only view of the data retrieved from line-of-business (LOB) applications—in this case Siebel CRM. How to insert and delete data in Siebel CRM from Office SharePoint Server 2007 is beyond the scope of this article.

Integration Benefits and Values

You can achieve the following benefits from this integration solution.

• The solution provides a one-stop data access of different LOB applications.

  
  

• The solution requires no training for SharePoint users in Siebel because they can access the Siebel data on the SharePoint portal.

  
  

• Office SharePoint Server 2007 features enable Siebel data to improve the efficiency of the SharePoint users, and improve the level of service provided to the customer.

  
  

• Users of Office SharePoint Server 2007 can access the different Siebel features from the Office SharePoint Server portal easily.

Solution Configuration Overview

The Business Data Catalog, a new integration feature in Office SharePoint Server 2007, provides the means to integrate data directly to LOB applications through Web services. The Business Data Catalog enables users to retrieve and display key business data from LOB applications in sites, lists, and user profiles within an Office SharePoint Server portal without any custom coding. The Business Data Catalog also supports features such as specific search, full text search, filtered data views, and so on.

Figure 1 provides a high-level overview of the participating components for this integration solution.

Figure 1. Solution Overview diagram

Read More

Item-Level Auditing with SharePoint Server 2007

Summary: Learn about the auditing support built into Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007, and how to extend this support with the custom Item-Level Auditing solution.

Auditing with SharePoint Server 2007
Many companies and government agencies have policies and regulations that require them to track carefully where and how users gain access to important records and documents. In particular, they need to maintain audit logs that detail events that track data such as which users viewed and updated records and documents, and when these events occurred.

Previously, Windows SharePoint Services 2.0 did not provide extensive audit support. For example, you could not use components to audit access to pages or access to items within lists. Furthermore, event handlers in Windows SharePoint Services 2.0 document libraries fired only when a document within a library was updated. Therefore, event handlers in Windows SharePoint Services 2.0 document libraries provided no support for auditing events that occur when users view documents.

Read More

Extending the Excel Services Programmability Framework

This first version of Excel Services, available in Microsoft Office SharePoint Server 2007, provides a simple yet-powerful programmability framework that you can customize to meet your business needs. However, because it is a first version, you might encounter certain limitations common to version 1 technologies and features. This article discusses how you can overcome these limitations, and how to also expand the following built-in functionality for your Excel Services solutions:

• Consumption of SharePoint lists



• Use of query tables on Excel Services



• Creation of external workbook references



• Exploitation of user-defined functions (UDFs) compatibility with the Microsoft Office Excel 2007 client application

In addition, the article shows how to use SQL write-back to further expand this built-in functionality.

Read More

Integrating SharePoint Server 2007 with Community Server Membership Databases

The business scenario discussed in this article is how to enable Community Server site users to log on to sites that are running Microsoft SharePoint Products and Technologies, by using the same credentials they use to log on to their Community Server site. Much of this article is based on Steve Peschka's post on the official Microsoft SharePoint Products and Technologies blog.

I recommend reading through his blog to get a better understanding of how this works by using SharePoint Products and Technologies.

The blog entry describes how to integrate the membership database of Community Server with the security model used in SharePoint Products and Technologies.

This article assumes a limited knowledge of Community Server, SharePoint Products and Technologies, and Microsoft ASP.NET.

Read More

Creating a Web Service Connection by Using the Business Data Catalog Definition Editor

Overview of Business Data Catalog Definition Editor

The Business Data Catalog in Microsoft Office SharePoint Server 2007 exposes and incorporates line-of-business (LOB) data into other baseline portal functionality, such as lists and Enterprise Search. To incorporate this data into your portal site, you must build an application definition file, which is an XML file that identifies where the data is stored (either in a database, or as a Web service) and what format the data is stored in (for example, what the data types and primary keys are).


Read More

The simple way to reset MOSS page caching

This is so easy solution and will not take time, just reset the IIS from the DOS prompt “iisreset”

But this is not recommended if you are working in a shared environment.