How to Retrieve Node’s ProviderData information in CBCreate NodeCallback

Hi,

currently we have a requirement to update SAP CRM when a document is added to content server from the GUI. Document will be stored in Archive server (Based on Storage rules Configured).

Plan is to use CBCreate Nodecallback -> Capture required Details -> Send these information to SAP using Activator to SAP -> SAP RFC to update the CRM system.

We were able to Achieve this flow , but facing problem while capturing Node ProviderData Information (especially Provider info e.g “ixos://A1@aaabeid1a25fkjeqpqah5zyk5dhby”).

We tried querying database using “select * from ProviderData where providerID = :A1” but we are getting empty recArray as we suppose data is not yet committed.

We tried retrieving information from “createInfo.context.LogicalProvider.provider.fLastProviderDataAssoc.pData”, but this seems not to be correct , Don’t know why ?

We tried using $Easp.Util.GetProviderData( prgCtx, version.pProviderID ) but again getting empty value ( Database transaction is not yet complete?)

Can anyone please help us on how to obtain providerData information in CBcreate Nodecallback OR suggest any better approach to achieve this.

** Also Noticed that the required information is being printed on Debug Window, but any help as how to get this

EASP:DocumentPutFileWithRetry result EASP:Timing Wed Apr 08 16:54:19 2015 78785

EASP:Times FilePut, netsend 1427

EASP:Timing Wed Apr 08 16:54:19 2015 78788

EASP:ProviderFilePut of 'testfile.txt' ok. returning ixos://A1@aaabeid1a25fkjeqpqah5zyk5dhby "

Find more posts tagged with

Comments

Appu_Nair1

I would do it a little differently the reason I am saying that is the way callbacks work.You might find a related discussion in LinkedIN that says the same thing.The callbacks are difficult to debug when you are in it.Ossie a great friend has this in his blog http://www.oscriptadventures.com/2013/03/observer-effect-quantum-physics-and.html .I ran into this in eventscripts as well which comes form the same kind my blog https://appukili.wordpress.com/2013/10/25/event-scripts-debugging/

What I would do is make the callback insert the dataid into a table or some place you can get to it later like the system data table or your own schema and you will be able to post process it using a pinger handler or a agent.

If the call works and you are able to find the archive server info in the providerdata column I would think it is just a matter of timing.

Hans Stoop

I agree with Appu that a different solution may be better. I don’t think it is a good idea to call an external system during a call back. What if the system Is not available?

I would create a task for the distributed agent to do the work.

I expect that your original code doesn’t work, because you used the wrong callback. You need to implement it in CBAddVersionPost. The version is added after the document node is created. Therefore your code is called too early.

Hans

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Mittwoch, 8. April 2015 15:13
To: eLink Recipient
Subject: How to Retrieve Node’s ProviderData information in CBCreate NodeCallback

How to Retrieve Node’s ProviderData information in CBCreate NodeCallback

Posted byappu.n.nair@conocophillips.com (Nair, Appu) On 04/08/2015 09:08 AM

If the call works and you are able to find the archive server info in the providerdata column I would think it is just a matter of timing.

[To post a comment, use the normal reply function]
Topic:	How to Retrieve Node’s ProviderData information in CBCreate NodeCallback
Forum:	Content Server Development Forum
Content Server:	Knowledge Center

Appu_Nair1

Hans,

In my implementation I was just doing a CAPI.Exec to a livelink schema table I had created.I suuggested.Later I realized that livelink has a convenience table called LLSYSTEMDATA with some easy to use oscript API's and to stay away form KINI for the cache re-load.So maybe if I get a project now I may try LLSYSTEMDATA .

Abhilash_Kenkere

Thanks Appu and Hans for the valuable suggestion. I will Go with storing Dataid in a table and then later update the external system using agent.

Abhilash_Kenkere

Hi Hans,

Just to understand better, please let me know if it is possible to get ProviderData information in CBAddVersionPost.callbacks.

eLink User

Yes just echo it out as echo("the variable here") don't put debugger using deduction you can program the output.

The problem if you do it synchronously is if you say you have a bulk loader process that creates thousands of nodes

the code will stop at each of your callback and slow it down that trifle.If you put the debugger it will rollback in most cases.

You have better control with a async process.DA might be overwhelming to start with that is why I suggested a pinger handler

where you don't have to write an agent per se...

..Appu

I wonder how one could debug livelink if Fiddler, Wireshark and Softerra LDAP browser was not invented and not free

On Wed, Apr 8, 2015 at 10:39 AM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

RE How to Retrieve Node’s ProviderData information in CBCreate NodeCallback Posted byabhilash.kenkere@accenture.com (Kenkere, Abhilash)On 04/08/2015 11:32 AM

Hi Hans,Just to understand better, please let me know if it is possible to get ProviderData information in CBAddVersionPost.callbacks.
[To post a comment, use the normal reply function]Topic:How to Retrieve Node’s ProviderData information in CBCreate NodeCallbackForum:Content Server Development ForumContent Server:Knowledge Center