|
VistaLink
Help for the VistaLink Console Extension
|
|
VistaLink Deployed Connectors tab
This tab scans the set of VistaLink ConnectionFactoryMonitor MBeans,
and displays information on each MBean found. There is a 1:1
correspondence between deployed VistaLink connectors, and MBean
instances.
- WLS App Name: The WebLogic application name assigned to the
connector during deployment.
- Deployed JNDI Name: The JNDI name under which the J2EE
container deployed this connector. Clicking on this link opens a detail
page with more detailed information for the connector.
- EIS Type: Indicates the type of connector. All VistALink
connectors should have an EISType of "VistA".
- M System Info: The IP and port of the M system connected to
by this connector.
- Deployment State:The WebLogic deployment state of the
connector.
Health Indicators/Failure Counts:
- JNDI Mismatch: Indicates that the JNDI name used to look up
the connector settings in the VistaLink configuration file does not
match the JNDI name from ra.xml, used by the container to deploy the
connector. This signals that the VistaLink configuration file and the
ra.xml deployment descriptors are not in synch, which could mean a
misconfigured connector.
- Conn Socket: The number of times, since deployment or server
re-start, that an attempt to create a physical connection to the M
system has failed.
- Conn Auth: The number of times, since deployment or server
re-start, that the connector has attempted to log on to the M system
with the connector user access/verify code, and failed.
- Prod Mismatch: The number of times, since deployment or
server re-start, that the connector has attempted to log on to the M
system, and found that the Production setting for the M system does not
match the Prodcution setting for the J2EE server's JVM. On the J2EE
server, this setting is controlled via the
gov.va.med.environment.production JVM argument.
- Div Mismatch: The number of RPC requests, since deployment
or server re-start, that have failed due to the division specified in
the RPC request not being legal for reauthentication user. A large
number of division mismatches may indicate a misconfigured
JNDI-to-institution mapping for the connector in question.
- Re-Auth: The number of times, since deployment or server
re-start, that re-authentication has failed when attempting to execute
RPCs on behalf of users. A large number of failures may indicate a
misconfigured JNDI-to-institution mapping for the connector in
question.
Institution Mappings tab
This tab displays the current set of Institution Mappings, based on
the current live system settings. On connector deployment, mappings for
the connector are read from the VistaLink connector configuration file,
and added to the live set of mappings. When a connector is stopped or
undeployed, its mappings are removed from the live mapping set upon JVM
garbage collection.