Archive

Posts Tagged ‘SDF’

Momentum Vienna and The SharePoint Documentum Framework

November 5th, 2012 Comments off

This week is Momentum 2012 in the European capital of the waltz: Vienna. Of course, cultural heritage is large with the music from Strauss as well as the yearly débutante ball in the Hofburg. It illustrates that the Viennese Waltz is live and kicking as part of the Vienna culture. Waltzing is a very applicable way to illustrate the way Microsoft and EMC ‘dance’ together around information management. SharePoint and Documentum have learned to move gracefully through crowds of ECM without stepping on each others tows to hard and to often.

Dancing requires one to lead, usually the male, and one to follow and shine, typically the female. It’s not that simple to say that either SharePoint or Documentum is leading or following. That is largely dependent on your starting point — more on that later — although one could say that if you take the shallow outside approach, SharePoint is the sexy partner and therefore must take the female role: follow and shine. That leaves EMC as a leader.

If you dive a little deeper, the roles are not always according to the look and feel.
On a high level you can have two starting points: collaboration versus enterprise document management.

When you start from a collaboration point of view, SharePoint will be leading, the male role, and will perform the dance for its audience. That audience is looking for flexibility, tools that they know already — that is the MS Office suite —, as well as speed of change. This would leave the EMC suite as the female role. Following and shining. Off course I too had second thoughts about EMC being shiny, being sexy.

From the enterprise point of view, there is now doubt that Documentum steps up. The male and leading role. For years we learned Documentum was not sexy. But with D2 that changed fundamentally. And yes, xCP is also a step forward. Still, for the individual collaborator, its just not always good enough. Hence their love for SharePoint. From this angle it thus is the challenge to meet the needs of the collaborators somehow. That could well be SharePoint.

But let’s face it, dancing a waltz requires 2 partners. Documentum and SharePoint next to each other creates to silo’s of information and it goes beyond telling that such is a bad thing. They must be connected.

With SDF we can can make that happen. As EMC’s Consulting Preferred Partner (C3P) we know how to bridge those two worlds. Not only is such a matter of knowing the technical bits of the SharePoint Documentum Framework (SDF) but also the ability to help the customer bridge the two silo’s of people in their organisation. Those that want freedom to collaborate and those that want to control and meet compliance. Bringing those worlds together is what makes projects a success.

We at Informed Consulting are glad to help out. Just reach out. We may not all shine on the ballroom floor, we do in the Information Management arena.

Access Documentum content through SharePoint

October 7th, 2012 Comments off

Just recently I read an article by TSG about replacing external SharePoint sites with a simple cached approach providing Documentum access to external users. That solution was required to provide a selective view-only access to external users so they would only see the subset of quality documents applicable to them.

In the case provided by TSG, the external users do not need access to all quality documents, but need access to the specific documents that they are expected to follow for the business process. Previously numerous SharePoint sites were set up to allow external users to access the required documents. The client found that the work effort to maintain these separate copies and keep them up to date was very difficult and was looking for an easier way. The client was also concerned about the compliance risk of the SharePoint sites being out of sync with the Approved and Effective documents stored in Documentum.

The question is: is it in general the solution that you would suggest to a client that already owns both SharePoint and Documentum? I believe it’s not.

I believe that there is a better solution available: the SharePoint Documentum Framework.

First, the case given is a common case. In many cases you want to share and collaborate on a subset of documents. Indeed, clinical trials are an example of that. But also claims, customer files or tenders match that case.
Second, the concerns about compliance and separate copies are genuine concerns. Keeping copies in sync, though theoretical simple, is difficult. It needs full control over new, updated and removed documents and on top of that proper security mapping between two – now disconnected – systems.

So why not go the route that leverages existing investments and – more importantly – use the UI powers of SharePoint and the compliance powers of Documentum?

Let me share that route.

Documentum is very capable of managing all the documents, its versions and its meta-data in a secure and controlled way. This will guarantee that any user has only access to the documents that this user is allowed to read or edit. Regardless if that user is an internal colleague or an external client. A must for compliance.

Giving access to the customer through Webtop can indeed be challenging. OK, you won’t do that. D2, the alleged Webtop replacement, is by far better suited but still isn’t perfect.
The reason for that is related to the business requirements that you must expect when sharing documents with your client. Normally, next to sharing the documents as the main requirement, there are requirements like being able to interact (discuss, set tasks) and provide related collateral or instructions.

That’s one of the reasons why SharePoint comes into the picture. SharePoint is very capable of doing just that. But how to get the right documents available in this environment?

This is where the SharePoint Documentum Framework comes into play. This framework provides webparts that can query the Documentum repository for the right documents. And they honour the security set by Documentum. So, if you revoke access in Documentum, access is revoked in SharePoint. And as a bonus, you can set access to read-only even if the user has write access in Documentum. Not that I would recommend this as a replacement to setting the proper settings in Documentum.

The other interesting part of using these webparts is that your query leverages the available information about those documents in Documentum. So, if you’ve marked a document as ready for sharing with the client through its meta-data, it will meet the query parameters and show up in SharePoint. As soon as you change the meta-data so that it no longer is available to the client, it won’t show up anymore.

Oh, and important to some organizations: this is a productised solution supported by EMC and not a custom solution.

But regardless of that, the SharePoint Document Framework provides a flexible way to merge two systems that each lead in their own space. A case where the total is larger than the sum of the individual parts. A framework sold by EMC, implemented by preferred consulting partners like Informed Consulting.

If you want to learn more, don’t hesitate to get in touch!

The Momentum 2011 Perspective on EMC Documentum in Q3/2012

November 7th, 2011 Comments off

Current state

The 2011 Momentum has reached its end. In 12 months from now, we’ll meet again in Vienna.

When we do meet in Vienna, the Documentum world will have changed. Documentum D7 and xCP 2.0 will be generally available. C6’s D2 (maybe even X3) will be the configurable alternative to Webtop. EMC OnDemand will be running for many months all over the world. Developers, partners, deliver vApp solutions to run in both the private and hybrid cloud. Next to it will be SharePoint and Office 2013. Both running on premise and in the cloud (Office 365 or otherwise).

Off course, still a lot can happen in between, but let’s assume that nothing does.

What are partners going to do with this knowledge? What will the customer do with this knowledge?

Will they change their way forward? Will they behave like any mother and father to-be, when they learn that they are pregnant of a beautiful baby in 9 months from now? Will they start preparing for the delivery of this new-born?

I think partners will. For successful partners, adopting to change is part of their DNA.

But what will the customer do? Will she change and if so how?
I believe she will. I believe she has to.

The ECM world is changing rapidly. The business never stopped changing. Competition continues to find ways to close gaps and take leads. Not less important, demands from new joiners in your company are rapidly changing. It’s nearing the point that you want to work with them rather than that they want to work for you.

However, how she’ll change will depend upon her current state related to her ECM vision and ambition.

Several scenarios are possible and include common scenarios like “Continue as is”, or “Technical ‘as-is’ upgrade”.

One particular scenario that could happen is the scenario what I would like to call “re-think & re-do”.

The “re-think & re-do” scenario is an appealing scenario. It can be a game changer. It applies lessons learned, leverages new functionality, and re-implements the requirements in the new target environment.

The soccer analogy of “re-think & re-do”

There is a great analogy to be made with sports. Especially team sports. Let’s take soccer.

Winning the National league, the European Champions League, and the World Cup for Teams are goals for the top teams. Many want it, few get it.

The easy road of buying 25 of the best players doesn’t get you there. Many tried, none succeeded(1).
Building a winning team is a carefully designed growth path that takes effort and time.

On this route, every now and then a player gets injured for a longer time, leading to adjustments in the process. Patches are applied.
Sometimes players get better offers elsewhere and new players have to be bought or incorporated from youth teams, the labs. Sort of a Service Pack is applied.
And then success is there. The team is on a winning streak.

After some time the successes diminish. Competing teams catch up. The common game-play changes. The players on the team are over the hill, nearing their sports technical end of life.
At this point the team manager has to make decisions.

A common decision is that they accept the absence on the prime stage for a year and rebuild the team from scratch.

Where in the previous period, patches and service packs have been used to continue, this time a new major release is needed.

You see this happening in many of the Olympic team-sports (field hockey, volleyball) in the post-Olympic year. The next World Championships are typically 2 years away, the next Olympics 4 years. Enough time to re-do the team and go for success at the next major event.

The good thing about building a new team, a new major release for future success, is that it allows the team manager to apply the lessons learned from the previews period (re-think) as well as to recover from unwanted side effects that come with patches and service packs (re-do).

The lessons learned can be in many different forms. As an example:

  • The game-play may have shifted from physical to tactical and thus new requirements apply.
  • The common positioning on the midfield may have changed from 3 players on one line to 4 that are positioned in a diamond shape. In essence the functional team design is changed.

Also the side effects come in different forms with examples like:

  • Due to the absence of left-footed wingers, a right-footed player has become the left-winger.
  • The youngster, replacing a player that has left, is not performing consistently.

Taking these lessons learned as well as side effects into account, a new design is created to succeed in future success and the new journey begins.

The EMC reality

The process illustrated above for soccer, can be applied to Enterprise Content Management solutions like Documentum. There too, patches and service packs are applied until you reach the point where you have to re-think what to do with a next major release.

Given the announced release of Documentum 7 / xCP 2, the adoption of C6’s D2 user interface, the availability of Documentum in the Cloud (OnDemand), and also the omnipresence of SharePoint fits, the point of re-think and re-do has arrived. The time is here and now. Too much is and will change to continue as if it’s still the same.

This is a far from easy task and is highly dependent on the unique settings of the customer.

It takes time. It takes careful considerations. It needs a free spirit to not limit yourself to budget, resource, calendar, or any other constraint yet. It takes guts in a budget constraint business to acknowledge that maybe with the new facilities, something better, cheaper, more flexible, and more future proof is possible and that now is the time to find out. It requires expertise to take it to the extreme on paper and see what it brings, to think out of the box.

Because even finding out requires budget, some arguments to help you build the business case are given below.

EMC OnDemand

    • Supported by certified professionals on behalf of EMC; No need to invest in company resources.
    • Off premise in the cloud or locked down ‘all-in’ box on premise; No need to purchase hardware.
    • Sizing for average load with on demand resource expansion to handle peak loads; no need to invest in hardware that can cope with peak loads that occur only once a week.
    • Optimum module architecture through xMS, the requirement-based configuration descriptions that are used to generated the required virtual servers.

SharePoint

    • SharePoint is the users choice for collaboration and “work in progress” content management.
      Leverages the dominance of MS Office on the desktop and the user acceptance that comes with it.
    • SharePoint doesn’t (yet) provide the appropriate means to cover all enterprise needs, but SDF(2) is there to rescue. SDF, the SharePoint – Documentum Framework provides optimal bi-directional integration with Documentum to cover the enterprise needs.

C6’s D2

    • Reduce cost of customizations of Webtop by leveraging the configurable user interface that D2 delivers.
    • Replace Webtop with a much more tailored and applicable interface for those users that need functionality that is not provided through SharePoint or xCP applications.
    • Increase user acceptance with the appealing skinnable interface that D2 provides.

Documentum D7 / xCP2

    • Leverage the new deployment model that uses vApps.
    • Leverage the ability to reverse patches if the outcome has unwanted side-effects
    • Leverage the vast amount of documented functional patterns and solutions to build xCP applications.
    • Leverage the growing number of xCelerators to reduce implementation time and effort.

Non-technical

    • Replace old school designs and include lessons learned of the current implementation.
    • Start supporting the Knowledge Worker; Make it goal-driven and reduce the rigidness of traditional workflows.
    • Prevent the typical chaos that uncontrolled, non-governed SharePoint environments tend to create.
    • Take a controlled route towards the cloud by using on premise cloud technology.

Conclusion

I believe it’s here and now that you have the opportunity to re-think what your Documentum centric solutions add to your business and re-do them using Documentum & xCP through EMC OnDemand and integrate them with SharePoint through SDF.

If the signs are right, we’re expecting a beautiful baby somewhere in the late summer of 2012.
But, we have to work for that. It will not come easy.

The above mentioned arguments are not meant to be complete or generically applicable; further discussion is needed to incorporate the specifics of your organisation. That first step is yours. I’m sure you can do it!

 

Ed Steenhoek
ECM Solution Principal


 

  1. While writing this post, I was thinking about Manchester City. A soccer team where huge investments have been made in recent years but yet without success. However, after reviewing this post, it dawned to me that it is also applicable to Oracle. Oracle has been purchasing ECM technologies and companies but still doesn’t deliver a clear package that delivers success on its own – that is without cross selling from e.g. Siebel or the Oracle RDBMS – that matches the investments made.
  2. Implementing SDF requires a specialism that is provided through EMC Professional Services or directly from selected partners. Informed Consulting is proud to be that partner for EMEA.

SharePoint Documentum Framework

September 27th, 2011 Comments off

I was as reading through my old posts and saw the one about Documentum Sharepoint integration.
I felt there is something that I need to clear up: SDF is not available for just anyone.

EMC currently offers 3 products that can be used to integrate Documentum with SharePoint:

  1. MyDocumentum for SharePoint
  2. Repository Services for SharePoint
  3. SharePoint Documentum Framework

I mentioned all that in my previous post. There is a difference between the first second and third however. The first two are offered as products that you can just buy and install. The SDF is not officially offered as a separate product. It is a product that you can buy, but it is only sold as part of an implementation deal with EMC Professional Services. EMC will not let the customer, nor a partner do the implementation of SDF, unless they are subcontracting for EMC Professional Services.

For some customers this should be no issue. For others this would mean that using SDF is not really an option. Fortunately there are 2 other integration products to choose from.

Sander Hendriks

ECM Consultant

Documentum SharePoint integration

September 27th, 2011 Comments off

The Momentum 2010 session about SharePoint integration was on my list, because I’m currently working on an RFP where this is the major requirement. Some of the client’s requirements are pretty steep, so I was really looking forward to what’s in this product’s future.

Well, there was a lot of good news. The Documentum SharePoint integration products 6.6. versions will be released in a matter of weeks. My Documentum for SharePoint 6.6 will bring some more webparts and support for SharePoint 2010.

Repository Services for SharePoint 6.6 will provide a slightly different model from the previous version. Repository Services sits between the SharePoint UI and its storage in SQLServer. In the 6.5 version Repository Services would take the contents of any SharePoint documents and store the in Documentum, along with a copy of the meta data. In 6.6 the content is initially stored on a filesystem. A new journaling mechanism will then move the content from the filesystem into the Documentum repository batchwise.

There are 2 advantages to the journalling mechanic:

  • You can add business rules to the journalling, so for instance only documents with a certain status will be moved into the Documentum repository
  • It will improve SharePoint performance, since content retrieval from a filesystem is generally faster then from a docbase.

Disadvantage: an extra filesystem component to manage

There is a new product/developer option in this field: SDF (SharePoint Documentum Framework). This is a framework that EMC has been building and using in projects since 2007. There are already 40.000 people using this in production.

SDF is a customization framework that enables you to leverage most Documentum functionality from within a SharePoint site. It is based on DFSX, so it can use all the DFS webservices. Many have already been turned into SharePoint webparts, such as Browse, Search, Inbox, Query, WorkQueues, Records Management and IRM.

SDF also enables us to add custom menu items to SharePoint that can call DFS, or your own custom webservices. This can be configured using XML configuration files (it start to feel like WDK for SharePoint). SDF is also integrated with Sharepoint workflows. It adds an activity template that calls DFS a webservice, so you can add Documentum functions to your workflows. Lastly I saw a screenshot where a form built with FormsBuilder was displayed inside SharePoint, using picklists from Documentum. Very nice !

Thanks to Micheal Mohen for saving my RFP.