Produced by Araxis Merge on 6/23/2017 11:56:35 AM 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.
| # | Location | File | Last Modified |
|---|---|---|---|
| 1 | OSCIF_CTT_v4_build 1 code..zip\aitc_install | CTT_DM_Installation_Guide.docx | Wed May 31 03:59:22 2017 UTC |
| 2 | OSCIF_CTT_v4_build 1 code.zip\aitc_install | CTT_DM_Installation_Guide.docx | Fri Jun 23 02:40:17 2017 UTC |
| Description | Between Files 1 and 2 |
|
|---|---|---|
| Text Blocks | Lines | |
| Unchanged | 37 | 1152 |
| Changed | 36 | 94 |
| Inserted | 0 | 0 |
| Removed | 0 | 0 |
| 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 |
No regular expressions were active.
| 1 | Collaborat ive Termin ology Tool ing & Data Managemen t (CTT & D M) | |
| 2 | Tooling an d Server D evelopment | |
| 3 | Deployment and Insta llation Gu ide | |
| 4 | ||
| 5 | November 2 016 | |
| 6 | Department of Vetera ns Affairs | |
| 7 | Office of Informatio n and Tech nology (OI &T) | |
| 8 | ||
| 9 | ||
| 10 | Revision H istory | |
| 11 | Date | |
| 12 | Version | |
| 13 | Descriptio n | |
| 14 | Author | |
| 15 | ||
| 16 | 1.0 | |
| 17 | Delivery t o VA | |
| 18 | ManTech Mi ssion Solu tions & Se rvices | |
| 19 | 10/31/2016 | |
| 20 | 0.3 | |
| 21 | Updated Do cument to Address TW Comments | |
| 22 | PII , ManTech Mission So lutions & Services | |
| 23 | 10/28/2016 | |
| 24 | 0.2 | |
| 25 | Technical Writer Rev iew – Draf t Edits | |
| 26 | PII , ManTech Mission So lutions & Services | |
| 27 | 10/27/2016 | |
| 28 | 0.1 | |
| 29 | Initial Dr aft | |
| 30 | PII , ManTech Mission So lutions & Services | |
| 31 | ||
| 32 | ||
| 33 | Table of C ontents | |
| 34 | 1Introduct ion1 | |
| 35 | 1.1Purpose 1 | |
| 36 | 1.2Depende ncies1 | |
| 37 | 1.3Constra ints2 | |
| 38 | 1.4Roles a nd Respons ibilities2 | |
| 39 | 2Deploymen t3 | |
| 40 | 2.1Timelin e3 | |
| 41 | 2.2Site Re adiness As sessment3 | |
| 42 | 2.2.1Deplo yment Topo logy (Targ eted Archi tecture)4 | |
| 43 | 2.2.2Site Preparatio n5 | |
| 44 | 2.3Resourc es5 | |
| 45 | 2.3.1Facil ity Specif ics5 | |
| 46 | 2.3.2Hardw are5 | |
| 47 | 2.3.3Softw are5 | |
| 48 | 2.3.4Commu nications6 | |
| 49 | 3Installat ion6 | |
| 50 | 3.1Pre-ins tallation and System Requireme nts6 | |
| 51 | 3.2Platfor m Installa tion and P reparation 6 | |
| 52 | 3.3Downloa d and Extr act Files6 | |
| 53 | 3.4Databas e Creation 6 | |
| 54 | 3.5Install ation Scri pts6 | |
| 55 | 3.6Cron Sc ripts6 | |
| 56 | 3.7Access Requiremen ts and Ski lls Needed for the I nstallatio n7 | |
| 57 | 3.8Install ation Proc edure7 | |
| 58 | 3.8.1JAVA7 | |
| 59 | 3.8.2SSL C ertsToJDK7 | |
| 60 | 3.8.3CSR a nd Certifi cate8 | |
| 61 | 3.8.4TOMCA T9 | |
| 62 | 3.8.5GitBl it10 | |
| 63 | 3.8.6Prism e11 | |
| 64 | 3.8.7Jenki ns11 | |
| 65 | 3.8.8Maven 12 | |
| 66 | 3.8.9Nexus 12 | |
| 67 | 3.8.10Kome t13 | |
| 68 | 3.8.11Sing le Sign On – Interna l15 | |
| 69 | 3.9Install ation Veri fication P rocedure16 | |
| 70 | 3.10System Configura tion16 | |
| 71 | 3.11Databa se Tuning1 7 | |
| 72 | 4Back-Out Procedure1 7 | |
| 73 | 4.1Back-Ou t Strategy 17 | |
| 74 | 4.2Back-Ou t Consider ations17 | |
| 75 | 4.2.1Load Testing17 | |
| 76 | 4.2.2User Acceptance Testing17 | |
| 77 | 4.3Back-Ou t Criteria 17 | |
| 78 | 4.4Back-Ou t Risks17 | |
| 79 | 4.5Authori ty for Bac k-Out17 | |
| 80 | 4.6Back-Ou t Procedur e17 | |
| 81 | 4.7Back-ou t Verifica tion Proce dure18 | |
| 82 | 5Rollback Procedure1 8 | |
| 83 | 5.1Rollbac k Consider ations18 | |
| 84 | 5.2Rollbac k Criteria 18 | |
| 85 | 5.3Rollbac k Risks18 | |
| 86 | 5.4Authori ty for Rol lback18 | |
| 87 | 5.5Rollbac k Procedur e18 | |
| 88 | 5.6Rollbac k Verifica tion Proce dure18 | |
| 89 | ||
| 90 | ||
| 91 | ||
| 92 | ||
| 93 | Introducti on | |
| 94 | This docum ent descri bes how to deploy an d install the CTT & DM system as well as how to ba ck-out the product a nd rollbac k to a pre vious vers ion or dat a set. Thi s document is a comp anion to t he project charter a nd managem ent plan f or this ef fort. The scope of t he ETS pro ject is to develop n ew product that prov ides the c apability to create and edit V HAT and ot her termin ology map sets for c onsumption by other VA service s. The tec hnology st ack provid es the cap ability to : | |
| 95 | Develop an integrate d web-acce ssible Ter minology M anagement Platform ( TMP) that supports t erminology developme nt, mainte nance, and distribut ion across VA. The p latform wi ll be buil t on exist ing open s ource tool s and fram eworks suc h as the I nternation al Health Terminolog y Standard s Developm ent Organi zation (IH TSDO) work bench and Informatic s Architec ture Accel eration (I SAAC) edit or. | |
| 96 | Deploy the TMP (ETS tooling an d server s olution) i n various environmen ts includi ng product ion and pr e-producti on. | |
| 97 | Provide op erations a nd mainten ance suppo rt for TMP developme nt and dep loyment. | |
| 98 | Provide su pport for production operation s, product ion perfor mance impr ovements, and portal framework . | |
| 99 | Create and deploy pa tches to V istA syste ms to inte grate auth oritative terminolog y content into VistA in a nati ve format. | |
| 100 | Enable com putability of VA hea lth and be nefits ser vices clin ical data through se mantic int eroperabil ity to exc hange clin ical data between VA (VHA, VBA , NCA), Do D, and app roved non- VA entitie s. (Clinic al data wi ll be nati vely coded and mappe d to natio nal standa rds and te rminologie s.) | |
| 101 | Purpose | |
| 102 | The purpos e of this plan is to provide a single, c ommon docu ment descr ibing how, when, whe re, and to whom the CTT & DM s ystem will be deploy ed and ins talled as well as ho w it is to be backed out and r olled back if necess ary. The p lan also i dentifies the resour ces, commu nications plan, and rollout sc hedule. Sp ecific ins tructions for instal lation, ba ck-out, an d rollback are inclu ded in thi s document . | |
| 103 | Dependenci es | |
| 104 | The CTT&DM tool requ ires a ser ies of ope n source t echnologie s to run u nderneath it. These technologi es are: To mcat, Apac he Webserv er, SSL, J enkins, Gi tBlit, Nex us and Mav en. | |
| 105 | An assigne d Systems Administra tor will i nstall the required software. PRISME and KOMET may be instal led after the requir ed softwar e installa tion is co mplete. | |
| 106 | This docum ent is par t of the d eliverable s package. | |
| 107 | Constraint s | |
| 108 | Servers in Pre Prod and Prod a t AITC hav e the foll owing conf iguration: | |
| 109 | 16GB of RA M | |
| 110 | 64GB x 1 HD1– OS | |
| 111 | 472GB x 1 HD2 - dat a | |
| 112 | 4 x CPUs | |
| 113 | Roles and Responsibi lities | |
| 114 | The list b elow ident ifies the individual s responsi ble for th e system’s deploymen t, configu ration, an d administ ration. | |
| 115 | Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les | |
| 116 | Name | |
| 117 | Team | |
| 118 | Role | |
| 119 | Esigie Agu ele | |
| 120 | ManTech | |
| 121 | Program Ma nager | |
| 122 | PII | |
| 123 | ManTech | |
| 124 | Lead Engin eer/Develo per | |
| 125 | PII | |
| 126 | ManTech | |
| 127 | Sr. System s Administ rator | |
| 128 | PII | |
| 129 | VA Team | |
| 130 | Project Ma nager | |
| 131 | PII | |
| 132 | VA Team | |
| 133 | Sr. System s Administ rator | |
| 134 | The list b elow ident ifies spec ific respo nsibilitie s of each team membe r. | |
| 135 | Table 2: D eployment, Installat ion, Back- out, and R ollback Re sponsibili ties | |
| 136 | ID | |
| 137 | Team | |
| 138 | Phase / Ro le | |
| 139 | Tasks | |
| 140 | Project Ph ase (See S chedule) | |
| 141 | ||
| 142 | PII (ManTech) and PII (VA Team) | |
| 143 | Deployment | |
| 144 | Plan and s chedule de ployment ( including orchestrat ion with v endors) | |
| 145 | ||
| 146 | ||
| 147 | PII (ManTech) and PII (VA Team) | |
| 148 | Deployment | |
| 149 | Determine and docume nt the rol es and res ponsibilit ies of tho se involve d in the d eployment. | |
| 150 | ||
| 151 | ||
| 152 | PII (ManTech) and PII (VA Team) | |
| 153 | Deployment | |
| 154 | Deploy and configure procedure and provi de install ation pack age. | |
| 155 | ||
| 156 | ||
| 157 | PII (ManTech) | |
| 158 | ||
| 159 | Oversee an d assist d uring the installati on in pre- prod and p rod. | |
| 160 | ||
| 161 | ||
| 162 | PII (ManTech) and PII (VA Team) | |
| 163 | Deployment | |
| 164 | Test for o perational readiness | |
| 165 | ||
| 166 | ||
| 167 | PII (VA Team) | |
| 168 | Deployment | |
| 169 | Execute de ployment | |
| 170 | ||
| 171 | ||
| 172 | PII (VA Team) | |
| 173 | Installati on | |
| 174 | Plan and s chedule in stallation | |
| 175 | ||
| 176 | ||
| 177 | PII (VA Team) | |
| 178 | Installati on | |
| 179 | Ensure aut hority to operate an d that cer tificate a uthority s ecurity do cumentatio n is in pl ace | |
| 180 | ||
| 181 | ||
| 182 | PII (VA Team) | |
| 183 | Installati on | |
| 184 | Validate t hrough fac ility POC to ensure that IT eq uipment ha s been acc epted usin g asset in ventory pr ocesses | |
| 185 | ||
| 186 | ||
| 187 | PII (VA Team) | |
| 188 | Installati ons | |
| 189 | Coordinate training | |
| 190 | ||
| 191 | ||
| 192 | N/A | |
| 193 | Back-out | |
| 194 | Confirm av ailability of back-o ut instruc tions and back-out s trategy (w hat are th e criteria that trig ger a back -out) | |
| 195 | ||
| 196 | ||
| 197 | PII (VA Team) | |
| 198 | Post Deplo yment | |
| 199 | Hardware, Software a nd System Support | |
| 200 | ||
| 201 | Once the a pproval pr ocess and certificat ions are c omplete, t he Project and Progr am Manager s will ind icate the starting d eployment time. | |
| 202 | Deployment | |
| 203 | This appli cation dep loyment is dependent on a seri es of open source se rvices/pac kages that must be i nstalled, configured and runni ng. | |
| 204 | We detaile d this pro cess below in sectio n 3.8. | |
| 205 | Timeline | |
| 206 | TBD | |
| 207 | Site Readi ness Asses sment | |
| 208 | The applic ation will be deploy ed on serv ers hosted at the AI TC Datacen ter in the pre-produ ction and production environme nts. | |
| 209 | The applic ations wil l be insta lled acros s multiple servers i n these tw o environm ents. | |
| 210 | The new ap plication is Collabo rative Ter minology T ooling and Data Mana gement sof tware. | |
| 211 | The applic ation will be instal led and de ployed on the follow ing server in AITC.T he server list below : | |
| 212 | DNS | |
| 213 | DNS | |
| 214 | DNS | |
| 215 | DNS | |
| 216 | DNS | |
| 217 | DNS | |
| 218 | DNS | |
| 219 | DNS | |
| 220 | DNS | |
| 221 | DNS | |
| 222 | Deployment Topology (Targeted Architectu re) | |
| 223 | ||
| 224 | Figure 1: Deployment Topology | |
| 225 | ||
| 226 | The deploy ment locat ion is pre -productio n and prod uction ser vers at AI TC | |
| 227 | Site Prepa ration | |
| 228 | N/A | |
| 229 | Resources | |
| 230 | Facility S pecifics | |
| 231 | N/A | |
| 232 | Hardware | |
| 233 | The follow ing table describes hardware s pecificati ons requir ed at each site prio r to deplo yment. | |
| 234 | Table 3: H ardware sp ecificatio ns | |
| 235 | Required H ardware | |
| 236 | Model | |
| 237 | Version | |
| 238 | Configurat ion | |
| 239 | Manufactur er | |
| 240 | Other | |
| 241 | Server | |
| 242 | ||
| 243 | CentOS6.8 | |
| 244 | 16GB RAM, 1x HD 64GB and 1 x H D 472GB, 4 x CPUs | |
| 245 | ||
| 246 | ||
| 247 | Server | |
| 248 | ||
| 249 | CentOS6.8 | |
| 250 | 16GB RAM, 1x HD 64GB and 1 x H D 2100GB, 4 x CPUs | |
| 251 | ||
| 252 | ||
| 253 | Please see the Roles and Respo nsibilitie s table in Section 1 .4 for det ails about who is re sponsible for prepar ing the si te to meet these har dware spec ifications . | |
| 254 | The hardwa re has alr eady been procured a nd running on the ne twork. | |
| 255 | Software | |
| 256 | The follow ing table describes software s pecificati ons requir ed at each site prio r to deplo yment. | |
| 257 | Table 4: S oftware sp ecificatio ns | |
| 258 | Required S oftware | |
| 259 | Make | |
| 260 | Version | |
| 261 | Configurat ion | |
| 262 | Manufactur er | |
| 263 | Other | |
| 264 | Tomcat | |
| 265 | Apache | |
| 266 | 8.0.33 | |
| 267 | ||
| 268 | ||
| 269 | ||
| 270 | WebServer | |
| 271 | Apache | |
| 272 | 2.2.15 | |
| 273 | ||
| 274 | ||
| 275 | ||
| 276 | JDK | |
| 277 | Oracle | |
| 278 | 8.9.1 | |
| 279 | ||
| 280 | ||
| 281 | ||
| 282 | Gitblit | |
| 283 | ||
| 284 | ||
| 285 | ||
| 286 | ||
| 287 | ||
| 288 | Jenkins | |
| 289 | Hudson | |
| 290 | 2.19.1 | |
| 291 | ||
| 292 | ||
| 293 | ||
| 294 | Maven | |
| 295 | Apache | |
| 296 | 3.3.9 | |
| 297 | ||
| 298 | ||
| 299 | ||
| 300 | Nexus | |
| 301 | Sonatype | |
| 302 | 2.14.0 | |
| 303 | ||
| 304 | ||
| 305 | ||
| 306 | SSL Certs | |
| 307 | VA Provide r | |
| 308 | ||
| 309 | ||
| 310 | ||
| 311 | ||
| 312 | Please see the Roles and Respo nsibilitie s table in Section 1 .4 above f or details about who is respon sible for preparing the site t o meet the se softwar e specific ations. | |
| 313 | Communicat ions | |
| 314 | For inquir ies relate d to deplo yment, con figuration , manageme nt, and er ror handli ng of thes e applicat ions, cont act PII at PII and/or PII PII | |
| 315 | Deployment /Installat ion/Back-O ut Checkli st | |
| 316 | N/A | |
| 317 | Installati on | |
| 318 | Pre-instal lation and System Re quirements | |
| 319 | All the ha rdware is in place a t AITC and ready to receive th e installa tion. | |
| 320 | Platform I nstallatio n and Prep aration | |
| 321 | All the ha rdware is in place a t AITC and ready to receive th e installa tion. | |
| 322 | Download a nd Extract Files | |
| 323 | Our deploy ment packa ge include s all nece ssary soft ware. | |
| 324 | Database C reation | |
| 325 | The Oracle databases and accou nts have a lready bee n created and are re ady for us e. | |
| 326 | Installati on Scripts | |
| 327 | See sectio n 4.8 for details. | |
| 328 | Cron Scrip ts | |
| 329 | N/A | |
| 330 | Access Req uirements and Skills Needed fo r the Inst allation | |
| 331 | The System s Administ rator exec uting the deployment will have elevated access to each syste m in pre-p roduction and produc tion syste ms. | |
| 332 | Installati on Procedu re | |
| 333 | Use this d ocument to install a nd configu re the fol lowing ser vices: | |
| 334 | Java | |
| 335 | SSL Certif icate | |
| 336 | Tomcat Ser ver | |
| 337 | GitBlit | |
| 338 | Maven | |
| 339 | Jenkins | |
| 340 | Nexus | |
| 341 | Prisme | |
| 342 | Komet | |
| 343 | Single Sig n On | |
| 344 | The provid ed serverS etup.zip f ile contai ns a “cert ” director y with all of the In ternal, In termediate and Root SSL Certif icates. | |
| 345 | There is a lso an “in stallers” directory where you can find J ava, Tomca t, Maven, GitBlit an d other sc ripts that will help during th e installa tion proce ss. | |
| 346 | JAVA | |
| 347 | From the r oot direct ory “ / ” unzip the provided s erverSetup .tar.gz fi le contain ing the Ja va RPM, se t the appr opriate pe rmissions and instal l it. | |
| 348 | Assuming t hat the se rverSetup. tar.gz fil e has been placed in servers / tmp direct ory. | |
| 349 | cd / | |
| 350 | tar –zxvf /tmp/serve rSetup.tar .gz | |
| 351 | As root ru n the foll owing: | |
| 352 | /app/insta llers/inst alljava.sh | |
| 353 | SSL CertsT oJDK | |
| 354 | This will install th e CA Root and Interm ediate Cer tificates to the JDK version j ust instal led in the previous step. | |
| 355 | As root ru n the foll owing: | |
| 356 | /app/insta llers/inst allsslcert .sh | |
| 357 | You will b e asked th e followin g question three tim es, one fo r each cer tificate: | |
| 358 | “Trust thi s certific ate?” | |
| 359 | Respond “y es” | |
| 360 | CSR and Ce rtificate | |
| 361 | This step requires t he use of keytool an d openssl to generat e the CSR and the ce rtificate chain requ ired for S SL to be p roperly se t up. | |
| 362 | -Generate a CSR (Cer tificate S igning Req uest) | |
| 363 | Update the CN (Commo n Name, wh ich is the Fully Qua lified Ser ver Name) to have th e right ho stname. | |
| 364 | cd /app/ce rts/ | |
| 365 | openssl re q -new -ne wkey rsa: PORT -nodes -ke yout serve r.key -out server.cs r -subj "/ C=US/ST= T X/L=Austin /O=VA/OU=S TS/CN= DNS /emailAddr ess= PII " | |
| 366 | View the C SR | |
| 367 | The openss l tool wil l allow us to view t he content s of the C SR. | |
| 368 | Once Gener ated, the contents o f the CSR should loo k like the following : | |
| 369 | openssl re q -text -n oout -veri fy -in ser ver.csr | |
| 370 | verify OK | |
| 371 | Certificat e Request: | |
| 372 | Data: | |
| 373 | Version: 0 (0x0) | |
| 374 | Subject: C =US, ST=TX , L=Austin , O=VA, OU =STS, CN= DNS /emailAddr ess= PII | |
| 375 | Subject Pu blic Key I nfo: | |
| 376 | Public Key Algorithm : rsaEncry ption | |
| 377 | Public-Key : (2048 bi t) | |
| 378 | CSR Submis sion | |
| 379 | Please sub mit the CS R server.k ey via the following URLs: | |
| 380 | http://URL | |
| 381 | https://UR L.DNS | |
| 382 | Create Cer tificate C hain | |
| 383 | When fulfi lled, put the certif icate into a server. crt file. | |
| 384 | ensure tha t your .cr t file sta rts with | |
| 385 | -----BEGIN CERTIFICA TE----- | |
| 386 | and ends w ith | |
| 387 | -----END C ERTIFICATE ----- | |
| 388 | Now we exp ort the ce rtificate from the s erver.crt file you r ecently cr eated and the keysto re file th at was use d to gener ate the CS R server.k ey into a new pkcs12 file call ed server. p12 togeth er with th e VA’s Int ernal Cert ficate nam ed VA-Inte rnal-E5-IC A1-v1.crt | |
| 389 | openssl pk cs12 -expo rt -in ser ver.crt -i nkey serve r.key -out server.p1 2 -name to mcat -CAfi le VA-Inte rnal-E5-IC A1-v1.crt -caname ro ot | |
| 390 | (password - tomcat) | |
| 391 | Then we im port the s erver.p12 file into a new keys tore file called ser ver.keysto re | |
| 392 | This serve r.keystore file will be used t o configur e apache a nd tomcat to support SSL. | |
| 393 | keytool -i mportkeyst ore -dests torepass t omcat -des tkeystore server.key store -src keystore s erver.p12 -srcstoret ype PKCS12 -srcstore pass tomca t -alias t omcat | |
| 394 | Place the server.key store file in the “/ app/certs” directory and set t he appropr iate permi ssions. | |
| 395 | sudo chown root /app /certs/ser ver.keysto re | |
| 396 | sudo chmod 700 /app/ certs/serv er.keystor e | |
| 397 | To view th e contents of the ke ystore fil e: keytool –list –v –keystore server.key store | |
| 398 | TOMCAT | |
| 399 | From the r oot direct ory “/app“ unzip the provided tomcat fil e as part of the ori ginal serv erSetup.zi p file. Be come root on the ser ver, unzip the tomca t file and run the “ finishTomc atSetup.sh ” script t o install and config ure tomcat . | |
| 400 | sudo su - | |
| 401 | cd /app | |
| 402 | yum –y ins tall unzip | |
| 403 | unzip inst allers/apa che-tomcat -8.0.33.zi p | |
| 404 | ./installe rs/finishT omcatSetup .sh | |
| 405 | Configure SSL in Tom cat | |
| 406 | Verify tha t the PORT connector for SSL i s in place . | |
| 407 | in the fil e /app/apa che-tomcat -8.0.33/co nf/server. xml” | |
| 408 | <Connector port=" PORT " protocol ="org.apac he.coyote. http11.Htt p11NioProt ocol" | |
| 409 | maxThreads ="150" SSL Enabled="t rue" schem e="https" secure="tr ue" | |
| 410 | clientAuth ="false" s slProtocol ="TLS" | |
| 411 | keyst oreFile="/ app/certs/ server.key store" key storePass= "tomcat" | |
| 412 | maxPo stSize="20 9715200"/> | |
| 413 | <!-- Defin e an AJP 1 .3 Connect or on port PORT --> | |
| 414 | <Connector port=" PORT " protocol ="AJP/1.3" redirectP ort=" PORT " /> | |
| 415 | GitBlit | |
| 416 | Deploy and Configure | |
| 417 | Run /app/i nstaller/i nstallgit. sh to crea te the dir ectory and set up pr oper owner ship. It w ill also d eploy the applicatio n in Tomca t | |
| 418 | Define new Git data directory in context .xml | |
| 419 | edit /app/ apache-tom cat-8.0.33 /conf/cont ext.xml - add: (towa rds end of file insi de the Con text tags) | |
| 420 | <Environme nt name="b aseFolder" type="jav a.lang.Str ing" value ="/app/git Data" over ride="fals e" /> | |
| 421 | Install To mcat’s sta rtup scrip t | |
| 422 | cp /app/et c/init.d/t omcat” to “/etc/init .d/” | |
| 423 | The server running T omcat must be able t o run it w ith an Xmx of 14GB | |
| 424 | This can b e tuned in /etc/init .d/tomcat | |
| 425 | Bring up T omcat | |
| 426 | /etc/init. d/tomcat s tart | |
| 427 | Tail the l ogs to che ck Tomcat coming up and to spo t any poss ible issue s | |
| 428 | tail –f /a pp/apache- tomcat-8.0 .33/logs/c atalina.ou t | |
| 429 | Finally, | |
| 430 | Edit /app/ gitData/de faults.pro perties – add the fo llowing at the end o f the file : | |
| 431 | web.enable RpcServlet =true | |
| 432 | web.enable RpcManagem ent=true | |
| 433 | web.enable RpcAdminis tration=tr ue | |
| 434 | Restart To mcat /etc/ init.d/tom cat restar t | |
| 435 | Login to g itblit wit h admin/ad min - crea te a new a ccount and delete de fault acco unt | |
| 436 | Replace th e “ServerN ame” with the actual fully qua lified hos tname. | |
| 437 | https://DN S/PORT | |
| 438 | Remember t he new adm in account you creat ed (for la ter config uration) | |
| 439 | Create the following Repositor ies: | |
| 440 | With Acces s Policy: “Restrict Push (Name d) | |
| 441 | contentCon figuration s | |
| 442 | editChange sets | |
| 443 | Prisme | |
| 444 | Deploy and Configure | |
| 445 | Execute th e followin g: | |
| 446 | /app/insta llers/inst allprisme. sh | |
| 447 | cd /app/pr ismeData | |
| 448 | make sure the server _config.ym l and orac le_databas e.yml file s are pres ent. | |
| 449 | Rename the file acco rdingly: | |
| 450 | PreProd | |
| 451 | mv /app/pr ismeData/o racle_data base.yml-P RE/app/pri smeData/or acle_datab ase.yml | |
| 452 | mv /app/pr ismeData/s erver_conf ig.yml-PRE /app/pris meData/ser ver_config .ymlmv /ap p/prismeDa ta/oracle_ database.y ml-PROD /a pp/prismeD ata/oracle _database. yml | |
| 453 | mv /app/pr ismeData/s erver_conf ig.yml-PRO D /app/pri smeData/se rver_confi g.yml | |
| 454 | Start Tomc at | |
| 455 | sudo /etc/ init.d/tom cat start | |
| 456 | Jenkins | |
| 457 | Install an d Configur e | |
| 458 | We are goi ng to inst all the Je nkins repo first and install t he RPM via yum. | |
| 459 | As Root ru n the foll owing: | |
| 460 | /app/insta llers/inst alljenkins .sh | |
| 461 | If a ssh k ey is need ed, this i s the manu al process of genera ting one. | |
| 462 | ########## ########## ######## | |
| 463 | # sudo -u jenkins ss h-keygen | |
| 464 | That will generate t he key for you here: | |
| 465 | /var/lib/ jenkins/.s sh/id_rsa. pub | |
| 466 | ########## ########## ########## | |
| 467 | /etc/init. d/Jenkins start | |
| 468 | Replace th e “ServerN ame” with the actual fully qua lified hos tname. | |
| 469 | Go to http s://Server Name:8080/ jenkins | |
| 470 | Log In wit h the foll owing cred entials de vtest/devt esthardtog uess | |
| 471 | Go to Conf igure / l ook for Je nkins Loca tion and c hange the Jenkins UR L to : | |
| 472 | https://DN S:PORT | |
| 473 | Replace th e “ServerN ame” with the actual fully qua lified hos tname. | |
| 474 | Click Appl y and Save | |
| 475 | Maven | |
| 476 | Install an d Configur e | |
| 477 | Maven must be instal led on the same serv er as Jenk ins. | |
| 478 | Become roo t on the s erver, and run the f ollowing: | |
| 479 | /app/insta llers/inst allmaven.s h | |
| 480 | Edit /app/ jenkinsMav enSettings .xml file and add th e serverna me and cre dentials f or nexus. | |
| 481 | Nexus | |
| 482 | Install an d Configur e | |
| 483 | As Root r un the fol lowing: | |
| 484 | /app/insta llers/inst allnexus.s h | |
| 485 | Add the fo llowing in to “/app/n exus-2.14. 0-01/bin/j sw/conf/wr apper.conf ” | |
| 486 | vi /app/ne xus-2.14.0 -01/bin/js w/conf/wra pper.conf | |
| 487 | wrapper.ap p.paramete r.3=./conf /jetty-htt ps.xml | |
| 488 | wrapper.ap p.paramete r.4=./conf /jetty-htt p-redirect -to-https. xml | |
| 489 | To set up SSL, use t he existin g keystore “server.k eystore” b ut rename it accordi ngly and s et ownersh ip. | |
| 490 | cp /app/ce rts/server .keystore /app/certs /nexus.key store | |
| 491 | chown nexu s /app/cer ts/nexus.k eystore | |
| 492 | chgrp nexu s /app/cer ts/nexus.k eystore | |
| 493 | Set the SS L port in “/app/nexu s-2.14.0-0 1/conf/nex us.propert ies” | |
| 494 | vi /app/ne xus-2.14.0 -01/conf/n exus.prope rties | |
| 495 | applicatio n-port-ssl =8443 | |
| 496 | Configure “jetty-htt ps.xml” to specify k eystore | |
| 497 | change /ap p/nexus-2. 13.0-01/co nf/jetty-h ttps.xml t o like thi s: | |
| 498 | <Set name= "keyStore" >/app/cert s/nexus.ke ystore</Se t> | |
| 499 | <Set name= "trustStor e">/app/ce rts/nexus. keystore</ Set> | |
| 500 | <Set name= "keyStoreP assword">t omcat</Set > | |
| 501 | <Set name= "keyManage rPassword" >tomcat</S et> | |
| 502 | <Set name= "trustStor ePassword" >tomcat</S et> | |
| 503 | Start Nexu s, log in and config ure via th e GUI. | |
| 504 | /etc/init. d/nexus st art | |
| 505 | Go to http s://YourSe rverName: PORT /nexus/ | |
| 506 | login (adm in/admin12 3), update permissio ns, disabl e unneeded repositor ies | |
| 507 | Create "te rmdata" re lease repo | |
| 508 | disable ap ache snaps hots, disa ble / dele te 3rd par ty, disabl e m1 shado w | |
| 509 | update 'pu blic' grou p to match repos | |
| 510 | Komet | |
| 511 | Komet is i nstalled 1 00% via th e Prisme U I. | |
| 512 | Log in to prisme htt p://YourHo stName: PORT / | |
| 513 | Once in, C lick on “A pp Deploye r” | |
| 514 | Select the applicati on type “K omet Tooli ng Deploym ent” and c lick “Next ” | |
| 515 | ||
| 516 | Figure 2: Applicatio n Deployer Applicati on Type Sc reen | |
| 517 | Then, sele ct the app lication c omponent(s ) “Tomcat Applicatio n Server: Isaac-rest ” and clic k “Next” | |
| 518 | ||
| 519 | Figure 3: Applicatio n Componen ts for Dep loyment to Tomcat | |
| 520 | ||
| 521 | Then, sele ct the tom cat server “Tomcat l ocalhost” and click “Next” | |
| 522 | ||
| 523 | Figure 4: Applicatio n Deployer Tomcat Ho st Server | |
| 524 | Lastly, re view and s ubmit the “Deploymen t Request” and click “Finish” | |
| 525 | ||
| 526 | Figure 5: Applicatio n Deployme nt Summary | |
| 527 | Single Sig n On – Int ernal | |
| 528 | There are 2 main com ponents fo r SSOi: | |
| 529 | Siteminder webagent and Apache webserver . | |
| 530 | Apache is already in stalled on servers i n pre-prod and prod. | |
| 531 | If it is n ot install ed, please run as ro ot: | |
| 532 | yum –y ins tall httpd | |
| 533 | Once httpd is instal led, the s iteminder for SSOi w ebagent mu st be sour ced in the Apache st art up scr ipt. | |
| 534 | vi /etc/in it.d/httpd | |
| 535 | # Source f unction li brary. | |
| 536 | . /app/CA/ webagent/c a_wa_env.s h | |
| 537 | Run the fo llowing co mmand to e xtract and copy all the necess ary files. | |
| 538 | This will also set t he proper file permi ssions and ownership | |
| 539 | app/instal lers/insta llssoi.sh | |
| 540 | Copy the c orrect ssl .conf file to /etc/h ttpd/conf. d | |
| 541 | cp app/ins tallers/ap ache_exten sions/ssl. conf-PRE / etc/httpd/ conf.d/ssl .conf | |
| 542 | cp app/ins tallers/ap ache_exten sions/ssl. conf-PROD /etc/httpd /conf.d/ss l.conf | |
| 543 | There will be update d ssl.conf files for both PreP rod and Pr od contain ing the ab ility to d eploy mult iple insta nces of is aac-rest a s well as komet in a single to mcat serve r. | |
| 544 | With this changes we have also updated t he server_ config.yml file that was initi ally insta lled as pe r in secti on 3.8.6.1 of this m anual. | |
| 545 | ||
| 546 | Install SS Oi webagen t | |
| 547 | Refer To s iteminder webagent i nstallatio n document | |
| 548 | Installati on Verific ation Proc edure | |
| 549 | To verify the instal lation acc ess each s ystem URL | |
| 550 | Replace th e “ServerN ame” with the actual fully qua lified hos tname. | |
| 551 | Tomcat | |
| 552 | https://Se rverName: PORT /manager | |
| 553 | Jenkins | |
| 554 | https://Se rverName: PORT /jenkins | |
| 555 | Nexus | |
| 556 | https://Se rverName: PORT /nexus | |
| 557 | Git | |
| 558 | https://Se rverName: PORT /git | |
| 559 | Prisme | |
| 560 | https://Se rverName: PORT /rails_pri sme | |
| 561 | Komet | |
| 562 | https://Se rverName: PORT /rails_kom et_a | |
| 563 | System Con figuration | |
| 564 | System con figuration is detail ed in the installati on section . No added configura tion neede d. | |
| 565 | Database T uning | |
| 566 | N/A | |
| 567 | Back-Out P rocedure | |
| 568 | The operat ion is not currently working o n legacy a pplication s. A manua l back-up process fo r creating and editi ng termino logy is av ailable. A s a result , the back -out strat egy for CT T_DM Relea se 2 (R2) is to turn off the a pplication if necess ary to add ress issue s. A back out proced ure will b e provided for Relea se 3. | |
| 569 | Back-Out S trategy | |
| 570 | The AITC w ill follow establish ed communi cations pr ocedures a nd turn of f the appl ication if necessary . | |
| 571 | Back-Out C onsiderati ons | |
| 572 | In the abs ence of le gacy appli cation, al l “Go/No-G o” decisio ns regardi ng deploym ent and in stallation in produc tion will be made du ring final functiona lity testi ng in pre- production . | |
| 573 | Load Testi ng | |
| 574 | TBD. This informatio n is expec ted by Nov ember 30, 2016. | |
| 575 | User Accep tance Test ing | |
| 576 | TBD. This informatio n is expec ted by Dec ember 09, 2016. | |
| 577 | Back-Out C riteria | |
| 578 | Back-out c riteria wo uld includ e a critic al data er ror discov ered under approval by the COR and VA PM . | |
| 579 | Back-Out R isks | |
| 580 | Slower op erations i n processi ng termino logy updat es has bee n identifi ed as a ba ck-out ris k. | |
| 581 | Authority for Back-O ut | |
| 582 | Alan Arnol d, COR, is the back- out author ity for th is project . | |
| 583 | Back-Out P rocedure | |
| 584 | Currently the back-o ut procedu re is to t urn the sy stem off. A back-out procedure will be p rovided wi th Release 3. | |
| 585 | Back-out V erificatio n Procedur e | |
| 586 | In the eve nt of a ba ck-out, th e team wil l verify t he presenc e of an ap plication landing pa ge informi ng that th e system i s not curr ently avai lable. | |
| 587 | Rollback P rocedure | |
| 588 | N/A | |
| 589 | Rollback C onsiderati ons | |
| 590 | N/A | |
| 591 | Rollback C riteria | |
| 592 | N/A | |
| 593 | Rollback R isks | |
| 594 | N/A | |
| 595 | Authority for Rollba ck | |
| 596 | N/A | |
| 597 | Rollback P rocedure | |
| 598 | N/A | |
| 599 | Rollback V erificatio n Procedur e | |
| 600 | N/A | |
| 601 | ||
| 602 | ||
| 603 | Template R evision Hi story | |
| 604 | Date | |
| 605 | Version | |
| 606 | Descriptio n | |
| 607 | Author | |
| 608 | March 2016 | |
| 609 | 2.2 | |
| 610 | Changed th e title fr om Install ation, Bac k-Out, and Rollback Guide to D eployment and Instal lation Gui de, with t he underst anding tha t Back-Out and Rollb ack belong with Inst allation. | |
| 611 | VIP Team | |
| 612 | February 2 016 | |
| 613 | 2.1 | |
| 614 | Changed ti tle from I nstallatio n, Back-Ou t, and Rol lback Plan to Instal lation, Ba ck-Out, an d Rollback Guide as recommende d by OI&T Documentat ion Standa rds Commit tee | |
| 615 | OI&T Docum entation S tandards C ommittee | |
| 616 | December 2 015 | |
| 617 | 2.0 | |
| 618 | The OI&T D ocumentati on Standar ds Committ ee merged the existi ng “Instal lation, Ba ck-Out, Ro llback Pla n” templat e with the content r equirement s in the O I&T End-us er Documen tation Sta ndards for a more co mprehensiv e Installa tion Plan. | |
| 619 | OI&T Docum entation S tandards C ommittee | |
| 620 | February 2 015 | |
| 621 | 1.0 | |
| 622 | Initial Dr aft | |
| 623 | Lifecycle and Releas e Manageme nt |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.