Migration Path Environments for Large Organizations

Migration Environment Pattern for Large Organizations
Migration Environment Pattern for Large Organizations

After describing the migration path environments for different customers, I thought it might be time to define some migration paths and their associated environments.  This is a migration environment pattern I have seen in larger organizations, perhaps, with some variation, but essential variations on a theme.  The definition of each environment is in the table below.

Environment NameDescription
Development (DEV)The Development environment is used for developing the application and the submission of baseline code to the source control system.
System Integration Test (SIT)System integration testing is high-level software testing process in which testers verify that all related systems maintain data integrity and can operate in coordination with other systems in the same environment. The testing process ensures that all subcomponents are integrated successfully to provide expected results.
Software Integration Test (SWIT)Software Integration Test is where software module or component subset testing occurs to verify the functionality and/or usability of a module or component and interaction with associated software models and components.
End-To-End (E2E) TestingEnd-to-End Testing exercises a complete production-like scenario of the software system, it also validates batch and data processing from other upstream/downstream systems (interfaces).
System Acceptance Testing (SAT)System Acceptance Testing is to simulate the business environment, security, and regression tests. System Acceptance Testing is conducted to gain acceptance of all functionality from the user community and meets user requirements, as specified.
Production (PROD)The production environment is the final release environment, where the system will begin its Initial Operating Capability (IOC).
Control (CTRL)Control is the ‘Gold’ standard baseline environment from which migrations and new environments are provisioned.  This environment houses base configurations and metadata.  It is not used for testing.

Related References

Migration Path Environments for Small Organizations

Migration Environment Pattern For Small Organizations
Migration Environment Pattern For Small Organizations

After describing the migration path environments for different customers, I thought it might be time to define some migration paths and their associated environments.  This a migration environment pattern I have, usually, seen in small organizations.  The definition for each environment is in the table below.

Environment NameDescription
Development (DEV)The Development environment is used for developing the application and the submission of baseline code to the source control system.
Quality Assurance (QA):The Quality Assurance environment is used for testing of configuration, performance, application processes, and functionality validation.
Production (PROD)The production environment is the final release environment, where the system will begin its Initial Operating Capability (IOC).

Related References

IBM InfoSphere DataStage Migration Checklist

IBM InfoSphere DataStage Migration Checklist
IBM Infosphere Information Server (IIS)

Assuming that your InfoSphere instance has been installed and configured, here is a quick migration checklist to assist in making sure that you have performed the essential tasks.

Major TasksParent-TasksChild-taskCompletion Status
Create Migration Package   
 Create Database scripts  
 Export DataStage components  
 Gather support files  
 Compress migration package  
 Baseline migration package in CM Tool  
 Upload package to target environment  
Deploy Database Components   
 Backup target databases  
 Deploy database components  
 Resolve script errors  
 Create JDBC, ODBC,  and/or TNSNAMES entries  
 Install and Configure RDBMS client on Infosphere server  
 Load configuration and conversion data (if not loaded by ETL)  
Deploy Support Files   
 Create File Structures  
 WSDLs  
 Certificates  
 Surrogate Key Files  
 System Administration Scripts  
 Job Scripts  
 Node Configuration Files  
Deploy DataStage Components   
 Create Project (if required)  
  Configure Project and/or Project Parameters (if required) 
 Import ETL’s into DataStage  
 Update Parameters and Parameter sets (if required)  
  File paths 
  Database names 
  Database credentials 
 Update job properties  
  File paths 
 Compile ETL using Multiple Job Compile  
 Resolve compilation errors  
Smoke Test   
Finalize CM Baseline   

PS Query Migration Validation SQLs

Oracle Peoplesoft Query Migration Validation SQL
Oracle Peoplesoft

While PeopleSoft PeopleTools Application Designer is the best way to validate query migrations, sometimes a few SQL scripts can be helpful when verifying that queries and associated tree exist in an environment with the necessary nodes.  This SQL can be run in the appropriate SQL editor and was written against an Oracle RDBMS.

Is The Query in the Environment?

SELECT DISTINCT QRYNAME

FROM PSQRYFIELD

WHERE QRYNAME LIKE ’<<QUERYNAME>>%’;

Is Query Tree in Environment?

SELECT TREE_NAME

FROM PSTREENODE

WHERE TREE_NAME =’<<TREENAME>>’

ORDER BY 1;

Is Record in Query Security Tree?

SELECT TREE_NODE

FROM PSTREENODE

WHERE TREE_NAME =’<<TREENAME>>’

AND TREE_NODE LIKE ’%<<RecordName>>%’;

Related References