Are your DTDs/FOSIs in the install directory or at least the same machine.
PE didn't like using APTCUSTOM and APTCATPATH when they were on a
different network location. Once I got the files to the machine,
everything stabilized.
..dan
> Hello all,
>
>
>
> I am working on setting up PE 5.4 M100 on a dev server to begin
> composition testing.
>
>
>
> I have several custom SGML DTDs and FOSIs that I have recompiled for
> 5.4, and a few custom XML DTDs with FOSI stylesheets.
>
>
>
> Since I had 5.3 running on this server (using Tomcat 5.5), I installed
> the 1.6 JRE and Tomcat 6 (the distro from the media), then PE.
>
>
>
> I got everything to come up fine, but I cannot get my custom doctypes to
> show up under the composition information.
>
>
>
> I checked the DCOM config for the service account we run PE under,
> everything's fine there. Set APTPATH to point to the 5.4 install tree,
> and set my APTCUSTOM to point at the custom directory containing my
> custom doctypes (under the doctype directory, with a catalog file at the
> root).
>
>
>
> I restart PE, it comes up fine, but when I open the index page and check
> the composition information, under the doctypes it lists the local
> doctypes for the PE install tree but no custom doctypes from the
> APTCUSTOM path.
>
>
>
> I looked through the help files for a bit, but nothing stands out. Is
> there a gotcha or caveat for PE 5.4 loading custom apps that I've
> missed? Is the default PE to still use FOSI, or is APP the new default
> in 5.4? Also, I noticed in my e3config.xml file, there was no defined
> "pool-tie" subprocess, which is typically used to field composition
> requests from Arbortext clients (but there was a defined subprocess for
> windchill, but it's enabled="no"). I added pool-tie and set the logging
> to verbose-debug, and it seems to initialize the subprocess just fine,
> but I cannot publish with the custom doctypes (returns the "doctype not
> installed on the PE server" error).
>
>
>
> What am I missing here?
>
>
>
> Thanks,
>
>
>
> -Jason
>
>