Adobe Drive CMIS connector and Authentication

Hello,
We have undertaken a project to make our DAM CMIS compliant and thus get connected with Adobe Drive using it's inbuilt CMIS connector. We will be following RESTful AtomPub binding of CMIS for this.
CMIS spec doesn't talk a lot about the authentication and seems like it is outside the scope of CMIS. I wanted to know how Adobe Drive client gets authenticated with any CMS/DAM using its CMIS connector. What is the mode of authentication used - is it HTTP basic, digest authentication or something custom. So I am not sure what would Adobe Drive send to get authenticated and what would it expect in the response. How do we pass back the session token that we will create.
Any pointers wrt this are appreciated. That will really help us make progress on this project.
Thanks!
Mandar Kulkarni

Drive CMIS connector uses HTTP basic authentiction.
Thanks.

Similar Messages

Developing: Endless loop in Adobe Bridge with and Adobe Drive CMIS Connector

Hi
Currently I’m implementing a CMIS-Server for the dam system of my company, using the apache chemistry framework. One of the main requirements is that adobe drive works with it.
At the moment I implemented only the navigation services (getChildren, getObject, …) and the repository services and test them against adobe drive. It’s already possible to navigate through folders and read assets with ad4 and the finder. So 3 days ago I installed adobe bridge (CS6) and test my server again.
My test environment is very easy.
root(1 object)->test1(0 objects; empty)
First I’m opening my repository with adobe drive and then I switch to bridge and connect it. Bridge shows me the folder test1 with no errors. So I double-click it and now bridge is in an endless loop. The notification switch between ‘Keine anzuzeigenden Elemente’(No elements to show) and ‘Einen Moment bitte, die Suche läuft …’(Searching, please wait …). This only happens in bridge. When I open the folder with the finder it just works, without the loop.
So I logged all requests, which were send by adobe drive, and get this list.
Connecting with adobe drive
getRepositoryInfos
getTypeChildren (null) -> all basetypes
getTypeDecendants (cmis:document)
getTypeChildren (null) -> all basetypes (Why two times?)
getTypeDecendants (cmis:document) (Why two times?)
getRepositoryInfos (Why two times?)
getObjectByPath (/.hidden)
getObjectByPath (/.hidden)
getObjectByPath (/.hidden) (Why so often?)
getObjectByPath (/DCIM)
getObjectByPath (/mach_kernel)
getObjectByPath (/.Spotlight-V100)
getObjectByPath (/.metadata_never_index)
getObjectByPath (/.metadata_never_index_unless_rootfs)
getObjectByPath (/.metadata_never_index)
getObjectByPath (/mach_kernel)
getObjectByPath (/.metadata_never_index_unless_rootfs)
getChildren (cmis:folder,0) (rootfolder) returning only one element (test1)
getObjectParents(cmis:folder,127) (test1) returning the rootfolder
getObjectByPath (/.hidden)
getObjectByPath (/mach_kernel) …
Open the Cmis repository in bridge and doubleclick the repository
getChildren (cmis:folder,0) (rootfolder) returning only one element (test1)
getObjectParents(cmis:folder,127) (test1) returning the rootfolder
Then I double click the test1 folder
getObject(cmis:folder,127)(test1)
getChildren(cmis:folder,127) -> empty list
… (endless loop)
I already checked getObject and getChildren against a reference implementation (FileShare Repository of apache Chemistry) and it returns exactly the same structure. Only the name and the timestamps are different. So my second though was to check the repository capabilities and as well they are both equal. Now I’m a little bit desperate because I spend already 3 days in try and error bugfixing but nothing worked. So here are my questions.
Is there a logfile for bridge because I thing this refreshing happens after an exception. I already checked the adobe drive log and it contains only asset not found errors for (e.g mach_kernel …).
In which circumstances does bridge reloads a folder?
Debugging of adobe drive: I already read http://forums.adobe.com/message/3928595 but it doesn’t work in AD4 any more, I only get info/error/fatal messages.(I changed the log4j config files in AD4ServiceManager.) Does something changed or did I forget something?
Why does AD4 make 2 or more times the exact same request? (Look table above).
I hope my English is good enough to understand.
Thanks

After two months I'm a little bit smarter so I can answer some of my question by my own.
No there is no logfile for bridge, but I was able to debug the scriptcode from the ad plugin, which is installed in bridge.
If an error occures in the plugin
I was able to decompile the cmis connector. That helps a lot when ad logs with weird exceptions.
Because AD maps the actions of the filebrowser(finder,explorer) to cmis and this one does sometimes the exact action two or more times.
Unfortunately is wasn't able to fix my main problem, but I found a workaround to use cmis in bridge. I deactivated the ad plugin in bridge and after that action, bride display the cmis volume as normal volume. Sadly some actions like to manage relationships etc. are with this workaround not usable but for me this is alright.

Adobe Drive Custom Connector

Hi,
We have a requirement for Digital Asset Management solution and the client already has a FileNet P8 4.5.1 solution in production. They are using Adobe Creative Suite CS5 (Indesign, Illustrator, Photoshop). We tested the CMIS connector with P8 5.0 and we found few limitation(no previews and thumbnails, no option to select the class as it always defaulted to "Document" class, version comments not stored, verison previews not available) and will appreciate if you can confirm that the following requirements can be met by developing a custom connector using Adobe Drive SDK:
The user needs to be able to Checkin Indesign Documents with all links from Indesign or by just doing a copy/paste of the full Indesign package folder in “Finder”
While checking in the user should have the option to select the class of the document and fill the indexes for the documents
The user should be able to search in Adobe Bridge based on the indexes filled during checkin operation (FileNet Properties)
Adobe Bridge should be able to show the thumbnails and preview for all added content (Indesign, illustrator, Photoshop)
Versioning should be supported with version comments, and versions dialog should show the preview of each version.
Thanks
Alex

from the perspective of Adobe Drive, I think the answers for all the above questions is Yes.
Adobe Drive is a set of client components for asset managementss, it depends on your connector and remote DAM service to provide all the information it needs, like thumbnails, preview, seach cretirias in Bridge, version comments and etc, throught Adobe Drive SDK, if your connector follow it and is good designed, I think Adobe Drive can meet all the above requirments.
any issue you will met in the developement, you can post here
thanks

Rename, New folder action using Drive CMIS connector

I am trying to work on "Rename" and "New Folder" actions from Drive. To give more details - when I connect to our DAM using Drive, the DAM gets mounted as a network drive and can be accessed from Windows Explorer. I was told on one of the Adobe forums thread that Drive uses the Windows in-built context menus to initiate these actions.
Refer: http://forums.adobe.com/message/3807568#3807568
But when I try "New Folder" menu, Explorer gives me "Access denied" or "You need permission" kind of error. On "Rename" I get similar error. I believe both these errors are due to the fact that I am trying to modify certain things on a network drive. But then what would be the work around so that I can perform these actions on a CMIS server using Drive?
We are adding CMIS layer on top of our DAM so that it will work as a CMIS server. For connection with Drive, we use the default CMIS connector that comes with it.

Logs on "Rename" action
2012/09/28 05:34:58,691 [IFSConnection-1] FATAL IFSConnection - NASTY Runtime exception for Request: RENAME
com.adobe.drive.biz.filesystem.FileSystemException: java.lang.NullPointerException
    at com.adobe.drive.internal.biz.filesystem.FileSystemService.run(FileSystemService.java:1680 )
    at com.adobe.drive.internal.biz.filesystem.FileSystemService.run(FileSystemService.java:1646 )
    at com.adobe.drive.internal.biz.filesystem.FileSystemService.rename(FileSystemService.java:9 81)
    at com.adobe.drive.ifs.job.RenameHandler$1.call(RenameHandler.java:95)
    at com.adobe.drive.ifs.job.RenameHandler$1.call(RenameHandler.java:1)
    at com.adobe.drive.model.context.Context.run(Context.java:88)
    at com.adobe.drive.ifs.internal.IFSConnection.dispatch(IFSConnection.java:187)
    at com.adobe.drive.ifs.internal.IFSConnection.run(IFSConnection.java:142)
Caused by: java.lang.NullPointerException
    at com.adobe.drive.connector.cmis.client.CMISProxy.buildQuery(CMISProxy.java:2086)
    at com.adobe.drive.connector.cmis.client.CMISProxy.query(CMISProxy.java:1987)
    at com.adobe.drive.connector.cmis.client.CMISProxy.getDescendantDocuments(CMISProxy.java:196 1)
    at com.adobe.drive.connector.cmis.client.CMISProxy.hasCheckedOutDocumentsByAnyUser(CMISProxy .java:1920)
    at com.adobe.drive.connector.cmis.handler.Handler.isCheckedOut(Handler.java:305)
    at com.adobe.drive.connector.cmis.handler.MoveHandler.execute(MoveHandler.java:95)
    at com.adobe.drive.connector.cmis.handler.MoveHandler.execute(MoveHandler.java:1)
    at com.adobe.drive.internal.data.manager.DataManager.execute(DataManager.java:3162)
    at com.adobe.drive.internal.data.manager.DataManager.execute(DataManager.java:3114)
    at com.adobe.drive.data.manager.call.AbstractFSCall.executeConnector(AbstractFSCall.java:323 )
    at com.adobe.drive.data.manager.call.Move.callConnector(Move.java:501)
    at com.adobe.drive.data.manager.call.Move.moveRemoteSource(Move.java:302)
    at com.adobe.drive.data.manager.call.MoveFinder.moveToEmptyDestination(MoveFinder.java:83)
    at com.adobe.drive.data.manager.call.MoveExplorer.moveToEmptyDestination(MoveExplorer.java:7 0)
    at com.adobe.drive.data.manager.call.Move.execute(Move.java:142)
    at com.adobe.drive.internal.data.manager.DataManager.moveAsset(DataManager.java:3892)
    at com.adobe.drive.internal.biz.filesystem.FileSystemService$12.execute(FileSystemService.ja va:998)
    at com.adobe.drive.internal.biz.filesystem.FileSystemService$FSRunnable.run(FileSystemServic e.java:1803)
    at com.adobe.drive.data.internal.persistence.PersistenceRunner.run(PersistenceRunner.java:11 9)
    at com.adobe.drive.internal.biz.filesystem.FileSystemService.run(FileSystemService.java:1666 )
    ... 7 more
Logs on "New folder" action
2012/09/28 05:23:42,321 [IFSConnection-1] FATAL IFSConnection - NASTY Runtime exception for Request: CREATE
com.adobe.drive.biz.filesystem.FileSystemException: com.adobe.drive.data.model.DriveException: Error creating directory
    at com.adobe.drive.internal.biz.filesystem.FileSystemService.wrapException(FileSystemService .java:1623)
    at com.adobe.drive.internal.biz.filesystem.FileSystemService.run(FileSystemService.java:1673 )
    at com.adobe.drive.internal.biz.filesystem.FileSystemService.create(FileSystemService.java:8 67)
    at com.adobe.drive.ifs.job.CreateHandler$1.mkDir(CreateHandler.java:204)
    at com.adobe.drive.ifs.job.CreateHandler$1.call(CreateHandler.java:183)
    at com.adobe.drive.ifs.job.CreateHandler$1.call(CreateHandler.java:1)
    at com.adobe.drive.model.context.Context.run(Context.java:88)
    at com.adobe.drive.ifs.internal.IFSConnection.dispatch(IFSConnection.java:187)
    at com.adobe.drive.ifs.internal.IFSConnection.run(IFSConnection.java:142)
Caused by: com.adobe.drive.data.model.DriveException: Error creating directory
    at com.adobe.drive.internal.data.manager.DataManager.create(DataManager.java:4434)
    at com.adobe.drive.internal.biz.filesystem.FileSystemService$10.execute(FileSystemService.ja va:885)
    at com.adobe.drive.internal.biz.filesystem.FileSystemService$10.execute(FileSystemService.ja va:1)
    at com.adobe.drive.internal.biz.filesystem.FileSystemService$FSCallable.run(FileSystemServic e.java:1767)
    at com.adobe.drive.data.internal.persistence.PersistenceRunner.run(PersistenceRunner.java:11 9)
    at com.adobe.drive.internal.biz.filesystem.FileSystemService.run(FileSystemService.java:1666 )
    ... 7 more
There might be something wrong with our implementation as well. But I am not able to figure out where lies the problem.

Adobe Drive 3.0 and Sharepoint 2010

Have the Adobe Drive/Sharepoint 2010 interoperability issues been resolved?

Are you still interested in Creative Suite <-> Adobe Drive <-> MS SharePoint integration? Do you have SharePoint configured with CMIS? I’m not sure which specific issues you’re referring to, but there are a number of known integration issues (for example, check out functionality not working) that are being looked into by MS (confirmed that the check out issue and a number of others are ones they need to resolve). I do not have an ETA yet as to when an update with fixes will be released.

Regression? Adobe CMIS Connector 4.2 and CC ten times slower than 4.0.

Hello dear forum members!
We developed an Adobe Drive CMIS connector for our DAM system and noticed a major navigation performance degradation
when updating CMIS connector on windows client systems from Version 4.0 to Version 4.2 or CC.
When visiting a folder:
Version 4.0 does a getChildren request ("children" url) and is finished: 1 call
Version 4.2 and CC do a getChildren request and IN ADDITION call:
   - getObjectParents ("parents" url) for each object in folder
   - getObjectParents for folder of path of each object
So lets say you have some folderX with path
/top1/folder1/folderX
containing 500 images of some photo session that needs sorting you get
1x getChildren
500x getObjectParents (one for each image)
2x500x getObjectParents (2 for each folder of path of each image)
in sum: 1501 calls until that same folder gets displayed.
Any chance that this gets fixed on Adobe Drive CMIS connector?
Can we do something on server side to prevent that behavior?
Does Adobe Drive support paging in big folders?
Anything else we can do to help?
Regards,
    Carsten

Hello together,
I noticed the same issue on Adobe Drive 5.
After accessing a folder with 35 files in it on Adobe Drive MAC CMIS Connector I saw over 200 HTTP Requests over the network (AtomPub).
On other CMIS Clients it were only 14 requests.
On Windows Adobe Drive CMIS Connector I did not record the requests but on windows it was anyway much much faster.
I assume the Java layer is the same on Windows and Mac so I think that maybe the underlying AdobeDrive4 filesystem (at least "mount" shows an "AdobeDrive4" FS) implementation on Mac polls very often and this results in extensive HTTP requests. Thats why I also thought of writing an own CMIS Connector which uses clever caching.
Maybe we can bundle our ideas and implement a fast open source CMIS 1.1 Connector for Adobe Drive?
@md_Zool:
How are your experiences with an own Connector?
Could you speed up things at Mac?
Maybe Adobe also can also shed some light on this issue?
tia
Cheers
Sascha

Operations supported by CMIS connector

I was wondering what all operations defined by CMIS, are supported by CMIS connector that comes with Drive 2.1 esp. from Windows Explorer. When I right click in Windows Explorer, the Drive context menu gives only these options - Check out, Check in, Cancel check out, Show versions and Connect to. But the tech note for CMIS connector says that we can even rename a folder, create a new folder (and a few more operations) by selecting options in context menu. I believe those are not certainly the options provided by Windows but should be somewhere in Drive menu.
Some clarification would help greatly.
Thanks.

Hello,
You want to use Adobe Drive + CMIS Connector to test your CMIS server, right? Because the operations in Adobe Drive, for example, rename operation in the context menu can uses serveral CMIS services, like getObject, moveObject, updateProperties, etc, you have to know exactly the CMIS services used by Adobe Drive for each operation.
Thanks,
Zhiqiang

Adobe Drive 2 and Alfresco CMIS interface problems

Hi,
we are currently testing Drive2 with the 3.3 Release of Alfresco. Connection, reading and writing towards Alfresco via AD2 is stable and showing good performance.
Sadly, checking in files created via AD2 fails with an Error on the Alfresco side whenever we try to execute check in from AD2 (on Windows clients as well as Macs). As the check in is not possible, files are added to the repository bute cannot be seen by any other users.
Although the error is on the Alfresco side, the log suggests that AD2 may be calling methods on the Alfresco side twice or in the wrong sequence or context.
Here's a clipping from the log:
8:17:31,712 ERROR [org.springframework.extensions.webscripts.AbstractRuntime] Exception from executeScript - redirecting to status template error: 08080005
Wrapped Exception (with status template): 08080183 Failed to execute script 'classpath*:alfresco/templates/webscripts/org/alfresco/cmis/children.post.atom.js
': Duplicate child name not allowed: A0122610_gb.jpg
Can anyone advise how we can come around this or find a solution for this problem ?
Kind regards,
dimgy.

Hi dimgy,
Can you tell us the exact Adobe Drive build number and Alfresco version?
For Alfresco, please tell us the download filename and file date. It would be better if you can give the download URL. We have submitted several bugs to Alfresco. Some had been fix and others are still in progress. So we need to know the exact version.
Regards,
Guo Wei

Adobe Drive and Alfresco Enterprise Fails to Check-in With Custom Content Types

Hello all,
I've been struggling with some drive limitations over the last few weeks as we try to utilize the CMIS connector to Alfresco. I am currently testing with Adobe Drive 3.2.0.41 and Alfresco 4.0.1 Enterprise but have tested this behavior with Drive 4.0.2.6 paired with Alfresco 4.1.1.3 and seen the same behavior:
The issue I am seeing is that I am unable to Check in a new document into the repository when there is a rule set up to apply a custom content type from our model. After entering my check-in comment and pressing OK, I get an unknown error from Bridge, InDesign, or Photoshop. It works fine if I do not specialize our type with a rule (leaving the content as cm:content). The error I recieve in Alfresco is: org.alfresco.service.cmr.repository.CopyServiceException: The source and destination node must be the same type.
I understand that this might be a limitation of Drive and Alfresco working together, but I just wanted to see if anyone had any experience with this issue or any potential workaround, since it is pretty limiting for alfresco to not have any non OOTB content types.
Thanks, your help would be appreciated.
Mike

Adobe Drive CC still has this issue. I can dra-n-drop a .PSD into Alfresco 4.2 and it will work perfectly - unless I use Adobe Drive to edit and check-in the file.

Versioning in Adobe Drive 3.0

Hello,
Have some problems with versioning in Adobe Drive 3.0
'View Versions' in Bridge display icon only for current version. 'Open' version returns corrupted file.
The same code works fine with Adobe Drive 2.6
Did not found any differences for version handling in sdk docs 3.0
Any suggestions?

Hi
Could you please share more detail information?
Which connector are you using? the built-in ADEP, CMIS connector or a custom connector?
What is the icon for the current version? a file system icon representing those files with the same file extension or a bitmap thumbnail? how about other versions?
What does you mean "'Open' version returns corrupted file"? you openned the current version or the previous version? Did the application openning the version crash or you could still open the version, however the file content is incomplete?
for your information, We never released Adobe Drive 2.6, only 2.0, 2.1, 3.0.
Furthermore, you can create a Environment variable named "AdobeDriveLogLevel" and set its value to "DEBUG", reproduce this issue and post the logs under <userdata>\Adobe\Adobe Drive CS5\logs and \Adobe\CS5ServiceManager\logs here or send them to [email protected]
Thanks

Adobe ASC 2.0 and ASDoc

After upgrading to the AIR 3.6 SDK which uses the new ASC 2.0 compiler all the ASDoc tasks in my Ant build files fail. I'm getting the error:
BUILD FAILED E:\Projects\Eclipse\project\build\build_swc.xml:51: The following error occurred while executing this line: E:\Projects\Eclipse\projectbuild\build_swc.xml:209: Problem: failed to create task or type asdoc Cause: The name is undefined. Action: Check the spelling. Action: Check that any custom tasks/types have been declared. Action: Check that any / declarations have taken place.
Did Adobe remove the ASDoc Ant task? I can't find any information about this elsewhere. ASDoc generation worked flawless before I installed the 3.6 SDK.

Guo Wei,
I'm trying to do the same here, connecting Adobe Drive 2.1 with Sharepoint 2010.
This is the URL to my CMIS-enabled SharePoint Library that I use as "Server URL" in Adobe Drive CMIS Connection:
http://sharepoint_server/_vti_bin/cmis/rest/document_guid_here?getrepositoryinfo
When I try connect I'll get "Authentication failed".
How do I know when the "Server URL" is right? When I type http://sharepoint_server/ I'll get the same response.
Is there a log-file for Adobe Drive and the CMIS-connection?
In this document there is some information and a short preview of the XML-file but nothing about SharePoint: http://help.adobe.com/en_US/creativesuite/cs/adobedrive/CMIS_Connector_Tech_Note.pdf
This is the xml-file that SharePoint generates: http://dl.dropbox.com/u/2665693/sharepoint_output.xml
I think there are (or will be) way more customers interested in a connection with SharePoint than Alfresco to be honest.
Thanks!

CMIS Connector - Mac OS 10.9 Finder Mounting Issue

Hi.
I have recently updated my system to MAC OS X Mavericks (10.9) and Adobe Drive to Version 5.0.1. I am using CS6.
I updated from CS5, Drive 3 and Mac OS X 10.6.
The problem is as follows:
When i connect the CMIS volume (an alfresco 3.4 community dam) with Drive 5 the volume is mounted in Mac Finder as "cmis". Instead of my custom volume mount name "MyCustomVolume". I defined the custom name in Drive as well as in Alfresco CMIS-Config. And it worked flawlessly before updating. But i need the volume to be mounted as "MyCustomVolume" and not as "cmis".
The strange thing is: If i run the terminal and have a look "~/Volumes" i can see, that there is a volume "dr-x------@ 1 myusername nogroup 0 20 Nov 15:22 MyCustomVolume" mounted. And no volume "cmis". So where does this "cmis" come from?
Needless to say, that my file linkings e.g. in InDesign documents relate to the old mount name and not to "cmis". Currently every file i open will have broken links.
And there is another issue: The "cmis" volume is "readonly" and not writeable. Using the Finder i am not able to change any of the cmis mount properties.
Actually i am wondering whether it is a Drive or a Mavericks issue.
I already tried this:
- Several Drive reinstallations, Drive Cache/Setting clearings as well as Mac OS Disk Utility permission repairs.
- Deactivated Sophos Antivir
- Uninstalled MacFuse and Tuxera NTFS
The problem is critical for me because my daily work depends on a seemless cmis integration.
So i hope for some help.
Best regards
Volker

UPDATE:
Intermediatly Adobe Drive 5.01.28 worked as it should do - But today i ran into the same issue i had before.
I haven't done anthing cruel to Adobe Drive, but suddenly i have this same strange behaviour like i described in my initial post.
The finder shows "cmis" as volume mount name BUT the Terminal/CLI shows me the correct volume name in the "/Volumes" folder - this is driving me nuts.
I already did a PRAM and SMC reset on my mac. And i deleted Adobe Drive 5 completly and reinstalled it. Same result - same problem.
The Alfresco server is running properly and i already restarted it.
The Errorlog of Adobe Drive shows these errors (repeatingly):
2014/02/04 20:29:25,189 [ConnectionHandler-kernel] ERROR GetAssetsHandler - asset not found: /Backups.backupdb 2014/02/04 20:29:25,190 [ConnectionHandler-kernel] ERROR GetAssetsHandler - asset not found: /DCIM 2014/02/04 20:29:25,227 [ConnectionHandler-kernel] ERROR GetAssetsHandler - asset not found: /.hidden 2014/02/04 20:29:25,228 [ConnectionHandler-kernel] ERROR GetAssetsHandler - asset not found: /.Spotlight-V100 2014/02/04 20:29:25,262 [ConnectionHandler-kernel] ERROR GetAssetsHandler - asset not found: /.metadata_never_index 2014/02/04 20:29:25,298 [ConnectionHandler-kernel] ERROR GetAssetsHandler - asset not found: /.metadata_never_index_unless_rootfs 2014/02/04 20:29:25,343 [ConnectionHandler-kernel] ERROR GetAssetsHandler - asset not found: /.metadata_never_index 2014/02/04 20:29:25,377 [ConnectionHandler-kernel] ERROR GetAssetsHandler - asset not found: /.metadata_never_index_unless_rootfs 2014/02/04 20:29:25,481 [ConnectionHandler-kernel] ERROR GetAssetsHandler - asset not found: /Backups.backupdb 2014/02/04 20:29:25,482 [ConnectionHandler-kernel] ERROR GetAssetsHandler - asset not found: /mach_kernel 2014/02/04 20:31:20,475 [ConnectionHandler-kernel] ERROR GetAssetsHandler - asset not found: /Sites/.localized 2014/02/04 20:31:23,130 [ConnectionHandler-kernel] ERROR GetAssetsHandler - asset not found: /Sites/.localized 2014/02/04 20:31:25,675 [ConnectionHandler-kernel] ERROR GetAssetsHandler - asset not found: /Sites/.localized ...
I don't know why Drive is looking for these files and what they are about. (Some of them seem to belong to Mac's TimeMachine, but my TM disabled!)
Need some help! Because i can't work with my server files and the Creative Suite anymore. Every server-based file i am trying to open with an Adobe Application causes an error.
Any ideas out there?

When will Adobe Drive 4 SDK be available?

When will the SDK and documentation be available?
I just went to grab the drive 3 sdk when I noticed that there is a Drive 4 now. I can't tell which versions of Creative Suite are compatable. Will CS6 work with adobe drive 3? And I can't tell if my plugin that I started will work in Drive4.
Help.

In addition, here are the Drive 4 related deployment change requirements for partner connectors:
Mac:
Old location: /Library/Application Support/Adobe/CS5ServiceManager/plugins
New location: /Library/Application Support/Adobe/AD4ServiceManager/plugins
Win 64-bit:
Old location: C:\Program files (x86)\Common Files\Adobe\CS5ServiceManager\plugins
New location: C:\Program files (x86)\Common Files\Adobe\AD4ServiceManager\plugins
Win 32-bit:
Old location: C:\Program files\Common Files\Adobe\CS5ServiceManager\plugins
New location: C:\Program files\Common Files\Adobe\AD4ServiceManager\plugins

'Delete' operation with CMIS connector

I was told in one of the post I made at - http://forums.adobe.com/thread/879186?tstart=0 that Drive uses 'Delete' option from the context menu of OS (no such option exists in the Drive menu). When I was testing my deleteObject method and tried to do that with this context menu option, the document got deleted just like any other document from local file system but reappeared once I hit refresh. (I have connected our DAM system using Drive)
Am I doing anything wrong? I expect selecting Delete would hit my code and document would get deleted from our DAM server.

Hello,
Can you explain me you mentioned " I expect selecting Delete would hit my code", you implemented a Connector for Adobe Drive to connector your own DAM server, right?
Thanks,
Zhiqiang

CMIS Connector Issues

Dear Sir/Madam,
We have implemented a CMIS repository for our database and have noticed a couple of issues with the Drive CMIS connector.
1. Paths
In our repository the paths are not made up of the names. For example if a consider a top level folder with the name Top Level Folder and sub-folder called Sub Folder, i.e
Top Level Folder
|
+-- Sub Folder
The CMIS connector assumes that the path to the folder is /Top Level Folder/Sub Folder whereas, in our repository, then path has the format /FOLDER00002/FOLDER00010. For folders the GetObject call returns the cmis:path property that should be used instead of assumnig that the path is made up of the names. For documents the GetObjectParents and GetChildren calls allow the path segment to be returned.
2. Multiple Parents
Our repository supports multi-filing and therefore documents can have multiple parents. We have found that thsi causes a problem when saving new assets. In our repository assets can be automatically added to a second folder when created. The connector requires the first parent returned by the GetObjectParents call to be the folder that the asset has just been created in. We have worked around this by ordering the parents returned but it would be better if the connector checked all the parents returned.
Kind regards,
Ian

Hi mandarpkulkarni,
For files, could you check your product whether there is ' cmis:versionSeriesId ' property for document object? CMIS connector uses it as asset id, and it must be not null.
As CMIS 1.0 Spec Section 2.1.9.5 'Versioning Properties on Document Objects' points out, all Document objects will have the following read-only property values pertaining to versioning:
cmis:versionSeriesId ID
ID of the Version Series for this Object.
Thanks,
Hui

Adobe Drive CMIS connector and Authentication

Similar Messages

Maybe you are looking for