• Usual backups at site
• Gina, who was having connection problems, sent me an email saying she was still having problems after working with a local admin.  I sent her an email requesting more information (IP address, network name, and physical location).  Hopefully an admin here will know what is going on.
• Burned a new copy of the vis suite stuff to a disc
• Meeting this afternoon
• Trying to figure out how to add a service to a webapp that return the date/time it was built and the svn version
• Step 1: Get Maven to record that information
• Date/Time: http://twit88.com/blog/2008/02/20/maven-adding-custom-attributes-and-build-timestamp-to-manifest/
• SVN: http://mojo.codehaus.org/buildnumber-maven-plugin/usage.html
• Note, you must install a command line version of svn
• Step 2: Find a way to read in those values (still working on this)
• http://stackoverflow.com/questions/3777055/reading-manifest-mf-file-from-jar-file-using-java
• http://stackoverflow.com/questions/3907737/how-to-read-manifest-mf-from-pojo-class-not-a-servlet-instantiated-by-spring
• http://stackoverflow.com/questions/615493/how-do-i-read-the-manifest-file-for-a-webapp-running-in-apache-tomcat
• Step 3: Create a service that returns the read in values

• Usual backups at site
• Meeting is set for tomorrow (Thursday the 10th) to talk about the new data ingest.  Dong, Phil and I will all be going.
• Finished updating the new index site on the inside and deployed it to the production server with application links to the test server.  I will update the links when we make the move.
• Back at the mill, resolved all my issues and finished rebuilding each of the projects.  All set to move them inside to the test server once it is no longer the production server.

• Usual backups at site
• Fixed an issue on the upcoming production server with our deployed webapps,  apparently copy/paste across remote desktops sometimes adds random bytes to the end of files.  This caused some run-time errors in visibility.  It may be best to zip everything up before moving it between servers.  At least then we’ll know right away if anything is corrupted as the zip will have errors.  Or move everything across networked drives…
• Jim and Tangie want to set up a meeting to talk about new data ingest.  This is going to be set up for sometime next week.
• Working on rebuilding the entire visibility suite + PM + PA with the new PKI login stuff to bring in and deploy.  Ran in to some errors in UsersAndRoles, I think I have fixed them.  Also there is a weird class called SolrXMLIngestor that makes constant calls to ‘{UPLOADS_DIR}/temp__’ which is hard-coded in to the class so it doesn’t seem very temporary to me…

• Usual backups at site
• imported the new visibility site and fixed a javascript error in IE, also added contact page content
• Talked to Tangie, apparently the two individuals having connection problems to our site contacted their local admins who could connect just fine.  So they are now working with those admins to resolve the problems.  So it’s out of our hands.
• Watched an interesting presentation about Spring Security (http://www.infoq.com/presentations/Spring-Security-3).  It’s rather long but does give a good basic introduction of what can be done:
• Users, roles, and rights
• Method level, annotation- based restrictions based on rights (based on rights is the best way to do it but you could base your rules on anything really)
• Restricting urls to authenticated users
• Restricting parts of the UI based on permissions
• Trying out some of the examples

• Usual backups at site
• Tangie still appears to be out but everything is still up and running as always
• Back at the mill, going to finish up the new site and burn it to a disc to deploy on Monday

• Backups at site
• Tried contacting Tangie with a list of addresses to try and connect to, got an out of office reply
• Moved visibility and ppm+pa over to the production server with a copy of the database tables, everything seems to be working
• Working on the new Visibility site.  I have pages for every tool now with images and some content.  I fixed a javascript issue that was preventing some of the cooler menus and functionality from working (you get what you pay for from free templates).

• Usual backups at site
• Turned in our April status report to Jim and his assistant from TASC
• Working with Tangie to diagnose connectivity issues at some sites.  Phil assistant has been requested by ‘management’
• Training for the new cognos system has fallen through so the customer would like to move forward with that.  There may be a meeting next week
• Dong’s VR came through
• Looked up the standards for classification banners on websites
• Back at the mill typing up our April status for FGM Jim
• Updated my 2012 performance plan
• Working on content for the VIS Tool index pages

• Compiled the status for myself, Dong, and Kristi to turn in to Jim from TASC tomorrow

• Usual back ups at site
• Production server still was not working when I got in.  Sent out and email checking on the status.  Right before I left I checked the site again and it worked!  No word from anyone but I sent an email out thanking everyone who I contacted and letting them know it was now working.
• Now that the production server is up and running I’m working on new index and information pages for the visibility suite.  One page will have a banner declaring it the test site and urging people to the production site.

4.25

• Usual backups in the morning
• I came in to find my help ticket for getting connectivity to our production server closed as ‘resolved.’  The server was still unreachable.  Luckily a very nice lady from the customer advocate office asked to confirm the the issue was in fact resolved.  She helped me get the ticket reopened.
• A guy who saw the email chain from earlier this week and last is trying to help me diagnose the firewall issue.  He asked me to run a continuous ping to the production server so I wrote a batch file that pings and queries port 443 on the production server ever 5 seconds until stopped.  Unfortunately he’s not responding today.
• While waiting I decided to verify that the CASPORT servlet filter I wrote will work on the production server.  I was mostly worried that connectivity to CASPORT would be a problem.  The library and  test servlet deployed without a problem.  This is probably the most valuable library I’ve ever written: “CASPORT enable your webapp in 5 minutes.”
• Continuing the spring-security tutorials

4.26

• Backups
• The firewall guy is back and responding to my emails.  Started the ping for him and he said he would investigate.  No word back after several hours of waiting and email stating I was about to stop the ping.
• Back at the mill learning about spring-security.

• Usual backups at site
• My proxy issue ticket is bouncing around from team to team, hopefully someone who knows what is going wrong eventually reads it
• Back at the mill looking in to the Spring Security frames, lots of tutorials
• http://www.javacodegeeks.com/2010/12/securing-gwt-apps-with-spring-security.html
• http://static.springsource.org/spring-security/site/start-here.html

• Backups at site
• Finished acquiring and building the new PKI Certificate for the production server.  I tested that it works by using it to connect to the authentication server and retrieve some user credentials.  I deployed it to the production web server but it did not fix the connectivity problem.
• Phil gave me his port checker program and I tested connectivity with the production server.  As expected the server responds as listening on port 443 whether or not the webserver is up.  This pretty much confirms there is a proxy issue.
• Back at the mill reading about GWT security and user authentication.  Here are some useful articles:
• Security for GWT Applications
• GWT Login Security FAQ
• Basics of GWT Authentication
• Authentication using servlet filters (general method I used for flex auto-login)
• GWT and Spring Security