MOSS 2007 Application Development Certification preparation - PowerPoint PPT Presentation

Loading...

PPT – MOSS 2007 Application Development Certification preparation PowerPoint presentation | free to download - id: 523c29-YjU4M



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

MOSS 2007 Application Development Certification preparation

Description:

By: Usman Zafar Malik [MCTS : Microsoft Office SharePoint Server 2007] Indicator using data in SharePoint list A SharePoint list that contains items from which you ... – PowerPoint PPT presentation

Number of Views:65
Avg rating:3.0/5.0
Slides: 99
Provided by: UsmanZaf
Learn more at: http://usmanzafarmalik.files.wordpress.com
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: MOSS 2007 Application Development Certification preparation


1
MOSS 2007 Application Development Certification
preparation
  • By Usman Zafar Malik
  • MCTS Microsoft Office SharePoint Server 2007

2
Agenda
  • Policy
  • Auditing
  • Creating Business Intelligence(BI) Solutions by
    using MOSS
  • Working with KPIs

3
Policy
  • What is the Policy?
  • Policy Architecture.
  • How to define Policy?
  • How to implement the Policy by using Code?

4
What is the Policy?
  • Policy is a collection of instruction sets for
    one or more policy features.
  • Each policy feature provides a specific kind of
    content management functionality.
  • You can assign a policy to either a content type
    or a list.

5
Policy architecture
6
Policy Item
  • Each policy feature that you want to include in a
    policy, you include an instruction set, called a
    policy item, in the policy.
  • Policy item is an XML node within a policy that
    contains the settings for only one policy
    feature, includes like ID, NAME of Policy Feature.

7
Policy Feature
  • A policy feature is an assembly that provides
    some content management functionality to Office
    SharePoint Server 2007.
  • You can include the same policy feature in
    multiple policies.
  • A policy feature can use one or more policy
    resources
  • Example Audit. Expiration ,Labels, Bar Codes

8
Policy Resource
  • A policy resource is an assembly that assists the
    policy feature by providing some functionality
    the feature needs.
  • For example, the Bar Code policy feature uses a
    Bar Code Provider, which generates the bar codes,
    as a policy resource.
  • Expiration policy feature applies an Expiration
    Formula Calculator as a policy resource to
    determine a document's actual expiration date.
    Policy feature also uses an Expiration Action
    policy resource to determine what action to take
    when an item reaches its expiration date.
  • Policy Resources are not shared between Policy
    Features.

9
How to define policy?
  • Implement Interface IPolicyFeature .
  • Reference
  • Microsoft.Office.Policy.dll
  • NameSpace
  • Microsoft.Office.RecordsManagement.InformationPoli
    cy
  • Include these methods
  • OnCustomDataChange
  • OnGlobalCustomDataChange
  • ProcessListItem
  • ProcessListItemOnRemove
  • Register
  • UnRegister

10
Create policy Manifest
  • lt?xml version"1.0" encoding"utf-8" ?gt
  • ltpPolicyFeature id"TST.POC.PolicyFeatures.Policy
    OfTruth"
  •     xmlnsp"urnschemas-microsoft-comofficeser
    verpolicy" group"Policy"gt
  •   ltpLocalizationResourcesgtdlccorelt/pLocalization
    Resourcesgt
  •   ltpNamegtPolicy of Truthlt/pNamegt
  •   ltpDescriptiongt
  •       This policy helps us to achieve the goals
    set in our
  •       "one version of the truth" project
  •   lt/pDescriptiongt
  •   ltpPublishergtTon Stegemanlt/pPublishergt
  •   ltpConfigPagegtpolicyoftruthsettings.ascxlt/pConf
    igPagegt
  •   ltpConfigPageInstructionsgt
  •       You can add keywords here.
  •       If any of these keywords is found in the
    item"s metadata and the metadata also has
  •       the word "truth" or "proof", then the item
    is considered to be the "truth". And our
  •       truth is something we need to manage.
    Separate your keywords with a ""
  •   lt/pConfigPageInstructionsgt
  •   ltpAssemblyNamegt
  •       TST.POC.PolicyOfTruth, Version1.0.0.0,
    Cultureneutral,

11
Create policy Control
  •     lt!-- _lcid"1033" _version"12.0.4518"
    _dal"1" --gt
  •     lt!-- _LocalBinding --gt
  •     lt_at_ Assembly Name"TST.POC.PolicyOfTruth,
    Version1.0.0.0, Cultureneutral,
    PublicKeyToken503edd7b21a430b3"gt
  •     lt_at_ Register Tagprefix"SharePoint"
    Namespace"Microsoft.SharePoint.WebControls"
  •             Assembly"Microsoft.SharePoint,
    Version12.0.0.0, Cultureneutral,
    PublicKeyToken71e9bce111e9429c" gt
  •     lt_at_ Register Tagprefix"Utilities"
    Namespace"Microsoft.SharePoint.Utilities"
  •             Assembly"Microsoft.SharePoint,
    Version12.0.0.0, Cultureneutral,
    PublicKeyToken71e9bce111e9429c" gt
  •     lt_at_ Import Namespace"Microsoft.SharePoint"
    gt
  •     lt_at_ Control Language"C" Inherits"TST.POC.Po
    licyOfTruth.PolicyOfTruthSettings" gt
  •     ltpgt
  •     lttable cellpadding"0" class"ms-authoringcont
    rols"gt
  •         lttrgt
  •             lttdgtnbsplt/tdgt
  •             lttdgtltaspLabel runat"server"
    Text"Enter your keywords, separated by
    """gtlt/aspLabelgtlt/tdgt
  •         lt/trgt
  •         lttrgt
  •             lttdgtnbsplt/tdgt
  •             lttdgt
  •             ltaspTextBox id"TextBoxKeywords"
    runat"server" MaxLength"1024"

12
Create policy Control
  • Creating the Policy Control you have to inherit
    the control from abstract class
    CustomSettingsControl.
  • Important part are CustomData property and
    onLoad Method.
  • In the CustomData property the xml is generated
    with the values of the controls.
  • The OnLoad reads the xml string and sets the
    values for the usercontrol(s) in your editor.

13
Deploy Policy
  • Add the Control in the LAYOUTS folder of the
    MOSS Deployed Path.
  • Deploy the Assemblies.

14
Register Policy
  • Register your policy in the Policy Catalog.
  • PolicyFeatureCollection policyFeatures
    PolicyCatalog.FeatureList
  •         foreach (PolicyFeature policyFeature in
    policyFeatures)
  •        
  •             if (policyFeature.Id"TST.POC.PolicyF
    eatures.PolicyOfTruth")
  •            
  •                 MessageBox.Show("Policy was
    already installed")
  •                 return
  •            
  •        
  •         string manifest System.IO.File.ReadAllTe
    xt("manifest.xml")
  •         PolicyFeature.ValidateManifest(manifest)
  •         PolicyFeatureCollection.Add(manifest)

15
UnRegister Policy
  • Unregister your policy in the Policy Catalog.
  • PolicyFeatureCollection policyFeatures
    PolicyCatalog.FeatureList
  •         foreach (PolicyFeature policyFeature in
    policyFeatures)
  •        
  •             if (policyFeature.Id
    "TST.POC.PolicyFeatures.PolicyOfTruth")
  •            
  •                 PolicyFeatureCollection.Delete(pol
    icyFeature.Id)
  •                 return
  •            
  •        

16
Building Policy XML
  • ltpPolicy xmlnsp"office.server.policy"
    local"false" id"62bb137b-e4c5-4dab-9b90-c9b3e543
    84c5"gt
  •         ltpNamegtThe truth about
    SharePointlt/pNamegt
  •         ltpDescriptiongtThis policy manages
    "truth" items on SharePoint in our
    portallt/pDescriptiongt
  •         ltpStatementgt
  •           SharePoint list items and documents
    that are considered to be the truth about
    SharePoint
  •           Technologies, will be managed by our
    "truth manager".
  •         lt/pStatementgt
  •         ltpPolicyItemsgt
  •           ltpPolicyItem featureId"TST.POC.PolicyF
    eatures.PolicyOfTruth"gt
  •             ltpNamegtPolicy of Truthlt/pNamegt
  •             ltpDescriptiongtThis policy helps us
    to achieve the goals set in our "one version of
    the
  •                 truth" projectlt/pDescriptiongt
  •             ltpCustomDatagt
  •               ltdatagt
  •                 ltkeywordsgtSharePoint MOSS
    WSSlt/keywordsgt
  •               lt/datagt
  •             lt/pCustomDatagt
  •           lt/pPolicyItemgt
  •         lt/pPolicyItemsgt

17
MOSS Demo
  • Demo (Label Policy)

18
Useful Policy Links
  • http//msdn2.microsoft.com/en-us/library/ms499244.
    aspx
  • http//jack.whyyoung.com/blog/www-sharepointblogs-
    com-MainFeed-aspx-GroupID-3/MOSS-Custom-policies-p
    art-1--Creat.htm

19
auditing
  • What is the Auditing?
  • Demos

20
Auditing ?
  • Audits are performed to ascertain the validity
    and reliability of information.
  • Track data such as which users viewed and updated
    records and documents, check-in, check-out etc.

21
Demos
  • Demo - Create a Custom Audit Report
  • Demo - Use auditing feature in MOSS
  • Demo - Create a Custom File Submission
  • Demo - Create a Custom Legal Hold

22
Custom File Submission
  • Implement interface IRouter
  • Only one method OnSubmitFile
  • Reference
  • Microsoft.Office.Policy.dll
  • NameSpace
  • Microsoft.Office.RecordsManagement.RecordsReposito
    ry

23
Useful Custom File Submission links
  • http//blog.thekid.me.uk/archive/2007/04/15/creati
    ng-a-custom-router-for-records-center-in-sharepoin
    t.aspx

24
Business intelligence Solution in MOSS 2007
  • What is Business Intelligence?
  • How many ways we can use BI in MOSS?

25
Business intelligence ?
  • The promise of Microsoft BI is to help decision
    makers at all levels throughout your organization
    have confidence that their decisions support your
    companys goals and initiatives.

26
Business intelligence in moss
  • Report Center
  • Excel Services
  • Connections to external data sources
  • Key Performance Indicators (KPIs)
  • Filter Web Parts
  • Dashboards

27
Report center
  • The Report Center site provides a central
    location for business-intelligence-related
    information.

28
Excel Services
  • Excel Services enables you to store an Excel
    workbook on a server and then publish any part of
    that workbook on a Web page.
  • Users need only a browser to view and interact
    with the live data.
  • The workbook is published on the Web page by
    using the Excel Web Access (EWA) Web Part

29
Connections to external data sources
  • You can use data from other business
    applications, such as SAP and Siebel, in
    SharePoint lists, pages, and Web Parts.
  • You can build Web Pages and SharePoint lists that
    allow users to interact with the data in the
    external source without ever leaving the
    SharePoint page.

30
Key Performance Indicators (KPIs)
  • A Key Performance Indicator (KPI) is a visual cue
    that communicates the amount of progress made
    toward a goal.
  • KPIs are created by using KPI lists and then are
    displayed by using special KPI Web Parts.

31
Filter Web Parts
  • Filters allow you to display only the subset of
    data that you are interested in view.
  • Office SharePoint Server 2007 has 10 Filter Web
    Parts.
  • Example Current User Filter Web Part.

32
Dashboards
  • Dashboards, also known as multi-report summary
    pages, contain one or more Web Parts, such as
    business data Web Parts, Excel Web Access Web
    Parts, or KPIs etc.
  • You can create your own dashboard page by using
    various Web Parts.

33
Useful Business intelligence in moss links
  • http//office.microsoft.com/en-us/sharepointserver
    /HA100872181033.aspx

34
Working with KPIs
  • Indicator using data in SharePoint list
  • A SharePoint list that contains items from
    which you want to create an aggregate value,
    such as a sum, minimum, or maximum. Before you
    set up the KPI, make sure the SharePoint list
    already is in the view that you want to use. You
    must first display the appropriate columns in
    order for the KPI to work.
  • Indicator using data in Excel workbook
  • An Excel workbook where the KPI is calculated
    in the workbook.
  • Indicator using data in SQL Server 2005 Analysis
    Services
  • A SQL Server 2005 Analysis Services cube.
  • Indicator using manually entered information
  • Information that is not in a system and
    therefore entered manually.
  • Demo

35
Useful Working with KPIs links
  • http//office.microsoft.com/en-us/sharepointserver
    /HA100800271033.aspx

36
Agenda
  • Extend Page Authoring Toolbar
  • Create Pages Dynamically.
  • Modify Page Layouts by using Content Placeholders
  • Create Custom Field Control
  • Variations
  • Deploy Content between servers.

37
Extend Page Authoring Toolbar
  • Demo
  • Files

38
Extend Page Authoring Toolbar
  • Class ConsoleAction
  • A class provided by MOSS for you to create new
    menu items.
  • Method RaisePostBackEvent
  • It basically does all the heavy lifting required
    at the time the action is clicked

39
Extend Page Authoring Toolbar
  • Class ConsoleNode
  • This feature to be presented as a top level menu
    with children not just a single menu item.
  • Method InitNode
  • Will be run on every page load, when the object
    is created so we use this method to determine
    whether the current page is in edit mode.
  • Method EnsureChildNodes
  • Will construct the correct list of links which
    are to be displayed to the user.

40
Extend Page Authoring Toolbar
  • Steps involved to change the custom XML file
  • Using SharePoint Designer, check out the
    CustomEditingMenu.xml file under the master page
    gallery   _Catalogs\masterpage\Editing Menu,
    Then, modify the custom XML file with the
    following changes.
  • Add some references to the top of the file so
    that the new actions from the assemblies can be
    referenced. Make sure you use the right
    PublicKeyToken key and the namespace so that the
    references are clear.

41
Useful Extend Page Authoring Toolbar links
  • http//blogs.msdn.com/ecm/archive/2007/03/04/custo
    mize-the-page-editing-toolbar-in-moss-2007.aspx

42
Creating Page Dynamically
  • PageLayout
  • PublishingPage

43
Modify Page layout by using content placeholders
  • Go to Site Actions ? Site Settings ? Modify
    All Site Settings ? Site columns ? Create
  • Enter the Column Name NewsHtmlColumn
  • Select Column type to Full HTML content with
    formatting and constraints for publishing.
  • Enter the Group Name ColumnsGroup in a new
    Group Section and Press the Ok Button.
  • The Go to Site content type ? Page (link under
    the Publishing Content Types Group) ? Add
    from existing site columns
  • Add the NewsHtmlColumn
  • Demo

44
Create custom field control
  • Create an .ascx file with a Sharepoint
    RenderingTemplate control.
  • We need to implement its code behind class must
    derives BaseFieldControl and overrides the
    Property Value.

45
Create custom field control
  • Create a custom field type class, must inherit
    the base class SPField.
  • Override method GetValidatedString to check the
    validity of input and return value.
  • Override method GetFieldValue to get the field
    value
  • Override FieldRenderingControl property returns
    the user control that created above.

46
Create custom field control
  • The custom type must include a custom field type
    definition and name convention should be
    fldtypes_.xml.

47
Create custom field control Deployment Procedure
  • Build the solution and sign the assembly
  • Put the assembly into GAC
  • Copy the user control to \program files\...\web
    server extensions\12\template\controltemplates
  • Copy fldtypes_name.xml to \program files\...\web
    server extensions\12\template\xml\
  • Run iisreset command.

48
Create custom field control Examples
  • SPFieldBoolean   Represents a Boolean
    field type.
  • SPFieldChoice    Represents a choice
    field type.
  • SPFieldCurrency     Represents a currency
    field type.
  • SPFieldDateTime    Represents a date-time
    field type.
  • SPFieldMultiColumn  Represents a multicolumn
    field type
  • Demo

49
Useful Create custom field control links
  • http//msdn2.microsoft.com/en-US/library/aa830815.
    aspxOffice2007SSBrandingWCMPart2_CreatingCustomFi
    eldControls
  • http//www.sharepointblogs.com/jimyang/default.asp
    x

50
Variations
  • Variations can be used for publishing related
    sites or pages, purpose is to support
    Multilingual in MOSS.
  • Instead, you will have sub sites under the web
    root representing your variations.

51
Variations
  • The root welcome page is configured by SharePoint
    (upon creation of variation labels and site
    structures) to point to a file called
    VariationRoot.aspx.
  • Template Page of VariationRoot.aspx is
    VariationRootPageLayout.aspx
  • This file contains a user control
    VariationsRootLanding.ascx, which has the code
    that redirects.
  •  
  • For customization you have to change the control.
  • Control Location
  • C\Program Files\Common Files\Microsoft
    Shared\web server extensions\12\TEMPLATE\CONTROLTE
    MPLATES\VariationsRootLanding.ascx

52
Variations
53
Useful Variations links
  • http//msdn2.microsoft.com/en-us/library/ms562040.
    aspx

54
Deploy Content between servers
  • Create Production Site Collection.
  • Allow Incoming Content Deployment Jobs on the
    Production Site.
  • Create Content Deployment Path from Staging to
    Production.
  • Create Content Deployment Job.
  • Run Content Deployment Job.
  • Run Quick Deploy Job.

55
Deploy Content between servers
  • Create Production Site Collection.
  • Select "Blank Site" as the template. This step is
    IMPORTANT, because Blank Site is the only
    template that you can import any other template
    into
  • Allow Incoming Content Deployment Jobs on the
    Production Site.
  • Central Administration?Operation?Content
    deployment settings?(Select Accept incoming
    content deployment jobs)
  • Create Content Deployment Path from Staging to
    Production.
  • Central Administration?Operation? Content
    deployment paths and jobs? New Path
  • Create Content Deployment Job.
  • Central Administration?Operation? Content
    deployment paths and jobs? New Job
  • Run Content Deployment Job.
  • From the context menu on the job, select Run
    Now
  • Run Quick Deploy Job.

56
Useful Deploy Content between servers links
  • http//blogs.msdn.com/jackiebo/archive/2007/02/26/
    content-deployment-step-by-step-tutorial.aspx

57
Agenda
  • Provision multiple sites in a hierarchy.
  • Display data from a Microsoft Excel workbook by
    using Excel Services.
  • Create a trusted workbook location by using the
    Stsadm.exe command-line tool.
  • Filter data in a workbook by using Excel
    Services.
  • Configuration of Reporting Services.
  • How to use Report Viewer webpart providing with
    parameters.

58
Provisioning multiple sites
59
Display data using excel services
  • Make sure the file from where the Excel file is
    view its path should be added in the trusted
    file location of Shared Services.
  • Path SharedServices1? Trusted file locations?
    Add Trusted File Location.
  • You can view the Excel file on the web with the
    help of excel services and at the backend the
    Excel Web Access (EWA) webpart is viewing this
    file.
  • Demo
  • Trusted file location

60
Trusted workbook location using stsadm.exe
command liine tool
  • STSADM -o add-ecsfiletrustedlocation -ssp
    sspname -location 1 -includechildren true
    -locationtype LocationType

61
Filter data in workbook by using excel services
62
Filter data in workbook by using excel services
63
Filter data in workbook by using excel services
64
Filter data in workbook by using excel services
65
Configuration reporting services required
  • Microsoft SQL Server 2005.
  • Reporting Services installed on the server.
  • SQL Server Service Pack 2
  • Microsoft SQL Server 2005 Reporting Services Add
    in for SharePoint Technologies
  • Download at http//www.microsoft.com/downloads/de
    tails.aspx?familyid1E53F882-0C16-4847-B331-132274
    AE8C84displaylangen

66
Configuration reporting services
67
Configuration reporting services
68
Configuration reporting services
69
Configuration reporting services
70
Configuration reporting services
71
Configuration reporting services
72
Configuration reporting services
73
Configuration reporting services
74
Configuration reporting services
75
Configuration reporting services
76
Configuration reporting services
77
Configuration reporting services
78
Configuration reporting services
79
Configuration reporting services
80
Configuration reporting services
81
Configuration reporting services
82
Configuration reporting services
83
Configuration reporting services
84
Configuration reporting services
85
Report viewer webpart providing with parameter
86
Report viewer webpart providing with parameter
87
Report viewer webpart providing with parameter
88
Report viewer webpart providing with parameter
89
Report viewer webpart providing with parameter
90
Report viewer webpart providing with parameter
91
Report viewer webpart providing with parameter
92
Report viewer webpart providing with parameter
93
Report viewer webpart providing with parameter
94
Report viewer webpart providing with parameter
95
Report viewer webpart providing with parameter
96
Report viewer webpart providing with parameter
97
Report viewer webpart providing with parameter
98
Report viewer webpart providing with parameter
About PowerShow.com