nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TS 6.0.0.1 install problem on soloris8

1111111

I upgrade teamsite from 5..5.2 to 6l, my os is solaris 8 . I get the such error message during the installion:
there were jsp compilation errors while compiling webapps execute following to determines the exact errors :
/iw-home/iw-perl/bin/iwperl install_webapps.ipl -f -r

I execute the command and the result like this :
Removing webapp content_center... done.
Installing [ base.tk.war teamsite.tk.war vpreview.tk.war formspub.tk.war ccpro.tk.war ccstd.tk.war metadata.tk.war vannotate.tk.war customer ] as webapp content_center... Exception in thread "main" java.net.UnknownHostException: java.sun.com
at java.net.InetAddress.getAllByName0(InetAddress.java:566)
at java.net.InetAddress.getAllByName0(InetAddress.java:535)
at java.net.InetAddress.getByName(InetAddress.java:444)
at java.net.Socket.<init>(Socket.java:95)
at sun.net.NetworkClient.doConnect(NetworkClient.java:45)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:334)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:520)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:270)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:280)
at sun.net.www.http.HttpClient.New(HttpClient.java:292)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:417)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:510)
at java.net.URL.openStream(URL.java:793)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startDTDEntity(Unknown Source)
at org.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at com.interwoven.webapp.TaglibMunger.read(TaglibMunger.java:359)
at com.interwoven.webapp.TaglibMunger.addInput(TaglibMunger.java:158)
at com.interwoven.webapp.PhantomWebapp.copyFrom(PhantomWebapp.java:101)
at com.interwoven.webapp.WebappMunger.addInput(WebappMunger.java:79)
at com.interwoven.webapp.WebappMunger.main(WebappMunger.java:185)
Configuring JSPs... Missing directory /data/interwoven/iw-home/httpd/webapps/content_center/WEB-INF!
OK.
Unable to open /data/interwoven/iw-home/httpd/webapps/content_center/META-INF/toolkits.xml at install_webapps.ipl line 335.

How can i resolve this ?

Find more posts tagged with

Comments

pflory

111,

The lines in the stack dump near the top:
Exception in thread "main" java.net.UnknownHostException: java.sun.com ...

indicate that a network connection was attempted.

I haven't seen/heard about this, but out of curiousity, does this machine have access to the internet?

Do you have all the required Solaris patches for TeamSite 6 installed? (see manual)

Paul

------------
Paul Flory

1111111

Thanks, I unpack the tsadmin.war and base.tk.war. find all tld file and remove the line under following.
<!DOCTYPE ..........>
Then I execute the install_webapps.ipl , The teamsite6l can be installed successully.
But i don't know whether this operation cause any problem?

Michael

Just in case anyone else is having this problem:

I encountered the same problem when installing on an isolated test network on a W2K machine with 6.0 L. This machine has no access to the internet and this would appear to the source of the error described in this post.

The workaround described by 111 also worked for me -- thanks very much for posting it! I haven't come across any problems yet by removing those lines -- presumably it just doesn't validate the XML against the DTD?

Cheers
Michael

Edited by Michael on 01/08/04 03:54 AM (server time).

Migrateduser

The workaround proposed by 111 should not create any problems. The DOCTYPE headers are (at present, in this context) only being used for validation purposes. There are no external entity declarations.

From your descriptions, it is likely that the system is trying to validate the web.xml files against a DTD published by Sun. I will investigate this.

Thank you both for reporting the problem and a viable workaround.

Brinko Kobrin
Interwoven Staff Engineer

setJobowner.PNG

Marvin

Hi,

we'd encountered the same problem. Will this problem also occur when upgrading a 5.5.2 System ?
Also will there be a fix instead of a workaround ?. I'm a little bit afraid, because we're just planning to upgrade from 5.5.2 to 6.0L in this quarter and we like to have a proper installation, instead of many manual steps.

Thanks

Marvin

Michael

Hi Marvin,

I should have made clear in my initial post -- I was upgrading from 5.5.2 SP3 to 6.0L. So you may have the same problem when upgrading... but only if your machine doesn't have internet access.

I agree that it should either be fixed, or at the very least documented as a requirement for the installation.

Good luck with your upgrade!

Cheers, Michael.

Migrateduser

This problem has been identified as bug 50560. I do not yet know in which release it will be fixed.

Brinko Kobrin
Interwoven Staff Engineer

Untitled3.jpg

Michael

Hi

I have had a request for more details on how you alter the war files so please find following below more of a step-by-step explanation:

The two files you are modifying are
- iw-home/httpd/webapps/tsadmin.war
- iw-home/private/lib/content_center/base.tk.war

You should take a backup of these files, but don't put the copy in the same directory as the original -- the script you run later will expand all war files in the webapps directory (or so it appears).

In case you weren't aware war files are in zip format so you can open them with a tool such as WinZip.

Take one war file at a time and extract all files to a new directory -- make sure you extract with directories.

Edit the tld files which are in WEB-INF/tlds in the new directory -- tsadmin.war had one file and base.tk.war had six. For each of these tld files modify the line that looks like

<!DOCTYPE taglib PUBLIC "-//Sun..." "http://...." >

to be something like

<!DOCTYPE taglib >

Now recreate your war file. Ensure that the path information in your war file is consistent with your original backup. Put your new war file in place of the original.

Repeat for the other war file.

Execute install_webapps.ipl -i -f as instructed by the installation program and it will hopefully run successfully.

At this point your TeamSite upgrade/installation should be up and running!

I hope this helps.

Cheers, Michael

Johnny

I have also encountered this problem and raised it with support.

we are on win2k

if you are behind a proxy and cant be ****'ed mangling all the xml files, you can use this version of install_webapps.ipl i hacked. Basically sets the jvm properties for the proxy settings... you will need to customise it for your settings.

Lines
581
662
741

are where you need to set Dhttp.proxyHost, http.proxyPort etc.

I think line 741 is where the real problem is, but i set it on all three just incase.

Hopefully there is some setting (perhaps maybe in xalan or whatever parser is being used) to not valid the files.

I have seen this before on the metatagger 3.0 war.

John Cuiuli

Johnny

Just another note.

win2k

at one point we tried uninstalling 6L.

It actually deleted all of our custom files that live in any product directories

IE

/iw-home/httpd/iw-bin/
/iw-perl/...../lib/

just be careful with any bright ideas Smiley Happy

John Cuiuli

pflory

We have a related problem to the original one posted here -- we used the
modified install_webapps.ipl that user 111 supplied in this thread, which
sets proxy settings for the java command, but now we are facing a problem
with proxy authentication (see error below).

We are on Windows and able to get through the proxy via Internet Explorer
using a domain\username combo like:
domain1\user1

and the respective password for the user.

However, this same combo is producing an HTTP 407 error in the install script (again below).

We tried escaping the backslashes for the username. but still get errors from this:


system($java, '-Dhttp.proxyHost="proxyserver"', '-Dhttp.proxyPort="8080"', '-Dhttp.proxyUser="domain\\username"', '-Dhttp.proxyPassword="****"', '-Dhttp.nonProxyHosts="cms.*"',   ...

(Single backslashes produce the same error)

Anyone have ideas about what syntax or format is needed to make
java proxy settings on windows happy? Other thoughts?

Thanks!
Paul

install_webapps.ipl ERROR:


E:\iw-home\install>iwperl install_webapps.ipl -f -r
Stopping Interwoven UI services... done.
Removing webapp content_center... done.
Installing [ base.tk.war teamsite.tk.war vpreview.tk.war formspub.tk.war ccstd.tk.war ccpro.tk.war vannotate.tk.war meta
data.tk.war customer ] as webapp content_center... Exception in thread "main" java.io.IOException: Server returned HTTP
response code: 407 for URL: http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:604)
        at java.net.URL.openStream(URL.java:793)
[...]

Perhaps the coffee that was spilled into the TS server has something to do with it? Smiley Happy

Paul Flory

pflory

Here's a way to solve the problem when you have no internet connection during a TS 6 install.

1) setup/use a local website to store the sun DTD, web-jsptaglibrary_1_1.dtd
2) place the DTD file from sun into your local webserver docroot, with the same dir path to the file, e.g.,
...\j2ee\dtds\web-jsptaglibrary_1_1.dtd
3) update your TS box's hosts file to fool it into using your local copy of the sun DTD. E.g., the line might be
10.11.11.90 java.sun.com
4) rerun install_webapps.ipl

Before #3 you may want to check the resolution trick from a web browser, with proxy turned off to see if you can resolve and get to the file.

Paul

Paul Flory

Michael

The main content of this thread has been published as Knowledge Base Article: 51226 . It kind of makes the workarounds more official

Hope this helps

Cheers
Michael