NetworkedPlanet Blog

Web3 and Concepts for SharePoint 1.0 Releases Now Available

Kal — Fri, 30 Jul 2010 08:58:31 +0000

We are very pleased to announce the immediate availability of the 1.0 release of our Web3 Platform and Concepts for SharePoint products.

The Web3 Platform is our "next-generation" structured information server built on the foundation of topic maps but with support for Linked Data standards including RDF and the SPARQL query language. The Web3 Platform provides a fully-featured REST API making it possible to create applications in almost any programming language and to quickly and easily integrate structured information into existing applications and websites. The Web3 service provides full support for the topic maps data model and support for browsing content as Linked Data RDF as well as providing a SPARQL endpoint that implements support for querying topic map data as RDF as well as querying at the detailed topic map data model level.

Concepts for SharePoint is simply the best way to organise, search for and find content on a SharePoint 2010 server. It integrates with and extends the taxonomy features of SharePoint 2010, allowing users to create richly interconnected data models that reflect the business in which they work. Unlike the tags in a standard SharePoint 2010 taxonomy, the concepts in Concepts for SharePoint can be made available as published pages complete with links to other concepts and to related content across the whole SharePoint server.

Both products are available for evaluation. Download them now!

Using HTTP Verbs to describe Server Side Transactions

Graham Moore — Fri, 30 Jul 2010 07:21:14 +0000

One of the challenges of putting together a REST service is how to let clients make transactional updates that involve two or more resources. One approach to this problem is to create a resource that is 'a collection of transactions'. A client can post a representation of a new transaction to this resource. The transaction becomes a 'child' of the 'transactions' resource and can be accessed via a returned URL.

Making the transaction explicit is good as it allows the transaction to be addressed and its status checked, it also allows for the service to return immediately and process the transaction in the background.

This basic pattern is good but it has a drawback in that for each different system you build you need to define the transaction language.

Our solution to this is to use HTTP verbs, URIs and resource representations as the building blocks of our transaction language. A transaction representation contains a number of operations. Each operation contains information about its Method, e.g. POST, PUT, DELETE, the resource URI to operate on and the request body.

.. more operations

The server processes a transaction by looking at each operation construct and operating on it as though the request has come from a client. The only difference is that all of the operations listed occur in a single transaction.

Each operation has a local id. When an operation completes the return URL from the operation is bound to that identifier. The identifier can then be used later in the transaction. This is especially useful when you want to create two new resources and then associate them together all in the same transaction.

After a transaction is processed the representation can be retrieved. The representation contains the URLs of newly created resources, as well as an errors information that occurred when processing the transaction.

This is a very powerful model that removes the need to create a domain specific transaction language for different applications, can reuse existing resource processing code and is very descriptive.

For more information about this approach, download and review the REST service documentation for the Web3 Platform

New NetworkedPlanet Support Forums

Kal — Thu, 29 Jul 2010 10:40:46 +0000

We have added new discussion forums for support questions about NetworkedPlanet products. We hope that by having more questions answered on these discussion groups we can help our customers find the answers to common issues more quickly. The old route for support (email to support@networkedplanet.com) also still works but we would encourage people to post questions to the forum wherever possible.
The forums are available at http://support.networkedplanet.com/

SharePoint Module 3.2 now available

Jen — Tue, 06 Jul 2010 15:48:07 +0000

NetworkedPlanet are pleased to annouce the release of version 3.2 of the TMCore SharePoint Module.
The TMCore SharePoint Module is a tight integration between Microsoft SharePoint and the TMCore information management server that greatly improves the way information is organised, classified and located with Microsoft SharePoint solutions.
This new release includes all the features and enhancements of the SharePoint Module 3.1 hotfix 6, and is packaged to be installed on either SharePoint 2007 or SharePoint 2010.

Any future hotfixes to the module will be released for version 3.2 and no further codebase changes will be made on version 3.1.
The new version is available as an upgrade for all customers with a current maintenance contract. For more information and download details please email us specifying the version of SharePoint that you will be installing the SharePoint Module on.

Web3 Platform Beta Now Available!

Kal — Mon, 21 Jun 2010 16:26:01 +0000

The Networked Planet Web3 Platform is a complete solution for creating, organising and publishing structured semantic data. The Web3 platform stores and manages data in a schema less data store, allowing complete flexibility of the shape of the data stored.

This is the first public beta of the NetworkedPlanet Web3 Platform. This beta version is licensed for use until 31st July 2010. We are planning to refresh this Beta release on a regular basis up until the final 1.0 release is available. To keep track of update announcements please subscribe to the RSS feed of this blog.

TMCore EPiServer Module v6.0.0 Released

andyturl — Wed, 14 Apr 2010 09:06:12 +0000

TMCore EPiServer Module v6.0.0 is now for EPiServer CMS 6. This version of the module brings compatibility with CMS 6 and is only intended for this version of EPiServer CMS. EPiServer CMS 5 R1 and later is still supported by the previous TMCore EPiServer Module which is currently v3.3.0.40.

The minimum requirements for TMCore EPiServer Module v6.0.0 are;

- TMCore07 SP4

- EPiServer CMS 6

Customers with a current maintenance contract should contact support@networkedplanet.com to obtain the latest version module.

SharePoint Module 3.1 Hotfix 6 now available

Jen — Mon, 15 Mar 2010 10:06:14 +0000

A new hotfix package is available for version 3.1 of the TMCore SharePoint Module. This package addresses a small number of bugs and provides new features. The full change list can be found below.

Systems Affected

This hotfix should be applied to any installation of the TMCore SharePoint Module 3.1 downloaded before 15th March 2010. If you downloaded your copy of the software from our site on or after this date, the hotfix is included in the package and you do not need to apply it again.
To determine if your system is affected, check the File Version property of the assembly NetworkedPlanet.SharePoint in the GAC (browse to C:\Windows\ASSEMBLY, locate the NetworkedPlanet.SharePoint assembly, right-click and choose Properties. The File Version can be found on the Version tab above Description and Copyright). This hotfix updates the File Version of the NetworkedPlanet.SharePoint assembly to 2.1.6.0 - if the file version shown is greater than or equal to 2.1.6.0, then you do not need to apply this hotfix.

Pre-Requisites

Upgrade to TMCore SP5 (if running an earlier version) to avoid issues with faceted search components in the SharePoint Module.

Upgrade Instructions

1. Download the Hotfix 6 package.
2. The package is provided in a compressed ZIP file. Unzip the package on a machine in the server farm.
3. Upgrade the NPSharePoint.wsp solution. The exact command-line you use will depend on how you want to schedule the upgrade, but will be similar to:

stsadm -o upgradesolution -name NPSharePoint.wsp -filename NPSharePoint.wsp -allowgacdeployment -allowcaspolicies -local

4. Restart IIS and Windows SharePoint Services Timer

Change Log

ENHANCEMENT: Optimized update of associated topic fields to reduce the number of database writes required when saving a SharePoint list item.
Added more logging of SharePoint object close and disposal.
ENHANCEMENT: Added check to ItemUpdated event receiver to check whether a double event was caused by a check-in. If so, do not do processing for check-in events.
BUGFIX: Amended the site deletion code so that topics for sub sites are correctly marked as superceded if the site is the root site of a site collection. This allows the WebCleanUp timer task to successfully remove any topics of the superceded sites on its next run.
BUGFIX: Site deletion - if a site deletion fails in SharePoint for any reason, the WebCleanUp timer task that runs 2 minutes after the delete event will now also check whether the site still exists and if so set the psi back to PUBLISHED.

TMCore07 SP5 Released

Kal — Tue, 05 Jan 2010 09:02:19 +0000

NetworkedPlanet today announces the release of latest version of the TMCore topic map engine. TMCore is the premiere toolkit for developers on .NET looking to harness the full power of Topic Maps in their applications. Built from the ground-up using .NET technologies, TMCore provides a flexible set of APIs and builds on the robustness, scalability, performance of Microsoft's SQL Server.

The new SP5 release of TMCore07 fixes a packaging issue found with the SP4 release that may prevent the faceted search features of the TMCore SharePoint Module from working correctly. Customers having a current support contract or currently evaluating TMCore may receive TMCore07 SP5 free of charge.

For download details please email us at contact@networkedplanet.com.

SharePoint Module 3.1 Hotfix 4 now available

Jen — Thu, 10 Dec 2009 14:21:36 +0000

A new hotfix package is available for version 3.1 of the TMCore SharePoint Module. This package addresses a small number of bugs and provides new features. The full change list can be found below.

Systems Affected

This hotfix should be applied to any installation of the TMCore SharePoint Module 3.1 downloaded before 10th December 2009. If you downloaded your copy of the software from our site on or after this date, the hotfix is included in the package and you do not need to apply it again.
To determine if your system is affected, check the File Version property of the assembly NetworkedPlanet.SharePoint in the GAC (browse to C:\Windows\ASSEMBLY, locate the NetworkedPlanet.SharePoint assembly, right-click and choose Properties. The File Version can be found on the Version tab above Description and Copyright). This hotfix updates the File Version of the NetworkedPlanet.SharePoint assembly to 2.1.4.0 - if the file version shown is greater than or equal to 2.1.4.0, then you do not need to apply this hotfix.

Upgrade Instructions

1. Download the Hotfix 4 package.
2. The package is provided in a compressed ZIP file. Unzip the package on a machine in the server farm.
3. Upgrade the NPSharePoint.wsp solution. The exact command-line you use will depend on how you want to schedule the upgrade, but will be similar to:

stsadm -o upgradesolution -name NPSharePoint.wsp -filename NPSharePoint.wsp -allowgacdeployment -allowcaspolicies -local

4. Upgrade the NPOfficeServer.wsp solution. Use the following STSADM command:

stsadm -o upgradesolution -name NPOfficeServer.wsp -filename NPOfficeServer.wsp -allowgacdeployment -allowcaspolicies -local

5. Run the following stsadm command:

stsadm -o copyappbincontent

6. Restart IIS and Windows SharePoint Services Timer
7. Reactivate the NPDiagnostics feature by running the stsadm command:

stsadm -o activatefeature -name NPDiagnostics -force

8. Upgrade Enterprise Services to the version included with the hotfix, the new version of Enterprise Services is 1.1.2.0

9. Restart the Topic Map Index Service

Change Log

BUGFIX: One hop and two hop web parts were intermittently returning Deadlock errors. These have
now been changed to sleep and retry up to a maximum of three times when encountering
deadlock issues with the database.
ENHANCEMENT: Url Mappings can now feature more than one publish URL for a web application by using
the zones set up when extending the SharePoint web application.
ENHANCEMENT: Additional diagnostic logging has been added to Url Mapping. The NPDiagnostics
feature must be reactivated on the farm for this to take affect.
FEATURE: The stsadm remapurls command now has an optional parameter which when used skips the url
remapping on content type to topic type mappings.
NOTE: The new hotfix of Enterprise Services has been included with this hotfix. This fixes issues with
results display and ordering when using advanced faceted search restriction sets.

Enterprise Services 1.1 Hotfix 2 released

Jen — Thu, 10 Dec 2009 14:21:16 +0000

We have just released a new version of Enterprise Services available for download. This release changes the way topics passed in from a result set are processed so that the search results retain the ordering of the topics passed in.
Please check the instructions contained in UPGRADE.TXT for important information on the upgrade process.
Download the updated package .