Is there a .NET COM interop for the Records Mgmt / Physical Objects APIs?

Hello,

We are using LAPI with LL 9.7.1 successfully from within a C# project as we integrate an in-house application built by a client with the LL repository. We need to invoke some Records Management & Physical Objects functions to complete the integration.

We could follow the "Open Text Records Management/Physical Objects API Guide" and link the RecMan and PhysObj objects with the lapi_base DLL but that would be an undesired approach give how easy it has been to invoke the other SDK calls using the lapi_netp.dll interop.

Does anyone know if there is a RM/PhysObjects interop we could use to easily access the RM functions from C#? Or perhaps that functionality is already in place and I had missed something? Any help will be appreciated.

Best regards,

Michael Paduch

Sophic Technologies Inc

Ottawa, Canada

Find more posts tagged with

Comments

Appu_Nair

The way I do this and a older link is like this

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=15249695&objAction=view&show=2

You need to bring the recman.cs and physobj.cs interface files into your solution and if regular lapi stuff works like connecting to enterprise and so on ,then the RM/PhysObj api works as well,you can then see the functions thru intellsesnse.The RM API guide probably has examples and gotcha's as well.Of the top of my head I always use the standard lapi session object,the other one that is suggested has never worked for me.

Michael_Paduch

Thank you for cross-referencing the relevant discussion thread.

Can you refresh my memory on how to generate the .cs interface file based on a non-assembly Windows DLL? I assume and recall there is an MS VS tool that does that.

If I follow that approach, I want to make sure the interface I use corresponds exactly to the function prototypes implemented in the exact version of RecMan.DLL I use.

Thanks again for your help.

Michael

P.S. A question for the OpenText folks: is there a plan to expose the RM/PO API as the valid assembly for .NET programmers at some point?

Appu_Nair

I just go to a livelink server that has PO and Recman installed.Like here

<OTHOME>\module\recman_4_2_0\SDK\csharp\RecMan.cs.I have attached the interface file for recman & PO as well as a VSS2008 solution

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=17595478&objAction=download

and this

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=17995800&objAction=download

I do not know if VSS projects can be shared if you find them useful let me know

Also what benefits would you get by using the dll method,that I see there but nobody seems to know

how to make it work.

Michael_Paduch

Appu, thanks again for all your help.

I am not sure if I understand your question about the DLL.

I would like the vendor to publish the RM/PO API the same way they publish the general SDK, so that we can simply add an assembly as a reference to a Visual Studio project and code right away.

The meaning of each RM/PO call or parameter is described relatively well in the reference manual. All we need is the consistency of how one brings the API to use within a Visual Studio project.

The approach whereby one has to add an auto-generated C# file to a project and do it again each time the new version of the module is released is in my mind a temporary workaround, not an end goal.

I am not sure if I am answering your question though.

Michael

Michael_Crandall

Has anyone had any luck with this? I was able to write a simple c# interface for PO. All I want to do is create a PO object but I am getting an error. The error message is: "com.opentext.api.LLIllegalOperationException: get(name) not implemented for this datatype". I can provide sample code if neccessary. I am using the CreateObjectEx method in the LAPI_DOCUMENTS class. I have tried this using the Web Services as well and get the same type of error.

Any help would be greatly appreciated.

Michael_Crandall

Looks like the problem I am having is when I set the object sub type to 411 (Physical Item).

David_Caughell

Hi Mike,

If you post your sample code, I can take a look at it. Also,can you specify what the Physical Properties are for the Physical Item Type youare using?

David.

From: eLink Entry: LAPI Forum[mailto:lapi@elinkkc.opentext.com]
Sent: August-27-10 6:30 PM
To: eLink Recipient
Subject: Is there a .NET COM interop for the Records Mgmt / PhysicalObjects APIs?