Solutions Customization and Integration – Part II

Update on this project… So far I am in the stages of selecting an Learning Management System (LMS) that is SCORM compliant and offers tools to manage courses, students, learning material and deliver it in a lightweight format. One of the biggest hurdles is selecting one that has an open API/SDK to interface with Flash Streaming Video and even synchronize content with the video – e.g. time coding frames etc.

As for the social networking and commerce tools, I have selected Community Server 2007 Enterprise and AspDotNetStorefront ML. Integrating both solutions should not be too complicated since they are both .NET 2.0 solutions, offer the entire source code with the license, and operate on IIS, SQL Server 2005, ASP.NET etc.

The biggest challenge with integrating these pieces is architecting a single sign-on model. LDAP and Active Directory are possible options, with the latter more in the headlights since we are working in a 100% Windows environment. ASPDNSF and CS 2007 can integrate fairly easily for the single sign-on, and since both are somewhat independent systems, there should be little effort to get that going.

The LMS solution will be more involved since we have to map data across the community site and LMS site (e.g. learning material, class forums and discussion groups, blogs on courses etc.). Table structures are fairly open and scalable, however we will very likely use SQL Server Replication and SSIS packages to handle the back-end integration and sharing of data across systems. On the user-facing site, meshing everything together will involve a blend of ASP.NET Master Pages (what CS 2007 uses), and XML/XSLT packages (what ASPDNSF uses), and possibly a customized Master Page and .ascx control architecture for the LMS solution.

The physical architecture that has been mapped out so far includes:

> 2 load balanced Windows 2003 Web servers – 200GB HD, 4GB RAM, 32-bit dual-core, RAID config.
> Single 64-bit SQL Server, 8GB RAM, 200GB HD.
> 1TB SAN (EMC or DELL) – blogs, photos and a subset of videos.
> Fibre Channel across all machines
> Load balancer, firewall etc.
> Content Delivery Network for bulk of Flash videos and larger photos

More details on these integrations in my next post…

Solutions Customization and Integration – Part I

When faced with a Web project, one always wonders: Someone must have done that before, right?

Almost always the answer is a resounding “Yes!”, and that puts you on the path towards purchasing, customizing and launching the solution to meet the project’s requirements.

Recently, I took on a project involving a “mash-up” of a Social Networking, eLearning and eCommerce site. How do you even start on a project like that? What are the implications and costs? These are only a few of the questions that come to mind with a project of this size.

Aligning Requirements with Solutions

After extensive online research, and referencing past experiences with projects of a similar nature, I finalized the foundation of the site down to 3 products: AspDotNetStorefront ML (eCommerce), Community Server 2007 (Social Networking) and Adobe Connect Professional (eLearning).

The biggest task is to start aligning the client’s expectations and requirements with what each of the products above offer “out of the box”, and to also produce customization points that will be required in the final site.

This process generally involves hands-on meetings, product demos, documenting and the like, all towards an effort to produce documentation outlining the User Experience supported with Use Cases and Business Requirements.

Design Phase

Approaching the design is probably one of the most challenging parts of any IT project, as it requires you to essentially build the solution on paper. However, in this situation we have to approach things a little differently.

Since we are not building everything from scratch, we have to create documentation that supports several key areas of the project:

• Integration Requirements – how each solution will integrate together and deliver functionality, such as “single sign on” and data sharing
• Customization Requirements – what parts of each solution need to be customized accross all 3 layers (UI, business logic, database)
• Physical Requirements – what type of hardware and networking equipment are needed to meet the demands of the site and each solution

These documents create a foundation for us to start the project and move towards the development phase with near 100% certainty as to what the final site should look like and function. Furthermore, these documents should dictate the tasks required by a developer to be heads down in the project without much concern on how everything should be done.

Next month I will post an update on this project, with details on how the design phase progressed.