VISTALINK (192)    PACKAGE (9.4)

Name Value
NAME VISTALINK
PREFIX XOBV
CURRENT VERSION 1.0
SHORT DESCRIPTION VistaLink
VERSION
  • 1.0
    DATE DISTRIBUTED:   2012-05-08 00:00:00
    PATCH APPLICATION HISTORY:
    • 1
      DATE APPLIED:   2003-03-30 00:00:00
      APPLIED BY:   File: 200, IEN: 990
      DESCRIPTION:   
      This build contains the M side software for the Foundations Toolbox.
       
       
      This build requires that the M XML Parser 1.1 be installed in the account.
      
    • 1 SEQ #1
      DATE APPLIED:   2004-09-24 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       This patch will set the RPC Broker variable XWBOS in VistALink routine
       XOBVSKT which is used in TCP/IP socket processes.
       
       Setting this variable is necessary to accomodate remote procedure calls 
       that test for this variable directly.
      
    DATE INSTALLED AT THIS SITE:   2003-11-21 00:00:00
    INSTALLED BY:   USER,ONE
    DESCRIPTION OF ENHANCEMENTS:   
    This build contains TCP/IP transport functionality that enables
    Handler.
     
    The VISTALINK package contains two native request handlers. One handles 
    system-type requests, like client heartbeats and close socket requests. 
    The other handler processes RPC requests.
     
    Other packages can also supply handlers. For example, VISTALINK SECURITY
    (XOBS) supplies a handler that is used to process VistA security-related
    requests.
     
    synchronous communication from the following:
    VISTALINK allows the following request formats:
       1) XML and conform to a XML Schema 
       2) a proprietary format (package must supply a proprietary parser)
       3) both 1 and 2
     
    VISTALINK also supplies a Java/J2EE component that allows developers of
    Java applications to make synchronous requests on the M server and for M
    applications to make synchronous requests of Java/J2EE application
    servers. The Java/J2EE side implements the J2EE Connector Architecture
    v1.0 framework (J2CA).
       1) from non-M based systems to M-based VistA servers
     
    ** NOTE: As of 7/2005, VISTALINK only supports Java to M communication.
     
    Finally, VISTALINK contains a number of library calls available to 
    other packages for developing a request handler if needed. (Currently, 
    only VISTALINK SECURITY is allowed to use these calls.)
       2) from M VistA servers to non-M systems (typically Java/J2EE based
          systems)
     
    The communications are in the form of requests. For requests received by
    the M-based system, the VISTALINK package contains a Request Manager to
    manage these requests. Requests are forwarded to the appropriate Request
    
  • 1.5
    DATE DISTRIBUTED:   2005-09-09 00:00:00
    PATCH APPLICATION HISTORY:
    • 1 SEQ #1
      DATE APPLIED:   2006-11-22 19:11:56
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      For complete information, see the patch description for patch XOBV*1.5*1
      in the National Patch Module on FORUM.
      
    DATE INSTALLED AT THIS SITE:   2006-06-08 00:00:00
    INSTALLED BY:   USER,ONE
    DESCRIPTION OF ENHANCEMENTS:   
    This build contains TCP/IP transport functionality that enables
    Handler.
     
    The VISTALINK package contains two native request handlers. One handles 
    system-type requests, like client heartbeats and close socket requests. 
    The other handler processes RPC requests.
     
    Other packages can also supply handlers. For example, VISTALINK SECURITY
    (XOBS) supplies a handler that is used to process VistA security-related
    requests.
     
    synchronous communication from the following:
    VISTALINK allows the following request formats:
       1) XML and conform to a XML Schema 
       2) a proprietary format (package must supply a proprietary parser)
       3) both 1 and 2
     
    VISTALINK also supplies a Java/J2EE component that allows developers of
    Java applications to make synchronous requests on the M server and for M
    applications to make synchronous requests of Java/J2EE application
    servers. The Java/J2EE side implements the J2EE Connector Architecture
    v1.0 framework (J2CA).
       1) from non-M based systems to M-based VistA servers
     
    ** NOTE: VISTALINK v1.5 only supports Java to M communication.
     
    Finally, VISTALINK contains a number of library calls available to 
    other packages for developing a request handler if needed. (Currently, 
    only VISTALINK SECURITY is allowed to use these calls.)
     
    [Build: 1.5.0.026]
       2) from M VistA servers to non-M systems (typically Java/J2EE based
          systems)
     
    The communications are in the form of requests. For requests received by
    the M-based system, the VISTALINK package contains a Request Manager to
    manage these requests. Requests are forwarded to the appropriate Request
    
  • 1.6
    DATE DISTRIBUTED:   2009-05-08 00:00:00
    PATCH APPLICATION HISTORY:
    • 3
      DATE APPLIED:   2019-02-01 14:46:56
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Adds a new RPC, XOBV VALIDATE SAML that is used to sign in with a PIV 
      card using 2 Factor Authentication.
      
    DATE INSTALLED AT THIS SITE:   2011-01-20 00:00:00
    INSTALLED BY:   USER,SEVENTEEN
    DESCRIPTION OF ENHANCEMENTS:   
    This build contains TCP/IP transport functionality that enables
    Handler.
     
    The VISTALINK package contains two native request handlers. One handles 
    system-type requests, like client heartbeats and close socket requests. 
    The other handler processes RPC requests.
     
    Other packages can also supply handlers. For example, VISTALINK SECURITY
    (XOBS) supplies a handler that is used to process VistA security-related
    requests.
     
    synchronous communication from the following:
    VISTALINK allows the following request formats:
       1) XML and conform to a XML Schema 
       2) a proprietary format (package must supply a proprietary parser)
       3) both 1 and 2
     
    VISTALINK also supplies a Java/J2EE component that allows developers of
    Java applications to make synchronous requests on the M server and for M
    applications to make synchronous requests of Java/J2EE application
    servers. The Java/J2EE side implements the J2EE Connector Architecture
    v1.0 framework (J2CA).
       1) from non-M based systems to M-based VistA servers
     
    ** NOTE: As of 7/2005, VISTALINK only supports Java to M communication.
     
    Finally, VISTALINK contains a number of library calls available to 
    other packages for developing a request handler if needed. (Currently, 
    only VISTALINK SECURITY is allowed to use these calls.)
       2) from M VistA servers to non-M systems (typically Java/J2EE based
          systems)
     
    The communications are in the form of requests. For requests received by
    the M-based system, the VISTALINK package contains a Request Manager to
    manage these requests. Requests are forwarded to the appropriate Request