Connecting to Windows SharePoint Services - 2003

Use the link to the page of SharePoint Server to specify the information needed to connect the project jogging Sever 2003 to a Web server running Windows SharePoint Services. The root path of a server running Windows SharePoint Services must exist when the team jogging Project Server 2003 connects to the server running Windows SharePoint Services. The URL of the server running Windows SharePoint Services must always focus on a top-level site in the virtual server root. If the top-level site at the root of the server running Windows SharePoint Services does not exist or is a redirect in place, the connection will fail. For example, if the direction of Windows SharePoint Services is http://MyServer:80/projects, the connection will only work if this URL is a higher level and feel



The Connect to SharePoint server page in Project Web Access.

To specify connection information for a server running Windows SharePoint Services

1. In Project Web Access Manager, in the side pane under Actions, click Manage Windows SharePoint Services .

2. In the side pane, under Options, click Connect to SharePoint server.

3. On the Connect to SharePoint server page, under Enter information on the web server running Windows SharePoint Services, in the SharePoint Central Administration URL box, type the Uniform Resource Locator (URL) for the SharePoint Central Administration page.

4. Create a site at this URL box SharePoint, SharePoint managed type route address of the server running Windows SharePoint Services that will host the site collections for projects. The SharePoint Managed Path is the address of the server running Windows SharePoint Services sites and appended to it. For example, http://serverName:80/sites.

5. Optionally, type the extranet address for the server running Windows SharePoint Services SharePoint Extranet Address box. This URL is a path and Managed SharePoint URL. When you enter the address of the Windows SharePoint Services extranet, you must also ensure that the extranet address is entered in the computer jogging Project Server 2003. You can specify the direction for the team extranet jogging Project Server 2003 in the server configuration section of the Admin page. 6. Perform the following validation steps before saving your changes:


# Verify that the SharePoint Central Administration URL is valid. Click the Test URL hyperlink to the right of the box SharePoint Central Administration URL to go to the page. You should be able to view the content of the page or receive a login. To view the content of the page, the current administrator logon account must have administrative access to the server running Windows SharePoint Services.


# Check that the Windows account (domain \ user) used to create the project for Windows SharePoint Services server administrator COM + application has permissions to the SharePoint Administration account. Log on to the server running Windows SharePoint Services as domain \ username (specified in the local user interface) and go to the SharePoint Central Administration page in the Administrative Tools menu. Note that Project Server 2003 to remotely manage the Web server running Windows SharePoint Services with this domain name. To change this account information, you must rerun the draft COM + server configuration tool (Pscomplus.exe) and then restart the account.


# Check that site documents public is valid. Click on Public Documents Site URL to go to the page. You ought to be able to view the content of the page or receive a login. To view the content of the page, the current administrator logon account must have at least read only access to the site. The documents for the public site is automatically created when you run the SharePoint Configuration Wizard during the installation of Project Server.

7.Click Save Changes.

How to enable an ASP.Net application to run on a SharePoint –2003 virtual server

To enable an ASP.NET application on a server walking on foot from Windows SharePoint Services or SharePoint Portal Server 2003, configure an exclusion for the application path on the virtual server. The exclusion tells the server not walking SharePoint Portal Server 2003 to intercept the request to access the virtual server and allow the information to Microsoft Web Services (IIS) to handle the request.
Note: in Office SharePoint Server 2007, you have to configure an exclusion. However, you must create a virtual directory using Internet Information Services Manager. Additionally, you must configure the virtual directory as an application. The application must have a corresponding Web.config file.
To create an exclusion for a part of the URL namespace of the virtual server, follow these steps:
1. Click Start, click Administrative Tools, and then click SharePoint Central Administration.
2. In the Virtual Server Configuration area, click Configure virtual server settings.
3. On the Virtual Server List tab, click the virtual server that you have to add the excluded paths to.
4. Under Virtual Server Management, click Define Managed Paths.
5. In the Add a New Path section, type the path that you want to exclude in the Path box.
6. Click Excluded Path, and then click OK.
Sometimes you have to do more than establish the route of exclusion. Some Web programs require modify the Web.config file for the server running Windows SharePoint Services or SharePoint Portal Server 2003. To modify the Web.config file, follow these steps:
Important Changes: These changes are the most open and unrestricted. Should be evaluated closely and carefully evaluated before use in a production environment.
1. On the server that hosts the Web page you want to configure, locate the path that was excluded from the steps earlier in this article. The route is similar to the following:
drive:\inetpub\wwwroot\Excluded Path
2. Save a backup copy of the Web.config file as Web2.config.
3. Open the Web.config file.
4. Locate the the tag, and then add the following code under the label:
<!-- Set the trust back to Full. WSS configures a very restrictive trust policy that does not allow most applications to run correctly. -->
<trust level="Full" originUrl="" />
<!--
Enable the modules that you must have for your program to run.
If you receive the following message:
Parser Error Message: The module '<moduleName>' is already in the program and cannot be added again
You can remove the modules that are mentioned in the error message. The SharePoint web.config already includes the module for OutputCache and WindowsAuthentication so you do not have to add them here.
-->
<httpModules>
<add name="Session" type="System.Web.SessionState.SessionStateModule"/>
<add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule"/>
<add name="PassportAuthentication" type="System.Web.Security.PassportAuthenticationModule"/>
<add name="UrlAuthorization" type="System.Web.Security.UrlAuthorizationModule"/>
<add name="FileAuthorization" type="System.Web.Security.FileAuthorizationModule"/>
</httpModules>
<!-- Enable Session for the pages -->
<pages enableSessionState="true" enableViewState="true" enableViewStateMac="true" validateRequest="false" />
5.Save the Web.config file.
For additional information about how to create a Web.config file to use with ASP.NET, click the following article number to view the article in the Microsoft Knowledge Base:
6. Install the HTTP module that is described in Microsoft Knowledge Base a look for canonicalization issues with ASP.NET. After installing the module, add module reference to the Web.config file for your ASP.NET application that resides under an excluded path of SharePoint Portal Server 2003 virtual server.
Note: the module is to be added to the Web.config file that SharePoint Portal Server 2003 uses the virtual server root.
To add the module reference to your ASP.NET application's Web.config file, follow these steps:
a. Open the Web.config file.
b. Locate the <httpModules> entries inside the <system.web> section that you added in step 4, and then add the following code after the last entry:
<add name="ValidatePathModule" type="Microsoft.Web.ValidatePathModule, Microsoft.Web.ValidatePathModule, Version=1.0.0.0, Culture=neutral, PublicKeyToken=eba19824f86fdadd"/>
c. Save the Web.config file.

SharePoint-2003 Customizer

Project Description
Customizer SharePoint is a tool for customizing SharePoint Web sites look and can also be used for any website, because it is designed to replace the default CSS classes of any website.



This tool developed specifically for customizing the look and not touch the default CSS files in SharePoint.


Features:
1- Opens any online site or offline page and apply your new styles without refreshing the page by few steps
2- Displays current CSS class attributes by click the class name
3- Full review of the page HTML and styles through:

• Mouse selections of the item
• HTML tree view
• Property box

4- You can add new/existing images and it will appended automatically to the CSS
5- Auto Complete CSS feature
6- You can append more than one CSS file
7- Color Picker tool which applies the Color code automatically to the CSS
8- Exports the full package to be applied on either SharePoint or any website

Customizing the Login Page in SharePoint 2007

Microsoft SharePoint 2007 you have the option of using forms authentication, but the out-of-the-box forms-based login experience is fairly smooth. Not bad, if you're doing something for internal use, but if you're doing something for internal use, then probably you are using Windows authentication. Forms authentication is normally found in the external customer-facing or in places where corporate branding is big business, and master pages play an important role in presenting a consistent look through a SharePoint site. But when you apply a master page to a publishing site, or edit default.master in a team site, you'll quickly realize that does not alter the appearance of the logon page. In this article we take a look at what is and what needs to do to get your login page in line with its corporate brand.

Where does the login.aspx page reside?
When you try to view a protected page in a forms authenticated site, SharePoint redirected to the login page (Figure 01). At the logon screen, take a good look at the URL in the browser page warning that login.aspx is in the _layouts folder. If you go to the directory that hosts the SharePoint application, you'll quickly realize that there is no _layouts folder in the directory itself. This revelation is not surprising to most since many of the pages you see in SharePoint does not really exist in the file system. But if you open the Internet Information Services (IIS) Manager and navigate to the SharePoint site, you will find that the _layouts folder is actually a virtual directory that points to the following real-life directory on the server (assuming you installed in the location default):
C:\Program Files\Common Files\Microsoft Shared\Web Server Extension\12\template\layouts

The folder contains application designs and system pages used by all SharePoint sites on the server. Upload a new document to a site that ends in the upload.aspx page folder of designs. View people who access the site will be people.aspx page. And if you're trying to login, it connects to the login.aspx page. There are 400 pages in the directory, each of which has its own particular point and purpose, so it's impossible to go into detail on every page.

Figure 1 – the login.aspx page

Global consequences of changing files in the _layouts folder

Armed with the location of the pages on the implementation of SharePoint, you may be tempted to dismiss an editor and start hacking away at them, but you should probably know what you're getting into before going down that road. Remember how the _layouts folder of your SharePoint site is a virtual directory that points to C: \ Program Files \ Common Files \ Microsoft Shared \ Web Server Extension \ 12 \ template \ layouts? Well, all SharePoint sites on the server is configured the same way. This means that when you change anything in the _layouts folder of a site will change to every single SharePoint site on your server. It also means that you are editing a single version of the file on your system, so it is best to back up the contents of the folder. Otherwise you need to reinstall SharePoint to get the files back into service if you have a nasty accident.


Creating a site-specific _layouts virtual directory
Depending on your situation, apply changes to all sites on the server may or may not be a bad thing. If all sites on the server of the need for exactly the same make, design and functionality, then go ahead and make the change directly in the standard design folder (after backing it up). But it may well only be in a situation where each site has to be different, so that the implementation of radical change to all sites won't work. What do you do when you are in that situation? You make a copy of the shared folder designs specifically for your site, and make changes in the copy of that site-specific. To do this, take the following actions

1.) Navigate to the C:\Program Files\Common Files\Microsoft Shared\Web Server Extension\12\template\ folder
2.) Select the layouts folder and copy it
3.) Navigate to the root directory of your SharePoint site
4.) Paste a copy of the layouts folder in your SharePoint directory
5.) Rename the layouts folder _layouts
6.) Open the IIS manager snap-in
7.) Expand your SharePoint site’s website entry
8.) Right click on the _layouts virtual directory (you may also see a non-virtual _layouts folder) and select Properties from the context menu
9.) On the virtual directory tab, click the Browse button next to the Local Path textbox to display the directory selection dialog
10.) Navigate to the _layouts folder you just created in your SharePoint site, select it, then click OK
11.) Click OK to apply the change to the _layouts virtual directory

Now you can make changes in the _layouts folder for your SharePoint site without it affecting other sites on
your server.

Warning: some operations in SharePoint Central Administrator, like extending a site or changing the authentication type for a zone, can “reset” the _layouts virtual directory in your SharePoint sites so they point back to C:\Program Files\Common Files\Microsoft Shared\Web Server Extension\12\template\layouts. When this occurs, just go back into the IIS manager snap-in and point the virtual directory back over at the _layouts folder copy for your site.

Login.aspx and its Master Page

When you open the login.aspx page you'll quickly discover is a content page that contains the marking of a title, a layout table, username text, password text, a login button, a "Remember Me" check box, and content controls useful for some text labels next to some of the fields. Just enough to set a non login indescribable, but certainly not enough to make the environment unpleasant bluish in the logon page standard SharePoint (see Figure 1 again). The login page is based on the home page in the _layouts folder simple.master define most of the look you see around the page (see Figure 2). What follows is the Page directive at the top of the login.aspx page that shows the association of the simple.master with page.

Code Snippet

1. <%@ Page Language="C#"
2.     Inherits="Microsoft.SharePoint.ApplicationPages.LoginPage"
3.     MasterPageFile="~/_layouts/simple.master"%>

When you are considering changing the appearance of the access method, you must determine exactly what we are trying to achieve. If you want to change the brand around the form itself, then you need to edit the page simple.master. To change the shape of the connection itself, reordering checks, add additional help text, graphics, etc, then you need to edit the login.aspx page.


Figure 2 – simple.master from the layouts folder

Editing the simple.master page

Like most master pages, the simple.master controls the look and feel or more than just a single page. In fact, it controls the look and feel of seven pages in the _layouts folder:

Page Name	Description
AccessDenied.aspx	Displays a notice that you have been denied access to the requested resource. Shows the name of the currently logged-in user and a link to sign-in as a different user.
Confirmation.aspx	Displays a message indicating that the requested operation succeeded.
Error.aspx	Displays a message indicating that an error has occurred. May also display additional stack trace information if the site has been configured to do so.
Login.aspx	Display a login page allowing users to enter forms authentication credentials.
ReqAcc.aspx	Displays a notice that you have been denied access to the requested resource.
Signout.aspx	Responsible for logging a user out of the site.
Webdeleted.aspx	Displays a message indicating the web site has been deleted.

People who visit your SharePoint site authenticated forms shall be implemented within a couple of these pages on a regular basis, so you'll definitely want to include in any effort simple.master brand who are committed to your SharePoint site. However, with seven different pages based on page simple.master, the question is what can be changed on page simple.master and what to leave? ContentPlaceHolders Master pages contain controls that identify the sections of the page where the content can be injected by a content page. Content pages contain content controls that relate to the ContentPlaceHolder controls on the master. If a content page refers to a ContentPlaceHolder in the master, but you have taken that ContentPlaceHolder, it fails. Therefore, the key to the modification of a homepage is not necessary to remove any ContentPlaceHolder control.

ContentPlaceHolder controls Determinging exactly what is needed in a home can be very difficult because some of ContentPlaceHolders may be required by a page, but not in another. For example, the page contains a ContentPlaceHolder controls simple.master name PlaceHolderPageImage. If the simple.master, login.aspx the page loads without any problem because the login.aspx page does not refer to the control. However, you get an error when you hit the AccessDenied.aspx page because PlaceHolderPageImage used to insert a small icon on the page. From simple.master only controls the appearance of seven pages, which do not have much time to review each page to see if it has taken a necessary control. With the main pages of others who are not so fortunate. APPLICATION
One way to avoid the headache of accidentally removing the controls required is to leave them on the page, but hide them. The process looks something like this:
1. Open your master page file
2. At the bottom of the page, add a hidden panel using the following code:

Code Snippet

1. <asp:Panel runat="server" visible="false">
2.  </asp:Panel>

3. Look through the markup of your content page and locate any ContentPlaceHolder controls  (or any other server controls for that matter) on the master page
4. When you find a ContentPlaceHolder control (or a server control) cut and paste it into that hidden panel

When finished, have a home server controls which are entirely contained in a hidden panel. View any page that references that I love, and you will see that the page is rendered without any error, because all the controls that are not originally there, just hidden. Of course, also is without any type of content, because the hidden panel hides everything, but we'll take care of that next. Now you can start changing the look of the homepage by adding brand elements to your corporate image. In doing so, you can start adding back in any ContentPlaceHolders and server controls you want in the final home.

If you’re curious, the following ContentPlaceHolders are required in the simple.master:

· PlaceHolderAdditionalPageHead
· PlaceHolderPageTitle
· PlaceHolderSiteName
· PlaceHolderTopNavBar
· PlaceHolderTitleBreadcrumb
· PlaceHolderPageImage
· PlaceHolderPageTitleInTitleArea
· PlaceHolderMain
· PlaceHolderPageDescription
You’ll also probably want to keep the ScriptLinkControl named ScriptLink1 as well, because it contains important JavaScript includes.

 

Editing the login page

Editing a page of content is a task far less dangerous than changing a page, because any error introduced is located on the page itself. You can save a copy of the page on your browser and refresh the screen to make a change to see if it breaks. Like the homepage, the most important thing to remember in a content page is the class that controls the page is in search of specific page elements. If it comes to finding a page element is not there, the page throws an error and would not be. If you do not want an item to display on the screen, you can place the control on a hidden control panel to hide it from view without breaking the code that handles the page.

Most changes will be doing in the content pages are cosmetic, and is likely to revolve around adding additional content here and there and change the design of elements within the page. Understand, however, that all these SharePoint pages are built using ASP. NET. As such, these pages can be altered in any way you can customize an ASP.NET page, allowing you to do some heavy renovations if desired. For example, take the login.aspx page. Here is the Page directive in login.aspx:

Code Snippet

1. <%@ Page Language="C#"
2.          Inherits="Microsoft.SharePoint.ApplicationPages.LoginPage"
3. MasterPageFile="~/_layouts/simple.master" %>

Note that references simple.master page as your home page and inherits its functionality Microsoft.SharePoint.ApplicationPages.LoginPage class. If you do not want the page to use a login.aspx page, you can remove the MasterPageFile element in the Page directive and place all the marks of marked directly in the login.aspx page itself. I do not recommend the approach, but you can do. Or what if you do not like the way Microsoft.SharePoint.ApplicationPages.LoginPage class is responsible for the page? You can remove the item to remove the logic of the page completely, or the point that in a different class. Removing the element inherits, you can write your own custom code for the page by adding server-side script directly in the login.aspx page. I put the following code in my login.aspx page and works well (and he really register on the site too!)

Code Snippet

1. <%@ Page Language="C#" %>
2.     <script runat="server">
3.         protected override void OnLoad(EventArgs e)
4.         {
5.             Response.Write("This is from the onload event");
6.             base.OnLoad(e);
7.         }
8.     </script>
9.     <html>
10.          <body>
11.              <form runat="server">
12.                  <asp:login id="login" runat="server" />
13.              </form>
14.          </body>
15.     </html>

Is it a good idea to get rid of the homepage and the control class for a SharePoint page? Absolutely not! But it does show that the flexibility is in editing pages.

SharePoint Reports with Microsoft Office Excel 2003

Microsoft Office Excel 2003 has the ability to synchronize with EPM Live SharePoint workspaces. By leveraging Microsoft Office Excel 2003 as an information tool has the ability to create multiple reports of different dynamics.

1.  Open Microsoft Office Excel 2003
2.  From your SharePoint site navigate to the list that you want to create your report from.  (Images indicate Project Center list.)
3.  Choose the view with the data that you want to report on.

4.  Click the “Actions” button and choose the “Export to Spreadsheet” option.

5.  Click “Open”

6.  Click “Enable” when the security notice window pops up.
7.  Choose the type of chart/table or both that you would like to create and click “OK”.

8.  Chose the data that you want to report on by checking the box next to it.

9.  You can now close the PivotChart Filter Pane and the Pivot Table Field List unless you want to set up a filter.
10. Right click on the chart itself if you want to change the chart type.

 

11.  Choose your chart type and click “OK”

Using Excel (Excel 2003) Data Source to Retrieve Data from SharePoint List

Using Excel 2003, you can create a data source to retrieve data from a SharePoint list. This method also has the added benefit of displaying columns that are not usually displayed in a traditional export to Excel. For example, in the fault database, 'Assigned to' and 'ownership' columns are not shown when the list is exported to Excel using Excel 2003.
* Open Microsoft Excel 2003
* Select Data > XML > XML Source from the menu. The 'XML Source' window is displayed to the right
* Click 'XML Maps'
* Click 'Add' in the XML Maps window
* Select 'New Source' in the 'Select XML Source' window. This displays the 'Data Connection Wizard' window
* Select 'Microsoft SharePoint Services lists' from the list and click the 'Next' button
* Enter the location of the data that is to be retrieved and click 'Next'
* Select the object or list that contains the data you need. Click 'Next'. 'Select Fields' window is displayed
* Select the columns required from the 'Available Columns' region and click 'Add'. Click 'Next'
* Specify 'Sort Criteria' and click 'Next'
* Specify 'Filter Criteria' to filter the displayed data and click 'Next'
* Specify whether you would like the number of rows to be retrieved and click 'Next'
* Enter a 'File Name' and 'Description' and click the 'Finish' button to complete.
* Note that the file name is displayed in the 'Select XML Source' window. Click 'Open'
* Click 'OK' in the 'XML Maps' window. Note that all the selected rows are displayed in the 'XML Source' region on the right side
* Map the elements by dragging the required rows to the Worksheet. What we have is the report with the header rows displayed; time to get the data
* Select Data > XML > Refresh XML Data from the menu to import the data
* Format the columns as required. Formatting may be required to align the cell display. Macros can be put to good use here


Note:
If the original list for data collection in rich text format, they would realize that the imported data is displayed with the html tags and not pleasant to read. You may want to change the input data in a column of text (in the SharePoint list) to resolve these.

Display SharePoint Metadata in Word 2003

So I had to find a generic solution shows the SharePoint metadata in Word 2003 templates. I have found different solutions to achieve this goal, but none of them solved all my problems. The most common problem ist updating their fields at the right time.

Getting Started / Limitations:
* SharePoint Metadata in Word 2003 is assigned more than Document Properties
* Only fields of type "Text" can be assigned (If you need to display the values of other text fields, you must add a text field to your type of content and use an EventHandler to copy the value to the desired the text field and the map as Doument this property to your Word template. A common scenario might be "version" or author of a document that are not text fields OOB)
* Properties OOB document updates Print only (This is a Word option that is set by default)
How:
* Link to your Word template for ContentType corresponding DocLib
* Add the following code, which updates the fields when the document is opened, such as Macro (Macro in the current document, not as module) for the Word template:

Code Snippet

1. Private Sub Document_New()
2.         ActiveDocument.Fields.Update()
3.     End Sub
4.     Private Sub Document_Open()
5.         ActiveDocument.Fields.Update()
6. OStory As Object
7. OTOC As Object
8.         'exit if no document is open
9.         If Documents.Count = 0 Then Exit Sub
10.         Application.ScreenUpdating = False
11.         For Each oStory In ActiveDocument.StoryRanges
12.             oStory.Fields.Update() 'update the fields in all stories
13.         Next oStory
14.         For Each OTOC In ActiveDocument.TablesOfContents
15.             oToc.Update() 'update TOC
16. OTOC Next
17.             Application.ScreenUpdating = True
18.     End Sub
19.     Private Sub Document_Close()
20.         ActiveDocument.Fields.Update()
21.     End Sub
22. Document_Sync Private Sub (ByVal SyncEventType As Office.MsoSyncEventType)
23. End Sub

This code updates all sections of the document, including header and footer, not only the content section.
Save the template and create your first document of this template.

Meeting workspaces SharePoint 2003: Organize for efficiency

A Meeting Workspace SharePoint integrates with Microsoft Outlook 2003. To create a new meeting workspace, click the Meeting Workspace button when sending a meeting request in Outlook. This will open a work space of the meeting of the task pane in collecting, as shown in Figure A. In this case, you can create a new workspace on the server of your SharePoint team. When sending the invitation to the meeting, some attendees will receive a link to the meeting area.

Figure A

A Meeting Workspace is a special type of SharePoint site. By default, the site will have sections for Objectives, Attendees, and Agenda. You can also add other sections (called Web Parts in SharePoint) by clicking on the hyperlink Modify This Workspace. In Figure B, we have added an element subroutine library of Web documents in the work area so that attendees can review important documents related to the meeting. Clicking on a document that allows you to open and edit in the permit application of Office.

Figure B


The working area of the meeting is a good demonstration of the principles of collaboration built into Office 2003:
* The Collaboration Data is stored in a SharePoint site.
* Users can manage the site themselves from their browsers, without any administrative support.
* The data is stored in Office documents and edited in Office applications.
* The workspace captures all aspects of a particular task or activity.


Document Workspaces Sharepoint 2003: collaboration effortless


Areas of documents have a document centered at (place of meeting-centric) way to work in Office 2003. A Document Workspace is designed to help a group of users collaborate on one or more documents. Office 2003 lets you convert a Word, Excel or PowerPoint in an area, simply by working with others in ad-hoc mode. By inviting others to collaborate on the document or the assignment of tasks creates a Document Workspace, but never to work directly with SharePoint.

You can create a document workspace without leaving your Office document. For example, if you have a Word document open, you can select Shared Workspace from the Tools menu. This will open the Task Pane Shared Workspace. The task pane opens with the Members tab highlighted, and prompts you for a workspace name and location. Choose a name, complete address of your SharePoint server as the location and click Create to create a new document workspace with you as the default (and only) members.
As part of the creation of the document area, the document is stored on the SharePoint server, which also maintains a register of members, tasks and other information in the document area. Any member of the Document Workspace can open the document directly from the server, or check out a copy to work with on your local hard drive. The task pane Shared Workspace (shown in Figure C) includes a link to the document area (Prospects of publicity is the name of the workspace in this case) and six tabs.

Figure C


You can use the link to open the Document Workspace in your browser. From left to right, the chips have the following functions:
* State: Displays alerts and other status messages
* Members: Displays the members of the workspace
* Tasks: Display tasks in the work area, along with his situation and who have been assigned
* Documents: Displays the documents in the workspace (although a work area begins with a single document, you can add many more documents as you like)
* Links: Displays the hyperlinks in the workspace
* Document Information: Lets see who has last modified the document and its version history.
A Document Workspace provides an easy way to create a group to collaborate on a document or group of documents. The built-in tabs that let you work with the features of SharePoint without having to open SharePoint. If you need any of the more advanced features of SharePoint (eg discussion group), you can skip the document to the actual work area on your Web browser with one click.

Access 2003 and Windows SharePoint Services

SharePoint has been around for a few years ago, in two versions: a product of the working group originally known as SharePoint Team Services, and a product known as SharePoint Portal Server portal. Although these products share a name, were actually separate code bases for the same purpose: to allow teams and workgroups to share documents and information in collaboration with others using Web protocols.
This year, however, SharePoint is moving from the wings to center stage. It's been redesigned to use SQL Server and ASP.NET as their foundations, and integrated more closely with other Microsoft software products, including Office 2003. This integration extends to Access 2003, which is able to treat SharePoint as another source of data for import, export, and data link.

Introduction to Windows SharePoint Services 2.0

Windows SharePoint Services (formerly SharePoint Team Services) is Microsoft's solution for working and department quislingism. SharePoint Services allows you to communicate, share documents and work together on projects using nought more than a web browser or any application of Microsoft Office 2003.
To make use of SharePoint in Access 2003, you must install the new version of SharePoint Services. Although there are ways to extract data from the original release of SharePoint to Access 2003, the deep integration possible with Access 2003 requires the use of SharePoint Services version 2.0. You will need a server to meet these minimum requirements:

• Windows Server 2003 operating system
  
• The NTFS file system
  
• IIS 6.0 installed on your worker process isolation mode default
  
• ASP.NET installed

If you meet these requirements, the installation of SharePoint Services is easy. SETUPSTS.EXE Just run the file in the Windows SharePoint Services CD-ROM. This installs SharePoint Services on the default Web site for the computer, and sets its own example of SharePoint Microsoft Desktop Engine (MSDE) Microsoft SQL Server (in this case the data set in SharePoint Services). For this article, I used the Beta 2 Technical Refresh version of SharePoint Services and Access 2003.



Figure 1 shows an open process in the SharePoint site in Internet Explorer 2.0. While this is the default to act with the data from SharePoint, which is far from being the only way. In particular, Access 2003 SharePoint seen as a source of first class in its own right. Note the "lists" category in the navigation bar to the left of the window. A SharePoint list is the equivalent of an Access table, which is an orthogonal matrix of data fields and records.

 
Exporters, importers, and linking data



While Web browsers do not provide ubiquitous access to data in SharePoint, you just provide the best possible user experience. Of course, as Access developers already know is an application program designed for a top-notch user experience when browsing structured data: Access. So it's good to know that Access 2003 SharePoint Services allows you to be treated like any other data source. You can export data from Access to SharePoint, SharePoint data relevant to access, or (perhaps most interesting from the standpoint of collaboration applications) of data link SharePoint for access and data access in real time. I will demonstrate each of these fundamental operations.
First, a warning. I'm using the beta version of Access 2003, so some details may change the final version.
Export data from Access to SharePoint
For starters, here is how you can export a table from Access to SharePoint:
1. Click on a table in the database window and select Export.
2. Select SharePoint Team Services in the Save as type of jazz band (presumably this will change to "Windows SharePoint Services" in the final version of Access 2003). This opens the Export to Windows SharePoint Services Wizard.
3. Enter the URL of the SharePoint site, where the exported data should reside. You can also specify a list of name and description, by default, they are populated with the name of the table access and description. Click Finish.
Figure 2 shows the exported table as a SharePoint list. As you can see, SharePoint exposes a very rich user interface for working with list data (for a rich web application, in any case).
Figure 2
Import data from SharePoint to access
Of course, if you can export, you can import. Import data from SharePoint to access is a bit more complicated than it exported, but still relatively simple:
1. Select File | Get External Data | Import.
2. Select SharePoint Team Services in the Files of type combo box (again, hopefully this will change for the release version). This will open the import of Windows SharePoint Services Wizard.
3. Enter the URL of the SharePoint site that contains the data to import and click Next.
4. In the next wizard panel, you can choose to import the lists and views. A view is similar to an Access query: That it is a subset of a list (eg "My Tasks" is a view of the standard task list). You can use Ctrl + click to select multiple lists to import.
5. It is also necessary to select which columns to search. The check box "Retrieve IDs lookup columns" is somewhat confusing. If you uncheck the box, then any lookup columns in the data are filled with data from the other list. For example, the task list has some lookup columns to get names from the list of UserInfo. If you uncheck this box, then imported the Access table will contain the actual names instead of numeric identifiers. If you check the box, numeric identifiers will be imported.
6. If you choose to recover IDs, the next step wizard will help you decide what to do with lists. You can choose to create linked tables pointing to these lists, or import into their own tables in Access.
7. The final panel of the wizard to confirm your choices. Click Finish to import the table or tables that you chose.
When you import data from SharePoint to Access, Access will import as field properties until you can. For example, if a SharePoint list contains a currency column, the import process will create a currency field in Access. Access will also inherit that required, the default, Format and Decimal Places settings SharePoint column (remember that it is MSDE / SQL Server that is storing data in SharePoint, so there are a lot of overlap with the Jet tables). Moreover, access is going to build a validation rule to enforce minimum and maximum values set in SharePoint.
Linking SharePoint data for access
Finally, you can link access to SharePoint data. This has the usual advantage of related data: It lets you keep data stored in SharePoint, and still work with it in Access. Linking works and import, unless you can only link (not import) related to the tables. Access uses a stylized calendar icon to represent a linked list of SharePoint. Figure 3 shows the window of the database with two linked lists in SharePoint.
Figure 3
Microsoft supports editing of data simultaneously access and SharePoint with a pessimistic locking scheme. If users change the same record in both environments, while the second copy to be saved will cause an error message. On the SharePoint side, the error appears as a Web page that tells the user that someone has changed the topic and providing the opportunity to save your data on top of changes. On the side of access, users get the dialog box Create Family Conflict if they try to overwrite changes made by another user.



The result of this coordination is that in some circumstances, SharePoint lists offer an ideal way to extend the reach of an Access database to work with users who have no access. For example, suppose you have field representatives that have to be able to view a table of parts that have been stored in an Access database. Instead of writing your own web interface to data, you can export the table to a SharePoint site on a server with Internet connection and link from the list back to your Access database.
Programming SharePoint access



traditional access points has been that all I could do from the user port could also be done from VBA code. That is still true when working with SharePoint, but as I will show in a moment, there is no branching rare. As with other data transfer operations, DoCmd.TransferDatabase method is used to move data to and from SharePoint programming. To export a table called orders to a call list OrdersList SharePoint, you can use a command like this:
DoCmd.TransferDatabase acExport, "WSS". _
"http://Server/sites/testsite", acTable, "Orders", _
"OrdersList", False
The final parameter controls whether to export only the structure of the structure, or export of both the structure and table data.



The significance or link a SharePoint list, you can also use the method TransferDatabase, but this is where the branch comes in. Here's a VBA command to link a SharePoint list named part
DoCmd.TransferDatabase acLink, "WSS", _
"WSS;HDR=NO;IMEX=2;" & _
"DATABASE=http://Server/sites/testsite;" & _
"LIST={800BE2B7-FA3C-4CFC-BBB3-8500C4EDCF22};" & _
"VIEW=;RetrieveIds=Yes;TABLE=Parts", acTable, , _
"Parts"
Ugly, huh? The problem is that SharePoint does not refer to the lists by name. GUID uses SharePoint internally to identify the lists (which is how they can store, for example, 10 different lists of contacts in the same database MSDE). When using the Access user interface to import or link SharePoint data, access is responsible for matching the names of the GUID. But when you're dealing with the Jet engine directly through VBA, you're on your own. The long chain (starting with "WSS" and ends with "TABLE = Parts") identifies a particular SharePoint list.



If you're faced with the problem of programming to import or link data from SharePoint, there are two ways to get the correct GUID. The easy way is to manually link the wanted list to a Access database and open the linked table in design view, the Description property of the linked table will contain the link chain requirement. Obviously, this is less useful when you need to be able to link to arbitrary lists, however. In that case, the interface can use the SharePoint Web service method Lists.GetList expurgated one. This method takes the name from a list at a given location and returns the detailed information, including the GUID that identifies the list.
 

What is SharePoint workflow life cycle

Cycle SharePoint workflow is very unique to the SharePoint environment. As mentioned SharePoint workflow are always related in a context with a SharePoint content as a list or document.

Partners: - As said in SharePoint workflows has always spoken in the context of a content type. So the first step is to associate a workflow with a content type as a list or document.
Start: - The second step is to start the workflow instance. Workflows are just finally classes, so that a workflow instance should be created to initiate the workflow in action.
Edit: - Later, the workflow instance is modified through the stages of workflow.
Full: - Finally, the workflow object is finished.






The web forms share point to interact with WSS, which in turn interacts with the flow runtime Windows work. The runtime Windows Workflow past the details to the instance of appropriate workflow based on information received from WSS. The instance of SharePoint workflow then run the workflow logic and take appropriate measures accordingly.

Basic guide to SharePoint workflow

The first important point to note is based workflow SharePoint and Windows are separate entities. The foundation of SharePoint workflow is the workflow window. In other words, the SharePoint workflow is at the top of Windows Workflow and adds the flavor of human workflow. The following graph reflects the broader definition of workflow in SharePoint. It requires the basic workflow of Windows. NET and then apply the workflow focused on the content in it. Content Workflows Windows Workflow dedicated just not attached to the list, documents and custom content.

You can envision sharepoint workflows as windows workflow with human workflow touch and feeling. The human work flow affect and feel comes when the work flow is attached to a content type like list, document etc.
For example, suppose we have approve and disapprove windows workflow. You can connect the workflow with a content type of students and human workflow for student becomes a student and the student. If the content type is a bill, then pass the workflow can be a workflow and disapprove paid the bill may become the unpaid bill.
In other words sharepoint workflow is content centric and they depict human work flow.

Steps to create work flow using SharePoint designer

• Create a team site using the sharepoint team site template.
  
• Create two of a task list is incomplete task list and another list of tasks completed. To create the list, click Create a site of action: - Add a new library to create a task list
  
• Start the Sharepoint designer.

• Open the site in your sharepoint designer using click on file à open site.

• Go to workflows by clicking on file à new à SharePoint content and click ok as shown in the below figure.

• This is an important step. In this step we define two important things first is this workflow be attached to the list. Currently we have a workflow attached to the list of unfinished tasks. Second, we must define the events that the workflow must be activated. For the current scenario, we considered two events, one when the item is created and the second when the item is updated.

• This is a crucial step further when we have to define the conditions under which the workflow will run and what action should be performed if the condition is true. So when a state of the task is completed then two actions will be carried out. First, the task will be copied from the list of unfinished tasks in the task list completed. Second, the task is removed from the list of unfinished tasks.

 

• 
  
  

  Once you click Finish, you can see the workflow created in the share point designer. This workflow will also be posted on the SharePoint server,

  
  
  

You can see if the workflow is associated with the list of unfinished tasks. Go to the unfinished tasks of configuration settings from a list of configuration options workflow, you can see the workflow joins the list of unfinished tasks. · Ok, now it’s time to see the work flow in action. So go to incomplete task list and create a task with status completed.

Work flow by using SharePoint designer

Sharepoint designer helps us to make workflows and bind the workflows to a content type like list , document etc. In other words Sharepoint designer make workflows and publishes the workflow on the sharepoint server site.

To understand it improve we will build a simple work flow of complete and uncomplete tasks. We will Make two lists one is the incomplete tasks and the other the completes tasks. The workflow will flow something like this. · User can create a task and enter the task status.

• If the task is not going to happen incomplete.

• Once the task is marked complete. The task will be copied from the list of incomplete tasks to complete the task list.

• The task is removed from the list of unfinished tasks.

So let’s understand the eight important steps we will need to create the above work flow using Sharepoint designer.

SharePoint integrated with ASP.NET 2.0

One of the things we did with ASP.NET 2.0 was to work real close with the SharePoint and CMS teams within Microsoft to change much richer architectural and creator integration than we had with previous releases.

Specifically, we have tried to carry many of the basic architectural requirements and scenarios they and other portal / CMS had vendors at runtime ASP.NET 2.0 (eg Web Parts, providers of virtual path and compilation, site navigation, membership and role management, personalization, etc.). The SharePoint / WSS / CMS Teams are then building their new releases on top of these APIs in ASP.NET 2.0 - and have the Beta2 versions of these applications soon. This will enable developers. NET to learn and master a single core set of APIs and readily re-use this across any type of web applications that are building - if this is a SharePoint portal, a CMS application, or a completely custom ASP. NET Web.
A few of the many cool extensible scenarios this changes.

You can now build a network of party control that supports drag and drop user-personalization and adaptation and use within any vanilla ASP.NET 2.0 application or host within a SharePoint 2007 or Windows SharePoint Services ( WSS).
You can build a class library, control, or page using the composition, role, profile, or web browsing and re-use API through the implementation of both a custom ASP.NET and SharePoint / CMS site. SharePoint will ship with a bunch of SharePoint providers that plug-in using the standard ASP.NET 2.0 Provider API (eg a supplier of ships that integrates SharePoint SharePoint page and models from the list in 2.0 ASP.NET Site Navigation API). This means you get * much * more mileage with your code, and can re-use their knowledge of the API for more projects.
You can plug-in your own tradition suppliers to extend SharePoint and WSS results just like you would vanilla ASP.NET 2.0 sites. Because SharePoint uses the standard ASP.NET 2.0 APIs for things like Membership, this means you can now easily exchange the authentication mode and membership storage for SharePoint solutions (previous versions required Windows Credentials. In One post it was using the default ASP.NET Membership Provider to change Forms Authentication for a SharePoint site. What is cool is that you could actually plug-in *any* ASP.NET membership provider and have this scenario work. You can also now download the source-code to the built-in ASP.NET providers, customize them or write your own, and then add them to a SharePoint or WSS solution.
Best of all, it means that you can also start more projects using SharePoint or WSS (Note: Windows SharePoint Services is a free download and can be deployed free of charge with Windows Server), and quickly create a solution with rich document management and support for collaboration and integrated (including client Office tool support) - and then be able to customize and further improve the use of ASP.NET 2.0 and VS 2005 skills you already know.

We believe all of this consolidation will allow a handful of really cool scenarios for developers. NET in the future. It also helps to validate and drive requirements to API in ASP.NET to send y. NET Framework, and ensures that they provide all the hooks needed to build great feature rich applications on top of them (with the Office Division starting to build on top of the new ASP.NET 2.0 API for two years that really drove a lot of great improvements and enhancements to its extensibility and ability).

Sharepoint solution deployment and configuration guide

Introduction
This guide will walk you through the steps to deploy and configure “Number Research” sharepoint solution into a new server.

Pre requisite

• New Sharepoint site collection must have been created with defined URL.
  
• Application portal must have been restored from Development server into new server.
  
• Site navigation must have been restored to the new site collection.

Web parts and class library DLL list
Below listed DLLs are deployed in sharepoint server’s BIN folder when we install the sharepoint solution.
Web part DLL files (Naming convention is NOT required)
1) ABCTopHeader.DLL : To display filter controls
2) ABCReportViewer.DLL : To display SSRS reports.
3) ABCContentWF.DLL : To display WF Content
4) ABCReportMDM.DLL : To show all Business groups
5) MDMReportMDMBrands.DLL : To maintain brands
6) ABCReportMDMSiteDomains.DLL : To maintain Site domains
7) ABCETLDataManagement.DLL : To maintain data mapping
8) ABCETLMonitoring.DLL : To monitor data sufficiency
9) ABCArchivedReportsLink.DLL : To display Archive PDF list.
10) ABCReportMDMDataInput.dll : To insert / update traffic data
11) ABC_RDLCaching.DLL : To reset the SSRS RDL caching minutes
12) AchiveReportByForce.DLL : To create / update archive PDF file

Class library DLL files (with naming convention)
13) ADS.NumberResearch.Workflow.DLL : Custom workflow engine.
14) ADS.NumberResearch.PollingAgentClassLibrary.DLL : Polling agent objects.
15) ADS.NumberResearch.INABCReports.DLL : Report viewer class objects
16) ADS.NumberResearch.DBAccess.dll : Database access objects
17) ADS.NumberResearch.ArchiveReport.DLL : Archive report class objects

Sharepoint Solution deployment
Deployment is done in 7 steps.
1) Install Sharepoint solution in the already created SharePoint site collection.
2) Activate Sharepoint solution in site collection.
3) Create user groups in site collection
4) Update configuration files.
5) Restart IIS.
6) Assign site access permission to admin user.
7) Assigning permission to “Executive summary content list”

Step 1: Installing SharePoint solution (.WSP)

Installing Sharepoint solution file name: ABCSol.wsp
Ø This is a navigation configuration file.
Ø This solution contains web part files and class library DLL files also.
Installer EXE file name: STSADM.EXE
Ø This file can be found at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN Path on Server machine.
Installation command syntax: STSADM.EXE -o addsolution -filename %SOL_FILE%
Installation command: STSADM.EXE -o addsolution -filename ABCSol.wsp

Step 2: Activating SharePoint solution (.WSP) in portal

Installer EXE file name: STSADM.EXE
Ø This file can be found at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN Path on Server machine.
Installation command syntax: STSADM.EXE -o addsolution -name %SOL_NAME% -url
%PORTAL_URL% -immediate –allowcaspolicies –force
NOTE:
%PORTAL_URL% : Site Collection URL Ex: http://Number-Research:9999
%SOL_NAME% : ABCSol.wsp (Name of solution file)
Installation command: STSADM.EXE -o deploysolution -name ABCSol.wsp
-url http://Number-Research:9999 -immediate –allowcaspolicies –force

Step 3: Creating user groups in site collection

Installer EXE file name: STSADM.EXE
Ø This file can be found at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN Path on Server machine.
Note: We need the following Groups in site Collection.

Admin Owner : User in this group can access Admin Site
Admin User : User can Updated any Content
APPROVERS : User can approve workflow
EDITOR : Users can edit/write contents for reports/workflow
ABC OWNERS : Users are administrator of complete Site Collection (by Default)
VIEWERS : Normal User (by Default Created in Site Collection)
Installation command syntax: STSADM.EXE -o createGroup –URL %PORTAL_URL% -name
%Group_NAME% -ownerlogin %OWN_NAME% -type member
NOTE:

%PORTAL_URL% : Site Collection URL Ex: http://Number-Research:9999
%Group_NAME% : Name of new group Ex: EDITOR / APPROVERS / Admin Owner
%OWN_NAME% : Name of parent group which can manage users in this group

Installation command: (Replace the URL with actual value)
STSADM.EXE -o createGroup –URL http://Number-Research:9999 -name “Admin Owner”
-ownerlogin “Admin Owner” -type member
STSADM.EXE -o createGroup –URL http://Number-Research:9999 -name “AdminUser”
-ownerlogin “Admin Owner” -type visitor
STSADM.EXE -o createGroup –URL http://Number-Research:9999 -name Editor
-ownerlogin “Admin Owner” -type visitor
STSADM.EXE -o createGroup –URL http://Number-Research:9999 -name Approvers
-ownerlogin “Admin Owner” -type visitor

Step 4: Updating configuration files

Configuration files to update: 2 files

1) App.config
o Contains all the key elements required for Database Connection, User Names and SSRS configurations.

Note: This file must me checked/changed element by element as per new deployment environment.

2) Web.config
o Contains security configurations for site collection and other required key elements.
4.1) Update app.config

i) Change the following important key element values as per the new server configuration.
SharePointUserName => User name which has access to
Sharepoint web services
SharePointPassword => Password of the user name
SharePointDomain => Sharepoint domain name
SharePointHost => Sharepoint site URL.
SiteLinkUrl => Sharepoint site URL
ConnectionString => Database connection string
AdminUsers => List of admin. users’ email.
ReportRDLServerPath => URL of “ReportViewer.aspx”
ReportRDLServerWebServiceUrl => URL of “ReportService.asmx”
ReportRDLDeployedPath => RDL deployed path will normally be
“/Number/”
ii) Copy this file to the same location as web.config file
(Please see the Web.config file section below, to know about the location of it)
This configuration file will be referred in web.config file.
4.2) Update web.config
Location:
C:\Inetpub\wwwroot\wss\VirtualDirectories\%SITE_COL_PORT%
EX: For http://Number-Research:9999, web.config will be in C:\Inetpub\wwwroot\wss\VirtualDirectories\9999\
Update <appSettings> and <trust> elements
i) Point the <appSettings> element to app.config as shown below.

ii) Assign the trust level value to the newly created “Trust Level”.

Now portal is ready for operation.

Step 5: Restart IIS

Since solution is deployed and configuration files are changed, we must restart IIS.

Step 6: Assign site access permission to admin Owner at ADMIN Site

Remove the permissions of all user groups except from admin owner.
6.1) Open the portal in browser, and go to Admin Site.
6.2) Click the Site ActionàSite SettingsàPeople and Groups


6.3) Click the link Site Permissions

6.4) At Permissions Page, Click the ActionàEdit Permission


It popup a confirmation box, click on OK button

6.5) Now select all the permission, except ‘Admin Owner’

6.6) Click ActionàRemove User Permission


It popup a confirmation box, click on OK button.
Now Site is accessible ONLY to admin owner user.

Step 7: Assign permission to “Executive summary content List”

7.1) Open the portal in browser.
7.2) Navigate to [Site Action]à[View All Site Contents]


7.3) Open the List named ‘Executive Summary Content List’


7.4) Click [Settings]à[List Settings]


7.5) Click the link ‘Permissions for this list’

7.6) Click [Action]à[Edit Permissions]


7.7) Confirm the editing by clicking OK button



Here we need to provide the Contribute Permissions to all Groups which can View/Edit/Approve the workflow contents. Ex: see the Viewer Group


It has “View Only” Permission and hence we need to assign Contribute Permission.

7.8) Click the Viewer Group.


Select the ‘Contribute’ Permission and Press OK button


Repeat step 7.8 to assign “Contribute permissions” to below listed user groups.
APPROVERS
EDITOR
VIEWERS


Now Site is ready for operation.

Promoting Widget Builder, New Home Page, Site Theme and Ad Category Multi View

Introduction

This guide will walk you through to deploy Widget Builder Solution, New home and Master Pages, Lists and ASPX pages in existing Staging and Production portals.

Pre requisite

For STAGING Promotion

Staging Sharepoint site http://adsportalstg/sites/numberresearch/ should be active.

For PRODUCTION Promotion

Production Sharepoint site http://NUMBERCALCULATOR should be active.

Deployment steps:

There are 9 steps to implement the widget Builder, New Home Page, Site Theme and Multi-View Category ads in organizing site.

1) Run Sharepoint solution WidgetManagerWP.wsp to deploy new web part for Widget Builder

2) Uploading PersonalWidget.swf & Blank.swf

3) Backup and deploy Master Pages

4) Installing New Sharepoint Theme

5) Backup and deploy ASPX Page from Development Sharepoint site

6) Backup and deploy Lists from 8888 portal

7) Setting up new sites & Navigation

8) Applying Master page & Theme

9) Run Sharepoint solution ABC_FlexHostSolution.wsp to deploy existing web part for FlexHost

Step 1: Run Sharepoint solution to deploy new web part for widget Builder

1.1) New Sharepoint solution

Solution File : WidgetManagerWP.wsp

Files in Solution : a) WidgetManagerWP.dll (New Web part to Widget Builder)

b) Image files used in web part

c) JavaScript files used in web part

For STAGING Promotion

Deploy the new Solution “WidgetManagerWP.wsp” at Staging Sharepoint server.

For PRODUCTION Promotion

Deploy the new Solution “WidgetManagerWP.wsp” at Production Sharepoint server.

Step 2: Uploading PersonalWidget.swf & Blank.swf

We have to get the files PersonalWidget.swf & Blank.swf "FlexReports" document library in site collection, this file is used by WidgetBuilder as hosting of applications.

Step 3: Restore Master pages

3.1) Take backup of following master pages from development site http://numberresearch-dev:8888

NUMBERCALCULATOR_Default.master

NUMBERCALCULATOR_Default2.master

3.2) Restore the backup in Staging / Production portal.

For STAGING Promotion

Source (Development Sharepoint site) => http://numberresearch-dev:8888

Destination (Staging Sharepoint site) => http://adsportalstg/sites/numberresearch/

For PRODUCTION Promotion

Source (Development Sharepoint site) => http://numberresearch-dev:8888

Destination (Production Sharepoint site) => http://NUMBERCALCULATOR

3.3) Apply the master page as follows:

NUMBERCALCULATOR_Default.master => to Site Collection

NUMBERCALCULATOR_Default2.master => To Distribution site and sub sites

ABC Site and sub sites

Admin Site

New Brand Entry Site

Step 4: Installing new Sharepoint Theme

4.1) Deploy NUMBERCALCULATOR Folder

ð Unzip the NUMBERCALCULATOR.Zip files and extract the NUMBERCALCULATOR Folder under C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\THEMES folder of Sharepoint server.

4.2) Update Theme Configuration file (SPTHEMES.XML)

ð Edit the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033\SPTHEMES.XML file in text editor.

ð Paste the following code at the end of file.(See screenshot)

<Templates>

<TemplateID>NumberCalculator</TemplateID>

<DisplayName>NumberCalculator</DisplayName>

<Description>Custom theme for ABC Number Research Portal.</Description>

<Thumbnail>images/thwheat.gif</Thumbnail>

<Preview>images/thwheat.gif</Preview>

</Templates>

Step 5: Backup and deploy aspx pages

5.1) NUMBERCALCULATORHome.aspx ASPX page

For STAGING Promotion

Ø Export from http://numberresearch-dev:8888/Pages/NumberCalculatorHome.aspx

Ø Deploy in Pages Library of STAGING site collection portal.

Ø Apply the NUMBERCALCULATORHome.ASPX page as Welcome page of STAGING Site

For PRODUCTION Promotion

Ø Export from http://numberresearch-dev:8888/Pages/NumberCalculatorHome.aspx

Ø Deploy in Pages Library of Production site collection portal.

Ø Apply the NUMBERCALCULATORHome.ASPX page as Welcome page of PRODUCTION Site

5.2) WidgetB.aspx ASPX Page

Similar to Step # 4.1 export the page http://numberresearch-dev:8888/dashboard/Pages/WidgetB.aspx and import in corresponding site.

Step 6: Backup and deploy Lists

6.1) SPLAllUserWidgets list

For STAGING Promotion

Ø Export the “SPLAllUserWidgets” List from the site collection of development portal http://numberresearch-dev:8888

Ø Import the list in Staging portal http://adsportalstg/sites/numberresearch/

For PRODUCTION Promotion

Ø Export the “SPLAllUserWidgets” List from the site collection of development portal http://numberresearch-dev:8888

Ø Import the list in Production portal http://NUMBERCALCULATOR

6.2) SPUserOwnWidgets list

Similar to Step # 5.1 export “SPUserOwnWidgets List” and import in corresponding site.

6.3) Give access to list

Give Full access to the above list for all Users / groups.

Step 7: Setting up new sites & Navigation

For STAGING Promotion

Do steps 6.1 to 6.3 in Staging site http://adsportalstg/sites/numberresearch/

For PRODUCTION Promotion

Do steps 6.1 to 6.3 in Production site http://NUMBERCALCULATOR

7.1) Create Three new sites under site ABC

1. Executive summary

2. Number Download

3. Press Rankers

7.2) Move the following Lists & Pages from ABC site to its new sub sites:

Destination Sub site name: Executive Summary

Lists à

Pagesà

Destination Sub site name: Number Download

Listsà

Pagesà

Destination Sub site name: Press Rankers

Listsà

Pagesà

7.3) Apply Navigation

From following sites, apply the navigation settings shown in screenshot.

Sites:

/ABC/Executive Summary

/ABC/Number Download

/ABC/Press Rankers

/Admin

Setting:

Enable Show Pages in navigation settings.

Step 8: Applying Master page & Theme

For STAGING Promotion

Do steps 7.1 and 7.2 in Staging site http://adsportalstg/sites/numberresearch/

For PRODUCTION Promotion

Do steps 7.1 and 7.2 in Production site http://NUMBERCALCULATOR

8.1) Site Collection

The site should have applied NUMBERCALCULATOR_Default.master homepage NUMBERCALCULATOR Site Theme.

Note:- See the steps to apply Master page & Theme in section 7.3 & Section 7.4

8.2) All other sites and sub sites (Other than site collection)

Sites must have NUMBERCALCULATOR_Default2.master as master page and NUMBERCALCULATOR Site Theme.

Note:- See the steps to apply Master page & Theme in section 7.3 & Section 7.4

8.3 Steps to apply Master page to a site

Step 1. Open the site, where we need to apply the master page. Ex: http://numberresearch:8888

Step 2: Site ActionàSite SettingsàModify All Site Settings(see screenshot)

Step 3. At Site Settings page, in Look and Feel column click at Master Page

Step 4. At Master page settings Page, Select the appropriate master page for both Site Master page & System Master Page.

8.4 Steps to apply site Theme to a site

Step 1. Open the site, where we need to apply the master page. Ex: http://numberresearch:8888

Step 2: Site ActionàSite SettingsàModify All Site Settings(see screenshot)

Step 3. At Site Settings page, in Look and Feel column click at Site Theme link.

Step 4: at site theme page, select the appropriate theme and click the Apply button.

Step 9: Run Sharepoint solution to deploy existing web part for FlexHost.

9.1) Remove Existing SharePoint solution ABC_FlexHostSolution.wsp

9.2) Install Sharepoint solution for Top Filters Web part

Solution File : ABC_FlexHostSolution.wsp

Files in Solution : a) FlexHost.dll

b) ADS.NumberResearch.ArchiveReport.dll

For STAGING Promotion

Deploy the new Solution “ABC_FlexHostSolution.wsp” at Staging Sharepoint server.

For PRODUCTION Promotion

Deploy the new Solution “ABC_FlexHostSolution.wsp” at Production Sharepoint server.

9.3) Modify few properties of FlexHost web part

9.3.1) Go to distribution report => Performance by Individual Partner Report

9.3.2) Go to Site Actions => Edit Page

9.3.3) Go to Property window of FlexHost web part

9.3.4) Modify following properties for this report

• Height => 3600 Pixels
• Width => 1300 Pixels
• XYZ Report Formatting => Report Height => 3550
• XYZ Report Formatting => Report Width = > 1250
• XYZ Report workflow Settings => 18