Archive

Posts Tagged ‘Database’

kVisia: Product Overview

March 18, 2015 Comments off

Howdy Users and Buddies,

Today I want to share on kVisia, a product that provides the core functionality to automate, control and deliver an organization’s engineering and enterprise business processes to the desktop or Web. It holds the business rules, executes the XML configurations, builds the business forms, and implements the lifecycles that automate an organization’s business processes.

I think the only Prerequisites that you need to know is , Basic concept of client-server applications and Documentum Architecture.

Let me put it in Content Wise for better understanding with a bit of background of what’s there , what’s missing and how this can be achieved.

  1. Abstract

Today the current era is defined by the terms like data, information, knowledge, wisdom etc. and in this electronic world the difficulty to manage data in abundance has begotten many technologies and one of them is the Documentum.

Documentum is nothing other than a Content Management Tool but its vastness and its ability to cater to almost all sorts of data types available are so rich in itself that these days it is widely used. If we undo the Documentum technically then it gives an edge over the Relational Database Management System by not storing only the Meta data but also storing the content in its native format.

kVisia blends with Documentum to bolster the level and depth of automation which can be achieved by the Documentum alone and this is what this document discusses in detail.

  1. Introduction

kVisia comes of McLaren Software Limited and users need to have a license before using it. McLaren is ISO 9001 certified and it has been accredited Independent Software Vendor for Documentum and FileNet. It has got 360+ customers worldwide and it operates from UK, USA and Switzerland.

In fact kVisia is an Enterprise Engineer product that encapsulates best practices and domain expertise. This is a user configurable application consisting of XML files managed by repository and standardized on a single ECM platform. It is also believed to be powered by Documentum.

For better understanding of the kVisia we can go through the following questions and answers that will help one to identify the need.

How does it help me?

Very quickly configure the user interface and deliver it to the Desktop and Web users.

Is it easy to change?

Very easy, configuration files are stored in the Docbase in XML format.

Configurable interface using objects and tables.

Do the configuration files allow me to control inputs?

Very complex business rules can be enforced via the XML files.

Validations at creation, promotion and check in.

  1. kVisia suite

kVisia suite consists of following three components:

  1. McLaren Studio
  2. McLaren_Core DocApp
  3. McLaren_Foundation DocApp

3.1 McLaren Studio

McLaren Studio provides a user-friendly desktop application that allows users to create and edit XML configuration files that will conform to the rules of the Document Type Definition (DTD).

An XML (eXtensible Markup Language) configuration file is a structured file consisting of many elements. Elements are ordered into a tree structure or hierarchy. Elements may have parent or child elements, and may also contain attributes. An element without a parent element is the highest in a tree structure and is called a root element. Not all of the elements will have child elements.

The structure of a valid XML file is defined in a DTD (Document Type Definition) file. The DTD contains the rules that apply to each XML configuration file; these include the definitions of parent and child elements, element attributes, and how each element can be used

The appearance and behaviour of user dialogs can be modified without the need to change programme code simply by changing settings in the appropriate XML configuration file. A definition of the appearance and behaviour of a dialog is referred to as a “configuration”. A common need, however, is to display different configurations under different circumstances. For example, members of different groups may need to fill in different properties on documents, and the document’s properties may change as it moves from state to state in a lifecycle. The definition of such a scenario is referred to as a “mapping”. When you do not want to differentiate functionality between different groups, lifecycles and states, there is a value called {default} that will apply to all circumstances.

The Actions for which dialogs can be defined using an XML configuration file are:

 New

When the user issues the New command, a customized dialog can be displayed. Commonly deployed features include automatic document numbering, interactive project allocation and any additional attributes (optional or mandatory), which may be required to be stored for the document.

 Properties

A customized Properties dialog can be displayed. Fields can be made editable or read-only as required.

 Import

When the user performs an import, a customized dialog can be displayed which may typically employ features similar to those used in the New dialog.

 Copy

When the user performs a copy and paste action, a customized dialog can be displayed which may typically employ features similar to those used in the New dialog.

 QuickFind

For each document type, a search dialog referred to as QuickFind can be defined and viewed by the user in the Docbase through the McLaren menu. The attributes that can be searched on are configurable and search options such as Between, Greater Than, Containing, etc., can be specified.

 3.2 McLaren_Core DocApp

Having installed kVisia you get two sets of Docapps in the Docbase, one is the McLaren_core and the other one is McLaren_foundation. The McLaren_core Docapp is available to the user of a Documentum repository. It is always suggested that one should have the overview of the additional functionality as a result of the deployment of the kVisia before configuring the product to suit the business need.

As the name suggests McLaren_core Docapp provides the basic functionality like New, Import, Properties, Copy, QuickSearch etc to be configured. As discussed above, we use the XML configuration tool McLaren Studio to configure it.

For each Object Type used in the repository, an XML Configuration File can be created and configured to define the appearance and behavior of the various dialogs for documents of that Object Type. The definition of the appearance and behavior of a dialog is referred to as a configuration, and different configurations can be displayed in different circumstances.

3.3 McLaren_Foundation DocApp

The McLaren_foundation installation enables you to deploy a pre-configured implementation of the Core technology which transforms it into a user application specifically adapted to the engineering environment, providing a ready-for-use engineering repository. It deals with the following configurations:

User Roles that is associated with Menu Systems and User Dialogs that are adapted to those roles.

Object Types for documents and folders.

XML Configuration Files that define the content, appearance and behavior of the New, Copy, Properties, Import and QuickFind dialogs for the supplied Object Types in accordance with the current user’s User Role and the document’s lifecycle and state, including pre-configured, automatically generated document numbering.

Check in dialogs which are specifically adapted for each supplied type of engineering document.

Automated document revision numbering that reflects common design practice. Revision numbers start at 0 and the first issued version is 1, the second 2, the third 3, etc. When a document is checked in for the first time, a numeric value is assigned and incremented each time it is checked in.

  1. Traditional – VB (Desktop) Vs kVisia(Desktop & Web)

Following Comparison lets you know how much flexibility kVisia provides and how much time and effort it saves.

Traditional – VB (Desktop) kVisia (Desktop and Web)
Ø  Obtain VB source code.

Ø  Open VBP.

Ø  Edit GUI.

Ø  Add code to populate list.

Ø  Add validation rules.

Ø  Save source code.

Ø  Compile DLL.

Ø  Create CAB file.

Ø  Open DocApp in Composer

Ø  Edit the component ACX and

replace CAB file.

Ø  Check DocApp back in.

Ø  Not available until next user login.

Ø  Check out XML.

Ø  Edit XML kVisia Studio.

Ø  Add XML tag.

Ø  Specify properties.

Ø  Save and Check back in.

Ø  Change available immediately (no logout required).

  1. Benefits
  • Easy to manage development process as applications are configured via XML using Studio
  • Fast route from innovation to user acceptance
  • Shorter time from design through to development
  • Shorter time to deploy to the business users
  • Reduces development costs
  • Future upgrades are minimised
  • Simple deployment and at a local level of control
  • Speeds up implementation process through rapid configuration

Hope you like the post, Feel free to post your comments and I will reply back to any queries that you have.

Adios , Have a great day ahead…

Upgrading Documentum Environment from 5.2 to 6.5

November 22, 2010 Comments off

The process of upgrading Documentum Content Server from 5.2.5 SP2 to 6.5 SP2 can be divided in two steps:

a)    Upgrading 5.2.5 SP2 to 5.3 SP5

b)    Upgrading the 5.3 SP5 to 6.5 SP2

Part A: Upgrading 5.2.5 SP2 to 5.3 SP5

Following are the steps for the upgrading Documentum environment from 5.2.5 SP2 to 5.3 SP5:

  1. Before upgrading the Documentum content server the database needs to be upgraded from Oracle 8i to Oracle 10g. Before upgrading the Oracle 10g take the db backup and restore them once oracle is upgraded.
  2. Now install the Documentum 5.3 SP5 on the same location where 5.2.5 SP2 is located. Here while installing 5.3 SP5 it will check whether older version of Documentum content server is installed. Since already Documentum is installed it will ask whether to proceed with upgrading the content server or not. Click OK to continue.

The remaining installation steps are similar to the normal content server installation.

3.    Now the content server has been upgraded to 5.3 SP5.

4.    Now docbroker, docbase needs to be upgraded.

Run the server configuration to upgrade the docbroker and docbase respectively. Check the two check boxes as shown in the following screen shot to upgrade the docbroker and docbases.

5.    First docbroker needs to be upgraded. Click on the upgrade docbroker option to upgrade the docbroker.

A confirmation dialog box will pop up informing about upgrading the connection broker. Click on OK to proceed.

6.    Once the docbroker is upgraded, docbase needs to be upgraded. Select continue with server configuration option to upgrade the docbase.

7.    Select upgrade the existing repository option to upgrade the docbase.

A confirmation dialog box will pop up informing about upgrading the connection broker. Click on OK to proceed.

8.    Once the dobase is upgraded, restart the Documentum server, connection broker and docbase. Test the connectivity through da and webtop.

9.    Check all the existing docapps are functioning as they were in the previous environment.

Part B: Upgrading 5.3 SP5 to 6.5 SP2

The second part of the upgrade process involves upgrading from 5.3 SP5to 6.5 SP2.

Following are the steps for upgrading Documentum environment from 5.3 SP5 to 6.5 SP2:

Assuming Documentum 5.3 SP5 is installed on windows 2003 server with database as Oracle 10g.

1.    Now install the Documentum 6.5 SP2 on the same location where 5.3 SP5 is located. Here while installing 6.5 SP2 it will check whether older version of Documentum content server is installed. Since already Documentum is installed it will ask whether to proceed with upgrading the content server or not. Click OK to continue.

The remaining installation steps are similar to the normal content server installation.

2.    Now the content server has been upgraded to 6.5 SP2.

3.    Now docbroker, docbase needs to be upgraded.

4.    Run the server configuration to upgrade the docbroker and docbase respectively. Check the two check boxes as shown in the following screen shot to upgrade the docbroker and docbases.

5.    First docbroker needs to be upgraded. Click on the upgrade docbroker option to upgrade the docbroker.

A confirmation dialog box will pop up informing about upgrading the connection broker. Click on OK to proceed.

6.    Once the docbroker is upgraded, docbase needs to be upgraded. Select continue with server configuration option to upgrade the docbase.

7.    Select upgrade the existing repository option to upgrade the docbase.

A confirmation dialog box will pop up informing about upgrading the connection broker. Click on OK to proceed.

8.    Once the dobase is upgraded, restart the Documentum server, connection broker and docbase. Test the connectivity through da and webtop.

9.    Check all the existing docapps are functioning as they were in the previous environment.

Functioning aspects of Documentum

March 21, 2010 Comments off

Documentum has the following functioning sectors:

  1. Client-WebTop or Desktop client – The client can be a web based client (WebTop client) or can be a desktop client.
  2. Content repository – The content repository contains the actual files. It stores data either as File system or External storage
  3. Database – The database contains the address about where the files are actually Stored (metadata).
  4. Web development kit (WDK) – The WDK contains a set of API’s which help to retrieve the relevant data.
%d bloggers like this: