• Usual back ups this morning
• Got an email from Gina, a woman at a remote site, who can’t connect to our credentials test
• I’m guessing it is because the URL is incorrect for the network she is on
• Just in case I sent her a URL that does not do PKI verification to see if she can see it
• Brian and I ingested some map / network data in to Visibility for testing purposes
• Back at savage, working on the PKI integration

• Usual backups this morning
• Read some CASPORT documentation at site looking how to integrate more with it
• Back at the mill making a PKI test project and new security library jar
• Demo moved up to 1:30, we’ll first be giving a general demo of Visibility to a new group of people, then one to the planned group followed by some training on everything

My thoughts on PKI/CASPORT integration, step by step:

1. A users connects to a flex application via HTTPS
2. A servlet filter intercepts the requests
3. The filter gets the X509Cert  and retrieves users details from CASPORT, if a cert is not found the session is rejected: the end
4. The filter places the cert and user information on the session for later access
5. Upon creation complete of the flex app, the application asks the user service for the user
6. The user service checks for information on the session:
1. If not there, null is returned and a log in screen is displayed as it is now
2. If it is found, the user service checks the database for a matching users
1. User not found in DB: log in screen is displayed, upon successful log in the userDN is stored in the databases for future use and no log in screen will be displayed again for that user
2. User found in DB: user service returns the UserInfoObject and the log in screen is skipped

We will have to add a new unique column to the user table called ‘userDN’ which uniquely identifies each user.  The value is provided by CASPORT when looking them up via their cert.

This scheme will allow us to continue using our existing user management schemes, not require wiping the user base, and, a logging in 1 time, the system will use PKI certs to log in from that point on.

• Did one final proof read of my quickstart guide before burning it to CD
• Watched an interesting video on software development concepts
• Looking in to fully integrating Visibility with PKI to remove the log in screens
• Technically it is pretty straightforward to grab the user’s cert and get their SID and userDN
• The hard part is the migration from the current user tables (one for PPM and one for Visibility) to using userDNs and linking permissions, etc.
• The easiest thing may be to add a new column to the database, userDN, and when they log in, if userDN is null, set it and use it for look ups in the future.  All users would be created the same way as they are now then log in once and use PKI forever after.
• Loaded Dong’s updates on my CD as well
• I will head to fort this afternoon and deploy the following:
• Quickstart HTML
• Update to PPA HTML
• Update to PPA help button
• Update to VisibilityScripting script engine which will resolve some issues regarding packet too large errors
• I will also do the normal backups
• Will create the final table and view for the demo tomorrow: the historic look at project statuses
• Hopefully will be able to meet with Sherri and show her the view

• Usual backups this morning.  The databases suddenly became a lot smaller, I’m not sure why.  It is 60% the size it was 2 days ago but the project list seemed the right length and neither Tangie or Chrinstina mentioned anything.
• Dong stopped by and we fixed the packet size issue and tested it.
• Testing our trending capabilities with some fake data.
• Finished the PPA quick start guide and exported it to HTML and DOC to bring inside

• Fixed the excel export issue this morning at site
• Briefing with Jim Griffe and other this morning about the Vis Tool, preparing for Colonel Dukes demo
• We need to prepare a slide that illustrates how to “examine the historical performance” of a project
• A short and sweet quickstart guide for PPA would be nice as well
• Working on a quick start guide for PPA

• Regular morning backups
• Imported a new visibility scripting that writes to a file instead of a servlet
• Ran the scripts on the current PPM data and published them to the data navigator
• Worked with Phil and Dong to create several slides for tomorrow’s predemo
• We ran in to an error when trying to load saved views, it was resolved when I closed IE and reopened it.  We believe it has to do with trying to load a table that was created after logging in.
• Resolved the excel export error

• Usual Backups
• Tried to get Colonel Dukes presentation, still no access
• Tried to do some mandatory training from TASC I just received, can’t complete because my name is not in the system
• Worked some more on the CASPORT production migration
• Trying to resolve the issue of the server not being able to make HTTPS requests of iteself
• Dong rewrote a part of VisibilityScripting to write to a file instead of a servlet which got around the issue.  I’ll deploy it tomorrow.

• Scanned in new test versions of the various visibility parts.
• The AccountManagers I moved to PPM and compiled last Friday worked!
• Also, modifying all the compiler settings to match those of PPM worked as well.
• Usual backups this morning.
• Answered several emails concerning stuff like “what is visibility?”
• Resolved the IAVA patch errors
• Attempted to locate the ISR PMO presentation from last week, apparently it is in a folder i don’t have permission to view
• Rebuilt visibility, account managers, and ingest manager with the new compiler settings, will deploy tomorrow
• Went back to site and deployed the rebuilt applications.  Everything works except for one small thing:
• VisibilityScripting publishes an xml file on the server.  IngestManager can then import that file in to the Visibility database.  However with the current server set up, the validate URL fails.  I’m guessing because of certificate errors.

• Usual daily server and DB backups
• Tested the rebuilt versions of ConnectionTest and Visibility, no good
• Lots of emails inside to keep me busy doing non-development
• Back at the office I am trying to match all compiler and library settings between PPM and Visibility as much as possible
• Moved a copy of AccountManagers to the PPM project and compiled it
• Copied some of the Visibility Documentation to a CD so I can answer some of the questions from curious people inside more quickly

• Usual server and DB backups
• Imported a new version of the connection tester application built with different libraries, it works!  Now I need to figure out the differences.
• Got status back on my Flash Builder request, i am still on the wait list
• Compiling Feb status reports for the team
• Had some issues with my internal email client, contacted EA and got it resolved
• Still trying to work out issues applying patches to the site server, got directions to submit an EA ticket and submitted one
• Dong found some sdk differences in the builds so I will test changing them to match PPM
• Flex builder was apparently using libraries from 2 different SDKs for visiblity, account managers, and ingest manager (one dictated by maven and one by flex builder).  So i went through and remove one of them and rebuilt them.  They work on my local machine but that’s not promise the problem is fixed.
• Also made a build of each using purely maven.  Watermarks may appear but if it fixes the connectivity issues we can address the watermark problems.
• Hudson is still running on fgmdev.com but all the assigned builds got wiped out 😦  I added the vis data nav application and it built fine.  I probably won’t add the others but it’s always an option.
• Hudson admin seems to be open to anyone as I didn’t have to log in, so either the builds were lost during the transfer of servers or some kind individual did some housekeeping for us.

• Usual server and database back up in the morning
• Reproduced the server environment on my local machine at site, ended up getting the same errors, so I will at least have a better working environment than on the ‘production’ system
• Attempted installing a working version of Visibility from Jeff’s sever, same issue
• Contacted Jim and Tangie regarding internal testing of our tool, waiting to hear back
• Contacted the software people regarding my request for Flash Builder, would be very handy right now
• Went back to the office to rebuild my connection tester using different libraries
• Also packing up other parts of my Tomcat Install to bring: crossdomain.xml, etc.
• ISP PMO Symposium, 1300-1500

• Did the normal database backup this morning
• Deployed a test client application to test remote object connectivity for Visibility on the client server
• It reads all properties for the properties file just fine
• It does NOT produce any errors while attempting to connect to the remote object, however it does not succeed either
• There no errors indicating anything went wrong in any log files anywhere
• Responded to several emails concerning the server going down yesterday
• Apparently as soon as I submitted a ticket it was restarted which is what fixed the issue
• The tech sent me an email at 9:40 when the server came up, my email server received the email two hours later…
• Back at the office I tried debugging several items to figure out why Visibility is failing on the inside
• Dong built a version of visibility which I will take back to try and debug
• I will also try stopping and restarting the Tomcat server
• Went back to site and tested the fixes, they did not help

• Imported a fresh build of Visibility
• The server was down when I got to the customer site this morning.  I contacted someone who Phil suggested as well as the EDC support center.  The system came back up around 9:40 AM without word from anyone.
• Deployed the new visibility, still not able to log in with the data navigator or the account managers tools.
• Reviewed required server updates from Denise.  Tried to apply several but got errors.  Asked Denise who to contact.
• Tried to listen to the FGM all hands meeting recording, doesn’t appear to be uploaded correctly
• Created a debugging application to try and figure out why visibility isn’t working at site
• Working on a “Home” page for the vis tool which will act as a launchpad for PPM, PPA, and the data visualizations

• Normal database backup and connectivity testing
• Brought in a version of Visibility and Visibility Scripting
• Reviewed some of the required updates from Denise
• Worked with Dong to try and deploy Visibility and Visibility Scripting
• Visibility Scripting is working after fixing some errors in the properties file
• Visibility doesn’t seem to be correctly reading the properties file, not sure what they error is but the swf is from July 2011 so I will try building a new one and bringing that one in
• Rebuilt IngestManager and AccountManagers
• Attempting to Build PPM and PA:
• Project Assistant built fine and I imported Dong’s database of fake data
• PPM is having remote object problems

• Regular back up and connectivity checks this morning
• Deployed a fix for a broken user select button in the Create Funding Request dialog
• Met with Tangie and discussed:
• Connectivity through outside networks
• Getting a link to our stuff from a more official site
• Difficulties creating a funding request, Tangie was able to while I was watching but we’re still trying to get a hold of Christina and diagnose her difficulties
• Contacted Denise Price regarding server maintenance, she said she would email me the details
• Contacted the authentications server helpdesk to try and get our system added to the production list from the test list
• Brought Dong up to speed about yesterday’s meeting
• Working on building a fresh version of Visibility, PPM, and PA on my laptop
• Need to find / install a flex 3.5 SDK
• Need my Eclipse to cooperate and quit locking up
• Got it built!