Copy objects from one docbase to another

Hello Experts,

I am trying to copy some objects from one docbase to another. Therefore, I need a session for both docbases. So, I create a session like in my this discussion. https://community.emc.com/message/715260#715260 . If I create a session in this way and call copy operation, it successfully copies the objects from source to target. If I create a module in this way, it works fine everywhere, in composer, in jms and in process builder.

==============================

sessionManager.setIdentity("REPOSITORY1", loginInfo);
        peerSession=sessionManager.newSession("REPOSITORY1");

        //Create session in second docbase
        loginInfo.setUser("dmadmin");
        loginInfo.setPassword("pass2");
        loginInfo.setDomain(null);
        sessionManager.setIdentity("REPOSITORY2", loginInfo);
        peerSession=sessionManager.getSession("REPOSITORY2");
        //Object to be copied in current docbase where the module is running         IDfSysObject sysObj=(IDfSysObject) peerSession.getObject(new DfId("09026c198006e946"));               //Destination folder in destination docbase                   IDfSysObject sysObj2=(IDfSysObject) peerSession.getObject(new DfId("0c00001680054ee1"));               IDfCopyOperation copyOpr=clientX.getCopyOperation();               copyOpr.setSession(peerSession);               copyOpr.setDestinationFolderId(sysObj2.getObjectId());  //sysObj2 is destination folder               IDfCopyNode node=(IDfCopyNode) copyOpr.add(sysObj);               copyOpr.execute();        IDfClient client=

Now, if I use get session method of the module for instead of hard coding the docbase credentials,

sessionManager;        
        IDfSession peerSession;

        //Create session in first docbase
        //loginInfo.setUser("dmadmin");
        //loginInfo.setPassword("pass1");
        //loginInfo.setDomain(null);
        //sessionManager.setIdentity("REPOSITORY1", loginInfo);
        //peerSession=sessionManager.newSession("REPOSITORY1");
          peerSession=getSession(); 
          sessionManager=peerSession.getSessionManager();     
        //Create session in second docbase
        loginInfo.setUser("dmadmin");
        loginInfo.setPassword("pass2");
        loginInfo.setDomain(null);
        sessionManager.setIdentity("REPOSITORY2", loginInfo);
        peerSession=sessionManager.getSession("REPOSITORY2");
        //Object to be copied in current docbase where the module is running         IDfSysObject sysObj=(IDfSysObject) peerSession.getObject(new DfId("09026c198006e946"));               //Destination folder in destination docbase                   IDfSysObject sysObj2=(IDfSysObject) peerSession.getObject(new DfId("0c00001680054ee1"));               IDfCopyOperation copyOpr=clientX.getCopyOperation();               copyOpr.setSession(peerSession);               copyOpr.setDestinationFolderId(sysObj2.getObjectId());  //sysObj2 is destination folder               IDfCopyNode node=(IDfCopyNode) copyOpr.add(sysObj);               copyOpr.execute();        IDfClient client=

This code works fine in composer and process builder but in JMS with P06 it throws "Using session handle that has already been released" exception. See error1.txt for details.

Now, if I modify my code like this and try to create a new session insted of using the one returned by getSession() method of the module.

sessionManager=client.newSessionManager();        
        IDfSession peerSession;        IDfSession session;
        //Create session in first docbase        loginInfo.setUser(session.getLoginInfo().getUser());                loginInfo.setPassword(session.getLoginTicket());                loginInfo.setDomain(session.getLoginInfo().getDomain());                if(!sessionManager.hasIdentity(session.getDocbaseName()))                   sessionManager.setIdentity(session.getDocbaseName(), loginInfo);                peerSession=sessionManager.newSession(session.getDocbaseName());                
     
        //Create session in second docbase
        loginInfo.setUser("dmadmin");
        loginInfo.setPassword("pass2");
        loginInfo.setDomain(null);
        sessionManager.setIdentity("REPOSITORY2", loginInfo);
        peerSession=sessionManager.getSession("REPOSITORY2");
        //Object to be copied in current docbase where the module is running         IDfSysObject sysObj=(IDfSysObject) peerSession.getObject(new DfId("09026c198006e946"));               //Destination folder in destination docbase                   IDfSysObject sysObj2=(IDfSysObject) peerSession.getObject(new DfId("0c00001680054ee1"));               IDfCopyOperation copyOpr=clientX.getCopyOperation();               copyOpr.setSession(peerSession);               copyOpr.setDestinationFolderId(sysObj2.getObjectId());  //sysObj2 is destination folder               IDfCopyNode node=(IDfCopyNode) copyOpr.add(sysObj);               copyOpr.execute();        IDfClient client=

This time, it throws "Session is not owned by this session manager" exception. Please see error2.txt for details.

Note that this problems occur after installing P06. Please help me to identify what is the cause and how I can fix it. I can't uderstand why it works when I hard code the credentials but when I use credentials of other session it does not. I really can't understand what is the difference between these two.

Thanks in advance

error2.txt

error1.txt

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

bacham2

OK. So it looks like cross-repository copies are supported by IDfCopyOperation. I think that the problem is that the IDfSysObject you pass as the source is somehow associated to the session of the target docbase. This may be the reason things fail. Try to change your code as follows:

1. Do not get a session for REPOSITORY2. The IDfCopyOperation should do that for you. That's probably also the reason why the setDestinationFolderId takes an IDfId argument, which is not tied to any session as you may know. You will need to add the credentials for REPOSITORY2 to the IDfSessionManager using setIdentity.

2. Get the source IDfSysObject with the session from REPOSITORY1.

Hope this helps.

All comments

bacham2

Why do you overwrite the IDfSession stored in peerSession? You should store each session in a different variable. The reason it works is probably because DFC will transparently connect to the other repository if you fetch an object which is not stored in the current repository.

Another comment: your IDfSessionManager variables are called sometimes sessionManeger and sometimes sessionManager. There might be a bug there.

Imran_Yusubov

Hello,

thank you very much for your reply.

Sorry it is sessionManager in all placeses. There was a typo. The compiler is happy with it, so there is no this problem.

Ok, if I have to store each session in a different variable, could you please tell me how I can create a session for multiple docbases?

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

Thanks in advance

bacham2

OK. I'm not so sure how the operations package manages sessions from multiple docbases. I guess it doesn't and relies on DFC's built-in ability to transparently connect to remote docbases when needed.

What's confusing in your code is that the first session instantiation for REPOSITORY1 is pointless since your never use it and immediately overwrite the session with one from REPOSITORY2. This is why I said that you should store each session in a separate variable. However, it looks like you can only specify one session in the IDfOperation so I guess you can skip the first session instantiation.

Again, I'm not sure if the operations package is supposed to support this. An alternative would be to perform the copy manually. In other words, you fetch the object with session1 and then create a new object with session2. This way you have full control.

Imran_Yusubov

That is ok. The dfc documentation says,

wether I use the sessionManager object that has been created previously or using session.getSessionManager() will behave exactly in the same way, and will return the same sessionManager object. Therefore, I think this is ok.

But, why does not it work in JMS is still a mystery.

But, using two sessions one for copying and one for getting the objects does not work. I had tried this, but since the objects were retrived with a different session the copy operation says now access to the object.

Haroon_A

I think, the trick is to have the same user/credentials in both source and target repositories, in order have an open session/connection simultaneously. This way you could use the same login info with different repositories to set your identity. I have used it in the past BUT with the same id/pass in source/target docbases.

bacham2

2. Get the source IDfSysObject with the session from REPOSITORY1.

Hope this helps.

Haroon_A

Do not get a session for REPOSITORY2. The IDfCopyOperation should do that for you. That's probably also the reason why the setDestinationFolderId takes an IDfId

Just curious, how can we obtain r_object_id of destination folder to pass to "setDestinationFolderId" without obtaining a session to target docbase?

bacham2

IDfId folderId = new DfId("0b.....");

Or pass it as an argument to the BOF module. Getting a session to REPOSITORY2 shouldn't hurt but the main point is to get the source object with the session that belongs to the docbase where the object is located.

Haroon_A

IDfId folderId = new DfId("0b.....");

Yes, this would definitly work, provided that destination folder is static and the same. I was thinking a dynamic scenario, if you need to fetch folder (and its id) dynamically.

Imran_Yusubov

Hello Guys,

This works properly. I get a session using getSession(); method of IDfModule interface and then I create a new login info for the target docbase and pass it to this session's session manager.

     //Set target docbase identity for current session     IDfSession currentSession=getSession();     if(currentSession.getSessionManager().hasIdentity(destinationDocbase)){         currentSession.getSessionManager().clearIdentity(destinationDocbase);     }     currentSession.getSessionManager().setIdentity(destinationDocbase,loginInfoTarget);

For the destination folder id, I create a separate specific session for the target docbase using the same login info and then get the folder using getFolderByPath() method and pass it's id to the copy operation.

But, I could not understand what was wrong when I use peerSession.Even it is the suggested way in DFC documentation.

Thank you very much