<br /><br />If nothing else works, then you definitely<br />need a DCF file. At the bottom of the file, there is valid markup you can use<br />to associate composer types for the doctype associated with the file.<br /><br /><br /><br /><br /><br /><br /><br />Looks something like this:<br /><br /><br /><br /><br /><br /><br /><br /><composition><br /><br /><br /><br /><compose<br/>type="pdf"></compose><br /><br /><br /><br /><compose<br/>type="web"></compose><br /><br /><br /><br /><compose<br/>type="xsl"></compose><br /><br /><br /><br /><compose<br/>type="xslfo"></compose><br /><br /><br /><br /><compose<br/>type="htmlfile"></compose><br /><br /><br /><br /></composition><br /><br /><br /><br /><br /><br /><br /><br />The “type” names correspond to<br />the default composer configuration types that ship with PE (look in the<br />custom\composer folder, these correspond to the *.ccf files).<br /><br /><br /><br /><br /><br /><br /><br />Restart PE and the clients (you also have<br />to restart clients when you make config changes to the doctypes/apps).<br /><br /><br /><br /><br /><br /><br /><br />Speaking of which, has anyone had any<br />extensive experience with content pipelines and custom composers? Just curious…<br /><br /><br /><br /><br /><br /><br /><br />Hope this helps.<br /><br /><br /><br /><br /><br /><br /><br />-Jason<br /><br /><br /><br /><br /><br /><br /><br /> <br /><br /><br /><br /><br /><br /> <br /><br />From: Steven Janoff<br /> <br /><br />Sent: Monday, June 11, 2007 1:42<br />PM<br /><br />To: adepters@arbortext.com<br /><br />Subject: RE: Can't get PE Server<br />to recognize our custom doctype.<br /><br /><br /><br /> <br /><br /><br /><br /><br /><br />Hi Gary,<br /><br /><br /><br /><br /><br /><br /><br />In addition to restarting the PE server,<br />as Steve Thompson suggests, we have also found the following to be helpful.<br /><br /><br /><br /><br /><br /><br /><br />In the Advanced Preferences of Editor<br />(Tools > Preferences > Advanced button), go to "catalogpath",<br />and at the very end of the list of catalog paths, add this one, if it is not<br />already there (Editor *may* have added this automatically when it encountered the<br />catalog in your custom-doctypes folder, assuming you closed/reopened Editor<br />after adding the custom files):<br /><br /><br /><br /><br /><br /><br /><br /> <span<br/>style='font-size:10.0pt;font-family:Arial;color:blue'>C:\Program<br />Files\Arbortext\Editor\custom\doctypes<br /><br /><br /><br /><br /><br /><br /><br />Or, of course, whatever similar path is<br />required to get to the custom-doctypes folder.<br /><br /><br /><br /><br /><br /><br /><br />If I understand the composition process<br />correctly (Print Preview, PDF), Editor goes out to the PE server and looks for<br />the corresponding folder with this doctype: C:\Program<br />Files\Arbortext\PE\custom\doctypes, where C in this case is the hard drive of the<br />server machine.<br /><br /><br /><br /><br /><br /><br /><br />I believe the Tomcat restart will actually<br />solve your problem, but we have had this problem persist with certain custom<br />doctypes even after a PE restart. The addition of the catalog path<br />*might* be the extra step that helps in this case. If not, it might<br />require opening a PTC support call.<br /><br /><br /><br /><br /><br /><br /><br />Hope that helps.<br /><br /><br /><br /><br /><br /><br /><br />Steve<br /><br /><br /><br /><br /><br /><br /><br />--<br /><br /><br /><br /><span<br/>style='font-size:10.0pt;font-family:Arial;color:navy'>Steve Janoff<br /><br /><br /><br />Information Manager, Specialty Engineering<br /><br /><br /><br />General Atomics Aeronautical Systems, Inc.<br /><br /><br /><br />Tel. (858) 909-5164<br /><br /><br /><br />Fax (858) 455-4668<br /><br /><br /><br />Steven.Janoff@uav.com<br /><br /><br /><br /><br /><br /><br /><br /> <br /><br /><span<br/>style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:<font<br/>size=2 face=Tahoma><br />EXT-Thompson, Steve <br /><br />Sent: Monday, June 11, 2007 9:31<br />AM<br /><br />To: adepters@arbortext.com<br /><br />Subject: RE: Can't get PE Server<br />to recognize our custom doctype.<br /><br /><br /><br />Gary,<br /><br /><br /><br />Just because we all occasionally forget<br />even the most basic things (and it's the 'simple' things that will bite you<br />every time), I have to ask:You did restart Tomcat on the server after<br />placing those files, yes?<br /><br /><br /><br /> <br /><br />Last time I saw that "Document type<br />not installed..." message here, it was because that simple step had been<br />forgotten. By someone who has been working with Adept/Arbortext Editorfor<br />years.<br /><br /><br /><br /> <br /><br /> <br /><br /><br /><br /><br /><br /> <br /><br /> <br /><br />Probably not even two cents-worth,<br /><br /><br /><br /> <br /><br />Steve<br />Thompson<br /><br />(316)977-0515<br /><br />When<br />the only tool you have is a hammer,<br /><br />Everything<br />looks like a hard disk... <br /><br /><br /><br /> <br /><br /><br /><br /><br /><br /> <br /><br /><br /><br /><br /><br /><br /><br /><br /><br /> <br /><br /><span<br/>style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:<font<br/>size=2 face=Tahoma> Kristina<br />Pike / Convex Technologies, LLC <br /><br />Sent: Monday, June 11, 2007 10:43<br />AM<br /><br />To: adepters@arbortext.com<br /><br />Subject: RE: Can't get PE Server<br />to recognize our custom doctype.<br /><br /><br /><br />The first thing I see is that there is a<br />double quote before URI but not one to close it. Also, you might want to try<br />using the exact path where the schema is located. In my experience, Ax does not<br />play well with relative paths. <br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /> <br /><br /><span<br/>style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:<font<br/>size=2 face=Tahoma> Gary<br />Ouzts <br /><br />Sent: Monday, June 11, 2007 10:42<br />PM<br /><br />To:<br />Adepters@maillist.arbortext.com<br /><br />Subject: Can't get PE Server to<br />recognize our custom doctype.<br /><br /><br /><br />We're trying to set up a PE Server to handle print/PDF requests from<br />the Arbortext Editor. We have a custom XML schema and are using Styler to<br />generate the stylesheets. We're using release 5.3 M010. We've placed our<br />schema, stylesheet, and catalog file in the custom doctypes folders on the PE<br />Server and on the machine with the Arbortext Editor. The problem is when we<br />attempt to send a request to the PE Server from the Arbortext Editor using the<br />menu: "File->Compose->PDF File…", an error dialog pops up<br />stating: "[A20448] Document type not installed on the PE server. Check the<br />server's catalog path setting." So I'm assuming there's something wrong<br />with the catalog file in our custom doctypes folder? The content of our catalog<br />file is a single line: <br /><br />"URI "WorkOrder.xsd" "workorder.xsd" <br /><br />(workorder is the name of our custom doctype, and the above referenced file is<br />the XML schema file.) <br /><br />One other tidbit: When I use the "Help->About Arbotext Editor->PE<br />Configuration" menu in the Editor, the report that is generated from that<br />request does have a section for our custom doctype, but in the subsection<br />titled "Document Type/Composer Associations", it says "No<br />doctype/composer associations." <br /><br /><br /><br />Does anyone have any pointers on what to look at to resolve this problem?<br />Thanks, Gary.