Plugin: SageTV Web Interface V2 for Jetty

[mkanet]

jreichen (or anyone else good at SSL/Java)

I have an existing Starfield signed SSL certificate installed on my II7 webserver (same machine that Jetty/sageTVserver is installed on). Since I already have this fancy certificate, I thought I'd use it instead of my existing poor-man's self-signed one for my jetty based apps.

My Starfield signed chained SSL certificate consists of two files: xxx.cer & xxx.p7b (intermediate certificate)

I'm looking for the easiest way to convert this PEM based certificate package to a DER based format (compatible with java).

It looks like I'm missing a critical step to getting this to work right. Can someone please tell me what I'm missing?

There are the steps I'm using:

1) Convert my .cer file to a .der file (using a converter such as this one.
2) Run this command: keytool -import -trustcacerts -file mycertificate.der -keystore c:\.keystore -storepass 123456
3) Follow the Jetty SSL instructions exactly... putting the .keystore file in the correct place and using "123456" for all the jetty.ssl.xxxxxx passwords (defined in JettyStarter.properties).

The end result is that the webpage will not be displayed at all. As soon as I put my old self-signed .keystore file back, it works again.

I have a strong feeling I need to insert the intermediate certificate(s) in the .keystore file as well, but I dont know how to do it.

Can someone please help? I'm sure this would also help anyone trying to do the same thing sometime in the future through a simple forum thread search.

Thanks a million for all the help so far guys!

[ArcAiN6]

just out of curiosity, is there supposed to be nielm_sagewebserver folder inside my jetty/webapps folder?

the reason i ask is i have 3 *.war files, and only two associated folders:
bmt.war ---> bmt folder
nielm_sagewebserver.war
SageWebApp.war ---> SageWebApp folder

just wondering if something is messed up or not.

[jreichen]

Nothing's messed up. Slugger configured the context xml to extract the war to the system's temp directory. I've been meaning to follow up with him to see if he knows something I don't

[Slugger]

Originally Posted by ArcAiN6

just out of curiosity, is there supposed to be nielm_sagewebserver folder inside my jetty/webapps folder?

the reason i ask is i have 3 *.war files, and only two associated folders:
bmt.war ---> bmt folder
nielm_sagewebserver.war
SageWebApp.war ---> SageWebApp folder

just wondering if something is messed up or not.

Originally Posted by jreichen

Nothing's messed up. Slugger configured the context xml to extract the war to the system's temp directory. I've been meaning to follow up with him to see if he knows something I don't

The reason for this choice is to support hot deploy on MS Windows systems. By using the system's temp dir, a hot deploy will always explode the war to a new subdir instead of recycling the existing directory. Doing this allows hot deploy to work (more reliably, though not 100% reliable) on Windows systems. If the temp dir is explicitly set in the context file then a hot deploy will always attempt to overwrite in the same dir and on Windows this usually causes problems with file locking and the hot deploy fails.

[wayner]

Thanks - now for my questions.

I have been running several Jetty apps for months - the mobile web server, SJQ, SRE, BMT and Sagealert.

I want to run both the old Nielm webserver, which I have been using since I started using Sage over a year ago, in conjunction with the new Jetty server until I am convinced that the new server meets my purposes.

I downloaded the last file in the list "Zip files for web interface with jetty" and I unzipped it into my Sage folder. What URL should I be using to access the web server? Is it http://sageserver:PORT/sage? If so then I am not having success yet. Some folks have commented that they are using both webservers fine. But there are other posts that mention having to remove some JARs. What should I do?

I have not restarted my Sage service yet, since I didn't think that was required with Jetty.

[razrsharpe]

Originally Posted by wayner

Thanks - now for my questions.

I have been running several Jetty apps for months - the mobile web server, SJQ, SRE, BMT and Sagealert.

I want to run both the old Nielm webserver, which I have been using since I started using Sage over a year ago, in conjunction with the new Jetty server until I am convinced that the new server meets my purposes.

I downloaded the last file in the list "Zip files for web interface with jetty" and I unzipped it into my Sage folder. What URL should I be using to access the web server? Is it http://sageserver:PORT/sage? If so then I am not having success yet. Some folks have commented that they are using both webservers fine. But there are other posts that mention having to remove some JARs. What should I do?

I have not restarted my Sage service yet, since I didn't think that was required with Jetty.

the address should be http://sageserver:JETTYPORT/sage/Home

also i stopped the sage server when unzipping the app and removed the nielm webserver jars before restarting...

[jreichen]

Originally Posted by wayner

What URL should I be using to access the web server? Is it http://sageserver:PORT/sage? If so then I am not having success yet. Some folks have commented that they are using both webservers fine. But there are other posts that mention having to remove some JARs. What should I do?

The URL format for the web interface hasn't changed: http://<sageserver>:<port>/sage/Home, except use the port that Jetty's running on, which (as you probably already know) can be found in JettyStarter.properties.

Enough people are installing it now to the point where I'm starting a wiki page for the installation steps.

Originally Posted by wayner

I have not restarted my Sage service yet, since I didn't think that was required with Jetty.

You shouldn't have to but the hot deploy doesn't work every time. If you get errors then sometimes they are fixed by restarting SageTV.

[wayner]

Thanks guys - I know Jetty is working fine since all of my other Jetty apps work fine. The web page still gives me an error - I will try restarting Sage once the kids go to bed - it kills the WAF or KAF to have to restart Sage during the day since it is almost always being used.

Should I have to delete any of the JARs mentioned in other posts?

[razrsharpe]

Originally Posted by wayner

Should I have to delete any of the JARs mentioned in other posts?

i did but thats because i hate bloat

no idea if you HAVE to.

i deleted the ones from this post:
http://forums.sagetv.com/forums/show...88&postcount=4

[jreichen]

This post was deleted because it contained obsolete information.

[wayner]

OK - I tried restarting Sage without success. I get the following error:
HTTP ERROR: 404
NOT_FOUND
RequestURI=/sage/Home

Powered by Jetty://

Jetty works fine as SRE, SJQ, etc. all work without issues. I have not deleted any JARs as I would like to run the nielm server and the jetty server in parallel at first, if possible.

[jreichen]

Did you download and unzip the zip file for the Jetty version? It contains a context xml and a war file that both need to be installed so it will run in Jetty.

[matt91]

Originally Posted by jreichen

• servlet.jar
• nielm_sagewebserver.jar
• nielm_sageutls.jar
• nielm_sagexmlinfo.jar

Note: nielm_sageutls.jar and nielm_sagexmlinfo.jar are also installed by some other plugins. Save those to a backup location in case you later find that you need them.

Didn't see this mentioned elsewhere - do we know which "other plugins" use these files?

[matt91]

I'm not sure if you guys have any place you'd like feature requests sent, so I'll just toss this one out here.

In some future release, would it be possible to list the year in the date field? I notice it the "past airings" for an old favorite. I know I can click through to see the details screen which reveals the year, but it'd be nice to have it on the listing here as well. There might be other no-year date listings elsewhere, but I just happened to notice this one.

thanks
Matt

(this airing is 3 years old...glad my wiz.bin is still going strong!)

[wayner]

Originally Posted by jreichen

Did you download and unzip the zip file for the Jetty version? It contains a context xml and a war file that both need to be installed so it will run in Jetty.

Yes - I downloaded and installed "NEW: Zip file for web interface with Jetty ".

What about the JAR files mentioned - should I move them?

[rmac321]

wayner,
Are you on the latest version of jetty? That fixed my problems.

[jreichen]

Originally Posted by matt91

Didn't see this mentioned elsewhere - do we know which "other plugins" use these files?

I don't know without doing some research. It's been awhile, but discussions used to pop up once in a while about one plugin overwriting newer versions of those files that were delivered with another plugin. I'll search the forums and put what I find on the wiki when I get it ready.

[jreichen]

Originally Posted by wayner

Yes - I downloaded and installed "NEW: Zip file for web interface with Jetty ".

What about the JAR files mentioned - should I move them?

Since you're still running the web interface in TJWS don't remove all the listed jars, only remove servlet.jar. A newer one with a different name is delivered with Jetty.

[wayner]

I removed servlet.jar (actually renamed it) and then restarted Sage Service but still not working - I still get the 404 errors. Any other ideas?

By the way, what version of Jetty should I be running and how do I check the version?

[jreichen]

Originally Posted by wayner

I removed servlet.jar (actually renamed it)

Did you change the extension? SageTV will pick up all files with the .jar extension. It's probably better to move it to another folder altogether to make sure Sage isn't loading it.

Originally Posted by wayner

Any other ideas?

Turn on the SageTV debug log and post it here. Add this setting to Sage.properties when SageTV is not running.

debug_logging=TRUE

Originally Posted by wayner

By the way, what version of Jetty should I be running and how do I check the version?

Version 1.6 is required. The version number is printed in the SageTV debug log during startup.