Scribd
Upload
197 views

DataStage Knowledge Transfer

The document summarizes four knowledge transfer sessions on DataStage architecture and administration. It discusses the DataStage server architecture, backup processes, the release management process for making changes to DataStage environments, how to create new projects and LDAP IDs, and how to set up new ODBC data source names for use in jobs.

Uploaded by

Madhu Srinivasan
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
197 views

DataStage Knowledge Transfer

The document summarizes four knowledge transfer sessions on DataStage architecture and administration. It discusses the DataStage server architecture, backup processes, the release management process for making changes to DataStage environments, how to create new projects and LDAP IDs, and how to set up new ODBC data source names for use in jobs.

Uploaded by

Madhu Srinivasan
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

DataStage Knowledge Transfer session

1st Session -- 1st Nov 10

Topic Covered.

Architecture Details of DataStage V8.

a. Server Architecture
b. Storage Architecture
c. Software Architecture

Sources:
\\uskihfil4.kih.kmart.com\public\KIS\Parks\Data Integration\Center of Competency\DI User Handbooks\
SHC Standard DI Framework - Ref_Manual YYMMDD v1.0.pdf

Discussed on doubt in the meeting.

a. Below filesystem are shared between the nodes (conductor, section leader and HA)

                                      /udb
                                         /di/Projects
                                        /di/UVProjects
                                        /opt/IBM
                                        /di/data

b. Backup is taken of filesystem not of repository


c. Backup is taken incremental and is handled by UNIX Admin team.
d. Schedule weekly Backup is taken at every Saturday.
                   Prod – 7:00 PM CST, QA and Dev – 7:00 AM CST
e. Backup of DB2 repository is taken through filesystem /udb and DS repository is taken through
/di/UVProjects.

2nd Session – 3rd Nov 10


Sources:

1. DataStage Admin Workflow Diagram – \\kih.kmart.com\datastore\Workgrp\KIS\InfoServer\


InfoServerUserDoc\DataStage Admin Workflow Diagram.pdf.
2. “BI Data Integration Release Management Process” document which is located at \\
uskihfil4.kih.kmart.com\public\KIS\Parks\Data Integration\Center of Competency\DI User Handbooks\BI
Data Integration Release Management Process YYMMDD v1.0.pdf

Topic Covered.

1. Process structure for any pacman.


● All the pacman case or request should be approved by member of DataStage
Application support team before implementing
● All the Pacman change should be approved by member of DataStage Application
support team and Product service manager team member before implementing
● For any change in production server, type of Pacman should be change (not case or
request)
● For any case or request, DataStage admin team has 5 days of time to complete as per
the standard process. DataStage Admin team can complete within 5 days as per
requirement.
● For any change, pacman should be completing on exact due date and time.
● If any pacman is getting created in the Freeze Season (peak season), it should be
approve by DataStage Application support team, Product service manager team
member and Director Level and CIA before implementing.

● If any developers need any new DataBase connection setup, pacman should come to
DataStage Admin team Queue and then Admin team will forward that pacman to
appropriate DB queue after adding DataStage server name.

2. Code (.dsx file) migration from one environment to other environment.


Detail steps are mention in the below document.
● Document

3. Unix Script migration from one environment to other environment.


To move the script, we have to use scp command.

3rd Session – 8-Nov-10


Topic Covered:

1. Creation of new project


2. Selection of project name as per business Area
3. Creation of LDAP ids associated to that project
4. Submission of SAR (System Access Request) to build the generic application LDAP ID for
use by Control-M

Sources:

\\kih.kmart.com\datastore\Workgrp\KIS\InfoServer\InfoServerAdmin\InfoSvr.Notes

Detail require updated document.

4th Session – 10-Nov-10

Topic Covered:

1. DSN (data source name) creation


● Information of all the DSN is present on .odbc.ini file under DS engine home path
● Jobs, which are using wire protocol, can use only odbc stage.
● In our environment we are using DSN for SQL, NZ and Teradata.
● All DSN creation request can be done only, if pacman is approved
● Details like DB name, DB server name and port number should be given by requester
● Most of the DSN is already present in .odbc.ini file, we have to add only in project level
to use that particular DSN for that project

Sources:

\\kih.kmart.com\datastore\Workgrp\KIS\InfoServer\InfoServerAdmin\InfoSvr.Notes

You might also like