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.
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
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. Fix Non-Provisioned User Login Problem
syntax errors when code stored in the $ET and $EC variables executes;
and a problem of blanks appearing in the error descriptions in the
error trap due to extrinsic function EZBLD^DIALOG being called
incorrectly.
When a non-provisioned user fails a login, subsequent attempts result
in a "Socket timeout has occurred" error, when they should still
receive the "Error processing login credentials" error.
2. Fix Three Issues in Routine XOBVLL
There are three known issues in routine XOBVLL: two occurrences of
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
