cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Can't get PE Server to recognize our custom doctype.

Newbie

Re: Can't get PE Server to recognize our custom doctype.

Hi Gary,

I've run into this problem before as well. It's usually due to a missing
DTD/Schema component (if one is referenced), or a path/name problem in the
catalog file. I also seem to recall that having a DCF file can help, too.

In the single line of your catalog file below, there appears to be an odd
number of quote characters, but I don't know if that's just an email issue
or if you've stubbed out one or more values.

You reported that the schema, the stylesheet, and the catalog file are all
in the custom doctypes area on the PE server. If your schema doesn't
require additional files, then I'd try creating a DCF file. There's
information in the Help on how to create one.

Hope that helps,
Jason





"Gary Ouzts" <gary.r.ouzts@boeing.com>
06/11/2007 08:41 PM
Please respond to
<adepters@arbortext.com>


To
<adepters@maillist.arbortext.com>
cc

Subject
Can't get PE Server to recognize our custom doctype.






We're trying to set up a PE Server to handle print/PDF requests from the
Arbortext Editor. We have a custom XML schema and are using Styler to
generate the stylesheets. We're using release 5.3 M010. We've placed our
schema, stylesheet, and catalog file in the custom doctypes folders on the
PE Server and on the machine with the Arbortext Editor. The problem is
when we attempt to send a request to the PE Server from the Arbortext
Editor using the menu: "File->Compose->PDF File…", an error dialog pops up
stating: "[A20448] Document type not installed on the PE server. Check the
server's catalog path setting." So I'm assuming there's something wrong
with the catalog file in our custom doctypes folder? The content of our
catalog file is a single line:
"URI "WorkOrder.xsd" "workorder.xsd"
(workorder is the name of our custom doctype, and the above referenced
file is the XML schema file.)
One other tidbit: When I use the "Help->About Arbotext Editor->PE
Configuration" menu in the Editor, the report that is generated from that
request does have a section for our custom doctype, but in the subsection
titled "Document Type/Composer Associations", it says "No doctype/composer
associations."

Does anyone have any pointers on what to look at to resolve this problem?
Thanks, Gary. >> To unsubscribe from the list, send an email to
listmanager@maillist.arbortext.com with the following in the body:
unsubscribe adepters - For additional information on the adepters list
(how to subscribe or unsubscribe etc), send an email to:
listmanager@maillist.arbortext.com with the following in the body: info
Adepters - You may also go to forums.arbortext.com, enter the Adepters
folder and change your subscription options and preferences.>>

Tags (2)
8 REPLIES 8
Highlighted

RE: Can't get PE Server to recognize our custom doctype.

The first thing I see is that there is a double quote before URI
but not one to close it. Also, you might want to try using the exact path where
the schema is located. In my experience, Ax does not play well with relative
paths.






From: Gary Ouzts

Sent: Monday, June 11, 2007 10:42
PM
To: Adepters@maillist.arbortext.com
Subject: Can't get
PE Server to recognize our custom doctype.


We're trying to set up a PE Server to handle print/PDF requests
from the Arbortext Editor. We have a custom XML schema and are using Styler to
generate the stylesheets. We're using release 5.3 M010. We've placed our
schema, stylesheet, and catalog file in the custom doctypes folders on the PE
Server and on the machine with the Arbortext Editor. The problem is when we
attempt to send a request to the PE Server from the Arbortext Editor using the
menu: "File->Compose->PDF File…", an error dialog pops up stating:
"[A20448] Document type not installed on the PE server. Check the server's
catalog path setting." So I'm assuming there's something wrong with the
catalog file in our custom doctypes folder? The content of our catalog file is
a single line:
"URI "WorkOrder.xsd" "workorder.xsd"
(workorder is the
name of our custom doctype, and the above referenced file is the XML schema
file.)
One other tidbit: When I use the "Help->About Arbotext
Editor->PE Configuration" menu in the Editor, the report that is generated
from that request does have a section for our custom doctype, but in the
subsection titled "Document Type/Composer Associations", it says "No
doctype/composer associations."

Does anyone have any pointers on what
to look at to resolve this problem? Thanks, Gary. >> To unsubscribe from
the list, send an email to listmanager@maillist.arbortext.com with the
following in the body: unsubscribe adepters - For additional information on
the adepters list (how to subscribe or unsubscribe etc), send an email to:
listmanager@maillist.arbortext.com with the following in the body: info
Adepters - You may also go to forums.arbortext.com, enter the Adepters folder
and change your subscription options and preferences.>>
Highlighted

RE: Can't get PE Server to recognize our custom doctype.

class=478122416-11062007>Gary,

class=478122416-11062007>Just because we all occasionally forget even the most
basic things (and it's the 'simple' things that will bite you every time), I
have to ask:You did restart Tomcat on the server after placing those
files, yes?

Last
time I saw that "Document type not installed..." message here, it was because
that simple step had been forgotten. By someone who has been working with
Adept/Arbortext Editorfor years.


Probably not even two cents-worth,

Steve
Thompson
face="Times New Roman">
(316)977-0515
face=Arial size=2>When the only tool you have is a hammer,face="Times New Roman">
Everything looks like
a hard disk...








From: Kristina Pike / Convex Technologies, LLC

Sent: Monday, June 11,
2007 10:43 AM
To: adepters@arbortext.com
Subject: RE: Can't
get PE Server to recognize our custom doctype.



The first thing I see is that there is a double quote before URI
but not one to close it. Also, you might want to try using the exact path where
the schema is located. In my experience, Ax does not play well with relative
paths.






From: Gary Ouzts

Sent: Monday, June 11, 2007 10:42
PM
To: Adepters@maillist.arbortext.com
Subject: Can't get
PE Server to recognize our custom doctype.


We're trying to set up a PE Server to handle print/PDF requests
from the Arbortext Editor. We have a custom XML schema and are using Styler to
generate the stylesheets. We're using release 5.3 M010. We've placed our
schema, stylesheet, and catalog file in the custom doctypes folders on the PE
Server and on the machine with the Arbortext Editor. The problem is when we
attempt to send a request to the PE Server from the Arbortext Editor using the
menu: "File->Compose->PDF File…", an error dialog pops up stating:
"[A20448] Document type not installed on the PE server. Check the server's
catalog path setting." So I'm assuming there's something wrong with the
catalog file in our custom doctypes folder? The content of our catalog file is
a single line:
"URI "WorkOrder.xsd" "workorder.xsd"
(workorder is the
name of our custom doctype, and the above referenced file is the XML schema
file.)
One other tidbit: When I use the "Help->About Arbotext
Editor->PE Configuration" menu in the Editor, the report that is generated
from that request does have a section for our custom doctype, but in the
subsection titled "Document Type/Composer Associations", it says "No
doctype/composer associations."

Does anyone have any pointers on what
to look at to resolve this problem? Thanks, Gary. >> To unsubscribe from
the list, send an email to listmanager@maillist.arbortext.com with the
following in the body: unsubscribe adepters - For additional information on
the adepters list (how to subscribe or unsubscribe etc), send an email to:
listmanager@maillist.arbortext.com with the following in the body: info
Adepters - You may also go to forums.arbortext.com, enter the Adepters folder
and change your subscription options and preferences.>>
>> To unsubscribe from the list, send an email to
listmanager@maillist.arbortext.com with the following in the body: unsubscribe
adepters - For additional information on the adepters list (how to subscribe or
unsubscribe etc), send an email to: listmanager@maillist.arbortext.com with the
following in the body: info Adepters - You may also go to forums.arbortext.com,
enter the Adepters folder and change your subscription options and
preferences.>>
Highlighted

RE: Can't get PE Server to recognize our custom doctype.

Hi Gary,


In addition to restarting the PE server, as Steve Thompson
suggests, we have also found the following to be helpful.


In the Advanced Preferences of Editor (Tools >
Preferences > Advanced button), go to "catalogpath", and at the very end of
the list of catalog paths, add this one, if it is not already there (Editor
*may* have added this automatically when it encountered the catalog in your
custom-doctypes folder, assuming you closed/reopened Editor after adding the
custom files):


face=Arial color=#0000ff size=2>C:\Program
Files\Arbortext\Editor\custom\doctypes


Or, of course, whatever similar path is required to get to
the custom-doctypes folder.


If I understand the composition process correctly (Print
Preview, PDF), Editor goes out to the PE server and looks for the corresponding
folder with this doctype: C:\Program Files\Arbortext\PE\custom\doctypes,
where C in this case is the hard drive of the server
machine.


I believe the Tomcat restart will actually solve your
problem, but we have had this problem persist with certain custom doctypes even
after a PE restart. The addition of the catalog path *might* be the extra
step that helps in this case. If not, it might require opening a PTC
support call.


Hope that helps.


Steve




--

Steve
Janoff


Information Manager, Specialty
Engineering
General Atomics Aeronautical Systems, Inc.

Tel. (858) 909-5164

Fax (858) 455-4668

Steven.Janoff@uav.com




From: EXT-Thompson, Steve

Sent: Monday, June 11, 2007 9:31
AM
To: adepters@arbortext.com
Subject: RE: Can't get PE
Server to recognize our custom doctype.



class=478122416-11062007>Gary,

class=478122416-11062007>Just because we all occasionally forget even the most
basic things (and it's the 'simple' things that will bite you every time), I
have to ask:You did restart Tomcat on the server after placing those
files, yes?

Last
time I saw that "Document type not installed..." message here, it was because
that simple step had been forgotten. By someone who has been working with
Adept/Arbortext Editorfor years.


Probably not even two cents-worth,

Steve
Thompson
face="Times New Roman">
(316)977-0515
face=Arial size=2>When the only tool you have is a hammer,face="Times New Roman">
Everything looks like
a hard disk...








From: Kristina Pike / Convex Technologies, LLC

Sent: Monday, June 11,
2007 10:43 AM
To: adepters@arbortext.com
Subject: RE: Can't
get PE Server to recognize our custom doctype.



The first thing I see is that there is a double quote before URI
but not one to close it. Also, you might want to try using the exact path where
the schema is located. In my experience, Ax does not play well with relative
paths.






From: Gary Ouzts

Sent: Monday, June 11, 2007 10:42
PM
To: Adepters@maillist.arbortext.com
Subject: Can't get
PE Server to recognize our custom doctype.


We're trying to set up a PE Server to handle print/PDF requests
from the Arbortext Editor. We have a custom XML schema and are using Styler to
generate the stylesheets. We're using release 5.3 M010. We've placed our
schema, stylesheet, and catalog file in the custom doctypes folders on the PE
Server and on the machine with the Arbortext Editor. The problem is when we
attempt to send a request to the PE Server from the Arbortext Editor using the
menu: "File->Compose->PDF File…", an error dialog pops up stating:
"[A20448] Document type not installed on the PE server. Check the server's
catalog path setting." So I'm assuming there's something wrong with the
catalog file in our custom doctypes folder? The content of our catalog file is
a single line:
"URI "WorkOrder.xsd" "workorder.xsd"
(workorder is the
name of our custom doctype, and the above referenced file is the XML schema
file.)
One other tidbit: When I use the "Help->About Arbotext
Editor->PE Configuration" menu in the Editor, the report that is generated
from that request does have a section for our custom doctype, but in the
subsection titled "Document Type/Composer Associations", it says "No
doctype/composer associations."

Does anyone have any pointers on what
to look at to resolve this problem? Thanks, Gary. >> To unsubscribe from
the list, send an email to listmanager@maillist.arbortext.com with the
following in the body: unsubscribe adepters - For additional information on
the adepters list (how to subscribe or unsubscribe etc), send an email to:
listmanager@maillist.arbortext.com with the following in the body: info
Adepters - You may also go to forums.arbortext.com, enter the Adepters folder
and change your subscription options and preferences.>>
>> To unsubscribe from the list, send an email to
listmanager@maillist.arbortext.com with the following in the body: unsubscribe
adepters - For additional information on the adepters list (how to subscribe or
unsubscribe etc), send an email to: listmanager@maillist.arbortext.com with the
following in the body: info Adepters - You may also go to forums.arbortext.com,
enter the Adepters folder and change your subscription options and
preferences.>> >> To unsubscribe from the list, send an email to
listmanager@maillist.arbortext.com with the following in the body: unsubscribe
adepters - For additional information on the adepters list (how to subscribe or
unsubscribe etc), send an email to: listmanager@maillist.arbortext.com with the
following in the body: info Adepters - You may also go to forums.arbortext.com,
enter the Adepters folder and change your subscription options and
preferences.>>
Highlighted

RE: Can't get PE Server to recognize our custom doctype.

<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 />&lt;composition&gt;<br /><br /><br /><br />&lt;compose&lt;br/&gt;type="pdf"&gt;&lt;/compose&gt;<br /><br /><br /><br />&lt;compose&lt;br/&gt;type="web"&gt;&lt;/compose&gt;<br /><br /><br /><br />&lt;compose&lt;br/&gt;type="xsl"&gt;&lt;/compose&gt;<br /><br /><br /><br />&lt;compose&lt;br/&gt;type="xslfo"&gt;&lt;/compose&gt;<br /><br /><br /><br />&lt;compose&lt;br/&gt;type="htmlfile"&gt;&lt;/compose&gt;<br /><br /><br /><br />&lt;/composition&gt;<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 &gt; Preferences &gt; 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 /> &lt;span&lt;br/&gt;style='font-size:10.0pt;font-family:Arial;color:blue'&gt;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 />&lt;span&lt;br/&gt;style='font-size:10.0pt;font-family:Arial;color:navy'&gt;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 />&lt;span&lt;br/&gt;style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'&gt;From:&lt;font&lt;br/&gt;size=2 face=Tahoma&gt;<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 />&lt;span&lt;br/&gt;style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'&gt;From:&lt;font&lt;br/&gt;size=2 face=Tahoma&gt; 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 />&lt;span&lt;br/&gt;style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'&gt;From:&lt;font&lt;br/&gt;size=2 face=Tahoma&gt; 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-&gt;Compose-&gt;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-&gt;About Arbotext Editor-&gt;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.

Highlighted

Re: Can't get PE Server to recognize our custom doctype.

When I had this problem awhile back Arbortext / PTC support had me set the following:


Within Epic> Tools > PreferencesAdvanced set the following

1) catalog path to your custom\doctype folder

2) peserver url (this usually gets set at install, however not always)

3) set your usersenvironment variable - APTCUSTOM to your custom folder on the PE server

4) make sure you have a .dcf file.


You can verify if PE server isfinding your catalog / document types by opening the P.E. Configuration software, select "TomCat/IIS tab, click on "Launch PE index page" click on "composition configuration", click on "Document Types". I found the P.E. Configuration software to be a tremendous help in debugging.


Hope some of this helps; good luck!!!






>>> "Gary Ouzts" <gary.r.ouzts@boeing.com> 6/11/2007 8:41 PM >>>
We're trying to set up a PE Server to handle print/PDF requests from the Arbortext Editor. We have a custom XML schema and are using Styler to generate the stylesheets. We're using release 5.3 M010. We've placed our schema, stylesheet, and catalog file in the custom doctypes folders on the PE Server and on the machine with the Arbortext Editor. The problem is when we attempt to send a request to the PE Server from the Arbortext Editor using the menu: "File->Compose->PDF File…", an error dialog pops up stating: "[A20448] Document type not installed on the PE server. Check the server's catalog path setting." So I'm assuming there's something wrong with the catalog file in our custom doctypes folder? The content of our catalog file is a single line:
"URI "WorkOrder.xsd" "workorder.xsd"
(workorder is the name of our custom doctype, and the above referenced file is the XML schema file.)
One other tidbit: When I use the "Help->About Arbotext Editor->PE Configuration" menu in the Editor, the report that is generated from that request does have a section for our custom doctype, but in the subsection titled "Document Type/Composer Associations", it says "No doctype/composer associations."

Does anyone have any pointers on what to look at to resolve this problem? Thanks, Gary. >> To unsubscribe from the list, send an email to listmanager@maillist.arbortext.com with the following in the body: unsubscribe adepters - For additional information on the adepters list (how to subscribe or unsubscribe etc), send an email to: listmanager@maillist.arbortext.com with the following in the body: info Adepters - You may also go to forums.arbortext.com, enter the Adepters folder and change your subscription options and preferences.>>
Highlighted

RE: Can't get PE Server to recognize our custom doctype.

Hi Jason,

I haven't played too much with the content pipeline or custom composers,
but the Java class we use when making f=java calls is highly customized to
perform a variety of activities.

Some of these activities can be time-consuming, so we're thinking about
separating these out into processes that don't use a PE subprocess pool.
It wouldn't be too difficult to set up a separate Java class that acts as
a servlet and parses out HTTP requests to do separate work (e.g. run Ant
scripts, XSLT, etc.).

After seeing Charles Angione demonstrate JMeter to stress-test a PE server
at the recent PTC-User conference, I'm focused on getting that set up
first.

Regards,
Another Jason




"Buss, Jason A" <jabuss@cessna.textron.com>
06/11/2007 01:41 PM
Please respond to
<adepters@arbortext.com>


To
"adepters@arbortext.com" <adepters@arbortext.com>
cc

Subject
RE: Can't get PE Server to recognize our custom doctype.






If nothing else works, then you definitely need a DCF file. At the bottom
of the file, there is valid markup you can use to associate composer types
for the doctype associated with the file.

Looks something like this:

<composition>
<compose type="pdf"></compose>
<compose type="web"></compose>
<compose type="xsl"></compose>
<compose type="xslfo"></compose>
<compose type="htmlfile"></compose>
</composition>

The â€Ã
“type� names correspond to the default composer configuration types
that ship with PE (look in the custom\composer folder, these correspond to
the *.ccf files).

Restart PE and the clients (you also have to restart clients when you make
config changes to the doctypes/apps).

Speaking of which, has anyone had any extensive experience with content
pipelines and custom composers? Just curious…

Hope this helps.

-Jason

Highlighted

Can't get PE Server to recognize our custom doctype.

We're trying to set up a PE Server to handle print/PDF requests from the Arbortext Editor. We have a custom XML schema and are using Styler to generate the stylesheets. We're using release 5.3 M010. We've placed our schema, stylesheet, and catalog file in the custom doctypes folders on the PE Server and on the machine with the Arbortext Editor. The problem is when we attempt to send a request to the PE Server from the Arbortext Editor using the menu: "File->Compose->PDF File…", an error dialog pops up stating: "[A20448] Document type not installed on the PE server. Check the server's catalog path setting." So I'm assuming there's something wrong with the catalog file in our custom doctypes folder? The content of our catalog file is a single line:
"URI "WorkOrder.xsd" "workorder.xsd"
(workorder is the name of our custom doctype, and the above referenced file is the XML schema file.)
One other tidbit: When I use the "Help->About Arbotext Editor->PE Configuration" menu in the Editor, the report that is generated from that request does have a section for our custom doctype, but in the subsection titled "Document Type/Composer Associations", it says "No doctype/composer associations."

Does anyone have any pointers on what to look at to resolve this problem? Thanks, Gary.
Highlighted

Re: Can't get PE Server to recognize our custom doctype.

I'd like to thank everyone that took the time to respond to my PE Server posting. I tried each of the suggestions, but still have been unable to get it to work. But I appreciate all the responses, some of which took me down new trails that will help in the future, I'm sure. I guess the next step will be a call into PTC support. Thanks again, Gary.
Announcements