Aug 24th- Sep 7th

The team made good progress this sprint, but were unable to complete all the work initially planned for the sprint ie., the transformers for QD and RD. This was due to additional research required for incorporating the asynchronous logging into the code base and supporting the feature on all supported application servers. In addition new members onboarded to the product team, the learning curve could have been the other contributing factor. Overall great progress was made with this feature specifically related to asynchronous logging and the team will continue working on known issues in the upcoming sprints.

Sprint 165 Themes

PD Audit logging completion and incorporation of asynchronous logging
QD and RD audit logging transformation and regression suite updates
Analyze load test adapters
Updating local dev to WildFly

Burndown

Sprint Themes and related tickets for Sprint 165:

Development:

Audit Logging for PD, QD and RD
- Updated requirements document - https://connectopensource.atlassian.net/wiki/x/lQGD
- Audit transformers for PD(synchronus) – 95% complete. (one issue addressed in Sprint 166)
- QD and RD transformers – 80% complete
- Implemented consistent design across all services or PD, QD and RD
- Incorporated asynchronous logging for PD
  - Utilizing JEE6 feature EJB 3.1
  - Further analyzed support on all application servers.
  - Incorporated the feature, and was successful on WebLogic, WildFly and WebSphere
  - Discovered issues on GlassFish and WebLogic - Will continue research in the upcoming sprints
    - GlassFish - Application can be deployed but audit logging not triggered
    - WebLogic requires restart of Application server after deployment of EAR

Testing documentation for PD, QD and RD(Draft)
Regression scripts can be found here
- Pass-through
- Standard
Opened forum questions related to audit logging with the test team here after reviewing the checklists for PD, QD and RD
http://exchange-specifications.wikispaces.com/page/messages/Testing+Team

Partner/Community Support:

eHealth Exchange
- Three (3) new UDDI entries for MedVA have been added to Production with unique OIDS and unique names but with the same endpoints
  - Contacted MedVA and VA and found that they were experiencing no issues with this update. Certificate requested from eHealth Exchange will be utilized during release testing
Product Team continues to monitor and respond to forum questions

JIRA Planning Board of Committed User Stories for Sprint 165:

Related Files for Sprint 165:

Sprint 165 code tag

Common-Types source

CONNECT-Webservices source

Browser not supported