Here is the screen shot!
Wednesday, January 14, 2009
How to find the list of sql server 2005 instances running in a server box
The list of running sql 2k5 running in a server box is made visible by making use of SQL Server Surface Area Configuration Tool.
Here is the screen shot!
Here is the screen shot!
Create and deploy a Custom Feature in Office SharePoint Server 2007
Features are a major enhancement to the template framework of MOSS 2007. It allows you to develop, test, deploy and activate custom functionality in your MOSS environment and provides a way to make the functionality available across your server farm. Examples of features are custom workflows, content types, templates of lists and libraries, etc.
Features are typically stored on the SharePoint server at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES. Each features has its own folder and contains a header file called Feature.XML.
The Feature.XML points to a manifest that tells SharePoint where to find the code and XML that defines the feature. It contains the location of assemblies, files, dependencies or properties that support feature. Optionally, the Feature element may point to an XML file that contains an Element which defines the components and types that make up the Feature.
Creating Your Own Custom Feature
For example, i want to create a content type for lists that defines columns for storing informations about RFQ (Request For Quote).
The columns are
-RFQ No.
-Purchase Order No.
-Description
-Vendor
-RFQ Close Date
Although we can create a list template and use it inside the site, creating this content type as a Feature allows Site Administrators to make the type available to all sites in the server farm without adding the content type manually.
To create the list column definition file
1. Create a folder called fieldsRFQ to hold the files defining the feature and elements.
2. Then create the XML file inside the folder that contains the list column definitions. An easy way is duplicate the column definition file of SharePoint itself, which is located at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES. You can copy the folder C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\fields and rename it with the new name. The folder contains two xml files, feature.xml and fieldswss.xml. I have copied and duplicated the folder with the new name "RFQColumns" and rename the file inside the folder fieldswss.xml as "fieldsrfq.xml.
3. Here is my fieldsrfq.xml, the element file that defines the columns. I have modified the copied file by defining my own column definitions.
<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<Field ID="{2ABC0796-E9B5-4288-B8D9-F1A66B87E61C}"
Name="RFQNo"
SourceID="http://schemas.microsoft.com/sharepoint/v3"
StaticName="RFQNo"
Group="RFQ Content Type"
RowOrdinal="0"
Type="Text"
Hidden="FALSE"
DisplayName="RFQ No.">
</Field>
<Field ID="{10F319FD-87EA-413a-9C00-A8EAE1C7E3E3}"
Name="PONo"
SourceID="http://schemas.microsoft.com/sharepoint/v3"
StaticName="PONo"
Group="RFQ Content Type"
RowOrdinal="1"
Type="Text"
Hidden="FALSE"
DisplayName="Purchase Order No.">
</Field>
<Field ID="{DDD9DA23-DFE5-4de6-9D12-5231A8499998}"
Name="Description"
SourceID="http://schemas.microsoft.com/sharepoint/v3"
StaticName="Description"
Group="RFQ Content Type"
RowOrdinal="2"
Type="Text"
Hidden="FALSE"
DisplayName="Description">
</Field>
<Field ID="{0844729B-2146-4593-844E-DB5762BAEAC1}"
Name="Vendor"
SourceID="http://schemas.microsoft.com/sharepoint/v3"
StaticName="Vendor"
Group="RFQ Content Type"
RowOrdinal="3"
Type="Text"
Hidden="FALSE"
DisplayName="Vendor">
</Field>
<Field ID="{AFF26D81-88F9-433b-ACCE-F0C836F62698}"
Name="RFQCloseDate"
SourceID="http://schemas.microsoft.com/sharepoint/v3"
StaticName="RFQCloseDate"
Group="RFQ Content Type"
RowOrdinal="4"
Type="Text"
Hidden="FALSE"
DisplayName="RFQ Close Date">
</Field>
</Elements>
All the attributes in the above file is self explanatory. You have to map the sharepoint native columns against your each columns in the list.
4. Next step is to finalize the feature.xml file and paste it inside the fieldsRFQ folder. The feature XML file will look like this after the moficitation.
<?xml version="1.0" encoding="utf-8"?>
<Feature Id="3313208E-36E6-481e-BCE8-96CA777FF5F1"
Title="Request For Quote (RFQ) Columns"
Description="Installs columns designed to manage RFQ data."
Version="12.0.0.0"
Hidden="FALSE"
Scope="Site"
DefaultResourceFile="core"
xmlns="http://schemas.microsoft.com/sharepoint/">
<ElementManifests>
<ElementManifest Location="fieldsrfq.xml"/>
</ElementManifests>
</Feature>
The following metadata is contained in the element in this XML file.
ID: The GUID that uniquely identifies the Feature. This value must be unique across the server farm. The easiest way to create a GUID is with the guidgen.exe utility that comes with Microsoft Visual Studio.
Title: The name of the Feature. In an actual scenario, you will see the name of the Feature displayed on the Site Features web page inside the Site Settings section for a given SharePoint site.
Description: The description of the Feature.
Version: The version of the Feature. This value can be incremented for successive versions of the Feature.
Scope:Web or Site are the typical values. The scope defines the context in which the Feature can be activated or deactivated. Setting the scope equal to Web means that the Feature can be activated or deactivated within the context of the site. A setting of Site means that the Feature can be activated or deactivated within the scope of a site collection. The scope is set to the site collection displayed to the administrator in the Site Collection Features page. There are also WebApplication and Farm values.
Hidden:TRUE or FALSE are allowable values here. This setting specifies if the Feature is visible in the list of Features on the Site Features web page. Setting the attribute to TRUE makes the Feature visible to users who want to activate it. Hidden Features must be activated either from the command line, in custom code, or through the dependency of another Feature.
DefaultResourceFile: Specifies the central location for settings and other items that may change frequently.
ImageUrl: Points to an image file that will be displayed next to the Feature in the user interface.
element : The container element for elements
element : Contains the location of the manifest file that contains the different elements that this Feature implements. The path to sub-directories and files is a relative path.
5. Now that defining the site columns for the Feature is completed, you need to create 2 files for the Feature content types that specify the components of the Feature. Create a new folder in "ctypesRFQ" folder in the path C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES. You can create the ctype.xml by duplicating the file ctypeswss.xml from C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\ctypes and the feature.xml file format remains the same. Here is my ctypeRFQ.xml.
<?xml version="1.0" encoding="utf-8" ?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<ContentType ID="0x01001EF379E5-F202-434f-8DA6-3401E94E291E"
Name="RFQ Content Type"
Group="RFQs"
Description="Designed to facilitate the storage of RFQ information."
Version="0">
<FieldRefs>
<FieldRef ID="{2ABC0796-E9B5-4288-B8D9-F1A66B87E61C}" Name="RFQNo" />
<FieldRef ID="{10F319FD-87EA-413a-9C00-A8EAE1C7E3E3}" Name="PONo" />
<FieldRef ID="{DDD9DA23-DFE5-4de6-9D12-5231A8499998}" Name="Description" />
<FieldRef ID="{0844729B-2146-4593-844E-DB5762BAEAC1}" Name="Vendor" />
<FieldRef ID="{AFF26D81-88F9-433b-ACCE-F0C836F62698}" Name="RFQCloseDate" />
</FieldRefs>
</ContentType>
</Elements>
The above ctypeRFQ.xml file details the fields with GUID of the content type involved.
6. Create another file called feature.xml inside the folder ctypesRFQ and paste the code below. Please note the format is similiar to one we created before. A new GUID has to be created for the ID attribute in the file below. Also add the feature id of the content type
(one created before) in the tag as below.
<?xml version="1.0" encoding="utf-8" ?>
<Feature Id="060EB007-9D6C-40c5-ABBE-901171CD04FF"
Title="RFQ Data Content Types"
Description="Installs content types designed to manage information about RFQ."
Version="12.0.0.0"
Hidden="FALSE"
Scope="Site"
DefaultResourceFile="core"
xmlns="http://schemas.microsoft.com/sharepoint/">
<ElementManifests>
<ElementManifest Location="ctypesRFQ.xml" />
</ElementManifests>
<ActivationDependencies>
<!-- Installs the site columns that hold RFQ data -->
<ActivationDependency FeatureId="3313208E-36E6-481e-BCE8-96CA777FF5F1"/>
</ActivationDependencies>
</Feature>
7. Now we are good to go for feature deployment. Open command prompt and type cd "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN". Now execute the command in below sequence,
a) stsadm –o installfeature –filename fieldsRFQ\feature.xml
b) stsadm –o installfeature –filename ctypesRFQ\feature.xml
8. Now the feature is implemented. Next step is to activate the feature. Execute the following command in sequence below (in the same location)
a) stsadm –o activatefeature –name fieldsRFQ -url "http:\\localhost"
b) stsadm –o activatefeature –name ctypesRFQ -url "http:\\localhost"
where the URL http://localhost should be the top level site collection url where you want to deploy the feature
9. Restart the IIS
Features are typically stored on the SharePoint server at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES. Each features has its own folder and contains a header file called Feature.XML.
The Feature.XML points to a manifest that tells SharePoint where to find the code and XML that defines the feature. It contains the location of assemblies, files, dependencies or properties that support feature. Optionally, the Feature element may point to an XML file that contains an Element which defines the components and types that make up the Feature.
Creating Your Own Custom Feature
For example, i want to create a content type for lists that defines columns for storing informations about RFQ (Request For Quote).
The columns are
-RFQ No.
-Purchase Order No.
-Description
-Vendor
-RFQ Close Date
Although we can create a list template and use it inside the site, creating this content type as a Feature allows Site Administrators to make the type available to all sites in the server farm without adding the content type manually.
To create the list column definition file
1. Create a folder called fieldsRFQ to hold the files defining the feature and elements.
2. Then create the XML file inside the folder that contains the list column definitions. An easy way is duplicate the column definition file of SharePoint itself, which is located at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES. You can copy the folder C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\fields and rename it with the new name. The folder contains two xml files, feature.xml and fieldswss.xml. I have copied and duplicated the folder with the new name "RFQColumns" and rename the file inside the folder fieldswss.xml as "fieldsrfq.xml.
3. Here is my fieldsrfq.xml, the element file that defines the columns. I have modified the copied file by defining my own column definitions.
<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<Field ID="{2ABC0796-E9B5-4288-B8D9-F1A66B87E61C}"
Name="RFQNo"
SourceID="http://schemas.microsoft.com/sharepoint/v3"
StaticName="RFQNo"
Group="RFQ Content Type"
RowOrdinal="0"
Type="Text"
Hidden="FALSE"
DisplayName="RFQ No.">
</Field>
<Field ID="{10F319FD-87EA-413a-9C00-A8EAE1C7E3E3}"
Name="PONo"
SourceID="http://schemas.microsoft.com/sharepoint/v3"
StaticName="PONo"
Group="RFQ Content Type"
RowOrdinal="1"
Type="Text"
Hidden="FALSE"
DisplayName="Purchase Order No.">
</Field>
<Field ID="{DDD9DA23-DFE5-4de6-9D12-5231A8499998}"
Name="Description"
SourceID="http://schemas.microsoft.com/sharepoint/v3"
StaticName="Description"
Group="RFQ Content Type"
RowOrdinal="2"
Type="Text"
Hidden="FALSE"
DisplayName="Description">
</Field>
<Field ID="{0844729B-2146-4593-844E-DB5762BAEAC1}"
Name="Vendor"
SourceID="http://schemas.microsoft.com/sharepoint/v3"
StaticName="Vendor"
Group="RFQ Content Type"
RowOrdinal="3"
Type="Text"
Hidden="FALSE"
DisplayName="Vendor">
</Field>
<Field ID="{AFF26D81-88F9-433b-ACCE-F0C836F62698}"
Name="RFQCloseDate"
SourceID="http://schemas.microsoft.com/sharepoint/v3"
StaticName="RFQCloseDate"
Group="RFQ Content Type"
RowOrdinal="4"
Type="Text"
Hidden="FALSE"
DisplayName="RFQ Close Date">
</Field>
</Elements>
All the attributes in the above file is self explanatory. You have to map the sharepoint native columns against your each columns in the list.
4. Next step is to finalize the feature.xml file and paste it inside the fieldsRFQ folder. The feature XML file will look like this after the moficitation.
<?xml version="1.0" encoding="utf-8"?>
<Feature Id="3313208E-36E6-481e-BCE8-96CA777FF5F1"
Title="Request For Quote (RFQ) Columns"
Description="Installs columns designed to manage RFQ data."
Version="12.0.0.0"
Hidden="FALSE"
Scope="Site"
DefaultResourceFile="core"
xmlns="http://schemas.microsoft.com/sharepoint/">
<ElementManifests>
<ElementManifest Location="fieldsrfq.xml"/>
</ElementManifests>
</Feature>
The following metadata is contained in the
ID: The GUID that uniquely identifies the Feature. This value must be unique across the server farm. The easiest way to create a GUID is with the guidgen.exe utility that comes with Microsoft Visual Studio.
Title: The name of the Feature. In an actual scenario, you will see the name of the Feature displayed on the Site Features web page inside the Site Settings section for a given SharePoint site.
Description: The description of the Feature.
Version: The version of the Feature. This value can be incremented for successive versions of the Feature.
Scope:Web or Site are the typical values. The scope defines the context in which the Feature can be activated or deactivated. Setting the scope equal to Web means that the Feature can be activated or deactivated within the context of the site. A setting of Site means that the Feature can be activated or deactivated within the scope of a site collection. The scope is set to the site collection displayed to the administrator in the Site Collection Features page. There are also WebApplication and Farm values.
Hidden:TRUE or FALSE are allowable values here. This setting specifies if the Feature is visible in the list of Features on the Site Features web page. Setting the attribute to TRUE makes the Feature visible to users who want to activate it. Hidden Features must be activated either from the command line, in custom code, or through the dependency of another Feature.
DefaultResourceFile: Specifies the central location for settings and other items that may change frequently.
ImageUrl: Points to an image file that will be displayed next to the Feature in the user interface.
5. Now that defining the site columns for the Feature is completed, you need to create 2 files for the Feature content types that specify the components of the Feature. Create a new folder in "ctypesRFQ" folder in the path C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES. You can create the ctype.xml by duplicating the file ctypeswss.xml from C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\ctypes and the feature.xml file format remains the same. Here is my ctypeRFQ.xml.
<?xml version="1.0" encoding="utf-8" ?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<ContentType ID="0x01001EF379E5-F202-434f-8DA6-3401E94E291E"
Name="RFQ Content Type"
Group="RFQs"
Description="Designed to facilitate the storage of RFQ information."
Version="0">
<FieldRefs>
<FieldRef ID="{2ABC0796-E9B5-4288-B8D9-F1A66B87E61C}" Name="RFQNo" />
<FieldRef ID="{10F319FD-87EA-413a-9C00-A8EAE1C7E3E3}" Name="PONo" />
<FieldRef ID="{DDD9DA23-DFE5-4de6-9D12-5231A8499998}" Name="Description" />
<FieldRef ID="{0844729B-2146-4593-844E-DB5762BAEAC1}" Name="Vendor" />
<FieldRef ID="{AFF26D81-88F9-433b-ACCE-F0C836F62698}" Name="RFQCloseDate" />
</FieldRefs>
</ContentType>
</Elements>
The above ctypeRFQ.xml file details the fields with GUID of the content type involved.
6. Create another file called feature.xml inside the folder ctypesRFQ and paste the code below. Please note the format is similiar to one we created before. A new GUID has to be created for the ID attribute in the file below. Also add the feature id of the content type
(one created before) in the
<?xml version="1.0" encoding="utf-8" ?>
<Feature Id="060EB007-9D6C-40c5-ABBE-901171CD04FF"
Title="RFQ Data Content Types"
Description="Installs content types designed to manage information about RFQ."
Version="12.0.0.0"
Hidden="FALSE"
Scope="Site"
DefaultResourceFile="core"
xmlns="http://schemas.microsoft.com/sharepoint/">
<ElementManifests>
<ElementManifest Location="ctypesRFQ.xml" />
</ElementManifests>
<ActivationDependencies>
<!-- Installs the site columns that hold RFQ data -->
<ActivationDependency FeatureId="3313208E-36E6-481e-BCE8-96CA777FF5F1"/>
</ActivationDependencies>
</Feature>
7. Now we are good to go for feature deployment. Open command prompt and type cd "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN". Now execute the command in below sequence,
a) stsadm –o installfeature –filename fieldsRFQ\feature.xml
b) stsadm –o installfeature –filename ctypesRFQ\feature.xml
8. Now the feature is implemented. Next step is to activate the feature. Execute the following command in sequence below (in the same location)
a) stsadm –o activatefeature –name fieldsRFQ -url "http:\\localhost"
b) stsadm –o activatefeature –name ctypesRFQ -url "http:\\localhost"
where the URL http://localhost should be the top level site collection url where you want to deploy the feature
9. Restart the IIS
Tuesday, January 13, 2009
Value does not fall within the expected range while activating feature in MOSS using stsadm tool
While i tried to implement a custom feature in MOSS, i ended up with the error message "Value does not fall within the expected range".
What has happened is i tried the implementation of feature in wrong sequence, and i received message saying the dependendent feature has to be activated first. Thereafter i activated the other one and then tried this later and got the above message.
The solution use the argument -force. And i beleive that the initial activate attempt haults the process halfway and hence we need to force the activation process.
Here is the full command
ststadm.exe -o activatefeature -filename\feature.xml -url "http://localhost" -force
That s it !
What has happened is i tried the implementation of feature in wrong sequence, and i received message saying the dependendent feature has to be activated first. Thereafter i activated the other one and then tried this later and got the above message.
The solution use the argument -force. And i beleive that the initial activate attempt haults the process halfway and hence we need to force the activation process.
Here is the full command
ststadm.exe -o activatefeature -filename
That s it !
Site Columns in Microsft Office SharePoint Server 2007 (MOSS 2007)
Site Column is one of the new features in the new version of SharePoint, MOSS 2007.
A Site Column (SC) is a reusable column definition that can be used in multiple lists across multiple SharePoint sites. This will be required when the organization need to have a consistent site design or components across the lists and libraries. SCs are attached to native column types which are made available in WSS 3.0
For instance, if your organization had a vendor site collection build on MOSS, then all the sub sites would have a common skeleton (data structures in libraries and lists) to capture the data. Defining a site column at the top level will help you to reuse the same columns across mutiple sites within the site collection. Eg:- RFQ (Request For Quote) document library in the vendor subsite in the above site collection . You can defined the columns required to capture the RFQ data and make use of those columns in all subsequent sites.
Again, after creating the site column in the top level site and leveraging it in the site columns in sub sites, any change in the definition of the site column can be reflected in all the sub sites. That is, if you make changes to a site column, you can update all the list columns based on that template. This is done by pushing down the changes you made to the site column. Pushing down is not an all-or-nothing operation: if the push down of changes fails on one list, Windows SharePoint Services continues pushing down the changes to the remaining lists. Windows SharePoint Services returns a list of errors encountered at the end of the push-down operation.
However, deletion of site column will not delete the columns from the lists where it has beeen used.
In other words, SC can be compared to the User Defined Data Types (UDT) in sql server. In SQL, the UDTs are built on native data types available in the server, say int, money, varchar, etc. Similiar to that, SC is built on native column types available in Windows SharePoint Services 3.0.
A Site Column (SC) is a reusable column definition that can be used in multiple lists across multiple SharePoint sites. This will be required when the organization need to have a consistent site design or components across the lists and libraries. SCs are attached to native column types which are made available in WSS 3.0
For instance, if your organization had a vendor site collection build on MOSS, then all the sub sites would have a common skeleton (data structures in libraries and lists) to capture the data. Defining a site column at the top level will help you to reuse the same columns across mutiple sites within the site collection. Eg:- RFQ (Request For Quote) document library in the vendor subsite in the above site collection . You can defined the columns required to capture the RFQ data and make use of those columns in all subsequent sites.
Again, after creating the site column in the top level site and leveraging it in the site columns in sub sites, any change in the definition of the site column can be reflected in all the sub sites. That is, if you make changes to a site column, you can update all the list columns based on that template. This is done by pushing down the changes you made to the site column. Pushing down is not an all-or-nothing operation: if the push down of changes fails on one list, Windows SharePoint Services continues pushing down the changes to the remaining lists. Windows SharePoint Services returns a list of errors encountered at the end of the push-down operation.
However, deletion of site column will not delete the columns from the lists where it has beeen used.
In other words, SC can be compared to the User Defined Data Types (UDT) in sql server. In SQL, the UDTs are built on native data types available in the server, say int, money, varchar, etc. Similiar to that, SC is built on native column types available in Windows SharePoint Services 3.0.
Wednesday, January 7, 2009
List of public sites built on MOSS2007
Living Prototypes
OBS
SharePoint Solutions/
Tourism Western Australia
Microsoft Flight Simulator Insider
Architecture Forum (Australia) South East Water Limited (by SDM) LivePoint (Partner)
EchoTechnology (by LivePoint)
Migros Glu Mobile Games Virtual TechEd 2007
Alphamosaik (Partner - France, Multilingual)
HedKandi
ShareView.co.uk
CORGI (UK)
speakTECH
Paul Mitchell
Tyler Butler
Microsoft-Oracle
ThreeWill
EmpowerID Demo
Oasys (French)
InfoCision
Ruijin Hospital Group
UCB (Une societe de BNP PARIBAS) Satama Reveu-d-Etudes (French)
Formextern (French) Cegos (Professional Services) (French)
Sharesquared FIFTEEN Guildford Grammar School website by Vivid Group, the first MOSS 2007 site to go live in Australia!
Australian Innovation (2007 Innovation Festival) by Eclipse Group
JTC Corporation (Singapore Government)
APAC SharePoint Conference 2007 by Microsoft Australia and Unique World
AATorque (New Zealand bro)
Wise Woman by CodeAndContent
Komatsu (by UniqueWorld)
Ditributed Logic Platform (Partner)
MyTalk (Southern Cross by HotHouse)
Hawaiin Air
Performance Food Group (by Dominion Digital)
Plymouth Hospitals NHS Trust (AA Compliant)
Direct Energy
McGrathNicol (by Dimension Data)
cScape Games for Windows
WesternAustralia.com
Subscribe to:
Posts (Atom)