All Versions
Microsoft Office SharePoint Server 2007 products comparison download
Penny Coventry: Sharepoint Version Table
Heather Solomon: CSS Quick Reference
Heather Solomon: CSS Reference Chart for Sharepoint 2003
Version 3
Microsoft TechNet: Office SharePoint Server 2007
Microsoft TechNet: Upgrading to Office SharePoint Server 2007
Microsoft TechNet: Determine upgrade approach (Office SharePoint Server)
Microsoft Office Online: Microsoft Office SharePoint Server 2007 Frequently Asked Questions
Jason Medero: WSS V3/MOSS 2007 Upgrade and Migration from V2: Part 1 of 2
Jason Medero: WSS V3/MOSS 2007 Upgrade and Migration from V2: Part 2 of 2
Joel Oleson: Troubleshooting & Logs during a WSS/MOSS Upgrade
Shane Young: Upgrading from SPS 2003 to MOSS 2007 Beta2 TR using the gradual approach
Jonathon Frost: Preparing for a SharePoint Server 2007 Upgrade
James Henry: SPS 2003 to MOSS 2007 Upgrade Issues
William Baer: Understanding PRESCAN.EXE in MOSS 2007
Bill English: Moving SPS 2003 Databases to new SQL Servers
MSDN: Best Practices for Ensuring Application Reusability and Upgrade in Windows SharePoint Services
Joel Oleson: Best of... Upgrade and Deployment Guides for WSS v3 and Microsoft Office SharePoint Server 2007
Version 2
MSDN: Branding a SharePoint Portal Server 2003 Site: Part 1, Understanding the Use of a Corporate Brand
MSDN: Branding a SharePoint Portal Server 2003 Site: Part 2, How to Apply Your Own Corporate Brand
Dr. Dobbs: Sharepoint Web Part Development
Version 1
Microsoft: How to Create a Personal Dashboard in SharePoint Portal Server
Microsoft: Programs That Cannot Coexist with SharePoint Portal Server
Microsoft: Accessing a Workspace Using HTTPS Does Not Work, Dashboard Error -2147221499
Microsoft: Setup FAQ and Troubleshooting Guide
Microsoft: IIS Lockdown Tool Affects SharePoint Portal Server
Microsoft: Errors When Antivirus Software Scans Web Storage System
Microsoft: Indexing Web Sites on the Internet
Microsoft: Portal Displays Incorrectly When You Use FQDN
Microsoft: Required Properties Not Enforced During Bulk Check-in
Microsoft: SharePoint Portal Server and Storage Area Networks
Tuesday, October 24, 2006
Monday, October 23, 2006
Links: SQL Server 2005
Microsoft SQL Server 2005 Books Online
Microsoft SQL Server 2005 RS Tutorials
Microsoft SQL Server 2005 Hardware and Software Requirements for Installing
Microsoft SQL Server 2005 Maximum Capacity Specifications
Microsoft SQL Server 2005 Maximum Number of Processors Supported
Microsoft SQL Server 2005 Memory Supported
Microsoft SQL Server 2005 RS Tutorials
Microsoft SQL Server 2005 Hardware and Software Requirements for Installing
Microsoft SQL Server 2005 Maximum Capacity Specifications
Microsoft SQL Server 2005 Maximum Number of Processors Supported
Microsoft SQL Server 2005 Memory Supported
Sunday, October 22, 2006
Monday, October 02, 2006
Using the Web Service Interface of Windows SharePoint Services (2003)
Web services available in Windows SharePoint Services:
Administration
Administrative methods for managing a deployment of Microsoft Windows SharePoint Services, such as for creating or deleting site collections.
http://server_name:5966/_vti_adm/Admin.asmx
Alerts
Methods for working with alerts for list items in a SharePoint site.
http://server_name/_vti_bin/Alerts.asmx
Data Retrieval Service
Methods for retrieving schemas and data.
http://server_name/_vti_bin/DspSts.asmx
Document Workspace
Methods for managing Document Workspace sites and the data they contain.
http://server_name/_vti_bin/DWS.asmx
Forms
Methods for returning forms used in the user interface when working with the contents of a list.
http://server_name/_vti_bin/Forms.asmx
Imaging
Methods that enable you to create and manage picture libraries.
http://server_name/_vti_bin/Imaging.asmx
Lists
Methods for working with lists and list data.
http://server_name/_vti_bin/Lists.asmx
Meetings
Methods that enable you to create and manage Meeting Workspace sites.
http://server_name/_vti_bin/Meetings.asmx
Permissions
Methods for working with Windows SharePoint Services security.
http://server_name/_vti_bin/Permissions.asmx
Site Data
Methods used by search services to extract and crawl data from SharePoint sites.
http://server_name/_vti_bin/SiteData.asmx
Sites
Methods for returning information about the collection of site templates on the virtual server.
http://server_name/_vti_bin/Sites.asmx
Users and Groups
Methods for working with users, site groups, and cross-site groups.
http://server_name/_vti_bin/UserGroup.asmx
Versions
Methods for working with file versions.
http://server_name/_vti_bin/versions.asmx
Views
Methods for working with views of lists.
http://server_name/_vti_bin/Views.asmx
Web Part Pages
Methods to send information to and retrieve information from XML Web services.
http://server_name/_vti_bin/WebPartPages.asmx
Webs
Methods for working with sites and subsites.
http://server_name/_vti_bin/Webs.asmx
Administration
Administrative methods for managing a deployment of Microsoft Windows SharePoint Services, such as for creating or deleting site collections.
http://server_name:5966/_vti_adm/Admin.asmx
Alerts
Methods for working with alerts for list items in a SharePoint site.
http://server_name/_vti_bin/Alerts.asmx
Data Retrieval Service
Methods for retrieving schemas and data.
http://server_name/_vti_bin/DspSts.asmx
Document Workspace
Methods for managing Document Workspace sites and the data they contain.
http://server_name/_vti_bin/DWS.asmx
Forms
Methods for returning forms used in the user interface when working with the contents of a list.
http://server_name/_vti_bin/Forms.asmx
Imaging
Methods that enable you to create and manage picture libraries.
http://server_name/_vti_bin/Imaging.asmx
Lists
Methods for working with lists and list data.
http://server_name/_vti_bin/Lists.asmx
Meetings
Methods that enable you to create and manage Meeting Workspace sites.
http://server_name/_vti_bin/Meetings.asmx
Permissions
Methods for working with Windows SharePoint Services security.
http://server_name/_vti_bin/Permissions.asmx
Site Data
Methods used by search services to extract and crawl data from SharePoint sites.
http://server_name/_vti_bin/SiteData.asmx
Sites
Methods for returning information about the collection of site templates on the virtual server.
http://server_name/_vti_bin/Sites.asmx
Users and Groups
Methods for working with users, site groups, and cross-site groups.
http://server_name/_vti_bin/UserGroup.asmx
Versions
Methods for working with file versions.
http://server_name/_vti_bin/versions.asmx
Views
Methods for working with views of lists.
http://server_name/_vti_bin/Views.asmx
Web Part Pages
Methods to send information to and retrieve information from XML Web services.
http://server_name/_vti_bin/WebPartPages.asmx
Webs
Methods for working with sites and subsites.
http://server_name/_vti_bin/Webs.asmx
SharePoint Products and Technologies (2003): GetUserProfileByName(String) Method
SharePoint Products and Technologies (2003) SDK Documentation
Methods
Method: GetUserProfileByName(String) Method.
The GetUserProfileByName method of the UserProfile service gets user profile property information by account name.
Parameters
Parameter: AccountName
The account name that specifies the user profile property.
Return ValueMicrosoft.SharePoint.Portal.UserProfiles.PropertyData that contains the user profile property information.
Exceptions
Exception Type: UserNotFoundException Class.
Condition: User is not found.
Requirements
Platforms: Microsoft Windows Server 2003.
Security: Code Access Security.
Methods
Method: GetUserProfileByName(String) Method.
The GetUserProfileByName method of the UserProfile service gets user profile property information by account name.
Parameters
Parameter: AccountName
The account name that specifies the user profile property.
Return ValueMicrosoft.SharePoint.Portal.UserProfiles.PropertyData that contains the user profile property information.
Exceptions
Exception Type: UserNotFoundException Class.
Condition: User is not found.
Requirements
Platforms: Microsoft Windows Server 2003.
Security: Code Access Security.
Sunday, October 01, 2006
Friday, September 29, 2006
Sharepoint revelation: it can leverage SOA, it can be a composite application
What happens when business users are demanding a single user interface? What happens when they want their data to be truly integrated and relational? What happens when all the other applications fall short?
The answer is to bring together data and functionality from other systems and create one single composite application.
Microsoft Sharepoint is a great architecture to leverage for this purpose. It offers an excellent portal and web part infrastructure. A solid authentication and security model can easily be achieved. It is easy to recover Sharepoint web applications. Sharepoint is scalable. Customizable look & feel and navigation...its there. In short, Sharepoint addresses all the aspects of web application overhead that may currently prevent you from being able to focus on and deliver those things that the business units are demanding.
Sharepoint is robust, but often times businesses require functionality that out of box web parts cannot achieve because these web parts tend to function at the "surface." In other words, unlike an off the shelf software application such as a CRM system which may store user data in a relational database, the back end data model for Sharepoint user data is relatively flat. Sure, you can create web parts to view external data from the other systems, but a lot of times business units want more than that. They want their portal to "be" the other application. This tends to be the line in the sand where many Sharepoint implementations stop. However, this boundary represents a new frontier for some. This is where you start thinking about how you can build a composite application using Sharepoint.
Building a composite application is all about breaking down functional components and being able to use them independently. For example, the act of adding a new contact record to a crm system. This is a simple, but vital action. Do you need an entire CRM application to do this? Who says you need to be in the CRM system to create contact records? Break down the programming and logic behind the act of creating a contact record, package this as a web part, and deploy it to Sharepoint. In this example you would keep your CRM system in place and extend the existing data and functionality to a Sharepoint web application by way of web parts.
On a broader scale, take a look at the various business applications in your environment and make a list of the functional components that each one is comprised of. Imagine what it would be like to have all this functionality in one single UI. The bulk of the effort to achieve this in Sharepoint is making each functional component available independently from its native software application and creating web parts for each of these components. Once you have done that you can use them througout the Sharepoint web application.
The ROI for a project such as this will be high in situations where you are buying user licenses and maintenance for your other business applications and when the users are only actually using a portion of the functionality that is being purchased. This is where a composite application project has some real value.
The answer is to bring together data and functionality from other systems and create one single composite application.
Microsoft Sharepoint is a great architecture to leverage for this purpose. It offers an excellent portal and web part infrastructure. A solid authentication and security model can easily be achieved. It is easy to recover Sharepoint web applications. Sharepoint is scalable. Customizable look & feel and navigation...its there. In short, Sharepoint addresses all the aspects of web application overhead that may currently prevent you from being able to focus on and deliver those things that the business units are demanding.
Sharepoint is robust, but often times businesses require functionality that out of box web parts cannot achieve because these web parts tend to function at the "surface." In other words, unlike an off the shelf software application such as a CRM system which may store user data in a relational database, the back end data model for Sharepoint user data is relatively flat. Sure, you can create web parts to view external data from the other systems, but a lot of times business units want more than that. They want their portal to "be" the other application. This tends to be the line in the sand where many Sharepoint implementations stop. However, this boundary represents a new frontier for some. This is where you start thinking about how you can build a composite application using Sharepoint.
Building a composite application is all about breaking down functional components and being able to use them independently. For example, the act of adding a new contact record to a crm system. This is a simple, but vital action. Do you need an entire CRM application to do this? Who says you need to be in the CRM system to create contact records? Break down the programming and logic behind the act of creating a contact record, package this as a web part, and deploy it to Sharepoint. In this example you would keep your CRM system in place and extend the existing data and functionality to a Sharepoint web application by way of web parts.
On a broader scale, take a look at the various business applications in your environment and make a list of the functional components that each one is comprised of. Imagine what it would be like to have all this functionality in one single UI. The bulk of the effort to achieve this in Sharepoint is making each functional component available independently from its native software application and creating web parts for each of these components. Once you have done that you can use them througout the Sharepoint web application.
The ROI for a project such as this will be high in situations where you are buying user licenses and maintenance for your other business applications and when the users are only actually using a portion of the functionality that is being purchased. This is where a composite application project has some real value.
Subscribe to:
Posts (Atom)
