2011.2 Production
Migration Plan
Document Revision History
Version
1
Date
Author
Description
Sept
Project Team
Initial Draft
NEHEN Production Migration Plan
Table of Contents
OVERVIEW ................................................................................................................................................................3
1.
PREP WORK ACTIVITIES FOR ALL SITES ..............................................................................................4
2.
DATABASE ACTIVITIES PRIOR TO PRODUCTION GO-LIVE DATE .................................................6
3.
APPLICATION SERVER ACTIVITIES PRIOR TO PRODUCTION GO-LIVE DATE .........................8
4.
ACTIVITIES ON PRODUCTION GO-LIVE DATE ................................................................................... 10
5.
OTHER PRODUCTION MIGRATION PLANS .......................................................................................... 12
Page 2 of 12
NEHEN Production Migration Plan
Overview
This document outlines the 2011.2 production upgrade process. There are four different sets of
activities to complete, each one of which is important on its own, and essential to your
production upgrade. Each of these activity sets may have individual activities that your
particular installation may not need to complete, or special steps that you do need to complete,
so please read through these instructions carefully. In the overview below we point out the
four sections of activities and sub activities, but for the full details you must read the actual
instructions which follow.
The four main sets of activities are:
1. Prep work steps – to happen ASAP
a. Review Hardware Specs
b. Purge NEHEN Database
c. Files and Folders Maintenance
d. Networking Changes
2. Database Activities prior to Go Live date – to happen 4-3 weeks before production
a. Execute the 12.5.1 database comparison check
b. Migrate 2011.2 databases
c. Prep the Scheduler and eGateway ADX
3. Application Server Activities prior to Go Live date – to happen 2-1 weeks before production
a. Install Third Party Software
b. Create Data Folder Structure
c. Copy Transaction Files
4. Activities on Production Go Live Date – to happen on production go-live date
a. Execute the 2011.2 SQL Scripts
b. Execute the application script
c. Configure the application
d. Assign IP Address
e. Activate the system
Please remember that not all activities may be required, depending on your installation.
This document outlines the process to upgrade your production environment to 2011.2. Sites
are able to use the information in this document to upgrade other test environments if needed.
Please remember that database names cannot be changed. Sites are required to use our
naming standard.
Page 3 of 12
NEHEN Production Migration Plan
1. Prep Work Activities for All Sites
This section outlines activities that a site should perform as soon as possible to verify the
NEHEN production environment is ready for the 2011.2 release.
a. Review Hardware Specifications


Timeline: ASAP
Compare the system resources of the production application to the NEHEN Hardware
Specifications document. It is important that the application server matches or exceeds the
NEHEN specifications.
Compare the system resources of the production SQL server to the NEHEN Hardware
Specifications document. It is important that the application server matches or exceeds the
NEHEN specifications.
b. Purge NEHEN Database



Timeline: ASAP
Determine if your site wants to maintain historical transaction information in your 2011.2
databases.
If your site wants to maintain historical information, execute the purge application to reduce the
volume if needed.
If your site wants to remove all historical transaction data from the production database, please
contact the NEHEN Support team.
c. Files and Folders Maintenance

Timeline: ASAP
Remove historical transactions that are no longer needed on the file system from various
service folders:
Audit
Problem
Temp
Logs
Page 4 of 12
NEHEN Production Migration Plan
d. Networking Changes




Timeline: ASAP
If your site is changing the IP address of your production application server, communicate the
new IP to the payers (BCBSMA, Tufts, HPHC, NHP, Network Health, BMC HealthPlan) with the
date that you will need the new IP available in the payer’s production environment.
If your site uses NEHENHub, communicate the new IP to the NEHEN Support.
If your site is changing the IP address of your production application server, communicate the
new IP to any integrated systems.
If a payer is changing the IP address of their NEHEN environment, please notify the providers
about the changes.
Page 5 of 12
NEHEN Production Migration Plan
2. Database Activities Prior to Production Go-live Date
This section outlines activities that a site should execute to get the SQL Server environment
ready prior to the production go-live date.
If your site wants to maintain the historical information in the 12.5.1 production database, you
will need to perform the activities in this section. Please refer to the document called NEHEN
2011.2 DB Configuration From 12.5.1.docx for detailed instructions on how to upgrade your
12.5.1 database to the 2011.2 databases.
If your site does not want to maintain historical information and wants to use the 2011.1 test
databases for production, your site will need to create the new databases in the SQL production
environment, backup the 2011.2 database in your test environment, and use the backups to
restore the information into your production databases. In addition to transaction information,
the users, groups, organizations, accounts and provider information from your test
environment will be the bases for your production environment.
.
a. Execute the 12.5.1 Database Comparison Check








Timeline: ASAP
Identify a date and time when to execute this process against the production database. The
NEHEN 12.5.1 production environment will need to be shutdown during this window.
Run the attached 12.5.1 Info Gathering.sql script against your current 12.5.1 test database.
There are three queries in the .SQL File. The first one is the Tables/Columns check, the second is
the Primary Key and the final one is the Foreign Key.
Save each of the query results as .CSV files. It is important to save the results as .csv. Otherwise
the text to text comparison will not be able to correctly identify the changes. To save a query as
.csv you can right click in the upper left corner of the query results and select “Save Result As”.
Send the CSV files to your NEHEN Team Lead.
These files will be reviewed by our DBA. We will identify changes that sites are able to make
now (“safe” changes) vs. changes that will have to wait for your go-live date.
When your site receives the list of “safe” changes, apply the manual updates to your 12.5.1
production database. This activity will need to be performed during off hours and the
application will need to be shut down.
Backup the 12.5.1 production database before making any changes to the database. If your site
encounters any application issues, your site will be able to restore the database is needed.
If your site is setting up a new production SQL Server, perform this task in your existing 12.5.1
SQL production environment.
Page 6 of 12
NEHEN Production Migration Plan
b. Migrate 2011.2 Databases




Timeline: 3 weeks
before Production
Please refer to the configuration section of the document called NEHEN 2011.2 DB
Configuration From 12.5.1.docx to get detailed information about migrating the eGateway and
Scheduler databases.
Create ADMN_eGateway_Prod and ADMN_Scheduler_Prod databases using the script.
Restore the ADMN_eGateway_Prod and ADMN_Scheduler_Prod databases from the
ADMN_eGateway_Test and ADMN_Scheduler_Test database backups resprectively.
Create the custom database with the appropriate tables and stored procedures based on your
custom applications. Data will need to be migrated from your existing production environment
on go-live date if your site wants to maintain the information.
c. Prep Scheduler and eGateway ADX


Configure the eGateway ADX Configurator to point to the production SQL Server.
Review and modify scheduler activities to verify that the following properties are using
production values:
IP Addresses




Timeline: 3 weeks
before Production
FTP Login IDs
Review and modify trading partner associations to verify the production flag is set to
production.
Review the start count property for each partner adapter based on production volumes.
Review and modify adapters to use the production IPs for payers and core systems. In addition,
verify login and submitter ids.
Remaining configuration information should not need any changes.
Page 7 of 12
NEHEN Production Migration Plan
3. Application Server Activities Prior to Production Go-live Date
This section outlines activities for a site that is setting up a new application server or planning
to upgrade the existing 12.5.1 application server.
If your site is planning to switch your 2011.2 test server to production, you may skip activity a
and go directly to activity b.
a. Install Third Party Software



Install Silverlight v.4 runtime plus Silverlight v.4 SDK.
Install .NET v 4.0
Activate MSMQ.
b. Create Data Folder Structure

Timeline: 2 weeks
before Production
Timeline: 2 weeks
before Production
Create folder structure on the application server to store transaction files. Utilize the file system
recommendation provided by NEHEN.
c. Copy Transaction Files (New Application Server
Only For Providers)
Timeline: 1 week before
Production
If your site does not use NEHEN for claims, please skip this section.


Copy the NEHENLite Inbound folder from the 12.5.1 production server to the new application
server. The claim response files need to be copied over. The realtime files are needed so your
site may want to exclude these during this activity.
Copy any Claim folders that contain 837s, 835s, 997s, submitter reports, and 277ACKs.
Page 8 of 12
NEHEN Production Migration Plan
d. Setup FTP Accounts (Payers Only)
Timeline: 2 week before
Production
If your site does not use your NEHEN application server as your FTP server, please skip this
activity.



Activate the FTP service on the application server.
Setup claim folder structure on the application server for inbound and outbound files related to
claims.
Create FTP Login IDs and passwords for each account.
Page 9 of 12
NEHEN Production Migration Plan
4. Activities on Production Go-live Date
This section outlines activities for a site that is setting up a new application server or planning
to upgrade the existing 12.5.1 application server.
If your site is planning to switch your 2011.2 test application and database servers to
production, you may skip the activities in this section. Your test should be ready to go if your
site has been applying all upgrades and patches including the production release.
a. Execute the 2011.2 SQL Scripts


Execute DB installation steps to upgrade the NEHEN Database 12.5.1 to 2011.1.
Execute DB installation steps to upgrade the NEHEN 2011.1 database to 2011.2
b. Execute the Application Script


Timeline: Production
Go-live Date
Execute Application installation steps to install 2011.2 on the application server.
c. Configure the Application

Timeline: Production
Go-live Date
Timeline: Production
Go-live Date
Setup the HTS Control, Cert, and Response folders on the application server if needed. This task
only applies to providers.
If your site is setting up a new server, you will need to install the production certs on the server
from Harvard Pilgrim, Neighborhood Health Plan, and Health New England. This task only applies
to providers that use HTS.
Page 10 of 12
NEHEN Production Migration Plan
d. Assign IP Address

If your site is activating the 2011.2 test server as your production server, assign the IP address of
your production server to the test server.
e. Activate the System



Timeline: Production
Go-live Date
Start the TCPIP Listener, Message Processer, Scheduler, Control Panel, and the Process EXPS
services.
Start the eGateway ADX Configurator tool.
Start Express.
f. Test the System



Timeline: Production
Go-live Date
Timeline: Production
Go-live Date
Submit transactions from Express.
Submit eligibility big batches if applicable.
Submit transactions from any core system if applicable.
Page 11 of 12
NEHEN Production Migration Plan
5. Other Production Migration Plans
This section outlines other plans that sites may utilized to migrate 2011.2 into production. If
your site needs to maintain the 12.5.1 production data, use the four main activities outlined
above.
a. Migrate 2011.2 Test Database
Timeline: Production
Go-live Date
Your site will need to review and possibly execute the activities outlines in the Prep Work
Steps and Application Server Activities Prior to Go Live Date sections of this document, before
executing the activities below on the go-live date:





Create the 2011.2 ADMN databases in your Production SQL Server.
Take a backup of each 2011.2 ADMN databases in your Test SQL server.
Restore each ADMN database from their respective backups.
Execute activities B thru E outlined in the section called “6. Activities on Production Go-live
Date”.
If the HIE application is installed on a drive letter that does not match the drive letter from your
test environment, you will need to update information in multiple database tables. For example
the HIE folder was installed on the “D” drive in your test environment and on the “E” drive in
your production environment. These tables contain the full folder paths.
Page 12 of 12