Archive

Posts Tagged ‘Administration’

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…

Prerequisites ,Installation and Configuration of ACS

November 10, 2010 Comments off

In my previous post i tried to bring out what is ACS , today lets see how we can install and configure an ACS , to start off with the Prerequisites for ACS:

a) Content Server.

b) Global registry Repository.

Installation and configuration of ACS:

Administrator doesn’t need to install it explicitly; it gets installed automatically when Content server 5.3 sp1 and above are installed. An ACS config. Object is also created automatically in the menu:

Administration-> Configuration->ACS Servers. As shown in following diagram:

 

The Administrator can check whether this service is running or not by going to following link in his system http://[system ip address]: [port no]/ACS/servlet/ACS. Or he can see the ACS service running in the services of his operating system service manager.

The Configuration of ACS means configuration of ACS server for the repository which will serve by that ACS server to specified network locations. We need to configure the ACS server config. Object for each repository, irrespective of the content server under which it is created. This configurations will be as following:

1)    Go to the Servers in Administration->configuration->Servers and click on information button to edit the properties for that server config. Object.

Go to “Connection Broker Proj” Tab and add the address of host name on which the ACS server is installed and also specify the Proximity for that Server. Administrator can add more than one connection broker to one repository at any time.

Now after following the above steps , you will see that the ACS server got added to server config object:

2)    Go to the “Network Location Proj “ tab to add the network location to be served by the repository.

Network Location got added to Server Config Object as in below:

3)    Now save and come out of the server config object to the ACS server config Object. And verify the “Connection Broker Projection” and “Network Location projection” for correct entries.

Now the ACS server is configured to the Repository server through a Connection broker to serve a set of network location.

Note: While creating the connection broker object take care for false host name because the Documentum never verifies for fake/non existing hosts.

User Management using Documentum Administrator

March 24, 2010 Comments off

Documentum Administrator is the Web-based tool for administering Content Server. By Documentum Administrator all the administrative tasks for a single installation or a distributed enterprise can be performed from one location.

One of the administrative tasks of Documentum Administrator is User Management. To access a Docbase, a person must be defined as a user in that Docbase.

The Administration/User Management displays a list of users in the current Docbase. Search for users can be done by their user name in the Docbase, user OS name (name on the operating system), or default group.

How to locate users in Docbase

1.  Connect to the Docbase where we want to locate a particular user.

2.  In the left-hand pane, click Administration.

3.  Click User Management.

4.  Click Users.

5.  To search by user name, user OS name, or default group, type in the information and click   Go 

 How to create new users

One must have Sysadmin or Superuser privileges to create users.

1.  Connect to the Docbase where we want to create new users.

2.  Click Administration –> User Management.

3.  Click File –> New –> User. (Check Right Hand Side)

  4.  Indicate whether the user’s state is active or inactive. An active user can connect to a    

     Docbase whereas an inactive user cannot.

5.  In the Name field, type the user’s name.

6.  Select a User Source from the drop-down list.

  • UNIX Only: Select this for the default UNIX user authentication.
  • Domain Only: Select this if the Docbase has Windows domain authentication enabled and the user must be authenticated against a domain.
  • UNIX first: Select this if the Docbase has Windows domain authentication enabled and the user must be authenticated first against UNIX, then against a domain.
  • Domain First: Select this if the Docbase has Windows domain authentication enabled and the user must be authenticated first against a domain, then against UNIX.
  • LDAP: Select this if users are authenticated against an LDAP server.

7.  In the E-Mail Address field, type the user’s email address. This is the address to which  

     notifications are sent for workflow tasks and registered events.

8.  In the User OS Name field, type the user’s operating system user name. This is used by the 

     user to login to the docbase.

9.  In the Windows Domain field, type the user’s Windows domain.

10. Select a home Docbase for the user.

11. Designate the user’s default folder which is the default storage place for any object the  user creates. To use an  existing Docbase folder, click Choose existing folder and to create  a folder with the user’s name, click Choose/Create folder with user name.

12. Click Select Group and select a default group for the user.

13. Click Select Permission Set and select a default permission set for the user.

14. Select the user’s privileges from the drop-down list.

User privileges authorize certain users to perform activities that are required to administer and maintain the system. The privilege levels are:

  • None
  • Create Type
  • Create Cabinet
  • Create Cabinet and Type
  • Create Group
  • Create Group and Type
  • Create Group and Cabinet
  • Create Group, Cabinet, and Type
  • System Administrator
  • Superuser

15. Select the user’s client capability from the drop-down list.

 There are four types of users:

  • Consumer
  • Contributor
  • Coordinator
  • System Administrator 

16. Click Finish and new user is created.

How to delete users

We can remove users from the Docbase, but Documentum strongly recommends making users inactive rather than deleting them from the Docbase.

 When a user is deleted, the server does not remove the user’s name from objects in the Docbase such as groups and ACLs. Thus when we delete a user, we must also remove or change all references to that user in objects in the Docbase.

%d bloggers like this: