KB Help

Using PowerChannel to Transfer Data Between PowerCenter on UNIX and Excel, Access, and SQL Server
Content
When you run the PowerCenter Server on UNIX, your access to application data on Windows systems is limited. There is no direct method of accessing data from MS Excel and MS Access. Connections to MS SQL Server must be established through an ODBC driver. When you use an ODBC connection to access SQL Server, the PowerCenter Server uses ODBC datatypes instead of native SQL Server datatypes. Also, ODBC configuration must be completed for each instance of the PowerCenter Server running on UNIX. PowerChannel enables the PowerCenter Server on UNIX to efficiently transfer data to and from Excel, Access, and SQL Server. The PowerCenter Server running on UNIX can access a SQL Server database using the native driver. It can also use PowerChannel to read data from Excel and Access and write data to Excel and Access.

Advantages of Using PowerChannel to Access Windows Applications

You can use PowerChannel to transfer data between Access, Excel, or SQL Server and the PowerCenter Server on UNIX. The following advantages apply when you use PowerChannel to allow the PowerCenter Server to read data from Access, Excel, and SQL Server and write data to Access, Excel, and SQL Server:
l l

PowerChannel offers compression and encryption capabilities For SQL Server, you do not need to perform any ODBC configuration.PowerChannel accesses SQL Server through native datatypes.

ConfiguringPowerChanneltoReadandWriteAccess,Excel,andSQLServerData
Before you can access Windows application data using the PowerCenter Server on UNIX, you need to install and configure the remote PowerChannel Server on a Windows system that can connect to the machine with Access, Excel, or SQL Server data. The PowerCenter Server uses the PowerChannel Server to access the application data. Figure 1 shows data transfer between the PowerCenter Server on UNIX and a Windows Application:

Figure 1. Transferring Data Between the PowerCenter Server on UNIX and a Windows Application

Optionally, you can configure a local PowerChannel Server to allow compression and encryption during data transfer. Figure 2 shows data transfer between the PowerCenter Server on UNIX and a Windows Application using compression and encryption:

Figure 2. Transferring Compressed and Encrypted Data Between the PowerCenter Server on UNIX and a Windows Application

For more information on installing and configuring PowerChannel refer to the PowerChannel User Guide.

Repository Administration

Register the pmpchrdb.xml plug-infilethatisinstalledbythePowerChannelinstallationinthePowerCenterrepository.

Importing and Creating Source and Target Definitions

The PowerCenter Designer uses an ODBCconnection to the source or target system to fetch applicationmetadata. For Access and SQL Server, the DSN connection specifies the database instance. For Excel, the DSN connection specifies the workbook instance. You can use the Source Analyzer to import source definitions for Access, Excel, and SQL Server. You can also use the Source Analyzer to create source definitions for Access and SQL Server. You can use the Warehouse Designer to import target definitions for Access, Excel, and SQL Server. You can also use the Warehouse Designer to create target definitions for Access and SQL Server. After importing or creating source or targetdefinitions for Access, Excel, or SQL Server, you can create mappings to allow the PowerCenter Server on UNIX to read or write Windows application data.

Workflow Manager
You need to create a PowerChannel connection to connect to Access, Excel, or SQL Server system. Use a PowerChannel for ODBC connection for MS Access or Excel. When you want to connect to SQL Server, use the PowerChannel for MS SQL Server connection. When you configure the Remote PowerChannel Host Name property for the PowerChannel connection in the Workflow Manager, specify the host name of the remote PowerChannel Server that is configured to access the Windows application. If you want to enable compression or encryption while transferring application data, you also need to specify the host name of the local PowerChannel Server to which the PowerCenter Server can connect.

PowerChannel Connection Properties

You can read or write Access, Excel, or SQL Server data through PowerChannel by configuring the following PowerChannel connection properties in the Workflow Manager:
l l l l l l l l

Remote PowerChannel Host Name Remote PowerChannel Port Number Use Local PowerChannel Local PowerChannel Host Name Local PowerChannel Port Number Encryption Level Compression Level Certificate Account

Figure 3 shows the PowerChannel for MS SQL Server connection:

Figure 3. PowerChannel for MS SQL Server Connection

The PowerCenter Server always connects to the transport listener port of the PowerChannel Server. When you use a local PowerChannel Server to transfer data between the PowerCenter Server and a remote database server, the PowerCenter Server connects to the local PowerChannel Server, and you can specify a transport port or admin port for the remote PowerChannel port number property. When you do not use a local PowerChannel Server, the PowerCenter Server connects to the transport listener on the remote PowerChannel Server directly.

Configuring Connectivity for Access, Excel and SQL Server

Before you can use PowerChannel to transfer data between the PowerCenter Server running on UNIX and Access, Excel, or SQL Server, you need to configure connectivity for the Windows application.

Access
For each database from which you want to read data or to which you want to write data, use the ODBC Administrator to create a connection. 1. 2. 3. 4. Add a new system DSN. Choose Microsoft Access Driver. Specify a name for the DSN. The DSN name is used as the Connect String property of the Workflow Connection configuration. Select a database to specify the Access database.

Excel
For each workbook from which you want to read data or to which you want to write data, use the ODBC Administrator to create a connection. 1. 2. 3. 4. 5. 6. Add a new system DSN. Choose Microsoft Excel Driver. Specify a name for the DSN. The DSN name is used as the Connect String property of the Workflow Connection configuration. Choose the version for the EXCEL Workbook. Select the actual workbook that you want the PowerCenter Server to read or write. If the Excel sheet is a target for PowerChannel, deselect the Read-Only option.

SQL Server
When you want to transfer data between SQL Server and the PowerCenter Server on UNIX, you need to create the following two connections:
l l

SQL Server native connection. Use this connection to transfer data between the PowerCenter Server and SQL Server. SQL Server ODBC connection. Use this connection to import source and target metadata into the Designer from SQL Server.

Native Connection
PowerChannel uses the native connection to SQL Server to access the SQL Server databases. Make sure that the appropriate SQL Server client is installed on the same machine. Test the connection to the database by establishing a connection via the Query Analyzer or using the isql command.

ODBC Connection
The Designer uses the ODBC connection to import SQL Server source and target definitions. Before you can read data from SQL Server or write data to SQL Server, you need to use the ODBC Administrator to create a connection to each database you want to import. 1. 2. 3. Add a new system DSN. Choose SQL Server driver. Specify a name for the DSN.

The DSN name is used as the Connect String of the Workflow Connection configuration if the user chooses the PowerChannel for ODBC Connection type. 1. 2. 3. Specify the host name in the Server property. Choose SQL Server connection, and specify the user id and password. Choose the database that you want to access, and click on the Test Connection button. Make sure that the connection test is successful.

Applies To
Database: Access, Excel, Microsoft SQL Server Product: PowerChannel