powerchannel-kb-15238

8/2/2019 PowerChannel-KB-15238

1/3

KB Help

Using Pow erChanne l t o T rans fe r Da ta Be tw een PowerCente r on UNI X and Excel ,Access, and SQL Server

ContentWhen 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 Pow erChannel t o Access Window s Appl icat ions

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 PowerChannel offers compression and encryption capabilities

l For SQL Server, you do not need to perform any ODBC configuration.PowerChannel accesses SQL Server through native

datatypes.

Configuring PowerChannel to Read and Write Access, Excel, and SQL Server Data

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:

F igure 1 . T rans fe r r i ng Data Be tween t he PowerCente r Serv er on UNI X and a W indow s App l i ca t i on

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:

F igure 2 . T rans fe r r i ng Compres s ed and Enc ry p ted Data Be tw een t he PowerCente r Serv er on UNIX and aWindow s App l i c a t i on

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

Repository Admin is t ra t ion


2/3

Register the pmpchrdb.xml plug-in file that is installed by the PowerChannel installation in the PowerCenter repository.

I mp or t ing and Creat ing Source and Target Def in i t ions

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.

W o r k f l o w M a n ag e r

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.

Power Chann el Connec t ion Proper t ies

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 Remote PowerChannel Host Name

l Remote PowerChannel Port Number

l Use Local PowerChannel

l Local PowerChannel Host Name

l Local PowerChannel Port Number

l Encryption Level

l Compression Level

l Certificate Account

Figure 3 shows the PowerChannel for MS SQL Server connection:

Figure 3. Pow erChannel for MS SQL Server Connec t ion

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.

Conf ig ur ing Connect iv i t y 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.


3/3

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. Add a new system DSN.

2. Choose Microsoft Access Driver.

3. Specify a name for the DSN.

The DSN name is used as the Connect String property of the Workflow Connection configuration.

4. 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.


2. Choose Microsoft Excel Driver.


The DSN name is used as the Connect String property of the Workflow Connection configuration.

4. Choose the version for the EXCEL Workbook.

5. Select the actual workbook that you want the PowerCenter Server to read or write.

6. 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 S QL Se rve r n a t i ve co n n e c t i o n . Use this connection to transfer data between the PowerCenter Server and SQL Server.

l SQL Server ODBC connect ion . Use this connection to import source and target metadata into the Designer from SQL Server.

Nat ive Connec t ion

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 isqlcommand.

ODBC Connect ion

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.


2. Choose SQL Server driver.


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. Specify the host name in the Server property.

2. Choose SQL Server connection, and specify the user id and password.

3. Choose the database that you want to access, and click on the Test Connection button. Make sure that the connection test is

successful.

Appl ies To

D a t a b a se : Access, Excel, Microsoft SQL Server

P ro d u c t : PowerChannel

powerchannel-kb-15238

Documents