Your SlideShare is downloading. ×
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Informatica Server Manager
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Informatica Server Manager

9,138

Published on

Informatica server manager

Informatica server manager

Published in: Technology
4 Comments
3 Likes
Statistics
Notes
  • l like it
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Hi Ganblue
    Nice and Useful post,could you please enable the save button to download document.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • please share your email ID.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • plz send me the link to download this..its really helpful
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
9,138
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
4
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • The Figure shows the processing path between the Informatica Server, repository, source, and target
  • The Informatica Server can combine data from different platforms and source types. For example, you can join data from a flat file and an Oracle source, and write the transformed data to a Microsoft SQL Server database. When a session starts, the Informatica Server retrieves mapping and session metadata from the repository to extract data from the source, transform it, and load it into the target. The Informatica Server can combine data from different platforms and source types
  • The Informatica Server can achieve high performance by partitioning source data and performing the extract, transformation, and load for each partition in parallel When you partition a session, configure partitioning based on source qualifiers in a mapping
  • Unlike connecting to a database, the Server Manager communicates with the Informatica Server through a TCP/IP or IPX/SPX port
  • The native connect string can be defined in the native database client connectivity software, such as Net8, on the machine hosting the repository database The adjacent table, summarizes the software you need to connect the Informatica Server to the repository, source, and target databases
  • The Load Manager is the primary Informatica Server process
  • The Load Manager holds the connection to the repository for the value set in the Informatica Server configuration, LMStayConnectToRepositDuration When you start the Informatica Server. When you start the Informatica Server, the Load Manager launches and queries the repository for a list of sessions configured to run on the Informatica Server. When you configure a session. When you add, update, or schedule a session in the Server Manager, the repository stores all the session metadata. The Load Manager maintains a list of sessions and session start times. When a session starts. When a session starts, the Load Manager fetches the session information from the repository to perform the validations and verifications prior to starting the DTM process. The execute lock allows the Informatica Server to run the session and prevents you from starting the session again until it completes. If the session is already locked, the Informatica Server cannot start the session. A session may be locked if it is already running, or if an error occurred during the previous run that prevented the repository from releasing the execute lock.
  • On UNIX, the Informatica Server creates a log for all status and error messages (default name: pmserver.log). It also creates an error log for error messages only (default name: pmserver.err). These files appear by default in the Informatica Server home directory. You can troubleshoot Informatica Server problems by examining error messages sent to these logs. On Windows NT/2000, the Informatica Server logs status and error messages in the event log. Use the Event Viewer to access those messages. The Informatica Server creates a session log file for each session it runs. It writes information in the session log such as initialization of processes, creation of SQL commands for reader and writer threads, errors encountered, and load summary. The amount of detail in the session log depends on the tracing level that you set. When you run a session, the Server Manager creates session details that provide load statistics for each target in the mapping. You can monitor session details during the session or after the session completes. Session details include information such as table name, number of rows written or rejected, and read and write throughput. You can view this information by double-clicking on the session in the Monitor window. The Informatica Server can create a set of information known as session performance details to help determine where performance can be improved. Performance details provide transformation-by-transformation information on the flow of data through the session. To generate this information for a session, select the performance detail option in the session property sheet. The Informatica Server creates a reject file for each target in the session. The reject file contains rows of data that the writer does not write to targets. When you run a session that uses the external loader, the Informatica Server creates a control file and a target flat file. The control file contains information about the target flat file such as data format and loading instructions for the external loader. If you use a flat file as a target, you can configure the Informatica Server to create an indicator file for target row type information. For each target row, the indicator file contains a number to indicate whether the row was marked for insert, update, delete, or reject. The Informatica Server creates index and data cache files for the following transformations in a mapping: Aggregator transformation (without sorted ports) Joiner transformation Rank transformation Lookup transformation (with caching enabled)
  • Can define error tracing levels for each transformation or for the entire session. By default, the Informatica Server saves session logs in the directory for the Informatica Server variable $PMSessionLogDir, which you define in the Server Manager. The default name for the session log is session_name .log. You can override the session log name and location in the session properties.
  • Configure Server Manager display options. You can configure the display options such as grouping sessions or docking and undocking windows. Register Informatica Servers. Before you can start an Informatica Server, you must register it with the repository. Create source and target database connections. Create connections to each source and target database. You must create connections to a database before you can create a session that accesses the database. Create FTP connections. After you create FTP connections, you can configure a session to use FTP to access source or target files. For details, see Creating an FTP Connection . Create external loader connections. Create connections to Oracle, Sybase IQ, and Teradata external loaders. You must create these connections before you can configure a session to use an external loader.
  • When you start a PowerMart Server, it verifies that it is the only Informatica Server registered in the repository. It does not start if there are other Informatica Servers registered in the repository
  • Database type. Type of the source or target database. Data source. Connection name used by the Server Manager. After creating the database connection, the data source name appears as the database connection. Database username. Must have the appropriate database permissions to read from and write to the database. Database password. Must be in US-ASCII only. Database name. Name of the source or target database. Server name. Name of the machine hosting the database. Database code page. Code page associated with the database.
  • With both source and target files, you can either FTP the files directly to the Informatica Server or stage them on a local directory for the session run. Host name. The name or IP address of the remote machine. Optionally, you can specify a port number between 1 and 65535 inclusive. If you do not specify a port number, the Informatica Server uses 21 as the port number by default. Use the following syntax for specifying a host name: hostname:port-number or IP address:port-number When you specify a port number, enable that port number for FTP on the host machine. Default remote directory. The directory you want the Informatica Server to use by default. In the session, when you enter a filename without a directory, the Informatica Server appends the filename to this directory. Therefore, this path must be exact and contain the appropriate trailing delimiters. For example, if you enter c:/data/ and in the session specify the file FILENAME, the Informatica Server reads the path and filename as c:\\data\\FILENAME.
  • Source Database Connection. Select the database connection for the relational source. Override SQL Query . On the Transformations tab, you can override the default SQL query to extract source data. Flat file buffer length. You can change the buffer length for flat files. Use the Advanced Options button on the General tab of the session properties to access this option.
  • If you have a heterogeneous session with relational sources, you can select a separate database connection for each source in the Source Location tab.
  • Truncate target tables. The Informatica Server can truncate selected relational target tables before loading session data. Load options. Configure the session to use normal or bulk loading. If you select a normal load, you can also run a test load session. Drop and recreate indexes. Set the option to drop and recreate an index on a relational target table to optimize query speed. Constraint-based loading. The Informatica Server can load data to targets based on primary-foreign key constraints and active sources in the session mapping. In the Server Manager, you can specify constraint-based loading for a session. When you select this option, the Informatica Server orders the target load on a row-by-row basis. For every row generated by an active source, the Informatica Server loads the corresponding transformed row first to the primary key table, then to any foreign key tables. Use this option when you load related target tables with data from the same active source. An active source is the last active transformation in the pipeline. The following transformations can be an active source within a mapping: Source Qualifier Normalizer (COBOL or flat file) Advanced External Procedure Aggregator Joiner Rank Mapplet, if it contains one of the above transformations
  • If you select Normal, the Informatica Server loads targets normally. If you select Bulk for a Sybase or Microsoft SQL Server target, Informatica invokes the BCP utility with default settings, bypassing database logging. For other types of databases, the Informatica Server loads targets normally even if you select Bulk. Loading in Bulk mode can improve session performance, but limits the ability of the Informatica Server to perform recovery because no database logging occurs.
  • You must have appropriate permissions to schedule sessions. If the session is not run-on-demand, you must have one of the following sets of privileges and permissions: Create Sessions and Batches privilege with folder read and execute permission Session Operator privilege with folder read permission Super User privilege You must have execute permission for global objects associated with the session in addition to the permissions and privileges listed above.
  • Once the indicator file appears: If you scheduled the session and the scheduled start time has not arrived, the Informatica Server waits until the next scheduled session run, then starts the session. If you scheduled the session and the scheduled start time has passed, the Informatica Server starts the session immediately. If you started the session manually, the Informatica Server starts the session immediately.
  • When you partition a session, the Informatica Server provides session details for each partition. You can use these details to determine if the data is evenly distributed among the partitions. For example, if the Informatica Server moves more rows through one target partition than another, or if the throughput is not evenly distributed, you might want to adjust the source data range for the partitions.
  • For example, you copy a session configured to run on the SALES server and use the Source and Target database connections. The target repository contains database connections named Source and Target, but it does not have a SALES server. During the copy, the wizard prompts you to select a server to run the session. It lists all servers registered with the target repository. Since the target repository contains the database connections named Source and Target, the wizard does not prompt you to select new database connections. Note: Make sure all connection types used in the session exist in the target repository before copying the session. For example, if the session uses an external loader connection, make sure the target repository contains at least one external loader connection. If an external loader connection is not available in the target repository, the wizard produces an invalid session in the target folder.
  • For example, you might have a mapping with Decimal (20,0) that passes the number 40012030304957666903. If you enable decimal arithmetic, the Informatica Server passes the number as is. If you do not enable decimal arithmetic, the Informatica Server passes 4.00120303049577 x 10 19 For example, if you want to process the number 2345678904598383902092.1927658, which has a precision of 29 digits, the Informatica Server automatically treats this number as a Double value of 2.34567890459838 x 10 21
  • You might create a sequential batch if you have sessions with source-target dependencies that you want to run in a specific order. You might also create a concurrent batch if you have several independent sessions you need scheduled at the same time. You can place them all in one batch, then schedule the batch as needed instead of scheduling each individual session. You can nest batches several levels deep, defining batches within batches. Nested batches are useful when you want to control a complex series of sessions that must run sequentially or concurrently. However, you can configure a batched session to run on its own schedule by selecting the Use Absolute Time session option.
  • If batch logic requires it, you can configure sessions in a sequential batch to run only if the previous session completes. If the previous session fails, the Informatica Server does not run the session and stops the batch. If you have sessions with dependent source/target relationships, you can place them in a sequential batch so the Informatica Server can run them in consecutive order. You might use a sequential batch, for example, if you have a session performing a lookup on the target table of another session. To provide up-to-date lookup information, the session providing the lookup table should run first. You can place both in a sequential batch to run in the correct order. You might use concurrent batches if your time on the Informatica Server is limited. When you place several sessions with separate sources and targets into a concurrent batch, you increase the chances of completing the sessions within a given time period. A session sends 14 million rows of data to a staging area. Instead of running one large session, you can improve session performance by separating the session into 14 separate sessions and running them concurrently in a batch. To do this, first add a source filter to the mapping. Then copy the session 13 times and edit each session attribute to override the source filter condition. When overriding the source filter, have the first session read the first million rows, the second session read the second million rows. Then place all 14 sessions in a concurrent batch.
  • For example, if you place a session using pre-session stored procedures into a batch, the Informatica Server runs the stored procedures before starting the session. The Informatica Server creates separate log files and reject files for each session.
  • Enter source attributes. Configure source attributes specific to the type of source you partition. For example, if you partition a relational source, you can override the SQL query or enter an additional source filter. If you partition a file source, you can enter the file location and FTP properties. Enter target attributes. Configure target attributes specific to the type of target in the mapping. For example, you can enter reject file name and location for both file and relational targets. With file targets, you can also specify information such as target file names and FTP connections.
  • If you insert data from a partitioned session into an Informix target configured for page-level locking, the session fails Microsoft Access does not allow multiple concurrent connections to tables. Do not partition a session that loads to Microsoft Access targets.
  • This does not replace the Server Manager, since there are many tasks that you can perform only with the Server Manager
  • Repository username. This can be configured optionally as an environment variable. Repository password. This can be configured optionally as an environment variable. Connection type. The type of connection from the client machine to the Informatica Server (TCP/IP or IPX/SPX). Port or connection. The TCP/IP port number or IPX/SPX connection (Windows NT/2000 only) to the Informatica Server. Host name. The machine hosting the Informatica Server (if running pmcmd from a remote machine through a TCP/IP connection). Session or batch name. The names of any sessions or batches you want to start or stop. Folder name. The folder names for those sessions or batches (if their names are not unique in the repository). Parameter file . The directory and name of the parameter file you want the Informatica Server to use with the session or batch.
  • Each time you run a session, the Informatica Server appends rejected data to the reject file. Delete the reject file if you do not want to load it using the reject loader utility. Depending on the source of the problem, you can correct the mapping and target database to prevent rejects in subsequent sessions.
  • Target-based commit. The Informatica Server commits data based on the number of target rows and the key constraints on the target table. The commit point also depends on the buffer block size and the commit interval. Source-based commit. The Informatica Server commits data based on the number of source rows. The commit point is the commit interval you configure in the session properties.
  • For example, a session is configured with target-based commit interval of 10,000. The writer buffers fill every 7,500 rows. When the Informatica Server reaches the commit interval of 10,000, it continues processing data until the writer buffer is filled. The second buffer fills at 15,000 rows, and the Informatica Server issues a commit to the target. If the session completes successfully, the Informatica Server issues commits after 15,000, 22,500, 30,000, and 40,000 rows.
  • Although the Filter, Router, and Update Strategy transformations are active transformations, the Informatica Server does not use them as active sources in a source-based commit session.
  • The Informatica Server might commit less rows to the target than the number of rows produced by the active source. For example, you have a source-based commit session that passes 10,000 rows through an active source, and 3,000 rows are dropped due to transformation logic. The Informatica Server issues a commit to the target when the 7,000 remaining rows reach the target. The number of rows held in the writer buffers does not affect the commit point for a source-based commit session. For example, you have a source-based commit session that passes 10,000 rows through an active source. When those 10,000 rows reach the targets, the Informatica Server issues a commit. If the session completes successfully, the Informatica Server issues commits after 10,000, 20,000, 30,000, and 40,000 source rows.
  • Can define error tracing levels for each transformation or for the entire session. By default, the Informatica Server saves session logs in the directory for the Informatica Server variable $PMSessionLogDir, which you define in the Server Manager. The default name for the session log is session_name .log. You can override the session log name and location in the session properties.
  • Transcript

    • 1. INFORMATICA POWERCENTER/ POWERMART SERVER MANAGER
    • 2. INFORMATICA SERVER AND DATA MOVEMENT
      • The Informatica Server moves data from sources to targets based on mapping and session metadata stored in a repository
      • A session is a set of instructions that describes how and when to move data from sources to targets
      • Server Manager creates and manages sessions and batches, and monitors and stops the Informatica Server
    • 3. INFORMATICA SERVER
      • When a session starts, the Informatica Server retrieves mapping and session metadata from the repository
      • The Informatica Server runs as a daemon on UNIX and as a service on Windows NT/2000
      • The Informatica Server uses the following processes to run a session:
        • The Load Manager process - Starts the session, creates the DTM process, and sends post-session email when the session completes
        • The DTM process - Creates threads to initialize the session, read, write, and transform data, and handle pre- and post-session operations
    • 4. INFORMATICA SERVER
      • The Informatica Server can achieve high performance by partitioning source data
      • To accomplish this, use the following session and server configuration:
        • Configure the session to partition source data
        • Install the Informatica Server on a machine with multiple CPUs
    • 5. INFORMATICA SERVER
      • The Informatica Server needs to have a connection to the repository database
      • Cannot start the Informatica Server without first configuring it to connect to the repository database
      • Need to use the Server Manager to register the Informatica Server in the repository
      • The Server Manager communicates directly with the Informatica Server whenever you try to
        • Schedule or edit a session
        • display session details
        • request session logs
    • 6. POWERMART AND POWERCENTER CONNECTIVITY
    • 7. INFORMATICA SERVER CONNECTIVITY REQUIREMENTS
      • The Informatica Server requires a connect string to communicate with the repository
      • The native connect string can be defined in the native database client connectivity software
    • 8. THE LOAD MANAGER PROCESS
      • The Load Manager performs the following tasks:
      • Manages session and batch scheduling
      • Locks the session and reads session properties
      • Reads the parameter file
      • Expands the server and session variables and parameters
      • Verifies permissions and privileges
      • Creates the session log file
      • Creates the Data Transformation Manager (DTM) process, which executes the session
    • 9. THE LOAD MANAGER PROCESS
      • It communicates with the repository in the following situations:
        • When you start the Informatica Server
        • When you configure a session
        • When a session starts
    • 10. INFORMATICA SERVER - OUTPUT FILES
      • Once launched, the Informatica Server logs status and error messages to a UNIX log file or to the Windows NT/2000 Application log
      • During each session, the Informatica Server creates a session log file and reject file
      • The Informatica Server creates the following output files:
        • Informatica Server Log
        • Session Log File
        • Session Details File
        • Performance Detail File
        • Reject Files
        • Control File
        • Post-Session Email
        • Output File
        • Cache Files
    • 11. INFORMATICA SERVER - OUTPUT FILES
      • The Informatica Server associates a message code with the text of every message
      • Messages from the Informatica Server on Windows appear in the Application Log, which you can view with the Event Viewer
      • Messages sent from the Informatica Server display PowerMart in the Source column, the code prefix in the Category column, and the code number in the Event column
    • 12. OUTPUT FILES - SESSION LOG FILE
      • The amount of detail in the session log depends on the error tracing level that you set
      • The session log contains the following information about a session:
        • Allocation of system shared memory
        • Execution of pre-session commands
        • Session initialization
        • Creation of SQL commands for reader and writer threads
        • Start and end times for target loading
        • Errors encountered during session
        • Execution of post-session commands
        • Load summary of reader, writer, and (DTM) statistics
    • 13. OUTPUT FILES– SESSION DETAILS FILE AND PERFORMANCE DETAILS FILE
      • When you run a session, the Server Manager creates session details that provide load statistics for each target in the mapping
      • Session details include information such as table name, number of rows written or rejected, and read and write throughput
      • The Informatica Server can create a set of information known as session performance details to help determine where performance can be improved
      • Performance details provide transformation-by-transformation information on the flow of data through the session
      • To generate this information for a session, select the performance detail option in the session property sheet
    • 14. OUTPUT FILES – REJECT FILE
      • The Informatica Server creates a reject file for each target in the session
      • The reject file contains rows of data that the writer does not write to targets
      • The writer may reject a row in the following circumstances:
        • It is flagged for reject by an update strategy in the data flow
        • It violates a database constraint, such as primary key constraint
        • A field in the row was truncated or overflowed, and the target database is configured to reject truncated or overflowed data
      • Informatica includes a reject loader utility to load corrected reject files to targets
      • By default, the Informatica Server saves the reject file in the directory entered for the server variable $PMBadFileDir in the Server Manager, and names the reject file target_table_name .bad
    • 15. OUTPUT FILES – CONTROL FILE AND INDICATOR FILE
      • When you run a session that uses the external loader, the Informatica Server creates a control file and a target flat file
      • The control file contains information about the target flat file such as data format and loading instructions for the external loader
      • The control file has an extension of .ctl
      • If you use a flat file as a target, you can configure the Informatica Server to create an indicator file for target row type information
      • For each target row, the indicator file contains a number to indicate whether the row was marked for insert, update, delete, or reject
      • The Informatica Server names this file target_name .ind and stores it in the same directory as the target file
    • 16. OUTPUT FILES – CACHE FILES
      • When the Informatica Server creates memory cache it also creates cache files
      • The Informatica Server creates index and data cache files for the following transformations in a mapping:
        • Aggregator transformation (without sorted ports)
        • Joiner transformation
        • Rank transformation
        • Lookup transformation (with caching enabled)
      • The Informatica Server writes to the index and data cache files during the session in the following cases:
        • The mapping contains one or more Aggregator transformations, and the session is configured for incremental aggregation
        • The mapping contains a Lookup transformation that is configured to use a persistent lookup cache, and the Informatica Server runs the session for the first time
        • The mapping contains a Lookup transformation that is configured to initialize the persistent lookup cache
        • The DTM runs out of cache memory and pages to the local cache
    • 17. SERVER MANAGER
      • You can configure display options and connection information in the Server Manager
      • You must register an Informatica Server before you can start it or create a session to run against it
      • You can configure the following settings in the Server Manager:
        • Configure Server Manager display options
        • Register Informatica Servers
        • Create source and target database connections
        • Create FTP connections
      • Can change connection information at any time
      • If you delete a connection, you invalidate any session or batch using the connection
    • 18. SERVER MANAGER
      • The Server Manager displays the following windows:
        • Navigator - View and select configured sessions
        • Configure - Create and edit sessions
        • Monitor - View information about running and completed sessions and batches
        • Output - View messages from the Informatica Server
    • 19. REGISTERING AN INFORMATICA SERVER
      • Before creating or running sessions, the Informatica Server must be registered in the repository
      • Use the Server Manager to register the Informatica Server
      • Can register and run multiple PowerCenter Servers against a local or global repository
      • Can register and run only one PowerMart Server in a local repository
      • Can not register a PowerMart Server in a global repository
      • When you start a PowerMart Server, it verifies that it is the only Informatica Server registered in the repository
      • It does not start if there are other Informatica Servers registered in the repository
    • 20. REGISTERING AN INFORMATICA SERVER
      • The following information is required for registering an Informatica Server:
        • Informatica Server name
        • Type of network protocol used to access the Informatica Server: TCP/IP or IPX/SPX
        • Code page identifying the character set associated with the Informatica Server
        • Default directories you want the Informatica Server to use for session files and caches
    • 21. REGISTERING AN INFORMATICA SERVER
      • You can define server variables for each Informatica Server you register
      • Server variables define the path and directories for session output files and caches
      • By default, the Informatica Server places output files in these directories when you run a session
      • The installation process creates directories in the location where you install the Informatica Server
      • To use these directories as the default location for the session output files, you must first set the server variable $PMRootDir to define the path to the directories
      • By using server variables, you simplify the process of changing the Informatica Server that runs a session or batch
      • If each session and batch in a folder uses server variables, then when you copy the folder to a production repository, the Informatica Server in production can run those sessions and batches using the server variables defined with the test Server
    • 22. DATABASE CONNECTION
      • Before the Informatica Server can use a source or target database in a session, a database connection needs to be configured in server manager
      • The following information is required to create a database connection:
        • Database type
        • Data source
        • Database username
        • Database password
        • Database name
        • Server name
    • 23. DATABASE CONNECTION
      • Some database drivers, such as ISG Navigator, do not allow usernames and passwords. Since the Server Manager requires a database username and password, PowerMart and PowerCenter provide two reserved words to register databases that do not allow usernames and passwords:
        • PmNullUser
        • PmNullPasswd
      • If you edit a database connection without changing the data source name, all sessions using the named connection then use the updated connection
    • 24. USING FTP
      • The Informatica Server can use File Transfer Protocol (FTP) to access source and target files
      • With both source and target files, you can either FTP the files directly to the Informatica Server or stage them on a local directory for the session run
      • You can also stage files by creating a pre-session shell command to move the files local to the Informatica Server
      • Accessing files directly with FTP generally provides better session performance than using FTP to stage the files
      • Before creating an FTP session, the FTP connection must be configured in the Server Manager
      • The following information is must while creating an FTP connection:
        • FTP Connection Name
        • Host Name
        • Default Remote Directory
    • 25. SESSION
      • A session is a set of instructions that tells the Informatica Server how and when to move data from sources to targets
      • Sessions are created and managed in server manager
      • When you create a session, you enter general information such as the session name, session schedule, and the Informatica Server to run the session
      • You can also select options to execute pre-session shell commands, send post-session email, and FTP source and target files
      • You can group sessions into a batch
      • The Informatica Server can run the sessions in a batch in sequential order, or start them concurrently
      • Some batch settings override session settings
    • 26. SESSION
      • Using session properties, you can override parameters established in the mapping, such as
        • source and target location
        • source and target type
        • error tracing levels
        • transformation attributes
      • Once you create a session, you can use either the Server Manager or the command line program pmcmd to start or stop the session
      • You can also use the Server Manager to monitor, edit, schedule, abort, copy, and delete the session
      • The Informatica Server may create several other files and in-memory caches depending on the transformations and options used in the session
    • 27. CREATING SESSION
      • You create a session for each mapping you want the Informatica Server to run
      • The Informatica Server uses the instructions configured in the session to move data from sources to targets
      • After you create the session, you can edit the session properties at any time
      • To create a new session, the following information must be entered:
        • Mapping used for the session
        • Session name, which must be unique among all sessions in a given folder
        • Source type
        • Update strategy for writing to targets
        • Target type
        • Schedule for the session to run
        • Server on which you want the session to run
    • 28. CREATING SESSION
      • Use the Session Wizard to create a session for a valid mapping
      • The Session Wizard has five different pages
      • Each of those pages has multiple dialog boxes where you enter session properties
    • 29. CREATING SESSION
      • The Session Wizard has the following pages:
        • General page - Enter source and target information and performance configuration
        • Sources page - Enter source information for heterogeneous sessions
        • Time page - Schedule the session
        • Log Files page - Enter log file and error handling information
        • Transformation page - Override transformation properties
        • Partition page - Configure the session for partitioning
    • 30. CREATING SESSION
      • You can enter the name and directory for session log files and set error handling options on the log file page
    • 31. CREATING SESSION
      • This page allows you to override transformation attributes for the session
    • 32. CREATING SESSION
      • This page allows you to add and configure partitions based on source qualifiers
    • 33. CONFIGURING SOURCES
      • In the Server Manager, you can create sessions with the following sources:
        • Relational - You can extract data from any relational database that the Informatica Server can connect to
        • File - You can create a session to extract data from a flat file, COBOL, or XML source
        • Heterogeneous - You can extract data from multiple sources in the same session
      • Before you can extract data from a source, you must configure the connection properties the Informatica Server uses to connect to the source file or database
      • When the Informatica Server initializes a session, it allocates blocks of memory to hold source and target data
    • 34. CONFIGURING SOURCES
      • Configure source properties for sessions on the General tab of the session properties.
      • The General tab displays a Source area when you configure the session to access source data
    • 35. CONFIGURING SOURCES
      • The General tab has the following options:
      • Source type. By default, the Server Manager displays the source type based on the mapping properties.
      • Treat rows as - When the Informatica Server reads a source, it marks each row with an indicator to specify which operation to perform when the row reaches the target. Depending on following options, the Informatica Server:
        • Insert - marks all rows to insert into the target
        • Delete - marks all rows to delete from the target
        • Update - marks all rows to update the target
        • Data Driven - uses the Update Strategy transformation in the mapping to determine the operation on a row-by-row basis
      • Source options - When you click the Source options button, you can configure source options based on the session source type
      • Source database - For sessions with a relational source type, choose a configured database connection to connect to the source
    • 36. CONFIGURING RELATIONAL SOURCES
      • When you create a session with a relational source type, you can configure the following options for sources:
      • Source Database Connection - Select the database connection for the relational source
      • Source Options - Click the Source Options button to configure relational source options.
      • Override SQL Query - On the Transformations tab, you can override the default SQL query to extract source data
    • 37. CONFIGURING FILE SOURCES
      • The Source Options dialog box for file sources allows you to configure the following source properties:
        • Source Directory - Location of the file or files.
        • File List - Configure multiple file sources using a file list
        • FTP Connection
        • File Properties - Edit fixed-width or delimited source file properties
    • 38. CONFIGURING TARGETS
      • Configure target properties for sessions on the General tab of the session properties
      • The General tab displays a Target area where you configure the session to load target data
    • 39. CONFIGURING TARGETS
      • The general tab has the following options for target:
      • Target Type
        • By default, the Server Manager displays the target type based on the mapping properties
        • The target types are file, XML, and relational
        • You can change the target type for a session
      • Target Options - can configure target options based on the session target type
      • Reject Options - can configure the directories and files the Informatica Server writes rejected rows to
      • Target Database - For sessions with a relational target type, choose a configured database connection to connect to the target
    • 40. CONFIGURING RELATIONAL TARGETS
      • Can configure the following options for relational targets:
      • Target type
      • Target database connections
      • Target options – Insert, Update as Update, Update as Insert, Update else Insert, Delete, Truncate Table
      • Load options - Configure the session to use normal or bulk loading
      • Table name prefix - can specify the target owner name or prefix in the session properties to override the table name prefix in the mapping
      • Deadlock retry - can configure the session to retry deadlocks when writing to targets
      • Drop and recreate indexes
      • Constraint-based loading - can load data to targets based on primary-foreign key constraints
    • 41. CONFIGURING RELATIONAL TARGETS
      • The Targets dialog box appears when you click the Target Options button on the General page
      • The Informatica Server can truncate target tables before running a session. You can choose to truncate tables on a target-by-target basis within a session
      • If you select Normal as a Target Load Option then you can optionally perform a test load
      • With a test load, the Informatica Server reads and transforms data without writing to targets
    • 42. CONFIGURING FLAT FILE TARGETS
      • Can create a target definition for a flat file in the Warehouse Designer
      • The Warehouse Designer creates this definition as a relational target
      • When you configure a session to use this target definition, configure the target as a flat file in the Session Wizard
      • When the Informatica Server runs the session, it creates the target flat file and organizes the contents according to the columns specified in the target definition
    • 43. PRE AND POST SESSION COMMANDS
      • Pre-session commands:
        • Can specify operating system commands that need to be run on the server when the session starts
        • shell commands/.bat file should return 0 for success and non-zero(any positive) for failure
        • Good for dropping indexes and constraints on target tables, truncating tables, deleting .bad file
      • Post-session commands:
        • Specify any operating system commands that need to be run on the server when the session ends
        • Good for rebuilding indexes and dropping temporary tables
        • Can specify scripts for success and failure
    • 44. STARTING A SESSION
      • Can manually start a session that is configured to run on a set schedule or on demand
      • Can use either the Server Manager or the command line program pmcmd to start a session
      • To start a session in the Server Manager, you must have one of the following sets of privileges and permissions:
        • Create Sessions and Batches privilege with folder read and execute permission
        • Session Operator privilege with folder read permission
        • Super User privilege
        • Execute permission for global objects associated with the session
    • 45. SCHEDULING A SESSION
      • You can schedule a session to run continuously, run at a given time or interval, or you can manually start a session
      • The Informatica Server runs scheduled sessions through the duration of the schedule, unless the session fails
      • If the session is not heterogeneous, the Time tab appears directly after the General tab. If the session is heterogeneous, the Time tab appears after the Source Location tab
    • 46. SCHEDULING A SESSION
      • Event Based Scheduling - Can also configure a session to start after an indicator file appears in a directory
      • You might use this feature to start a session if you do not know when source data becomes available
      • To use event-based scheduling, you need a shell command, script, or batch file to create an indicator file when all sources are available
      • The file must be created or sent to a directory local to the Informatica Server
      • The file can be of any format recognized by the Informatica Server operating system
      • The Informatica Server deletes the indicator file once the session starts
    • 47. SCHEDULING A SESSION
      • If you manually start the session, the Informatica Server waits for the indicator file to appear before running the session
      • If you schedule the session, the Informatica Server waits for the first scheduled start time and then for the indicator file to appear before running the session
      • Once the indicator file appears:
        • If you scheduled the session and the scheduled start time has not arrived, the Informatica Server waits until the next scheduled session run, then starts the session
        • If you scheduled the session and the scheduled start time has passed, the Informatica Server starts the session immediately
        • If you started the session manually, the Informatica Server starts the session immediately
    • 48. MONITORING A SESSION
      • The Server Manager allows to monitor sessions on an Informatica Server
      • When monitoring a session, you can use information provided through the Server Manager to troubleshoot sessions and improve session performance
      • When you poll the Informatica Server, it indicates the following types of session status in the Monitor window:
        • Initializing - Indicates that the session is initializing
        • Scheduled - Indicates that the session is scheduled
        • Running - Indicates that the session is running
        • Completed - Indicates that the session completed successfully
        • Failed - Indicates that the session has failed
    • 49. MONITORING A SESSION
    • 50. MONITORING A SESSION
    • 51. MONITORING A SESSION
      • When you start a session, the Output window indicates whether the Informatica Server acknowledges your request to run the session
      • To monitor an Informatica Server, select it in the Navigator, then choose Server Configuration-Monitor
      • When you monitor an Informatica Server, you monitor all sessions configured to run on that Informatica Server
      • The sessions might be created in separate folders
      • The number of sessions you can monitor is determined by the number of sessions the Load Manager can store in shared memory
      • By default, the Informatica Server allocates 2,000,000 bytes of memory to monitor a maximum of 10 sessions
      • You can poll the Informatica Server continuously or one time only to display updated information about the sessions in the Monitor window
    • 52. MONITORING A SESSION
    • 53. MONITORING A SESSION
      • When you run a session, the Server Manager creates session details that provide load statistics for each target in the mapping
      • You can view session details during the session or after the session completes
    • 54. STOPPING OR ABORTING A SESSION
      • Can stop or abort a session
        • through the Server Manager
        • by using the command line program pmcmd
      • Can issue the stop or abort command in the Server Manager at any point during the session run
      • If the session you want to stop is a part of a batch, you must stop the batch to stop the session
      • If the session is part of a batch that is nested in a series of batches, you must stop the outermost batch to stop the session
      • When a stop command is issued, the Informatica Server stops reading data
      • It continues processing and writing data and committing data to targets
      • If the Informatica Server cannot finish processing and committing data, you can issue the abort command
    • 55. STOPPING OR ABORTING A SESSION
      • The Informatica Server handles the abort command like the stop command, except it has a 60 second timeout
      • If the Informatica Server cannot finish processing and committing data within 60 seconds, it kills the DTM process and terminates the session
      • After you stop or abort a session, you can recover the results of the session
      • When you perform recovery, the session continues from the point at which it stopped
      • If you do not recover the session, the Informatica Server runs the entire session the next time you schedule or start the session
    • 56. VALIDATING A SESSION
      • The Server Manager marks a session invalid if you perform one of the following tasks:
        • Edit the mapping in a way that might invalidate the session
        • Delete a database connection used by the session
        • Delete an FTP connection used by the session
        • Delete an external loader connection used by the session
        • Change the code page of a session database connection to an incompatible code page
      • To validate a session, open the session property sheet, make any necessary changes, then save and close the property sheet
      • The Server Manager does not validate SQL overrides or filter conditions entered in the session properties
    • 57. VALIDATING A SESSION
      • You can validate a specified set of sessions in a folder or validate all the invalid sessions in the folder
      • The Validate Sessions Wizard validates sessions associated with the following types of updated mappings:
        • You add a source to a mapping that does not require a specified database connection
        • You delete a source from the mapping
        • You add or delete a target from the mapping
        • You add or delete a source qualifier from the mapping
    • 58. COPYING A SESSION
      • In the Server Manager, you can copy sessions within a folder
      • You can also copy sessions to a different folder or repository by using the Copy Session Wizard
      • You can also copy sessions by exporting a session to an XML file and importing a session from the XML file
      • When copying a session to a different repository, the mapping for the session must exist in the target folder
      • When copying a session to a different repository, the session uses the global object permissions, database connection, FTP connection, external loader connection, and registered server of the same name if they exist in the target folder
      • If they do not exist, the wizard prompts you to select a new server or connection for the session
      • When you copy or import a session that has mapping variable values saved in the repository, the Server Manager either copies or retains the saved variable values
    • 59. HANDLING HIGH-PRECISION DATA
      • To enable high-precision data handling:
        • Use the Decimal datatype with a precision of 16 to 28 in the mapping
        • Enable high-precision handling by selecting Enable Decimal Arithmetic in the session property sheet
      • The precision attributed to a number also includes the scale of the number
      • For example, the value 11.47 has a precision of 4 and a scale of 2
      • If you want to process a Decimal value with a precision greater than 28 digits, the Informatica Server automatically treats it as a Double value
      • Do not use high-precision data handling for Microsoft SQL Server sources or targets. Microsoft SQL Server has a limitation that prevents the Informatica Server from writing decimal values with precision greater than 15
    • 60. BATCHES
      • Batches provide a way to group sessions for either serial or parallel execution by the Informatica Server
      • There are two types of batches:
        • Sequential - Runs sessions one after the other
        • Concurrent - Runs sessions at the same time
      • You might create a sequential batch if you have sessions with source-target dependencies that you want to run in a specific order
      • You might create a concurrent batch if you have several independent sessions you need scheduled at the same time
      • Can create, edit, start, schedule, and stop batches with the Server Manager
      • Cannot copy or abort batches
      • Each batch can contain any number of sessions or other batches
    • 61. BATCHES
      • Can nest batches several levels deep, defining batches within batches
      • When sessions are placed in a batch, the batch schedule overrides the session schedule by default
      • However, you can configure a batched session to run on its own schedule by selecting the Use Absolute Time session option
      • Can configure sessions in a sequential batch as:
        • run only if the previous session completes
        • always run the session
      • When you run a sequential batch, the Informatica Server runs the sessions in the order they appear in the Navigator, from top to bottom
      • Concurrent batches take advantage of the resources of the Informatica Server, reducing the time it takes to run the sessions separately or in a sequential batch
    • 62. BATCHES
      • Can club Concurrent Batches in a Sequential Batch and vice-a-versa
      • The Informatica Server configured to run a batch overrides the Informatica Server configuration to run sessions within the batch
      • If you have multiple servers, all of the sessions within a batch run on the Informatica Server that runs the batch
      • The Informatica Server recognizes all other session options and performs them accordingly
      • The Informatica Server marks a batch as failed if one of its sessions is configured to “run if previous completes” and that previous session fails
    • 63. BATCHES
      • After you start a batch, you can stop a batch through the Server Manager or by using pmcmd
      • When a batch is stopped, the Informatica Server immediately stops
        • reading sources
        • processing data in the DTM data flow
        • writing to targets for all running and initializing sessions
      • After you stop a batch, you can recover the results of the sessions in the batch
      • When you perform recovery, the session continues from the point at which it stopped
      • If the batch is nested in a series of batches, stop the outermost batch to stop the batch
    • 64. SESSION PARAMETERS
      • You can use a parameter file to define the values for parameters and variables used in a session
      • A parameter file is a file created by a text editor such as WordPad or Notepad
      • In the parameter file, you specify the folder and session name, then list the parameters and variables used in the session and assign each a value
      • Save the parameter file in any directory local to the Informatica Server
      • Enter the parameter file name and directory in the session property sheet
    • 65. SESSION PARAMETERS
      • You can use $PMSessionLogFile to change the session log name between sessions
      • On the Log and Error Handling tab of the session property sheet, enter $PMSessionLogFile in the Session Log Name field
      • Then define $PMSessionLogFile in the session parameter file
    • 66. SESSION PARAMETERS
      • You can create user-defined database connection session parameters to reuse sessions for different relational sources or targets
      • Name all database connection session parameters with the prefix $DBConnection, followed by any alphanumeric and underscore characters
    • 67. PARTITIONING DATA
      • Data partitioning is only available with PowerCenter
      • The Informatica Server can achieve high performance
        • by partitioning source data
        • by performing the extract, transformation, and load for each partition in parallel
      • For relational sources, the Informatica Server creates multiple database connections to a single source and extracts a separate range of data for each connection
      • For XML or file sources, the Informatica server reads multiple files concurrently
      • When the Informatica Server loads relational data, it creates multiple database connections to the target and loads partitions of data concurrently
      • The Informatica Server cannot partition sources that might result in data inconsistencies, such as the master source for a Joiner transformation
    • 68. PARTITIONING DATA
    • 69. PARTITIONING DATA
      • The Partitions tab allows you to add and configure partitions based on source qualifiers
      • You can choose to partition some source qualifiers and leave others unpartitioned
      • You can configure the following types of information on the Partitions tab:
        • Add and delete partitions - When you partition a source qualifier, you must create at least two partitions. You can add up to 16 partitions for each source qualifier
        • Enter descriptions
        • Add keys and key ranges - Use keys and key ranges to configure the WHERE clause for relational sources
        • Enter source attributes - Configure source attributes specific to the type of source you partition
        • Enter target attributes - Configure target attributes specific to the type of target in the mapping
    • 70. PARTITIONING DATA
      • When you run a session that partitions relational or ERP sources, the Informatica Server creates a separate connection to the source database for each partition
      • It then creates a SQL query for each partition according to the parameters in the Partitions tab
      • When you customize the SQL statement in the Partitions tab, you override any customized SQL queries
      • Informatica supports all databases that allow multiple concurrent connections to a table
      • If you partition a session that loads to a database or ODBC target that does not support multiple concurrent connections to tables, the session fails
      • When you partition a session that loads data to an Informix database, you must create the target table with row-level locking
    • 71. PARTITIONING DATA
      • Can partition a mapping with file sources when you want to extract data from multiple files that have the same structure
      • Can partition flat files, XML files, and COBOL files
      • The Server Manager generates a default file name and location for each partition
      • The file name is based on the source file name and the partition number
      • The location is $PMSourceFileDir
      • When you run the session, the Informatica Server reads the files concurrently
    • 72. PARTITIONING DATA
      • You can use a file list when you need to extract from more than 16 files
      • For example, you have 18 web logs with identical structure. You create two partitions to read file lists that contain two files. The remaining 14 partitions each read one file. The Informatica Server concurrently reads the two file lists and files 3 through 16
      • It sequentially reads the files in the lists
    • 73. PMCMD
      • Can use the command line program pmcmd to communicate with the Informatica Server
      • Can perform the following actions with pmcmd :
        • Determine if the Informatica Server is running
        • Start sessions and batches
        • Stop sessions and batches
        • Recover sessions
        • Stop the Informatica Server
      • Can configure repository usernames and passwords as environmental variables with pmcmd
      • can also customize the way pmcmd displays the date and time on the machine running the Informatica Server
      • pmcmd returns zero on success and non-zero on failure
      • You can use pmcmd with operating system scheduling tools like cron to schedule sessions, and you can embed pmcmd into shell scripts or Perl programs to run or schedule sessions
    • 74. PMCMD
      • Need the following information to use pmcmd :
        • Repository username
        • Repository password
        • Connection type - The type of connection from the client machine to the Informatica Server
        • Port or connection - The TCP/IP port number or IPX/SPX connection (Windows NT/2000 only) to the Informatica Server
        • Host name - The machine hosting the Informatica Server
        • Session or batch name - The names of any sessions or batches you want to start or stop
        • Folder name - The folder names for those sessions or batches
        • Parameter file
      • Can configure the following environmental variables to use with pmcmd :
        • PM_CODEPAGENAME
        • PMTOOL_DATEFORMAT
    • 75. REJECT LOADING
      • During a session, the Informatica Server creates a reject file for each target instance in the mapping
      • If the writer or the target rejects data, the Informatica Server writes the rejected row into the reject file
      • Can correct reject files and load them to relational targets using the Informatica reject loader utility
      • The reject loader also creates another reject file for the data that the writer or target reject during the reject loading
      • Each time you run a session, the Informatica Server appends rejected data to the reject file
      • The Informatica Server creates reject files for each target instance in the mapping
      • You cannot load rejected data into a flat file target
    • 76. REJECT LOADING
      • The Informatica Server creates reject files in the session reject file directory, as configured on the Log Files tab of the session property sheet
      • By default, the Informatica Server creates reject files in the $PMBadFileDir server variable directory
      • The Informatica Server names reject files after the target instance name, the default name is target instance .bad
    • 77. COMMIT POINTS
      • A commit interval is the interval at which the Informatica Server commits data to relational targets during a session
      • The commit point can be a factor of the commit interval, the commit interval type, and the size of the buffer blocks
      • The commit interval is the number of rows you want to use as a basis for the commit point
      • The commit interval type is the type of rows that you want to use as a basis for the commit point
      • Can choose between the following types of commit interval
        • Target-based commit
        • Source-based commit
      • During a source-based commit session, the Informatica Server commits data to the target based on the number of rows from an active source in a single pipeline
    • 78. COMMIT POINTS
      • During a target-based commit session, the Informatica Server continues to fill the writer buffer after it reaches the commit interval
      • When the buffer block is filled, the Informatica Server issues a commit command
      • As a result, the amount of data committed at the commit point generally exceeds the commit interval
    • 79. COMMIT POINTS
      • During a source-based commit session, the Informatica Server commits data to the target based on the number of rows from an active source in a single pipeline
      • These rows are referred to as source rows
      • A pipeline consists of a source qualifier and all the transformations and targets that receive data from the source qualifier
      • An active source can be any of the following active transformations:
        • Advanced External Procedure
        • Source Qualifier
        • Normalizer
        • Aggregator
        • Joiner
        • Rank
        • Mapplet, if it contains one of the above transformations
    • 80. COMMIT POINTS
      • When the Informatica Server runs a source-based commit session, it identifies the active source for each pipeline in the mapping
      • The Informatica Server generates a commit row from the active source at every commit interval
      • When each target in the pipeline receives the commit row, the Informatica Server performs the commit
    • 81. COMMIT POINTS
    • 82. SESSION LOG FILE
      • The Informatica Server creates a session log file for each session it runs
      • The amount of detail in the session log depends on the error tracing level that you set
      • The session log contains the following information about a session:
        • Allocation of system shared memory
        • Execution of pre-session commands
        • Session initialization
        • Creation of SQL commands for reader and writer threads
        • Start and end times for target loading
        • Errors encountered during session
        • Execution of post-session commands
        • Load summary of reader, writer, and (DTM) statistics
    • 83. MULTIPLE SERVERS
      • You can register multiple PowerCenter Servers with a PowerCenter repository
      • Can run these servers at the same time
      • Can distribute the repository session load across available servers to improve overall performance
      • Can use the Server Manager to administer and monitor multiple servers
      • With multiple Informatica Servers, you need to decide which server you want to run each session and batch
      • You can register and run only one PowerMart Server in a local repository
      • Cannot start a PowerMart Server if it is registered in a local repository that has multiple servers registered to it
    • 84. MULTIPLE SERVERS
      • When attached to multiple servers, you can only view, or monitor , one Informatica Server at a time, but you have access to all the servers in the repository

    ×