Using the New Storage Rules Wizard on a LES9.7.1

Friday April 24, 2009

Using the New Storage Rules Wizard on a LES9.7.1

Posted by anair@alitek.com on 04/24/2009 08:57 AM
My rating:(1 rating )
Using the New Storage Rules Wizard on a LES9.7.1Recently I was playing with LEA as an alternate storage provider.So the storage provider rules dawned on me and I saw a rule that looks like this Attribute ‘?’ Value is ‘?’.I looked at how one would go about it and the help had nothing.I asked OT support who added me to a ticket and said they would let me know in a patch later.So I just asked around other friends etc who did not know either.But John Simon my good friend from COP asked me this “so did they ever tell you what to put in?  Or have they decided it is bugged and you can’t put anything in to make it work?”That challenged me so I decided to look at what the  code was doing or how one would do this.Without further ado here’s one way that works.My category name is called ‘CoreCatAtts’

My attribute Name is called ToStoreWhere its index is 4.This is to deliberately mislead you.

So the Attribute Spec has to be written like this

CoreCatAtts[1].ToStoreWhere[1] picture of the rule will make it more worthwhile to the reader

llisapi.dll

For Developers who want to see what all that means

The way you are supposed to use it is like that

CategoryName[1].AttributeName[1]

Don’t be tempted by putting the attribute index it is figuring that from the name.

the number 1 after category name specifies the Root Set

and the number 1 after attribute name says the row where it is found(they have generic function for row number to handle MVA)

{{3762.2},{1,1.4,1}} that is what they are making it do

what it means is find the category with defid 3762 and version 2

and the Root Set 1,Row 1,ID and first value of that ID

So in oscript if I wanted to find the value of attribute (ID=4) at its 4 th row

will be like this {{3762.2},{1,1.4,4}}

Try it out and see if that works for you 🙂

Advertisements

The Perils of Using Default Access List

Thursday November 12, 2009

The Perils of Using Default Access List

Posted by anair@alitek.com on 11/12/2009 01:22 PM Functions
My rating:
4 star overall rating. (1 rating )
The famous Default Access List that stays with every object in LES.Every now and then people get into all kinds of arguments on how to use a ACL effective for the organization.Recently as of today somebody had a 911 on it and my dear friend John Simon commented.I did and Jim Coursey wrote an exctensive good reply.I wanted to see if I had forgotten what I learned so I wrote this little document to help.Discussion Thread on thishttps://knowledge.opentext.com/knowledge/llisapi.dll/open/16960219Most experienced Livelink administrators understand ACL’s really well and are guided by Open Text or some other experienced persons in setting up a organizational security model .However when writing this we are in a severe economic downturn so most new people have no inkling on how livelink works,how security works and that sort.All they get is the standard OT training and I really don’t think they cover this at all.Most think of Scare Point as the ultimate and it is just a call to the SP admin who logs on clicks a link adds the AD group to the ACL and lo and behold you have a link where you can all communicate/ collaborate while the system is up and running.This is just written for upcoming people so that they understand what they can avoid.I got into this after a user started having qns on some stuff that RecMan poses and my good friend and mentor John Simon COP said something very straightforward.I added to the reply and Jim Coursey also contributed.The trouble is the default access list that Livelink provides out of the box is really geared for a system administrator who understands the livelink owner role.However in a roll out all these get really muddled and then you have a chaotic security model that nobody can ever comprehend. .I wrote an article to complement John’s KISS(Keep It Simple ,S*****)  method  it and hopefully somebody may find it useful.This has already been attempted at OT by another article but mine has some screen shots for the impatient 🙂
https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=3498977&objAction=ArticleView

Please do let me know if this article has factual errors.I would not want to mislead anyone.So post why you think this is problematic and why you would like to give Owner a lot of unwanted perms.

Attachments:
Document Perils of using the high privs associated with Owner.docx (254 KB) Functions Download
Hide Recent Comments

Re The Perils of Using Default Access List – kenneth.huie@mantech.com  Wed Nov 18 11:04:09 2009
Appu,   This is a great write up!  I appreciate your document and the references you provided. You are so right, this is such a huge topic in that its impact is often not fully understood and the results of incorrect usage of the OWNER …
Attachments:
Document Access Control TIP.doc (23 KB) Functions Download

What Pray is Enterprise Library

Stuff from my old BLOG  ARCHIVED – Livelink Rocks– GlobalStar ECM Champ Appu

After I posted this when I look OT has basically introduced more java based code streams especially the module Directory Services is being offered in the realm of RCS.If and when I need to get into OTDS I will post my experiences

In a nut shell both livelink and archive server are not written in java.However in a situation where SAP has to export/import documents or make visible an archived document  which was done using the GOS capabilities of SAP perhaps with the intents of putting a Records Management classification  or maybe get people in SAP a collaborative workspace as in livelink this comes into play.The solution is referred as Extended ECM. For this to work the main plumbing is

SAP to Archive Server using ECMlink  (Archive link is still there I am not sure if they are one and the same)

Livelink to Archive server using Archive Storage provider

RCS(Run Time & Core Services) Lots and lots of helper java code to interact with livelink and archive server

For SAP code to create/declare objects within livelink they will send their requests to a high level wrapper.The wrapper has the code to create livelink type items,such as documents,folders etc.A enterprise library objects is nothing but a livelink object with a livelink category.From SAP and their consultants call it with a different name.Also in a ELS scenario all objects are created within a separate section(volume) like the Enterprise Data Source.Typically for integrating a SAP SID the livelink team uses RCS (the high level wrapper code on Tomcat). When an Application is created in livelink you will see a new data source  by that name.

As a programmer if you have RCS and livelink setup you can actually run code in any language using the examples provided by OT.Note this is not the same as Enterprise Web Services or Content web services that one writes to do something against livelink.

Tha actual ECM deployment is very/highly complicated so please make sure  you understand all the moving parts and players.

Getting ELS accepted will need some help

Posted by anair@alitek.com on 07/09/2010 12:04 PM Functions
My rating:
Unrated
OT has embraced ELS or Enterprise Library services as  a very cool paradigm for integrating perhaps disparate software systems.The main products in the mix are Livelink and Archive.Even though both products are OT many livelink admins including me would not necssarily know the Archive side(although I am much better at it it).The ELS install documentation is a gargantuan deal and clearly many people trying it out the first time may have a difficult time.I encourage people to ask around,keeping their inhibitions to themselves and usually will get help from the community.I answered a recent KB post on ELS and I published my cheat sheet on it as well.I enclose a link thinking that it may help a potential livelink or ELS admin some day.https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=17841798&objAction=download