session.apply() DQL Question

kmac5

I'm trying to trigger a DQL statement without triggering the TBO code,

I've seen several references to the following API call that achieves this.

apply,c,EXEC,QUERY,S,'{DQL}',FOR_UPDATE,B,T,BOF_DQL,B,F

this discussion talks to it:

https://community.emc.com/message/638470#638470

What I'm trying to do is convert this to a DFC session.apply() call much like the

DO_METHOD example discussed here.

https://community.emc.com/message/93097#93097

My question is mapping the API call to the argument lists, I haven't found any

documentation that spells it out and my first couple attempts didn't work right.

...

IDfList argList = new DfList();

{add arguments}

IDfList argTypes = new DfList();

{add argTypes}

IDfList argsValues = new DfList();

{add argValues}

col = session.apply(null, "EXEC", argList, argsTypes, argsValues);

...

Does anyone have a canned example or is there a specific document I can look at

to glean this information?

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

PanfilovAB

Not sure about need escapes for commas....

    public static int execUpdateQueryWOTBO(IDfSession session, String updateQuery) throws DfException {
        IDfCollection coll = null;
        try {
            coll = session.apply(
                    null,
                    "EXEC",
                    new DfList(new String[]{"QUERY", "FOR_UPDATE", "BOF_DQL"}),
                    new DfList(new String[]{"S", "B", "B"}),
                    new DfList(new String[]{updateQuery, "T", "F"}));
            if (coll.next() && coll.hasAttr(APPLY_RESULT_FIELD)) {
                return (int) Double.parseDouble(coll.getString(APPLY_RESULT_FIELD));
            }
            return 0;
        } finally {
            closeCollection(coll);
        }
    }

All comments

JorgKrause

Hi,

there are TONS of examples of how this is done. A simple google search returns a couple of them, actually

https://community.emc.com/thread/128767

However, the main point of your question is that you want to bypass the invocation of the TBO, right? Well, this was possible in earlier versions (up to 5.3 I believe), and required the use of API calls only. The IDfSession.apply triggers the invocation of a server method, and unless this method is using API calls only, you're not achieving the possible result.

From 6.x on, API calls like save etc, do invoke TBO as well!!!

Regards

Jørg

kmac5

I gave Google the once (and twice) over and couldn't find a good example/reference for a DQL statement

through the session.apply() method. The link you provided is an example of a DO_METHOD call though

the session.apply() - I included one of those in the original question.

From what I've read (discussion 638470 ), adding "BOF_DQL,B,F" as an argument to the apply statement

by-passes the TBOexecution. Maybe I assume too much and the straight API call behaves differently than

the session.apply() execution, I'd still like to give it a try. (the alternative solution is very tedious)

PanfilovAB

Not sure about need escapes for commas....

    public static int execUpdateQueryWOTBO(IDfSession session, String updateQuery) throws DfException {
        IDfCollection coll = null;
        try {
            coll = session.apply(
                    null,
                    "EXEC",
                    new DfList(new String[]{"QUERY", "FOR_UPDATE", "BOF_DQL"}),
                    new DfList(new String[]{"S", "B", "B"}),
                    new DfList(new String[]{updateQuery, "T", "F"}));
            if (coll.next() && coll.hasAttr(APPLY_RESULT_FIELD)) {
                return (int) Double.parseDouble(coll.getString(APPLY_RESULT_FIELD));
            }
            return 0;
        } finally {
            closeCollection(coll);
        }
    }

PanfilovAB

Jørg Krause wrote:From 6.x on, API calls like save etc, do invoke TBO as well!!!

You are wrong At frist, in 6.x EMC did not invent anything except contract between dfc and content server: CS performs update and returns list of updated objects, dfc calls save for each returned object. At second, api call are myth, they are just a shorthands for apply rpc-call and operation-specific arguments.

JorgKrause

My bad, didn't catch that you're looking for DQL statement.

But there are examples for this as well I searched google with "execute do_method dql sample" and found

https://community.emc.com/thread/119131

Main point is that you're specifying arguments and values as pairs. If you specify your arguments like

-arg1 value1 -arg2 value2

The will automatically be paired in to the IDmMethod/IDfMethod Map params for methods written in java. Docbasic methods don't have this at all, you simply have to declare sufficient parameters in the function declaration.

I must admit that I haven'¨t seen this method before (BOF_DQL). Not sure what it is supposed to do, either. Could you provide some links, so I can have a look?

Thanks

Jørg

JorgKrause

PanfilovAB wrote:You are wrong  At frist, in 6.x EMC did not invent anything except contract between dfc  and content server: CS performs update and returns list of updated objects, dfc calls save for each returned object. At second, api call are myth, they are just a shorthands for apply rpc-call and operation-specific arguments.

Not sure if I understand what you mean, I'm afraid.

Up to version 6 (not 100% certain if it's up to 6.5 though), TBO code was invoked only if objects were instantiated thorugh DFC calls. Using an api script like

retrieve,c,<type> where r_object_id='<something>'

set,c,l,<attribute>

<attribute_value>

save,c,l

didn't NOT invoke the associated TBO. This was a neat backdoor to avoid TBO invocation in certain circumstances.

In addition, we could use BOF 1.0 deployment, which enabled BOF functionality pr client, depending on settings in dbor.properties. Using BOF 2.0 deployment through repository, BOF is always invoked from any client!

Since 6.0, maybe 6.5, the above API script does invoke associated TBO as well, if BOF2.0 deployment is used.

What exactly are you meaning by "api calls are myths...."?

Regards

Jørg

PanfilovAB

 Since 6.0, maybe 6.5, the above API script does invoke associated TBO as well, if BOF2.0 deployment is used.

All your retrieves, sets, saves .. etc invoke TBO methods, and so what? It is not relevant to the initial question that sounds like: "How change objects in dfc without invoking tbo?".

 What exactly are you meaning by "api calls are myths...."?

CS still does not know anything about TBO and Java, TBO is a DFC staff

JorgKrause

So CS doesn't know about TBO and Java??????

Last time I checked, CS was using DFC, quite extensively!

Rather uncertain about what you're trying to say, to be honest.

And the answer to the initial question has been given several times as well. If TBO is deployed through BOF2.0, you can't bypass TBO invocation!

Regards

Jørg

PanfilovAB

 So CS doesn't know about TBO and Java??????

Hey, look here:

 ldd /u01/documentum/ord/product/6.5/bin/documentum
        linux-gate.so.1 =>  (0xffffe000)
        libdl.so.2 => /lib/libdl.so.2 (0x00353000)
        libldap50.so => not found
        libssldap50.so => not found
        libprldap50.so => not found
        libnss3.so => /usr/lib/libnss3.so (0x00c9b000)
        libssl3.so => /usr/lib/libssl3.so (0x00c64000)
        libsoftokn3.so => /usr/lib/libsoftokn3.so (0xf7f4e000)
        libnspr4.so => /usr/lib/libnspr4.so (0x00b43000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0xf7f1c000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x0035a000)
        libsm_sms.so => not found
        libsm_clsapi.so => not found
        libsm_env.so => not found
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x003a7000)
        libm.so.6 => /lib/libm.so.6 (0x00376000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00494000)
        libc.so.6 => /lib/libc.so.6 (0x001f7000)
        /lib/ld-linux.so.2 (0x001d4000)
        libnssutil3.so => /usr/lib/libnssutil3.so (0x00101000)
        libplc4.so => /usr/lib/libplc4.so (0x003a1000)
        libplds4.so => /usr/lib/libplds4.so (0x00734000)
        libz.so.1 => /lib/libz.so.1 (0x004a2000)

Are there any dependencies on java executable? Does CS execute TBO methods by itself? Is DFC the only library can connect to CS?

 If TBO is deployed through BOF2.0, you can't bypass TBO invocation!

Did you try invoke apply,c,,EXEC with BOF_DQL,B,F argument?

JorgKrause

Hi,

if you read my replies carefully, you would have noticed that I'm NOT familiar with the BOF_DQL argument at all

Haven't seen it before, and haven't been looking for it either since we're not having issues like this for the time being.

It looks interesting, any idea when this was introduced?

No idea what point you're trying to make with the list of libraries though

There are quite a large number of components involved in the CS, but I would like to see how CS would work without dfc.jar anywhere

Jørg

JorgKrause

Interesting,

just tried

apply,c,EXEC,QUERY,S,'<update query>',FOR_UPDATE,B,T,BOF_DQL,B,F

from DA/API tester.

Getting

Error processing command:java.lang.IllegalArgumentException: Invalid object identifer specified: EXEC

Something I'm missing here?

Jørg

PanfilovAB

Jørg Krause wrote: There are quite a large number of components involved in the CS, but I would like to see how CS would work without dfc.jar anywhere Jørg

Ok, what is "CS" from your point of view? As for me it is as network service represented by the "documentum" process(es) in OS, it can work w/o any other stuff like docbrocker, workflow agent, dm_agent_exec, mthdsvr, jms (last three actually depends on dfc because they are clients) and successfully serve client connections.

Jørg Krause wrote:Something I'm missing here?

It would be honest for you to say that you first time read about "apply" rpc-call rather than "BOF_DQL argument", check manual or read "carefully" my posts.

JorgKrause

Well young man,

even if this is rather entertaining, I'm still puzzled about your "API calls are myth" statement

What's your point???

The API call DOES work, just forgot a comma, of course!

apply,c,,

This was actually new to me, not certain when this was introduced. Still learning, after 12 years with Documentum

IDfSession.apply() is certainly NOT new to me, of course

Neither is API apply, which IDfSession.apply calls, according to DFC Reference (Calls the server API Apply method),

even if I was lucky enough to start with Documentum after DFC was introduced.

Some historical background might be of interest here:

Up to Documentum version 4, the only way to access repository objects was the API. Obviously, running Docbasic scripts with dmApiExec/dmApiGet/dmApiSet was rather cumbersome, so Documentum got it's java library, aka DFC.

Major step indeed. Up to version 6, DFC was basically transforming all calls to API calls, or expressed in another way, DFC was implemented on top of API.

From version 6, all dmcl stuff was removed, and Documentum became a clean java implementation. API calls are still available, but are now executed through DFC; which had the interesting side effect that you couldn't bypass TBOs any longer, which was commonly used by administrators for a bunch of reasons.

Regards

Jørg

PanfilovAB

once again: "API Calls" are just shorthands for apply rpc-call and real server methods (the full list of server methods you can get through apply,c,,ENTRY_POINTS), there are no significant changes in client/server protocol at least since Documentum 4: all calls go through apply rpc (except create session, close collection, fetch next collection entries, logoff and some others), and CS always returns a collection, for example:

fetch is a shorthand for apply,c,r_object_id,FETCH

getServerConfig is: apply,c,,GET_SERVER_CONFIG,OBJECT_TYPE,S,dm_server_config

getType is: apply,c,,FETCH_TYPE,TYPE_NAME,S,dm_sysobject

authenticate is: apply,c,,AUTHENTICATE_USER,CONNECT_POOLING,B,F,USER_PASSWORD,S,password,AUTHENTICATION_ONLY,B,F,CHECK_ONLY,B,F,LOGON_NAME,S,username

all your historical impovements are just client-side changes, not server-side

Vino14987

I need to run the below API command through DFC program.

apply,c,i_contents_id,PURGE_CONTENT

Can anyone help me how to acheive this?