Versions Compared

Old Version 3

changes.mady.by.user Tran Tang (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Patrick Lobre (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • SoapUI scripts will be used to send requests to CONNECT Gateway.
  • LoadUI projects will be used to perform the actual load test. This includes,  It will be used to capture and report response time. 
  • JConsole will be used to capture and report the CONNECT gateway JVM metrics, CPU utilization and Memory usage. nd to simulate concurrent messaging.
  • Custom adapters will be used to quickly respond to service requests to eliminate the processing time that a full adapter would require. The adapters are available at : Plugins/PerformanceTestTools
  • Test Scripts are available at : //shared-folder/Software/Performance 4.6/ConnectPerformanceTest. Follow Configuration instructions for test setup and execution.

...

#
Test Case
Description
LoadUI Adapter
1Patient Discovery
  1. Test will be performed with an overloaded initiator and an overloaded responder. The goal is to determine how many concurrent Patient Discovery messages CONNECT can handle in one minute and prove that Patient Discovery can handle 1600 concurrent messages per minute.
  2. Execute below scenarios four times bidirectionally (Ex: JBoss as initiator and JBoss as responder) on individual CONNECT supported application server and capture metrics and provide a summary including average throughput rate.
    1. Audit logging on using audit proxy secure Implementation.
    2. Audit logging on using audit proxy javaImplementation.
    3. Audit logging off with any audit proxy implementation.

CONNECTLoadTestAdapter - gov.hhs.fha.nhinc.patientdiscovery.loadtest.PatientDiscoveryBO

2Document Query
  1. Test will be performed with an overloaded initiator and an overloaded responder. The goal is to determine how many concurrent Document query messages CONNECT can handle in one minute and prove that Document Query can handle 1600 concurrent messages per minute.
  2. Execute below scenarios four times bidirectionally (Ex: JBoss as initiator and JBoss as responder) on individual CONNECT supported application server and capture metrics and provide a summary including average throughput rate.
    1. Audit logging on using audit proxy secure Implementation.
    2. Audit logging on using audit proxy javaImplementation.
    3. Audit logging off with any audit proxy implementation.

CONNECTLoadTestAdapter - gov.hhs.fha.nhinc.documentquery.loadtest.DocumentQueryBO

3Document Retrieve
  1. Test will be performed with an overloaded initiator and an overloaded responder. The goal is to determine how many concurrent Document Retrieve messages CONNECT can handle in one minute and prove that Document Retrieve can handle 1600 concurrent messages per minute.
  2. Execute below scenarios four times bidirectionally (Ex: JBoss as initiator and JBoss as responder) on individual CONNECT supported application server and capture metrics and provide a summary including average throughput rate.
    1. Audit logging on using audit proxy secure Implementation.
    2. Audit logging on using audit proxy javaImplementation.
    3. Audit logging off with any audit proxy implementation.

CONNECTLoadTestAdapter - gov.hhs.fha.nhinc.documentret

4Document Submission
  1. Test will be performed with an overloaded initiator and an overloaded responder. The goal is to determine how many concurrent Document Submission messages CONNECT can handle in one minute and prove that Document Submission can handle 1600 concurrent messages per minute.
  2. Execute below scenarios four times bidirectionally (Ex: JBoss as initiator and JBoss as responder) on individual CONNECT supported application server and capture metrics and provide a summary including average throughput rate.
    1. Audit logging on using audit proxy secure Implementation.
    2. Audit logging on using audit proxy javaImplementation.
    3. Audit logging off with any audit proxy implementation.

CONNECTLoadTestAdapter - gov.hhs.fha.nhinc.docsubmission.loadtest.DocumentSubmissionBO

5X12 RealTime
  1. Test will be performed with an overloaded initiator and an overloaded responder. The goal is to determine how many concurrent X12 RealTime messages CONNECT can handle in one minute and prove that X12 RealTime can handle 1600 concurrent messages per minute.
  2. Execute below scenarios four times bidirectionally (Ex: JBoss as initiator and JBoss as responder) on individual CONNECT supported application server and capture metrics and provide a summary including average throughput rate.
    1. Audit logging on using audit proxy secure Implementation.
    2. Audit logging on using audit proxy javaImplementation.
    3. Audit logging off with any audit proxy implementation.

CONNECTLoadTestAdapter - gov.hhs.fha.nhinc.x12.loadtest.CORE_X12DSRealTimeBO


6X12 BatchRequest
  1. Test will be performed with an overloaded initiator and an overloaded responder. The goal is to determine how many concurrent X12 BatchRequest messages CONNECT can handle in one minute and prove that X12 BatchRequest can handle 1600 concurrent messages per minute.
  2. Execute below scenarios four times bidirectionally (Ex: JBoss as initiator and JBoss as responder) on individual CONNECT supported application server and capture metrics and provide a summary including average throughput rate.
    1. Audit logging on using audit proxy secure Implementation.
    2. Audit logging on using audit proxy javaImplementation.
    3. Audit logging off with any audit proxy implementation

CONNECTLoadTestAdapter - gov.hhs.fha.nhinc.x12.batch.request.loadtest.CORE_X12DSBatchRequestBO

7X12 BatchResponse
  1. Test will be performed with an overloaded initiator and an overloaded responder. The goal is to determine how many concurrent X12 BatchResponse messages CONNECT can handle in one minute and prove that X12 BatchResponse can handle 1600 concurrent messages per minute.
  2. Execute below scenarios four times bidirectionally (Ex: JBoss as initiator and JBoss as responder) on individual CONNECT supported application server and capture metrics and provide a summary including average throughput rate.
    1. Audit logging on using audit proxy secure Implementation.
    2. Audit logging on using audit proxy javaImplementation.
    3. Audit logging off with any audit proxy implementation.

CONNECTLoadTestAdapter - gov.hhs.fha.nhinc.x12.batch.response.loadtest.CORE_X12DSBatchResponseBO

Performance Results

Preliminary test results are located