70. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 9/24/2019 1:37:59 PM Eastern Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.

70.1 Files compared

#	Location	File	Last Modified
1	PCL-5_v1_build_8.zip\v1_build 8\Unredacted\spp_mha_web-development.zip\spp_mha_web-development\Docs\vistalink	vistalink_1_6_ig.doc	Wed Jul 31 17:35:31 2019 UTC
2	PCL-5_v1_build_8.zip\v1_build 8\Unredacted\spp_mha_web-development.zip\spp_mha_web-development\Docs\vistalink	vistalink_1_6_ig.doc	Tue Sep 24 17:05:34 2019 UTC

70.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	9	2908
Changed	10	25
Inserted	0	0
Removed	0	0

70.3 Comparison options

Whitespace
Character case	Differences in character case are significant
Line endings	Differences in line endings (`CR` and `LF` characters) are ignored
CR/LF characters	Not shown in the comparison detail

70.4 Active regular expressions

No regular expressions were active.

70.5 Comparison detail

	1
	2	VISTALINK
	3	INSTALLATI ON GUIDE
	4	Version 1. 6
	5	December 2 010
	6	Department of Vetera ns Affairs
	7	Office of Informatio n and Tech nology
	8	Product De velopment
	9	Revision H istory
	10	DateDescri ptionAutho r12/03/10V istALink V ersion 1.6 release.P roduct Dev elopment S ervices Se curity Pro gram VistA Link devel opment tea m.
	11	Albany, NY OIFO:
	12	Developer— Mike Kilma de
	13	Developer— Liz Defiba ugh
	14	Bay Pines, FL OIFO:
	15	Developmen t Manager— Charles Sw artz
	16	Tester—Jas on Woodyar d
	17	Oakland, C A OIFO:
	18	Developer— Kyle Clark e
	19	SQA—Gurbir Singh
	20	Technical Writer—Sus an StrackT able i. Re vision His tory
	21	Contents
	22	iiRevision History
	23
	24
	25	iiiContent s
	26
	27
	28	viiTables
	29
	30
	31	viiFigures
	32
	33
	34	ixOrientat ion
	35
	36
	37	ixDocument Overview
	38
	39
	40	xAdditiona l Resource s
	41
	42
	43	1-11.
	44	Introducti on
	45
	46
	47	1-11.1.
	48	About Vist ALink
	49
	50
	51	1-11.1.1.
	52	WebLogic U pdates Pro ject
	53
	54
	55	1-11.2.
	56	VistALink Version Co mpatibilit y
	57
	58
	59	1-11.2.1.
	60	J2EE/WebLo gic Versio n Compatib ility
	61
	62
	63	1-21.2.2.
	64	M Listener Backwards /Forwards Version Co mpatibilit y
	65
	66
	67	1-21.3.
	68	Known Issu es and Lim itations
	69
	70
	71	2-12.
	72	Installati on Overvie w
	73
	74
	75	2-12.1.
	76	Restrictio ns
	77
	78
	79	2-12.2.
	80	Assumption s about In stallers
	81
	82
	83	2-12.3.
	84	Separation of M and J2EE Serve r Installa tion Proce dures
	85
	86
	87	2-12.4.
	88	VistALink Distributi on ZIP Fil e <DIST FO LDER> Stru cture (new structure )
	89
	90
	91	2-22.5.
	92	M Routine Checksum I nformation
	93
	94
	95	2-22.6.
	96	Installati on Summary
	97
	98
	99	2-22.6.1.
	100	VistA/M Se rver
	101
	102
	103	2-22.6.2.
	104	J2EE Appli cation Ser ver
	105
	106
	107	3-13.
	108	VistA/M Se rver Insta llation Pr ocedures
	109
	110
	111	3-13.1.
	112	Preparatio n
	113
	114
	115	3-13.1.1.
	116	Software I nstallatio n Time
	117
	118
	119	3-13.1.2.
	120	Virgin Ins tallations
	121
	122
	123	3-13.1.3.
	124	System Req uirements
	125
	126
	127	3-23.1.4.
	128	System Pre paration
	129
	130
	131	3-33.1.5.
	132	HFS and Nu ll Devices
	133
	134
	135	3-33.1.6.
	136	Deletion o f Obsolete File #18
	137
	138
	139	3-33.2.
	140	Install Vi stALink KI DS Distrib ution
	141
	142
	143	3-33.2.1.
	144	Preliminar y Steps
	145
	146
	147	3-43.2.2.
	148	Stop VistA Link Syste m Processe s
	149
	150
	151	3-43.2.3.
	152	Install KI DS Distrib ution
	153
	154
	155	3-103.3.
	156	(Optional) Configure VistALink Listener
	157
	158
	159	3-103.3.1.
	160	Do I Need to Configu re Listene rs As Part of the Vi stALink In stallation ?
	161
	162
	163	3-103.3.2.
	164	Listener I ntroductio n
	165
	166
	167	3-113.3.3.
	168	Recommende d VistALin k Ports (a ll operati ng systems )
	169
	170
	171	3-113.3.4.
	172	OS-Based L istener Co nfiguratio n for Cach é/VMS Syst ems
	173
	174
	175	3-123.3.5.
	176	OS-Based L istener Co nfiguratio n for Cach é/Linux Sy stems
	177
	178
	179	3-133.3.6.
	180	M-Based Li stener Con figuration for Caché /NT (Windo ws) System s
	181
	182
	183	3-133.4.
	184	(Optional) Verify Li stener Con nectivity
	185
	186
	187	3-133.4.1.
	188	Telnet Tes t
	189
	190
	191	3-143.4.2.
	192	VistALink J2SE Swing Tester Sam ple Applic ation Test (optional )
	193
	194
	195	3-143.5.
	196	(Optional) Configure Connector Proxy Use r(s) for J 2EE Access
	197
	198
	199	3-153.5.1.
	200	Connector Proxy Over view
	201
	202
	203	3-153.5.2.
	204	How to Cre ate Connec tor Proxy User Kerne l Accounts
	205
	206
	207	3-153.6.
	208	Installati on Back-Ou t/Roll-Bac k Procedur e
	209
	210
	211	3-153.6.1.
	212	Reinstall v1.5
	213
	214
	215	3-153.6.2.
	216	Optional D eletions o f v1.6-Onl y Componen ts
	217
	218
	219	4-14.
	220	Oracle Web Logic Appl ication Se rver: Inst allation P rocedures
	221
	222
	223	4-14.1.
	224	Overview
	225
	226
	227	4-14.1.1.
	228	Adapter De ployment D escriptors
	229
	230
	231	4-14.1.2.
	232	VistALink 1.6 Adapte r Changes
	233
	234
	235	4-24.1.3.
	236	VistALink Adapters a nd Classlo ading
	237
	238
	239	4-24.2.
	240	Preparatio n
	241
	242
	243	4-24.2.1.
	244	Software I nstallatio n Time (Va ries)
	245
	246
	247	4-24.2.2.
	248	System Req uirements
	249
	250
	251	4-24.2.3.
	252	Deployer R equirement s
	253
	254
	255	4-34.2.4.
	256	Obtain the VistALink Distribut ion File
	257
	258
	259	4-34.2.5.
	260	Obtain M C onnector P roxy User and Listen er Informa tion
	261
	262
	263	4-34.3.
	264	Upgrading a WebLogic 8.1 Domai n w/Existi ng VistALi nk Adapter s
	265
	266
	267	4-34.3.1.
	268	Back Up Ex ploded RAR Directori es and Vis tALink Con figuration File
	269
	270
	271	4-34.3.2.
	272	If Running the Domai n Upgrade Wizard
	273
	274
	275	4-44.4.
	276	WebLogic 9 /10 Server Configura tion
	277
	278
	279	4-44.4.1.
	280	Create <HE V Configur ation Fold er>
	281
	282
	283	4-54.4.2.
	284	Create/Cop y VistALin k Configur ation File
	285
	286
	287	4-54.4.3.
	288	Place <HEV Configura tion Folde r> on Serv er Classpa th(s)
	289
	290
	291	4-64.4.4.
	292	Create/Upd ate Server log4j Con figuration s
	293
	294
	295	4-74.4.5.
	296	Server JVM Argument: gov.va.me d.environm ent.produc tion
	297
	298
	299	4-74.4.6.
	300	Server JVM Argument: gov.va.me d.environm ent.server type
	301
	302
	303	4-84.5.
	304	WebLogic 9 .x/10.0: I nstall the Console P lug-In (Ad min Server )
	305
	306
	307	4-84.5.1.
	308	Copy Conso le WAR fil e
	309
	310
	311	4-84.5.2.
	312	Start (or Bounce) Ad min Server
	313
	314
	315	4-84.5.3.
	316	Verify Pre sence of V istALink C onsole Plu g-In
	317
	318
	319	4-94.5.4.
	320	Check Conf iguration Editor Acc ess to Con figuration File
	321
	322
	323	4-104.6.
	324	WebLogic 1 0.3: Insta ll the Sta ndalone Co nsole EAR (Admin Ser ver)
	325
	326
	327	4-104.6.1.
	328	Copy Conso le EAR fil e
	329
	330
	331	4-104.6.2.
	332	Deploy Con sole EAR
	333
	334
	335	4-104.6.3.
	336	Access Sta ndalone Vi stALink Co nsole
	337
	338
	339	4-114.6.4.
	340	Check Conf iguration Editor Acc ess to Con figuration File
	341
	342
	343	4-124.7.
	344	Deploy Sha red J2EE L ibraries ( Production Domains O nly)
	345
	346
	347	4-124.8.
	348	Create/Dep loy VistAL ink Adapte r(s)
	349
	350
	351	4-124.8.1.
	352	Add Connec tor Entry to VistALi nk Configu ration Fil e
	353
	354
	355	4-134.8.2.
	356	Create New or Update Existing Adapter Fo lder on Ad min Server
	357
	358
	359	4-134.8.3.
	360	Back Up De ployment D escriptors
	361
	362
	363	4-134.8.4.
	364	Copy New 1 .6 Files
	365
	366
	367	4-144.8.5.
	368	Update Dep loyment De scriptors
	369
	370
	371	4-164.8.6.
	372	Deploy Ada pter
	373
	374
	375	4-164.8.7.
	376	Monitor Ad apter in V istALink C onsole
	377
	378
	379	4-164.9.
	380	Troublesho oting
	381
	382
	383	4-174.10.
	384	Test with J2EE Sampl e Applicat ion (Devel opment Sys tems Only)
	385
	386
	387	4-174.10.1 .
	388	Deploy the Sample We b Applicat ion
	389
	390
	391	1Appendix A: Install ing and Ru nning the J2SE Sampl e Apps
	392	Appendix A -
	393
	394	1Overview
	395	Appendix A -
	396
	397	1Installat ion Instru ctions
	398	Appendix A -
	399
	400	1Appendix B: DSM/VMS -Specific Install In formation
	401	Appendix B -
	402
	403	1Operating System Re quirements
	404	Appendix B -
	405
	406	1Global Pr otection
	407	Appendix B -
	408
	409	1Listener Management for Caché /VMS Syste ms
	410	Appendix B -
	411
	412	1Glossary
	413	Glossary-
	414
	415
	416
	417	Tables
	418	iiTable i. Revision History
	419
	420
	421	3-1Table 3 ‑1. VistA Software D ependencie s for Vist ALink 1.6 installati on
	422
	423
	424	3-2Table 3 ‑2. VistAL ink 1.6 fi le and glo bal instal lation
	425
	426
	427	3-3Table 3 ‑3. Global protectio n
	428
	429
	430	9Table A-6 . VistALin k Sample A pplication Loggers
	431	Appendix A -
	432
	433
	434
	435	Figures
	436	xFigure ii i. Docume ntation sy mbol descr iptions
	437
	438
	439	2-2Figure 2‑1. Direc tory struc ture of th e VistALin k 1.6 Dist ribution Z IP File
	440
	441
	442	3-5Figure 3‑1. KIDS Installati on option: Verify Ch ecksums in Transport Global [X PD PRINT C HECKSUM]
	443
	444
	445	3-6Figure 3‑2. KIDS Installati on option: Backup a Transport Global [XP D BACKUP]
	446
	447
	448	3-9Figure 3‑3. VistA Link J2M I nstallatio n Example
	449
	450
	451	3-13Figure 3‑4: Exam ple XINETD Service C onfigurati on
	452
	453
	454	4-5Figure 4‑1. Admin Server: A dd the cla sspath fol der to the server cl asspath in the setDo mainEnv sc ript
	455
	456
	457	4-9Figure 4‑2. VistA Link 1.6 C onsole
	458
	459
	460	4-11Figure 4‑3. Stan dalone Vis tALink 1.6 Console
	461
	462
	463	4-15Figure 4‑4. webl ogic-ra.xm l sample d eployment descriptor
	464
	465
	466	4-18Figure 4‑5. Vist ALink Samp le Applica tion
	467
	468
	469	4-19Figure 4‑6. Vist ALink Samp le Applica tion Re-au thenticati on Page
	470
	471
	472	4-20Figure 4‑7. Vist ALink J2EE Sample Ap plication Results Pa ge
	473
	474
	475	3Figure A- 2. Test Pr ogram Acce ss/Verify Code Entry
	476	Appendix A -
	477
	478	4Figure A- 3. SwingTe ster RPC L ist
	479	Appendix A -
	480
	481	5Figure A- 4. Test Pr ogram User Informati on
	482	Appendix A -
	483
	484	7Figure A‑ 5. log4jco nfig.xml f ile contai ns extensi ve informa tion on lo g4j config uration op tions
	485
	486	Appendix A -
	487
	488	1Figure B‑ 1. Global protection
	489	Appendix B -
	490
	491
	492
	493	Orientatio n
	494	Document O verview
	495	This manua l provides informati on for ins talling th e VistALin k 1.6 reso urce adapt er and M-s ide listen er. Its in tended aud ience incl udes Java 2 Enterpri se Edition (J2EE) ap plication server adm inistrator s, Informa tion Resou rce Manage ment (IRM) Informati on Technol ogy (IT) S pecialists at Depart ment of Ve terans Aff airs (VA) facilities , and deve lopers of Java appli cations re quiring co mmunicatio n with Vet erans Heal th Informa tion Syste ms and Tec hnology Ar chitecture (VistA)/M (Massachu setts Gene ral Hospit al Utility Multi-Pro gramming S ystem) sys tems.
	496	System adm inistrator s and deve lopers sho uld use th is documen t in conju nction wit h the Vist ALink 1.6 System Man agement Gu ide, which contains detailed i nformation on the Ja va 2 Platf orm, Enter prise Edit ion (J2EE) applicati on server management , institut ion mappin g, the Vis tALink con sole, M li stener man agement, a nd VistALi nk securit y, logging , and trou bleshootin g.
	497	Terminolog y
	498	The term r esource ad apter is o ften short ened in th is guide t o "adapter ," and is also used interchang eably with the term connector.
	499	Text Conve ntions
	500	File names and direc tory names are set o ff from ot her text u sing bold font (e.g. , config.x ml). Bold is also us ed to indi cate Graph ical User Interface (GUI) elem ents, such as tab, f ield, and button nam es (
	501	e.g., "pre ss Delete" ).
	502	All caps a re used to indicate M routines and optio n names (e .g., XMINE T). All ca ps used in side angle brackets indicate f ile names to be supp lied by th e user. Ex ample:
	503	<JAVA_HOME >\bin\java -Dlog4j.c onfigurati on=file:// /c:/localC onfigs/myl og4j.xml
	504	Names for Java objec ts, method s, and var iables are indicated by Courie r font. Sn apshots of computer displays a lso appear in Courie r, surroun ded by a b order:
	505	Select Ins tallation Option: LO AD a Distr ibution
	506	Enter a Ho st File: X OB_1_6_Bxx .KID
	507	In these e xamples, t he respons e that the user ente rs at a pr ompt appea rs in bold font:
	508	Enter the Device you want to p rint the I nstall mes sages.
	509	You can qu eue the in stall by e nter a 'Q' at the de vice promp t.
	510	Enter a '^ ' to abort the insta ll.
	511	DEVICE : HOME// H OME;80;999 <Enter> T ELNET PORT
	512	Boldface t ext is als o used in code and f ile sample s to indic ate lines of particu lar intere st, discus sed in the preceding text:
	513	<?xml vers ion="1.0"? >
	514	<weblogic- connector xmlns="htt p://www.be a.com/ns/w eblogic/90 " xmlns:xs i="http:// www.w3.org /2001/XMLS chema-inst ance" xsi: schemaLoca tion="http ://www.bea .com/ns/we blogic/90
	515	http://www .bea.com/n s/weblogic /90/weblog ic-ra.xsd" >
	516
	517	<!-- For n ew ADAPTER -level jnd i-name, re commend us ing value of connect ion instan ce JNDI na me, append ed with "A dapter" -- >
	518
	519	<jndi-name >vljtestco nnectorAda pter</jndi -name>
	520	The follow ing symbol s appear t hroughout the docume ntation to alert the reader to special i nformation or condit ions.
	521	SymbolDesc riptionUse d to infor m the read er of gene ral inform ation and references to additi onal readi ng materia l, includi ng online informatio n. Used to caution t he reader to take sp ecial noti ce of crit ical infor mationFigu re iii. D ocumentati on symbol descriptio ns
	522	Folder Con ventions
	523	The follow ing logica l folder n ames are u sed in the J2EE Inst allation s ection:
	524
	525	<DIST FOLD ER>
	526
	527
	528	The locati on for the unzipped VistALink distributi on file.
	529
	530	<HEV CONFI GURATION F OLDER>
	531
	532	A folder p laced on t he classpa th of WebL ogic serve rs, contai ning confi guration f iles for a ll Healthe Vet-VistA applicatio ns.
	533	Additional Resources
	534	Product We b Site
	535	The VistAL ink produc t website (http:// URL /vistalink ) summariz es VistALi nk archite cture and functional ity and pr esents sta tus update s.
	536	VistALink Documentat ion Set
	537	The follow ing is the VistALink 1.6 end-u ser docume ntation se t, which c an be down loaded fro m the VA S oftware Do cument Lib rary (VDL) Web site at:
	538	URL
	539	VistALink 1.6 Instal lation Gui de (this m anual): P rovides de tailed ins tructions for settin g up, inst alling, an d configur ing the Vi stALink 1. 6 listener on VistA/ M servers and the Vi stALink re source ada pter on J2 EE applica tion serve rs. Its in tended aud ience incl udes serve r administ rators, IR M IT speci alists, an d Java app lication d evelopers.
	540	VistALink 1.6 System Managemen t Guide: C ontains de tailed inf ormation o n J2EE app lication s erver mana gement, in stitution mapping, t he VistALi nk console , M listen er managem ent, and V istALink s ecurity, l ogging, an d troubles hooting.
	541	VistALink 1.6 Develo per Guide: Contains detailed i nformation about wor kstation s etup, re-a uthenticat ion, insti tution map ping, exec uting requ ests, Vist ALink exce ptions, Fo undations Library ut ilities, a nd other t opics pert aining to writing co de that us es VistALi nk.
	542	VistALink 1.6 Releas e Notes: L ists all n ew feature s included in the Vi stALink 1. 6 release.
	543	VistALink 1.6 end-us er documen tation and software can be dow nloaded an y of the a nonymous.s oftware di rectories on the Off ice of Inf ormation & Technolog y (OI&T) F ile Transf er Protoco l (FTP) do wnload sit esxe "EPS Anonymous Directorie s":
	544	Preferred Method
	545	URL
	546	This metho d transmit s the file s from the first ava ilable FTP server.
	547	Albany OIF O
	548	URL
	549	Hines OIFO
	550	URL
	551	Salt Lake City OIFO
	552	URL
	553	The docume ntation is made avai lable onli ne in Micr osoft Word format an d Adobe Ac robat Port able Docum ent Format (PDF). Th e PDF docu ments must be read u sing the A dobe Acrob at Reader (i.e., ACR OREAD.EXE) , which is freely di stributed by Adobe S ystems Inc orporated at the fol lowing Web addressXE "Adobe:Ho me Page We b Address"
	554
	555	XE "Web Pa ges:Adobe Home Page Web Addres s"
	556
	557	XE "Home P ages:Adobe Home Page Web Addre ss"
	558
	559	XE "URLs:A dobe Home Page Web A ddress":
	560	http://www .adobe.com /
	561	DISCLAIMER : The appe arance of any extern al hyperli nk referen ces in thi s manual d oes not co nstitute e ndorsement by the De partment o f Veterans Affairs ( VA) of thi s Web site or the in formation, products, or servic es contain ed therein . The VA d oes not ex ercise any editorial control o ver the in formation you may fi nd at thes e location s. Such li nks are pr ovided and are consi stent with the state d purpose of this VA Intranet Service.In troduction
	562	About Vist ALink
	563	The VistAL ink resour ce adapter is a tran sport laye r that pro vides comm unication between He altheVet-V istA Java applicatio ns and Vis tA/M serve rs, in bot h client-s erver and n-tier env ironments. It is a r untime and developme nt tool th at allows java appli cations to execute r emote proc edure call s (RPCs) o n the Vist A/M system and retri eve result s, synchro nously. Vi stALink is also refe rred to as VistALink J2M.
	564	VistALink consists o f Java-sid e adapter libraries and an M-s ide listen er:
	565	The adapte r librarie s use the J2EE Conne ctor Archi tecture (J 2CA) 1.5 s pecificati on to inte grate Java applicati ons with l egacy syst ems.
	566	The M list ener proce ss receive s and proc esses requ ests from client app lications.
	567	Java appli cations ca n call Rem ote Proced ure Calls (RPCs) on the M serv er, execut ing RPC Br oker RPCs on the M s erver with out modifi cation.
	568	The previo us version of VistAL ink, 1.5, was releas ed in June of 2006, and provid ed project developer s with J2E E and Java Platform, Standard Edition (J 2SE) appli cation con nectivity to VistA/M servers. It was des igned spec ifically f or J2EE 1. 3 applicat ion server s (e.g., W ebLogic 8. 1).
	569	WebLogic U pdates Pro ject
	570	In support of the De partment o f Veterans Affairs I nformation Technolog y applicat ion Modern ization ef fort, the three appl ications F at-client Kernel Aut henticatio n and Auth orization (FatKAAT), Kernel Au thenticati on and Aut horization for the J ava 2 Ente rprise Edi tion (KAAJ EE) and Vi stALink ha ve been de veloped. B ased on th e directio n of the T echnical R eview Mode l (TRM) an d in order to suppor t applicat ions that upgrade to the new W ebLogic Se rver versi ons 9.2 an d 10.x, th is project is requir ed. The sc ope of the project i s to upgra de these t hree appli cations to work with the WebLo gic Server 9.2 and 1 0.x.
	571	VistALink Version Co mpatibilit y
	572	J2EE/WebLo gic Versio n Compatib ility
	573	Significan t changes to the J2C A specific ation were made in J 2EE 1.4, a nd additio nal change s in WebLo gic classe s (e.g., c onsole ext ensions) w ere also m ade for We bLogic 9.x . As a res ult, some components of VistAL ink 1.5 ar e not comp atible wit h WebLogic 9 and hig her. All c omponents of VistALi nk 1.6 are compatibl e with Web Logic 9 an d higher, up to and including WebLogic 1 1g.
	574	VistALink versionJ2E E 1.3
	575	WebLogic 8 .1J2EE 1.4 +
	576	WebLogic 9 .x, 10.x, 11g1.5yesn o1.6noyesM Listener Backwards/ Forwards V ersion Com patibility
	577	The 1.5 an d 1.6 M li steners ar e backward s and forw ards compa tible, as follows:
	578	1.6 client s cannot e xecute req uests agai nst 1.5 M listeners
	579	1.5 client s can exec ute reques ts against 1.6 M lis teners
	580	1.0 client s can exec ute reques ts against 1.5 and 1 .6 listene rs
	581	Known Issu es and Lim itations
	582	VistALink console pl ug-in on W ebLogic v1 0.0: In We bLogic v10 .0, there is no navi gation lin k for the VistALink console ex tension in the WebLo gic consol e navigati on tree (l eft hand s ide of the console). A possibl e bug has been repor ted to Ora cle (forme rly BEA).
	583	Workaround : An alter nate route to the Vi stALink co nsole is t o click on the top l ink of the navigatio n tree, wh ich is the domain na me. On the right-han d page, on e of the t abs is 'Vi stALink J2 M'.
	584	VistALink console pl ug-in on W ebLogic v1 0.3: In We bLogic v10 .3, the na vigation l ink and ta b link to access the VistALink console e xtension m ay not be displayed in the Web Logic cons ole on som e systems, upon sub sequent lo gins after initial d eployment, leaving t he console extension inaccessi ble.
	585	Workaround : An alter native ver sion of th e VistALin k console has been p rovided as a standal one EAR. U se the sta ndalone EA R version of the Vis tALink con sole for W ebLogic 10 .3 (and an y other fu ture versi on of WebL ogic that has the sa me problem ).
	586
	587	Anomaly: U nexplained Productio n/Test Mis match Erro r During T esting: On e unexplai ned anomal y was repo rted durin g testing with CHDR 2.0. VistA Link conne ctions to VistA site s began fa iling on o ne of the 6 CHDR Web Logic serv ers, with the logger error bei ng a produ ction/test mismatch, where Vis tALink req uests were incorrect ly reporti ng that th e CHDR ser ver in que stion was not a prod uction ser ver. The s etting use d by VistA Link to de termine if a given W ebLogic se rver is te st or prod uction is a server-s pecific JV M configur ation argu ment confi gured by t he data ce nter. The argument a ppeared to be set co rrectly on the serve r in this case.
	588
	589	The anomal y has occu rred once on one ser ver, after 5 months of running in produc tion. The impact was that the affected W ebLogic se rver could not acces s producti on VistA s ervers, an d that eac h failed c onnection attempt ad ded an err or to each VistA sit e's error log. After a number of server restarts, and examin ations / p ossible up dates to t he server configurat ion, the p roblem res olved itse lf. Withou t a deeper investiga tion, it w as not pos sible to i solate whi ch system component was respon sible for the observ ed failure .
	590
	591	Workaround : None.
	592	Installati on Overvie w
	593	Restrictio ns
	594	VistALink 1.6 has be en tested and is sup ported on Oracle Web Logic Serv er 9.x and 10.x, onl y.
	595	Assumption s about In stallers
	596	These inst ructions a ssume that installer s will hav e a basic working kn owledge of J2EE and M systems, including applicati on deploym ents.
	597	Separation of M and J2EE Serve r Installa tion Proce dures
	598	This guide provides VistALink installati on instruc tions. Bec ause VistA Link consi sts of mod ules for b oth a Java 2 Enterpr ise Editio n (J2EE) a pplication server an d a VistA/ M server, separate s ets of ins tructions are provid ed to set up, config ure, and i nstall the appropria te module( s) on each type of s erver.
	599	At product ion facili ties in pa rticular, different administra tors may b e responsi ble for th e two serv er types ( M and J2EE ); thus, s eparate pa rts of the installat ion proces s. At such sites, co mpleting b oth sides of a VistA Link insta llation wi ll require ongoing c ommunicati on and coo rdination between th e two type s of syste m administ rators. De velopers, on the oth er hand, m ay be resp onsible fo r both sid es of the installati on process , M and J2 EE.
	600	Though the VistA/M s erver inst ructions a re present ed first i n this doc ument, the order is arbitrary— most of th e steps fo r the two servers ar e not depe ndent on e ach other.
	601	VistALink Distributi on ZIP Fil e <DIST FO LDER> Stru cture (new structure )
	602	The VistAL ink distri bution ZIP file cont ains:
	603	Directory Structure of the Vis tALink 1.6 Distribut ion ZIP Fi le /vlj-1. 6.0.xxx
	604	/app -j2ee Applicatio n componen ts for J2E E installa tion
	605	/configFil e-j2ee sample gov .va.med.vi stalink.co nnectorCon fig.xml
	606	c onfigurati on file
	607	/console-e xt Console pl ug-ins and standalon e EAR vers ion
	608	/Rar-Dev-T emplate RAR for de velopment systems
	609	/Rar-Prod- Template RAR for pr oduction s ystems
	610	/sample J2EE sampl e applicat ion
	611	/shared-li b shared lib raries for productio n systems
	612	/jav adoc javadoc fo r public j ava-side V istALink A PIs
	613	/lib -deprecate d contains s upporting jar no lon ger needed in most
	614	c ases
	615	/log 4j configurat ion file e xamples, V istALink l ogger
	616	s preadsheet
	617	/m KIDS distr ibution co ntaining M side of V istALink
	618	/rpc -doc extract of RPC Broke r document ation on h ow to writ e
	619	R PCs
	620	/sam ples-J2SE sample J2S E rich cli ent applic ationsFigu re 2‑1. Di rectory st ructure of the VistA Link 1.6 D istributio n ZIP File
	621	M Routine Checksum I nformation
	622	The routin e name and correspon ding check sum value for each M routine c ontained w ithin the VistALink 1.6 softwa re package is provid ed in the README.TXT file in t he <DIST_F OLDER>'s r oot folder .
	623	Installati on Synopsi s
	624	VistA/M Se rver
	625	The detail ed instruc tions for installing VistALink on the Vi stA/M serv er are pre sented in chapter 3, "VistA/M Server Ins tallation Procedures
	626	." The gen eral steps for insta lling Vist ALink on t he VistA/M server ar e as follo ws:
	627	Preparatio n
	628	Install Vi stALink Ke rnel Insta llation an d Distribu tion Syste m (KIDS) D istributio n
	629	(Optional) Configure VistALink Listener – not nece ssary when upgrading an existi ng configu ration
	630	(Optional) Verify Li stener Con nectivity
	631	(Optional) Configure Connector Proxy Use r(s) for J 2EE Access – not nec essary whe n upgradin g an exist ing config uration
	632	J2EE Appli cation Ser ver
	633	The detail ed instruc tions for installing VistALink on the J2 EE applica tion serve r are pres ented in c hapter 4, "Oracle We bLogic App lication S erver: Ins tallation Procedures
	634	." The gen eral steps for insta lling Vist ALink on t he J2EE ap plication are as fol lows:
	635	Preparatio n
	636	Upgrading a Previous Installat ion
	637	Server Pre paration
	638	Install th e Console Plug-In or Standalon e Console (Admin Ser ver)
	639	Create/Dep loy VistAL ink Adapte rs
	640	Test with J2EE Sampl e Applicat ion (Devel opment Sys tems Only)
	641	VistA/M Se rver Insta llation Pr ocedures
	642	Preparatio n
	643	Software I nstallatio n Time
	644	The estima ted time f or the ins tallation of the Vis tALink KID S distribu tion is le ss than fi ve minutes .
	645	Virgin Ins tallations
	646	It is not necessary for a prev ious versi on of Vist ALink to b e installe d on your VistA/M se rver befor e you inst all VistAL ink 1.6.
	647	System Req uirements
	648	Patch Requ irements
	649	Before the VistALink 1.6 insta llation, t he followi ng package s and patc hes must b e installe d:
	650	SoftwareVe rsionPatch Informati onKernel8. 0Fully pat ched. Kern el Toolkit 7.3Fully p atched.Mai lMan8.0Ful ly patched .RPC Broke r1.1Fully patched.VA FileMan22 .0Fully pa tched.Tabl e 3‑1. Vis tA Softwar e Dependen cies for V istALink 1 .6 install ation
	651	Operating System Req uirements
	652	Caché/VMS: Caché (ve rsion 5.0. 21 or grea ter)
	653	Caché/NT: Caché (ver sion 5.0.2 1 or great er)
	654	Caché/Linu x: Caché ( version 5. 2.3 or gre ater)
	655	NOTE: "NT" means Win dows NT, 2 000, XP, e tc.VistA/M Server Pe rmissions
	656	Kernel-lev el program mer access (DUZ(0)=" @") is req uired for installing VistALink 1.6.
	657	On a VMS s ystem, the installer must have a VMS acc ount. Inst allers who are also configurin g Transmis sion Contr ol Protoco l (TCP) se rvices for VistALink listeners must also hold suff icient Vir tual Memor y System ( VMS) privi leges (e.g ., SYSPRV) .
	658	Namespaces
	659	VistALink has been a ssigned th e XOB* nam espace.
	660	File and G lobal Info rmation
	661	VistALink 1.6 instal ls the fol lowing fil es:
	662	File #File NameRoot GlobalFile Man
	663	Protection 18.01FOUND ATIONS SIT E PARAMETE RS^XOB(18. 01,@18.03V ISTALINK L ISTENER CO NFIGURATIO N^XOB(18.0 3,@18.04VI STALINK LI STENER STA RTUP LOG^X OB(18.04,@ 18.05VISTA LINK MESSA GE TYPE^XO B(18.05,@T able 3‑2. VistALink 1.6 file a nd global installati on
	664	System Pre paration
	665	Global Pla cement, Ma pping, and Translati on
	666	VistALink utilizes o ne VistALi nk-specifi c global, ^XOB. For virgin ins talls, ^XO B should b e placed i n a databa se locatio n appropri ate for a small, sta tic global , prior to installat ion.
	667	For M conf igurations with mult iple datab ases or vo lume sets, any neces sary mappi ng or tran slation sh ould be se t up at th is time as well.
	668	Journaling
	669	Because th e ^XOB glo bal is rel atively st atic, jour naling of this globa l is not r equired.
	670	Global Pro tection
	671	Global Nam eCaché^XOB Owner:RWDG roup:NWorl d:NNetwork :RWDTable 3‑3. Globa l protecti on
	672	HFS and Nu ll Devices
	673	Verify tha t you have a Host Fi le Server (HFS) devi ce named " HFS" and a Null devi ce named " NULL" in t he DEVICE file (#3.5 ).
	674	NOTE: You can have o ther devic es with si milar name s, but one device is needed wh ose name o r mnemonic is "NULL. "Deletion of Obsolet e File #18
	675	During the original testing of VistALink 1.0, it w as discove red that s ome sites might stil l have an old Kernel file resi ding on th eir system called SY STEM file (#18). To support vi rgin insta lls, VistA Link 1.6 s till inclu des steps to check a nd clean u p File #18 .
	676	If your sy stem alrea dy has Vis tALink 1.0 or 1.5 in stalled, t his file h as already been remo ved. Other wise, if p resent on your syste m, you may wish to m anually ba ck up and delete SYS TEM file ( #18). If t his file i s on your system at the time o f installi ng VistALi nk 1.6, th e environm ent check will delet e the file for you.
	677	NOTE: This file was created in the early 1980s and was a pre cursor to the curren t KERNEL S YSTEM PARA METERS fil e (#8989.3 ). However , it is no w obsolete and must be removed from your system be fore the V istALink p ackage can be instal led, becau se it shar es the sam e number s pace that VistALink was assign ed.Install VistALink KIDS Dist ribution
	678	Follow the steps in this secti on to inst all VistAL ink KIDS d istributio n.
	679	Preliminar y Steps
	680	Obtain the VistALink KIDS dist ribution. Download e ither the entire Vis tALink ZIP distribut ion file ( XOB_1_6.ZI P), or jus t the stan dalone KID S build (X OB_1_6_Bxx .KID, whe re xx is a build num ber) from the anonym ous.softwa re directo ry on any of the OI& T FTP down load sites .
	681
	682	NOTE: I f you down load the e ntire ZIP distributi on, after unzipping it, the KI DS build i s located in the unz ipped m su bfolder.FT P (or othe rwise tran sfer) the KIDS build file to t he intende d VistA/M server.
	683	Log on to your VistA /M server. Select th e Programm er Options . . . men u from the Systems M anager Men u option ( EVE).
	684	Stop VistA Link Syste m Processe s
	685	If a previ ous versio n of VistA Link is ru nning on y our system , stop the VistALink Listener on the ser ver. Follo w your nor mal proced ures to st op the Vis tALink Lis tener:
	686	If your Vi stALink li stener run s via VMS TCP Servic es, use VM S TCP serv ices to di sable the service (l istener)
	687	If your Vi stALink li stener pro cess runs within Cac hé (not vi a VMS TCP services), use the F oundations menu to s top the li stener.
	688	VistALink users must be stoppe d.
	689
	690	NOTE: C heck the s ystem stat us for any XOBVSKT r outines th at are run ning (e.g. , VistALin k Handler) . If you f ind any of these job s running on the sys tem, notif y users to log off o r FORCEX t he jobs. A ctive user s may get NOSOURCE o r CLOBBER errors.Whi le install ing this p ackage on the server , do not r un any Vis tALink-bas ed Client/ Server sof tware (e.g ., Care Ma nagement).
	691	Roll-and-s croll and RPC Broker users may remain on the syste m
	692	TaskMan do es not nee d to be pu t into a w ait state
	693	CAUTION: I f you acce pt a risk of VistALi nk clients getting a CLOBBER/E DITED erro r, VistALi nk/Care Ma nagement u sers may r emain runn ing. Other wise stop all other VistALink/ Care Manag ement jobs on the sy stem.Insta ll KIDS Di stribution
	694	NOTE: T he XOB_1_6 _Bxx.KID d istributio n exports 3 VistALin k packages /transport globals: XOBU 1.6, XOBV 1.6, and XOBS 1 .6. For in stallation , KIDS wor ks with th em as a si ngle unit. When prom pted by KI DS to ente r a packag e for load ing/instal ling, alwa ys enter X OBU 1.6. D oing this will load/ install al l 3 packag es contain ed in the distributi on, in the correct o rder. Load Distribut ion.
	695	Use the KI DS Install ation opti on, Load a Distribut ion [XPD L OAD DISTRI BUTION].
	696	Enter "XOB _1_6_Bxx.K ID" as the name of t he Host fi le (where xx is a bu ild number ). If the KIDS file is not in the Kernel 's default HFS direc tory on th e host fil e system, you will n eed to inc lude the d irectory p ath to the file as w ell.
	697	The Load a Distribut ion option will load three tra nsport glo bals conta ined withi n the dist ribution:
	698	XOBU 1.6
	699	Common fil es and lib raries use d by all t he XOB* pa ckages and menu opti ons to man age site p arameters/ operations
	700	XOBV 1.6
	701	Handles sy stem and R PC request s
	702	XOBS 1.6
	703	M-side sec urity modu le
	704	Verify Che cksums.
	705
	706	Run the KI DS Install ation opti on, Verify Checksums in Transp ort Global [XPD PRIN T CHECKSUM ]. This op tion will ensure the transport global wa s not corr upted in t ransit.
	707
	708	At the Sel ect Select INSTALL N AME: promp t, enter X OBU 1.6. C hecksums f or all 3 V istALink p ackages (X OBU 1.6, X OBV 1.6 an d XOBS 1.6 ) will be displayed.
	709
	710	NOTE: When executing the Verif y Checksum s option, the checks ums for al l three pa ckages (XO BU, XOBV, and XOBS) are displa yed. Howev er, due to page feed s, you may need to s croll back up to see the check sums for t he first t wo package s.Follow t he example below:
	711	Select Ins tallation Option: V erify Chec ksums in T ransport G lobal
	712	Select INS TALL NAME: XOBU 1 .6 <ENTER> Loaded fr om Distrib ution 4/3 /08@09:54: 49
	713	=> Fo undations, VistALink and VistA Link Secur ity v1.6 ;Created o n Apr 03
	714	This Distr ibution wa s loaded o n Apr 03, 2008@09:54 :49 with h eader of
	715	Foundat ions, Vist ALink and VistALink Security v 1.6 ;Crea ted on Apr 03, 2008@
	716	09:34:33
	717	It cons isted of t he followi ng Install (s):
	718	XOB U 1.6 XOBV 1.6 XOB S 1.6
	719	Want each Routine Li sted with Checksums: Yes// NO
	720	DEVICE: HO ME// TEL NET
	721	PACKAGE: X OBU 1.6 Apr 03, 2008 9:58 am PAGE 1
	722	---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------
	723	8 Routi nes checke d, 0 faile d.
	724	PACKAGE: X OBV 1.6 Apr 03, 2008 9:58 am PAGE 1
	725	---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------
	726	16 Rout ines check ed, 0 fail ed.
	727	PACKAGE: X OBS 1.6 Apr 03, 2008 9:58 am PAGE 1
	728	---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------
	729	7 Routi nes checke d, 0 faile d.
	730	Figure 3‑1 . KIDS Ins tallation option: Ve rify Check sums in Tr ansport Gl obal [XPD PRINT CHEC KSUM]
	731	Backup Tra nsport Glo bal.
	732
	733	Use the KI DS Install ation opti on, Backup a Transpo rt Global [XPD BACKU P]. This o ption crea tes a Mail Man messag e that wil l backup a ll current routines on your Vi stA/M syst em that wi ll be repl aced by th e packages in this t ransport g lobal. (If you need to preserv e componen ts that ar e not rout ines, you must back them up se parately.)
	734
	735	At the Sel ect INSTAL L NAME: pr ompt, ente r XOBU 1.6 . All 3 Vi stALink pa ckages (XO BU 1.6, XO BV 1.6 and XOBS 1.6) will be b acked up.
	736	Follow the example b elow:
	737	Select Ins tallation Option: Ba ckup a Tra nsport Glo bal
	738	Select INS TALL NAME: XOBU 1.6 <ENTER> Lo aded from Distributi on 4/3/08 @09:54:49
	739	=> Fo undations, VistALink and VistA Link Secur ity v1.6 ;Created o n Apr 03
	740	This Distr ibution wa s loaded o n Apr 03, 2008@09:54 :49 with h eader of
	741	Foundat ions, Vist ALink and VistALink Security v 1.6 ;Crea ted on Apr 03, 2008@
	742	09:34:33
	743	It cons isted of t he followi ng Install (s):
	744	XOB U 1.6 XOBV 1.6 XOB S 1.6
	745	Subject: B ackup of X OBU 1.6 in stall on A pr 03, 200 8
	746	Replace <ENTER>
	747	Loading Ro utines for XOBU 1.6. ....
	748	Routine XO BUZAP is n ot on the disk..
	749	Routine XO BUZAP0 is not on the disk..
	750	Routine XO BUZAP1 is not on the disk..
	751	Loading Ro utines for XOBV 1.6. .......... ......
	752	Loading Ro utines for XOBS 1.6. ......
	753	Send mail to: VLUSER ,ONE// <EN TER>
	754	Select bas ket to sen d to: IN// <ENTER>
	755	And Send t o: <ENTER>
	756	Figure 3‑2 . KIDS Ins tallation option: Ba ckup a Tra nsport Glo bal [XPD B ACKUP]
	757	Use the KI DS Install ation opti on, Instal l Package( s) [XPD IN STALL BUIL D] to inst all VistAL ink 1.6.
	758	At the Sel ect INSTAL L NAME: pr ompt, ente r XOBU 1.6 . All 3 Vi stALink pa ckages (XO BU 1.6, XO BV 1.6 and XOBS 1.6) will be i nstalled.
	759
	760	Answer the following install q uestions a s follows:
	761	Although t ypically t he answer is "No," y ou can ans wer "Yes," to the qu estion
	762	Want KIDS to Rebuild Menu Tree s Upon Com pletion of Install?
	763	Just remem ber that r ebuilding menu trees will incr ease patch installat ion time.
	764	Answer "No " to the q uestion:
	765	Want KIDS to INHIBIT LOGONs du ring the i nstall?
	766	Answer "No " to the q uestion:
	767	Want to DI SABLE Sche duled Opti ons, Menu Options, a nd Protoco ls?
	768	The follow ing is an example of a VistALi nk 1.6 ins tallation on a VistA /M server (that has VistALink 1.5 previo usly insta lled):
	769	Select Ins tallation Option: 6 <ENTER> In stall Pack age(s)
	770	Select INS TALL NAME: XOBU 1.6 <ENTER> L oaded from Distribut ion 4/3/0 8@12:00:46
	771	=> Fo undations, VistALink , and Vist ALink Secu rity v1.6 ;Created on Apr 0
	772	This Distr ibution wa s loaded o n Apr 03, 2008@12:00 :46 with h eader of
	773	Foundat ions, Vist ALink, and VistALink Security v1.6 ;Cre ated on Ap r 03, 2008
	774	@11:54:01
	775	It cons isted of t he followi ng Install (s):
	776	XOB U 1.6 XOBV 1.6 XOB S 1.6
	777	Checking I nstall for Package X OBU 1.6
	778	Will first run the E nvironment Check Rou tine, XOBU ENV
	779	>>> Perfo rming envi ronment ch eck...
	780	All runni ng VistALi nk listene rs should be stopped before pr oceeding w ith
	781	this inst allation. Enter ? fo r help on stopping V istALink l isteners.
	782	Have all VistALink listeners been stopp ed? NO// Y ES <ENTER> YES
	783	>>> VistA Link envir onment che ck complet ed for KID S Install Package op tion.
	784	Install Qu estions fo r XOBU 1.6
	785	Incoming F iles:
	786	18.01 FOUNDAT IONS SITE PARAMETERS
	787	Note: You already h ave the 'F OUNDATIONS SITE PARA METERS' Fi le.
	788	Want KIDS to Rebuild Menu Tree s Upon Com pletion of Install? NO// <ENTE R>
	789	Checking I nstall for Package X OBV 1.6
	790	Install Qu estions fo r XOBV 1.6
	791	Incoming F iles:
	792	18.03 VISTALI NK LISTENE R CONFIGUR ATION
	793	Note: You already h ave the 'V ISTALINK L ISTENER CO NFIGURATIO N' File.
	794	18.04 VISTALI NK LISTENE R STARTUP LOG
	795	Note: You already h ave the 'V ISTALINK L ISTENER ST ARTUP LOG' File.
	796	18.05 VISTALI NK MESSAGE TYPE (in cluding da ta)
	797	Note: You already h ave the 'V ISTALINK M ESSAGE TYP E' File.
	798	I will OVE RWRITE you r data wit h mine.
	799	Want KIDS to Rebuild Menu Tree s Upon Com pletion of Install? NO// <ENTE R>
	800	Checking I nstall for Package X OBS 1.6
	801	Install Qu estions fo r XOBS 1.6
	802	Want KIDS to INHIBIT LOGONs du ring the i nstall? NO // <ENTER>
	803	Want to DI SABLE Sche duled Opti ons, Menu Options, a nd Protoco ls? NO// < ENTER>
	804	Enter the Device you want to p rint the I nstall mes sages.
	805	You can qu eue the in stall by e nter a 'Q' at the de vice promp t.
	806	Enter a '^ ' to abort the insta ll.
	807	DEVICE: HO ME// <ENTE R> TELNET
	808	Install St arted for XOBU 1.6 :
	809	Apr 0 3, 2008@12 :22:04
	810	Build Dist ribution D ate: Apr 0 3, 2008
	811	Installin g Routines :
	812	Apr 0 3, 2008@12 :22:04
	813	Running P re-Install Routine: EN^XOBUPRE
	814	Installin g Data Dic tionaries:
	815	Apr 0 3, 2008@12 :22:04
	816	Installin g PACKAGE COMPONENTS :
	817	Installin g INPUT TE MPLATE
	818	Installin g PROTOCOL
	819	Installin g LIST TEM PLATE
	820	Installin g OPTION
	821	Apr 0 3, 2008@12 :22:04
	822	Running P ost-Instal l Routine: EN^XOBUPO ST
	823	Updating Routine fi le...
	824	Updating KIDS files ...
	825	XOBU 1.6 Installed.
	826	Apr 0 3, 2008@12 :22:04
	827	Install M essage sen t #159
	828	Install S tarted for XOBV 1.6 :
	829	Apr 0 3, 2008@12 :22:04
	830	Build Dist ribution D ate: Apr 0 3, 2008
	831	Installin g Routines :
	832	Apr 0 3, 2008@12 :22:04
	833	Running P re-Install Routine: EN^XOBVPRE
	834	Installin g Data Dic tionaries:
	835	Apr 0 3, 2008@12 :22:04
	836	Installin g Data:
	837	Apr 0 3, 2008@12 :22:04
	838	Installin g PACKAGE COMPONENTS :
	839	Installin g INPUT TE MPLATE
	840	Installin g DIALOG
	841	Installin g PROTOCOL
	842	Installin g REMOTE P ROCEDURE
	843	Installin g OPTION
	844	Apr 0 3, 2008@12 :22:05
	845	Running P ost-Instal l Routine: EN^XOBVPO ST
	846	>>> Schedu ling the X OBV LISTEN ER STARTUP option...
	847	>>> The XO BV LISTENE R STARTUP option has previousl y been sch eduled:
	848	Updating Routine fi le...
	849	Updating KIDS files ...
	850	XOBV 1.6 Installed.
	851	Apr 0 3, 2008@12 :22:05
	852	Install M essage sen t #161
	853	Install S tarted for XOBS 1.6 :
	854	Apr 0 3, 2008@12 :22:05
	855	Build Dist ribution D ate: Apr 0 3, 2008
	856	Installin g Routines :
	857	Apr 0 3, 2008@12 :22:05
	858	Installin g PACKAGE COMPONENTS :
	859	Installin g DIALOG
	860	Apr 0 3, 2008@12 :22:05
	861	Updating Routine fi le...
	862	Updating KIDS files ...
	863	XOBS 1.6 Installed.
	864	Apr 0 3, 2008@12 :22:05
	865	Install M essage sen t #163
	866	────────── ────────── ────────── ────────── ────────── ────────── ────────── ──────────
	867	┌───────── ────────── ────────── ────────── ────────── ────────── ─┐
	868	100% │ 25 5 0 75 │
	869	Complete └───────── ────────── ────────── ────────── ────────── ────────── ─┘
	870	Install Co mpleted
	871	Figure 3‑3 . VistALin k J2M Inst allation E xample
	872	NOTE: The option XOB V LISTENER STARTUP w ill be sch eduled for Task Mana ger startu p on Caché /NT system s only.NOT E: The ins tallation adds a new Kernel Ap plication Proxy User named "XO BVTESTER,A PPLICATION PROXY" to the NEW P ERSON file (#200), i f not alre ady presen t. This ap plication proxy user account i s used in the VistAL ink sample Web appli cation to demonstrat e usage of the Vista LinkAppPro xyConnecti onSpec con nection sp ec.5.
	873	Restart li steners: I f VistALin k has alre ady been s et up on y our server , and you want your server to resume ser vicing Vis tALink cli ent reques ts, restar t the Vist ALink List ener on th e server. Follow you r normal p rocedures to start t he listene r. Otherwi se, config uring the listener i s a follow -on task ( see the se ction "Con figure Vis tALink Lis tener"):
	874	If your Vi stALink li stener run s via VMS TCP servic es, use VM S TCP serv ices to en able the s ervice (li stener).
	875	If your Vi stALink li stener is started wi thin Caché (not via VMS TCP se rvices), u se the Fou ndations m enu to sta rt the lis tener.
	876	(Optional) Configure VistALink Listener
	877	Do I Need to Configu re Listene rs As Part of the Vi stALink In stallation ?
	878	If you are upgrading an existi ng VistALi nk install ation, you likely ha ve one or more liste ners alrea dy configu red on you r system. You should not need to add to or change your liste ner config uration in any way. Your exist ing listen er configu rations wi ll continu e to funct ion, witho ut reconfi guration, after upgr ading Vist ALink.
	879	For Caché/ Linux site s only, wi th existin g listener s, you may want to s witch from the M-onl y listener (started from the F oundations menu) to the XINETD version o f the list ener (star ted from t he OS leve l). You ca n do this switch at any time, however; i t does not need to b e done as part of th e installa tion of Vi stALink v1 .6.
	880	For sites where Vist ALink is b eing insta lled for t he first t ime, you w ill need t o configur e at least one new l istener in order to support Vi stALink-ba sed reques ts. You ca n do this as part of the insta llation, o r at later time as i s convenie nt.
	881	Listener I ntroductio n
	882	A VistALin k listener runs on y our M syst em, in ord er for Jav a applicat ions to co nnect to y our M syst em using V istALink. The listen er waits f or and acc epts incom ing client connectio ns on a sp ecified TC P port, an d spawns o ff handler jobs to s ervice tho se connect ion reques ts.
	883	There are two styles of listen ers:
	884
	885	OS-Based S ervice (th e listener runs as a n operatin g system p rocess, i. e., a VMS TCP Servic e, or an L inux XINET D service)
	886	M-Based (t he listene r starts, stops and runs as an M process )
	887	Recommenda tions for which type of listen er to use are based on operati ng system type, and account ty pe:
	888	Production VMS syste ms: Run as a VMS-bas ed TCPIP s ervice
	889	Production Linux sys tems: Run as a Linux -based XIN ETD servic e
	890	Windows sy stems: The M-based l istener mu st be used , includin g for prod uction.
	891	Non-produc tion VMS a nd Linux s ystems: Ei ther the M -based or OS service -based lis tener can be used
	892	The sectio ns below p rovide set up require ments for the Caché/ VMS and Ca ché/NT ope rating sys tems, as w ell as gen eral infor mation for all opera ting syste ms.
	893	Recommende d VistALin k Ports (a ll operati ng systems )
	894	Though any available TCP port may be use d, the rec ommended p ort for th e VistALin k Listener is 8000 f or product ion system s and 8001 for test systems. T his recomm endation c omes from the DBA’s list of re served por ts, publis hed on FOR UM at DBA Option \| P ort Assign ments for TCP.
	895	NOTE: The recommende d port for the VistA Link liste ner is 800 0 for prod uction sys tems and 8 001 for te st systems . Avoiding Port Conf licts
	896	Within a s ingle IP a ddress/sys tem, VistA Link liste ners can b e set up a s:
	897	A single V istALink l istener, r unning on any availa ble port.
	898	Multiple V istALink l isteners r unning on the same I P address/ system, bu t listenin g on diffe rent ports .
	899	To run one listener in a produ ction acco unt and an other in a test acco unt on the same IP a ddress/sys tem, you m ust config ure them t o listen o n differen t ports (e .g., 8000 for produc tion and 8 001 for te st). If, o n the othe r hand, yo u are runn ing the li steners on different IP addres ses/system s, the por ts can be the same ( e.g., one VistALink listener o n every sy stem liste ning on po rt 8000).
	900	OS-Based L istener Co nfiguratio n for Cach é/VMS Syst ems
	901	For produc tion Caché /VMS syste ms, it is recommende d to run t he VistALi nk listene r as a VMS TCP/IP se rvice. The advantage s include:
	902	The abilit y to run t he TCP/IP service on multiple nodes in a cluster. This allow s for an u ninterrupt ed listeni ng process , by redir ecting the job if on e of the n odes in th e cluster goes down.
	903	Since Task Man is not used to s tart the l istener, i t doesn't matter if the TaskMa n process is running on the sa me node(s) as the Vi stALink li stener(s).
	904	REF: For f urther ass istance wi th set-up of a VMS T CP/IP serv ice for Vi stALink, a nd for the latest in formation on recomme nded confi guration, we strongl y recommen d that you log a Rem edy ticket so that t he appropr iate Produ ct Support team (cur rently HST S) can ass ist you.Th e methodol ogy for ru nning Vist ALink as a TCP liste ner was de veloped an d written into a coo kbook by t he HSTS Pr oduct Supp ort team, to aid IRM support s taff. The cookbook, as a docum ent named VISTALINK_ TCPIP_COOK BOOK.DOC, can be obt ained from the HSTS team or do wnloaded f rom the st andard Pro duct Suppo rt ftp dow nload dire ctories.
	905	When confi guring VMS TCP Servi ces, some issues to consider i nclude:
	906	Many of th e operatio ns require elevated VMS privil eges, spec ifically, SYSPRV. Be fore you b egin, use the VMS SH OW PROCESS /ALL comma nd to veri fy that yo u are logg ed into an account t hat has SY SPRV.
	907	If you nee d to creat e a new se rvice, ref er to VIST ALINK_TCPI P_COOKBOOK .DOC for s tep-by-ste p instruct ions.
	908	To modify an already -existing VistALink service:
	909	Use the TC P/IP utili ties to di sable the service, e .g., VLINK :
	910	TCPIP> DIS ABLE SERVI CE VLINK
	911	Copy any u pdated com mand file to the dir ectory use d by the s ervice.
	912	Modify the command f iles to ma tch your e nvironment . You’ll n eed to rem ove the co mment from the appro priate lin e in the ‘ command li ne:’ secti on and the n modify i t to match your conf iguration. Refer to the commen ts for exa mples of h ow the lin e should b e modified .
	913	Save the f ile(s).
	914	Enable the VistALink service, e.g., VLIN K:
	915	TCPIP> ENA BLE SERVIC E VLINK
	916	In general , use VIST ALINK_TCPI P_COOKBOOK .DOC to he lp you:
	917	Set up Vis tALink as a TCP/IP s ervice in VMS
	918	Modify the service c ommand fil e template s to match your envi ronment
	919	Create and update a dedicated VMS user a ccount, e. g., VLINK with the p roper auth orized and default p rivileges (e.g., rem ove OPER p rivilege).
	920	OS-Based L istener Co nfiguratio n for Cach é/Linux Sy stems
	921	For produc tion Caché /Linux sys tems, it i s recommen ded to run the VistA Link liste ner as a X INETD (Lin ux) servic e.
	922	The advant ages inclu de a unifo rm method for starti ng and sto pping Vist ALink as o ne of many different types of listener p rocesses o n Linux.
	923	NOTE: For further as sistance w ith set-up of an XIN ETD servic e for Vist ALink, and for the l atest info rmation on recommend ed configu ration, we strongly recommend that you l og a Remed y ticket s o that the appropria te Product Support t eam can as sist you.A n example of an XINE TD configu ration fil e for a Vi stALink li stener is provided b elow.
	924	#descripti on: VA Vis tALink Lis tener for Port 8000
	925	#
	926	service la s_vlkp
	927	{
	928	type = UNLISTED
	929	disabl e = no
	930	flags = REUSE
	931	socket _type = st ream
	932	protoc ol = tcp
	933	port = 8000
	934	wait = no
	935	user = lastcpip
	936	env = TZ=/usr/sh are/zonein fo/US/Paci fic
	937	server = /usr/lo cal/caches ys/system0 1/bin/cses sion
	938	server _args = sy stem01 -ci -U OEX CA CHELNX^XOB VTCP
	939	instan ces = UNLI MITED
	940	}
	941	Figure 3‑4 : Example XINETD Ser vice Confi guration
	942	You will n eed to adj ust certai n values t o match yo ur system environmen t:
	943	port
	944	user
	945	env
	946	server
	947	server_arg s
	948	M-Based Li stener Con figuration for Caché /NT (Windo ws) System s
	949	See Append ix A, "Lis tener Mana gement for Caché NT, " in the V istALink 1 .6 System Management Guide. Th is approac h starts, manages an d stops th e listener entirely within M ( as opposed to using VMS (TCP/I P utility) or Linux (XINETD) t o start/st op the lis tener.
	950	Note: You can also u se the sam e instruct ions to se t up an M- based (rat her than O S service based) lis tener on L inux and/o r VMS syst em, i.e., for non-pr oduction s ystems.
	951	(Optional) Verify Li stener Con nectivity
	952	The genera l process for testin g the list ener is as follows:
	953	Telnet tes t
	954	VistALink J2SE Swing Tester sam ple applic ation test
	955	Telnet Tes t
	956	Telnet fro m your wor kstation t o the IP a ddress and port of t he VistALi nk listene r. On most workstati ons you ca n do this simply by entering t he telnet IP address port in a command w indow, e.g .:
	957	c:\> telne t 10.21.1. 85 8000 <E nter>
	958	When you c onnect, pr ess <Enter >. If a Vi stALink li stener is running on that port , you shou ld see ech oed someth ing simila r to this example:
	959	<?xml vers ion="1.0" encoding=" utf-8" ?>< VistaLink messageTyp e="gov.va. med.founda
	960	tions.vist alink.syst em.fault" version="1 .5" xmlns: xsi="http: //www.w3.o rg/2001/XM
	961	LSchema-in stance" xs i:noNamesp aceSchemaL ocation="v lFault.xsd "><Fault>< FaultCode>
	962	Server</Fa ultCode><F aultString >System Er ror</Fault String><Fa ultActor>R equest Man
	963	ager</Faul tActor><De tail><Erro r type="Re quest Mana ger" code= "184001" > <Message>R
	964	equest Han dler Loadi ng Error: No message type defi ned</Messa ge></Error ></Detail>
	965	</Fault></ VistaLink>
	966	Although t here is an error mes sage echoe d in this display, t he error i s due to t he fact th at you are connectin g from tel net rather than from a VistALi nk client. If an Ext ensible Ma rkup Langu age (XML) message si milar to t he one abo ve is echo ed back, t he network connectio n between your works tation and the VistA Link liste ner at the requested IP addres s and port is valid.
	967	If you can not make t he telnet connection , there ma y be a pro blem somew here in th e network / firewall / machine TCP confi guration.
	968	If you con nect but d o not see XML output similar t o that in the sample in step 2 above whe n you pres s <Enter>, check the type of l istener th at is runn ing in the port. (It may be a Broker, He alth Level 7 [HL7], or other t ype of lis tener.)
	969	NOTE: To d isconnect the sessio n, press a nd hold th e CTRL key then pres s the righ t brace "] " key: C TRL + ]
	970	This will properly d isconnect the telnet connectio n.NOTE: Er rors (at S ETMSG+5^XO BVRH) will be logged in the Ke rnel error trap when you use t elnet to t est the Vi stALink li stener. Su ch errors can be ign ored when Telnet tes ting is th e source.V istALink J 2SE SwingT ester Samp le Applica tion Test (optional)
	971	To test yo ur M liste ner with t he SwingTe ster sampl e applicat ion, follo w the inst ructions p rovided in Appendix A of this document, "Installin g and Runn ing the J2 SE Sample Applicatio ns."
	972	The SwingT ester J2SE (client/s erver) sam ple applic ation is s upplied in the vljSa mples_1.6. 0.nnn.jar file.
	973	You can us e the Swin gTester sa mple appli cation to perform a standalone test of t he M VistA Link liste ner before proceedin g with the app serve r installa tion.
	974	(Optional ) Configur e Connecto r Proxy Us er(s) for J2EE Acces s
	975	Follow thi s step onl y if you a re setting up a bran d new Vist ALink impl ementation on your V istA/M sys tem for im mediate ac cess by on e or more specific J 2EE server s. This st ep is not necessary if you are upgrading an existi ng VistALi nk impleme ntation.
	976	Connector Proxy Over view
	977	To allow a J2EE syst em to acce ss resourc es on your M system via VistAL ink, you n eed to an M Kernel " connector proxy user " account for the J2 EE system to connect /login to your M sys tem. A con nector pro xy account represent s a specif ic applica tion serve r (not an end-user). A VistALi nk adapter on a J2EE system lo gs on to y our VistA/ M server u sing the a ssigned Ke rnel conne ctor proxy user acco unt, authe nticating with an ac cess/verif y code pai r.
	978	How to Cre ate Connec tor Proxy User Kerne l Accounts
	979	See the Se curity cha pter, "Cre ating Conn ector Prox y Users fo r J2EE Sys tems" sect ion, in th e VistALin k 1.6 Syst em Managem ent Guide, for compl ete instru ctions on how to cre ate connec tor proxy users.
	980	Installati on Back-Ou t/Roll-Bac k Procedur e
	981	If there i s an unfor eseen prob lem with t he install ation of V istALink v 1.6, it is possible to reinsta ll VistALi nk v1.5. P ossible lo sses of fu nctionalit y with a r ollback to v1.5 incl ude:
	982	Inability of any cli ent applic ations tha t have upg raded to V istALink v 1.6 (clien t-side) to connect t o your sit e.
	983	NOTE: Ther e are no F ileMan dat a dictiona ry changes between v 1.5 and v1 .6.Reinsta ll v1.5
	984	To re-inst all v1.5:
	985	Obtain the v1.5 KIDS distribut ion from t he EIE ftp server (X OB_1_5.KID ).
	986	Obtain the v1.5 Inst all Guide from the E IE ftp ser ver and fo llow the i nstallatio n steps in chapter 2 (VistA/M Server Ins tallation Procedures ) to reins tall VistA Link v1.5. Or:
	987	Stop any r unning Vis tALink lis teners (if any are r unning at all).
	988	Use KIDS t o install the XOB_1_ 5.KID dist ribution. The instal l package is XOBU 1. 5.
	989	Start any listeners after the installati on, either from the operating system lev el or Mump s level, d epending o n how Vist ALink list eners have been conf igured at your site.
	990	Optionally verify li stener con nectivity – with tel net and/or with a v1 .5 VistALi nk client applicatio n
	991	Optional D eletions o f v1.6-Onl y Componen ts
	992	Optionally delete th e followin g v1.6-onl y componen ts:
	993	Routines:
	994	XOBUZAP
	995	XOBUZAP0
	996	XOBUZAP1
	997	Protocols
	998	XOBU TERMI NATE A JOB
	999	XOBU TERMI NATE ALL J OBS
	1000	XOBU TERMI NATE CONNE CTION MANA GER
	1001	XOBU TERMI NATE JOBS REFRESH
	1002	XOBU TERMI NATE JOBS UTILITY ME NU
	1003	XOBU TERMI NATE SYSTE M STATUS
	1004	List Templ ates
	1005	XOBU TERMI NATE JOBS UTILITY
	1006	Dialogs
	1007	182010
	1008	Oracle Web Logic Appl ication Se rver: Inst allation P rocedures
	1009	Overview
	1010	Goal: Inst all VistAL ink adapte r(s) on ap plication servers so that J2EE applicati ons runnin g on those servers c an execute requests against on e or more M systems.
	1011	Main insta llation ta sks:
	1012	Admin serv er:
	1013	Make VistA Link confi guration f ile access ible on cl asspath
	1014	Install Vi stALink-sp ecific mon itoring pl ug-in into WebLogic console
	1015	Servers ta rgeted for adapter(s ):
	1016	Make a cop y of VistA Link confi guration f ile access ible on cl asspath
	1017	Install su pporting j ars as J2E E Shared L ibraries ( production servers o nly)
	1018	Install Vi stALink ad apters (on e per uniq ue M syste m IP addre ss/port co mbination)
	1019	Adapter De ployment D escriptors
	1020	VistALink resource a dapters ha ve deploym ent descri ptors that control c onfigurati on of the adapter. T ext editor s are the recommende d tool for editing d eployment descriptor s. These f iles are l ocated in the META-I NF directo ry in each adapter a rchive (RA R):
	1021	ra.xml: Th e standard J2EE depl oyment des criptor fo r J2CA res ource adap ters.
	1022	weblogic-r a.xml: Con tains WebL ogic-speci fic extend ed configu ration inf ormation.
	1023	MANIFEST.M F: Manifes t file def ining info rmation ab out the fi les packag ed in the RAR.
	1024	VistALink 1.6 Adapte r Changes
	1025	VistALink 1.6 adapte rs are upd ated to su pport the new J2EE 1 .4 specifi cations fo r J2EE con nectors, s upported i n WebLogic 9 and 10. Changes s ignificant to the in stallation process a re:
	1026	Deployment Descripto rs. The fo rmat of bo th the ra. xml and we blogic-ra. xml descri ptors is d ifferent. Existing a dapters' d eployment descriptor s need to be updated .
	1027	Linked Ada pters repl aced by J2 EE Shared Libraries. The prima ry benefit of the We bLogic 8.1 linked ad apter was the re-use of one ad apter's re sources (j ars) by ot her adapte rs. The li nked adapt er feature is not su pported fo r upgraded adapters in WebLogi c 9/10. Ho wever, for productio n servers that need to minimiz e resource consumpti on, the re placement feature fo r linked a dapters is to deploy the adapt er jars as "J2EE sha red librar ies".
	1028	Automatic Classloadi ng. In the previous version of VistALink (1.5) run ning on We bLogic 8.1 , VistALin k and its supporting jars need ed to be m anually ad ded to ser ver classp aths. This is no lon ger necess ary with V istALink 1 .6 running in WebLog ic 9/10:
	1029	Jars conta ined in re source ada pter folde rs are loa ded onto t he appropr iate high- level clas sloaders w ith no nee d to manua lly update server cl asspaths ( recommende d for deve lopment sy stems)
	1030	Alternativ ely, Vista Link and s upporting jars can b e deployed as J2EE s hared libr aries (rec ommended f or product ion system s)
	1031	VistALink Adapters a nd Classlo ading
	1032	VistALink resource a dapters ar e intended to be dep loyed and run as sta ndalone de ployments in WebLogi c. The ada pter is th en made av ailable fo r use by a ny applica tion on th e server. To support this, the applicati on server places jav a classes used in th e VistALin k RAR on h igh-level classloade rs visible by all ap plications .
	1033	Preparatio n
	1034	Software I nstallatio n Time (Va ries)
	1035	The estima ted instal lation tim e installi ng VistALi nk adapter s in a Web Logic doma in varies, depending in part o n whether it is a fi rst time i nstallatio n, and in part on ho w many new or existi ng adapter s need to be deploye d or upgra ded. As su ch, a time estimate for indivi dual tasks is provid ed below, from which you can e stimate on how much time is re quired for the insta llation ta sks necess ary on you r system.
	1036	Place Vist ALink conf iguration file on se rver class path: 5 mi nutes per server
	1037	Install co nsole plug -in or sta ndalone EA R (admin s erver): 5 minutes
	1038	Update exi sting 8.1 RAR deploy ment descr iptors: 5- 10 minutes per adapt er
	1039	Install J2 EE shared libraries (productio n servers only): 20 minutes
	1040	Install ne w adapters : 5-15 min utes per a dapter
	1041	System Req uirements
	1042	VistALink 1.6 is sup ported onl y on WebLo gic at the current t ime. This is the req uirement f or install ation:
	1043	Oracle Web Logic Serv er (WLS) 9 .x or 10.x
	1044	Deployer R equirement s
	1045	The WebLog ic adminis trator/dep loyer shou ld have pr ior WebLog ic adminis tration ex perience, and be com fortable w ith (and h ave the pr ivileges f or) the fo llowing ta sks:
	1046	Modify ser ver startu p scripts
	1047	Set "Remot e Start" o ptions for managed s ervers sta rted by No de Manager
	1048	Set JVM ar guments fo r WebLogic servers
	1049	Modify the classpath for WebLo gic server s
	1050	Configure log4j
	1051	Deploy and undeploy applicatio ns
	1052	Bounce ser vers
	1053	Obtain the VistALink Distribut ion File
	1054	You can ob tain the V istALink d istributio n ZIP file from any of the ano nymous.sof tware dire ctories on the Offic e of Infor mation & T echnology (OI&T) Fil e Transfer Protocol (FTP) down load sites . You shou ld unzip i t to a fol der in a g ood workin g location for your WebLogic S erver inst allation p rocess, mo st likely on a drive of the ad ministrati on server for your W ebLogic do main. This location will be re ferred to as the "<D IST FOLDER >" for the rest of t he instruc tions.
	1055	Obtain M C onnector P roxy User and Listen er Informa tion
	1056	If you are configuri ng a new a dapter, co ntact the VistA/M sy stem’s Inf ormation S ecurity Of ficer (ISO ) and/or t he VistA/M system ma nager to o btain the connector proxy user ’s credent ials for t he VistA/M system to which you intend to connect. This infor mation inc ludes:
	1057	Access/ver ify codes for connec tor proxy user
	1058	VistALink listener p ort
	1059	IP address of the Vi stA/M syst em
	1060	See the se ction "Pos t Install: Configure Connector Proxy Use r(s) for J 2EE Access " in this guide for more infor mation on the connec tor proxy user.
	1061	Upgrading a WebLogic 8.1 Domai n w/Existi ng VistALi nk Adapter s
	1062	Back Up Ex ploded RAR Directori es and Vis tALink Con figuration File
	1063	You should back up ( copy) all of your ex ploded RAR directori es, and al so the Vis tALink con figuration file. You will need these to recreate y our adapte rs in the WebLogic 9 /10 domain .
	1064	If Running the Domai n Upgrade Wizard
	1065	There are two approa ches to mo ving from a WebLogic 8.1 domai n to a Web Logic 9/10 domain (a nd only yo u can deci de which i s best):
	1066	Create a n ew WebLogi c 9/10 dom ain from s cratch and redeploy all applic ations to it that yo u want car ried forwa rd, or
	1067	Run Oracle 's domain upgrade wi zard to up grade your WebLogic 8.1 domain to WebLog ic 9/10.
	1068	If you cho ose to upg rade your domain by running th e upgrade wizard (ra ther than starting f rom scratc h with a n ew domain) , we recom mend you p erform the following steps, be fore shutt ing down y our WebLog ic 8.1 dom ain and ru nning the wizard.
	1069	Undeploy R ARs
	1070	If you hav e any Vist ALink adap ters deplo yed, delet e them fro m the WebL ogic confi guration b y navigati ng to:
	1071	mydomain>D eployments >Connector Modules
	1072	Then selec t each ada pter, and click on t he trashca n icon ().
	1073	Undeploy V istALink C onsole
	1074	If you hav e deployed the VistA Link Conso le, delete it from t he WebLogi c configur ation by n avigating to:
	1075	mydomain>D eployments >Web Appli cation Mod ules
	1076	Then selec t the Vist aLink cons ole web ap plication, and click on the tr ashcan ico n ().
	1077	Undeploy S ample Appl ication
	1078	If you hav e deployed the VistA Link sampl e web appl ication, d elete it f rom the We bLogic con figuration by naviga ting to:
	1079	mydomain>D eployments >Applicati ons
	1080	Then selec t the Vist ALink samp le web app lication, and click on the tra shcan icon ().
	1081	WebLogic 9 /10 Server Configura tion
	1082	For the do main's adm in server, and for e ach manage d server t hat will r un VistALi nk adapter s, perform the follo wing steps :
	1083	Create <HE V Configur ation Fold er>
	1084	We recomme nd using a single fo lder to ho ld any ext ernal conf iguration files for all Health eVet (HEV) applicati ons, inclu ding VistA Link. If i t is not a lready pre sent, you should cre ate this f older, on each physi cal WebLog ic server.
	1085	If not alr eady prese nt, create a secure, protected directory to place on the ser ver classp ath for ea ch of your WebLogic servers ru nning Vist ALink. Thi s folder w ill be ref erred to a s the <HEV CONFIGURA TION FOLDE R> in the following steps.
	1086	Ensure tha t this fol der is sec ure and pr otected. T he gov.va. med.vistal ink.connec torConfig. xml file i t will con tain holds login cre dentials f or accessi ng VistA/M systems. On Linux s ystems, ac cess to th e folder s hould be r estricted to the acc ount or gr oup under which WebL ogic runs. On all J2 EE systems , access t o the host file syst em should be protect ed.
	1087	Create/Cop y VistALin k Configur ation File
	1088	VistALink makes use of its own configura tion file to load Vi stALink-sp ecific con nector set tings. Whe n configur ed for you r system, it will co ntain one entry for each VistA Link adapt er.
	1089	Copy the g ov.va.med. vistalink. connectorC onfig.xml configurat ion file i nto the <H EV CONFIGU RATION FOL DER> on ea ch physica l server t hat will b e running VistALink adapters. Also do th is on the admin serv er:
	1090	If upgradi ng a previ ous domain , copy the existing gov.va.med .vistalink .connector Config.xml from that domain
	1091	Obsolete S etting: pr imaryStati onSuffix: This attri bute has b een elimin ated. Any primary st ation numb ers requir ing an alp ha suffix, should in stead be e ntered as part of th e "primary Station" a ttribute, i.e., prim aryStation ="200M".
	1092	Note: If V A institut ion rules are being used, only 200-serie s (Austin Informatio n Technolo gy Center) station n umbers can have alph a suffixes for the p rimary sta tion numbe r.
	1093	If any ent ries have primarySta tionSuffix , they sho uld remove that attr ibute and append the value of the suffix into the existing p rimaryStat ion attrib ute.If thi s is a bra nd new Vis tALink dep loyment, c opy the ex ample conf iguration file from the <DIST FOLDER>/ap p-j2ee/con figFile-j2 ee folder.
	1094	NOTE: For additional informati on on sett ing up a c onnector c onfigurati on file, s ee the sec tion "Vist ALink Conn ector Conf iguration File," in the VistAL ink 1.6 Sy stem Manag ement Guid e.Place <H EV Configu ration Fol der> on Se rver Class path(s)
	1095	Admin Serv er. On adm in servers , modify t he server classpath by updatin g the appr opriate va riable in either the setDomain Env.cmd/.s h (preferr ed) script , or in th e startWeb Logic.cmd/ .sh script (both scr ipts are i n the doma in root’s /bin folde r). Add th e <HEV Con figuration Folder> c lasspath f older to t he PRE_CLA SSPATH (se tDomainEnv ) or CLASS PATH (star tWebLogic) variable.
	1096
	1097	The follow ing exampl e shows ex ample modi fications for a Wind ows (.cmd) setDomain Env script :
	1098
	1099	. . .
	1100	@REM ADD E XTENSIONS TO CLASSPA THS
	1101	@REM for V ISTALINK
	1102	set PRE_CL ASSPATH=%P RE_CLASSPA TH%;C:\Dat a\bea103-s tage\admin \Classpath Folder;
	1103	. . .
	1104	Figure 4‑1 . Admin Se rver: Add the classp ath folder to the se rver class path in th e setDomai nEnv scrip t
	1105	Managed Se rvers. On any manage d servers started by Node Mana ger, updat e the serv er classpa th in the Configurat ion \| Serv er Start t ab of the console. A dding a cl asspath fo lder to th e server c lasspath w ill also n ecessitate specifyin g the comp lete serve r startup classpath, which typ ically mea ns, at a m inimum, in cluding th e followin g jars:
	1106	weblogic_s p.jar
	1107	e.g., c:/b ea/weblogi c92/server /lib/weblo gic_sp.jar
	1108	weblogic.
	1109	e.g., c:/b ea/weblogi c92/server /lib/weblo gic.jar
	1110	webservice s.jar
	1111	e.g., c:/b ea/weblogi c92/server /lib/webse rvices.jar
	1112	tools.jar
	1113	e.g., c:/b ea/jdk150_ 04/lib/too ls.jar (re quired onl y if serve r compilat ion needed , e.g., JS Ps)
	1114	<HEV Confi guration F older>
	1115	(the point of this e xercise)
	1116	NOTE: You can find t he exact c lasspath u sed to sta rt any giv en managed server by examining the log f iles (.out , .log) st ored in th e domain f older, ser vers/<SERV ER NAME> s ubdirector y and look ing for th e value of the java. class.path property. NOTE: No o ther class path chang es are nec essary to support Vi stALink on WebLogic 9/10. (on WebLogic 8 .1, a numb er of jars needed to be manual ly added o n the serv er classpa th). On We bLogic 9/1 0, jars fo r adapters are loade d either a s:
	1117	J2EE share d librarie s (product ion system s), or
	1118	Automatica lly from t he adapter RAR folde r (develop ment syste ms)Create/ Update Ser ver log4j Configurat ions
	1119	VistALink uses log4j for loggi ng. To ena ble VistAL ink loggin g, you sho uld create (or if up grading fr om a previ ous domain , update t he existin g) log4j c onfigurati on file(s) for each server tha t will hav e VistALin k componen ts install ed:
	1120	admin serv er (VistAL ink consol e applicat ion, and/o r adapters )
	1121	managed se rvers (ada pters)
	1122	To help wi th configu ring log4j , in the V istALink < DIST FOLDE R>/log4j d irectory, VistALink- specific l og4j infor mation is provided, including:
	1123	vistalink_ 1_6_logger s.xls (des cribes Vis tALink sup ported log ger catego ries/level s)
	1124	log4jSampl eJ2EEConfi g.xml (exa mple log4j configura tion file for VistAL ink for J2 EE)
	1125	To enable logging:
	1126	Create/upd ate a log4 j configur ation file on each J 2EE server (admin an d managed servers)
	1127	Configure each serve r to find log4j conf iguration file. Meth ods includ e:
	1128	Name the f ile log4j. xml and pl ace in a f older that is on the server cl asspath, s uch as the <HEV CONF IGURATION FOLDER> (W ebLogic wi ll find au tomaticall y), or
	1129	Name the f ile anythi ng, and pu t it in an y location on the se rver file system. Th en configu re each se rver's JVM to start with the f ollowing J VM argumen t to expli citly prov ide the fu ll filepat h for the log4j conf iguration file:
	1130	–Dlog4j.co nfiguratio n=director y/filename
	1131	NOTE: Due to the fac t that usi ng deployi ng VistALi nk adapter s place th e log4j li brary on a classload er higher than all d eployed ap plications , log4j co nfiguratio n on all s ervers wit h VistALin k adapters deployed must conta in the log ger and ap pender log 4j configu rations fo r ALL appl ications d eployed to that serv er. Server JVM Argum ent: gov.v a.med.envi ronment.pr oduction
	1132	The gov.va .med.envir onment.pro duction JV M system p roperty co nfigures w hether the WebLogic server is considered a Test or Productio n server, and is use d in VistA Link and m ade availa ble to oth er applica tions thro ugh the go v.va.med.e nvironment .Environme nt Applica tion Progr am Interfa ce (API). Optionally add the f ollowing J VM argumen t to your server sta rtup(s):
	1133	JVM Argume ntValueDef ault Value -Dgov.va.m ed.environ ment.produ ctionfalse \| truefal seFor prod uction ser vers only, set the " -Dgov.va.m ed.environ ment.produ ction" JVM argument to true. M odify one of the fol lowing loc ations to set this a rgument:
	1134	Admin serv er: modify the setDo mainEnv.cm d/.sh (pre ferred) or startWebL ogic.cmd/. sh script (both scri pts are in the domai n home, /b in subdire ctory). Mo dify the J AVA_OPTION S variable .
	1135	Managed se rvers star ted by nod e manager: In the We bLogic con sole, go t o the <Ser ver Name> \| Configur ation \| Re mote Start tab, and modify the "Argument s" field.
	1136	NOTE: The gov.va.med .environme nt.product ion settin g marks a J2EE syste m as being a "produc tion" or " test" syst em, and is used by V istALink a dapters to prevent a test J2EE system fr om connect ing to a p roduction M system, and vice v ersa.2.
	1137	On non-pro duction We bLogic ser vers, the argument d oes not ne ed to be s et, since the API us ing it def aults to f alse.
	1138	Server JVM Argument: gov.va.me d.environm ent.server type
	1139	On WebLogi c servers, in most c ases the a rgument do es not nee d to be se t (a chang e since Vi stALink 1. 5), becaus e automati c serverty pe detecti on is perf ormed on W ebLogic se rvers, and will succ eed (excep t with unu sual class loader con figuration s.) If set , however, the value of the JV M argument still ove rrides the automatic ally detec ted value.
	1140	The gov.va .med.envir onment.ser vertype JV M system p roperty co nfigures t he value o f the "cur rent" serv er type re turned to VistALink and other applicatio ns by gov. va.med.env ironment.E nvironment API. Opti onally add the follo wing JVM a rgument to your serv er startup (s):
	1141	JVM Argume ntValueDef ault Value -Dgov.va.m ed.environ ment.serve rtypeweblo gic, websp here, jbos s, oracle, j2se, etc .auto-dete cts for we blogic, ot herwise de faults to "unknown"I f you deci de to pass this argu ment to th e server J VMs, optio nally modi fy one of the follow ing locati ons to set this argu ment:
	1142	Admin serv er: modify the setDo mainEnv (p referred) or startWe bLogic scr ipt (both are in the domain ho me, /bin s ubdirector y).
	1143	Managed se rvers star ted by nod e manager: In the We bLogic con sole, go t o the <Ser ver Name> \| Configur ation \| Re mote Start tab, and modify the "Argument s" field.
	1144	WebLogic 9 .x/10.0: I nstall the Console P lug-In (Ad min Server )
	1145	The VistAL ink consol e plug-in is helpful to monito r and trou bleshoot V istALink a dapters. A s such it is useful to install it prior to install ing any Vi stALink ad apters.
	1146	NOTE: For WebLogic 1 0.3, don’t install t he console plug-in. Instead, i nstall the standalon e EAR vers ion of the console. Skip to Se ction "4.6 WebLogic 10.3: Inst all the St andalone C onsole EAR (Admin Se rver)."Cop y Console WAR file
	1147	Copy the a ppropriate version o f the cons ole WAR fi le from th e <DIST FO LDER>/app- j2ee/conso le-ext fol der to the "console- ext" folde r containe d in your WebLogic 9 or 10 dom ain folder :
	1148	For WebLog ic 9.x ins tallations , use Vist aLinkConso le-ext-WLS 9-x.x.x.xx x.war
	1149	For WebLog ic 10.0 in stallation s, use Vis taLinkCons ole-ext-WL S10-x.x.x. xxx.war
	1150	For WebLog ic 10.3 in stallation s, do not install. I nstead, sk ip to Sect ion "4.6 W ebLogic 10 .3: Instal l the Stan dalone Con sole EAR ( Admin Serv er)"
	1151	Start (or Bounce) Ad min Server
	1152	Start (or bounce/res tart) your admin ser ver.
	1153	Verify Pre sence of V istALink C onsole Plu g-In
	1154	If success fully depl oyed, the VistALink console pl ug-in will be reacha ble from i nside the WebLogic a dministrat ion consol e applicat ion in two ways:
	1155	(WebLogic 9.x/10.0) As a tab i n the doma in setting s on the r ight-hand side of th e console. Click on the domain name (the first nav igation tr ee link). "VistaLink J2M" shoul d be a top -level tab on the do main confi guration p age set.
	1156	(WebLogic 9.x only) As a link in the na vigation t ree in the "Domain S tructure" on the lef t-hand sid e of the c onsole. Lo ok under < domain nam e> \| Envir onment. Th ere should be a link called "V istaLinkJ2 M" at the bottom of the Enviro nment link s.
	1157	Click on t he link to open the VistALink console pl ug-in main page. You should se e a page l ike the fo llowing:
	1158
	1159	Figure 4‑2 . VistALin k 1.6 Cons ole
	1160	Check Conf iguration Editor Acc ess to Con figuration File
	1161	On the mai n page of the VistAL ink consol e plug-in, click the "Configur ation File Editor" l ink:
	1162	If the ser ver classp ath on the admin ser ver file s ystem is s et up corr ectly, you should be presented with a li st of entr ies from t he copy of the VistA Link confi guration f ile on you r admin se rver's fil e system.
	1163	Otherwise, if there is a probl em, you wi ll see an error mess age, for e xample, "E rror while retrievin g configur ation file : 'Missing configura tion file path.'.". If you see this or s imilar err or message , check:
	1164	Is the con figuration file pres ent on the host file system of the admin server?
	1165	Is the con figuration file name d "gov.va. med.vistal ink.connec torConfig. xml"?
	1166	Is the fol der contai ning the c onfigurati on file on the class path speci fied in th e setDomai nEnv or st artWebLogi c script o f the admi n server?
	1167	WebLogic 1 0.3: Insta ll the Sta ndalone Co nsole EAR (Admin Ser ver)
	1168	For WebLog ic 10.3 we recommend installin g the stan dalone Vis tALink con sole EAR a pplication , rather t han the co nsole plug -in, due t o difficul ties integ rating wit h the WebL ogic conso le navigat ion tree a nd tab set .
	1169	The VistAL ink consol e is helpf ul to moni tor and tr oubleshoot VistALink adapters. As such i t is usefu l to insta ll it prio r to insta lling any VistALink adapters.
	1170	Copy Conso le EAR fil e
	1171	Copy the c onsole EAR file from the <DIST FOLDER>/a pp-j2ee/co nsole-ext folder to a staging folder on your admin server:
	1172	VistaLinkC onsole-x.x .x.xxx.ear
	1173	Deploy Con sole EAR
	1174	Target the deploymen t to the d omain admi n server o nly.
	1175	Finish the deploymen t, and act ivate chan ges. In th e main "De ployments" listing, the state of the Vis taLinkCons ole applic ation shou ld be New or Prepare d (dependi ng on whet her target ed servers are runni ng or not) .
	1176	Start the applicatio n (in the Deployment list, cho ose Start \| Servicin g all requ ests for t he VistaLi nkConsole applicatio n). The st ate of the applicati on should now be Act ive.
	1177	Access Sta ndalone Vi stALink Co nsole
	1178	If success fully depl oyed, the standalone VistALink console w ill be rea chable at the follow ing URL:
	1179	http://<ad minserver> :<port>/vl console
	1180	You’ll be prompted f or a user name and p assword. U se the sam e credenti als as you would use to login to the Web Logic admi nistration console. From that point on, the standa lone VistA Link conso le applica tion will look almos t identica l to the c onsole ext ension plu g-in versi on.
	1181	Click on t he link to open the VistALink console pl ug-in main page. You should se e a page l ike the fo llowing:
	1182
	1183	Figure 4‑3 . Standalo ne VistALi nk 1.6 Con sole
	1184	Check Conf iguration Editor Acc ess to Con figuration File
	1185	On the mai n page of the VistAL ink consol e, click t he "Config uration Fi le Editor" link:
	1186	If the ser ver classp ath on the admin ser ver file s ystem is s et up corr ectly, you should be presented with a li st of entr ies from t he copy of the VistA Link confi guration f ile on you r admin se rver's fil e system.
	1187	Otherwise, if there is a probl em, you wi ll see an error mess age, for e xample, "E rror while retrievin g configur ation file : 'Missing configura tion file path.'.". If you see this or s imilar err or message , check:
	1188	Is the con figuration file pres ent on the host file system of the admin server?
	1189	Is the con figuration file name d "gov.va. med.vistal ink.connec torConfig. xml"?
	1190	Is the fol der contai ning the c onfigurati on file on the class path speci fied in th e setDomai nEnv or st artWebLogi c script o f the admi n server?
	1191	Deploy Sha red J2EE L ibraries ( Production Domains O nly)
	1192	Copy the f ollowing j ars from < DIST FOLDE R>>/app-j2 ee/shared- lib to you r deployme nt staging area, and deploy ea ch of them as shared libraries :
	1193	log4j.jar
	1194	vljFoundat ionsLib-x. x.x.xxx.ja r
	1195	vljConnect or-x.x.x.x xx.jar
	1196	On product ion domain s only, an d for serv ers that w ill host a dapters on ly, deploy these jar s as J2EE shared lib raries:
	1197	Copy each jar listed above to a file loc ation on t he admin s erver's fi le system.
	1198	Perform a deployment in the We bLogic con sole for e ach jar, u sing the s ame steps as you wou ld for dep loying an EAR. Accep t the defa ults prese nted by th e WebLogic console.
	1199	Target the deploymen t to all s ervers tha t will be hosting Vi stALink ad apters.
	1200	Activate c hanges, ei ther indiv idually or after all libraries are deplo yed.
	1201	NOTE: For J2CA adapt ers, J2EE shared lib raries ser ve as a re placement for WebLog ic 8.1's " linked ada pter" feat ure. Linke d adapters in WebLog ic 8.1 all owed the s haring of jar resour ces across multiple adapters, reducing t he amount of systems resources consumed by multipl e adapters .For devel opment sys tems, depl oying the jars as J2 EE shared libraries is not nec essary. In stead, the jars can be deploye d with eac h adapter, inside ea ch adapter 's RAR fol der.
	1202	Create/Dep loy VistAL ink Adapte r(s)
	1203	Repeat the steps in this secti on for eac h adapter you need t o deploy. You would deploy one adapter f or every M system th at applica tions on y our domain need to c ommunicate with.
	1204	NOTE: Unli ke with We bLogic 8.1 , no jars need to be manually added to t he server classpath in WebLogi c 9/10. No manually added clas spath entr ies are ne cessary fo r librarie s like "vl jConnector ", "vljFou ndationsLi b", and "l og4j" libr ary jars a nymore.Add Connector Entry to VistALink Configurat ion File
	1205	If this is a new ada pter, use the VistaL ink consol e's config uration ed itor to ad d a new co nfiguratio n entry fo r the new adapter. Y ou will ne ed to prov ide:
	1206	A unique J ava Naming and Direc tory Inter face (JNDI ) name for the adapt er to be d eployed un der, (e.g. , vlj/Sale m658) in t he jndiNam e attribut e.
	1207	The primar y station number of the M syst em being c onnected t o, in the primarySta tion attri bute.
	1208	The IP and port of t he VistALi nk listene r on the M system be ing connec ted to (ip and port attributes )
	1209	The access and verif y code for the conne ctor proxy user assi gned by th e M system administr ator (acce ss-code an d verify-c ode attrib utes)
	1210	Be sure to set the " enabled" a ttribute t o true.
	1211	Save the n ew entry.
	1212	Copy the u pdated con figuration file to a ll managed servers t hat will b e hosting the adapte r (if it i s a multi- server dom ain).
	1213	NOTE: Use of the Vis taLink con sole's con figuration editor is not manda tory. The VistALink configurat ion file c an also be edited di rectly usi ng a text editor.Cre ate New or Update Ex isting Ada pter Folde r on Admin Server
	1214	If this is a new ada pter, on t he admin s erver, cre ate a new, empty fol der for th e adapter, with a fo lder name that easil y identifi es the ada pter (e.g. , "vlj/Sal em658").
	1215	NOTE: The folder nam e will bec ome the de fault depl oyment nam e for the adapter wh en display ed in the WebLogic c onsole. So choose fo lder names that will identify the adapte r mnemonic ally to th e administ rators vie wing them in the Web Logic cons ole later. If you are updating an existin g adapter folder fro m a previo us WebLogi c 8.1 doma in, delete :
	1216	all jar fi les in the root dire ctory of t he folder
	1217	all jar fi les in the /lib subd irectory
	1218	Back Up De ployment D escriptors
	1219	If you are updating an existin g adapter folder fro m a previo us WebLogi c 8.1 doma in,, move elsewhere, rename or otherwise back up t he followi ng files i n the exis ting META- INF direct ory:
	1220	ra.xml
	1221	weblogic-r a.xml
	1222	Copy New 1 .6 Files
	1223	Copy the u pdated 1.6 files nee ded for th e RAR from the VistA Link zip d istributio n to the e xisting or new RAR f older:
	1224	Production Systems: Copy the e ntire cont ents of th e <DIST FO LDER>/app- j2ee/Rar-P rod-Templa te folder from the V istALink z ip distrib ution to t he new RAR folder, i ncluding t he entire META-INF s ubfolder.
	1225	Non-produc tion syste ms: <DIST FOLDER>/ap p-j2ee/Rar -Dev-Templ ate folder from the VistALink zip distri bution to the new RA R folder, including the entire lib and M ETA-INF su bfolders.
	1226	Update Dep loyment De scriptors
	1227	The new ra .xml deplo yment desc riptor no longer nee ds to be m odified. L eave as-is the templ ate ra.xml descripto r copied a bove.
	1228	If creatin g a new ad apter, det ermine the JNDI name you want to deploy the adapte r and conn ection-ins tance unde r. Otherwi se, get th e existing JNDI name from the old deploy ment descr iptors. Th is value s hould matc h the valu e used for the adapt er's entry in the Vi staLink co nfiguratio n file ear lier (e.g. , vlj/Sale m658).
	1229	Edit the w eblogic-ra .xml descr iptor copi ed above, as follows :
	1230	In the <co nnection-i nstance> s ection, <j ndi-name> element, r eplace the placehold er value " ${vlj.jndi .name}" wi th the cho sen JNDI n ame.
	1231	In the <co nnection-i nstance> s ection, <c onnection- properties > element, <properti es> elemen t, <proper ty> elemen t, <value> element, replace th e placehol der value "${vlj.jnd i.name}" w ith the ch osen JNDI name.
	1232	Near the t op of the file, in t he first, first-leve l <jndi-na me> proper ty, replac e the plac eholder va lue "${vlj .jndi.name }": we rec ommend usi ng the cho sen JNDI n ame append ed with "A dapter".
	1233	NOTE: This JNDI name (for the entire ada pter) must be differ ent than t he JNDI na me of the connection instance, that was configured in previo us steps a ) and b).I f updating an existi ng adapter , for othe r any prop erties you changed f rom the de faults in the old de scriptors, update th e correspo nding valu es in the new descri ptors.
	1234	NOTE: Link ed adapter s are not supported (i.e., via the WebLo gic 8.1 <r a-link-ref > mechanis m). Any ex isting lin ked adapte rs should be changed to standa lone adapt ers before upgrading .Example w eblogic-ra .xml deplo yment desc riptor:
	1235	<?xml vers ion="1.0"? >
	1236	<weblogic- connector xmlns="htt p://www.be a.com/ns/w eblogic/90 " xmlns:xs i="http:// www.w3.org /2001/XMLS chema-inst ance" xsi: schemaLoca tion="http ://www.bea .com/ns/we blogic/90
	1237	http://www .bea.com/n s/weblogic /90/weblog ic-ra.xsd" >
	1238	<!-- War ning: The order the elements a ppear in c omplex ele ments is u sually imp ortant.
	1239	It is a good idea to va lidate and test the weblogic-r a.xml docu ment befor e committi ng. -->
	1240	<!-- For new ADAPT ER-level j ndi-name, recommend using valu e of conne ction inst ance JNDI name, appe nded with "Adapter" -->
	1241	<jndi-na me>vljtest connectorA dapter</jn di-name>
	1242	<enable- global-acc ess-to-cla sses>true< /enable-gl obal-acces s-to-class es>
	1243	<outboun d-resource -adapter>
	1244	<conne ction-defi nition-gro up>
	1245	<con nection-fa ctory-inte rface>java x.resource .cci.Conne ctionFacto ry</connec tion-facto ry-interfa ce>
	1246	<def ault-conne ction-prop erties>
	1247	<p ool-params >
	1248	<initial-c apacity>1< /initial-c apacity>
	1249	<max-capac ity>5</max -capacity>
	1250	<capacity- increment> 1</capacit y-incremen t>
	1251	<shrinking -enabled>t rue</shrin king-enabl ed>
	1252	<shrink-fr equency-se conds>1800 </shrink-f requency-s econds>
	1253	<highest-n um-waiters >214748364 7</highest -num-waite rs>
	1254	<connectio n-creation -retry-fre quency-sec onds>30</c onnection- creation-r etry-frequ ency-secon ds>
	1255	<connectio n-reserve- timeout-se conds>0</c onnection- reserve-ti meout-seco nds>
	1256	<test-freq uency-seco nds>3600</ test-frequ ency-secon ds>
	1257	<profile-h arvest-fre quency-sec onds>30</p rofile-har vest-frequ ency-secon ds>
	1258	<ignore-in -use-conne ctions-ena bled>false </ignore-i n-use-conn ections-en abled>
	1259	<match-con nections-s upported>t rue</match -connectio ns-support ed>
	1260	</ pool-param s>
	1261	<t ransaction -support>N oTransacti on</transa ction-supp ort>
	1262	<r eauthentic ation-supp ort>false< /reauthent ication-su pport>
	1263	</de fault-conn ection-pro perties>
	1264	<con nection-in stance>
	1265	<d escription >This is t he connect ion and JN DI name th at applica tions will be access ing.</desc ription>
	1266	<j ndi-name>v ljtestconn ector</jnd i-name>
	1267	<c onnection- properties >
	1268	<propertie s>
	1269	<propert y>
	1270	<!-- c onnectorJn diName val ue should be the sam e value as connectio n instance jndi-name a few lin es above - ->
	1271	<name> connectorJ ndiName</n ame>
	1272	<value >vljtestco nnector</v alue>
	1273	</proper ty>
	1274	</properti es>
	1275	</ connection -propertie s>
	1276	</co nnection-i nstance>
	1277	</conn ection-def inition-gr oup>
	1278	</outbou nd-resourc e-adapter>
	1279	</weblogic -connector >
	1280	Figure 4‑4 . weblogic -ra.xml sa mple deplo yment desc riptor
	1281	Deploy Ada pter
	1282	Perform a deployment in the We bLogic con sole for t he new RAR folder (i .e., an ex ploded RAR ). Accept the defaul ts present ed by the WebLogic c onsole.
	1283	Target the deploymen t to all s ervers tha t will be hosting th e VistALin k adapter.
	1284	Finish the deploymen t, and act ivate the changes. I n the main "Deployme nts" listi ng, the st ate of the deployed adapter sh ould be Ne w or Prepa red (depen ding on wh ether targ eted serve rs are run ning or no t).
	1285	Start the server(s) the adapte r is targe ted to, if they aren 't running . The stat e of the d eployed ad apter shou ld now be Prepared.
	1286	Start the adapter it self (in t he Deploym ent list, choose Sta rt \| Servi cing all r equests fo r the adap ter). The state of t he deploye d adapter should now be Active .
	1287	Monitor Ad apter in V istALink C onsole
	1288	With a suc cessfully configured adapter a nd a succe ssful depl oyment, yo u will be able to:
	1289	See the ad apter list ed in the "Live Conn ector Stat us" sectio n of the V istALink c onsole for every run ning serve r it was d eployed on
	1290	On the lis t of conne ctors for any given server, un der "M Sys tem Info", you shoul d see the IP address and port for the co nnector. T his means the adapte r was able to find a nd load se ttings fro m an entry in the Vi stALink co nfiguratio n file on that serve r.
	1291	If you cli ck on hype rlinked JN DI name fo r each con nector, yo u should b e able to access a d etail page for the c onnector, showing ad ditional i nformation and perfo rming a li ve query a gainst the M system to retriev e a number of settin gs, includ ing the in troductory text for the M serv er.
	1292	The failur e counts u nder healt h monitori ng should be '0'. Ot herwise, a n error co ndition ex ists that should be corrected.
	1293	Troublesho oting
	1294	If the ada pter does not appear to be cor rectly con figured or deployed, please re fer to the "Troubles hooting Vi stALink" s ection of the System Managemen t Guide fo r further guidance.
	1295	NOTE: Some of the fi rst places to look w hen troubl eshooting a non-work ing adapte r:
	1296	VistALink console (w hat error messages i f any are displayed when you t ry to view the adapt er and per form a liv e query?)
	1297	WebLogic s erver log files (per server)
	1298	WebLogic c onsole "ou t" output
	1299	log4j log filesTest with J2EE Sample App lication ( Developmen t Systems Only)
	1300	Deploy the Sample We b Applicat ion
	1301	A sample J 2EE applic ation is p rovided to developer s to demon strate the use of Vi stALink in a J2EE en vironment. The sampl e applicat ion is als o a way to test your basic ada pter setup .
	1302	The sample applicati ons is pro vided in t he <DIST F OLDER>/app -j2ee/samp le folder.
	1303	To deploy the sample J2EE appl ication:
	1304	Copy the s ample appl ication's EAR file ( VistaLinkS amples-1.6 .0.xxx.ear ) to the a dmin serve r's host f ile system .
	1305	Perform a deployment in the We bLogic con sole for t he sample applicatio n's EAR. A ccept the defaults p resented b y the WebL ogic conso le.
	1306	Target the deploymen t to any o r all serv ers hostin g VistALin k adapters .
	1307	Finish the deploymen t, and act ivate chan ges. In th e main "De ployments" listing, the state of the sam ple applic ation shou ld be New or Prepare d (dependi ng on whet her target ed servers are runni ng or not) .
	1308	Start the server(s) the applic ation is t argeted to , if they aren't run ning. The state of t he sample applicatio n should n ow be Prep ared.
	1309	Start the applicatio n (in the Deployment list, cho ose Start \| Servicin g all requ ests for t he sample applicatio n). The st ate of the applicati on should now be Act ive.
	1310	To run the sample J2 EE applica tion:
	1311	Point your browser t o
	1312
	1313	http://<yo urserver>: <yourport> /VistaLink Samples
	1314	Example: h ttp://loca lhost:7001 /VistaLink Samples.
	1315	If the ins tall is su ccessful, you should reach a p age titled "VistALin k Sample/D emo J2EE A pplication ."
	1316
	1317	Figure 4‑5 . VistALin k Sample A pplication
	1318	Choose a r e-authenti cation met hod (VPID, Applicati on Proxy, or DUZ) th at will al low you to invoke a valid user identity on the tar get M syst em to run RPCs under .
	1319	NOTE: This user must hold the [XOBV VIST ALINK TEST ER] "B"-ty pe option.
	1320	Note also that if yo u select d efault app lication p roxy user "XOBV VIST ALINK TEST ER", which is distri buted/inst alled by V istALink, that this user is no t assigned this "B"- type optio n by defau lt.Enter t he divisio n (for DUZ (2)) valid for both the user y ou selecte d, and the M system you're con necting to .
	1321	Choose the connector to use, e ither by u sing insti tution map ping featu re, or sel ecting fro m the list of deploy ed connect ors.
	1322
	1323	Figure 4‑6 . VistALin k Sample A pplication Re-authen tication P age
	1324	Press Subm it to atte mpt to run a set of sample RPC s using th e end-user and conne ctor crite ria specif ied.
	1325	The result s, success ful or not , are disp layed on a result pa ge:
	1326
	1327	Figure 4‑7 . VistALin k J2EE Sam ple Applic ation Resu lts Page
	1328	Appendix A : Installi ng and Run ning the J 2SE Sample Apps
	1329	Overview
	1330	The instru ctions in this secti on for set ting up th e SwingTes ter and ot her sample applicati ons assume the use o f a Window s workstat ion. Howev er, becaus e VistALin k is a pur e Java app lication, it is not particular ly tied to the Windo ws client environmen t.
	1331	Four batch files are supplied in the sam ples-J2SE folder of the distri bution, on e for each of the fo ur sample applicatio ns:
	1332	runSwingTe ster.bat ( runs Vista LinkRpcSwi ngTester)
	1333	runSwingSi mple.bat ( runs Vista LinkRpcSwi ngSimple)
	1334	runSwingSi mpleCcow.b at (runs V istaLinkRp cSwingSimp leCcow)
	1335	runRpcCons ole.bat (r uns VistaL inkRpcCons ole)
	1336	A fourth b atch file manages th e environm ent settin gs used by each of t he three b atch files above:
	1337	
	1338	setVistaLi nkEnvironm ent.bat
	1339	Installati on Instruc tions
	1340	Install th e Java Run time Envir onment (JR E)
	1341	VistALink 1.6 requir es the J2S E Java Run time Envir onment (JR E) 5.0 (or higher) o r the Java Developme nt Kit (JD K) to be i nstalled o n the clie nt worksta tion.
	1342	Select J2S E Sample A pplication Location
	1343	To install the J2SE Sample App lication f iles, you should eit her:
	1344	Configure and run th e samples directly i n the unzi pped distr ibution fo lder set, or
	1345	Create a n ew folder to hold th e sample a pplication files, an d copy the contents of the \sa mples-J2SE folder in the distr ibution fi le to the new folder .
	1346	Configure JAVA_HOME
	1347	The JAVA_H OME variab le in the provided s etVistaLin kEnvironme nt batch f ile must b e modified to match the locati on of the Java execu table to u se on your workstati on. You ma y have mul tiple Java Runtime E nvironment s (JREs) o r Java Dev elopment K its (JDKs) installed on your w orkstation . The sele cted JRE f or the JAV A_HOME var iable must be versio n 1.5 or h igher.
	1348	In the set VistaLinkE nvironment .bat file, replace d efault loc ation for the JAVA_H OME enviro nment vari able with the locati on to use on your sy stem, e.g. :
	1349	REM -- set directory with bin subdirecto ry contain ing java.e xe
	1350	REM -- (do n't includ e the /bin subdirect ory)
	1351	REM -- Not e: in gene ral you sh ould obtai n the late st v5 JRE available
	1352	set JAVA_H OME=C:\Pro gram Files \Java\jre1 .5.0_11
	1353	Configure Jar Classp aths
	1354	If you are running t he sample directly o ut of the unzipped d istributio n folder s et, you ca n skip thi s step (cl asspaths s etVistaLIn kEnvironme nt.bat map to the co rrect rela tive folde r location s.)
	1355	Otherwise, ensure th e individu al classpa th setting s in the s etVistaLin kEnvironme nt batch f ile correc tly reflec t the loca tions of e ach of the following files:
	1356	log4j-1.2. 13.jar
	1357	vljConnect or-1.6.0.n nn.jar
	1358	vljFoundat ionsLib-1. 6.0.nnn.ja r
	1359	vljSecurit y-1.6.0.nn n.jar
	1360	Each entry added to the CLASSP ATH variab le needs t o be modif ied to mat ch the fil e name and location of the cor responding library o n your sys tem, as yo u installe d them abo ve. For ex ample:
	1361	REM -- cla sspath for log4j
	1362	set CLASSP ATH=%CLASS PATH%;./lo g4j-1.2.13 .jar
	1363	Grant Your self Kerne l Access t o the Samp le Applica tion
	1364	The Kernel "B"-type option, Vi stALink Te ster [XOBV VISTALINK TESTER] w as created as part o f the M-si de KIDS in stall. To run the sa mple appli cation, yo u will nee d to grant yourself access to the [XOBV VISTALINK TESTER] on the VistA /M server to which y ou will be connectin g (unless you alread y have Ker nel progra mmer acces s on the M server).
	1365	REF: For m ore inform ation on g ranting yo urself acc ess to RPC s, see the RPC Broke r Systems Manual on the VistA Documentat ion Librar y (VDL) at URL .Run the S wingTester Sample Ap plication
	1366	This versi on of Vist ALink incl udes the S wingTester sample ap plication, which is a diagnost ic tool fo r the clie nt worksta tion. You can use th is sample applicatio n to verif y and test the VistA Link clien t/server c onnection and sign-o n process. Use the f ollowing i nstruction s to use t his tool.
	1367	To run the SwingTest er sample applicatio n:
	1368	Launch the batch fil e runSwing Tester.bat by double -clicking on it, or run it in a command window. Th is launche s the main sample ap plication, designed to demonst rate VistA Link funct ionality a nd test se rver conne ctivity.
	1369	If the GUI applicati on window opens, the JAVA_HOME and class path locat ions have probably b een set co rrectly.
	1370	If the GUI applicati on window does not o pen, look in the com mand windo w output f or the rea son for fa ilure. Mos t likely t he Java ex ecutable w as not fou nd at the location s pecified b y JAVA_HOM E, or one of the sup porting ja r files is not in it s specifie d classpat h location .
	1371
	1372	In the ip and port f ields, ent er the IP and port o f the M li stener you r want to connect to , and pres s Connect. (Alternat ively, you could sel ect an ent ry in a ja as.config settings f ile to set the IP an d port.)
	1373
	1374	Click Conn ect on the Access/Ve rify Code interface.
	1375	Enter the Access / V erify code pair you have been assigned. Click OK.
	1376
	1377	Figure A-2 . Test Pro gram Acces s/Verify C ode Entry
	1378	If logon i s successf ul, the st atus chang es to "Con nected." Y ou can pin g the M se rver, and also execu te RPCs us ing the va rious tab options in the Swing Tester app lication.
	1379
	1380	An interfa ce with mu ltiple tab s will dis play. Clic k on the R PC List ta b. Type "X " in the E nter names pace box. Then click Get RPC L ist to dis play the i nformation in the fi gure below .
	1381
	1382	Figure A-3 . SwingTes ter RPC Li st
	1383	To disconn ect, press Disconnec t.
	1384	Troublesho oting
	1385	If the app lication i s unable t o launch, check for errors in the comman d-window o utput. The most like ly source of the pro blem is in correct cl asspath lo cations se t in the b atch file.
	1386	When conne cted, you can also u se the Swi ngTester s ample app to display and verif y your use r informat ion.
	1387	Click on t he User In fo tab in the interf ace shown in the fig ure below.
	1388
	1389	Figure A-4 . Test Pro gram User Informatio n
	1390	Click Get user infor mation to display yo ur user da ta.
	1391	Running th e Other Sa mple Appli cations
	1392	In additio n to Swing Tester, ot her sample applicati ons are pr ovided. Fo llow the s teps provi ded in the section o n the Swin gTester sa mple appli cation to modify set VistaLinkE nvironment .bat for y our JAVA_H OME and fo r the loca tions of v arious lib raries.
	1393	Unlike the SwingTest er sample applicatio n, the rem aining sam ple applic ations req uire the f ile jaas.c onfig to b e set up w ith config urations f or your M server. (S wingTester allows fr ee-form en try of M s erver IP a nd port to connect t o.)
	1394	To set up jaas.confi g to hold the config uration fo r your M s erver's IP and port:
	1395	Modify the jaas.conf ig file in your copi ed samples files, so that the settings f or ServerA ddress and ServerPor tKey are c orrect for connectin g to your M system.
	1396	runRpcCons ole.bat an d runSwing Simple.bat are hard- coded to l oad a conf iguration named "Dem oServer" f rom the ja as.config file. Eith er modify the DemoSe rver confi guration w ith the se ttings nee ded for yo ur M syste m, or, if you add a different configurat ion and co nfiguratio n name, mo dify runRp cConsole.b at and run SwingSimpl e.bat to u se your co nfiguratio n name. (T he -s para meter at t he end of the comman d line tha t launches the appli cation.)Wi th jaas.co nfig and s etVistaLin kEnvironme nt.bat con figured, y ou can the n use the batch file s describe d below to launch th e other tw o sample a pplication s.
	1397	runSwingSi mple.bat
	1398	runSwingSi mple.bat i s a simple r Swing ap plication than Swing Tester. It is a bett er program ming examp le program because i t lacks th e "bells a nd whistle s" of Swin gTester. I t passes a command l ine parame ter to spe cify which configura tion in th e jaas.con fig file s hould be u sed to con nect to.
	1399	runRpcCons ole.bat
	1400	runRpcCons ole.bat is a console -only samp le applica tion. In a ddition to requiring a command -line para meter to s pecify the JAAS conf iguration to connect to, it is dependent on passin g an acces s and veri fy code on the comma nd line, u nless the defaults e mbedded in the appli cation wor k (they pr obably wil l not).
	1401	You can pa ss in acce ss and ver ify codes with addit ional "-a" and "-v" command-li ne paramet ers.
	1402	Enabling L og4J Loggi ng for Cli ent Sample Applicati ons (optio nal)
	1403	Assume th at c:\Prog ram Files\ vistalink\ samples is the curre nt directo ry.
	1404	Folder c: \Program F iles\vista link\sampl es\props c ontains a sample log 4jconfig.x ml configu ration fil e with var ious log4j configura tion optio ns.
	1405	Each sampl e applicat ion will t ry to load the log4j configura tion from the file n amed "prop s\log4jcon fig.xml," relative t o the curr ent direct ory. There fore c:\Pr ogram File s\vistalin k\samples\ props\log4 jconfig.xm l will be loaded.
	1406	The log4jc onfig.xml file withi n the c:\P rogram Fil es\vistali nk\samples \props\ fo lder conta ins extens ive inform ation on v arious log 4j configu ration opt ions. Look at this s imple exam ple of a l og4jconfig .xml file:
	1407	<?xml vers ion="1.0" encoding=" UTF-8" ?>
	1408	<!DOCTYPE log4j:conf iguration SYSTEM "lo g4j.dtd">
	1409	<log4j:con figuration xmlns:log 4j="http:/ /jakarta.a pache.org/ log4j/">
	1410	<appende r name="my ConsoleApp ender1" cl ass="org.a pache.log4 j.ConsoleA ppender">
	1411	<layou t class="o rg.apache. log4j.Patt ernLayout" >
	1412
	1413	<param nam e="Convers ionPattern " value="% -4r [%t] % -5p class %C method %M
	1414	line numbe r %L categ ory %c %x - %m%n"/>
	1415	</layo ut>
	1416	</append er>
	1417	<root>
	1418	<prior ity value ="info" />
	1419	<appen der-ref re f="myConso leAppender 1"/>
	1420	</root>
	1421	</log4j:co nfiguratio n>
	1422	Figure A‑5 . log4jcon fig.xml fi le contain s extensiv e informat ion on log 4j configu ration opt ions
	1423	When you r un the sam ple applic ation, you should se e "logger" output fo r debug an d error in formation being disp layed on t he console window (t he window in which y ou are sta rting up t he applica tion).
	1424	An example log4J pro perties fi le is prov ided in th e
	1425	<DIST FOLD ER>samples -J2SE\prop s folder i n the dist ribution Z IP file.Sa mple Appli cation Log gers
	1426	The follow ing table lists all the logger s used by VistALink sample app lications and log le vels. Syst em adminis trators ma y need to use this l ist when d eciding wh ich logger s to activ ate in the site’s lo g4j config uration fi le.
	1427	Logger Nam eDescripti onEnvironm ent
	1428	(J2EE \| J2 SE )
	1429	PackageCla ssLog Leve lsLoggers for the sa mple appli cations th at demonst rate VistA Link funct ionalityJ2 SEgov.va.m ed.vistali nk.samples VistaLinkR pcSwingSim pleDebug
	1430	ErrorJ2SE" VistaLinkR pcSwingSim pleCcowDeb ug
	1431	ErrorJ2SE" VistaLinkR pcConsoleD ebug
	1432	ErrorJ2SE" VistaLinkR pcConsole. OtherError J2SE"Vista LinkRpcSwi ngTesterDe bugJ2EE"Vi staLinkJ2E ESampleDeb ug
	1433	ErrorTable A-6. Vist ALink Samp le Applica tion Logge rs
	1434	Appendix B : DSM/VMS- Specific I nstall Inf ormation
	1435	NOTE: Most OI&T site s have upg raded from DSM/VMS t o Caché fo r VMS. DSM -specific installati on informa tion has b een retain ed in this appendix. Operating System Req uirements
	1436	DSM/VMS: D SM (versio n 7.2.1 fo r OpenVMS or greater )
	1437	NOTE: Most DSM/VMS s ystems in VA OI&T ha ve been co nverted to Caché/VMS .Global Pr otection
	1438	Global Nam eDSM
	1439	for OpenVM S *^XOBSys tem:RWPWor ld:RWGroup :RWUCI:RW Fig ure B‑1. G lobal prot ection
	1440	Listener M anagement for Caché/ VMS System s
	1441	We recomme nd running VistALink on DSM/VM S systems as a TCP/I P service. See Appen dix B, "Li stener Man agement fo r DSM/VMS Systems," in the Vis tALink 1.6 System Ma nagement G uide.
	1442	Glossary
	1443	Access Cod eA passwor d used by the Kernel system to identify the user. It is used with the verify cod e. Adapter Another t erm for re source ada pter or co nnector.Ad ministrati on ServerE ach Oracle WebLogic server dom ain must h ave one se rver insta nce that a cts as the administr ation serv er. This s erver is u sed to con figure all other ser ver instan ces in the domain.Al iasAn alte rnative fi lename. Al pha/VMSAlp ha: Hewlet t Packard computer s ystem
	1444	VMS: Virtu al Memory SystemAnon ymous Soft ware Direc toriesDire ctories wh ere VHA ap plication, documenta tion, and patch file s are plac ed for dis tribution. APIApplic ation Prog ram Interf aceApplica tion Proxy UserA Ker nel user a ccount des igned for use by an applicatio n rather t han an end -user.Appl ication Se rverSoftwa re/hardwar e for hand ling compl ex interac tions betw een users, business logic, and databases in transa ction-base d, multi-t ier applic ations. Ap plication servers, a lso known as app ser vers, prov ide increa sed availa bility and higher pe rformance. Authentica tionVerify ing the id entity of the end-us er.Authori zationGran ting or de nying user access or permissio n to perfo rm a funct ion.Base A dapterVers ion 8.1 of WebLogic introduced a "link-r ef" mechan ism enabli ng the res ources of a single " base" adap ter to be shared by one or mor e "linked" adapters. The base adapter is a complet ely set up standalon e adapter. Its resou rces (clas ses, jars, etc.) can be linked to and re used by ot her resour ce adapter s (linked adapters), and the d eployer on ly needs t o modify a subset of linked ad apters’ de ployment d escriptor settings.B EA WebLogi cBEA WebLo gic is a J 2EE Platfo rm applica tion serve r. Oracle has acquir ed BEA Sys tems, Inc. From here forward i t will be referred t o as Oracl e.Caché/VM SCache: In terSystems Caché obj ect databa se that ru ns SQL
	1445	VMS: Virtu al Memory SystemCCOW The Clinic al Context Object Wo rkgroup is a standar d defining the use o f a techni que called "context management ," providi ng the cli nician wit h a unifie d view on informatio n held in separate a nd dispara te healthc are applic ations tha t refer to the same patient, e ncounter o r user. Cl asspathThe path sear ched by th e JVM for class defi nitions. T he class p ath may be set by a command-li ne argumen t to the J VM or via an environ ment varia ble.Client Can refer to both th e client w orkstation and the c lient port ion of the program r unning on the workst ation. Con nection Fa ctoryA J2C A class fo r creating connectio ns on requ est. Conne ction Pool A cached s tore of co nnection o bjects tha t can be a vailable o n demand a nd reused, increasin g performa nce and sc alability. VistALink 1.5 uses connection pooling. Connector A system-l evel drive r that int egrates J2 EE applica tion serve rs with En terprise I nformation Systems ( EIS). Vist ALink is a J2EE conn ector modu le designe d to conne ct to Java applicati ons with V istA/M sys tems. The term is us ed interch angeably w ith connec tor module , adapter, adapter m odule, and resource adapter.Co nnector Pr oxy UserFo r security purposes, each inst ance of a J2EE conne ctor must be granted access to the M ser ver it con nects to. This is do ne via a K ernel user account s et up on t he M syste m. This pr ovides ini tial authe ntication for the ap p server a nd establi shes a tru sted conne ction. The M system manager mu st set up the connec tor user a ccount and communica te the acc ess code, verify cod e and list ener IP ad dress and port to th e J2EE sys tem manage r. COTSCom mercial, O ff-The-She lfDBFDatab ase file f ormat unde rlying man y database applicati ons (origi nally dBas e)DCLDigit al Command Language. An intera ctive comm and and sc ripting la nguage for VMS.Divis ionVHA sit es are als o called i nstitution s. Each in stitution has a stat ion number associate d with it. Occasiona lly a sing le institu tion is ma de up of m ultiple si tes, known as divisi ons. To ma ke a conne ction, Vis tALink nee ds a stati on number from the e nd-user’s New Person entry in the KERNEL SYSTEM PA RAMETERS f ile (#8989 .3). It lo oks first for a divi sion stati on number and if it can’t find one, uses the stati on number associated with defa ult instit ution. DSM Digital St andard MUM PS. An M e nvironment , a produc t of Inter Systems Co rp. DUZUnk nown acron ym. A loca l variable holding a number th at identif ies the si gned-on us er. The nu mber is th e Internal Entry Num ber (IEN) of the use r’s record in the NE W PERSON f ile (file #200)EAR f ileEnterpr ise archiv e file. An enterpris e applicat ion archiv e file tha t contains a J2EE ap plication. EISEnterp rise Infor mation Sys temFatKAAT Fat-Client (i.e. Ric h client) Kernel Aut henticatio n and Auth orizationF ile #18SYS TEM file # 18 was the precursor to the KE RNEL SYSTE M PARAMETE RS file (# 8989.3), a nd is now obsolete. It uses th e same num ber space that is no w assigned to VistAL ink. There fore, file #18 must be deleted before Vi stALink ca n be insta lled. FTPF ile Transf er Protoco lGlobalA m ulti-dimen sional dat a storage structure -- the mec hanism for persiste nt data st orage in a MUMPS dat abase.GUIG raphical U ser Interf aceHealthe Vet-VistAT he VHA is converting its MUMPS -based Vis tA healthc are system to a new J2EE-based platform and applic ation suit e. The new system is known as HealtheVet -VistA.HL7 Health Lev el 7IDEInt egrated de velopment environmen t. A suite of softwa re tools t o support writing so ftware. In stitutionV HA sites a re also ca lled insti tutions. E ach instit ution has a station number ass ociated wi th it. Occ asionally a single i nstitution is made u p of multi ple sites, known as divisions. To make a connectio n, VistALi nk needs a station n umber from the end-u ser’s New Person ent ry in the KERNEL SYS TEM PARAME TERS file (#8989.3). It looks first for a division station n umber and if it can’ t find one , uses the station n umber asso ciated wit h default institutio n. Institu tion Mappi ngThe Vist ALink incl udes a sma ll utility that admi nistrators can use t o associat e station numbers wi th JNDI na mes, and w hich allow s runtime code to re trieve the a VistALi nk connect ion factor y based on station n umber.IRMI nformation Resource Management ISOInforma tion Secur ity Office rJ2CAJ2EE Connector Architectu re. J2CA i s a framew ork for in tegrating J2EE-compl iant appli cation ser vers with Enterprise Informati on Systems , such as the VHA’s VistA/M sy stems. It is the fra mework for J2EE conn ector modu les that p lug into J 2EE applic ation serv ers, such as the Vis tALink ada pter.J2CAJ 2EE Connec tor Archit ectureJ2CA CCIJ2EE C onnector A rchitectur e Common C lient Inte rfaceJ2EET he Java 2 Platform, Enterprise Edition ( J2EE) is a n environm ent for de veloping a nd deployi ng enterpr ise applic ations. Th e J2EE pla tform cons ists of a set of ser vices, API s, and pro tocols tha t provide the functi onality fo r developi ng multi-t iered, Web -based app lications. A J2EE Co nnector Ar chitecture specifica tion for b uilding ad apters to connect J2 EE systems to non-J2 EE enterpr ise inform ation syst ems.J2SEJa va 2 Stand ard Editio n. Sun Mic rosystem’s programmi ng platfor m based on the Java programmin g language . It is th e blueprin t for buil ding Java applicatio ns, and in cludes the Java Deve lopment Ki t (JDK) an d Java Run time Envir onment (JR E).JAASJav a Authenti cation and Authoriza tion Servi ce. JAAS i s a plugga ble Java f ramework f or user au thenticati on and aut horization , enabling services to authent icate and enforce ac cess contr ols upon u sers. JAR fileJava archive fi le. It is a file for mat based on the ZIP file form at, used t o aggregat e many fil es into on e. Java Li braryA lib rary of Ja va classes usually d istributed in JAR fo rmat.Javad ocJavadoc is a tool for genera ting API d ocumentati on in HTML format fr om doc com ments in s ource code . Document ation prod uced with this tool is typical ly called Javadoc.JB ossJBoss i s a free s oftware / open sourc e Java EE- based appl ication se rver.JDKJa va Develop ment Kit. A set of p rogramming tools for developin g Java app lications. JMXJava Ma nagement e Xtensions. A java sp ecificatio n for buil ding manag eability i nto java a pplication s, includi ng J2EE-ba sed ones.J NDIJava Na ming and D irectory I nterface. A protocol to a set of APIs fo r multiple naming an d director y services .JREThe Ja va Runtime Environme nt consist s of the J ava virtua l machine, the Java platform c ore classe s, and sup porting fi les. JRE i s bundled with the J DK but als o availabl e packaged separatel y.JSPJava Server Pag es. A lang uage for b uilding we b interfac es for int eracting w ith web ap plications . JVMJava Virtual Ma chine. The JVM inter prets comp iled Java binary cod e (byte co de) for sp ecific com puter hard ware.KAAJE EKernel Au thenticati on and Aut horization for Java 2 Enterpri se Edition KernelKern el functio ns as an i ntermediar y between the host M operating system an d VistA M applicatio ns. It con sists of a standard user and p rogram int erface and a set of utilities for perfor ming basic VA comput er system tasks, e.g ., Menu Ma nager, Tas k Manager, Device Ha ndler, and security. KIDSKernel Installat ion and Di stribution System. T he VistA/M module fo r exportin g new Vist A software packages. LDAPAcrony m for Ligh tweight Di rectory Ac cess Proto col. LDAP is an open protocol that permi ts applica tions runn ing on var ious platf orms to ac cess infor mation fro m director ies hosted by any ty pe of serv er. Linke d AdapterV ersion 8.1 of WebLog ic introdu ced a "lin k-ref" mec hanism ena bling the resources of a singl e "base" a dapter to be shared by one or more "link ed" adapte rs. The ba se adapter is a comp letely set up standa lone adapt er. Its re sources (c lasses, ja rs, etc.) can be lin ked to and reused by other res ource adap ters (link ed adapter s), and th e deployer only need s to modif y a subset of linked adapters’ deploymen t descript or setting s.LinuxAn open-sourc e Unix-lik e computer operating system th at runs on various t ypes of ha rdware pla tforms. Li nux is one of the mo st promine nt example s of free software a nd open so urce devel opment; ty pically al l underlyi ng source code can b e freely m odified, u sed, and r edistribut ed. Health eVet-VistA servers u se both Li nux and Wi ndows oper ating syst ems. Liste nerA socke t routine that runs continuous ly at a sp ecified po rt to fiel d incoming requests. It sends requests t o a front controller for proce ssing. The controlle r returns its respon se to the client thr ough the s ame port. The listen er creates a separat e thread f or each re quest, so it can acc ept and fo rward requ ests from multiple c lients con currently. log4J Util ityAn open -source lo gging pack age distri buted unde r the Apac he Softwar e license. Reviewing log files produced at runtime can be he lpful in d ebugging a nd trouble shooting. loggerIn l og4j, a lo gger is a named entr y in a hie rarchy of loggers. T he names i n the hier archy typi cally foll ow Java pa ckage nami ng convent ions. Appl ication co de can sel ect a part icular log ger by nam e to write output to , and admi nistrators can confi gure where a particu lar named logger’s o utput is s ent.M (MUM PS)Massach usetts Gen eral Hospi tal Utilit y Multi-Pr ogramming System, ab breviated M. M is a high-level procedura l programm ing comput er languag e, especia lly helpfu l for mani pulating t extual dat a.Managed ServerA se rver insta nce in a O racle WebL ogic domai n that is not an adm inistratio n server, i.e., not used to co nfigure al l other se rver insta nces in th e domain.M BeansIn th e Java pro gramming l anguage, a n MBean (m anaged bea n) is a Ja va object that repre sents a ma nageable r esource, s uch as an applicatio n, a servi ce, a comp onent, or a device. MBeans mus t be concr ete Java c lasses.Mes sagingA fr amework fo r one appl ication to asynchron ously deli ver data t o another applicatio n, typical ly using a queuing m echanism.M ultipleA V A FileMan data type that allow s more tha n one valu e for a si ngle entry . Namespac e A unique 2-4 chara cter prefi x for each VistA pac kage. The DBA assign s this cha racter str ing for de velopers t o use in n aming a pa ckage’s ro utines, op tions, and other ele ments. The namespace includes a number s pace, a pr e-defined range of n umbers tha t package files must stay with in. NEW PE RSON File #200The NE W PERSON f ile contai ns informa tion for a ll valid u sers on an M system. NISTNatio nal Instit ute for St andards an d Technolo gyOI&TOffi ce of Info rmation & Technology Oracle Web LogicOracl e WebLogic is a J2EE Platform applicatio n server. Oracle has acquired BEA System s, Inc.OSO perating S ystemPatch An update to a VistA software package th at contain s an enhan cement or bug fix. P atches can include c ode update s, documen tation upd ates, and informatio n updates. Patches a re applied to the pr ograms on M systems by IRM ser vices.Plug -inA compo nent that can intera ct with or be added to an appl ication wi thout reco mpiling th e applicat ion.ra.xml ra.xml is the stand ard J2EE d eployment descriptor for J2CA connectors . It descr ibes conne ctor-relat ed attribu tes and it s deployme nt propert ies using a standard DTD (Docu ment Type Definition ) from Sun . Re-authe nticationW hen using a J2CA con nector, th e process of switchi ng the sec urity cont ext of the connector from the original a pplication connector "user" to the actua l end-user . This is done by th e calling applicatio n supplyin g a proper set of us er credent ials.Resou rce Adapte rJ2EE reso urce adapt er modules are syste m-level dr ivers that integrate J2EE appl ication se rvers with Enterpris e Informat ion System s (EIS). T his term i s used int erchangeab ly with re source ada pter and c onnector.R outineA pr ogram or s equence of computer instructio ns that ma y have som e general or frequen t use. M r outines ar e groups o f program lines that are saved , loaded, and called as a sing le unit wi th a speci fic name.R PCRemote P rocedure C all. A def ined call to M code that runs on an M se rver. A cl ient appli cation, th rough the RPC Broker , can make a call to the M ser ver and ex ecute an R PC on the M server. Through th is mechani sm a clien t applicat ion can se nd data to an M serv er, execut e code on an M serve r, or retr ieve data from an M serverRPC BrokerThe RPC Broker is a clie nt/server system wit hin VistA. It establ ishes a co mmon and c onsistent framework for client -server ap plications to commun icate and exchange d ata with V istA/M ser vers.RPC S ecurityAll RPCs are secured wi th an RPC context (a "B"-type option). A n end-user executing an RPC mu st have th e "B"-type option as sociated w ith the RP C in the u ser’s menu tree. Oth erwise an exception is thrown. SADSoftwa re Archite cture Docu mentSE&ISo ftware Eng ineering & Integrati onServletA Java prog ram that r esides on a server a nd execute s requests from clie nt web pag es. Socket An operati ng system object tha t connects applicati on request s to netwo rk protoco ls. SRSSof tware Requ irements S pecificati onTCP/IPTr ansmission Control P rotocol (T CP) and th e Internet Protocol (IP),TXTTe xt file fo rmat VADep artment of Veterans AffairsVAC OVeterans Affairs Ce ntral Offi ceVerify C odeA passw ord used i n tandem w ith the ac cess code to provide secure us er access. The Kerne l’s Sign-o n/Security system us es the ver ify code t o validate the user' s identity .VistAVete rans Healt h Informat ion System s and Tech nology Arc hitecture. The VHA’s portfolio of M-base d applicat ion softwa re used by all VA me dical cent ers and as sociated f acilities. VistALink LibrariesC lasses wri tten speci fically fo r VistALin k.VLVistaL ink is a r untime and developme nt tool pr oviding co nnection a nd data co nversion b etween Jav a and M ap plications in client -server an d n-tier a rchitectur es, to whi ch this do cument des cribes the architect ure and de sign. VMSV irtual Mem ory System . An opera ting syste m, origina lly design ed by DEC (now owned by Hewlet t-Packard) , that ope rates on t he VAX and Alpha arc hitectures . VPIDVA P erson Iden tifier. A new enterp rise-level identifie r uniquely identifyi ng VA ‘per sons’ acro ss the ent ire VA dom ain.WAR fi leWeb arch ive file. Contains t he class f iles for s ervlets an d JSPs.Web Logic Serv erA J2EE a pplication server ma nufactured by Oracle WebLogic Systems. W ebSphereWe bSphere Ap plication Server (WA S) is and IBM applic ation serv er.XLSMicr osoft Offi ce XL work sheet and workbook f ile format XMLExtensi ble Markup LanguageX mlBeansXML Beans is a Java-to-X ML binding framework which is part of th e Apache S oftware Fo undation X ML project .XOB Names paceThe Vi stALink na mespace. A ll VistALi nk program s and thei r elements begin wit h the char acters "XO B."REF: Fo r a compre hensive li st of comm only used infrastruc ture- and security-r elated ter ms and def initions, please vis it the Sec urity and Other Comm on Service s Glossary Web page at the fol lowing Web addressXE "Glossary :ISS Home Page Web A ddress, Gl ossary"
	1446
	1447	XE "ISS:Gl ossary:Hom e Page Web Address, Glossary"
	1448
	1449	XE "Web Pa ges:ISS:Gl ossary Hom e Page Web Address, Glossary"
	1450
	1451	XE "Home P ages:ISS:G lossary Ho me Page We b Address, Glossary"
	1452
	1453	XE "URLs:I SS:Glossar y Home Pag e Web Addr ess, Gloss ary":
	1454	http:// URL /iss/gloss ary.asp
	1455	For a comp rehensive list of ac ronyms, pl ease visit the Secur ity and Ot her Common Services Acronyms W eb site at the follo wing Web a ddressXE " Acronyms ( ISS):Home Page Web A ddress, Gl ossary"
	1456
	1457	XE "ISS:Ac ronyms:Hom e Page Web Address, Glossary"
	1458
	1459	XE "Web Pa ges:ISS:Ac ronyms Hom e Page Web Address, Glossary"
	1460
	1461	XE "Home P ages:ISS:A cronyms Ho me Page We b Address, Glossary"
	1462
	1463	XE "URLs:I SS:Acronym s Home Pag e Web Addr ess, Gloss ary":
	1464	http:// URL /iss/acron yms/index. asp _128 2 0 38439.psd