Subject: Per CO or ANR xxxxx AITC will bring down <ENV> to perform maintenance at hh:mm AM/PM CST Email line1: Per CO or ANR xxxxx AITC will bring down <ENV> to perform scheduled maintenance at hh:mm AM/PM CST Email line2: AITC will send out notice once the <ENV> is back online and ready for smoke test. Step 2 Login to the WebLogic GUI Admin console with your LAN ID, if this does not work, check the Password Vault for the environment and use the specified account. Shutdown the requested Managed Servers or Clusters as listed in the Change Order or Service Request. Verify maintenance/deployment completed Step 3 Start the requested Managed Servers or Clusters as listed in the Change Order or Service Request. Step 4 Send out email to: Subject: Per CO or ANR xxxxx AITC has successfully completed <ENV> maintenance at {time} CST Email line1: Per CO or ANR xxxxx AITC has successfully completed <ENV> maintenance at {time} CST Email line2: <ENV> is back online and ready for smoke test. Email line3: Please update this thread with test results and any outstanding issues. System downtime due to application or system software upgrades will be planned with AITC. Users will be notified by PRE using the appropriate mailing lists. The notice will be provided at least two hours in advance. Notification will also be provided when the application becomes available again. System Monitoring, Reporting, & Tools Oracle Enterprise Manager and Grid Control are used to monitor availability and performance of the database on the vaausppsdbs1 server. Standard AITC thresholds are set for space monitoring, availability of the database, and network connectivity. Database administrators are alerted immediately if the monitoring tool detects a problem. In addition, if connectivity to the database fails, an incident ticket is created in the User Service Desk software and relayed to AITC management and the primary and secondary database administrator for the project. System monitoring is done through the following: WebLogic console VistA link console Introscope
Subject: Per CO or ANR xxxxx AITC will bring down <ENV> to perform maintenance at hh:mm AM/PM CST Email line1: Per CO or ANR xxxxx AITC will bring down <ENV> to perform scheduled maintenance at hh:mm AM/PM CST Email line2: AITC will send out notice once the <ENV> is back online and ready for smoke test. Step 2 Login to the WebLogic GUI Admin console with your LAN ID, if this does not work, check the Password Vault for the environment and use the specified account. Shutdown the requested Managed Servers or Clusters as listed in the Change Order or Service Request. Step 3 Verify maintenance/deployment completed Start the requested Managed Servers or Clusters as listed in the Change Order or Service Request. Step 4 Send out email to: Subject: Per CO or ANR xxxxx AITC has successfully completed <ENV> maintenance at {time} CST Email line1: Per CO or ANR xxxxx AITC has successfully completed <ENV> maintenance at {time} CST Email line2: <ENV> is back online and ready for smoke test. Email line3: Please update this thread with test results and any outstanding issues. System downtime due to application or system software upgrades will be planned with AITC. Users will be notified by PRE using the appropriate mailing lists. The notice will be provided at least two hours in advance. Notification will also be provided when the application becomes available again. System Monitoring, Reporting, & Tools Oracle Enterprise Manager and Grid Control are used to monitor availability and performance of the database on the vaausppsdbs1 server. Standard AITC thresholds are set for space monitoring, availability of the database, and network connectivity. Database administrators are alerted immediately if the monitoring tool detects a problem. In addition, if connectivity to the database fails, an incident ticket is created in the User Service Desk software and relayed to AITC management and the primary and secondary database administrator for the project. System monitoring is done through the following: WebLogic console VistA link console Introscope
pren_1_1p3_v1_1_02_tg.docx