Ajay's profileAJ's BlogBlogLists Tools Help

Ajay Mistry

Occupation
November 17

New Home..

I have recently started a new role with Microsoft in the Consultancy Services division.

I will be writing my blogs at : http://blogs.msdn.com/ajmistry/

August 04

Can't report Site Usage Stats on SPS 2003/WSS

I been given a task to maintain a SPS2003 Portal.
 
I was asked to give some stats on the Site Usage for newly launched Discussion form. 
 
Thinking this would be a walk in the park, I go to relevant admin area to generate some reports, I first find out that the Usage Analysis Prcoessing option was not switched on since the portal has been live (nearly a year!), hence no stats been logged! :(
 
So I switch on the logging and also enable anlysis processing to allow the SPSTimer Service to process the logs overnight - this only generates reports on the last 24hrs.
 
I come back in the morning expecting to see some usage data by viewing through the View site usage data link in the Management and Statisitics section of the Portal Administration, to my horror I see:

Use this page to view a detailed usage report for this Web site. The report does not include data for sites under this Web site. To see detailed data for these sites, see their corresponding usage reports. For usage information on all sites in this site collection see the Web site collection usage summary.
A usage report is not available for this site. Usage processing may be disabled on this server or the usage data for this site has not been processed yet.
 
Now I wondering whats going on!! Check in the logs directory to make sure SPS is writing the logs, and it is.
 
I do some googling and come across a blog article by Jeff Cate which explains why Site Statics page keeps coming to a blank, see below:
 
There are pages available in Windows SharePoint Services that will allow you to obtain usage statistics for WSS Sites. However, this is not the case for Areas in SharePoint Portal Server 2003. There are no built-in hyperlinks in the Admin pages for viewing usage statistics for a give Area.

Does this mean that usage statistics are not available for Areas in SPS 2003? No, it just means that you have to know a backdoor URL to get to the pages that display the stats. Here is the format of the URL:

http://{your portal name}/_layouts/1033/usageDetails.aspx

This URL will take you to a usage statistics page for the Home Area of your portal. (Note: the 1003 is the designator for you language, so it will be different if not using U.S. English).

If you want to look at usage statistics for a Subarea, for instance, News, you would modify the URL to look as follows:

http://{your portal name}/News/_layouts/1033/usageDetails.aspx
 
Happy analysis!
 
 
Happy Days!! I am now seeing my Site usage Stats!!!
February 08

CS2002 & 64-bit, .NET 2.0, and SQL2005

via Ryan R. Donovan's:

A frequently asked question that has come up quite a bit lately is what is Microsoft's policy going to be on supporting .NET 2.0, SQL2005, and 64-bit Windows with CS2002. I figured this was worthy of a blog post...

The short answer is that there are currently no plans to support any of these. If you want to use these platforms, you will need to use CS2006.

The longer answer is that there are A LOT of collective changes in these three platforms. CS2002 is an old product rapidly approaching its fourth birthday. It took the team several months worth of work to get through it all and at times it was not an easy task. All of this work is done and in CS2006. Right now, I honestly don't see us back-propagating these to CS2002 given the other things that still wouldn't be there (like integration between our Profiles and ASP.NET 2.0, etc.).

However, you can still run .NET 2.0 on a box with CS2002 in a .NET side-by-side configuration (.NET 1.1 is installed and the CS-specific applications are using 1.1).

------------------------------------------------------------------------------------------------------------------------------------

 

I guess this is not good news for companies planning to move a MSIB 2.5 (MCMS 2002 & CS2002) website over to a SQL Server 2005 / ASP.NET 2.0 or a Windows 64 Bit enviornment.

It will mean investing in the new CS2006 which will be out this year.

As for MCMS 2002 with SP2 it will support ASP.NET 2.0 and SQL Server 2005. SP2 also supports x64-compatible versions of Microsoft Windows in 32-bit emulation mode.

SO what does this mean for CS 2006 and MCMS vNext/ Office 12 integration. Will Microsoft come out with a new MSIB Toolkit or a connector?

February 06

Another undocument approach..

I came across a blog which demonstrates how to Create Resource Galleries programmatically, this is a totally unsupported by Microsoft and could lose your support with them on the product.
 
There is no way with the current MCMS API to allow you to create Galleries on the fly.
 
I am sure this feature will be availabel in the vNext version of MCMS/O12.
 
Another similar approach by Cubik to create Galleries programmatically.
January 27

How to switch MCMS databases programmatically

Stefan has come up with a great hack to switch MCMS Databases, this will be great when you are working with multiple test databases!
 
via Stefan:
 

Today I received the question if it is possible to script the actions of the DCA when changing the MCMS database. This can be extremly useful in developer environments where users develop against different databases.

Actually the DCA cannot be scripted but it is possible to backup and restore the configuration settings the DCA does in the registry. To ensure that no side effects show up (especially with MCMS node cache coming out of sync) it is require to restart all MCMS services while changing the database configuration settings.

The following steps will do the job:

  1. You need to manually configure the database using the DCA.
  2. Then export the following registry key into a .reg file:
    HKEY_LOCAL_MACHINE\SOFTWARE\NCompass\Resolution Content Server\Configuration\0\Local\Database
  3. You need to repeat this for every database to get a reg file for every database configuration (e.g. DB1.reg, DB2.reg, ...)

To switch to another database you now need to do the following:

  • IISRESET /STOP
  • NET STOP AESecurityService
  • REGEDIT /S DBx.reg                              <--- here you need to pass in the registry file for the desired database configuration.
  • NET START AESecurityService
  • IISRESET /START

MCMS vNext - new terminology

Mark has posted information about the new terminology going to be used in the next version of MCMS.
 
 
As part of MCMS vNext becoming a component within O12 Server, there has been a need to change the name of some of the core entities to be consistent with the SharePoint technologies.

Here are the new names to learn :
  • Posting -> Page (see below)
  • Channel -> Site (see below)
  • Template -> Page Layout + MasterPage
  • Template Definition -> Content Type
  • Placeholder -> Field Control
  • Placeholder Definition -> Column Templates
  • Channel Structure / Top Level Channel -> Site Collection
  • Template Gallery -> Master Page Gallery
  • Resource Gallery -> Image Library ; Document Library
  • Resources -> Images in the Image Library; Documents in the Document Library
  • Site Manager -> Site Manager Tool (now web based !)

With MCMS / SharePoint today we have three types of containers - MCMS Channels / SPS Areas / WSS workspaces. vNext will introduce a single new container (a Site) that provides a superset of all existing functionality.

An MCMS web page (previously a posting) will be stored as a WSS list item (in a list called Pages). The MCMS placeholder content will be stored in the columns in the WSS list item. By storing the MCMS content within a WSS List, we can have same consistent workflow / metadata / versioning / checkin-out that SharePoint utilises.

January 23

MS Commerce Server 2006 Beta.

There has been further developments to Commerce Server, they have now released a beta version of 2006.
 
MCS2006 Beta available
 
You can get further information on Commerce Server 2006 from :
 
 

MCMS vNext information

There is a lot of information emerging about the next verson of MCMS and Office 12 in past few weeks, here are some links below:
 
Mark Harrison (MS):
MCMS/O12 vNext -
 
MCMS migration to vNext - early adopter opportunity -
 
Arpan Shah:
Microsoft CMS Futures
 
Content Management Server and SharePoint (Office 12 Blogs)
 
Microsoft Enterprise Content Management (ECM) white paper-
 
 
September 30

Utility for searching a substring in MCMS

via Jawad:
 
I have created a Windows App utility that can search All or Specific Portal for any particular string to be found in any of the placeholders.
 
Download utility : MCMS Search Utility
 
September 28

Using CompareHTML to compare postings

 
CompareHTML is a component which ships with MCMS which can be used to compare two postings. This blog explains how it can be used to compare two postings. It can be extended as needed.
September 27

Programming the Commerce Server Product Catalog System

 
This is the first in a series of posts on how you can program the product catalog system. The product catalog system that shipped in Commerce Server 2002 provided three programming models:

1. The Catalog Com objects :  These are a set of objects which allow you to perform management and runtime operations on the catalog system. These were implemented using COM and they communicate directly with the SQL server. Methods on this object were intended to be called from VB scripts, ASP, ASP.Net, C++ etc (COM aware) clients.

2. The Catalog PIA : These are a set of objects in the Microsoft.CommerceServe.Interop.Catalog namespace which wrap the Catalog com objects and can be used to program the product catalog system from managed clients. To know more about PIA's see this link. Methods on these objects were intended to be called from managed clients.

 3. The Runtime BCL: These are a set of objects which were provided to  program the catalog system from your web sites. These types reside in the Microsoft.CommerceServer.Runtime.Catalog namespace and  provides methods to access the run time functionality (readonly operations) of the catalog system. Internally though these objects call methods on the PIA but expose a consistent, flexible and easy to use programming model from your runtime commerce server sites.

4. Web services model : The Commerce Server 2002 feature pack further extended the programming model by allowing the product catalog system to be managed by a catalog web service.

September 23

Pimp My PSP...Please!

Well if Xzibit needs a challenge on the next Pimp My Ride is to drop the cars and take on the Pimp My PSP challenge!
 
Here is the first - Baby Phat PSP by Simmons Jewelry Co.
 
Check the specs:
The Baby Phat by Kimora Lee Simmons piece is made with one pound of gold and 8ct yellow and black diamonds on the front and crock finishing on the back.
 
Baby Phat and Phat Farm logos accented with Simmons Jewelry Co diamonds dangle from the bottom of the luxurious accessory. The $35,000 design easily fits over any PSP to add extra bling.
 
Pictures:
 
 

Atlas

To get you started on Atlas development, some useful MSDN links:

    Also if you haven't heard Telerik have launched r.a.d callback, a suite of AJAX-enabled UI Controls. I would love to implement this into a MCMS website, like a navigation control.

     

    1.02

    r.a.d.callback is a suite of AJAX-enabled UI controls, which allow you to update page content without postback and loss of scroll position. The short response time combined with the smooth interface transitions results in superior users experience and level of interactivity, which can only be found in desktop applications.

    Tracking Rita

    This site includes a Google hack that combines Google Maps with hurricane tracking data, for a comprehensive view of Rita's activities.

     

    Google Maps  of Storm Rita

     

    September 22

    WSS Templates - Applications for Windows SharePoint Services

    These application templates are tailored to address the needs and requirements for specific business processes or sets of tasks for organizations using WSS.
     
    Templates to download:
     
     Absence and Vacation Schedule
     Board of Directors
     Case Work Management
     Change Management
     Classroom Management
     Competitive Intelligence
     Employee Activities Site
     Employee Timesheet and Scheduling
     Employee Training
     Event Coordination 
     Expense Reimbursement
     Help Desk
     HR Programs and Services
     IT Developer Team Site
     Legal Document Review Workflow
     Loan Initiation Management
     Marketing Campaigns
     Meeting Management
     New Product Development
     Performance Review
      Professional Svcs Contracts
     Professional Svcs Site
     Project Team Site
     Public Official Activity
     Public Relations Work Site
     Publication Editorial Review
     Recruiting Resource Center
     Request for Proposal Management
     Room and Equipment Reservation
     Travel Request
     
     

    10 great things about the next version of SharePoint Products and Technologies and CMS

    via Stefan:

    Arpan Shah, Product Manager for MCMS and SharePoint has provided a nice list of his personal top 10 features in the next version:

    There's a lot of great buzz in the community as well as Microsoft around the next version of Windows SharePoint Services and Office "12" servers. The amount of investment that's going into these technologies, if it wasn't obvious at PDC, is tremendous. I thought I'd take a moment to share with you my list of the top 10 favorite "things":

    - Security/Auth "stuff" from supporting the ASP.NET 2.0 authentication provider model and security trimming to single item security. :-)
    - Built on top of Whidbey - support for ASP.NET 2.0 web parts, nav/auth provider models, master pages :-), and more
    - SPS/CMS integrated architecture from end-user to development and deployment
    - RSS, Wikki and Blogging support.. the RSS support is especially great w/ the new version of Outlook... or any RSS reader really
    - Content types - very cool and super useful.. define a content type that includes metadata and actions
    - Recycle bin - IT orgs will love that
    - Lists - things like eventing support, scalability
    - Search investments - relevancy and User Experience are fantastic
    - ECM investments - from content creation, sharing, searching, publishing to retaining
    - Workflow based on Windows Workflow Foundation

    There's a lot more... but I thought I'd list my top 10. I bet Fitz's top ten is more developer focused... and Mark's top ten is more solutions focused... mine is more of a mix of everything.

    If you're already developing SharePoint solutions - your web part investments with the current version -will- carry on to VNext.

    If you're a CMS customer, there's a lot of great things in the next release. However, there are some architectural changes. So, I recommend taking a look at the best practices whitepaper that I listed in my previous. On SP2 and Beta availability, we'll have more guidance on how to prepare.

    September 20

    Debugging Web Applications using Web Development Helper

    via Nikhil:

    I demonstrated some features of the latest version of my Web Development Helper during my PDC session. Version 0.8.1 is now published and available for download.

    The tool is implemented as an Internet Explorer browser helper object. When installed, it provides a console window at the bottom on the IE window, and can be launched using the View | Explorer Bar, or Tools menu. This is a pet project that I work on during my spare time. It started as a tool scoped to ASP.NET scenarios, but has evolved into something that targets Web applications in general. A number of features described below are useful for those developing AJAX-style, rich Web applications.

     

    Read more...

    September 16

    MCMS v.Next - The curtain has been lifted at PDC

    Exciting news on the vNext version of MCMS!
     
    via Stefan:
     

    Ok, finally some official information next version of MCMS has been officially anounced and presented at PDC. Here is a short summary of everything that has been anounced so far:

    • Next version of MCMS will be build on top of WSS in Office 12
    • ASP.NET 2.0 features like Masterpages will be leveraged
    • Plugable Membership and Role providers allow authentication against any 3rd party authentication source
    • Plugable Navigation Providers allow easy to build navigation for your website
    • Improved Content Deployment Concepts
    • Improved Caching
    • Publishing Content from documents in a SharePoint document library through an extensible converter framework
    • Build in Search capabilities
    • Extensible Workflow through use of Windows Workflow Foundation (WinFX)
    • Automated Content Migration from MCMS 2002

    MCMS Manager 4.3

    via Chester:
    This version includes

    1. Posting Revert.
    2. Resource Replace.
    3. Multiple posting Approve, Submit, decline etc...

    Download the newer version of MCMS Manager from here. Please post your feedbacks.
    September 15

    Atlas Architecture Overview

    via Nikhil Kothari's Weblog:

    I like to think of Atlas as an end-to-end framework, rather than simply being "yet another AJAX library". Atlas is designed to be an end-to-end application framework spanning client and server development, and the communication between the two. In addition it provides an application framework that enables developers to put together components, and wire them up together. It can be used both declaratively (using XML-script) and imperatively (using JavaScript). Finally it addresses how script functionality can be integrated into asp.net apps as well as HTML pages in a clean, and unobstrusive manner.

    In yesterday's talk, Shanku presented a task list application, and an overview of the architecture. This post will provide a similar overview of the architecture. On the left is a diagram of the architecture (hopefully it will convey Atlas' application framework characteristics).

    On the client, Atlas provides a set of scripts forming the Atlas Client Script Library consisting of the following:

    • Browser Compat Layer - This is where we abstract out differences between browsers, so that higher level functionality doesn't have to have if... else... code all over the place, or is at the very least minimized. Today we support Atlas running on Safari and Firefox.
    • Script Core - This is something that rightfully should have been part of JavaScript, but it isn't. It includes a set of type system patterns allowing you to use standard OOP constructs such as namespaces, classes, interfaces, inheritance, enumerations, delegates, and so on. The goal is to provide mechanism to encapsulate data, logic, behavior into classes much like you would in any other programming language, so as to enable a disciplined approach to scripting. In addition, we've added a number of more intuitive APIs to built in JavaScript objects to bring them closer to their .NET equivalents.
    • Base Class Library - This was inspired by the BCL in the .NET Framework. It consists of useful types such as StringBuilder, Debug, Event, and IDisposable. In addition, it contains our abstraction over XMLHTTP via WebRequest, and WebResponse (much like their System.Net counterparts). On top of WebRequest, we've built MethodRequest which allow calling into WebMethods defined on .asmx, and .aspx files, or any server class for that matter. This layer also includes serialization - specifically, our JSON serializer, though the intent is to provide other forms of serialization. Finally this layer contains services such as Profile and Authentication that integrate with the corresponding functionality back on the server. All in all, this provides familiar APIs to script code, thereyby making it easier to develop and read/maintain.
    • Component Model and UI Framework - This layer introduces the notion of components (types that can be self-describing of their object model). Components also participate in the dispose mechanism managed by a top-level Application class. Other features build on top of components and their OM descriptions. Specifically we have a parser for parsing script components persisted in declarative XML-script. Bindings allow wiring up components to transfer property values from one component to another (these bindings are "live" via change notifications). Actions allow performing work by calling into component methods in response to events raised by components. The UI framework features specific types of components: controls, behaviors, validators etc. Controls represent UI elements. Behaviors are a mechanism to attach additional semantics to existing controls (eg. Drag/drop). Validators, are like behaviors, but are meant to define validation rules associated with an input control.
    • Controls and Components - We have an early set of built in components such as Timer, and Counter and controls such as the usual set of form controls, ListView, and a map control (based on Virtual Earth) thrown in for some sizzle.

    On the server end, we built our Atlas framework bits on top of ASP.NET 2.0. It has three primary pieces to it:

    • Server Control Framework - We have defined a new control ScriptManager that manages the set of scripts sent down to the client, as well as any XML-script markup generated by server controls. Server controls can start to participate in this processing by virtue of implementing IScriptComponent. In addition to this core framework, we have server-side representations of various client component model types, and controls.
    • Web Services Bridge - This allows using both .asmx style and Indigo style .svc services to be used from client script (as well as WebMethods defined on .aspx pages, or any other referenceable type on the server dynamically registered as a Web service). In order to make it simple to do so, we automatically generate JavaScript proxies when the services are referenced via <script> tags. Secondly, we provide the necessary plumbing to process an incoming request with JSON-serialized parameter data, invoke the service method, and serialize the result using JSON to send back to the client script.
    • Application Services Bridge - We use the web services bridge to expose a few of the key ASP.NET application services. Specifically, we currently allow you to authenticate users (using the membership service), and to retrieve and update user data (using the profile service).

    I'll talk about our client services piece in the future. For now, I'll just say, its designed to be a mechanism to safely expose mechanisms for client script to integrate well with desktop functionality and other applications on the client.

    Over time, we intend to add a number of features, enhancements, and of course address feedback we get from you on top of this core architecture we have put in place. I'll be delving into details over time as well. What are the areas that interest you?

     

    Microsoft Unveils Web Design Tool Set

    via Bink.nu:
     
    LOS ANGELES -- Microsoft today unveiled Microsoft Expression, a suite of Web site design and graphics software that enables .Net developers to handle tasks similar to those that users of corresponding software from from Adobe Systems and Macromedia have performed for years.

    As expected, Sparkle Interactive Designer, a new tool for building 3D animation and graphics, is part of the suite. Eric Rudder, senior vice president of Microsoft's Server and Tools division, unveiled a prerelease version of Expression in his keynote speech at Microsoft's Professional Developers Conference here on Wednesday morning.

    In addition to Sparkle, Expression includes Acrylic Graphic Designer (a painting and illustration tool) and Quartz Web Designer (a layout and design tool for building Web sites). All of the current names for individual tools are Microsoft code names.

    Microsoft Expression is now available as a community technology preview; the company expects the suite to ship in 2006. Microsoft plans to make several more CTPs available before releasing a full production version of the suite.

    Continue At Source

    The Future of WSS, SPS and CMS revealed at PDC

    via Arpan:
     

    There were several large announcements made at PDC that are very relevant to SharePoint and CMS customers. I'm personally super excited about this and to be part of this. Microsoft revealed Office "12" - client and servers and talked about our investment in ECM. This is great news for CMS and SharePoint customers that there is one integrated architecture for end-to-end document and content lifecyle.

    Another huge announcement was the introduction of Windows Workflow Foundation - WinFX. http://www.msdn.microsoft.com/windowsvista/building/workflow/ Office "12" servers will build on this technology to provide some great workflow!

    A lot of CMS and SharePoint customers and partners are wondering what they can do to better prepare for the next version of the technology. If you are a CMS customer, take a look at the newly published whitepaper at: http://msdn.microsoft.com/library/en-us/dnmscms02/html/CMSDesigningCMS2002Sol.asp.

    If you are a SharePoint customer, make sure you follow guidelines published at: http://msdn.microsoft.com/library/en-us/odc_SP2003_ta/html/WSSSharePointCodeReuse.asp

    September 14

    Search for Blogs using Google Blog Search...

    Google has just launched a Blog Search Service....
     
    Go to Blog Search Home
     
     
     
     
     
     
     
     
    Now you can search and find all your favorite Blogs on the net!
     

     
    September 09

    Taperwire - Flat Speaker Wire

    This is what I been looking for.... I have a 6.1 Speaker Setup at home and the problem is running those dam wires along the skirting board or ripping the carpet up and then feeding the wires up the walls up to the wall mounted speakers, which sometimes can be a bit of a hassle and looks a mess, even with plastic cable trunking.

     
    Taperwire is a flat adhesive-backed speaker-wire that you stick to your walls and paint over:

    No drilling necessary. Just press Taperwire on the wall and attach your speakers and sound system. Hidden by paint, wallpaper or spackle, this paper-thin wire will go unnoticed. You can even lay it under carpets—no bulges!

    http://www.taperwire.com/