13. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 7/13/2017 3:41:39 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.

13.1 Files compared

#	Location	File	Last Modified
1	Genisis_v3.zip\Release 3_Docs	Genisis2_VIP_Release 3_Maintenance_Troubleshooting_Guide_06162017.docx	Wed Jun 28 20:38:06 2017 UTC
2	Genisis_v3.zip\Release 3_Docs	Genisis2_VIP_Release 3_Maintenance_Troubleshooting_Guide_06162017.docx	Wed Jul 12 21:40:38 2017 UTC

13.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	1	156
Changed	0	0
Inserted	0	0
Removed	0	0

13.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

13.4 Active regular expressions

No regular expressions were active.

13.5 Comparison detail

	1	Maintenanc e & Troubl eshooting Guide
	2	Genomic In formation System for Integrate d Science 2
	3	(Genisis2) Technical Services
	4	Release 3
	5
	6	June 2017
	7	Document V ersion 3.0
	8	Department of Vetera ns Affairs
	9
	10	Document R evision Hi story
	11	Date
	12	Revision
	13	Descriptio n
	14	Author
	15	02/10/2017
	16	1.0
	17	Release 1
	18	Booz Allen Hamilton
	19	05/12/2017
	20	2.0
	21	Release 2
	22	Booz Allen Hamilton
	23	06/16/2017
	24	3.0
	25	Release 3
	26	Booz Allen Hamilton
	27
	28	Table of C ontents
	29	1.Introduc tion1
	30	2.Maintena nce Guide1
	31	2.1.Techni cal Manual 1
	32	2.2.Develo pers Guide 1
	33	2.3.Deploy ment Guide 1
	34	3.Troubles hooting Gu ide2
	35	3.1.Sympto ms, Causes , and Fixe s2
	36
	37	Introducti on
	38	This docum ent provid es Genomic Informati on System for Integr ated Scien ce 2 (Geni sis2) deve lopers wit h relevant informati on for und erstanding how the a pplication is struct ured and h ow to main tain it. I n addition , it provi des inform ation rega rding othe r document ation that details t echnical a spects of the applic ation. The Troublesh ooting Gui de section specifies common sy mptoms ide ntified wh en using t he applica tion, some of the ca uses for t hese sympt oms, and l ikely fixe s for them . This sec tion can b e utilized by Genisi s2 users t o troubles hoot the a pplication based on abnormal b ehavior th ey might e xperience when they login to p erform tas ks.
	39	The intend ed audienc e for this document are the In formation Technology (IT) team s responsi ble for de veloping n ew code or maintaini ng the exi sting code base betw een releas es or in a pplication sustainme nt.
	40
	41	Maintenanc e Guide
	42	Technical Manual
	43	The Genisi s2 Technic al Manual provides a high-leve l overview of the sy stem archi tecture. I t also pro vides info rmation on the vario us compone nts used i n the web, applicati on, and th e database servers; and how th ey communi cate with each other ; as well as informa tion about the Authe ntication and Author ization co mponents o f the appl ication. T he Genisis 2 API Manu al is a pa rt of the Genisis2 T echnical M anual, but it is a s eparate do cument. It describes the Appli cation Pro gramming I nterface ( API) that the backen d applicat ion server exposes t o the Web server and the User Interface part of th e applicat ion. This API can al so be used by other internal V A systems to interac t directly with the backend ap plication engine wit hout going through t he web use r interfac e.
	44
	45	Developer s Guide
	46	The Genisi s2 Develop ers Guide provides s ystematic instructio ns for dev elopers to install a nd configu re Genisis 2 developm ent enviro nment soft ware. Once the setup is comple te, the de veloper ca n develop new code o r maintain the exist ing system .
	47
	48	Deploymen t Guide
	49	The Genisi s2 Deploym ent Guide provides i nstruction s for deve lopers to prepare th e environm ents (i.e. , DEV, TES T, SQA/UAT , PRE-PROD , and PROD ) and enab le them to receive G enisis2 co mponents ( such as We b, Applica tion and D atabase se rvers), an d deploy t hem. It al so details the Jenki ns/Continu ous Integr ation (CI) environme nt setup f or buildin g software for deplo yment.
	50
	51	Troublesho oting Guid e
	52	Symptoms, Causes, a nd Fixes
	53	The follow ing table outlines t he symptom s, causes, and fixes experienc ed with Re lease 3.
	54	Symptom
	55	Cause
	56	Likely Fix es
	57	Login page is up but users not able to l og in.
	58	Could be a breakdown in one or more of t he compone nts that a re trying to communi cate with each other .
	59	1.Ensure t hat the Ap ache and W ildfly ser vers are u p and runn ing.
	60	2.Ensure t hat correc t configur ation file s are pres ent in eac h server a nd are poi nting to c orrect end points.
	61	3.Ensure t hat firewa ll ports a re open an d servers can commun icate with each othe r.
	62	4.Ensure t hat the SQ L server i s up and r unning and correct a ccess cred entials ar e present (edited).
	63	5.Ensure t hat the SQ L server u ser has ad equate dat abase perm issions fo r CRUD ope rations.
	64	Strange er rors appea r that mix up Logins .
	65	Credential s stored i n the Cach e or the b rowser rem embering s ettings fr om a previ ous sessio n.
	66	Clear the cache in t he browser . Close th e browser, reopen th e browser, and log i n.
	67	During Tab le Copy, r eceiving a “Wrong Ta ble Name” error.
	68	Wrong tabl e names, t ranspositi on errors, or errors while spe lling the name(s) ou t.
	69	While copy ing a tabl e from a s ource data base to a destinatio n database , ensure t hat the ta ble name i s correct, then try copying th e table ag ain.
	70	During Tab le Copy, r eceiving a “Wrong So urce Schem a” error.
	71	Table name s are iden tified by a combinat ion of Sou rce Schema Name and Table Name expressed as “Schem aName.Tabl eName”. Fo r example, StudyMart 1.LipidPro files tabl e is diffe rent from StudyMart2 .LipidProf iles even though the Table Nam es (LipidP rofiles) a re the sam e.
	72	While copy ing a tabl e from a s ource data base to a destinatio n database , ensure t hat the So urce Schem a name is also corre ct in the Source dat abase. The n try copy ing the ta ble again.
	73	During Tab le Copy re ceiving a “Source Da tabase Not Reachable ” error.
	74	For variou s networki ng and com puting env ironment r easons, so metimes th e Source D atabase se rver may n ot be reac hable by t he server that runs the Table Copy funct ion.
	75	Check with the Syste ms Adminis trator on why the So urce Datab ase server is not re achable by the serve r running the Table Copy funct ion.
	76	During Tab le Copy re ceiving a “Destinati on Databas e Not Reac hable” err or.
	77	For variou s networki ng and com puting env ironment r easons, so metimes th e Destinat ion Databa se server may not be reachable by the se rver that runs the T able Copy function
	78	Check with the Syste ms Adminis trator on why the De stination Database s erver is n ot reachab le by the server run ning the T able Copy function.