ENGINE MANAGEMENT

MANAGING THE ENGINE

The development and production engines shall be managed by the Informatica support Team. Information regarding planned downtime/ upgrades shall be provided to the user community from time to time.

RESTARTING THE ENGINE

A mail shall be sent to the user community regarding the re-starting of the engine and after the engine has been brought up this confirmation will be sent so that users can double check status of their sessions. If the sessions have not been scheduled properly the uses should inform the Informatica support team.

TRANSITION OF PROJECTS FOR SUPPORT

REQUIREMENTS FOR SUPPORT

1              A operations document on the functionality of sessions/Mappings to be supported. 2              A re-start and recovery document explaining the actions to be taken if there is a failure for every session/batch. It would be recommended to create cleanup scripts so as to avoid unnecessary manual intervention. 3              Information on support contacts should be provided so that in case there is a need they can be contacted. The types of contacts to be provided should be a primary contact and a secondary contact.

SUPPORT PROCESS ON FAILURE

1              On failure the session will send out a mail/Page to the support team. The Informatica support team shall follow the Re-start and recovery process provided. 2              A mail will be sent to the primary and secondary contacts summarizing the reason for failure and the action taken

SUPPORT WINDOW

Support for Informatica jobs will be provided between the following hours

Monday to Friday

OnSite Support -xxx AM to xxx PM  OffShore Support -xxx PM to xxx PM

Saturday/Sunday and Holidays OffShore Support - xxx PM to xxx PM

CHANGES TO AN EXISTING PROJECT

If enhancements/Bugfixes have been made to existing mappings/Sessions, the same need to be tested in development and the following information should be provided to the Informatica Support Team

1              Project name 2              Folder in development 3              List of session/mapping names 4              If any scripts need to be moved then the list of the same.

Date when the movement has to be made

MIGRATION TO PRODUCTION

Information to be provided

After coding and testing has been done in development, the following information should be provided to the Informatica Development Team so as to facilitate movement of code. This could also be true for enhancements/Bugfixes existing mappings/Sessions

1. Project name

2. Folder in development

3. List of session/mapping names

4. If any scripts need to be moved then the list of the same

5. Date when the movement has to be made

Review before movement

The Informatica Support group will review mappings and Sessions before it is moved from development to Production, following are some of the important points

1              Check if existing database connector/FTP connectors/ External loaders have been used 2              Check if the failure scripts have been added, refer to the Best Practices session for more details 3              Location of scripts/intermediate files and any datafiles 4              Location of lookup and other Caches 5              If any intermediate files are being generated as a part of the process then they should be deleted at the end of the process 6              Check if any existing code or setting can cause a known bug 7              Check if the Scheduling could effect the performance of existing sessions 8              Suggest process improvements to improve efficiency. Any project team could approach the Informatica Support Team during the initial stages of the project for process review. If the methods used to code may affect the existing systems then they will not be moved into production.

Restartability

DEVELOPMENT AND TESTING PROCESS

All development should be done in the development instance of Informatica and Oracle. Separate folders should be created in the same development repository for development, QA and SIT.

The folders marked as _prod will be moved to production on request. The naming convention to be followed will be as described in the Naming Convention best practice in posts thread 

STARTING A NEW PROJECT

Project Initialization A mail has to be sent to the Informatica Support team before the start of any project. The mail should contain the following information.

1. Project Name

2. Project Contact

3. Folder Name

4. List of users accessing the folder

5. Informatica version planned to be used

6. Expected date of moving to Production

7. Expected number of sessions/mappings in the project

A minimum of 5 days notice should be given for code to be moved to production to help plan the same.

Login Every user should have a login into development as well as production. The Corp id will be used as login for individual users. In development users will be given access to both create and execute mappings/sessions whereas in production only read access will be given. The request for creating a new login may come as a part of the project initialization mail or a separate mail maybe sent to the Informatica Support Group. A selective execute privilege can be requested for some sessions or workflows.

Folders and Groups setup Folders will be created based on the information provided to the Informatica Support Group as a part of the project initialization process. Groups will be setup in Informatica to manage access of users to various folders.