Sunday, May 13, 2007

Instructions - WSS Server Admin Templates Downolad


Instructions

http://www.microsoft.com/downloads/details.aspx?FamilyId=AAE4CB5A-91D2-4F1B-9A45-3BB894E218F8&displaylang=en

Note: To install or remove a server admin template, you must have Administrator rights to both the Windows SharePoint Services site and to the root of the server on which it is to be installed or removed. Installation and removal are done via the Stsadm.exe command-line utility located at the following path: %PROGRAMFILES%\common files\microsoft shared\web server extensions\12\bin.

Installing a template:
  1. Before installing a server admin template, you must first install the Application Template Core solution, ApplicationTemplateCore.wsp. (Click here to download). If you have already installed this solution, proceed to Step 2.
    1. Pull the core file, ApplicationTemplateCore.wsp, from the extracted distribution. The core solution file will be added to the solution store, a table in the Windows SharePoint Services configuration store that holds solution files.
    2. Via command line, run stsadm -o addsolution -filename \ApplicationTemplateCore.wsp
    3. Next, run stsadm -o deploysolution -name ApplicationTemplateCore.wsp -allowgacdeployment
      (Additional attributes may be required based on your Windows SharePoint Services configuration. For example:
      Single Server: [ -local | -time
    4. Finally, run stsadm -o copyappbincontent
  2. Pull the solution file, .wsp, from the extracted distribution. The solution file will also be added to the solution store.
  3. Via command line, run stsadm -o addsolution -filename \.wsp
  4. Next, run stsadm -o deploysolution -name .wsp -allowgacdeployment
    (Additional attributes may be required based on your Windows SharePoint Services configuration. For example:
    Single Server: [ -local | -time
  5. To check the deployment status, browse to the WSS Central Administration site. Click the Operations tab, and then click Solution management under global configuration.
  6. After all the solutions are marked Globally Deployed, run iisreset from the command line.
Creating a site:
  1. Log into the SharePoint site as the site administrator.
  2. From the Site Actions drop-down menu in the top right, select Site Settings.
  3. Under the Site Administration section, select Sites and Workspaces.
  4. Select Create to create a new site using a site template.
  5. Complete the new SharePoint site information. In the Template Selection section, select the Application Templates tab. Any server admin templates that have been deployed will be listed here.
  6. Select the template to use for this site and click Create.
A site has now been created using the application template.

Removing a template:

This process will not remove any sites that were already created using the template. It will only prevent users from creating new sites based on the template. The Application Template Core solution must remain installed and deployed for other server admin templates to be installed.
  1. As administrator, access the server. Removal is done via the command line utility stsadm.
  2. To retract a solution from being available to SharePoint sites, run stsadm -o retractsolution -name .wsp (To see a list of optional attributes that can be added to this command, run stsadm -help retractsolution)
  3. To remove a solution from the server, run stsadm -o deletesolution -name .wsp (To see a list of optional attributes that can be added to this command, run stsadm -help deletesolution)
The application template is now unavailable to SharePoint sites and the solution has been removed from the solution store.

Top of page

Top of page

Posted by at No comments:

Sample master pages overview

http://office.microsoft.com/en-us/sharepointdesigner/HA102223711033.aspx

Sample master pages overview
In this article

What are master pages?

Master pages are a feature of ASP.NET 2.0; they work the same way in Windows SharePoint Services 3.0 and Office SharePoint Server 2007 as they do in ASP.NET 2.0. Using master pages, you can create a single page template and then use that template as the basis for multiple pages, instead of having to build each new page from scratch.

Microsoft has made available a package of four sample master page sets that were built using new CSS and Master Page editing tools within Office SharePoint Designer 2007. These sample master pages:

  • Enable you to apply a pre-designed style and layout to SharePoint sites
  • Work with the forty new Application Templates for Windows SharePoint Services 3.0
  • Provide a starting point for deeper SharePoint site look and feel customizations
  • Are available for download at no additional cost

Top of Page Top of Page

Download the sample master page package

The sample master pages provide a variety of instant styles ready to be applied to your SharePoint site. The download includes four master page sets; each set has a distinctive look and feel and comes in five color variations: blue, orange, red, purple, and green.

Download now

The four sample master page styles are:

Top of Page Top of Page

How to use the sample master pages

Master pages are applied manually after site creation; you can apply a master page to a SharePoint site either through a separate SharePoint-compatible editor such as Microsoft Office SharePoint Designer 2007, or through the Web interface of Microsoft Office SharePoint Server 2007 installations. You can also view existing master pages and upload new sets from within the SharePoint site administration.

Using Office SharePoint Designer 2007, users can:

  • Add the files to the Web site and then set the master page as default for the Web site
  • Modify the site definitions to make use of master pages
  • Create a content page from a master page

In Office SharePoint Server 2007 installations, users can:

  • Add the files to the Web site and then set the master page as default for the Web site
  • Modify the site definitions to make use of master pages
  • Create a content page from a master page

More information about using master pages:

Top of Page Top of Page

Customization

While the sample master pages are fully functional and usable out-of-the-box, they can also be custom tailored or built upon to suit your organization’s needs. This is one of the main goals of these sample master pages, to provide an example of the site-wide design and functionality control you have when applying master pages to SharePoint sites.

More information about master page customization:

Top of Page Top of Page

Compatibility and support

Compatibility with Application Templates The sample master pages were designed to be compatible with the Application Templates for Windows SharePoint Services 3.0. If used out-of-the-box, the sample master pages will work with SharePoint sites created from the application templates.

Learn more about Application Templates for Windows SharePoint Services 3.0

Compatibility with other SharePoint sites While some design and functionality features of the sample master pages may display when applied to any other SharePoint site, such as a default team site or workspace, not all site features may work properly. Customization of the sample master pages is encouraged to use them with other SharePoint sites.

Compatibility with SharePoint site themes The sample master pages are fully compatible with the “Default” SharePoint site theme; they may not render properly when other themes are applied.

Support The four example master pages are not supported by Microsoft. They are intended to provide an example of what can be done with master page support in Office SharePoint Designer 2007 and the Application Templates for Windows SharePoint Services 3.0.

Posted by at No comments:

Customize the Display of Quick Launch

http://msdn2.microsoft.com/en-us/library/ms466994.aspx

Customize the Display of Quick Launch

You can modify the display of Quick Launch by modifying attributes of the navigation control specified in the default.master file of the deployment (Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\GLOBAL). The default.master file is the Windows SharePoint Services master page that contains templates for site page layout, including the template for the left navigational area used in SharePoint pages.

The master page includes templates for two controls that by default are available for implementation on the Home page, a Microsoft.SharePoint.WebControls.Menu control, which displays the standard Quick Launch view used in the left navigational area, and a Microsoft.SharePoint.WebControls.SPTreeView control, which displays a site folder view. You can select which view to display on site pages through the user interface.

To select which left navigational control to display on site pages

  1. Click Site Actions and on the Site Settings page in the Look and Feel section, click Tree view.

  2. Select Enable Quick Launch to display the Quick Launch view, or select Enable Tree View to display a folder view.

    As an example of a customization that you can make to left navigation, you can collapse Quick Launch and add fly-out menus to the view by setting attributes on the Menu control. This kind of customization requires that you either customize the originally installed default.master file through a SharePoint-compatible editing application such as Microsoft Office SharePoint Designer 2007, or that you create a custom .master file and use the Windows SharePoint Services object model to point a site to the new file.

To use SharePoint Designer to modify the default.master file instance in the site's Master Page Gallery to display a collapsed view with fly-out menus

  1. Click Site Actions, click Site Settings, and then in the Galleries section of the Site Settings page, click Master pages.

  2. On the Master Page Gallery page, click Edit in Microsoft Office SharePoint Designer on the drop-down menu.

  3. In Code view, find the ContentPlaceHolder container control whose ID is PlaceHolderLeftNavBar. Within the PlaceHolderLeftNavBar control, find the AspMenu control whose ID is QuickLaunchMenu.

  4. Set both the StaticDisplayLevels and MaximumDynamicDisplayLevels values of the Menu control to 1, as follows:

     id="QuickLaunchMenu"
     DataSourceId="QuickLaunchSiteMap"
     runat="server"
     Orientation="Vertical"
     StaticDisplayLevels="1"
     ItemWrap="true"
     MaximumDynamicDisplayLevels="1"
     StaticSubMenuIndent="0"
     SkipLinkText=""
    >

  5. Save the file and open a site page to see the results of your changes.

To display a collapsed view with fly-out menus by creating a custom .master file and using the SharePoint object model

  1. Copy the default.master file in the \12\TEMPLATE\GLOBAL folder and rename it, for example, myDefault.master.

  2. Open your new myDefault.master file and find the ContentPlaceHolder container control whose ID is PlaceHolderLeftNavBar.

  3. In the PlaceHolderLeftNavBar control, find the AspMenu control whose ID is QuickLaunchMenu, and then set both the StaticDisplayLevels and MaximumDynamicDisplayLevels values to 1, as follows:

     id="QuickLaunchMenu"
     DataSourceId="QuickLaunchSiteMap"
     runat="server"
     Orientation="Vertical"
     StaticDisplayLevels="1"
     ItemWrap="true"
     MaximumDynamicDisplayLevels="1"
     StaticSubMenuIndent="0"
     SkipLinkText=""
    >

  4. Create a Web site in Microsoft Visual Studio and use the Microsoft.SharePoint.SPWeb.MasterUrl property to point the site to the custom .master file, as shown in the following example.

    C#
    SPWeb subSite = SPControl.GetContextWeb(Context);
    subSite.MasterUrl = "/Site/SubSite/_catalogs/masterpage/myDefault.master";

    To run this example, you must add a Microsoft.SharePoint.WebControls.FormDigest control to the page making the post. For information about how to add a FormDigest control, see Security Validation and Making Posts to Update Data. The example also requires referencing and importing the Microsoft.SharePoint and Microsoft.SharePoint.WebControls namespaces. For basic information about how to create a Web application that runs in the context of Windows SharePoint Services, see How to: Create a Web Application in a SharePoint Web Site.

  5. Reset IIS for your changes to take effect and navigate to a site page to see the results of your changes.

Replacing the Menu Control with the TreeView Control

You can replace the AspMenu control with a SPTreeView control to display a familiar tree view with nodes that collapse and expand.

To replace the Menu control with the TreeView control

  1. Open the myDefault.master file you created in the previous procedure and find the ContentPlaceHolder container control whose ID is PlaceHolderLeftNavBar.

  2. In the AspMenu control, find the PlaceHolderLeftNavBar control whose ID is QuickLaunchMenu, and replace SharePoint:AspMenu with SharePoint:SPTreeView in both the opening and closing tags.

  3. Remove the following LevelMenuItemStyles element and its contents from the new SPTreeView element.

  4. Reset IIS for changes to take effect.

    The SPTreeView control provides properties that allow you to easily customize the control. For more information about Windows SharePoint Services master pages and site customization, see Master Pages.

See Also

Concepts

Custom Navigation and New User Interface Elements
Customizing Quick Launch and the Top Link Bar Through the User Interface
How to: Share the Top Link Bar Between Sites
Adding Links through the Object Model
Using a Custom Data Source for Navigation
Posted by at No comments:

Windows SharePoint Services Default Master Pages


http://msdn2.microsoft.com/en-us/library/ms467402.aspx

Windows SharePoint Services Default Master Pages

Windows SharePoint Services pages that end users can customize—list view pages, list form pages, and Web Part Pages—are content pages that contain the content to display. When a user requests a content page, it is merged with a master page to produce output that combines the layout of the master page with the content from the content page.

All content pages share the same page structure—the global breadcrumb, site title area, top navigation, page title area, and left navigation bar. In Windows SharePoint Services, this shared page structure is moved into a master page called default.master, which is used by all content pages, including the following:

  • default.aspx

  • AllItems.aspx, DispForm.aspx, NewForm.aspx, and EditForm.aspx: for all lists

  • Upload.aspx and Webfldr.aspx: for all document libraries

  • Any new content pages that are created in this site

At installation, default.master is located at <%System Drive%>Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\GLOBAL. As long as this master page is not customized, its page definition is cached on the front-end Web server and shared across sites. If the master page definition inside of default.master is subsequently edited for a particular Windows SharePoint Services site, an edited copy of the master page file is then stored in the content database.

The standard set of content pages all use the default master page and are initially located in the file system, in the same directory area as the rest of the template pages. For example, in the case of a SharePoint team site, default.aspx is stored at <%SystemDrive%>\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\SiteTemplates\STS, while form pages such editform.aspx are stored in their respective <%SystemDrive%>\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\Features folder. After a content page is customized, it is stored in the content database.

Content Placeholders Defined in default.master

In addition to static text and controls that appear on all pages, a master page also includes one or more System.Web.UI.WebControls.ContentPlaceHolder controls, which define regions where replaceable content can appear. In turn, the replaceable content is defined in content pages.

The Windows SharePoint Services default master page contains several ContentPlaceHolder controls to enable easy customization to an individual content page. By default, Windows SharePoint Services content pages use the content placeholders described in the following table. When creating custom master pages, developers must use the same set of content placeholders, or a superset of these placeholders; otherwise, their pages may fail to render.

The following table describes the content placeholders contained in the Windows SharePoint Services default master page and what each of the placeholders represents on the page.

Name of Content Placeholder

Description

PlaceHolderAdditionalPageHead

Additional content that needs to be within the "head" tag of the page, for example, references to script in style sheets

PlaceHolderBodyAreaClass

Additional body styles in the page header

PlaceHolderBodyLeftBorder

Border element for the main page body

PlaceHolderBodyRightMargin

Right margin of the main page body

PlaceHolderCalendarNavigator

Shows a date picker for navigating in a calendar when a calendar is visible on the page

PlaceHolderFormDigest

The "form digest" security control

PlaceHolderGlobalNavigation

The global navigation breadcrumb

PlaceHolderHorizontalNav

Top navigation menu for the page

PlaceHolderLeftActions

Bottom of the left navigation area

PlaceHolderLeftNavBar

Left navigation area

PlaceHolderLeftNavBarBorder

Border element on the left navigation bar

PlaceHolderLeftNavBarDataSource

Data source for the left navigation menu

PlaceHolderLeftNavBarTop

Top of the left navigation area

PlaceHolderMain

Page's main content

PlaceHolderMiniConsole

A place to show page-level commands, for example, WIKI commands such as Edit Page, History, and Incoming Links

PlaceHolderNavSpacer

The width of the left navigation area

PlaceHolderPageDescription

Description of the page contents

PlaceHolderPageImage

Page icon in the upper left area of the page

PlaceHolderPageTitle

The page "title" that is shown in the browser’s title bar

PlaceHolderSearchArea

Search box area

PlaceHolderSiteName

Site name

PlaceHolderTitleAreaClass

Additional styles in the page header

PlaceHolderTitleAreaSeparator

Shows shadows for the title area

PlaceHolderTitleBreadcrumb

Main content breadcrumb area

PlaceHolderTitleInTitleArea

Page title shown immediately below the breadcrumb

PlaceHolderTitleLeftBorder

Left border of the title area

PlaceHolderTitleRightMargin

Right margin of the title area

PlaceHolderTopNavBar

Top navigation area

PlaceHolderUtilityContent

Extra content that needs to be at the bottom of the page

SPNavigation

Empty by default in Windows SharePoint Services. Can be used for additional page editing controls.

WSSDesignConsole

The page editing controls when the page is in Edit Page mode (after clicking Site Actions, then Edit Page)

See Also

Tasks

How to: Customize the Display of Quick Launch

Concepts

Customizing Master Pages in Windows SharePoint Services
Posted by at No comments:

Saturday, December 16, 2006



Solutions Whether you are involved in AEC, government, education, manufacturing or professional services, Infooptima has the expertise and experience which will enable you to be productive in a very short time. Our solutions allow users to interactively analyze information with colleagues in multiple locations, manipulate data locally and publish it providing global access using a variety of integrated tools.

Company Intranet & Extranet
Reduced costs and increased productivity are just two of the many benefits realized by a well-designed SharePoint implementation. Infooptima leverages our team's industry experience to design the right solution. From initial analysis through development, deployment and training, we call on our expertise and past experiences to produce a solution that delivers results.

Our Portal Solutions Offer:

• Internal and External access
• Branded Customizations
• Department Sites
• Project Sites
• Human Resources Areas
• RFP Management & Collaboration
• Enterprise Search
• Plan Room Capabilities
• Improved Navigation
• Simplified Administration
• Custom Templates

•Rapid Deployment Configuration VIEW DEMO
2-3 Days proof of Concept

Projects at the Center
Project managers, technical consultants, executives, subcontractors, and other personnel all need access to different sets of job-related information, which are often spread across disconnected applications, spreadsheets, and paper files. Providing project-centric access to this information increases the sharing of accurate, timely project information, increasing process standardization and reducing errors caused by incomplete or outdated information.


Document Solutions
The sheer volume of files and paper associated within an organization or job can be an indicator that systems are not integrated or are not meeting the needs of all team members.

Infooptima has developed document management solutions that reduces paper and makes information readily available. In place of looking endlessly through a filing cabinet for customer related documents, you can search the portal for the specific content.

We have developed document management solutions that truly reduce paper, and make the information usable. From a few documents a day to large-scale scanning projects, we will work with you to develop a custom solution based on your document volume.

Performance Indicators
Immediate information on how an organization is performing can be imperative to maintaining a competitive edge. Our executive dashboards give a quick, graphical view into the current health of the organization by providing bullet point information extracted from a third-party database you are currently running.

Infooptima can connect to virtually any third-party database application, pulling out the vital information and presenting it in a very clear manner. We are especially adept in accessing Deltek, one of the leading business accounting packages. From time management and productivity to revenue and expense reporting, we allow users to select the data they want to monitor and set thresholds to trigger alerts. Every executive can have his own reporting tools - surprises are eliminated and a change can be made from reactive management to proactive management.

Drawing Tools
Infooptima is an official reseller of Brava!® Enterprise which provides secure content visualization and annotation for your intranet or extranet. Store, view, markup and collaborate around drawings and other supported files reducing AutoCAD and other client application and licensing expenses.

SharePoint provides anywhere access to the tools you need most with quick rendering speeds and browser based functionality. Seemless integration with SharePoint means enterprise content management & project management honoring user rights, leveraging metadata, and managing annotations. It can easily handle the load demands of large, enterprise-wide deployments that scale out.

Key Features

• Easy to use markup, annotation and redaction
• Opens many formats DWG, Publish to TIFF, PDF and secure CSF
• Manipulate Layers
• Fast and accurate view/print...more

Industry Deployments
• Construction
• Finance/Insurance
• Legal
• Manufacturing
• Government
• Life Sciences




Posted by at No comments:

J.O's SharePoint Links

http://blogs.msdn.com/joelo/archive/tags/Upgrade/default.aspx

Posted by at No comments:

WSS resources


Izhodišče:

MOSS trial 2007
http://www.microsoft.com/downloads/details.aspx?FamilyID=2e6e5a9c-ebf6-4f7f-8467-f4de6bd6b831&displaylang=en

Windows SharePoint Services 3.0: Software Development Kit

http://www.microsoft.com/downloads/details.aspx?familyid=05E0DD12-8394-402B-8936-A07FE8AFAFFD&displaylang=en

Windows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions

http://www.microsoft.com/downloads/details.aspx?familyid=19F21E5E-B715-4F0C-B959-8C6DCBDC1057&displaylang=en
Posted by at No comments:
Subscribe to: Posts (Atom)