Wanted: Developer for Web Interface Mobile

[jreichen]

It was compiled for Java 6. I recompiled them for 1.5. Get jettystarter_1_0_01.zip from the downloads page and SageWebApp.zip again from the link above.

[rickw]

Just to let you know...the new web app is working great from Windows Mobile 6 using PIE. My main activity is managing the recording schedule.

I've been using it both from my phone (PPC-6700) and the Windows Mobile Emulator on my PC.

I think you've done a good job of formatting the displays for a mobile browser. My only suggestion right now is related to the guide listing. There needs to be some method for jumping to a specific date and time slot. For example it's morning right now, but I'd like to see the primetime listing. It takes a while to "Next>" through the entire day.

Anyway great work!

Rick...

[LehighBri]

Hi there - I am a heavy user of nielm's web browser plugin and would love to get it to work on my Blackberrry. I tried following the directions and am having issues.

1. When do you think there will be an easier way to install/set this up?
2. I updated the port in jetty.xml and the jettystarter.properties file to 8889 and also added the appropriate string to the sage.properties file. When I restart the Sage server, I don't see anything listening on that port when I use netstat -a. Any ideas on how to debug this? In looking through the sagetv_0.txt log, things seem to be OK.

Note that I'm running Vista with UAC turned off. My nielm web server works great on port 8888.

[jreichen]

Originally Posted by LehighBri

1. When do you think there will be an easier way to install/set this up?

This is pretty early in development. I haven't thought much about simplifying installation. Eventually I'd like to deliver the desktop and mobile web servers together.

Originally Posted by LehighBri

2. I updated the port in jetty.xml and the jettystarter.properties file to 8889 and also added the appropriate string to the sage.properties file. When I restart the Sage server, I don't see anything listening on that port when I use netstat -a. Any ideas on how to debug this? In looking through the sagetv_0.txt log, things seem to be OK.

Take a look at posts 14 and 15 in this thread. I'm guessing there are spaces in the path to your SageTV install location. I'm working on a fix, so for now try the workaround.

[bcjenkins]

Is this supposed to work from a regular browser too? When clicking on anything I get weird chars filling the screen.

B

[jreichen]

Originally Posted by bcjenkins

Is this supposed to work from a regular browser too? When clicking on anything I get weird chars filling the screen.

B

Yes, it works from a regular browser. I just noticed those weird chars for the first time last night. I don't know what's causing it. It happened when I clicked on a recording group for The Office, but not for any other shows.

[LehighBri]

OK... I started over to make sure I did this right... here are the steps I performed (would be good to consolidate these somewhere so we don't have to dig throughout this thread)... looks like the logfile may give us some help?

1. Unzipped jettystarter_1_0_01.zip and SageWebApp.zip to C:\Program Files\SageTV\SageTV folder
2. Updated JettyStarter.properties to include the updated options:

jetty.configfiles=C\:\\PROGRA~1\\SageTV\\SageTV\\jetty\\etc\\jetty.xml
jetty.logs=C\:\\PROGRA~1\\SageTV\\SageTV\\jetty\\logs

3. Updated sage.properties file with the following property:

load_at_startup_runnable_classes=net.sf.sageplugins.webserver.StartServer;net.sf.sageplugins.jetty.starter.Main

4. Updated jetty.xml file to indicate I want to use port 8889 (do I need to update any other port options?... I see multiple references in that xml file):

      <Arg>
          <New class="org.mortbay.jetty.nio.SelectChannelConnector">
            <Set name="host"><SystemProperty name="jetty.host" /></Set>
            <Set name="port"><SystemProperty name="jetty.port" default="8889"/></Set>

From logfile

Wed 6/4 19:52:34.937 Loading startup runnable:net.sf.sageplugins.jetty.starter.Main
Wed 6/4 19:52:34.939 Loaded startup runnable:net.sf.sageplugins.jetty.starter.Main
Wed 6/4 19:52:34.939 JettyStarter: Starting Jetty
Wed 6/4 19:52:34.941 Starting webserver with args: [-p, 8888, -root, webserver, -t, throttles.properties, -s, servlets.properties, -r, realms.properties, -a, aliases.properties, -nohup]
Wed 6/4 19:52:34.944 jetty.home property: C:\Program Files\SageTV\SageTV\jetty
Wed 6/4 19:52:34.944 jetty.logs property: C:\PROGRA~1\SageTV\SageTV\jetty\logs
Wed 6/4 19:52:34.945 JettyStarter properties
Wed 6/4 19:52:34.945 -- listing properties --
Wed 6/4 19:52:34.945 jetty.logs=C:\PROGRA~1\SageTV\SageTV\jetty\logs
Wed 6/4 19:52:34.945 jetty.configfiles=C:\PROGRA~1\SageTV\SageTV\jetty\etc\j...
Wed 6/4 19:52:34.945 jetty.home=C:\Program Files\SageTV\SageTV\jetty
Wed 6/4 19:52:34.946 Starting Jetty from the following configuration files: 'C' '\PROGRA~1\SageTV\SageTV\jetty\etc\jetty.xml'
Wed 6/4 19:52:34.982 Acme httpd BRI-HTPC:8888 listening.

Is there an issue with the line that says "Starting Jetty from the following configuration files: 'C' '\PROGRA~1\SageTV\SageTV\jetty\etc\jetty.xml'"?... looks fishy to me...

[TechBill]

I would love to see a Closed Caption of some type added to it. Or Closed Caption converted into subtitle the streamed etc. Mplayer can take CC and hard subtitle it into the video itself before streaming it so that would be a very nice feature to have.


Bill

[jreichen]

Originally Posted by LehighBri

OK... I started over to make sure I did this right... here are the steps I performed (would be good to consolidate these somewhere so we don't have to dig throughout this thread)... looks like the logfile may give us some help?

Yes it did! I had a bug in 1.0.01 where it was parsing the config files line using colons, that's why you saw the "fishy" message I'm still learning about uploading files to SourceForge, so the 1.0 and 1.0.01 downloads are now the same. It wouldn't have done any good to try that one.

Originally Posted by LehighBri

2. Updated JettyStarter.properties to include the updated options:

jetty.configfiles=C\:\\PROGRA~1\\SageTV\\SageTV\\jetty\\etc\\jetty.xml
jetty.logs=C\:\\PROGRA~1\\SageTV\\SageTV\\jetty\\logs

As of 1.0.02, you don't need to modify the paths in JettyStarter.properties. It now has quotes around each path to allow paths with spaces.

Originally Posted by LehighBri

4. Updated jetty.xml file to indicate I want to use port 8889 (do I need to update any other port options?... I see multiple references in that xml file):

      <Arg>
          <New class="org.mortbay.jetty.nio.SelectChannelConnector">
            <Set name="host"><SystemProperty name="jetty.host" /></Set>
            <Set name="port"><SystemProperty name="jetty.port" default="8889"/></Set>

That's the only port that needs to be modified. There's also a "confidential port" setting in there that can be used for the SSL port. I don't have instructions yet for setting up SSL.

Version 1.0.02 has been posted to the download page. Right now the instructions for upgrading the Jetty plugin are the same as they are for installing. Just make sure to save off any files you have modified. (JettyStarter.properties can be overwritten, but for those of you who have modified the port, make sure to back up jetty/etc/jetty.xml and make the change to the file again after unzipping the file)

EDIT: I also modified jetty/etc/realm.properties so the default user/password is sage/frey.

[jreichen]

Originally Posted by rickw

Just to let you know...the new web app is working great from Windows Mobile 6 using PIE. My main activity is managing the recording schedule.

Great to hear it!

Originally Posted by rickw

I've been using it both from my phone (PPC-6700) and the Windows Mobile Emulator on my PC.

My phone is a Samsung A737. It has a pretty small screen compared to the PDA's and uses the NetFront 3.4 browser. It works pretty well, but I think I'm working with the lowest common denominator. I'm interested in hearing what devices other people are using.

Originally Posted by rickw

I think you've done a good job of formatting the displays for a mobile browser. My only suggestion right now is related to the guide listing. There needs to be some method for jumping to a specific date and time slot. For example it's morning right now, but I'd like to see the primetime listing. It takes a while to "Next>" through the entire day.

I agree. I'll put it on the TODO list. I think the layout turned out well, considering mobile screens are narrow. But the more I use it I wish I could jump directly to a date/time. One trick I use is to click the "plus" and "minus" links to expand the time span, then use "Next". So if the time span is two hours, each time you click "Next" it jumps forward two hours instead of the default of one.

[jreichen]

I found a problem in the Jetty plugin 1.0.02 I just released. The jetty.configfiles setting works fine, but the jetty.logs setting does not. Use Rick's workaround in post #15 for jetty.logs for now. I'll fix it in the next day or two, then get back to working on the web pages.

[LehighBri]

Originally Posted by jreichen

Yes it did! I had a bug in 1.0.01 where it was parsing the config files line using colons, that's why you saw the "fishy" message I'm still learning about uploading files to SourceForge, so the 1.0 and 1.0.01 downloads are now the same. It wouldn't have done any good to try that one.

As of 1.0.02, you don't need to modify the paths in JettyStarter.properties. It now has quotes around each path to allow paths with spaces.
That's the only port that needs to be modified. There's also a "confidential port" setting in there that can be used for the SSL port. I don't have instructions yet for setting up SSL.

Getting warmer.... I used 1.0.02 and jetty is now listening on the port I need. I get a 404 error though when I navigate to: http://localhost:8889/sage/m/menu.jsp

HTTP ERROR: 404
NOT_FOUND
RequestURI=/sage/m/menu.jsp

Powered by jetty://

Any idea on how to fix this? Very close here! Do I need to do anything with the SageWebApp.zip file other than simply unzipping it to the same location as the jetty.zip file? Seems to me like jetty doesn't know where the war file was deployed to...

[jreichen]

Originally Posted by LehighBri

Any idea on how to fix this? Very close here! Do I need to do anything with the SageWebApp.zip file other than simply unzipping it to the same location as the jetty.zip file? Seems to me like jetty doesn't know where the war file was deployed to...

Jetty polls the jetty/contexts directory every 1 second by default (to change it see the ContextDeployer scanInterval in jetty/etc/jetty.xml) for new or modified files. If it finds something, it (re)deploys the war file specified in the context xml file. No need to restart Sage when updating SageWebApp.zip!

It might be that the context xml was extracted from the zip before the war, Jetty detected the context xml and didn't find a war file, and didn't deploy it. Try resaving the context file to update its time stamp and see if that fixes it.

[LehighBri]

I tried initially to update the context xml file and saved it to update the timestamp. No luck. I then deleted the contexts and webapps folder, and then re-extracted the SageWebApp.zip file and noticed the war file was deployed as I see files under the SageWebApp\webapp folder.

Note though that nothing exists under the SageWebApp\jsp folder...

[jreichen]

Originally Posted by LehighBri

Note though that nothing exists under the SageWebApp\jsp folder...

That's fine. When the browser requests a jsp, the server will compile it into a servlet and place the Java class file under the jsp folder. So if you haven't requested a page yet, that folder will be empty.

[LehighBri]

Originally Posted by jreichen

That's fine. When the browser requests a jsp, the server will compile it into a servlet and place the Java class file under the jsp folder. So if you haven't requested a page yet, that folder will be empty.

Nonetheless, when I go to http://localhost:8889/sage/m/menu.jsp, I still get the 404 issue I mentioned. Any reason why that continues to appear even through the war file looks to be deployed?

[bcjenkins]

Fri 6/6 6:24:55.756 2008-06-06 06:24:55.973::WARN: failed org.mortbay.jetty.NCSARequestLog@14462b
java.io.IOException: Cannot write log directory /opt/sagetv/server/jetty/"/opt/sagetv/server/jetty/logs"

Changed jetty.logs=logs

Works. Seems like the quotes around the path are throwing it off.

B

[jreichen]

Originally Posted by LehighBri

Nonetheless, when I go to http://localhost:8889/sage/m/menu.jsp, I still get the 404 issue I mentioned. Any reason why that continues to appear even through the war file looks to be deployed?

I've seen that if I try accessing the page while Jetty is extracting the war. Usually waiting a few seconds and then refreshing fixes it. That doesn't seem to be the case here, though.

Is there anything in sagetv_0.txt log?

[Brent]

UPDATE 06/22/2008: There is now a wiki with the latest instructions and download links. Check out the Mobile Web Interface Wiki


Below is the instructions for installing the mobile web interface as of 06/08/2008:

1. Make Sure you have Nielm's Web User Interface already installed and working properly. Note: Requires version 2.22 (or higher) of nielm's webserver
2. Download the Jetty Program From the Download Page
3. Shut Down SageTV and SageTV Services (if you run as service)
4. Unzip the jettystarter_1_2.zip file (this is the current version as of 06/13/08) into the SageTV/SageTV directory
5. This step is no longer required as of jettystarter_1_1.zip
6. Open up Sage.properties file and the following line (note: If the key has multiple values, they need to be separated by a semicolon)

   net.sf.sageplugins.jetty.starter.Main

   should be added to this line:
   

   load_at_startup_runnable_classes

7. Decide what port you want to use for the mobile web app (default is 8080). Use a different, unused port (not the same port as neilms webadmin)
   If you want to change the port, change it in JettyStarter.properties.
   Assuming you wanted to change the port to 8500, you would Change
   

   #jetty.port=8080

   To
   

   jetty.port=8500

   Notice that you have to remove the # from that line or it won't work
   
   NOTE: You will have to port forward this port to access outside your network
8. Download the mobile web server SageWebApp.zip. NOTE: Updated to new version 6/13/2008
9. Unzip the SageWebApp.zip into the SageTV/SageTV directory.
10. The default username and password is sage/frey. This can be changed in SAGE_HOME/jetty/etc/realm.properties.
11. Run SageTV
12. Point your browser to http://server/sage/m/menu.jsp. Note: the server you specify should include the port that you specified above in step 7

EDIT:

• Added run SageTV step
• Added Edit JettyStarter Properties step
• Added reminder to have Neilm's Web User Interface Installed before starting on this project
• Updated/corrected step 7 and step 12
• 06/08/2008 Updated instructions for jettystarter_1_1.zip (eliminated need for step #5)
• 06/13/2008 Updated the SageWebApp.zip file to new version
• 06/13/2008 Updated #4 and #7 per jreichen's request in post #81
• 06/14/2008 Updated Step 7 for clarification
• 06/17/2008 Added the requirement of Version 2.22 or higher of nielm's webserver

[jreichen]

Looks good, Brent. Just a few things:

• jettystarter_1_0_02.zip is the current version.
• If you want to change the user/password that needs to be done before starting Sage.
• Add a step to start Sage
• For #15, remove the quotes from the jetty.logs property in JettyStarter.properties. This is will be fixed in the next release.