John Vaudin
12
COW Coins
Forum Replies Created
-
Send to CS 6 is a shortcut for Export as FCP 7 XML and then importing that into Premiere. If you could send a sample of the FCP XML files that won’t import into Premiere to support at squarebox dot com we’ll take a look.
-
You can configure the system in this way but you would need to manually configure the settings for the Web Client on the Tomcat server by creating a /usr/local/catdvServer/catdv.properties file (I’d copy it from the CatDV Server initially and then just change the database url to point to the database server) and make sure your firewall and MySQL settings are set up to allow connections from the Tomcat machine.
Doable, but not for the faint-hearted.
-
Server 6.8 ships with some very simple HTML samples that show you how to do exactly this kind of thing. If you install 6.8 (using the default embedded web browser) then the samples are right there in the root of the web site.
-
Sorry – my mistake – when I said copy the lib folder into catdv2 what I actually meant to say was copy the lib folder into catdv2/WEB-INF.
Sorry
John -
Starting with server 6.8 the preferred method of deploying the web client is using the built in web server. You can still use an external copy of Tomcat, but you have to set it up manually.
Taking your specific questions:
1. The reason you still need to fill in the port if you are using Tomcat is so that the Control Panel can monitor the web service and check it’s running OK. It doesn’t affect the anything in Tomcat.
2. The catdv2.war file contains the CatDV WebClient itself, whereas the websamples.war file contains the sample web apps that you are free to use as the starting point for any custom web client you might want to create.
We no longer deploy the catdv2.war file automatically to Tomcat. The default set up assumes you use the embedded Web Server (which is just embedded Tomcat anyway). Support for using an external copy of Tomcat is really just there for backwards compatibility and also to support running the web server on another machine.
3. The Document Root typically points to web app installed as the default application (websamples by default). The Web Client url is a relative url from the where the CatDV WebClient should appear – traditionally this is /catdv2. None of these settings are relevant if you are using an external copy of Tomcat.
If you want to deploy the Web Client to Tomcat you need to copy the catdv.war file to the Tomcat webapps folder. You then need to manually expand it using jar. You then need to copy the lib folder from the CatDV Server installation directory to inside the catdv2 directory you just created. It should then work OK.
But it’s far easier just to use the embedded server!
John
-
If you could click on View Log and then Save Log Files and send the resultant ZIP file to support at squarebox dot com we’ll take a look.
-
Currently the only way to go back and forth to CS6 is via FCP7 XML, which means you are limited to the fields that can be passed via FCP XML. You can control what fields get sent using the FCP Field mappings in your Prefs, which will also apply to CS6. But until Adobe provide a richer interchange format we are limited to the FCP fields.
-
Just to clarify – you’re saying CatDV Server is running on a Mac, but talking to Active Directory on some other Windows Server? Or do you mean the Mac is using Apple’s OpenDirectory – which isn’t currently officially supported by CatDV’s LDAP integration.
-
Could you send a request to support at squarebox dot com, and we will look into this. Thank you.
-
Sounds wrong. Could you send us an email to support@squarebox.com attaching the CatDV Control Panel log file just after you’ve tried to browse the LDAP repository, so we can see if there are any errors being generated behind the scenes. The log file is in C:\Users\\AppData\Local\Square Box\Logs\CatDV Control Panel Launch Log.txt. Be aware that AppData is a hidden folder (great idea there Microsoft..)
Thanks
Square Box Support