<< June 2008 | Home | August 2008 >>

FAFDS Work Journal

Complete re-install of WL against Amy's Wiki

  • EOB: WL up-and-running w/ the servicing domain included.
  • Issues surrounding the difficulties in getting the WL to run were: 1) any current JVM running while trying to excecute the fcservicingDomain.py script will inevitably fail. 2) there were some other configuration issues but minor compared to #1.
  • some of the gothas for Amy: 1. need to include the command-line: ssh maven2@flooddata.com
  • I completed all of the Tiki steps to install a WL domain on the Linux box and completed steps 8a or for the WL domain install on the Windows box.

FAFDS Work Journal

QCReport authentication woes

  • Eric: changed the stageident.flooddata.com back to: orion.flooddata.com in the WL admin console.
  • Eric: replaced the ojdbc14.jar w/ another because of mismatching MD5 checksums.
  • Eric: copied from a remote server to my Linux box the fdsauthprovider.jar and replaced the default authprovider.jar
    at location: EXT_PRE_CLASSPATH.
  • The above actions produced No Change in the authentication login of the qcreport.jar app. We were able to confirm the cvasicek
    and pjernigan logins work as expected when used directly against the SWAN console (http://localhost:8001).
  • In response to the email from Amy:
  • Jdk_5.0_12 installed
  • WL 9.2 + the upgrade installed.
  • Steps 3, 4 and 5 to be completed tomorrow morning.
  • FAFDS email from top corp. announced company split delayed. Various reasons.

FAFDS Work Journal

QCReport project

  • RK: showed me the POM snippet: <build><resources>src/main/resources ... tag
  • Attempted to edit the assembly.xml file in an effort to accomplish the previous bullet using the tag: <fileSets><fileSet><directory>src/main/resources ... but does not work. The report.properties file needs to be inside the qcreport.jar archive.
  • qcreport.jar is up-and-running once the first bullet was attained but lack of authentication because of a missing CACERT I cannot login to the qcreport app.
  • I reported the previous bullet to EL and got an email from RK to use the CACERT TESTING.der in my $JAVA_HOME/jre/security/lib directory using the keytool import arg. The keytool import failed because I used the file name extension: (dot).derx instead of (dot).der. The keytool complains that the CACERT alias <mykey> is already in use (or somthing to this effect).

FAFDS Work Journal

QCReport project &amp; dev. meeting

  • Worked w/ and asked RK a lot of questions today w/ the payoff: qcreport.jar running as an executable. RK inserted a Maven assembly that uses an external assembly.xml file. This external assembly is something like an Ant <fileset>. With the Maven fileset and the special dependecies element I was able to include a /lib such that it would run at the command-line.
  • RK: after the dev meeting I started on repackaging the /util directory into the qcreport-app directory such that we remove the secondary <module>.
  • Dev meeting: mostly discussions about SWAN related issues and RKs FIC stuff. I put in my 2 cents worth about Xythos and QCReport projects.

FAFDS Work Journal

QCReport project

  • Installed SWAN in lieu of Servicing to have the t3://localhost:8001 url as input to qcreport.jar.
  • qcreport.jar running w/ the above but now there are issues w/ LDAP authorization.
  • Received a report.zip from AF that is about 40KB larger with a better directory structure (includes the reports.properties).
  • Started to clean the above report.zip as stated above in preparation to be mavenized.
  • DBVisualizer installed but not configured for anything useful yet (like an Oracle connection).

FAFDS Work Journal

Xythos &amp; QCReport projects

  • Added custom retry handler to XythosProxy.java
  • Cleaned up parameter error handling. Commented all overloaded methods: uploadFile(). Tested the remaining 6 overloaded methods: uploadFile().
  • XythosProxyServlet replaced w/ FileUploadServlet. The conditional: isDebugEnabled() inserted where try/catch found and where conditionals on variables required.
  • QcReportClientFrame built and running. CK needs to be brought back to login to qcreport.jar for a test.
  • RK wants qcreport moved to TRUNK.

FAFDS Work Journal

Xythos and QcReportClient projects

  • All xythosproxy project files committed under: 23692 and 23700.
  • FileUploadServlet migrated to XythosProxyServlet (23700)
  • Executable of QcReportClient invoked as a command-line shell script
  • Invoking QcReportClient reveals many unknown inputs including: report.properties file and class: AbstractApplication
    (jar).
  • Email sent to C. Kozlowski requesting a copy of his report.properties file.

FAFDS Work Journal

Xythos/QCreport projects

  • Reported to RK about the 5 or 6 bullets emailed to him yesterday concerning CK and his QCReport app. It appears I need to build the app to executable jar and try for a repeatable condition.
  • The issues with the old fds upload-war POM and svn were resolved. The XythosProxy POM parent now compiles and builds correctly.
  • The Broken Pipe issue though is not resolve. I think what I need to do is have a second Servlet using the URLconnection and the ObjectStream for the XythosProxyResponse metadata.
  • Another possible problem is the setting of the request content-type.

FAFDS Work Journal

Projects: xythos, qcreport (Bugzilla 14847)

  • RK talked to me today about the emails to me about: Bugzilla 14847 and the Super Audit issues.
  • As a result I went and talked to Chris Kozlowski and did some over-the-shoulder analysis.
  • The result as emailed to RK was as follows:
  • The QCreport app does not fail in terms of Exceptions or crashes.
  • The user is expecting a non-zero length (dot).csv file for all quarters but the application outputs a zero-length (dot).csv file at the execution of the app against any time range input from the second quarter 08.
  • The initial hunch is there is a back-end DB problem.
  • Ultimately, I need to get the qcreport.jar running as an executable such that I can debug the app.
  • CK claims they will not start processing the (dot).csv audit data until around 15th Aug.
  • CK also says he can request ad hoc queries from the DB folks but he prefers to use the app.

oDesk buyer gig

Transaction WS (axis 1.4)

  • I have been talking w/ a buyer from oDesk this week.
  • The buyer attached a .zip file in an email to me and I began looking over the WSDL generated code last night.
  • I suspect I will need to download or re-install the axis 1.4 on my Windows box
  • I will need to get the code into some shape to be able to land the gig.
  • Additionally, I will have to take the oDesk readiness test today and hopefully pass.

FAFDS Work Journal

XythosProxy and broken pipe

  • Installed log4j.xml for the XythosProxy module in its own resources folder under the POM src/main.
  • Spent most  of the day log trace debugging XythosProxy and the XythosProxyResponse. The HTTP request is being interrupted with only the only error condition being return: broken pipe and some related Socket error messages.

FAFDS Work Journal

QCReport mavnized &amp; Xythos projects

  • A parent POM created for: qcreport with modules of: qcreport-app and util (shared/util was flattened).
  • Jars for the qcreport-app and the util (report) were built.
  • All of the above was commited to SVN @ fc/apps/qcreport.
  • XythosProxy is uploading the file OK but  the XythosProxyResponse will have to be debugged for the return metadata issues.

FAFDS Work Journal

Xythos/qcreport projects

  • Xythos-parent-2.4.jar and upload-war.2.07.war generated from
    POM
  • Upload-war.2.07.war installed in WL as xythos-upload-war-2.07
  • Xythos test client uploads a file but did not complete testing
    on returned metadata (XythosProxyResponse)
  • Ran memory test on the Linux box from a CD borrowed from Brian
    reason: restarted WL several times in succession before the entire
    desktop disappeared.
  • After 1.5 hours memory testing I restarted work on the
    qcreport POMs:
    1. Qcreport folder was mavenized in apps/qcreport w/ many dependencies
      unresolved.
    2. Qcreprot is dependent upon the folder: util which is not yet
      mavenized.
    3. The share/util folder is not yet mavenized.
    4. When all folders are mavenized I will check everything into SVN.

FAFDS Work Journal

xythos-2.4.jar (project)

  • The parent POM builds the xythosproxy-2.4.jar w/ the correct
    contents in the /jar directory.
  • Not able to build the .war as FileUploadServlet.java needs the
    newly built .jar file to return the XythosProxyResponse object.

Drug re-hab expert on CNN

Drug re-hab for the Hollywood well-to-do

  • This week-end I saw another one of these reports where, in this case, CNN digs up an expert to espouse his expert views. The target view?: drug re-hab. The re-hab targets?: Hollywoods well-to-do such as: Howard Downey Jr.
  • As much as I liked Hollywoods perennnial Bad-boy in Ironman I was fairly disgusted at CNN and their presentation of drug re-hab for the folks that can afford such privileges.
  • I suppose CNN's real target, of course, is viewership and their intent of delivering some type of educational message in their drug re-hab report was nothing more than a facade.
  • There was a long list of Hollywood notables (celebs I suppose) that were part of the report given by the drug re-hab expert. All of these folks are still alive. Where is my kid?: in the ground.

FAFDS Work Journal

Xythos project

  • UploadFileWar (war) source commited to svn repos.
    http://code.flooddata.com/repos/fc/apps/servicing/trunk/apps/fds-app:upload-war:2.07
  • Xythos fileupload client source commited to svn.
    The rest of the day taken up in studying maven techniques to
    make the upload-war-2.07.jar public such that it may be imported and
    used in NB client project Libraries.
  • RK stopped by before COB and discussed the project and the following bullet.
  • Ccentry was checkout and put into a NB project to study the
    pom.xml  as a solution to the previous bullet.

FAFDS Work Journal

Xythos project

  • XythosProxyResponse refactored with one additional constructor
    added to accommodate the server side
  • The server side now returns a XythosProxyResponse object and the
    XythosProxy extracts the info.
  • The client can now extract one to several Xythos metadata
    items depending on requirements.
  • Minimally, the Xythos File ID will be returned.
  • The single XythosProxy object can withstand changes and
    additions w/o breaking the server side or the client.

FAFDS Work Journal

Xythos project

  • I reworked the XythosProxyAbstract.java to just XythosProxy according to RKs reply email on the matter.
  • I used most of the day on the first bullet creating all of the overloaded methods as required: uploadFile() w/ a complement of 6 more methods w/ args.
  • I also created the entire complement of getter/setter methods such that if only the uploadFile() method is desired then all or most of the setters must be used to upload a file.
  • The Xythos dev meeting brought back the returned Xythos ID as I had originally implemented. As it stands it may have changed anyway since RK has given me a Java file: changeResponse.java that I should use to return the Xythos ID and any other response data including error conditions.
  • After the Xythos dev meeting RK ask questions about individual points surrounding: XythosProxy.java - the class name and all of the method calls including the getters and setters. As a result of this discussion I included the mimeTypes[] array and the fileExt[] array as gleaned from mimetype.org. And, I pasted in the lookupMimeType() method.

FAFDS Work Journal

Xythos project (RK returns; requirements change)

  •  Created an abstract class XythosProxyAbstract.java that implements an
    interface XythosProxyInf.java to return a mimeType.
  • XythosProxyAbstract contains all the public static setters()
    and private getters() for all the Xythos related field variables that
    are needed to process Xythos WFS files.
  • Created 2 uploadFile()s w/ the complement of uploadFile()s coming
    tomorrow.
  • Created a fileUpload(...,...,...,...,) partially implemented and
    should be finished by tomorrow.
  • Created a private getMimeTypes() that satisfies XythosProxyInf and
    that automatically sets the file content type inside uploadFile() and
    fileUpload() based on the filename retrieved from the input File object.
  • The abstract class should allow usage now avoiding breakages
    in the future if changes or additions are needed to be made.
  • I will test this tomorrow or Friday with a concrete class.
  • TODO: implement the log4j methods.

FAFDS Work Journal

Xythos project

  • Completed most of the changes for the Xythos project as follows:
  • The client: added the description field for the method: uploadFileToXythos().
  • I put the mimeType String arrays in an interface: XSFileUploadInf.java to remove the clutter.
  • Edited the complement to the top bullet for the description field variable as a request parameter such that it could become the description argument to the uploadFileToXythos() method.
  • Commented both the client and the Servlet. And, I removed the getXythosVirtualServer() method and replace it w/ the: VirtualServer.find(String VS) method.
  • Created an executable jar-w-dependencies (Windows clickable) for the client.
  • Completed the online performance review.

FAFDS Work Journal

Xythos project

  • I finished up with the FileUploadServlet.java and the client: XSFileUploadApp.java.
  • Todo: add the client and servlet code for user input of the File description (any text is OK).
  • I added the JComboBoxes and JLabels for the Virtual Server, the User Names and the TLD/Sub entries.
  • I also added an automated but user configurable JComboBox to attach the MimeType to the uploaded file.
  • Fixed numerous small development bugs as I went along.

FAFDS Work Journal

Xythos project

  • I finished up with the FileUploadServlet.java and the client: XSFileUploadApp.java.
  • Todo: add the client and servlet code for user input of the File description (any text is OK).
  • I added the JComboBoxes and JLabels for the Virtual Server, the User Names and the TLD/Sub entries.
  • I also added an automated but user configurable JComboBox to attache the MimeType to the uploaded file.
  • Fixed numerous small development bugs as I went along.

July The Fifth

Lament and reflections at home

  • Karl and I talked about Dean yesterday starting with his autopsy report.
  • I suppose both of us still don't understand how Dean got to the condition he was in. I explained the autopsy report to Karl and like his Mother I think they were a little bit better about Dean's death.
  • Karl did lament that Dean had entrusted to him when Dean was 16 about how Dean could not wait to leave home. It appears that even Karl did not understand Dean's position or his views.
  • I know that Dean had not been happy at home especially from the Day I went to Iraq. Looking back now it appears Dean probably viewed my departure for Iraq as abandoning the family. I didn't really try to explain the financial reasons why I went to Iraq.
  • Karl was just very emotionally upset when I went to Iraq and did not understand why I had to go to Iraq.
  • The final analysis is I thought it would help the family financially and that it would put Dean into college which the money I earned did put Dean into college. The reality is all I did was to put Dean into the street drug world of Austin, Texas.
  • Austin, Texas was the beginning of Dean's demise into hard and illicit drugs.
  • Aug. 14, 2004 will be a day I will regret forever.

The Dean Saga

The Autopsy report

  • I got home last night from Austin early since Cliff took off early and so did the rest of the group.
  • Helen directed my attention to the Autopsy Report for Dean: case  C08-0537.
  • I need to buy another printer/scanner so I can scan the autopsy and put it in w/ Dean's website.
  • I plan to begin work on Dean's website this weekend. It is time.

FAFDS Work Journal

Xythos integration project

  • Today EL came by and installed a new CACERT and viola! Xythos server began working again. And, in the most important way: LDAP would resolve WFSSecurity issues.
  • As a result of EL's visit I was able to employ the code snippet from PD and I finally was able to upload a file to the Xythos system on the xythoshome.flooddata.com.
  • The downside is the only Virtual Server I have had success with is: xythoshome.flooddata.com.
  • At a minimum I have generated a chink-in-the-armor and I should be able to move on to improving the XSFileUploadApp interface to remove the hardwired arguments.
  • Today: the systems crowd went out to Rudy's the all-time dept. reliable eatery and watering-hole. I only had 6 bucks but I ate like a king: two sandwiches made from 2 Jalapeno sausage links, WoW! To top off the day I got to go home early for the 4th!

FAFDS work journal

Xythos et. al

  • I received an email from Dan Harlan about reporting in high-level language about the so-called Xythos integration. I don't have a Xythos server to test my application so the outlook is not good.
  • Spent most of the day vascilating between solving the issues I am experiencing w/ creating an executable jar file for XSFileUploadApp and fielding the volly of email between me and Gary Serrino (Xythos) in an effort to solve the Xythos/LDAP mystery.
  • One curiosity is I was able to connect w/ my Windows Xythos instance but the app response was: NOT FOUND. At least I have something to go on in the morning.

FAFDS Work Journal

Xythos project

  • Today I was able to get FileUploadServlet mostly working correctly but now it generates a LDAP server connection exception exactly the same exception generated by getUserContext() in FileUploadServlet.
  • I mostly believe there are folks at FA that can help w/ the Xythos/LDAP issues but are dragging their feet. I wonder why?
  • I tried to add the manifest assembly to the pom.xml to get an exectuable jar but it did not work.
  • If I can move the XSFileUploadApp client to the Windows box I will continue to work there.
Technorati Profile