I understand that CMIS will be used as standard connector to exchange data between DAM-systems and Adobe tools like PS, ID, Bridge etc. Is that right? It is a very promising approach and i would love to see it become a fully supported core technology within the Adobe product range. It also seems to make a lot of sense, considering that the purchase of Day Software brought powerful DAM technology with full CMIS support to Adobe.
At the time being the CMIS-connector is still lacking so important things like previews, metadata and alike. Is there some kind of roadmap available for Adobe Drive?
Any infos would be very appreciated.
Thanks for the validatoin of this direction. Currently we have the Adobe Drive CMIS connector in pre-release on
labs for the express purpose on maturing its functionality and getting feedback regarding what the most critical features are to support and to give some time for additional vendors to provide CMIS interfaces and test the Adobe Drive connector against those.
In terms of roadmap we intend to make the CMIS connector in final form available to Creative Suite customers in our next update of Adobe Drive sometime later this year. After that we will continue to participate in the development of the CMIS specification and update Adobe Drive as needed when the specification is updated. In addition we will respond to customer requests through updates to Adobe Drive that will roughly align with major releases of the Creative Suite.
Hope this helps.
thank your for your promising reply
For now the most relevant things missing from my point of view are:
I have to agree,
add metadata extraction and update with advanced search + rating ..and do not forget alfresco renditions and thumbnail creation
We are really looking forward to see DRIVE2 working as we have been trying to implement Alfresco as our DAM, but the combination of CIFS and InDesign was not working at all - crashes of InDesign due to grabage collection in Alfresco (deleting temporary file) - at least we think so because we could not get any response on Alfresco Forum to this problem
I can imagine interesting stuff concerning our workflow make this work..
What do you mean "but the combination of CIFS and InDesign was not working at all - crashes of InDesign due to grabage collection in Alfresco (deleting temporary file)"? Could you please provide more detail backgroud for us?
of course, no problem.
We have been experimenting with alfresco community edition since 2.1 (I think). We wanted to use alfresco as our repository and workflow service for our design projects. As we are small pre-press company based on WIN/ADOBE solutions we are using InDesign, Photoshop and Illustrator as a daily tools for the production.
The scenario was to use Alfresco CIFS as a shared drive on a local network to take care about versioning and approval workflow with our clients (Clients would use alfresco explorer/share to submit the assets/approve the proofs and receive the output). We have been able to solve most of the hassle and I have produced very basic Flex app for creting complex directory structure with perrmissions and simple workflow customized for each project (using .acp and webscripts).
The problem was that after editting an InDesign document it crashed when attemting to save. Time that the document was edited played a role in the occurence of such a behaviour so it let us to join this beahviour with the alfresco's garbage collector. I think that the temporary file that has been created by InDesign when editing was somehow destroyed by garbage collector which caused InDesign to crash...
BUT.. as we are pre-press company we do not have any coder available. So this all are only assumtions after several months of trying... I can be wrong of the cause....
I was trying to bring this issue in alfresco forum two times, but there was no answer or anybody with the same problem.
Now alfresco in CE 3.4 with Activiti starting to take care about the workflow seems to be a good start to get back to our plans. Having DRIVE2 working hugged on Alfresco server would make several of my workflow dreams come true Especially with such an easy way to connect FLEX with alfresco using webservices. Not to say if alfresco can render previews of adobe formats.. fantastic...
wuuuuu... having two more lives to try everyhing I have in my mind would be fantastic ))
concerning InDesign and Alfresco CIFS, we are experiencing exactly the same problems, which I documented but wasn't able to sort out with Alfresco :-(
You can find details in my posts on the English and German Alfresco Forums - the German has more infos, but sadly, no solution.
In case you need more infos, you can contact me anytime.
what's your current plan for the public release of the CMIS Connector as a part AdobeDrive 2 ?
We've been setting up and planning a project and would like to start implementung it when the official AD2 CMIS connector is released. Hence, infos on your current roadmap would be appreciated !
Thx and Kr,
we are also working with creative suite (on mac os 10.6 clients) and alfresco 3.4b (on debian lenny and tomcat6 server) and adobe drive 2.0 with cmis connector (used the stable release with the cmis-connector jar files of the pre-release on labs). Unfortunatly we are not happy with the solution since drive 2 and alfresco crash very often:
The "Share"-webclient of alfresco works perfectly and very reliable, so i assume the problems within drive 2 and maybe mac os 10.6?
Whats the latest Issue-State for this major problems, cause i assume others losing their heads with the same problems...?
I have noticed that the working copy of a document one is editing is saved directly on the server beside the orig-document. I presume that this makes the editing more crash-prone, wouldn't be a local copy better, also in context of performance? How is the cache folder used, which i can define and allocate within the options of drive 2.0?
I am pleased to announce that an update to Adobe Drive 2 is scheduled to be released approximately within the next 6 weeks (release timing subject to change). This update will include the following key updates and several important bug fixes: CMIS Connector A production release of the CMIS connector will be made available with the download. The CMIS connector enables basic access to servers that implement the Content Management Interoperability Services (CMIS) specification. CMIS is a standard for improving interoperability between Digital Asset Management servers. It specifies a domain model, plus a set of services and protocol bindings for web services (SOAP) and AtomPub. Connector API Improvements · Additional APIs have been added to improve extensibility capabilities · Comments are no longer lost when promoting a version Adobe Drive Connect UI Improvements When adding a drive or setting a source and target server for data migration, all available connectors are listed automatically in the Adobe Drive Connect UI. In addition, there is the ability to customize connector names, icons, descriptions and more. When using Adobe Drive to connect to a Version Cue CS4 Server, Adobe Drive no longer returns the error “The server could not be connect.” when a Version Cue Server has a URL that doesn’t start with versioncue://.
I am pleased to announce that an update to Adobe Drive 2 is scheduled to be released approximately within the next 6 weeks (release timing subject to change).
This update will include the following key updates and several important bug fixes:
A production release of the CMIS connector will be made available with the download. The CMIS connector enables basic access to servers that implement the Content Management Interoperability Services (CMIS) specification. CMIS is a standard for improving interoperability between Digital Asset Management servers. It specifies a domain model, plus a set of services and protocol bindings for web services (SOAP) and AtomPub.
Connector API Improvements
· Additional APIs have been added to improve extensibility capabilities
· Comments are no longer lost when promoting a version
Adobe Drive Connect UI Improvements
When adding a drive or setting a source and target server for data migration, all available connectors are listed automatically in the Adobe Drive Connect UI. In addition, there is the ability to customize connector names, icons, descriptions and more.
When using Adobe Drive to connect to a Version Cue CS4 Server, Adobe Drive no longer returns the error “The server could not be connect.” when a Version Cue Server has a URL that doesn’t start with versioncue://.
Nice to hear that there is a scheduled update in the near future!
I'm looking forward to the bugfixes within this version.
Will Bugfixes for the InDesign problems and the Mac OS 10.6 Finder freezings be part of it?
Can you tell us if your Mac clients that are showing what you believe to be the issue Knowledgebase article cpsid_85851 are running any kind of virus protection of other hard drive monitoring utilities? It's only the presence of some other software scanning the Adobe drive mounted volumes that would introduce that issue, so if you can identify that software, you can disable it to avoid the issue. Because the issue stems from third party software scanning the drive, I don't expect this to be addressed in the upcoming release. If there is no software scanning the Adobe Drive volume, then the issue is probably different than the documented one you've referred to.
Hi Volker Lux,
For issue2, we want to confirm following question:
1.Which product did you use to edit document when interacting with Bridge?( we take Photoshop to reproduce.)
2.You edit,and check in the document in Product then return back to Bridge again, right?( we follow this step.)
1. Which media file type did you place in the Indesign document?(we use mp3,flv. both managed and unmanaged)
2. Can you help to provide one test file for Indesign?(Thanks very much)
If you encounter these issue again,Please help to post the product crash data.
i couldnt reproduce the freezing problems within MacOS finder in the last couple of days (after installing drive 2.1), so i hope its gone. We also revealed the issues within Bridge:
Bridge and adobe Drive were started automatically at the system startup on each client, the ordering is set to load drive at first. But: Adobe Drive takes a little to establish the connection to the server and meanwhile Bridge has started. So Bridge has problems to build the links to a server which isnt connected at this state, later on it works, but inside Bridge's favorites one get a very strange icon without description if you click on "Adobe Drive" in the favs panel. The solution for a clean behavior is to remove Bridge from the auto startup and start it manually after the server-connection ist completely established. This solves any problems within Bridge. I think some unix programmers could implement a delay for the Drive and Bridge autostart on macs but unfortunatly i have no skilled guys finding an approach for that....
so a part of our problems is solved but a major part still is not: The InDesign crashes. It's still behaving very unhandy and unreliable. I started to accustom myself to first check out any Document manually within Bridge an then open it with InDesign. But if i place media files within the documents that have maybe visibility overrides or exceed the 100MB limit of filesize i have to bargain for an indesign crash "the server version has been deleted". I just have this problems with designing a twosided flyer which is based an 1GB psd (from the correspdonding A1-poster) at the front and has some linkings to a "SmartCatalog" CSV. Now im trying to place the product image which is within a 300MB PSD and if i do that InDesign crashes, again and again and again... its driving me nuts. I can reproduce this behavior also with some other PSD-picture-files.
Photoshop works very well with Drive, alfresco and the Check-in Check-Out process but InDesign doesnt.
So i suspect InDesign or the interoperability of InDesign and Drive of causing the errors.
Can you list the specific steps involved to reproduce the crash? Also, include give me example dimensions, resolution, and colorspace of one of the files that fails, so I can build one similar to it for my testing. If I can reproduce it, I'll get it to the dev team to investigate.
i hope i could solve my indesign crash problem. Due to a fresh alfresco installation and a fileupload of the local/versioncue files to the new alfresco database most files are initial versions on the server and have not been saved out of their specific programs yet. If i open the relevant PSD file and save it as new version again, the problem is gone. Maybe there was a fault within the initial file upload!?
But i noticed another issue within drive: the server connection can't be established sometimes at startup. The clients are shutdown at the evening of every workday, at the next morning sometimes the serverconnection (is set to automatically connect at startup) could not be established. The server is in the drive list and available, but if i try to connect manually, it says "authentication fails" but the authdata ist correct. Restarts of the client could not solve the problem. The only solution is to remove the server from the drive list and add it as new server again - BUT: if i do so and i have still files checked-out (and tmp files of the programs are on the server) they will all be deleted and all changes are lost! Very annoying, i lost a whole day of work due to this problem.
I couldn't find any solution yet.
First, check to ensure that the following folder has permissions set such that it and it's children are read/write for the user account you're logged in with:
Mac: Users/[username]/Library/Application Support/Adobe/CS5ServiceManager/
Win: C:\Documents and Settings\[User]\Application Data\Adobe\CS5ServiceManager\
If permissions are set correctly, and you still have the problem. Try the following:
1) Quit Adobe Drive.
2) Use the Task Manager (Win) or Activity Monitor (Mac) to quit the CS5ServiceManager task.
3) Move the folder mentioned above to some safe place for back up (you can restore if this doesn't help).
4) Restart Adobe Drive, establish your connection, and see if it sticks.
Could you please clarify your case?
In our understanding: AD can’t connect to server automatically after restart OS when the AD is set to automatically connect, right?
According to this understanding, we tried to reproduce the issue with AD 2.1 and alfresco 3.4.a (which is installed on Windows 7 32bit) on Mac 10.6, the result is: AD can connect to CMIS server automatically.
But we have one known issue with AD automatic connect:
1. Add one CMIS server (IPV6 is enabled on the server machine) and Set automatically connects.
2. Restart OS.
3. Disconnect after AD connect to server.
4. Connect to server again.
Results: There will be error message: ‘The server could not be connected’.
For your mentioned issue, could you provide the following information?
1. The alfresco server’s version
2. The OS type of the machine that host alfresco server
3. Check whether IPV6 is enabled on the server host machine.
4. Post the log file: CS5ServiceManager_java.log which is in following location: Users/ [username]/Library/Application Support/Adobe/CS5ServiceManager/logs/ on Mac.