Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Specify a contentProcessor to MT CLT's?
Soph
Is there any way to manually force MT to use a specific content processor via the CLT's, rather than being based off of the extension of the file?
None of my files in TeamSite have extensions, and the number of indexes we have is growing.
Using the "iwgenmetadata" parmeter "-suggest_by_tag" I can use a specific index/project, but this errors out if I have not associated the index with the "none", no extension content processor.
Since we have loads of indexes, and no extensions, every piece of content would unnecessarily be tagged against every index.
I know it can be done via the Java API, but would like to use the CLT's if possible.
Find more posts tagged with
Comments
Migrateduser
Hey Soph -
You can use a path regex to select CP as well if you have no extension. There's an existing enhancement request to support a "catch-all" file-type group but it's not there today.
If you need to create a catch-all, the best way is through the API, which allows you to specify the filename and stream independently. The CIWeb web application provided in
http://devnet.interwoven.com/site.fcgi/techlib/54486
shows most of this, but let me know if you need more example code. CIWeb is also good if you need a MT API for Perl as the Perl binding was deprecated following 3.x. CIWeb will let you call MT functions as command URLs.
Cheers,
Clark
Soph
Clark,
Essentially what I would like to do is to be able to call a specific content processor and a specific project via CLT's without having to explicitly associate a the project to the content processor within the MT server. I want to do this for the sake of efficiency.
I have the sample web app, and have also written a stand alone Java processor that works completely outside of TeamSite, database to MT then persist back to database. But, I was hoping to leverage off of the CLT because it has the TeamSite integration built in.
Thanks,
Soph