Sprint 167 Progress Summary

Owned by Deepthi Rodrigues (Unlicensed)
Last updated: Oct 06, 2015
2 min read

Sep 21st - Oct 5th

Sprint status is excellent. The team made great progress with audit logging by fixing the issues uncovered on WebLogic and GlassFish application servers.

The issue related to GlassFish application server was pulled into the sprint as it tied into the WebLogic issue and was addressed. Progress was made with the RD and DS services for asynchronous logging, those tickets will be completed next sprint.

Sprint 167 Themes:

 

  • Research WebLogic and GlassFish issues for audit logging.
  • Continue work on DS and RD auditing
  • Community/forums support

Burndown:

Sprint Themes and related tickets for Sprint 167:

Development:

  • Audit Logging (this sprint)
    • Fixed the issue where audit events were not being logged on the GlassFish application server. 
      • GlassFish requires packaging of EJB module within CONNECT ear /lib, as opposed to within ear root for other application servers.
      •  This addressed the issue for asynchronous audit logging in GlassFish.
    • Fixed asynchronous auditing issue on the WebLogic application server.
      • Jar conflicts were resolved and this issue is addressed. No longer requires a server restart.
      • Testing on WebLogic 12.1.1 and 12.1.3
    • Fixed values for PD, QD and RD elements in the audit blob message.
    • Updated Testing documentation for PD, QD and RD(Draft) - 

Partner/Community Support:

  • Following up on CONN-1624 - support question from DoD related to configuration setup for 4.4.

JIRA Planning Board of Committed User Stories for Sprint 167:

Related Files for Sprint 167:


Sprint 167 code tag

Common-Types source

CONNECT-Webservices source