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.
![INFORMATICA SERVER AND DATA MOVEMENT ,[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)