PATS uses Microsoft Outlook email for sending Informational Notifications (INs) and Action Request Notifications (ARNs). One component of the email system is the Lightweight Directory Access Protocol (LDAP). In order for PATS to use LDAP for retrieving user information, an LDAP account was set up with the VA Enterprise Group. The user currently configured for PATS use is named vhaishpats.
This account is used during application configuration. This setting resides in the gov.va.med.pats.notification.properties file:
activedirectory.PRINCIPAL=vhaishpats
LDAP fail-over and load-balancing is also setup during configuration. This setting resides in the gov.va.med.pats.notification.properties file:
activedirectory.SERVER=ldap://bigkahunas.vha.med.va.gov:%ADSERVER_PORT%
1.7 Integration Agreements for use of Java Components
Integration Agreement
|
Description
|
4851 – KAAJEE (Supported)
|
KAAJEE addresses the Authentication and Authorization needs of HealtheVet-VistA web-based applications in the J2EE environment.
|
4148 - VistALink J2M (v1.5) Java APIs (Supported)
|
Lists all Java APIs for the VistALink J2M software package. A summary of all VistALink J2M Java APIs by package is listed first, and the components of each package are presented in detail thereafter.
|
4338 - Person Service Patient Construct Java APIs - used by PATS (Private)
|
Lists supported Java APIs for the Patient Service Construct (PSC) software package that are used by PATS.
|
4368 - Person Service Patient Lookup Java APIs - used by PATS (Private)
|
Lists supported Java APIs for the Patient Service Lookup (PSL) software package that are used by PATS.
|
4369 - Standard Data Service Java APIs - used by PATS (Private)
|
Lists supported Java APIs for the Standard Data Service (SDS) software package that are used by PATS.
|
1.8 PAD Servlet ROC Creation
The PAD servlet is designed to receive XML messages sent over HTTP and automatically generate and store a new ROC. This service was envisioned to work with the Inquiry Routing and Information System (IRIS) but will be compatible with any SOAP web service consumer as long as the IP address of the caller is authorized in the patsweb.properties file.
The PAD functionality is encapsulated in the gov.va.med.pats.pad package in the patsweb project and is implemented in the following two classes:
-
PadServlet.java
-
Main entry point for receiving the XML request
-
Determines the authorized IP address, creates the SOAP object from the request and passes the main ROC XML node to the Roc Parser
-
Validates the resulting ROC object and stores the ROC in the PATS database
-
Processes and sends the successful response message (or error message) back to the service caller
-
RocParser.java
-
Receives the populated XML object from Pad Servlet
-
Transverses each XML node, parses and validates the data and stores in the ROC object
-
Searches for a matching patient in the PATS database and stores in the ROC object if found
-
Flags any error messages for the Pad Servlet to return to the caller
The PAD functionality utilizes the existing PATS classes and delegate framework for patient search, ROC validation, ROC storage, and ROC update. PAD requires a data source connection only to the PATS DB schema supplied by the hosting WebLogic Server.
The PAD servlet is invoked by sending an XML SOAP request to the pad servlet URL:
/pad.servlet. See the PAD ICD at the PAD TSPR documentation page for details on the exact content of the XML request http://tspr.vista.med.va.gov/warboard/anotebk.asp?proj=1425
1.8.1 Troubleshooting PAD
Successful execution of the PAD servlet will always result in an XML response to the caller with an associated ROC number in this format:
Any response from the PAD servlet that does not contain a node in the XML response is an indication that the interface failed to execute properly. Error messages returned from PAD may include:
Your system is not authorized for this function XML error response returned to the caller. This is the message PAD sends back to the service caller if the IP address of the request is not in the authorized ‘iris.ips’ list in patsweb.properties. Validate the IP of the caller and add it to the list.
Error 500--Internal Server Error error message returned to the caller. This message indicates PAD was properly invoked but encountered an unchecked exception during parsing of the XML request; i.e. the thread crashed. Validate the request XML for validity and format. Examine the server log file and associated stack trace for indications of the error.
The is required error message returned to the caller. This message indicates the request XML contained a null value for a required field. Validate the request XML according the PAD ICD and re-send the request.
Invalid error message returned to the caller. This message indicates the request XML contained data for an expected field but the supplied data failed to pass the validation rules; i.e. length was too long or too short. Validate the request XML for the failed data field and re-send the request.
Curl error: Cannot resolve host error message returned to the caller. This message indicates the SOAP request could not find the URL destination for the PAD servlet; most likely due to firewall blocking. Validate the URL and port the caller is using to invoke the PAD servlet.
The VA firewall must be configured to allow incoming requests to the PAD servlet URL to be passed through to the PATS server. Coordinate with the PATS system adiminstrator and the VA NSOC to ensure existing FQDN fowarding rules and server certificates are still valid.
IRIS-PAD SOAP Communication Exchange
-
The IRIS system is provided the external URL to send messages to the PAD Servlet
/PATS/pad.servlet, i.e. www.pats.va.gov/PATS pad.servlet
-
The VA firewall recieves the external request for the URL and forwards to the internal PATS production/staging/dev URL as appropriate to invoke the PAD servlet.
-
PAD processes the ROC and returns the Success message to the caller.
Dostları ilə paylaş: |
