You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@manifoldcf.apache.org by Roman Šitina <ro...@sitina.cz> on 2015/08/21 17:21:04 UTC
Documentum Connector path problem
Hello,
we are experiencing path/cabinet problem when using a Documentum
Connector. If we setup a job using this connection then on a Paths tab
the cabinets that are listed do not correspond with cabinets we can
see in Documentum Administrator for the same user and docbase.
Actually the cabinets in ManifoldCF look like home directories of
Documentum users. We tried to contact our Documentum administrator and
he was wondering how ManifoldCF queries the root cabinets.
Did anybody experienced this?
Thank you
Roman
Re: Documentum Connector path problem
Posted by Karl Wright <da...@gmail.com>.
I am not a Documentum expert, but I was told at one point that "isOneOf()"
will also match types derived from the types explicitly mentioned? Or am I
incorrect?
Karl
On Fri, Aug 21, 2015 at 11:48 AM, Roman Šitina <ro...@sitina.cz> wrote:
> Thank you,
>
> it looks like the problem is with these lines:
>
> // Look up whether this is a type of folder or cabinet
> boolean isMatch = session.isOneOf(strObjectType,new
> String[]{"dm_folder","dm_cabinet"});
>
> because cabinets we are looking for are of type fdrd_cabinet. Which I
> believe is our custom type inherited from dm_cabinet.
>
> Do you suggest some better way to test for cabinets so we can do our
> custom ManifoldCF build?
>
> Roman
>
> On 21 August 2015 at 17:41, Karl Wright <da...@gmail.com> wrote:
> > The documentum connector uses one of two methods to get cabinets. Here's
> > the code:
> >
> >>>>>>>
> > ArrayList objFolderNames = new ArrayList();
> > if (strTheParentFolderPath.equalsIgnoreCase("/"))
> > {
> > String strDQLForCabinets = "select object_name, r_object_type,
> > r_object_id from dm_cabinet order by 1";
> > result = session.performDQLQuery(strDQLForCabinets);
> > }
> > else
> > {
> > result = session.getFolderContents(strTheParentFolderPath);
> > }
> > <<<<<<
> >
> > getFolderContents() uses DFC as follows:
> >
> >>>>>>>
> > IDfFolder objTheParentFolderNode = (IDfFolder)
> > objIDfSession.getObjectByPath(folderPath);
> > if (objTheParentFolderNode == null)
> > {
> > return new DocumentumResultImpl(null);
> > }
> >
> > return new
> > DocumentumResultImpl(objTheParentFolderNode.getContents(null));
> >
> > <<<<<<
> >
> >
> > Thanks,
> > Karl
> >
> >
> > On Fri, Aug 21, 2015 at 11:21 AM, Roman Šitina <ro...@sitina.cz> wrote:
> >>
> >> Hello,
> >>
> >> we are experiencing path/cabinet problem when using a Documentum
> >> Connector. If we setup a job using this connection then on a Paths tab
> >> the cabinets that are listed do not correspond with cabinets we can
> >> see in Documentum Administrator for the same user and docbase.
> >>
> >> Actually the cabinets in ManifoldCF look like home directories of
> >> Documentum users. We tried to contact our Documentum administrator and
> >> he was wondering how ManifoldCF queries the root cabinets.
> >>
> >> Did anybody experienced this?
> >>
> >> Thank you
> >>
> >> Roman
> >
> >
>
Re: Documentum Connector path problem
Posted by Roman Šitina <ro...@sitina.cz>.
Thank you,
it looks like the problem is with these lines:
// Look up whether this is a type of folder or cabinet
boolean isMatch = session.isOneOf(strObjectType,new
String[]{"dm_folder","dm_cabinet"});
because cabinets we are looking for are of type fdrd_cabinet. Which I
believe is our custom type inherited from dm_cabinet.
Do you suggest some better way to test for cabinets so we can do our
custom ManifoldCF build?
Roman
On 21 August 2015 at 17:41, Karl Wright <da...@gmail.com> wrote:
> The documentum connector uses one of two methods to get cabinets. Here's
> the code:
>
>>>>>>>
> ArrayList objFolderNames = new ArrayList();
> if (strTheParentFolderPath.equalsIgnoreCase("/"))
> {
> String strDQLForCabinets = "select object_name, r_object_type,
> r_object_id from dm_cabinet order by 1";
> result = session.performDQLQuery(strDQLForCabinets);
> }
> else
> {
> result = session.getFolderContents(strTheParentFolderPath);
> }
> <<<<<<
>
> getFolderContents() uses DFC as follows:
>
>>>>>>>
> IDfFolder objTheParentFolderNode = (IDfFolder)
> objIDfSession.getObjectByPath(folderPath);
> if (objTheParentFolderNode == null)
> {
> return new DocumentumResultImpl(null);
> }
>
> return new
> DocumentumResultImpl(objTheParentFolderNode.getContents(null));
>
> <<<<<<
>
>
> Thanks,
> Karl
>
>
> On Fri, Aug 21, 2015 at 11:21 AM, Roman Šitina <ro...@sitina.cz> wrote:
>>
>> Hello,
>>
>> we are experiencing path/cabinet problem when using a Documentum
>> Connector. If we setup a job using this connection then on a Paths tab
>> the cabinets that are listed do not correspond with cabinets we can
>> see in Documentum Administrator for the same user and docbase.
>>
>> Actually the cabinets in ManifoldCF look like home directories of
>> Documentum users. We tried to contact our Documentum administrator and
>> he was wondering how ManifoldCF queries the root cabinets.
>>
>> Did anybody experienced this?
>>
>> Thank you
>>
>> Roman
>
>
Re: Documentum Connector path problem
Posted by Karl Wright <da...@gmail.com>.
The documentum connector uses one of two methods to get cabinets. Here's
the code:
>>>>>>
ArrayList objFolderNames = new ArrayList();
if (strTheParentFolderPath.equalsIgnoreCase("/"))
{
String strDQLForCabinets = "select object_name, r_object_type,
r_object_id from dm_cabinet order by 1";
result = session.performDQLQuery(strDQLForCabinets);
}
else
{
result = session.getFolderContents(strTheParentFolderPath);
}
<<<<<<
getFolderContents() uses DFC as follows:
>>>>>>
IDfFolder objTheParentFolderNode = (IDfFolder)
objIDfSession.getObjectByPath(folderPath);
if (objTheParentFolderNode == null)
{
return new DocumentumResultImpl(null);
}
return new
DocumentumResultImpl(objTheParentFolderNode.getContents(null));
<<<<<<
Thanks,
Karl
On Fri, Aug 21, 2015 at 11:21 AM, Roman Šitina <ro...@sitina.cz> wrote:
> Hello,
>
> we are experiencing path/cabinet problem when using a Documentum
> Connector. If we setup a job using this connection then on a Paths tab
> the cabinets that are listed do not correspond with cabinets we can
> see in Documentum Administrator for the same user and docbase.
>
> Actually the cabinets in ManifoldCF look like home directories of
> Documentum users. We tried to contact our Documentum administrator and
> he was wondering how ManifoldCF queries the root cabinets.
>
> Did anybody experienced this?
>
> Thank you
>
> Roman
>