Professional Documents
Culture Documents
0)
User Guide
Informatica PowerChannel User Guide
Version 9 .0
December 2009
This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement
containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited.
No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise)
without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or international Patents and other Patents
Pending.
Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software
license agreement and as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013 ©(1)(ii) (OCT 1988), FAR
12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.
The information in this product or documentation is subject to change without notice. If you find any problems in this product or
documentation, please report them to us in writing.
Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data
Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data
Transformation, Informatica B2B Data Exchange and Informatica On Demand are trademarks or registered trademarks of Informatica
Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or
trademarks of their respective owners.
Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright
DataDirect Technologies. All rights reserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights
Reserved. Copyright © Ordinal Technology Corp. All rights reserved.Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc.
All rights reserved. Copyright 2007 Isomorphic Software. All rights reserved. Copyright © Meta Integration Technology, Inc. All rights
reserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems Incorporated. All
rights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © Microsoft
Corporation. All rights reserved. Copyright © Rouge Wave Software, Inc. All rights reserved. Copyright © Teradata Corporation. All rights
reserved. Copyright © Yahoo! Inc. All rights reserved. Copyright © Glyph & Cog, LLC. All rights reserved.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and other software which is
licensed under the Apache License, Version 2.0 (the "License"). You may obtain a copy of the License at http://www.apache.org/licenses/
LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS
IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific
language governing permissions and limitations under the License.
This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all
rights reserved; software copyright © 1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under the
GNU Lesser General Public License Agreement, which may be found at http://www.gnu.org/licenses/lgpl.html. The materials are provided
free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied
warranties of merchantability and fitness for a particular purpose.
The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington
University, University of California, Irvine, and Vanderbilt University, Copyright ( ©) 1993-2006, all rights reserved.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All
Rights Reserved) and redistribution of this software is subject to terms available at http://www.openssl.org.
This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved.
Permissions and limitations regarding this software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to
use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright
notice and this permission notice appear in all copies.
The product includes software copyright 2001-2005 ( ©) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this
software are subject to terms available at http://www.dom4j.org/ license.html.
The product includes software copyright © 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding
this software are subject to terms available at http:// svn.dojotoolkit.org/dojo/trunk/LICENSE.
This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved.
Permissions and limitations regarding this software are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/
license.html.
This product includes software copyright © 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the
license which may be found at http://www.gnu.org/software/ kawa/Software-License.html.
This product includes OSSP UUID software which is Copyright © 2002 Ralf S. Engelschall, Copyright © 2002 The OSSP Project
Copyright © 2002 Cable & Wireless Deutschland. Permissions and limitations regarding this software are subject to terms available at
http://www.opensource.org/licenses/mit-license.php.
This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and
limitations regarding this software are subject to terms available at http:/ /www.boost.org/LICENSE_1_0.txt.
This product includes software copyright © 1997-2007 University of Cambridge. Permissions and limitations regarding this software are
subject to terms available at http://www.pcre.org/license.txt.
This product includes software copyright © 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this
software are subject to terms available at http:// www.eclipse.org/org/documents/epl-v10.php.
This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/
overlib/?License, http://www.stlport.org/doc/license.html, http://www.asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT,
http://hsqldb.org/web/hsqlLicense.html, http://httpunit.sourceforge.net/doc/license.html, http://jung.sourceforge.net/license.txt , http://
www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/release/license.html, http://www.libssh2.org, http://slf4j.org/
license.html, and http://www.sente.ch/software/OpenSourceLicense.htm.
This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common
Development and Distribution License (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://
www.opensource.org/licenses/cpl1.0.php) and the BSD License (http://www.opensource.org/licenses/bsd-license.php).
This product includes software copyright © 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and
limitations regarding this software are subject to terms available at http://xstream.codehaus.org/license.html. This product includes
software developed by the Indiana University Extreme! Lab. For further information please visit http://www.extreme.indiana.edu/.
This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374;
6,092,086; 6,208,990; 6,339,775; 6,640,226; 6,789,096; 6,820,077; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,254,590; 7,
281,001; 7,421,458; and 7,584,422, international Patents and other Patents Pending..
DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied,
including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. Informatica
Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation
may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at
any time without notice.
NOTICES
This Informatica product (the “Software”) includes certain drivers (the “DataDirect Drivers”) from DataDirect Technologies, an operating company of Progress Software
Corporation (“DataDirect”) which are subject to the following terms and conditions:
1. THE DATADIRECT DRIVERS ARE PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF
THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH
OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica Customer Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Informatica Multimedia Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Table of Contents i
Starting the PowerChannel Server as a Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Starting the PowerChannel Server as an Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Running PowerChannel Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Running Web Client Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Running PcCmd Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Restoring the Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Uninstalling PowerChannel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Troubleshooting a PowerChannel Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
ii Table of Contents
Chapter 5: Configuring PcCmd Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Configuring PcCmd Properties Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Configuring PcCmd Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
SERVER_ADDRESS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
SERVER_PORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
PCCMD_LOG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
USERNAME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
PASSWORD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
SESSION_NAME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
COMPRESSION_LEVEL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
ENCRYPTION_LEVEL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
CHECKSUM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
CODE_PAGE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
HOSTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
STAGE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
CRYPTOGRAPHY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Configuring the PcCmd Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
iv Table of Contents
XML Command File Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Table of Contents v
Preface
The Informatica PowerChannel User Guide provides information to install and configure PowerChannel, administer
the PowerChannel repository, transfer data from sources to targets, and manage PowerChannel sessions. It is
written for information services developers and software engineers who are responsible for extracting data from
different sources to implement a data warehouse.
Informatica Resources
Informatica Documentation
The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have
questions, comments, or ideas about this documentation, contact the Informatica Documentation team through
email at infa_documentation@informatica.com. We will use your feedback to improve our documentation. Let us
know if we can contact you regarding your comments.
The Documentation team updates documentation as needed. To get the latest documentation for your product,
navigate to the Informatica Documentation Center from http://my.informatica.com.
vi
Informatica Knowledge Base
As an Informatica customer, you can access the Informatica Knowledge Base at http://my.informatica.com. Use
the Knowledge Base to search for documented solutions to known technical issues about Informatica products.
You can also find answers to frequently asked questions, technical white papers, and technical tips. If you have
questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team through
email at KB_Feedback@informatica.com.
Use the following telephone numbers to contact Informatica Global Customer Support:
North America / South America Europe / Middle East / Africa Asia / Australia
Preface vii
viii
CHAPTER 1
Understanding PowerChannel
This chapter includes the following topics:
¨ PowerChannel Architecture, 3
You can transfer files between PowerChannel Servers and between FTP clients and servers. PowerChannel also
lets you read flat file and relational source data and write flat file and relational target data during a PowerCenter
session. You can transfer relational data between PowerCenter and a database on a local area network (LAN) or
WAN. You can also transfer the database data in compressed and encrypted format.
PowerChannel Concepts
PowerChannel uses the following concepts to ensure fast, secure, and reliable data transfer:
¨ File integrity
¨ Recovery
¨ User authentication
¨ Server authentication
1
RELATED TOPICS:
¨ “PowerChannel Protocol” on page 25
User Authentication
When you run a command to run a PowerChannel task, you enter a PowerChannel user account name and
password as part of the command parameters. The PowerChannel Server uses the user account name and
password to authenticate you as a valid PowerChannel user. When the authentication succeeds, the
PowerChannel Server runs the user command. PowerChannel clients use a secure protocol to communicate with
the server. It exchanges data with the server in encrypted format.
Server Authentication
When you transfer data from a local PowerChannel Server to a remote PowerChannel Server, the remote server
must authenticate the local server as a trusted server. To send data to a remote server, the local server must have
a certificate account in the remote PowerChannel repository. When you run a command to transfer data, you enter
the remote PowerChannel certificate account name as part of the command parameters. The remote
PowerChannel Server uses the certificate account name to authenticate the local server. When the authentication
succeeds, data transfer can begin. The local server communicates with the remote server using a secure protocol.
It exchanges data with the remote server in encrypted format.
File Integrity
PowerChannel ensures that when you transfer files, the file you transfer is intact and secure during file transfer.
With integrity checking, you can make sure that no third party tampers with the file while it is in transit. This
prevents the file from data corruption during file transfer. PowerChannel uses the CR32 checksum algorithm to
perform integrity checking.
Recovery
PowerChannel lets you recover sessions that fail due to errors. When data transfer between PowerChannel
Servers fails due to network failure, PowerChannel can recover the session. If the PowerChannel Server cannot
recover the session, the PowerChannel session fails. When the PowerChannel Server cannot recover a failed file
transfer PowerChannel session, use manual recovery.
RELATED TOPICS:
¨ “Recovering PowerChannel Sessions” on page 79
¨ PowerChannel clients. PowerChannel uses a web client and the PcCmd command line program to run
commands to the PowerChannel Server.
¨ PowerChannel Server. PowerChannel implementation requires a PowerChannel Server installation at the
remote site. When you use PowerChannel to read or write flat file data, or when you want to compress or
encrypt data using PowerChannel, you also need to install a PowerChannel Server at the local site. The
PowerChannel Server listens to requests from PcCmd, the web client, the PowerCenter Client, and remote
PowerChannel Servers to run PowerChannel sessions.
¨ PowerChannel repository. PowerChannel uses an encrypted repository that stores information about
PowerChannel accounts and sessions.
¨ PowerChannel properties files. The PowerChannel Server and clients use a set of properties files. Use the
default values set values in the properties files to run the PowerChannel Server and clients using a
configuration utility.
PowerChannel Clients
PowerChannel uses the following client applications to run commands to the PowerChannel Server:
¨ Web client
¨ PcCmd
Web Client
Use the PowerChannel web client to manage PowerChannel accounts and sessions and stop the PowerChannel
Server from a web browser. When you run a command from the web client, the web client translates the command
into an XML request and passes the request to the PowerChannel Server. The server receives the request and
runs the user command.
PcCmd
PcCmd is the command line program you use to run commands to the PowerChannel Server. Use PcCmd
commands to run PowerChannel tasks. When you run a PcCmd command, PcCmd translates the command into
an XML request and passes the request to the server. The server receives the request and runs the user
command.
You can run PcCmd from the machine hosting the PowerChannel Server or on a client machine. To use PcCmd,
you must have a valid user account in the PowerChannel repository. PcCmd communicates with the server using a
secure protocol. It exchanges data with the server in encrypted format for security.
¨ Transfer files. Use PcCmd to run commands to transfer files between PowerChannel Servers. You can also
use PcCmd to create a PowerChannel connection to transfer files between the Integration Service and an FTP
server or between FTP clients and servers.
¨ Administer PowerChannel accounts. Use PcCmd to administer PowerChannel accounts in the repository.
¨ Manage PowerChannel sessions. Use PcCmd to manage PowerChannel sessions in the PowerChannel
repository.
PowerChannel Architecture 3
¨ Run an XML command file. Use PcCmd to run an XML command file. An XML command file lets you run file
transfer commands from an XML file. When you use an XML command file, you have more flexibility in
structuring commands.
¨ Stop the PowerChannel Server. Use PcCmd to stop the PowerChannel Server.
PowerChannel Server
The PowerChannel Server reads and writes flat file and database data. The server listens to user requests from
PcCmd, the web client, the Integration Service, and remote PowerChannel Servers on a listener port and runs
PowerChannel sessions to complete the tasks. When you read or write flat file data or use compression or
encryption, install a PowerChannel Server in the same LAN as the Integration Service. You also need to install a
PowerChannel Server in the same LAN as the remote source or target. Local and remote PowerChannel Servers
communicate with the TCP/IP protocol.
When you want to read flat file data in compressed and encrypted format, the remote PowerChannel Server reads,
compresses and encrypts the data from the source. Then it sends the data to the local PowerChannel Server. The
local PowerChannel Server decompresses and decrypts the flat file data and sends it to the Integration Service.
Similarly, when you want to write flat file data in compressed and encrypted format, the local PowerChannel
Server receives data from the Integration Service. It compresses and encrypts the data before sending it to the
remote PowerChannel Server. The remote PowerChannel Server decrypts and decompresses the data. The
remote PowerChannel Server then writes the data to the target. You can administer the PowerChannel Server
from the PowerChannel command line.
RELATED TOPICS:
¨ “Administering the PowerChannel Server” on page 24
PowerChannel Repository
The PowerChannel Server creates an encrypted file-based repository during installation. It creates the
PowerChannel repository in the repository folder under the PowerChannel root directory. The PowerChannel
repository stores information that the PowerChannel Server, web client, and PcCmd use to run commands.
¨ PowerChannel accounts
¨ PowerChannel sessions
Accounts
PowerChannel uses accounts to authenticate users and PowerChannel Servers. PowerChannel uses user
accounts to run PowerChannel commands and certificate accounts to authenticate remote PowerChannel Servers.
To run PowerChannel commands, you must have a user account in the PowerChannel repository. User accounts
require a password for authentication. When you run a command, you provide the PowerChannel user account
name and password as part of the command parameters. Or, you provide the PowerChannel account name and
password in the PowerChannel properties files.
To communicate with remote PowerChannel Servers to transfer data, a PowerChannel Server uses a certificate
account to authenticate itself as a valid server. To send data to a remote server, the local PowerChannel Server
must have a certificate account in the remote PowerChannel repository.
Certificate accounts use account profiles to define privileges for the PowerChannel accounts. A certificate account
can have a profile of oneway or twoway.
RELATED TOPICS:
¨ “Certificate Accounts” on page 17
Sessions
The PowerChannel repository also stores information about PowerChannel sessions. A PowerChannel session
includes tasks that the PowerChannel Server completes when it receives a request from PcCmd, the web client,
the PowerCenter Client, or a remote PowerChannel Server. For example, the Integration Service starts a session
to write flat file data through PowerChannel. When the local PowerChannel Server receives the request, it initiates
a session to write the flat file to a remote PowerChannel Server. The PowerChannel repository stores session
information for PowerChannel session recovery purposes.
RELATED TOPICS:
¨ “Managing PowerChannel Sessions” on page 74
The following table describes the properties files for the PowerChannel Server and clients:
PcWeb.properties Web client uses this properties file to run web client commands.
PowerChannel Architecture 5
CHAPTER 2
¨ Uninstalling PowerChannel, 14
The PowerChannel Server communicates with PcCmd, the web client, the Integration Service, and other
PowerChannel Servers using the TCP/IP protocol. Install the PowerChannel Server, PcCmd, the web client, and
the Integration Service on a network that can establish TCP/IP connections.
You can configure PowerCenter to use PowerChannel to transfer data between the PowerCenter Integration
Service and remote databases.
Install the PowerChannel Server on a machine with a static IP address. Otherwise, you cannot use default server
parameters for PowerChannel. To install PowerChannel, you must have knowledge of Java installation.
You can install and run PowerChannel as a service or an application. To run PowerChannel as a service, you
must install the PowerChannel Server on Windows. When you install PowerChannel as a service, the
PowerChannel Server starts when you log in to Windows. It also stops when you shut down Windows. When you
run PowerChannel as an application, you must start and stop the PowerChannel Server manually.
6
Minimum System Requirements
The following table describes the system requirements to run the PowerChannel Server and clients:
PowerChannel Windows, 128 MB Install the PowerChannel Server on Windows or UNIX (Solaris, HP-UX,
Server UNIX AIX, Linux).
PcCmd Windows, 64 MB Install PcCmd on Windows or UNIX (Solaris, HP-UX, AIX, Linux). You
UNIX can install PcCmd on the machine running the PowerChannel Server or
on client machines that can access the local PowerChannel Server.
Web Client Windows 64 MB Install the web client on Windows. You can install the web client on the
machine running the PowerChannel Server or on a Windows client
machine that can access the local PowerChannel Server.
The web client requires BEA WebLogic Server. Make sure a web server
is installed on the web client machine.
PowerChannel uses Java Runtime Environment (JRE). The installation program installs JRE when you install
PowerChannel.
¨ Install and configure BEA WebLogic Server. Install and configure BEA WebLogic Server.
¨ Install a web browser. You must install a web browser on the machine from which you want to access the web
client.
Complete the following task if you want to read data from a remote source or write data to a remote target during a
PowerCenter session:
¨ Install PowerCenter. When you want PowerChannel to read data from a remote source or write data to a
remote source during a PowerChannel session, you need to install and configure PowerCenter.
¨ RC2.
¨ 3DES. Select 3DES when you want the PowerChannel Server to use FIPS-certified 3DES encryption.
After you select the encryption algorithm, the following information applies:
¨ After you install the PowerChannel repository, you cannot change the encryption algorithm for that repository.
To change the encryption algorithm, you must copy the sample repository provided for the encryption algorithm
and replace the default repository. You must also change the encryption algorithm in the PowerChannel and
PcCmd properties files using the configuration utility.
¨ PowerChannel Servers and their clients must use the same encryption algorithm to communicate with each
other.
¨ PowerChannel Servers must use the same encryption algorithm to communicate with each other.
Note: Select the encryption algorithm you used in the previous version of PowerChannel. Select 3DES when you
want the PowerChannel Server to use FIPS-certified 3DES encryption.
The installation program includes a user name and password in the sample repository that you can use to
administer the PowerChannel Server and transfer data. The sample repository uses the following user name and
password:
¨ Password: Administrator
The PowerChannel installation also includes a default certificate account with a twoway profile in the sample
repository. The default certificate account allows PowerChannel Servers that use the sample repository to transfer
data with each other. After you install PowerChannel, you can start the PowerChannel Server, run PowerChannel
commands, and transfer data.
Warning: Using the admin user and default certificate account to run PowerChannel does not ensure a secure
data transfer environment. If you do not require a secure data transfer environment, you can continue to use the
admin user and default certificate account to run PowerChannel. If you want to ensure a secure data transfer
environment, you must implement the following security measures into the PowerChannel sample repository:
1. Install PowerChannel.
2. Optionally, configure the web client on BEA WebLogic Server.
3. Start the PowerChannel Server.
1. Install the PowerChannel Server on the same network as the remote database from which you want to read
data or write data. Install the PowerChannel Server on the same machine as the remote database.
2. Optionally, install a PowerChannel Server on the same network as the Integration Service when you want the
Integration Service to read compressed and encrypted data from a remote database and write compressed
and encrypted data to a remote database. Install the PowerChannel Server on the same machine as the
Integration Service.
Installing PowerChannel
To run PowerChannel, you install the PowerChannel Server and PcCmd on Windows or UNIX. You also install the
web client on Windows.
Note: You must have write permissions for the directory where you want to install PowerChannel. Other, the
installation program might not be able to successfully install PowerChannel.
Note: The installation program lets you install the PowerChannel Server on Windows XP. However, Windows XP
is not compatible with the PowerChannel Server. Do not install the PowerChannel Server on Windows XP.
When you want to install the PowerChannel Server to run as a service on Windows, you also need a Windows
user account that runs the PowerChannel Server service. Before you install PowerChannel, create a user account
with the right to run services, known as the Service Start Account. To see if this account has the correct rights, run
User Manager for Domains and select the user. Select User Rights from the Policies menu. The user must have
the Logon as a service right. Create this account specifically to run the PowerChannel Server. Do not run the
PowerChannel Server as the System account.
When you install the PowerChannel Server on Windows, the installation program creates a pcservice.log file in the
PowerChannel root directory. The pcservice.log file shows the status of the PowerChannel Server service
installation. If you uninstall the PowerChannel Server service, check the pcservice.log file to verify if the service
uninstalled successfully.
Installing PowerChannel 9
Note: When you install PowerChannel, the installation program only copies the web client files into the directory
you enter. You need to configure BEA WebLogic Server to run the web client.
1. Log in to the Windows system as a member of the Administrators group in the local domain.
2. If the Informatica Welcome window does not start, run install.exe from the CD.
The Informatica Welcome window appears.
3. Click Next.
4. Enter a valid license key.
5. Click Choose to select the destination folder where you want to install the PowerChannel Server, PcCmd, and
the web client. Click Next. Or, click Next to accept the default installation location.
6. Select RC2 or 3DES for the encryption algorithm.
7. Click Next.
8. Verify the installation information and click Install.
The installation program installs PowerChannel. If the installation is successful, a message appears asking if
you want to configure PowerChannel.
9. Click Yes to open the PowerChannel configuration utility to configure the properties file. Or, click No if you
want to configure the PowerChannel properties later, and go to 11.
10. If you clicked Yes, configure the following properties and click Next:
Property Description
EXPORT_DIR Path to the export directory that PowerChannel to export all certificate files you create for
certificate accounts.
LOG_LEVEL Enter a value from 0 to 3 for the level of detail in the PowerChannel log files.
If you omit values for any of the properties, you can configure the PowerChannel.properties file.
11. Click Yes to restart the machine. Or, click no to restart the machine later.
12. Click Done to complete the setup.
A message appears asking if you want to view the readme file.
13. Click Yes to view the PowerChannel release notes. Or, click No if you do not want to read the release notes.
1. Create ODBC connections. Create ODBC connections on the PowerCenter Client machine to import
definitions for remote database sources and targets.
2. Create relational database connections. Create connection objects in the Workflow Manager so the
Integration Service can connect to remote databases.
Note: You do not need to install PowerChannel on the PowerCenter Client or Integration Service machines to
enable PowerCenter to read file data or write file data through PowerChannel.
The PowerChannel Server unlocks the repository when you stop the server. If you do not stop the server properly,
you need to unlock the repository before you can restart it.
When you start the PowerChannel Server as a service, the server starts with the following Java Virtual Machine
(JVM) memory configuration:
You cannot change the memory configurations for the JVM if you start the PowerChannel Server as a service on
Windows.
On Windows, you can stop the PowerChannel service from the Control Panel.
When you start the PowerChannel Server, you can configure the JVM memory. The PowerChannel Server uses
JVM memory when it runs data transfer sessions. If you do not configure the JVM memory, PowerChannel data
transfer sessions might fail when JVM runs out of memory.
Configure JVM memory in the PowerChannel file on UNIX and the PowerChannel.bat file on Windows. You can
find these files in the PowerChannel directory. Use the following guidelines to configure the JVM memory:
¨ If you run fewer than 20 PowerChannel sessions concurrently, set the -Xms value to 40 MB. Set the -Xmx
value to 60 MB.
¨ If you run 20 to 60 PowerChannel sessions concurrently, set the -Xms value to 40 MB. Set the -Xmx value to
100 MB.
¨ If you run more than 60 PowerChannel sessions concurrently, set the -Xms value to 100 MB. Set the -Xmx
value to 200 MB.
¨ If the session still fails, increase the maximum memory for Java.
u Optional Enter a user account name. Otherwise, the PowerChannel Server looks for the default
user account name in the PowerChannel.properties file.
p Optional Enter the password for the account. Otherwise, the PowerChannel Server looks for it in
the PowerChannel.properties file.
You can use a web client that is a different version that the PowerChannel Server.
1. Using a web browser, go to the web client login page by entering the following in the browser path:
http://<hostname:port>/pcweb/Login.jsp
where <hostname:port> refers to the host name and port of the PowerChannel Servers.
The login page appears.
2. Enter the following information:
Server IP IP address or host name of the PowerChannel Server to which you want to log in.
Server Port Port number of the PowerChannel Server to which you want to log in.
Uninstalling PowerChannel
You can uninstall PowerChannel from Windows.Use the Add/Remove Programs utility to uninstall the
PowerChannel Server and PcCmd from Windows. When you uninstall PowerChannel from Windows, setup does
not remove the PowerChannel.jar and PcCmd.jar files from the Windows CLASSPATH.
When you uninstall PowerChannel, log in to the Windows system as a member of the Administrators group in the
local domain.
You must have administrator privileges on the machine where you uninstall PowerChannel. If you uninstall
PowerChannel without administrator privileges, PowerChannel may not uninstall properly.
If you want to run PowerChannel as a service, correct the error in the service installation error message. Then, run
the PowerChannel installation again to install the service.
If you want to run PcCmd or PcPassword, you need to modify the PowerChannel scripts to specify the right shell
location.
The -X option is an extended option and is not supported for some versions of JVM.
You need to modify the scripts to remove the “X” from all -X options. For example, if the script includes a -Xms
command, you must replace it with the -ms command.
I get the following error message when I start the PowerChannel Server:
[50008] Cannot find “SERVER_ERR_LOG” in the properties file.
The PowerChannel Server generates this error message if the specified property is missing from the
PowerChannel.properties file or when the PowerChannel.properties file contains inconsistencies.
When you receive this error, use the PowerChannel configuration utility to edit the PowerChannel.properties file.
Change the default value of the <listener_name>.FILEr attribute of the ACTIVE_LISTENERS property from “user”
to “” (blank).
Administering PowerChannel
Accounts
This chapter includes the following topics:
¨ User accounts. All PowerChannel users must have a user account to use PowerChannel.
¨ Certificate accounts. A certificate account authenticates one PowerChannel Server to another PowerChannel
Server. It allows a PowerChannel Server to communicate with another PowerChannel Server.
You can administer accounts with the web client or PcCmd.
User Accounts
PowerChannel requires user accounts to authenticate users. The PowerChannel administrator must create user
accounts for all PowerChannel users that run PowerChannel commands. When you create a user account, the
PowerChannel Server stores the account attributes and password in an encrypted file in the repository.
When you run a command, the client communicates with the PowerChannel Server to authenticate you as a valid
user. During the authentication protocol, the client sends the account name along with an encrypted string, which it
encrypts using the password you enter. It never sends the account password across the network. The
PowerChannel Server verifies if the user account name exists in the repository. If the account exists, it decrypts
the string using the account password in the repository. After the user authentication succeeds, the PowerChannel
Server runs the command to complete the PowerChannel tasks.
You do not need a user account when the Integration Service sends a request to the PowerChannel Server to read
data from a remote source or write data to a remote target. The PowerChannel listener on the PowerChannel
Server uses the transport profile to authenticate requests that it receives directly from the Integration Service.
16
Use the following profiles for a user account:
¨ Admin. Use this profile to create an account for a PowerChannel administrator. Accounts with the admin profile
can run all commands including user management commands to create accounts, edit accounts, display a list
of all PowerChannel accounts, and remove accounts from the repository.
¨ User. Use this profile to create an account which you can use for running commands to transfer file data from
one PowerChannel Server to another. You can also change your account attributes.
¨ Disabled. Use this profile to create a disabled account. When the account profile is disabled, you cannot run
any PowerChannel commands. The PowerChannel administrator can edit the account to enable the account
profile. You can change a disabled account profile to admin or user.
Certificate Accounts
When a local PowerChannel Server communicates with a remote PowerChannel Server, the PowerChannel
Servers use certificate accounts to authenticate each other. To communicate with a remote PowerChannel Server,
the local PowerChannel Server must have a certificate account in the remote PowerChannel repository. Similarly,
for a remote PowerChannel Server to communicate with the local PowerChannel Server, it must have a certificate
account in the local PowerChannel repository.
The PowerChannel installation program includes a default certificate account in a sample repository. Use this
certificate account to transfer data between PowerChannel Servers that contain the sample repository. Create a
certificate account for secure data transfer.
When you create a certificate account for a remote PowerChannel Server, the local PowerChannel Server stores
the certificate account attributes in an encrypted file in the repository. It also creates a certificate file for the remote
PowerChannel Server in the PowerChannel/export directory. The local PowerChannel administrator must provide
the certificate file to the remote PowerChannel administrator.
To use a certificate account to communicate with the local PowerChannel Server, the remote PowerChannel
administrator must import the certificate file into the remote PowerChannel repository. When a remote
PowerChannel user runs a command to transfer data from the remote PowerChannel Server to the local
PowerChannel Server, the user must use the certificate account for the local PowerChannel Server to
communicate with it.
¨ Oneway. Use for a certificate account that allows one-way communication from the local PowerChannel Server
to the remote PowerChannel Server. The local server can connect to the remote server to transfer data.
However, the remote server cannot connect to the local server to transfer data.
¨ Twoway. Use when you create a certificate account to allow two-way communication between the remote
PowerChannel Server and the local PowerChannel Server.
Command Description
Option
Account Name New user account name from 3 to 32 characters. Account names are not case sensitive.
Password Password of at least three characters for the new user account.
Input Folder When you transfer files, enter the path of the default input folder for the new user account. If the
path contains spaces, enclose the path in double quotes.
You do not use this parameter when you transfer data between PowerCenter and remote databases.
You can also use the $PC_USER and $PC_DATE server variables for the input folder value.
Output Folder When you transfer files, enter the path of the default output folder for the new user account. If the
path contains spaces, enclose the path in double quotes.
You do not use this parameter when you transfer data between PowerCenter and remote databases.
You can also use the $PC_USER and $PC_DATE server variables for the output folder value.
Account Profile Select one of the following values for the user account profile:
- user
- admin
- disabled
Command Description
Option
Account Name Enter a certificate account name from 3 to 32 characters. Account names are not case sensitive.
Password Enter a password of at least three characters for the new certificate account.
Default Default IP address of the PowerChannel Server where you want to register the new certificate
PowerChannel account. Otherwise, the PowerChannel Server creates the certificate account without a default IP
Hostname/IP address.
Address
Default Default port number of the PowerChannel Server where you want to register the new certificate
PowerChannel account. Use a port number from 1 to 65535. Otherwise, the PowerChannel Server creates the
Port certificate account without a default port number.
Input Folder When you transfer files, enter the path of the default input folder for the new certificate account. If
the path contains spaces, enclose the path in double quotes.
You do not use this parameter when you transfer data between PowerCenter and remote databases.
You can also use the $PC_USER and $PC_DATE server variables for the input folder value.
Output Folder When you transfer files, enter the path of the default output folder for the new certificate account. If
the path contains spaces, enclose the path in double quotes.
You do not use this parameter when you transfer data between PowerCenter and remote databases.
You can also use the $PC_USER and $PC_DATE server variables for the output folder value.
Account Profile Select one of the following values for the certificate account profile:
- oneway
- twoway
¨ Account profile. Account profiles for user accounts are user, admin, and disabled. Account profiles for
certificate accounts are oneway and twoway.
¨ Default input folder. Default folder for input data files during file transfer.
¨ Default output folder. Default folder for output data files during file transfer.
¨ Default port number. Default port number of the local PowerChannel Server.
If you have a user account with the user profile, you can display your own account attributes. If you have a user
account with the admin profile, you can display all user or certificate accounts.
1. Click OwnAccount.
2. Click Display Account.
The web client displays the account attributes.
Command Description
Option
Account Name Enter a filter condition to filter account names. Use the following rules and guidelines:
Filter - Use only one entry in the account name filter.
- Enter an account name or the wildcard character,%, in the account name filter. Use the wildcard
character as a suffix in the filter condition. For example, to display account names that begin with
the letter “a,” use “a%” as the account name filter.
Records per Page Select one of the following values to limit the number of accounts to display on a page:
- 10
- 20
- 50
- 100
3. Click Go.
The web client displays the accounts based on the filter you enter.
Tip: Click Refresh to view an updated account list.
4. Click an account name to display information for that account.
¨ Account profile. User account profiles are user, admin, and disabled.
¨ Default input folder. Default folder for input data files during file transfer.
¨ Default output folder. Default folder for output data files during file transfer.
If you have a user account with the user profile, you can change account attributes for your own account. If you
have a user account with the admin profile, you can change account attributes for any user account. When editing
your own account, you cannot change the account profile.
Input Folder Changes the default input folder path for the user account.
Output Folder Changes the default output folder path for the user account.
Tip: To remove default attributes for an account, leave the command option for the attribute blank. For user
accounts, you can remove the default attributes for the input folder and output folder.
3. Click Save to save changes to the account.
Input Folder Changes the default input folder path for the user account.
Output Folder Changes the default output folder path for the user account.
Account Profile To change the user account profile, select user, admin, or disabled.
Tip: To remove default attributes for an account, leave the command option for the attribute blank.
5. Click Save to save changes to the account. Or, click Cancel to abort the edit account command.
¨ Default port number. Default port number of the local PowerChannel Server.
¨ Default input folder. Default folder for input data files during file transfer.
¨ Default output folder. Default folder for output data files during file transfer.
¨ Account profile. Certificate account profile. Certificate account profiles are oneway and twoway.
You cannot change the password for a certificate account. You can remove the default attributes for the following
account attributes: IP address, port, input folder, and output folder. You must have a user account with the admin
profile to edit a certificate account.
Default PowerChannel Changes the default IP address for the local PowerChannel Server.
Hostname/IP Address
Default PowerChannel Port Changes the default port for the local PowerChannel Server. Use a port number from 1 to
65535.
Input Folder Changes the default input folder path for the certificate account. Do not use this
parameter when you transfer data between PowerCenter and remote databases.
Output Folder Changes the default output folder path for the certificate account. Do not use this
parameter when you transfer data between PowerCenter and remote databases.
Account Profile To change the certificate account profile, select oneway or twoway.
Tip: To remove default attributes for an account, leave the command option for the attribute blank.
5. Click Save to save changes to the account.
When you remove a certificate account, the PowerChannel Server also removes the certificate file for the account
from the PowerChannel/export directory. If you delete the certificate file prior to account removal, the server only
removes the certificate account. It does not provide a message for the missing certificate file.
The PowerChannel Server listens to incoming user requests from PcCmd, the web client, and the Integration
Service on a listener port. The PowerChannel Server also listens to requests from other PowerChannel Servers on
a listener port. When it receives a user request, the PowerChannel Server runs a session. A session includes a
set of tasks that the server completes in response to the user request. The PowerChannel Server communicates
with PcCmd, the web client, and remote servers using a secure protocol.
The PowerChannel Server uses sessions to transfer data in different formats depending on the user request. The
PowerChannel Server can also compress and encrypt data. When a PowerChannel Server receives compressed
and encrypted data from another PowerChannel Server, it decrypts and decompresses the data.
The PowerChannel Server runs as a service on Windows. It runs as an application on Windows and UNIX.
PowerChannel Connectivity
The PowerChannel Server uses the TCP/IP protocol to communicate with the Integration Service and other
PowerChannel Servers. It listens to user requests from PcCmd, the web client, the Integration Service, and other
PowerChannel Servers on a listener port. You define the listener port for the server using the PowerChannel
configuration utility.
24
PowerChannel Protocol
PowerChannel uses a secure protocol to communicate with PcCmd, the web client, and other PowerChannel
Servers. When the Integration Service uses the local and remote PowerChannel Servers to read data from remote
sources and write data to remote targets, the PowerChannel Servers use the secure protocol to ensure that all
data transmitted across the network is encrypted and secure.
For example, when you run a PcCmd command to run a PowerChannel task, PcCmd first uses the PowerChannel
protocol to initiate a handshake with the PowerChannel Server. During the handshake, PcCmd sends the user
account name of the user and a string of text encrypted with the user’s password to the PowerChannel Server.
The PowerChannel Server receives this information and tries to locate the user in the PowerChannel repository. If
the user exists in the repository, the PowerChannel Server uses the user password in the repository to decrypt the
string of text. When the decryption succeeds, the PowerChannel Server acknowledges the user as a valid user
and prompts PcCmd for the user command. PcCmd then sends the user command to the PowerChannel Server
encrypted with the user password. The PowerChannel Server decrypts the command using the user password in
the repository, and runs the PcCmd command to complete the PowerChannel tasks.
If the user command includes transferring database data or files to a remote PowerChannel Server, the local
PowerChannel Server uses the secure protocol to initiate a handshake with the remote PowerChannel Server.
During this handshake, the local PowerChannel Server sends the local host information and a string of text
encrypted with the certificate account key for the remote PowerChannel Server. The remote PowerChannel Server
receives this information and tries to locate the certificate account in its repository. If the account exists, it uses the
certificate account key in the repository to decrypt the string of text. When the decryption succeeds, the remote
PowerChannel Server acknowledges the local PowerChannel Server as a valid server and prompts it to start
transferring database data or files. The local PowerChannel Server then transfers the database data or files to the
remote PowerChannel Server according to the user command.
If the user command includes an FTP connection to read data from flat file sources and write data to flat file
targets, the local PowerChannel Server uses the secure protocol to initiate a handshake with the remote
PowerChannel Server. During this handshake, the local PowerChannel Server sends the local host information
and a string of text encrypted with the certificate account key for the remote PowerChannel Server. The remote
PowerChannel Server receives this information and tries to locate the certificate account in its repository. If the
account exists, it uses the certificate account key in the repository to decrypt the string of text. When the
decryption succeeds, the remote PowerChannel Server acknowledges the local PowerChannel Server as a valid
server. The local PowerChannel Server connects to the remote PowerChannel Server that remains open until you
close it. While the connection is open, the local PowerChannel Server listens for user requests to transfer data
using the FTP connection.
When you transfer data between PowerChannel Servers, the local PowerChannel Server uses a channel to read
the data from the source location, transform it according to the user command, and then write the data to the
network.
Similarly, the remote PowerChannel Server uses a channel to read the data from the network, transform it
according to the user command, and write the data to a target.
You use channel information in a command when you use an XML command file to transfer files. When you use
PcCmd to transfer files, you do not have to enter channel information in the command. PcCmd generates the XML
The following table describes the types of channels the PowerChannel Server uses during data transfer:
READSTREAM To transfer files between PowerChannel Servers with PcCmd or an XML command file,
PowerChannel uses the READSTREAM channel to read the files from the network. When the
PowerChannel Server receives files from a remote PowerChannel Server, it uses this channel to
read the files in bytes from the network.
WRITESTREAM To transfer files between PowerChannel Servers with PcCmd or an XML command file,
PowerChannel uses the WRITESTREAM channel to write the files to the network. When the
PowerChannel Server sends files to a remote PowerChannel Server, it uses this channel to write the
files in bytes to the network.
COMPRSTAGE To transfer files between PowerChannel Servers with PcCmd or an XML command file,
PowerChannel uses the COMPRSTAGE channel when it stages the files during file transfer. When
you transfer files to a remote PowerChannel Server, and you stage the files at the sending and
receiving PowerChannel Servers, the sending PowerChannel Server uses this channel to transfer
the files in bytes.
DECOMPRSTAGE PowerChannel uses the DECOMPRSTAGE channel to decompress staged files during file transfer.
When you transfer files to a remote PowerChannel Server, and you stage the files at the receiving
PowerChannel Server only, the receiving PowerChannel Server uses this channel to read the files in
bytes and decompress the staged files.
PIPE When you use an FTP connection to transfer files, PowerChannel uses the PIPE channel to read
data from the network and write data to the network. The PowerChannel Server uses this channel to
write data to the network in blocks. The PowerChannel Server also uses a PIPE channel to read data
from the network in blocks. PIPE channels remain open until you close them.
TRANSPORT PowerChannel uses the TRANSPORT channel to read data from databases and write data to
databases. The PowerChannel Server uses the TRANSPORT channel to transfer database data to
another PowerChannel Server. The PowerChannel Server also uses the TRANSPORT channel to
transfer data between the Integration Service and remote databases. You do not specify the
TRANSPORT channel when you use an XML command to transfer data.
When the Integration Service sends a request to read compressed and encrypted data from a remote source or
write compressed and encrypted data to a remote target, the sending PowerChannel Server creates a channel to
send the data. This channel uses a set of transformers to compress and encrypt the data according to the user
command. When the receiving PowerChannel Server receives the data from the network, it creates a channel to
receive the data. This channel uses a set of transformers to decrypt and decompress the data.
Enter data transformers in the command when you use an XML command file to transfer files. The PowerChannel
Server uses data transformers in a channel based on the compression, encryption, and staging parameters you
enter in the command. For example, you want to send compressed and encrypted files from a remote
When you transfer data using PcCmd, you do not have to enter data transformers in the command. However, you
can set compression and encryption levels in the PcCmd command. Also, you do not need to configure data
transformers when the PowerChannel Server transfers database data.
Note: You can only enter staging parameters in the command when you transfer files between PowerChannel
Servers. You cannot use staging when you transfer files between the Integration Service and an FTP server or
between FTP clients and servers. Also, you cannot use staging when you transfer database data.
The following table describes the data transformers you use in a channel during file transfer:
STAGECOMPRESSOR COMPRSTAGE Use in a WRITESTREAM channel when you compress files at the
WRITESTREAM sending PowerChannel and stage files at the receiving PowerChannel
only.
Use STAGECOMPRESSOR in a COMPRSTAGE channel when you
compress and stage files at the sending PowerChannel.
When you use the STAGECOMPRESSOR transformer, you can enter
the compression level for data compression. Compression levels
range from 1 to 9, where 9 is the highest compression level.
ENCRYPTOR WRITESTREAM Use in a WRITESTREAM channel when you want to encrypt data at
the sending PowerChannel. When you use ENCRYPTOR in an XML
command file, you can enter the encryption level for data encryption.
When you run a file transfer command or a command to connect
PowerChannel Servers to transfer files between PowerCenter and an
FTP server or between FTP clients and servers, use the -el
parameter for encryption level in a PcCmd command. Encryption
levels range from 1 to 3, where 3 is the highest level of encryption.
DECRYPTOR READSTREAM Use in a READSTREAM channel when you want to decrypt data at
the receiving PowerChannel.
When you use DECRYPTOR in an XML command file, you do not
need to enter the decryption level for data decryption. The
PowerChannel Server determines the decryption level based on the
encryption level you used for data encryption in the command.
DECOMPRESSOR READSTREAM Use in a READSTREAM channel when you want to decompress data
at the receiving PowerChannel.
When you use DECOMPRESSOR in an XML command file, you do
not need to enter the decompression level for data decompression.
The PowerChannel Server determines the decompression level based
on the compression level you use for data compression in the
command.
You also use ACTIVE_LISTENERS when the Integration Service reads data from remote sources or writes data to
remote targets through PowerChannel. The PowerChannel Server uses an active listener to listen for requests
from the Integration Service. For example, when you want the Integration Service to read data directly from the
remote PowerChannel Server, you configure an active listener on the remote PowerChannel Server.
Complete the following tasks when you configure active listeners to administer a PowerChannel Server or transfer
remote data through a PowerChannel Server:
¨ Provide a unique port number for each active listener you want to configure bound on the same IP
address. This port should not be in use by any other application.
¨ Provide a unique listener name for each active listener port you want to make available to clients.
¨ Configure an IP address for the PowerChannel Server that is bound to the port for the active listener
(optional). When you start the PowerChannel Server, it listens at the port number, which is bound to the IP
address you specified. If you do not configure an IP address, the PowerChannel Server uses all IP addresses
of the machine on which it resides.
You can configure the ACTIVE_LISTENERS property using the PowerChannel configuration utility.
If you enter a filter, only clients from IP addresses that meet the filter condition may run client commands on the
PowerChannel Server or transfer data using the PowerChannel Server. This lets you prevent unknown clients from
accessing the PowerChannel Server. When a client attempts to run a client command on the PowerChannel
Server or transfer data using the PowerChannel Server, the PowerChannel Server verifies that the client meets
the filter before it continues the session. If the client does not meet the filter, the PowerChannel Server
disconnects the client.
You can configure the active listeners to restrict the types of commands clients can run on the PowerChannel
Server by entering user profiles for each active listener.
Use the following user profiles to restrict client access to the PowerChannel Server:
¨ Admin. Use the admin profile when you want the client to be able to create, modify, or remove any user
accounts on the PowerChannel Server and run commands to transfer data to and from the PowerChannel
Server. Clients must use user accounts with the admin profile to run client commands on the PowerChannel
Server. The PowerChannel Server will not accept client commands from user accounts with the user profile.
Also, the PowerChannel Server will not accept data transfer requests from active listeners configured with the
transport profile.
¨ User. Use the user profile when you only want the client to be able to change its own account attributes and
transfer data to and from the PowerChannel Server. The PowerChannel Server only accepts client commands
¨ PowerChannel.properties. The default properties file installed with the PowerChannel Server. You can set the
default values for all the server properties in the PowerChannel.properties file. The server uses this file to run
PowerChannel. The server also uses this file when you omit an optional parameter in a PowerChannel
command, and you do not enter a user-defined properties file in the command.
¨ Username.properties. You can create a properties file with all the PowerChannel.properties file attributes
when you run PowerChannel as an application. For example, you can create a properties file,
username.properties, and set the default values for all the PowerChannel Server properties in this file. When
you run a PowerChannel command, use the properties file option to enter the username.properties file in the
command. During command execution, the server uses the properties in the username.properties file to run the
command.
PowerChannel provides a configuration utility to configure the properties file. You can launch the utility when you
install PowerChannel. If you want to change the properties after you install PowerChannel, you can run a
PowerChannel command to launch the utility.
¨ “REPOSITORY” on page 30
¨ “ACTIVE_LISTENERS” on page 30
¨ “CRYPTOGRAPHY” on page 31
¨ “LICENSE” on page 32
¨ “MAX_BLOCK_SIZE” on page 32
¨ “TOTAL_CHANNEL_MEMORY” on page 32
¨ “SERVER_LOG” on page 32
¨ “SERVER_ERR_LOG” on page 33
¨ “LOG_FOLDER” on page 33
¨ “LOG_LEVEL” on page 33
¨ “USERNAME” on page 33
¨ “EXPORT_DIR” on page 34
¨ “MAX_SESSIONS_MONITORED” on page 34
¨ “MAX_CONCURRENT_RUNNING_SESSIONS” on page 35
¨ “REMOVE_LOG_FILES_ON_PURGE” on page 35
¨ “NUM_AUTO_RECOVERY_ATTEMPTS” on page 35
¨ “INPUT_FOLDER” on page 35
¨ “OUTPUT_FOLDER” on page 36
¨ “TRUST_REMOTE_EXECUTION” on page 36
¨ “RUN_EXTERNAL_EXECUTE” on page 36
¨ “PLUGIN.PMREMOTEDATA.LIB” on page 37
REPOSITORY
You set the location of the PowerChannel repository using the PowerChannel configuration utility. Use only ASCII
characters to specify the repository directory. When you install the PowerChannel Server, the installation program
creates a file-based repository for the local PowerChannel in the repository directory. You can move the repository
folder to a different location. When you move the repository, you need to enter the new repository location.
ACTIVE_LISTENERS
You can configure additional listeners to enhance security for the PowerChannel Server when you transfer
database data. When you configure additional listeners, you can restrict client access to the PowerChannel
Server. To configure additional listeners, you enter a name for each listener and configure listener attributes.
If you configure attributes for a listener, but do not want the listener to be active, you can deactivate the listener
using the PowerChannel configuration utility. This lets you retain the configuration information for the listener for
later use.
The following parameters set additional listeners with the ACTIVE_LISTENERS property:
ACTIVE_LISTENERS = <listener_name1> [, <listener_name2>]*
<listener_name1>.PORT = <listener_port_number>
[<listener_name1>.IPADDRESS = <listener_IP_address>]
[<listener_name1>.PROTOCOL = {encrypted|generic}]
[<listener_name1>.USER_PROFILES = [{admin}, {user}, {transport}]]
[<listener_name1>.FILTER = <remote_client_IP_address / subnet>]
The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Values in the
format {x|y} represent the options you can use for the command parameter. Parameters followed by an asterisk (*)
can contain multiple values.
PORT Required Port number of the additional listener. Enter a value from 1 to 65535. The port should not
be used by other applications. For example, do not share the port with an FTP application
or a web server that runs on the same network as the PowerChannel Server.
IPADDRESS Optional IP address of the listener port. Enter an IP address when the PowerChannel Server
resides on a machine with more than one network adapter. When you start the
PowerChannel Server, the server listens at the port number on the network adapter that
is identified by the IP address you specified. Otherwise, the PowerChannel Server listens
for the port on all available adapters.
FILTER Optional Enter a filter to limit the IP addresses from which clients may run commands on the
PowerChannel Server or transfer data using the PowerChannel Server. This lets you
prevent unknown clients from accessing the PowerChannel Server. If a client that is not in
the subnet tries to access the PowerChannel Server, the PowerChannel Server
disconnects the client.
To enter a filter, enter the IP address from which users can run client commands and a
value for the filter. For example, you can enter the following:
128.2.0.1 / 255.255.255.0
When you enter this value for the filter, the PowerChannel Server only accepts requests
from addresses with the IP 128.2.0.x. For example, the PowerChannel Server will not
accept requests from 128.2.1.0, but will not accept requests from 128.2.0.2.
If you do not enter a filter, the PowerChannel Server accepts requests from all clients.
PROTOCOL Optional Enter encrypted or generic for the protocol. Otherwise, the PowerChannel Server uses
the encrypted protocol by default.
Enter encrypted when you want the PowerChannel Server to use the standard
PowerChannel encryption for secure data transfer between PowerChannel Servers. Enter
generic when you want the Integration Service to use the PowerChannel Server to
transfer data without security.
USER_PROFIL Optional Enter user, admin, and/or transport for the user profile. Enter user for the client to have
ES user privileges. Enter admin for the client to have admin privileges. Enter transport when
you want the PowerChannel Server listen for data transfer requests from the Integration
Service. You can enter more than one user profile.
If you do not enter a user profile, the PowerChannel Server uses the admin and user
profiles by default.
Use ACTIVE_LISTENERS to configure two listener ports for the Integration Service.
The following example shows ACTIVE_LISTENERS configured with two listener ports, 7000 and 7001, for the
PowerChannel Server:
ACTIVE_LISTENERS = AdminListener, TransportListener
AdminListener.PORT = 7000
AdminListener.IP_ADDRESS = sunqa1
AdminListener.USER_PROFILE = admin, user
TransportListener.PORT = 7001
TransportListener.IP_ADDRESS = sunqa2
TransportListener.PROTOCOL = generic
TransportListener.USER_PROFILE = transport
TransportListener.FILTER = 10.1.0.0 / 255.255.0.0
CRYPTOGRAPHY
PowerChannel uses an encryption algorithm to encrypt and decrypt data. During installation you set the encryption
algorithm that you want the PowerChannel Server to use. When you set the encryption algorithm, the installation
program configures the CRYPTOGRAPHY property.
When you select an encryption algorithm for CRYPTOGRAPHY, any PowerChannel Server or client you
communicate with must use the same encryption algorithm. When you want to use FIPS-certified encryption, set
the value for CRYPTOGRAPHY to the 3DES encryption algorithm.
LICENSE
When you install the PowerChannel Server, you must enter a valid license key. The installation program registers
the license key in the PowerChannel.properties file.
The following parameter shows the license key entered during PowerChannel Server installation:
LICENSE = <license_key>
MAX_BLOCK_SIZE
PowerChannel uses data block buffers to store blocks of data during data transformation. You can set the
maximum buffer size for data blocks the PowerChannel Server uses in the properties file using the PowerChannel
configuration utility. The default block size for MAX_BLOCK_SIZE is 100 KB. You can set a default value from
1000 to 100000000.
The following parameter sets the maximum buffer size for data blocks:
MAX_BLOCK_SIZE = <buffer_size_in_bytes>
TOTAL_CHANNEL_MEMORY
You can set the total allocated memory for each channel that the PowerChannel Server creates from the
properties file. By default, the server allocates 1.6 MB for each channel. You can set a default value from 1000000
to 100000000.
The following parameter specifies the total allocated memory for each channel:
TOTAL_CHANNEL_MEMORY = <number_of_bytes>
SERVER_LOG
PowerChannel uses a server log file to write server log messages. The default location of the server log file is
<PowerChannel>/log/PowerChannel.log. You can configure the PowerChannel Server to write server log
messages to a different directory.
The following parameter specifies the server error log filename and path:
SERVER_ERR_LOG = <file_path>
LOG_FOLDER
The PowerChannel Server stores session log data in the log directory. The default location of the log directory is
<PowerChannel>/log. You can change the log folder location on the local PowerChannel Server.
When you view session log data for a parent session, the name for the session log file is session name_session
ID. For example, the name of the session log file for a parent session with the name alice and the ID 326 is
alice_326.
When you view the session log for a child session, the name for the session log is session name_parent session
ID_child session ID. For example, the name of the session log for a child session with the ID 752 and with the
session name alice_326 is alice_326_752.
LOG_LEVEL
Use LOG_LEVEL to specify the level of detail in the PowerChannel log files.
LOG_LEVEL Description
Values
0 PowerChannel Server does not write any messages to the log files.
1 PowerChannel Server writes only system critical messages to the log files.
2 PowerChannel Server writes all system critical messages, including some informational messages, to the
log files.
3 PowerChannel Server writes all messages to the log files, including debug messages.
USERNAME
You can enter a default user account name with the admin profile in the properties file using the PowerChannel
configuration utility. When you set a default user name in the properties file, you can omit the user account name
parameter in the PowerChannel Server commands.
Note: This property is required when you run the PowerChannel Server as a service on Windows.
PASSWORD
You can enter a default encrypted password for the default user account in the properties file using the
PowerChannel configuration utility. When you set the default encrypted password in the properties file, you can
omit the password parameter in the PowerChannel Server commands.
To encrypt the default password, use the PcPassword encryption utility from the PowerChannel command line. To
use the PcPassword utility for encrypting a user account password, enter PcPassword and the password you want
to encrypt. For example, if you want to encrypt the password “Administrator,” go to the PowerChannel directory
from the command line and use the following command:
PcPassword Administrator
The password encryption utility returns a randomly generated string for the encrypted password.
You can copy the password string to PASSWORD using the PowerChannel configuration utility. When you enter a
value for PASSWORD, you can omit the password parameter in PcCmd commands.
Note: This property is required when you run the PowerChannel Server as a service.
EXPORT_DIR
PowerChannel uses an export directory to export all certificate files you create for certificate accounts. When you
create a certificate account, the PowerChannel Server creates a certificate file for the certificate account. During
installation, the installation program creates an export directory in the PowerChannel root directory. You can
configure the server to store certificate files in a different export directory.
If the export path contains spaces, you must enclose the path in quotes.
MAX_SESSIONS_MONITORED
The PowerChannel Server stores session information in memory for all data transfer sessions you run. If a session
fails, the server stores the session information for the failed session in the repository.
You can define the number of sessions the server stores in memory by configuring
MAX_SESSIONS_MONITORED using the PowerChannel configuration utility. The value you enter determines the
number of file transfer sessions to retain in memory for session monitoring. The default value for
MAX_SESSIONS_MONITORED is 100. You can set a default value from 10 to 1000.
When you enter a value for MAX_SESSIONS_MONITORED, do not use special characters, such as a comma.
When the number of data transfer sessions in memory exceeds the value for MAX_SESSIONS_MONITORED, the
PowerChannel Server removes the session information for the excess sessions. When the server removes the
excess session information, it removes the oldest session information first.
MAX_CONCURRENT_RUNNING_SESSIONS
You can limit the number of sessions that run concurrently on the PowerChannel Server. Use
MAX_CONCURRENT_RUNNING_SESSIONS in the properties file to specify the maximum number of sessions to
run concurrently. The number of sessions you run concurrently determines the amount of system resources the
server uses. The default value for MAX_CONCURRENT_RUNNING_SESSIONS is 20. You can set a default value
from 1 to 10000.
The following parameter sets the value for the maximum number of sessions that run concurrently:
MAX_CONCURRENT_SESSIONS = <value>
When you enter a value for MAX_CONCURRENT_RUNNING_SESSIONS, do not use special characters, such as
a comma.
REMOVE_LOG_FILES_ON_PURGE
You can configure the PowerChannel Server to remove the log files for sessions that are no longer in the system
memory. To remove log files, enter “yes” for REMOVE_LOG_FILES_ON_PURGE using the PowerChannel
configuration utility. Otherwise, the server does not remove log files. The server removes log files when it removes
session information for old sessions from the memory.
The following parameter specifies whether you want to remove log files on purge:
REMOVE_LOG_FILES_ON_PURGE = {yes|no}
NUM_AUTO_RECOVERY_ATTEMPTS
The PowerChannel Server attempts to recover data transfer sessions if a session fails due to network error. For
example, PowerChannel tries to send a file to a remote PowerChannel Server, but the session fails during file
transfer.
You can set the maximum number of attempts the PowerChannel Server makes to recover the session using the
PowerChannel configuration utility. When the server successfully recovers the connection between PowerChannel
Servers, it begins to count the maximum number of attempts from 0. When it reaches the maximum number of
recovery attempts, the session fails due to network failure.
Use NUM_AUTO_RECOVERY_ATTEMPTS to set the maximum number of recovery attempts for the server. The
default value for the number or recovery attempts is 10. You can set a default value from 0 to 1000.
When you enter a value for NUM_AUTO_RECOVERY_ATTEMPTS, do not use special characters, such as a
comma.
INPUT_FOLDER
PowerChannel uses an input folder as the default folder for input data files during file transfer. For example, you
want to send a file from the local PowerChannel Server to a remote PowerChannel Server. In the command
The PowerChannel Server uses the default input folder under the following conditions:
¨ The user does not enter the absolute path to the file source.
¨ The user account does not have a specified absolute path for the input folder.
You can enter a different location for the default input folder. To change the input folder location, edit the
INPUT_FOLDER parameter value using the PowerChannel configuration utility.
The following parameter sets the default input folder for PowerChannel:
INPUT_FOLDER = <directory_path>
You can also use a server variable for the INPUT_FOLDER value.
OUTPUT_FOLDER
PowerChannel uses the output folder as the default folder for output data files during file transfer. For example,
you want to receive a file from a remote PowerChannel Server. In the command parameter, you do not enter the
absolute path to the destination file. When the PowerChannel Server receives the file from the remote server, it
writes the file to the default output folder specified in the properties file. During installation, install creates the
default output folder under the PowerChannel root directory.
The PowerChannel Server uses the default output folder under the following conditions:
¨ The user does not enter the absolute path to the destination file.
¨ The user account does not have a specified absolute path for the output folder.
You can enter a different location for the default output folder.
The following parameter sets the default output folder for PowerChannel:
OUTPUT_FOLDER = <directory_path>
TRUST_REMOTE_EXECUTION
You can configure the PowerChannel Server to restrict operating system commands from a remote PowerChannel
Server. Use this parameter when you want to allow only file transfer commands from a remote server. For
example, you may want to restrict remote servers from deleting files on the local PowerChannel system. Use
TRUST_REMOTE_EXECUTION in the properties file to specify the restriction.
The PowerChannel Server only allows operating system commands from remote PowerChannel Servers when you
enter “yes” for TRUST_REMOTE_EXECUTION. Otherwise, the server restricts operating system commands from
remote servers.
The following parameter restricts operating system commands from remote PowerChannel Servers:
TRUST_REMOTE_EXECUTION = {yes|no}
RUN_EXTERNAL_EXECUTE
You can configure the PowerChannel Server to control external execute commands run by any account on the
local PowerChannel Server. Use RUN_EXTERNAL_EXECUTE to restrict users from running operating system
The following parameter controls external execute commands by users on the local PowerChannel Server:
RUN_EXTERNAL_EXECUTE = {all|admin|none}
Valid Description
Values
all All users can run external execute commands on the local PowerChannel Server.
admin Only users with the admin profile can run external execute commands on the local PowerChannel Server.
none External execute commands are not allowed on the PowerChannel Server.
PLUGIN.PMREMOTEDATA.LIB
To use PowerCenter with PowerChannel, the PowerChannel plug-in requires a plug-in library. PowerChannel
specifies the PowerChannel plug-in library for PLUGIN.PMREMOTEDATA.LIB. Do not modify this property. Make
sure that the entry in the PowerChannel.properties file is correct.
The following table describes values for PLUGIN.PMREMOTEDATA.LIB based on operating system:
Windows pmtlserver.dll
Solaris libpmtlserver.so
AIX libpmtlserver.a
HP-UX limpmtlserver.sl
Value Description
1 Add a listener.
3 Edit a listener.
4 Remove a listener.
¨ IP Address (optional).
¨ IP Filter (optional).
If you do not want to configure or change a listener, select 5 and press ENTER.
5. Select an encryption algorithm from the options shown in the following table:
Value Description
1 JSAFE/RC2
2 JSAFE/3DES
Value Description
0 No messages.
Value Description
Value Description
1 Add a plug-in. Lets you select property values if you change operating systems.
3 Edit a plug-in.
¨ $PC_DATE. Controls the location of source and destination files during file transfer, and the location of session
log files based on the system date. $PC_DATE supports the YYYY-MM-DD date format.
¨ $PC_USER. Controls the location of source and destination files during file transfer, and the location of session
log files based on the user account that runs the command.
Use the server variables for the following tasks:
You can also use $PC_USER and $PC_DATE as values for the input and output folder properties for a user
account. For example, when you create or edit a user account, use $PC_USER and $PC_DATE as values for the
input and output folder parameters.
For example, the PowerChannel user account name is “alice,” and you want to configure the PowerChannel
Server to read source files during file transfer from the output directory, and write destination files during file
transfer to the input directory. Create a directory for the source data with the name “alice” under the output
directory. Also create a directory for the destination files with the name “alice” under the input directory.
Set the following value for the OUTPUT_FOLDER property using the PowerChannel configuration utility:
output/$PC_USER
Set the following value for the INPUT_FOLDER property using the PowerChannel configuration utility:
input/$PC_USER
When the PowerChannel Server runs the session to transfer files, it looks for the source files in the output/alice
directory. It writes destination files to the input/alice directory.
Set the following value for the OUTPUT_FOLDER property using the PowerChannel configuration utility:
output/$PC_DATE
Set the following value for the INPUT_FOLDER property using the PowerChannel configuration utility:
input/$PC_DATE
When the PowerChannel Server runs the session to transfer files, it looks for source files in the output/2007-07-01
directory. It writes files data to the input/2007-07-01 directory.
Using $PC_USER and $PC_DATE for Source and Destination File Paths
You can also use $PC_USER and $PC_DATE together to define the path for the source and destination files. For
example, the user account name is “tracy,” and you want to configure the PowerChannel Server to read source
files on July 01, 2007, from a directory specific to the user account and the system date. You also want the server
to write destination files on July 01, 2007, to a directory specific to the user account and the system date. Create
the following directory under the output directory for the source files:
tracy/2007-07-01
Set the following value for the OUTPUT_FOLDER property using the PowerChannel configuration utility:
output/$PC_USER/$PC_DATE
Set the following value for the OUTPUT_FOLDER property using the PowerChannel configuration utility:
input/$PC_USER/$PC_DATE
When the PowerChannel Server runs the session to transfer files, it looks for the source files in the output/tracy/
2007-07-01 directory. It writes destination files to the input/tracy/2007-07-01 directory.
You can also use $PC_USER and $PC_DATE to define the source or destination file path in the file transfer
command. Use $PC_USER and $PC_DATE as values for the -f option in the file transfer command.
For example, the user account name is “bob,” and you enter the following value for the LOG_FOLDER property
using the PowerChannel configuration utility:
log/$PC_USER
When you run sessions, the PowerChannel Server writes session log files to the log/bob directory.
For example, you want to configure the server to write session log files on July 01, 2007, to a directory specific to
the system date. Enter the following value for the LOG_FOLDER property using the PowerChannel configuration
utility:
log/$PC_DATE
When you run sessions, the PowerChannel Server writes session logs to the log/2007-07-01 directory.
For example, the user account name is “mary,” and you want the server to write certificate files for all certificate
accounts you create to a directory specific to the user account. Enter the following value for the EXPORT_DIR
property using the PowerChannel configuration utility:
export/$PC_USER
When you create a certificate account, the PowerChannel Server writes the certificate file for the account to the
export/mary directory. You do not have to create a directory with a name specific to the user account. The server
creates a directory under the export directory with the account name and writes certificate files for all certificate
accounts you create.
When you create a certificate account on July 01, 2007, the PowerChannel Server writes the certificates files to
the export/2007-07-01 directory. You do not have to create the directory with a name specific to the system date.
The server creates a directory under the export directory with a name specific to the system date and writes
certificate files for all certificate accounts you create in that directory.
When you create certificate accounts on July 01, 2007, the PowerChannel Server writes the certificate files to the
following directory:
export/alice/2007-07-01
You can also use PowerChannel Server commands to start the server.
The following table describes the parameters for the PowerChannel config command:
r Optional Enter the name and path of the properties file you want to modify. Otherwise, the
PowerChannel Server opens the default properties file for you to configure.
pl Optional Enter the type of properties you want to configure. You can enter one of the following
values:
- all. Displays all properties.
- install. Lists properties you must configure during installation.
- plug-in. Lists properties specific to adding or editing a plug-in.
If you omit the parameter from the command, the PowerChannel Server displays all
properties.
Note: The sample PowerChannel repository includes a default certificate account with a twoway profile. The
default certificate account allows PowerChannel Server that use the sample repository to transfer data with each
other.
When you import a certificate account, you can set the profile for the certificate account. You can set the profile to
oneway or twoway. When you set the certificate account profile to oneway, a remote PowerChannel Server cannot
connect to the local PowerChannel Server with this account. When you set the certificate account profile to
twoway, the local and remote PowerChannel Servers can connect to each other and transfer data.
Note: When you create a certificate account with a oneway profile, and a remote PowerChannel Server imports
the account with a oneway profile, neither PowerChannel Server can use the account to communicate with the
other PowerChannel Server.
r Optional Enter the name and path of the PowerChannel.properties file. Otherwise, the
PowerChannel Server uses the default properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, the PowerChannel Server looks for the default
user account name in the default PowerChannel.properties file.
p Optional Enter the password for the account. Otherwise, the PowerChannel Server looks for it in
the default PowerChannel.properties file.
c Required Enter the name and path of the remote PowerChannel certificate file that you want to
import. If the path of the certificate file contains spaces, enclose the path in double quotes.
P Required Enter the password for the remote PowerChannel certificate file you want to import.
You can reencrypt the repository from the PowerChannel command line. When you reencrypt the repository, the
server decrypts the repository using the old repository key and encrypts the repository again using a new
randomly generated key. When you reencrypt the repository, you do not alter the account and session information
stored in the repository. You must have a user account with the admin profile to reencrypt the PowerChannel
repository.
r Optional Enter the name and path of the PowerChannel.properties file using the PowerChannel
configuration utility. Otherwise, the PowerChannel Server uses the default properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, the PowerChannel Server looks for the default
user account name in the default PowerChannel.properties file.
p Optional Enter the password for the account. Otherwise, the PowerChannel Server looks for it in
the default PowerChannel.properties file.
Before you can start the PowerChannel Server again, you must unlock the PowerChannel repository. You can
unlock the repository from the PowerChannel command line. To unlock the repository, you must have a user
account with the admin profile.
r Optional Enter the name and path of the PowerChannel.properties file. Otherwise, the
PowerChannel Server uses the default properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, the PowerChannel Server looks for the default
user account name in the default PowerChannel.properties file.
p Optional Enter the password for the account. Otherwise, the PowerChannel Server looks for it in
the default PowerChannel.properties file.
r Optional Enter the name and path of the PowerChannel.properties file. Otherwise, the
PowerChannel Server uses the default properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, the PowerChannel Server looks for the default
user account name in the default PowerChannel.properties file.
p Optional Enter the password for the account. Otherwise, the PowerChannel Server looks for it in
the default PowerChannel.properties file.
When you use PowerChannel to transfer files for a PowerCenter source or target, you can run PcCmd commands
from the Workflow Manager. You can include PcCmd commands in the pre- or post-session commands dialog to
read data from flat file sources and write data to flat file targets.
PcCmd requires a properties file to run commands. The properties file contains a set of properties that PcCmd
uses when you run a command. You can configure the properties file with the PcCmd configuration utility.
¨ PcCmd.properties. The default properties file installed with PcCmd. You can set the default values for all
PcCmd properties in the PcCmd.properties file. PcCmd uses this file if you do not use an optional parameter to
specify a user-defined properties file in the PcCmdconfig command.
¨ Username.properties. You can create a properties file with all the PcCmd.properties file attributes. For
example, you can create a properties file, username.properties, and set the default values for all PcCmd
properties in the username.properties file. When you run a PcCmd command, use the properties file option to
specify the username.properties file in the command. During command execution, PcCmd uses the properties
in the username.properties file to run the command.
RELATED TOPICS:
¨ “Working with PcCmd Commands in PowerCenter Sessions for File Transfer” on page 66
49
Configuring PcCmd Properties
PcCmd uses property values when it runs a PcCmd command. For example, you can define the default user
account name and password values for PcCmd commands in the properties file. When you define the user
account name and password values in the properties file, you can omit the user account name and password
parameters in a command. PcCmd uses the user account name and password parameter values in the properties
file.
You can set the following PcCmd properties in the properties file:
¨ “SERVER_ADDRESS” on page 50
¨ “SERVER_PORT” on page 50
¨ “PCCMD_LOG” on page 50
¨ “USERNAME” on page 51
¨ “PASSWORD” on page 51
¨ “SESSION_NAME” on page 51
¨ “COMPRESSION_LEVEL” on page 52
¨ “ENCRYPTION_LEVEL” on page 52
¨ “CHECKSUM” on page 52
¨ “CODE_PAGE” on page 52
¨ “HOSTS” on page 53
¨ “STAGE” on page 53
¨ “CRYPTOGRAPHY” on page 53
You can set default values for PcCmd properties in a properties file with the PcCmd configuration utility.
SERVER_ADDRESS
You can define the default PowerChannel Server address with the PcCmd configuration utility. If you omit the local
PowerChannel Server name in the PcCmd command, PcCmd uses the server name or IP address defined in the
SERVER_ADDRESS property.
SERVER_PORT
Define the default PowerChannel Server port in the properties file with the PcCmd configuration utility. If you omit
the local PowerChannel Server port in the PcCmd command, PcCmd uses the port defined in the SERVER_PORT
property. You can set a default port value from 1 to 65535.
Note: When you enter a value for SERVER_PORT, do not use special characters, such as a comma.
PCCMD_LOG
You can enter the name and path of the PcCmd system log filename with the PcCmd configuration utility. PcCmd
writes all PcCmd system log messages to the PcCmd system log file.
USERNAME
You can enter a default user account name with the PcCmd configuration utility. When you set a default user
account name in the properties file, you can omit the user account name parameter in the PcCmd command.
PASSWORD
You can enter a default encrypted password for the default user account with the PcCmd configuration utility.
When you set the default encrypted password in the properties file, you can omit the password parameter in the
PcCmd command.
To encrypt the default password, use the PcPassword encryption utility from the PowerChannel command line. To
use the PcPassword utility for encrypting a user account password, enter PcPassword and the password you want
to encrypt.
For example, if you want to encrypt the password “Administrator,” go to the PowerChannel directory from the
command line and use the following command:
PcPassword Administrator
The password encryption utility returns a randomly generated string for the encrypted password.
You can copy the password string to the PASSWORD property in the properties file with the PcCmd configuration
utility. When you enter a value for PASSWORD, you can omit the password parameter in PcCmd commands.
SESSION_NAME
You can set a default PowerChannel session name in the PcCmd properties file with the PcCmd configuration
utility. PcCmd uses the session name to name parent and child sessions. When you configure a name for a
PowerChannel session, you can easily identify the PowerChannel sessions you run in the PowerChannel session
log. For example, you can set the session name to a PowerChannel user account name. PcCmd names the parent
session session_name.
Each parent and child PowerChannel session also receives a session ID. The session ID values increment by one
each time the PowerChannel Server runs a session. The session name for the child session includes the parent
session name and the parent session ID. For example, you run the PcCmdsend command. You name the session
alice. The local PowerChannel Server creates a parent session for the file transfer with the ID 326. The remote
PowerChannel Server creates a child session with the ID 752. The name of the child session is alice_326.
When you set the default session name, you can omit the session name parameter in the PcCmd command.
The following sets the default session name with the PcCmd configuration utility:
SESSION_NAME = <session_name>
The following parameter sets the default compression level in the properties file with the PcCmd configuration
utility:
COMPRESSION_LEVEL = <level>
ENCRYPTION_LEVEL
Enter the default encryption level you want to use for data encryption. Encryption levels range from 0 to 3. 3 is the
highest encryption level. Enter 0 if you do not want to encrypt files during file transfer. When you enter the default
encryption level in the properties file, you can omit the encryption parameter in the PcCmd command.
The following parameter sets the default encryption level in the properties file with the PcCmd configuration utility:
ENCRYPTION_LEVEL = <level>
CHECKSUM
You can configure the PowerChannel Server to calculate a checksum value to ensure data integrity during file
transfer. When you set CHECKSUM to “yes” in the properties file, the PowerChannel Server calculates a distinct
long integer value for the file you transfer at the source and the destination PowerChannel Servers. If the
checksum values for the source file and the destination file are equal at the end of the file transfer, PowerChannel
completes the session. If the checksum values are not equal, the session fails.
Use checksum when the source files you transfer are located in an input folder on a machine hosting the
PowerChannel Server. When you use an FTP connection to transfer files, you cannot use checksum. You cannot
use checksum when PowerCenter reads data from remote database sources or writes data to remote database
targets with PowerChannel.
When you enter a default value for CHECKSUM, you can omit the checksum parameter in the command for
sending or getting files.
CODE_PAGE
Enter the code page of the machine running PcCmd. The code page of the machine running PcCmd must be a
subset of the code page of the PowerChannel Server machine. If you do not ensure code page compatibility
between the PowerChannel Server and PcCmd, the PowerChannel Server is unable to interpret the XML
commands it receives from PcCmd.
The default code page for PcCmd is US-ASCII. If you run PcCmd on a Japanese machine, use a code page that
supports Japanese characters. For example, use the MS Shift JIS code page.
STAGE
Enter whether you want to stage files during file transfer. When you enter a default staging value, you can omit the
staging parameter in the PcCmd get or PcCmd send commands.
Use staging when the source files you transfer are located in an input folder on a machine hosting a
PowerChannel Server.
Note: You can only use staging when you run commands for transferring files. You cannot use staging when you
use an FTP connection to transfer flat files. You also cannot use staging when PowerCenter reads data from
remote sources or writes data to remote targets.
CRYPTOGRAPHY
PowerChannel uses an encryption algorithm to encrypt and decrypt data. You set the encryption algorithm that
you want PcCmd to use during installation. The installation program writes the value to the CRYPTOGRAPHY
property.
You can modify the value for CRYPTOGRAPHY. When you enter a value for CRYPTOGRAPHY, any
PowerChannel Server or client you communicate with must use the same encryption algorithm. When you want to
use FIPS-certified encryption, you must specify the 3DES encryption algorithm. If you do not include a value for
CRYPTOGRAPHY, PcCmd uses the RC2 encryption algorithm by default.
Note: When running the PcCmd configuration utility, you can enter Ctrl-C to exit the configuration utility at any
time.
Value Description
none No staging.
Value Description
1 JSAFE/RC2
2 JSAFE/3DES
¨ To send files to remote PowerChannel Servers and receive files from remote PowerChannel Servers.
¨ To transfer data between FTP clients and servers in compressed and encrypted format.
¨ To read flat file source data and write flat file target data during a PowerCenter session.
PowerChannel lets you transfer multiple files from a local PowerChannel Server to multiple remote PowerChannel
Servers. You can also use PowerChannel to transfer multiple files from a remote PowerChannel Server to the
local PowerChannel Server.
¨ A PowerChannel Server must exist at the local and remote file transfer locations.
¨ You must have a PowerChannel user account with a profile of user or admin.
¨ A certificate account for the remote PowerChannel Server must exist in the local PowerChannel repository.
55
Working with Input and Output Folders During File Transfer
During file transfer, the PowerChannel Server reads files from input folders and writes files to output folders. You
can change the default input and output folders with the PowerChannel configuration utility. You can also enter
input and output folders for user accounts and certificate accounts. The PowerChannel Server uses the input and
output folders you enter in the properties file, user account, and certificate account when transferring files.
If you do not enter a value for the input folder or output folder in the user or certificate account, the PowerChannel
Server only uses the values in the default input and output folders from the PowerChannel.properties file.
When the local PowerChannel Server receives the files from the remote PowerChannel Server, and the user
account you used to run the command contains a relative path to an output folder, the local PowerChannel Server
receives the files in the following directory:
<default_output_folder>/<user_account_output_folder>
For example, the default input folder in the PowerChannel.properties file is input. The default output folder in the
PowerChannel.properties file is output. The value for the input folder in the certificate account is cert1. The value
for the output folder in the user account is admin. When you run PcCmdget, the remote PowerChannel Server
looks for the files you want to transfer in the input/cert1 directory. When the local PowerChannel Server receives
the files, it receives them in the output/admin folder.
If you enter an absolute path for the certificate account input folder or the user account output folder, the
PowerChannel Servers ignore the default input and output folder values from the PowerChannel.properties file.
For example, you enter PcCmdget, and the certificate account you specified in the command contains the
following absolute path for the input folder:
c:\powerchannel\pchserv1
When you run the command, the remote PowerChannel Server looks for the files you want to transfer in the c:
\powerchannel\pchserv1 directory.
When the remote PowerChannel Server receives the files from the local PowerChannel Server, and the user
account you used to run the command contains a relative path to an output folder, the remote PowerChannel
Server receives the files in the following directory:
<default_output_folder>/<certificate_account_output_folder>
For example, the default input folder in the PowerChannel.properties file is input. The default output folder in the
PowerChannel.properties file is output. The value for the input folder in the user account is admin. The value for
the output folder in the certificate account is cert1. When you run a PcCmdsend command, the local
PowerChannel Server looks for the files you want to transfer in the input/admin directory. When the remote
PowerChannel Server receives the files, it receives them in the output/cert1 folder.
If you enter an absolute path for the user account input folder or the certificate account output folder, the
PowerChannel Servers ignore the default input and output folder values from the PowerChannel.properties file.
When you run the command, the local PowerChannel Server looks for the files you want to transfer in the c:
\powerchannel\pchserv1 directory.
¨ If you do not enter a destination filename, the PowerChannel Server writes the source file to the destination
with the same name as the source file.
¨ When you separate filename pairs on UNIX, escape the “;” character with a “\” character. For example, use the
following to get the files, data001.txt and data002.txt, from a remote PowerChannel Server: -f=/data001.txt\;/
data002.txt.
¨ Use an absolute path with destination filenames. Otherwise, the local PowerChannel Server writes target files
into the default output folder.
¨ You cannot use an absolute path with source filenames. Otherwise, the session fails.
¨ Use the $PC_USER and $PC_DATE server variables to define the path for the source and destination files.
¨ When you use $PC_USER and $PC_DATE on a UNIX platform, escape the “$” character with a “\” character.
For example, use the following to write the target file to /$PC_USER/$PC_DATE/target.txt: -f=\$PC_USER/\
$PC_DATE/target.txt.
¨ If you want to send or receive multiple files, enter the source and destination filename pairs separated by a
semicolon. For example, you can enter data1.txt;data2.txt to transfer the files data1.txt and data2.txt.
Warning: When you use PcCmdget to get files and you get files with the same name from multiple remote
PowerChannel Servers, avoid overwriting existing files.
For example, you transfer the file data1.txt from the server PowerChannel1 to an input folder. Later, you transfer
another file, data1.txt, from the server PowerChannel2 to an input folder. The file data1.txt from the server
PowerChannel2 overwrites the file of the same name from the server PowerChannel1 because it is the most
recent file you transferred.
To avoid overwriting files, you can make sure the files you transfer do not use the same name. Or, you can put the
files into separate directories according to the server you get the files from. Use the -f parameter in the PcCmdget
command to specify the path and filename of the files you want to transfer.
r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the default
properties file.
You must enter the absolute path to the PcCmd.properties file when you read data from a
flat file source with a pre-session command in a PowerCenter session.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in the
PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server. If
you do not enter this parameter, PcCmd uses the server in the PcCmd.properties file.
sn Optional Enter a name for the PowerChannel session. If you do not enter a name for the session,
PcCmd assigns a name based on the session naming convention defined in the
PcCmd.properties file.
f Required Enter the source filename and the destination filename separated by a comma. For
guidelines on entering values for -f, see “Entering Filenames in PcCmd get and PcCmd
send Commands” on page 57.
R Optional Enter a certificate account name and host information for the remote PowerChannel
Server from which you want to receive files.
If you do not enter the IP address and port of the remote host, the PowerChannel Server
uses the default IP address and port for the remote PowerChannel certificate account.
cl Optional Enter the compression level. You can select compression levels from 1 to 9 or none.
Enter “none” for no compression.
If you do not enter a compression level, PcCmd uses the compression level defined in the
PcCmd.properties file.
el Optional Enter the encryption level. You can select encryption levels from 1 to 3 or none. Enter
“none” for no encryption.
If you do not enter an encryption level, PcCmd uses the encryption level defined in the
PcCmd.properties file.
T Optional Enter one of the following options for the staging parameter:
- receiving. To stage files at the receiving PowerChannel.
- all. To stage files at the sending and receiving PowerChannels.
- none. To disable staging at the sending and the receiving PowerChannels.
If you do not enter the staging parameter, PcCmd uses the default staging configuration
defined in the PcCmd.properties file.
w Optional Use the wait option if you want the PowerChannel Server to wait until it completes a
session before it responds to PcCmd with a message. This option is useful when you run
multiple sessions in a batch and you want the sessions to run sequentially.
You must use the wait option when you read data from a flat file source with a pre-session
command in a PowerCenter session.
cs Optional Specify whether you want the PowerChannel Server to calculate checksum for the file
transfer. Enter “yes” to enable checksum. Enter “no” to disable checksum. If you do not
enter a value, PcCmd uses the default checksum value in the PcCmd.properties file.
You can also get files from a remote PowerChannel Server with an XML command file.
Note: When you transfer files to multiple PowerChannel Servers and the local PowerChannel Server fails to
connect to one of the remote servers, the local server fails the file transfer session.
r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the default
properties file.
You must enter the absolute path to the PcCmd.properties file when you write data to a
flat file target with a post-session command in a PowerCenter session.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in the
PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server. If
you do not enter this parameter, PcCmd uses the server in the PcCmd.properties file.
sn Optional Enter a name for the PowerChannel session. If you do not enter a name for the session,
PcCmd assigns a name based on the session naming convention defined in the
PcCmd.properties file.
f Required Enter the source filename and the destination filename separated by a comma.
R Optional Enter a certificate account name and host information for the remote PowerChannel
Server to which you want to send the files. If you are sending files to multiple
PowerChannel Servers, you need to enter a certificate account name for each remote
server separated by a semicolon.
If you do not enter the IP address and port of the remote hosts, the PowerChannel Server
uses the default IP address and port for the remote PowerChannel certificate account.
cl Optional Enter the compression level. Valid compression levels are from 1 to 9 or none. Enter
“none” for no compression.
If you do not enter a compression level, PcCmd uses the compression level defined in the
PcCmd.properties file.
el Optional Enter the encryption level. Valid encryption levels are from 1 to 3 or none. Enter “none” for
no encryption.
If you do not enter an encryption level, PcCmd uses the encryption level defined in the
PcCmd.properties file.
T Optional Enter one of the following options for the staging parameter:
- receiving. To stage files on the receiving PowerChannel Server.
- all. To stage files at the sending and receiving PowerChannels.
- none. To disable staging at the sending and the receiving PowerChannels.
If you do not enter the staging parameter, PcCmd uses the default staging configuration
defined in the PcCmd.properties file.
w Optional Use the wait option if you want the PowerChannel Server to wait until it completes a
session before it responds to PcCmd with a message. This option is useful when you run
multiple sessions in a batch, and you want the sessions to run sequentially.
You must use the wait option when you write data to a flat file target with a post-session
command in a PowerCenter session.
cs Optional Specify whether you want the PowerChannel Server to calculate checksum for the file
transfer. Enter “yes” to enable checksum. Enter “no” to disable checksum. If you do not
enter a value, PcCmd uses the default checksum value in the PcCmd.properties file.
You can also send files to a remote PowerChannel Server with an XML command file.
PowerChannel can listen for FTP client requests from multiple clients and forward the requests to multiple FTP
servers. PowerChannel can also forward requests from multiple FTP clients to a single FTP server.
When you configure PowerChannel to transfer data between FTP clients and servers, the local PowerChannel
Server listens for requests from FTP clients on the same LAN as the server. You configure FTP client commands
to forward the command requests to the local PowerChannel Server. Use the PcCmd createpipe command from
the command line of the local PowerChannel Server to start a session for the local PowerChannel Server to listen
for requests from FTP clients. The PowerChannel session opens PIPE channels between the local PowerChannel
Server and a remote PowerChannel Server in the same LAN as the FTP server. The servers use the PIPE
channels for transferring files between FTP clients and servers.
When you create a session to connect the local and remote PowerChannel Servers with PIPE channels, you enter
connection information to the FTP server in PcCmd createpipe. You can also enter a timeout period in the
command after which any idle connections between PowerChannel and FTP servers close. The local
PowerChannel Server uses the connection information to forward file transfer requests from FTP clients to FTP
servers through the remote PowerChannel Server. The PowerChannel Servers then transfer the data between
FTP clients and servers.
After the PowerChannel Servers complete the file transfer tasks, the connection between PowerChannel and the
remote FTP servers closes. However, the PIPE channels connecting the PowerChannel Servers remain open until
you stop the PowerChannel session. The PIPE channels also remain open when file transfer between
PowerCenter and the FTP server fails. Keeping the connection open allows PowerChannel to transfer data
whenever you run an FTP file transfer command.
For example, you want to run an FTP script to transfer a large volume of data through PowerChannel with
encryption and compression. You connect the local and remote PowerChannel Servers with PIPE channels. The
local PowerChannel Server then listens for user requests from FTP clients.
When you run the script from the FTP client, the local PowerChannel Server receives the file transfer request. It
opens a connection to the remote FTP server through the remote PowerChannel Server. The local PowerChannel
Server compresses and encrypts the data according to the user command and writes the data to the network. The
remote PowerChannel Server reads the data from the network and decompresses and decrypts the data. It writes
the data to the FTP server. The connection between the PowerChannel Server and FTP server closes. The
session hosting the connection between the PowerChannel Servers continues to run until you stop the session.
¨ A PowerChannel Server must exist in the same LAN as the FTP client.
¨ A PowerChannel Server must exist in the same LAN as the FTP server.
¨ You must have a PowerChannel user account with a profile of user or admin.
¨ A certificate account for the remote PowerChannel Server must exist in the local PowerChannel repository.
r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the default
properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account. Otherwise, the PowerChannel Server looks for
the default password defined in the PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server. If
you omit this parameter, PcCmd uses the server in the PcCmd.properties file.
sn Optional Enter a name for the PowerChannel session. If you do not enter a name for the session,
PcCmd assigns a name based on the session naming convention defined in the
PcCmd.properties file.
R Optional Enter the certificate account name and host information for the remote PowerChannel
Server.
F Required Enter the following information to connect to an FTP server through PowerChannel:
- The connection type. Enter FTP.
- The local connector parameter. You can enter the listener port number of the local
PowerChannel Server. The server uses this port to listen for requests from
PowerCenter or FTP clients. If you do not enter a listener port, the local PowerChannel
Server uses port 21 by default.
- The remote connector parameters. Enter the host name or IP address of the FTP
server you want to connect to through PowerChannel. You can enter a port for the FTP
server. If you do not enter a listener port, the local PowerChannel Server uses port 21
by default. You can also enter a timeout period in seconds from 0 to 100000. Any idle
connections between PowerChannel and FTP servers close after the timeout period
expires.
Note: Do not enter a timeout period when transferring target files to an FTP server in
PowerCenter.
For example, you want to connect to the FTP server serv1 with a timeout period of 1,000
seconds. Use the following parameter in the command:
-F=FTP!~serv1/1000
If the FTP server uses a port number other than 21, you must enter the port number in the
remote connector parameters. For example, use the following to connect to the FTP
server serv1 on listener port 22 with a timeout period of 1,000 seconds:
-F=FTP!~serv1:22/1000
cl Optional Enter the compression level. Valid compression levels are from 1 to 9 or none. Enter none
for no compression.
If you do not enter a compression level, PcCmd uses the compression level defined in the
PcCmd.properties file.
el Optional Enter the encryption level. Valid encryption levels are from 1 to 3 or none. Enter none for
no encryption.
If you do not enter an encryption level, PcCmd uses the encryption level defined in the
PcCmd.properties file.
w Optional Use the wait option if you want the PowerChannel Server to wait until it completes a
session before it responds to PcCmd with a message. Since sessions hosting PIPE
channels do not end until you stop them, set the wait option to no.
1. Enter the host information for the local PowerChannel Server in the FTP command or script:
open <local_PowerChannel_IPaddress> <port>
For example, to connect to a local PowerChannel Server at pchserv with port 22, enter the following
parameter in the FTP command:
open pchserv 22
2. Enter a valid user name for the remote FTP server.
3. Enter a valid password for the remote FTP server.
4. Complete the FTP command or script.
5. Run the FTP command or script.
When the session is running, the PowerChannel Server command window, the Event Viewer, and the
PowerChannel session log file display the following message:
Pipe Listener is accepting connections at port: <port> (forward to <host_name:port/timeout_period>)
For example, the local PowerChannel Server is listening for FTP client requests at port 21. It forwards the
requests to the FTP server at serv1:21. The timeout period is 1,000 seconds. The PowerChannel Server command
window and the session log file display the following message:
Pipe Listener is accepting connections at port: 21 (forward to serv1:21/Timeout=1000)
You can also monitor the PowerChannel session with the web client or PcCmd. For example, you can determine
the number of bytes the PowerChannel Servers transfer during the session.
You can stop the PowerChannel session with the web client or PcCmd.
When you replace the direct FTP connection between PowerCenter and the FTP server, you create a connection
between PowerChannel Servers to transfer the data. You configure the FTP connection in the PowerCenter
Workflow Manager. As long as the connection between PowerChannel Servers is open, use the FTP connection to
read flat file source data from an FTP server or write flat file target data to an FTP server whenever you run a
PowerCenter session.
When you configure the PowerCenter session, you replace the direct connection between PowerCenter and the
FTP server with a fast, secure PowerChannel connection. You create the PowerChannel connection between
PowerCenter and the FTP server by entering the PcCmd createpipe command from the command line of the local
PowerChannel Server, which resides in the same LAN as PowerCenter.
PcCmd createpipe starts a PowerChannel session to listen for requests from the Integration Service. The
PowerChannel session opens PIPE channels between the local PowerChannel Server and a remote
PowerChannel Server in the same LAN as the FTP server. The servers use the PIPE channels for transferring
source and target files between PowerCenter and the FTP server.
When you enter the PcCmd createpipe command, you enter connection information to the FTP server. The local
PowerChannel Server uses the connection information to forward file transfer requests from PowerCenter to the
FTP server through the remote PowerChannel Server. The PowerChannel Servers then transfer the file between
PowerCenter and the FTP servers.
After the PowerChannel Servers complete the file transfer tasks, the connection between PowerChannel and the
remote FTP servers closes. However, the PIPE channels connecting the PowerChannel Servers remain open until
you stop the PowerChannel session. The PIPE channels also remain open when file transfer between
PowerCenter and the FTP server fails. Keeping the connection open allows PowerChannel to transfer files
whenever you run PowerCenter session with the FTP connection in the session properties.
For example, you want to run a PowerCenter session to read data from a flat file source with an FTP connection.
You connect the local and remote PowerChannel Servers with PIPE channels. The local PowerChannel Server
then listens for file transfer requests from PowerCenter. When you run a PowerCenter session, the local
PowerChannel Server receives the file transfer request. It opens a connection to the remote FTP server through
the remote PowerChannel Server and forwards the file transfer request to the remote FTP server.
The remote PowerChannel Server compresses and encrypts the file from the remote FTP server according to the
PcCmdcreatepipe command and writes the file to the network. The local PowerChannel Server reads the file from
the network and decompresses and decrypts the file. It writes the file to the Integration Service. The connection
between PowerChannel Server and PowerCenter closes. The session hosting the connection between the
PowerChannel Servers continues to run until you stop the session.
When you to read source files from an FTP server and write target files to an FTP server through PowerChannel,
you can view the status of the files you transfer. You can also view the status of the PowerChannel session
hosting the connection between the PowerChannel Servers.
¨ A PowerChannel Server must exist in the same LAN as the Integration Service.
¨ A PowerChannel Server must exist in the same LAN as the FTP server.
¨ You must have a PowerChannel user account with a profile of user or admin.
¨ If you want to read files from a source, the source definition in the mapping must be flat file. Similarly, if you
want to write files to a target, the target definition in the mapping must be flat file.
1. Create a connection between PowerChannel Servers. When you create a connection between
PowerChannel Servers to transfer data during a PowerCenter session, do not use the timeout option in the -F
parameter of the PcCmdcreatepipe command.
2. Configure the FTP connection in PowerCenter.
3. Enter FTP as the connection type for the source or target in the PowerCenter session properties.
For example, to connect to a local PowerChannel Server at pchserv with port 22, enter the following host name
and port:
pchserv:22
To transfer source or target data with PowerChannel commands in a PowerCenter session, you use PcCmdget
and send commands in pre- and post-session commands. Use PcCmdget in the pre-session command dialog box
when you want to read data from a flat file source. Use PcCmdsend in the post-session command dialog box when
you want to write data to a flat file target. If the PcCmd command you want to use is in a .bat file, you can also use
the .bat file in the pre- or post-session commands. Enter the .bat filename in the pre- or post-session command
dialog box.
For example, you want to analyze customer transactional data stored in a file at the customer site. You want to get
the customer data file from the remote location, use the file as a source in a session, and write the output to a
target. To retrieve the customer data file and run the session, use PcCmd get in the PowerCenter pre-session
command. PowerCenter uses the PowerChannel command to get the customer data file before it runs the session.
¨ -r. Use the properties file option by running the PowerChannel configuration utility to specify the absolute path
to the PcCmd.properties file.
¨ -w. Use the wait option with the PcCmd get and PcCmd send commands in the pre- and post-session
commands. Set the value to “yes” for the wait option.
When you use PcCmd file transfer commands in a pre- or post-session command, use the -r option to enter the
absolute path to the PcCmd.properties file or the username.properties file. When you do not enter the absolute
path to a properties file, PcCmd cannot locate the properties file, and the command fails.
You must use the wait option when you use PcCmd file transfer commands inside a pre- or post-session
command. When you use the wait option with PcCmdget, the PowerChannel Server waits until the file transfer is
complete before it responds to PcCmd with a message. The Integration Service uses this prompt to start reading
from the source. As a result, the Integration Service starts reading the source file only after the PowerChannel file
transfer is complete. If you do not use the -w option in the pre-session command, the Integration Service might
start reading the file before the PowerChannel file transfer is complete.
Use the wait option with PcCmdsend to determine if the target file transfer succeeds. If you use the wait option in
PcCmd send, the PowerCenter session fails when the PowerChannel file transfer fails. You can view the
PowerChannel session log for details on the file transfer. If you do not use the wait option in PcCmd send, you
cannot determine whether the file transfer completes successfully. You can view the PowerChannel session log
file for the status of the PowerChannel session.
Note: You may not have access to the PowerChannel Server to check the PowerChannel session log file.
Therefore, use the wait option to ensure that you can determine if the file transfer succeeds.
¨ A PowerChannel Server must reside in the same LAN as the Integration Service.
¨ You must have a PowerChannel Server at the file transfer source and target locations.
¨ A certificate account for the remote PowerChannel Server must exist in the local PowerChannel repository.
¨ If you want to read files from a source, the source definition in the mapping must be flat file. Similarly, if you
want to write files to a target, the target definition in the mapping must be flat file.
¨ If you want to use PcCmd in a pre-session command, the source file in the session must have the same
filename and path as the filename you enter in the PcCmd get command. Similarly, if you want to use PcCmd
in a post-session command, the target file in the session must have the same filename and path as the
filename you enter in the PcCmdsend command.
¨ Enter None as the connection type for the source or target in the PowerCenter session properties.
Note: To use PcCmdget in a pre-session command, the source file in the session must have the same filename
and path as the target file in the PowerChannel file transfer.
1. In the Workflow Manager, locate the pre-session command field in the session properties of the session for
which you want to run the command.
2. Enter the PcCmd get command.
The following command syntax is a sample PcCmd get command:
PcCmd get -r=d:\PcCmd\PcCmd.properties -u=admin -p=test -S=127.0.0.1:7000 -sn=csksession -
f=authors,”d:\Program Files\Informatica\Integration Service\SrcFiles\authors”
-R=PowerChannel2@PowerChannel2:7000 -cl=9 -el=3 -T=none -w=yes
Note: You must use the -r and -w parameters with PcCmd get in the pre-session command.
You can also use a .bat file that contains PcCmd get in the post-session command field.
3. Close the pre-session command dialog box.
Note: To use PowerChannel in a post-session command, the target file you use in the session must have the
same filename and path as the source file in the PowerChannel file transfer.
1. In the Workflow Manager, locate the post-session command field in the session properties of the session for
which you want to run the command.
2. Enter the PcCmd send command.
The following command syntax is a sample PcCmd send command:
PcCmd send -r=d:\PcCmd\PcCmd.properties -u=admin -p=test -S=127.0.0.1:7000
-sn=csksession -f=”d:\Program Files\Informatica\Integration Service\TgtFiles\contact.out”,contact
-R=PChannel3@PChannel3:7000 -cl=9 -el=3 -T=both -w=yes
Note: You must use the -r and -w parameters with PcCmd send in the post-session command.
You can also use a .bat file that contains PcCmd send in the post-session command field.
3. Click OK to close the post-session command dialog box.
My file transfer session fails when I transfer the same file with staging multiple times in the same command.
When you transfer files with staging, each file is staged as a ZIP file at the target PowerChannel Server. For
example, if you transfer the file data1.txt with staging, the target PowerChannel Server temporarily stages the file
data1.txt.zip. If you transfer the file data1.txt more than once in the same command and set staging on both the
sending and receiving PowerChannel Servers, the target PowerChannel Server overwrites the first data1.txt.zip
file with the second. This causes the session to fail. For example, you use the following PcCmd get command:
PcCmd get -f=data1.txt; data2.txt; data1.txt, data3.txt -T=all
Use two separate file transfer commands when you transfer the same file with staging more than once between
PowerChannel Servers.
The FTP server stopped during a session. However, the session log indicates that the session was successful.
When you use an FTP connection through a PIPE channel to read source data, make sure that the FTP server
does not stop during the session. If the FTP server stops or fails during the session, restart the FTP server and
run the session again.
To use remote database sources and targets in a PowerCenter mapping, you need to create a mapping in the
Designer to define the data transfer. In the Workflow Manager, you configure a connection to the remote database
through PowerChannel. When you configure the connection, enter an active listener port number that the
PowerChannel Server uses to listen for data transfer requests from the Integration Service. You then create a
session for the mapping and use the PowerChannel connection to the database to extract, transform, and load
data.
When you want PowerCenter to read or write remote database data, you connect the Integration Service to a
remote PowerChannel Server. You set up the remote PowerChannel Server on the same network as the source or
target data. When you use a remote database as a source in the mapping, the remote PowerChannel Server
reads the data from the remote database and sends it to the Integration Service. When you use a remote
database as a target in the mapping, the remote PowerChannel Server writes the data received from the
Integration Service to the remote database.
Note: A PowerCenter session running in ASCII mode loads invalid data when the source is not valid ASCII. To
avoid loading invalid data, change the data movement mode for the Integration Service to run in Unicode mode.
You can connect to the following databases to extract and load data with PowerChannel:
¨ IBM DB2
¨ ODBC
70
¨ Oracle
¨ SQL Server
¨ A PowerChannel Server must exist in the same network as the remote database. The PowerChannel Server
needs to exist on the same machine as the remote database.
¨ The PROTOCOL attribute for the active listener you want to use to listen to data transfer requests from the
Integration Service must be generic.
¨ The USER_PROFILE attribute for the active listener that you want to use to listen for data transfer requests
from the Integration Service must be transport.
¨ The remote PowerChannel Server must be running.
When the Integration Service extracts data from a remote database source, the remote PowerChannel Server
compresses and encrypts the source data and sends it to the local PowerChannel Server. The local
PowerChannel Server decrypts and decompresses the data and passes it to the Integration Service. When you
use a remote database target in the mapping, the local PowerChannel Server encrypts and compresses the data
received from the Integration Service and sends it to the remote PowerChannel Server. The remote PowerChannel
Server decrypts and decompresses the data and writes it to the remote database.
¨ A PowerChannel Server must exist in the same network as the Integration Service. You can install the
PowerChannel Server on the same machine as the Integration Service.
¨ Encrypt the PROTOCOL attribute for the active listener you want to use on the remote PowerChannel Server.
¨ The USER_PROFILE attribute must be user or admin for the active listener you want to use on the remote
PowerChannel Server.
¨ Create a certificate account for the local PowerChannel Server in the remote PowerChannel repository.
When you want the Integration Service to read compressed and encrypted data from databases and write
compressed and encrypted data to databases, you must configure a local PowerChannel Server in addition to a
remote PowerChannel Server. The remote PowerChannel repository must contain a certificate account for the
local PowerChannel Server.
If you want the Integration Service to send data transfer requests to the local PowerChannel Server, you must
configure the ACTIVE_LISTENERS property with the PowerChannel configuration utility. You must ensure that the
value for the PORT attribute is not used by other applications on the local PowerChannel Server. You can also
enhance security for the PowerChannel Server by configuring the IP address and FILTER attributes for the
ACTIVE_LISTENERS property.
1. Create a mapping. Create an ODBC data source to connect to the source or target database to import
definitions.
2. Create a PowerCenter session. Configure a PowerChannel connection to enable the Integration Service to
access the remote database through PowerChannel.
3. Configure and start PowerChannel. Configure the remote PowerChannel Server to read data from remote
database sources and write data to remote database targets. If you use compression and encryption, you also
need to configure the local PowerChannel Server to compress and encrypt data before sending it to the
remote PowerChannel Server. You also need to configure the PowerChannel.properties file on the
PowerChannel Server from which the Integration Service requests data.
4. Create and schedule a workflow.
In the PowerCenter session log, the Integration Service associates each partition with its corresponding
PowerChannel session. The session log represents partitions in the following way:
{READER|WRITER}_1_1_x
where READER indicates that the Integration Service is reading data from a source, and WRITER indicates that
the Integration Service is writing data to a target. The x represents the partition number. For example,
READER_1_1_1 represents partition 1 when the Integration Service reads data from a source.
The following session log messages show a PowerChannel session associated with a partition to read data from a
DB2 source:
MASTER> PETL_24006 Starting data movement.
MAPPING> TM_6660 Total Buffer Pool size is 12000000 bytes and Block size is 64000 bytes.
READER_1_1_1> DBG_21438 Reader: Source is [EE72SRC], user [pcsrc10]
READER_1_1_1> BLKR_16051 Source database connection [EE72SRC_pcsrc10] codepage: [MS Windows Latin 1
(ANSI), superset of Latin1]
READER_1_1_1> CMN_1021 Database driver event...
CMN_1021 [DB2 Event Using Array Inserts. connect string = [EE72SRC]. userid = [pcsrc10]]
READER_1_1_1> BLKR_16003 Initialization completed successfully.
.
.
.
READER_1_1_2> BLKR_16019 Read [4] rows, read [0] error rows for source table [ALL_DATATYPES_400]
instance name [ALL_DATATYPES_400]
READER_1_1_1> BLKR_16019 Read [5] rows, read [0] error rows for source table [ALL_DATATYPES_400]
instance name [ALL_DATATYPES_400]
READER_1_1_1> BLKR_16008 Reader run completed.
.
.
.
MASTER> PETL_24012 Session run completed successfully.
You can also monitor the status of the PowerChannel data transfer session.
When you run a data transfer session between PowerChannel Servers, the local PowerChannel Server creates a
parent session to connect to the remote PowerChannel Server. After the local server connects to the remote
PowerChannel Server, the remote server creates a child session. When you transfer data between PowerCenter
and a remote database, the PowerChannel Server creates a parent session and a child session for each partition
configured in the PowerCenter session properties.
When you transfer data between PowerCenter and a remote database with a single PowerChannel Server, the
PowerChannel Server creates one session for each partition configured in the PowerCenter session properties.
You can run the following session management commands to manage data transfer sessions:
When you transfer data between PowerChannel Servers, you can also recover failed sessions.
74
When you monitor sessions, the web client displays the following information:
Account Name Account name of the user who starts the session.
End Time Time when the session completes successfully or fails. It can also refer to the time when the user stops
the session.
First Error Msg If you are displaying session information for a failed session, the PowerChannel Server displays the
reasons for the session failure.
Channel Name Name of the channel transferring the data. The PowerChannel Server names all channels it creates during
data transfer. A data transfer session can contain one channel or multiple channels depending on the data
transfer tasks.
Channel Type Depending on the data transfer, the PowerChannel Server uses the following channels:
- READSTREAM. The PowerChannel Server uses this channel to read data from the network.
- WRITESTREAM. The PowerChannel Server uses this channel to write data to the network.
- COMPRSTAGE. The PowerChannel Server uses this channel to stage files during transfer.
- DECOMPRSTAGE. The PowerChannel Server uses this channel to decompress staged files during file
transfer.
- PIPE. The PowerChannel Server uses this channel for transferring files between PowerCenter and an
FTP server and between FTP clients and servers.
- TRANSPORT. The PowerChannel Server uses this channel to transfer data between PowerCenter and
a remote database.
Start Time Time when the PowerChannel Server initiates the channel.
End Time Time when the channel completes successfully or fails. It can also refer to the time when the user stops
the channel. The channel stops when the user stops the session.
Forward For file transfer between PowerCenter and an FTP server or between FTP clients and servers, the
Connection PowerChannel Server lists the following information:
- Type of connection between PowerChannel and the Integration Service, FTP client, or FTP server. The
PowerChannel Server lists FTP for the connection type.
- Listener port number of the PowerChannel Server uses to listen for commands from the Integration
Service, FTP client, or FTP server.
- IP address and port of the FTP server.
- Timeout period after which idle connections between PowerChannel and the FTP server close.
Total Bytes to Size of the file in bytes to read from the local PowerChannel Server.
Read
Total Bytes to Size of the file in bytes to write to the remote PowerChannel Server.
Write
Read Bytes For file transfer between PowerChannel Servers, read bytes is the number of bytes read from the file
system.
For file transfer between PowerCenter and an FTP server or between FTP clients and servers, read bytes
is the number of bytes read from the Integration Service, FTP client, or FTP server.
For data transfer between PowerCenter and a remote database, read bytes is the number of bytes read
from the remote database or from PowerCenter during data transfer with two PowerChannel Servers.
Written Bytes For file transfer between PowerChannel Servers, written bytes is the number of bytes written to the file
system.
For file transfer between PowerCenter and an FTP server or between FTP clients and servers, written
bytes is the number of bytes written to the FTP client or server.
For data transfer between PowerCenter and a remote database, written bytes is the number of bytes
written to the remote database or from PowerCenter during data transfer with two PowerChannel Servers.
Sent Bytes Amount of data in bytes local PowerChannel Server sends to the remote PowerChannel Server.
Sent Blocks Number of packages the local PowerChannel Server sends to the remote PowerChannel Server.
Count
Received Bytes Amount of data in bytes the local PowerChannel Server receives from the remote PowerChannel Server.
Received Blocks Number of packages the local PowerChannel Server receives from the remote PowerChannel Server.
Count
Connector For file transfer between PowerCenter and an FTP server or between FTP clients and servers, the
Signature PowerChannel Server lists the following connection information:
- IP address and port the local PowerChannel Server uses to connect to the Integration Service, FTP
client, or FTP server.
- IP address and port of the Integration Service, FTP client, or FTP server.
Read Bytes Amount of data in bytes the PowerChannel Server reads during the connection with the Integration
Service, FTP client, or FTP server when transferring files between PowerCenter and an FTP server or
between FTP clients and servers.
Written Bytes Amount of data in bytes the PowerChannel Server writes during the connection with the Integration
Service, FTP client, or FTP server when transferring files between PowerCenter and an FTP server or
between FTP clients and servers.
Type During file transfer between PowerCenter and an FTP server or between FTP clients and server, the
PowerChannel Server lists the following information for the type of connection:
- FTP. Displays when PowerChannel connects to the Integration Service, FTP client, or FTP server.
- SOCKET. Displays when transferring files between PowerCenter and an FTP server or between FTP
clients and server.
- ERROR. Displays when the connection is not valid.
Status PowerChannel Server lists the following information for the status of the connection to the Integration
Service, FTP client, or FTP server when transferring files between PowerCenter and an FTP server or
between FTP clients and servers:
- Blocked. The Integration Service, FTP client, or FTP server cannot read data. Therefore, PowerChannel
cannot transfer data to or from the Integration Service, FTP client, or FTP server.
- Closed. The connection between PowerChannel and the Integration Service, FTP client, or FTP server
is closed.
- Init. PowerChannel is connecting to the Integration Service, FTP client, or FTP server.
- Ready. PowerChannel can transfer data to or from the Integration Service, FTP client, or FTP server.
Creation Time Time when PowerChannel Server connects to the Integration Service, FTP client, or FTP server.
Time Last Last time PowerChannel transferred data to or from the Integration Service, FTP client, or FTP server.
Accessed
1. On the Session Management page, use the Session Filter to display sessions
You can filter sessions by the following session properties:
Session Name To display sessions by name, enter the name of the sessions you want to display. Or, use the
wildcard character,%, as a suffix in the filter condition. For example, to display sessions that
begin with the letter “s,” use “s%” for session name.
Sessions for transferring data between PowerCenter and a remote database always use the
name TransportSession.
Records per Page Select one of the following values to limit the number of sessions to display on a page:
- 10
- 20
- 50
- 100
1. On the Session Management page, use the Session Filter to select Running Sessions from the Session
Status list and click Go.
The web client displays the sessions that are currently running on the PowerChannel Server.
Tip: Click Refresh to view an updated session list.
2. Select the sessions you want to stop and click Stop.
3. Click OK.
Recovering PowerChannel
Sessions
This chapter includes the following topics:
¨ Automatic Recovery, 80
¨ Manual Recovery, 80
¨ Troubleshooting, 81
For example, you use the PcCmd send command to transfer a 100 MB file from a local PowerChannel Server to a
remote PowerChannel Server. After transferring 50 MB, the session fails due to an error. When the local server
runs the session in recovery mode, it only transfers the part of the file that it failed to transfer. It starts transferring
the file from the first byte after the 50th megabyte.
When you transfer data between PowerChannel Servers, the local PowerChannel Server creates a parent
session. The remote PowerChannel Server creates a child session. When data transfer fails due to network
failure, the child session terminates. During recovery, the parent session tries to reconnect to the remote
PowerChannel Server. When the connection succeeds, the remote server creates a new child session with a new
session ID to complete the file transfer.
During the recovery session, the parent session communicates with the new child session to determine the
number of bytes that transferred successfully. The parent session then transfers the remaining bytes of data.
The local and remote PowerChannel Servers log recovery messages in the PowerChannel session log. The
PowerChannel Server creates a session log for the parent session and the child sessions that it runs.
The PowerChannel Server can recover a failed file transfer session in the following ways:
¨ Automatic recovery. The PowerChannel Server recovers a session when a data transfer session between
PowerChannel Servers fails due to network failure.
¨ Manual recovery. If the PowerChannel Server cannot recover a failed file transfer session between
PowerChannel Servers, you can recover the failed session manually. Before you run manual recovery, check
the PowerChannel session log and make sure you correct the error that caused the session to fail.
79
Automatic Recovery
PowerChannel lets you recover a data transfer session between PowerChannel Servers when the session fails
due to network failure. For example, you use a file transfer command to transfer a 50 MB file from a local
PowerChannel Server to a remote PowerChannel Server. After transferring 45 MB, a network error occurs and the
file transfer fails. In this event, PowerChannel tries to recover the file transfer session.
Note: When you transfer data between PowerCenter and a remote database with one PowerChannel Server,
PowerChannel cannot recover the session. You must rerun the PowerCenter session.
The PowerChannel Server tries to recover a session based on the configurations you set with the PowerChannel
configuration utility. Use the NUM_AUTO_RECOVERY_ATTEMPTS parameter in the PowerChannel.properties
file to set the number of times the PowerChannel Server tries to recover a failed connection between
PowerChannel Servers. For example, if you set this parameter to 10, the server tries to recover the connection 10
times before it fails automatic recovery.
When you run a PowerCenter session to read data from a remote database source or write data to a remote
database target with two PowerChannel Servers, and the PowerChannel session fails due to network failure, the
PowerCenter session continues to run while the local PowerChannel Server attempts to recover the
PowerChannel session based on the NUM_AUTO_RECOVERY_ATTEMPTS configuration in the
PowerChannel.properties file. If autorecovery fails for the PowerChannel session, the PowerCenter session fails.
If autorecovery fails for a file transfer session between PowerChannel Servers, you can try to recover the session
manually. When autorecovery fails for a session transferring files between PowerCenter and an FTP server or FTP
clients and servers, you must create a session with the PcCmdcreatepipe command and begin data transfer from
the first byte. When autorecovery fails a for session transferring compressed and encrypted data between
PowerCenter and a remote database, you must rerun the PowerCenter session.
Manual Recovery
If the PowerChannel Server cannot recover a failed file transfer session, use the web client to recover the session
manually by session ID. For example, you can manually recover a session when the remote server runs out of disk
space.
If your user account profile is admin, you can recover all failed sessions in the PowerChannel repository. If your
user account profile is user, you can only recover failed sessions you ran.
Before you manually recover a session, see the session log to determine the cause of the session failure. Correct
the errors.
Note: You cannot use manual recovery for a session that transfers data between PowerCenter and an FTP server
or between FTP clients and servers. Also, you cannot use manual recovery for a session that transfers data
between PowerCenter and a remote database.
Troubleshooting 81
CHAPTER 10
PcCmd uses a properties file to run commands. You can use the PcCmd configuration utility to configure PcCmd
properties.
¨ Use “/” to define path names when transferring files to or from a PowerChannel Server on UNIX.
82
Path Names with Spaces
The PowerChannel Server can locate files or folders with spaces when you enclose them in quotes. Complete one
of the following tasks to specify path names or filenames with spaces:
¨ Use double quotes around the folder name that contains spaces.
Define the path of the source file with “/”, as in the following example:
PcCmd get -u=admin2 -p=test -f=c:/admin2/data1.txt -cl=3 -el=3 -cs=yes
Similarly, when you run PcCmd send to transfer files from a PowerChannel Server on Windows to the remote
PowerChannel Server on UNIX, define the path of the destination files with “/”.
r Optional Enter the name the name of the properties file you want to modify. If you omit the
properties file, the PowerChannel Server opens the default properties file for you to
configure.
r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the default
properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in the
PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server.
Otherwise, PcCmd uses the PowerChannel Server in the PcCmd.properties file.
a Required Enter a user account name from 3 to 32 characters. Account names are not case
sensitive.
P Required Enter a password of at least three characters for the new user account.
l Required Enter one of the following values for the user account profile:
- admin
- user
- disabled
i Optional When you transfer files, enter the path of the default input folder for the new user account.
If the path contains spaces, enclose the path in double quotes.
You do not use this parameter when you transfer data between PowerCenter and remote
databases.
You can also use the $PC_USER and $PC_DATE server variables for the input folder
value.
o Optional When you transfer files, enter the path of the default output folder for the new user
account. If the path contains spaces, enclose the path in double quotes.
You do not use this parameter when you transfer data between PowerCenter and remote
databases.
You can also use the $PC_USER and $PC_DATE server variables for the output folder
value.
r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the default
properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in the
PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server.
Otherwise, PcCmd uses the PowerChannel Server in the PcCmd.properties file.
a Required Enter a certificate account name from 3 to 32 characters. Account names are not case
sensitive.
P Required Enter a password of at least three characters for the new certificate account.
H Optional Enter the default IP address of the PowerChannel Server where you want to register the
new certificate account. Otherwise, the PowerChannel Server creates the certificate
account without a default IP address.
t Optional Enter the default port of the PowerChannel Server where you want to register the new
certificate account. Use a port number from 1 to 65535. Otherwise the PowerChannel
Server creates the certificate account without a default port.
l Required Enter one of the following values for the certificate account profile:
- oneway
- twoway
i Optional When you transfer files, enter the path of the default input folder for the new certificate
account. If the path contains spaces, enclose the path in double quotes.
You do not use this parameter when you transfer data between PowerCenter and remote
databases.
You can also use the $PC_USER and $PC_DATE server variables for the input folder
value.
o Optional When you transfer files, enter the path of the default output folder for the new certificate
account. If the path contains spaces, enclose the path in double quotes. You do not use
this parameter when you transfer data between PowerCenter and remote databases.
You do not use this parameter when you transfer data between PowerCenter and remote
databases.
You can also use the $PC_USER and $PC_DATE server variables for the output folder
value.
¨ Account profile. Account profiles for user accounts that you can display are user, admin, and disabled.
¨ Default input folder. The default folder for input data files during file transfer.
¨ Default output folder. The default folder for output data files during file transfer.
r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the default
properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in the
PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server.
Otherwise, PcCmd uses the PowerChannel Server in the PcCmd.properties file.
¨ Account profile. Account profiles for certificate accounts are oneway and twoway.
¨ Default input folder. Default folder for input data files during file transfer.
¨ Default output folder. Default folder for output data files during file transfer.
r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the default
properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in the
PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server.
Otherwise, PcCmd uses the PowerChannel Server in the PcCmd.properties file.
F Optional Enter a certificate account name filter. When you use the certificate account name filter,
use the following guidelines:
- Use only one entry in the certificate account name filter.
- Use the certificate account name or the wildcard character, %, in the certificate account
name filter. Use the wildcard character as a suffix in the filter condition. For example, to
display certificate account names that begin with the letter “a,” use the following
command syntax to filter the accounts list: PcCmd displaycert -u=admin -p=test -
F=a%
¨ Profile. The user account profile. You can select the user, admin, or disabled account profile.
¨ Default input folder. The default folder for input data files during file transfer.
¨ Default output folder. The default folder for output data files during file transfer.
r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the default
properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in the
PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server.
Otherwise, PcCmd uses the PowerChannel Server in the PcCmd.properties file.
a Required Enter the name of the user account you want to edit.
l Optional To change the user account profile, enter one of the following values:
- user
- admin
- disabled
i Optional Use this option to change the default input folder path for the user account. If the path
contains spaces, enclose the path in double quotes.
You can also use the $PC_USER and $PC_DATE server variables for the input folder
value.
o Optional Use this option to change the default output folder path for the user account. If the path
contains spaces, enclose the path in double quotes.
You can also use the $PC_USER and $PC_DATE server variables for the output folder
value.
Tip: To remove default account attributes, leave the command parameter for the attribute blank. For example, to
remove the default input folder, enter -i=. For user accounts, you can remove the default attributes for the input
folder and output folder.
¨ Default port. The default port number of the local PowerChannel Server.
¨ Default input folder. The default folder for input data files during file transfer.
¨ Profile. The certificate account profile. User account profiles are oneway and twoway.
r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the default
properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in the
PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server. If
you omit this parameter, PcCmd uses the PowerChannel Server in the PcCmd.properties
file.
H Optional Changes the default IP address for the PowerChannel Server where you want to register
the certificate account.
t Optional Changes the default port for the PowerChannel Server where you want to register the
certificate account. Use a port number from 1 to 65535.
l Optional To change the certificate account profile, enter one of the following values:
- oneway
- twoway
i Optional Changes the default input folder path for the certificate account. If the path contains
spaces, enclose the path in double quotes.
You can also use the $PC_USER and $PC_DATE server variables for the input folder
value.
o Optional Changes the default output folder path for the certificate account. If the path contains
spaces, enclose the path in double quotes.
You can also use the $PC_USER and $PC_DATE server variables for the output folder
value.
r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the default
properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account. Otherwise, the PowerChannel Server looks for
the default password in the PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server. If
you omit this parameter, PcCmd uses the PowerChannel Server in the PcCmd.properties
file.
a Required Enter the name of the user account you want to remove.
r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the default
properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in the
PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server. If
you omit this parameter, PcCmd uses the PowerChannel Server in the PcCmd.properties
file.
a Required Enter the name of the certificate account you want to remove.
r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the default
properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account.Otherwise, PcCmd looks for it in the
PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server. If
you omit this parameter, PcCmd uses the PowerChannel Server in the PcCmd.properties
file.
fi | fn | fa | fs | a Required Filter options to monitor PowerChannel sessions running on the PowerChannel Server.
Use a single filter for monitoring. If you do not monitor PowerChannel sessions by session
ID, you can also use a combination filters. When you use more than one filter, the
PowerChannel Server monitors PowerChannel sessions that meet all filter conditions.
Choose from the following filters:
- fi. Use this option to filter PowerChannel sessions by session ID. For example, to
monitor session 317, use -fi=317.
- fn. Use this option to filter PowerChannel sessions by session name. For example, to
monitor a session named “dev01,” use -fn=dev01.
- fa. Use this option to filter PowerChannel sessions by session owner. For example, if
the user “admin” created the session, use -fa=admin.
- fs. Use this option to filter PowerChannel sessions by session status. Valid values for
session status are: running, completed, stopped, and failed. For example, to monitor all
sessions that are currently running, use -fs=running.
- a. Use this option to monitor all PowerChannel sessions on the PowerChannel Server.
When you use -fn or -fa to filter PowerChannel sessions, use the wildcard character, %,
as a suffix in the filter condition. For example, to filter session names that begin with the
letter “a,” use-fn=a%.
r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the default
properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in the
PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server. If
you omit this parameter, PcCmd uses the PowerChannel Server in the PcCmd.properties
file.
fi | fn | fa | a Required Filter options to stop PowerChannel sessions running on the PowerChannel Server. Use a
single filter or a combination of filters. When you use more than one filter, the
PowerChannel Server stops PowerChannel sessions that meet all filter conditions.
Choose from the following filters:
- fi. Filters PowerChannel sessions by session ID. For example, to stop session 317, use
-fi=317.
- fn. Filters PowerChannel sessions by session name. For example, to stop a session
named “dev01,” use -fn=dev01.
- fa. Filters PowerChannel sessions by session owner. For example, if the user “admin”
created the session, use -fa=admin.
- a. Stops all PowerChannel sessions running on the PowerChannel Server.
When you use -fn or -fa to filter PowerChannel sessions, use the wildcard character, %,
as a suffix in the filter condition. For example, to stop session names that begin with the
letter “a,” use -fn=a%.
Note: You cannot use manual recovery for a PowerChannel session to transfer data between PowerCenter and a
remote database.
r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the default
properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in the
PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server. If
you omit this parameter, PcCmd uses the PowerChannel Server in the PcCmd.properties
file.
s Required Enter the session ID for the PowerChannel session you want to recover.
Note: You cannot stop the PowerChannel Server from the PowerChannel command line.
r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the default
properties file.
If the path of the properties file contains spaces, enclose the path in double quotes.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in the
PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server. If
you omit this parameter, PcCmd uses the PowerChannel Server in the PcCmd.properties
file.
Running commands from an XML command file provides more flexibility in creating a command structure. When
you use a PcCmd command from the command line, you can only run one command at a time. You can run
multiple commands from the same XML command file. For example, you can run a batch of PowerChannel tasks
sequentially.
The command syntax you use in an XML command file differs from the PcCmd command syntax. For XML
command usage and syntax, see the PC.dtd file in the PowerChannel installation directory. The PowerChannel
Server parses the XML command file with the PC.dtd file.
¨ ExternalExecute. Runs an operating system command on the machine hosting the local PowerChannel Server.
¨ RemoteExecute. Runs a PowerChannel command on the remote PowerChannel Server. For example, use this
command if you want to monitor sessions running on a remote PowerChannel Server.
97
Transferring Files with an XML Command File (FileTransfer)
Use an XML command file to transfer files between the local PowerChannel Server and remote PowerChannel
Servers. You can transfer multiple files to multiple servers with an XML command file. You can also use a single
XML command file to run several file transfer commands. For example, you want to send five different files to five
separate servers. You also want to use different levels of compression and encryption for each file. Use a single
XML command file to perform all of these tasks.
Note: When you use an XML command file to transfer files, and you want to name the file transfer session, enter
the session name in the PcCmd run command when you run the XML command file.
When you use the FileTransfer command to get files with the same name from multiple remote PowerChannel
Servers, avoid overwriting existing files. Make sure files you transfer do not use the same name. Or, you can put
the files into separate directories according to the server you get the files from. Use the FileNamePair command
element in the command to specify the path and filename of the files you want to transfer.
Note: When you send files to multiple remote PowerChannel Servers, and the local PowerChannel Server fails to
connect to one of the remote servers, the local server fails the file transfer session.
The following table describes the command elements for the FileTransfer XML command:
Checksum Optional Enter yes to enable checksum for data integrity during the file transfer. Enter no to
disable checksum.
HostInfo Required Enter the certificate account name, IP address, and port for the remote PowerChannel
Server.
FileNamePair Required Enter the local and remote filenames. The local filename is the name of the source file
you want to transfer. The remote filename is the name of the target file. If you do not
enter a remote filename, the PowerChannel Server writes the source file to the target
with the same name as the source file. You cannot use an absolute path with the remote
filename.
To transfer multiple files with the same channel information, enter a separate
FileNamePair command element for each file you want to transfer.
ChannelInfo Required Enter the channel and transformer types for the local and remote channel.
The following example shows an XML command file for sending files to a remote PowerChannel Server. In this
example, the files data1.txt and data2.txt are being transferred with an encryption level of 3 and a compression
level of 4:
<?xml version='1.0' encoding='us-ascii'?>
XMLRequest Wait="no">
<XMLCmd>
<FileTransfer>
<HostInfo Account="PowerChannel1" IPAddress="208.200.214.000" PortNo="7000"/>
<FilenamePair LocalFilename="c:\data1.txt" RemoteFilename="data1.txt"/>
<FilenamePair LocalFilename="c:\data2.txt" RemoteFilename="data2.txt"/>
<ChannelInfo>
<LocalChannelInfo ChannelType="WRITESTREAM">
<Transformer Type="ENCRYPTOR" Param="3"/>
<Transformer Type="COMPRESSOR" Param="4"/>
</LocalChannelInfo>
<RemoteChannelInfo ChannelType="READSTREAM">
<Transformer Type="DECRYPTOR"/>
<Transformer Type="DECOMPRESSOR"/>
</RemoteChannelInfo>
</ChannelInfo>
</FileTransfer>
</XMLCmd>
</XMLRequest>
To run operating system commands on the PowerChannel Server, the RUN_EXTERNAL_EXECUTE property must
be set to all or admin. If RUN_EXTERNAL_EXECUTE is set to all, user accounts with the user or admin profile
can run external operating system commands. If RUN_EXTERNAL_EXECUTE is set to admin, only user accounts
with the admin profile can run external operating system commands.
The following table describes the command elements for the ExternalExecute XML command:
CommandLine Required Enter the external command syntax. Use operating system specific command
syntax.
RecoverCommandLine Optional Use this parameter if you want PowerChannel to run a different external command
during recovery mode.
The following example shows an XML command file for executing operating system commands. In this example,
the file data1.txt is removed from the local PowerChannel Server.
<?xml version='1.0' encoding='us-ascii'?>
<XMLRequest Wait="no">
<XMLCmd>
<ExternalExecute ExecutorType="OS" CommandLine="cmd /c del c:\data1.txt"/>
</XMLCmd>
</XMLRequest>
To run commands on a remote PowerChannel Server, set TRUST_REMOTE_EXECUTE to yes with the
PowerChannel configuration utility on the machine hosting the remote PowerChannel Server.
The following table describes the command elements for the RemoteExecute XML command:
Account Required Enter a certificate account for the remote PowerChannel Server.
IPAddress Optional Enter the IP address for the remote PowerChannel Server.
PortNo Optional Enter the port for the remote PowerChannel Server.
XMLRequest Required Enter the XML command you want to run on the remote PowerChannel Server.
u Optional Enter a user account name. Otherwise, PcCmd looks for the default user account name in
the PcCmd.properties file.
p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in the
PcCmd.properties file.
S Optional Enter the host name or IP address and port number of the local PowerChannel Server. If
you omit this parameter, PcCmd uses the default server defined in the PcCmd.properties
file.
sn Optional Enter a name for the session if you are running a FileTransfer command in the XML
command file. If you do not enter a name for the session, PcCmd assigns a name for the
session based on the session naming convention defined in the PcCmd.properties file.
x Required Enter the name and path of the XML command file. If the path of the XML file contains
spaces, enclose the path in double quotes.
For example, you want to create an XML file that lets you complete the following tasks:
¨ Send data2.txt to PowerChannel2 with staging at both the sending and receiving PowerChannel and encryption
at level 3.
¨ Get data3.txt from PowerChannel3 with staging at the receiving PowerChannel and encryption at level 1.
PowerChannel Messages
The PowerChannel Server displays messages when there is an error in the PowerChannel command. Messages
appear in the PowerChannel Server and session log files for the current instance of the session.
¨ General messages
¨ Server messages
¨ Session messages
¨ Repository messages
General Messages
General messages display when you encounter errors related to the server, session, or the repository.
User Response: Run the command again to connect to the remote PowerChannel Server.
10003 The connection request was rejected by the remote server: <error message>.
Explanation: The remote PowerChannel Server rejected the connection request for the session.
User Response: Verify that you used the correct certificate account to communicate with the remote
PowerChannel Server. Check the remote PowerChannel Server log.
103
10004 Peer channel creation failed: <error message>.
Explanation: The remote PowerChannel Server failed to create a channel for the session.
User Response: Check the remote PowerChannel session log for more information.
User Response: Check the network connection between the remote and local PowerChannel Servers.
Server Messages
Server messages result from PowerChannel Server errors.
User Response: Enter a valid listener port number from 1 to 65535 in the with the PowerChannel configuration
utility.
User Response: Enter a valid password at the command line with the -p command parameter.
Explanation: The value for the CRYPTOGRAPHY property in the PowerChannel.properties file is changed.
User Response: Make sure the value for the CRYPTOGRAPHY property is the same as the value for the
property when you installed the PowerChannel Server. For example, if the value for the
CRYPTOGRAPHY property was JSAFE/3DES when you installed the PowerChannel Server,
verify that JSAFE/3DES is the current value for the property.
User Response: Restore the repository from backup. If you have no repository backup, contact Informatica
Global Customer Support.
User Response: Enter a valid certificate account profile with the -l parameter in the PowerChannel import
command. Valid certificate account profiles are oneway and twoway.
User Response: Check the PC.dtd file in the PowerChannel root directory. See if the file is corrupt.
20020 Server could not find session with the ID: <session ID>.
Explanation: The PowerChannel Server could not locate the session with the given ID.
User Response: Verify the session ID in the server log file for the session you want to monitor.
User Response: Check the PowerChannel Server log file for more information.
User Response: Check the PowerChannel Server log file for more information. Or, check the PowerChannel
Server network settings.
User Response: Check the PowerChannel Server and session log files for a related message.
User Response: Check the PowerChannel Server log file for more information.
User Response: Restore the repository from backup. If you have no repository backup, contact Informatica
Global Customer Support.
20028 Invalid value for MAX_BLOCK_SIZE property: <value> (should be 1000 to 100,000,000).
Explanation: You entered the wrong value for MAX_BLOCK_SIZE in the PowerChannel.properties file.
User Response: Enter a value for MAX_BLOCK_SIZE from 1000 to 100000000 with the PowerChannel
configuration utility.
User Response: Enter a value for TOTAL_CHANNEL_MEMORY from 1000000 to 100000000 with the
PowerChannel configuration utility.
User Response: Enter a compression level from 1 to 9 or none for the COMPRESSOR transformer.
User Response: Enter an encryption level from 1 to 3 or none for the ENCRYPTOR transformer.
User Response: Enter a port number from 1 to 65535 with the PowerChannel configuration utility.
20037 Certificate password (-P option) for certificate file <filename> is not specified.
Explanation: You did not enter the -P parameter for the certificate password in the PowerChannel import
command.
User Response: Enter a password for the certificate account with the -P parameter.
User Response: Check the command parameters and enter a certificate filename with the -c parameter.
User Response: Check the PowerChannel installation for errors. If the installation fails, contact Informatica
Global Customer Support.
User Response: Check the PowerChannel Server and session log files for a related message.
20041 Invalid number was provided for number of attempts in auto recovery mode: <number>
(should be 0 to 1000).
Explanation: You entered a wrong value for NUM_AUTO_RECOVERY_ATTEMPTS, the maximum number
of auto recovery attempts, in the PowerChannel.properties file.
User Response: Enter a value for NUM_AUTO_RECOVERY_ATTEMPTS from 0 to 1000 with the
PowerChannel configuration utility.
User Response: Restore the repository from backup. If you have no repository backup, contact Informatica
Global Customer Support.
User Response: Create a repository with the PowerChannel init command. For more information, enter
PowerChannel init-help at the command line.
User Response: Check the PowerChannel Server log file for more information.
20047 Cannot remove session information from the repository: <error message>.
Explanation: PowerChannel cannot remove session information from the repository. The repository
contains inconsistencies.
User Response: Restore the repository from backup. If you have no repository backup, contact Informatica
Global Customer Support.
User Response: Enter a value for MAX_SESSIONS_MONITORED from 10 to 10000 with the PowerChannel
configuration utility.
User Response: Enter a valid certificate account profile with the -l parameter. Valid certificate account profiles
are oneway and twoway.
User Response: Check the additional error message for more information. Start the PowerChannel Server
again.
User Response: Check the detailed message in the session log file.
User Response: Verify that no other PowerChannel user is using the repository. Unlock the repository before
starting the PowerChannel Server. To remove the repository lock, run the PowerChannel
unlock command.
User Response: Check the PowerChannel Server log file for more information.
20061 Wrong value for the maximum number of concurrently running sessions: <number> (should
be 1 to 10000).
Explanation: You entered a wrong value for MAX_CONCURRENT_RUNNING_SESSIONS in the
PowerChannel.properties file.
User Response: Enter a value for MAX_CONCURRENT_RUNNING_SESSIONS from 1 to 10000 with the
PowerChannel configuration utility.
User Response: Check the PowerChannel.properties file and enter a valid number for
MAX_CONCURRENT_RUNNING_SESSIONS. This value must be less than the maximum
number of sessions that can be saved in the repository. To determine the maximum number
of sessions that can be saved in the repository, check the value of the
MAX_SESSIONS_MONITORED parameter in the PowerChannel.properties file with the
PowerChannel configuration utility.
20063 Server has reached the maximum number of concurrent sessions allowed: <number>.
Explanation: The PowerChannel Server has reached its allocated maximum number of concurrent
sessions.
User Response: Wait until one of the sessions completes before running the command again.
User Response: Enter a valid certificate account profile. Valid certificate account profiles are oneway and
twoway.
User Response: Enter a valid certificate account profile with the -l parameter. Valid certificate account profiles
are oneway and twoway.
User Response: Check the PowerChannel.properties file for the parameter with the PowerChannel
configuration utility. Verify the spelling of the parameter.
User Response: Check the RUN_EXTERNAL_EXECUTE parameter in the PowerChannel.properties file with
the PowerChannel configuration utility. Enter “all” to allow all users to run external commands
on the local PowerChannel Server. Or, enter “admin” to only allow users with the user
account profile of admin to run external commands on the local PowerChannel Server.
20069 Invalid value for RUN_EXTERNAL_EXECUTE property: <value>. (Supported values are all,
admin, and none.)
Explanation: You entered the wrong value for the RUN_EXTERNAL_EXECUTE parameter in the
PowerChannel.properties file.
User Response: Verify that you have write privileges for the operating system.
20075 Initial administrator user name is not specified in the command or properties file.
Explanation: The PowerChannel Server cannot find the initial user account name in the PowerChannel init
command or in the PowerChannel.properties file.
User Response: Enter the -u (user account name) parameter in the PowerChannel init command. Or, check
the USERNAME parameter in the PowerChannel.properties file. Verify that there is a valid
user name for the USERNAME parameter.
20076 Initial administrator password is not specified in the command or properties file.
Explanation: The PowerChannel Server cannot find the initial password for the administrator account in
the PowerChannel init command or in the PowerChannel.properties file.
User Response: Enter the -p (password) parameter in the PowerChannel init command. Or, check the
PASSWORD parameter in the PowerChannel.properties file with the PowerChannel
configuration utility.
20078 Cannot create a pipe data listener. Port <port number> is in use.
Explanation: The PowerChannel Server could not create a listener for file transfer requests from an FTP
client. The port you entered in the command is already in use.
User Response: Enter an available listener port number from 1 to 65535 with the PowerChannel configuration
utility.
20080 An unknown block header type <block header type> was received.
Explanation: The PowerChannel Server received an unknown block header type in the PIPE channel. The
block header may contain inconsistencies.
User Response: Start a session by running the PcCmd createpipe command. For more information, enter
PcCmd createpipe -help at the command line.
20081 An unexpected header sequence number was received. Expected: <header sequence
number>. Received: <header sequence number>.
Explanation: The PowerChannel Server received an unexpected header sequence number in the PIPE
channel. The header may be corrupt. Or, data blocks were lost.
User Response: Start a session by running the PcCmd createpipe command. For more information, enter
PcCmd createpipe -help at the command line.
User Response: Verify the name of the file you want to transfer. Enter the filename with the -f parameter in the
command.
User Response: Restart the PowerChannel Server. Run the command again.
User Response: Enter a port number for the PORT attribute in the ACTIVE_LISTENERS property with the
PowerChannel configuration utility.
20094 <listener> cannot accept connection from <hostname:port> because it does not meet the filter
<IP address / subnet>.
Explanation: The specified host name does not belong to the subnet you entered for the FILTER attribute
in the ACTIVE_LISTENERS property.
User Response: Verify that you entered the filter correctly with the PowerChannel configuration utility.
User Response: Set the PROTOCOL attribute to encrypted with the PowerChannel configuration utility.
User Response: Enter a valid IP address. For example, enter 127.0.0.1. Or, enter a valid subnet filter with the
PowerChannel configuration utility. For example, enter 255.255.0.0.
User Response: Set the protocol type to encrypted or generic with the PowerChannel configuration utility.
20099 <listener> cannot accept connection from <port> because profile <profile> is not supported.
Explanation: The PowerChannel Server cannot accept requests from the specified port. The account
profile associated with the listener port is not valid.
User Response: Enter a valid account profile for the listener port.
User Response: Make sure that the port is not in use by another application. Or, enter a port that is not in use
by another application.
Session Messages
Session error messages refer to errors resulting from the current PowerChannel session.
User Response: For more information, check the session log for this session and remote sessions.
30037 Account <account name> does not have privileges to complete task. Check the account name
and make sure the listener that you connect to has the appropriate profile.
Explanation: The account does not have the privileges to complete the task. Or, the PROFILE attribute for
the ACTIVE_LISTENERS property does not contain the appropriate account profile.
User Response: Verify the user account profile with the PcCmd displayuser command. Or, use a user account
with the admin profile to complete the task. Or, verify the PROFILE attribute for the
ACTIVE_LISTENERS property with the PowerChannel configuration utility.
User Response: Check the data transformer type. PowerChannel uses the following data transformer types:
COMPRESSOR, STAGECOMPRESSOR, ENCRYPTOR, and DECRYPTOR.
User Response: Verify each parameter with the PowerChannel.properties file with the PowerChannel
configuration utility.
User Response: Check the additional error message and the PowerChannel Server log file for more
information.
User Response: Check the additional error message and the PowerChannel Server log file for more
information.
User Response: Verify the XML command parameters if you used a direct XML command.
User Response: Contact Informatica Global Customer Support. Provide the XML command from the session
log file.
User Response: Contact Informatica Global Customer Support. Provide the XML command from the session
log file.
30047 Session encountered an error declaring internal <internal variable> variable: <error message>.
Explanation: PowerChannel cannot declare an internal variable.
30048 The connection to the remote server <account@hostname:port> failed: <error message>.
Explanation: You entered an invalid certificate account when connecting to the remote PowerChannel
Server.
User Response: Enter a valid certificate account to connect to the remote PowerChannel Server.
User Response: Check the network connection. Or, check the account parameters.
User Response: Check the command syntax for errors. Check the source and target files.
30053 Error waiting for the <channel name> channel to complete: <error message>.
Explanation: The PowerChannel session encountered an error while waiting for the channel to complete.
User Response: Check the additional error message for more information.
30054 Server encountered an error while obtaining session information: <error message>.
Explanation: PowerChannel cannot get session information. This might be due to repository failure.
User Response: Restore the repository from backup. If you have no repository backup, contact Informatica
Global Customer Support.
30055 Session encountered an error executing the <command name> external command: <error
message>.
Explanation: PowerChannel cannot run the external command.
User Response: Verify the command syntax and operating system user privileges.
User Response: Check the session log file to see which tasks were completed.
User Response: Check the session log file to see which tasks were completed.
User Response: Contact Informatica Global Customer Support. Provide the XML command from the session
log file.
30062 Source and target transformers are incompatible. Check the order of the transformers in the
command syntax: <transformer-transformer>.
Explanation: You entered the wrong order for the data transformers in the XML command.
User Response: Enter the correct order of the data transformers in the XML command syntax.
30063 There should not be any transformers provided for the channel of type “<channel type>”.
Explanation: You specified data transformers for a DECOMPRSTAGE channel. DECOMPRSTAGE does
not use any transformers.
User Response: The PowerChannel Server cannot perform recovery. It will send the file from the first byte.
User Response: If you receive this message during session recovery, execute the session again.
30071 Attempt to recover the wrong session (ID=<session ID>) from the remote session ID=<session
ID> at <hostname:port>.
Explanation: The PowerChannel Server found attempts to recover a session that does not belong to a
recovery request. This may be a remote PowerChannel Server error.
User Response: If you receive this message during session recovery, execute the session again.
30074 Error initializing the session with the ID: <session ID>.
Explanation: Session initialization failed.
User Response: Check the PowerChannel Server and session log files for more information.
User Response: Check the PowerChannel Server and session log files for more information.
User Response: Restore the repository from backup. If you have no repository backup, contact Informatica
Global Customer Support.
User Response: Check the session log file for a related message.
User Response: Check the error message in the PowerChannel Server and session log file for more
information.
30082 Specified user account profile <profile> is invalid (should be admin, user, or disabled).
Explanation: You entered an invalid user account profile.
User Response: Check the command parameters. Enter a valid user account profile. Valid user account
profiles are admin, user, and disabled.
30083 The specified account <account> does not exist in the repository.
Explanation: You entered an account that does not exist in the repository.
User Response: Verify the account name you used in the command.
User Response: Check the account name and create an account with a different name.
User Response: Check the account name and re-enter the command.
User Response: Use a different account with the admin profile to delete the account.
User Response: Verify the network settings. Or, verify that the remote PowerChannel Server is running.
User Response: If you want to transfer files between PowerChannel Servers, you can run manual session
recovery with PcCmd recover.
30092 User account <account name> cannot be used to connect to the remote server.
Explanation: You tried to connect to the remote PowerChannel Server with a user account.
User Response: Use a certificate account when connecting to a remote PowerChannel Server.
User Response: Run the command again. Or, verify that the PowerChannel Server is running. Or, verify that
the session exists.
30094 Server encountered an error while obtaining session information: <error message>.
Explanation: The PowerChannel Server cannot get session information. Or, internal error.
30097 The task cannot be executed in the child session for security reasons.
Explanation: You cannot execute this task in a child session.
User Response: Verify that TRUST_REMOTE_EXECUTION in the PowerChannel.properties file is set to yes
with the PowerChannel configuration utility.
User Response: Use a different user account with the admin profile to change the profile of the account.
30107 Specified certificate account profile <profile> is invalid (should be oneway or twoway).
Explanation: You did not enter a valid certificate account profile.
User Response: Check the command parameters. Enter a valid certificate account profile. Valid certificate
account profiles are oneway and twoway.
30108 Channels of type READSTREAM cannot be used to get files from multiple hosts.
Explanation: You cannot use READSTREAM channels for getting files from multiple hosts.
User Response: Enter a separate command for each PowerChannel Server you want to get files from.
30109 Session (ID=<session ID>) is not recoverable because it did not fail or stop.
Explanation: You cannot recover the session because it is currently running. You can only recover a failed
session.
30110 Session (ID=<session ID>) is not recoverable because it is not a parent session.
Explanation: You cannot recover the session because it is a child session. You can only recover a parent
session.
User Response: Verify that you entered the correct session ID.
30111 Source and compressed files contain different data. Recovery will restart file transfer.
Explanation: During session recovery, the PowerChannel Server determined that the compressed file does
not contain the same data as the source file. Recovery is not possible.
30117 Cannot use absolute path <path name> in the child session.
Explanation: You used an absolute path to the remote file in the command. You cannot enter the absolute
path to the remote file.
User Response: Check the original command for the remote file path.
30119 Wrong transformer: <transformer name>. Channel COMPRSTAGE should have only one
transformer: <transformer name>.
Explanation: COMPRSTAGE can only contain the STAGECOMPRESSOR data transformer.
User Response: Verify that you entered only one data transformer in the XML command.
User Response: Verify that the source file exists in the specified directory.
User Response: Enter a valid listener port number from 1 to 65535 for -F of the PcCmd createpipe command.
User Response: Enter a valid port number from 1 to 65535 in -F of the PcCmd createpipe command.
30138 The value <value> you provided for the pipe connection timeout is not valid (should be 0 to
100000).
Explanation: The value you provided for timeout in -F in the PcCmd createpipe command is not valid.
User Response: In the PcCmd createpipe command, enter a valid timeout value from 0 to 100000. For more
information about the timeout parameter in the PcCmd createpipe command, enter PcCmd
createpipe -help at the command line.
30155 Recovery failed. Remote server does not have enough memory.
Explanation: Internal error.
User Response: If the remote staged file is corrupt, run PcCmdget or PcCmdsend again with different names
for the source and target files.
User Response: Check if you connected to an external application with an FTP client. Verify that the remote
server is an FTP server.
User Response: Enter a valid listener port number from 1 to 65535 for the -F parameter of the PcCmd
createpipe command.
30178 File transfer in broadcast mode failed because one or more channels failed.
Explanation: One or more channels failed during file transfer to multiple remote PowerChannel Servers.
User Response: Check the additional error message for more information.
User Response: Start the PowerChannel Server. Run the PcCmdrecover command again.
User Response: Start a session by running the PcCmd createpipe command. For more information, enter
PcCmd createpipe -help at the command line.
Repository Messages
Repository messages appear when there is an error in the PowerChannel repository.
40001 Server was unable to create/update the repository object: <repository object>.
Explanation: The PowerChannel Server cannot create or update the repository object. This is most likely
an operating system problem.
User Response: Restore the repository from backup. If you have no repository backup, contact Informatica
Global Customer Support.
User Response: Restore the repository from backup. If you have no repository backup, contact Informatica
Global Customer Support.
User Response: Check the server log file for a related message.
User Response: Check the additional error message and the PowerChannel Server log file for more
information.
User Response: Restore the repository from backup. If you have no repository backup, contact Informatica
Global Customer Support.
User Response: Check the operating system user privileges to write files.
User Response: Check the PowerChannel Server log file for more information.
User Response: Restore the repository from backup. If you have no repository backup, contact Informatica
Global Customer Support.
User Response: Create a repository with PowerChannel init. For more information, enter PowerChannel init-
help at the command line.
User Response: Restore the repository from backup. If you have no repository backup, contact Informatica
Global Customer Support.
40015 Administrator account name <account name> does not exist in the repository.
Explanation: The repository cannot find the administrator account to open the repository.
User Response: Check the account name. Use a valid user account with the admin profile.
User Response: Run PowerChannel upgrade to upgrade the repository to the version recommended in the
error message. For more information, enter PowerChannel upgrade -help at the command
line.
User Response: Restore the repository from backup. If you have no repository backup, contact Informatica
Global Customer Support.
User Response: Restore the repository from backup. If you have no repository backup, contact Informatica
Global Customer Support.
User Response: Check the PowerChannel.properties file to verify that the REPOSITORY property contains
the correct path to the repository.
40025 Error loading session (ID=<session ID>) repository object: <error message>.
Explanation: The PowerChannel Server found a session repository object that contains inconsistencies.
The PowerChannel Server might be out of memory or disk space. Or, there was an error
during session execution.
User Response: Check the appropriate session log file and the PowerChannel Server log file for more
information.
User Response: Restore the repository from backup. If you have no repository backup, contact Informatica
Global Customer Support.
User Response: Check the remote PowerChannel Server log for more information.
Common Messages
Common error messages result from PcCmd, web client, or PowerChannel commands. If you get an error
message as the result of a PcCmd command, the error message appears at the PcCmd command line and in the
PcCmd log file. Web client error messages appear in the web client. PowerChannel error messages appear in the
PowerChannel Server and session log files for that session.
User Response: Verify that the JSAFE libraries are in the PowerChannel/lib directory.
User Response: Check the PowerChannel installation for the class file.
Explanation: If you see this message in the web client, there is an internal error.
Explanation: If you see this message in the web client, there is an internal error.
User Response: Check the installation for the properties file that uses the PowerChannel configuration utility.
User Response: Check the appropriate properties file for the specified parameter with the PowerChannel
configuration utility.
Explanation: If you see this message in the web client, there is an internal error.
User Response: Verify that you entered the correct directory for the filename.
User Response: Verify that the file is located in the right directory.
User Response: Check available JVM memory on the machine hosting the PowerChannel Server.
Explanation: The value for TOTAL_CHANNEL_MEMORY is higher than the value for JVM memory. The
value for TOTAL_CHANNEL_MEMORY cannot exceed the value for JVM memory.
User Response: Set the value for TOTAL_CHANNEL_MEMORY to be less than or equal to the value for JVM
memory.
User Response: Enter a valid value for LOG_LEVEL from 0 to 3 with the PowerChannel configuration utility.
50021 Certificate verification failed. Certificate file <filename> and password do not match.
Explanation: The system cannot decrypt the certificate file with the password you entered.
User Response: Make sure you used the correct password. Otherwise, there might be a corrupt or wrong
version of the certificate file.
Explanation: If you see this message in the web client, there is an internal error.
50024 The connection request was rejected by the server <host name:port>. Check the user account
name and password.
Explanation: The protocol handshake operation failed for an unknown reason.
User Response: Verify that you used a valid user account name and password.
Explanation: The encryption algorithm for the PowerChannel Server and client does not match.
User Response: Make sure the PowerChannel Server and client use the same encryption algorithm. For
example, if the encryption algorithm is set to JSAFE/RC2 for the CRYPTOGRAPHY property
in the PowerChannel.properties file, the properties file for the client must have the same
value for CRYPTOGRAPHY.
User Response: Verify that the JSAFE libraries are in the Java lib/ext directory.
User Response: Verify that the JAXP libraries are in the Java lib/ext directory.
User Response: Check the session log file. Enter the correct session ID.
User Response: Reencrypt the password with the PcPassword utility. Replace the old encrypted password
value.
User Response: Reencrypt the password with the PcPassword utility. Replace the old encrypted password
value.
User Response: Enter an account name from 3 to 32 characters without special characters.
50042 Session name <session name> cannot contain special characters like <character>.
Explanation: The session name contains special characters. Do not use special characters.
50043 User name <user account name> cannot contain special characters like <character>.
Explanation: The user account name contains special characters. Do not use special characters.
User Response: Reencrypt the password with the PcPassword utility. Replace the old encrypted password
value.
50046 The filter <filter> provided for the account name is invalid.
Explanation: You provided an invalid filter for account name. You can place variables after a string or
instead of a string. Or, use a string with no variables. You cannot place a variable inside a
string. For example, “account%” is a valid filter. “us%account” is not.
User Response: Enter a value from 1 to 65535 for the -R parameter in the command.
Explanation: The value for the SERVER_PORT property in the PcCmd.properties file is invalid.
50051 The account name <account name> is too long (should be from 3 to 32 characters).
Explanation: You provided an account name longer than 32 characters. This is not allowed.
50056 The account name <account name> is too short (should be from 3 to 32 characters).
Explanation: You entered an account name fewer than three characters. This is not allowed.
User Response: Enter a password, which is different than the account name.
User Response: Check the connector type in the command. Enter a valid connector type.
50064 Attempt to connect with a non-existent user account <account name> from <hostname:port>.
Explanation: The PowerChannel Server found connection attempts with an unknown user account.
User Response: This is likely user error. Do not take any action.
Explanation: If there are multiple sequential instances of this message, there might be an attempt to hack
the system.
50065 Attempt to connect with a non-existent certificate account <account name> from
<hostname:port>.
Explanation: The PowerChannel Server found connection attempts with an unknown certificate account.
User Response: This is likely a user error. Do not take any action.
Explanation: If there are multiple sequential instances of this message, there might be an attempt to hack
the system.
50066 Attempt to connect with the wrong password or key for user account <account name> from
<hostname:port>.
Explanation: The PowerChannel Server found connection attempts from a client with the correct user
account name, but the wrong account password or key.
Explanation: If there are multiple sequential instances of this message, there might be an attempt to hack
the system.
50067 Attempt to connect with the wrong password or key for certificate account <account name>
from <hostname:port>.
Explanation: The PowerChannel Server found connection attempts from a remote PowerChannel Server
with the correct certificate account name, but the wrong account password or key.
User Response: This is likely a user error from the remote PowerChannel Server. Do not take any action.
Explanation: If there are multiple sequential instances of this message, there might be an attempt to hack
the system.
User Response: Restore the repository from backup. If you have no repository backup, contact Informatica
Global Customer Support.
Explanation: If you received this message when logging in to the web client, you did not enter the listener
port number of the PowerChannel Server.
User Response: Enter the listener port number of the PowerChannel Server. Verify the listener port by
checking the SERVER_PORT with the PowerChannel configuration utility.
90003 The local and remote communication protocols are not compatible.
Explanation: Internal error. The protocol could not complete the handshake, because the two protocols
have incompatible versions.
User Response: Verify that the PowerChannel Server is running. Verify that the network is alive.
User Response: Enter the remote PowerChannel Server IP address in the command or in the account
properties.
User Response: Enter the remote PowerChannel Server port in the command parameters or in the account
properties.
User Response: Check the PowerChannel Server port value. Verify that it is between 1 and 65535.
User Response: Check the PowerChannel Server log filename. Check the operating system user privileges.
90016 Cannot log message (context:message) because of the error: <error message>.
Explanation: The PowerChannel Server cannot write the message to the PowerChannel Server log file.
This is probably an operating system error.
PcCmd Messages
PcCmd displays messages when there is an error in the PcCmd command. PcCmd messages appear at the
PcCmd command line and in the PcCmd log file.
User Response: Check the session log and the additional error message for more information. Or, contact
Informatica Global Customer Support.
User Response: Check the command parameters. Use PcCmd <command> -help for a list of optional and
required parameters for the command.
60039 PcCmd execution failed. See PcCmd log for more details.
Explanation: PcCmd command execution failed.
User Response: Check the PcCmd log file for more information.
60046 Session name <session name> cannot contain special characters like <character> in the
properties file.
Explanation: You entered a session name in the PcCmd.properties file, which contains special characters.
User Response: Do not use special characters for session names in the PcCmd.properties file.
60047 Log filename <filename> cannot contain special characters like <character> in the properties
file.
Explanation: You entered a log filename for the PCCMD_LOG parameter in the PcCmd.properties file,
which contains special characters.
User Response: Do not use special characters for the PCCMD_LOG parameter in the PcCmd.properties file.
For example, if you are running two or more client sessions from multiple browsers on the same client machine,
you may encounter an error message. If the message is because of an internal error, contact Informatica Global
Customer Support.
User Response: Check the command parameters. Use PcCmd <command> -help for a list of optional and
required parameters for the command.
70002 No session ID(s) specified in the command. Enter a session ID for individual sessions or use
the -a parameter in the command syntax.
Explanation: You did not enter the required session IDs in the command.
User Response: Enter the session IDs for the individual sessions, or use the -a parameter to display all
sessions in the command syntax.
User Response: Enter the account attributes you want to change. For example, if you want to change the
account profile, enter the -l command parameter followed by the new account profile.
User Response: Use the following command parameters to provide a filter for monitoring sessions: -fi, -fn, -fs, -
fa, -a.
70005 Invalid filter combination was provided for the PcCmd monitor command.
Explanation: You provided invalid filter information in the PcCmd monitor command.
User Response: Use the following command parameters to provide a filter for monitoring sessions: -fi, -fn, -fs, -
fa, -a.
70007 The value <value> provided for the -a option is not valid.
Explanation: You used the -a parameter improperly.
User Response: Use the -a parameter in the command to monitor all sessions. When you use the -a
parameter, do not provide any value after the parameter. For example, enter -a in the
command.
User Response: Verify that the XML file exists. Or, verify that you entered the correct path to the XML file in
the command.
70009 Using the PcCmd get command to receive files from multiple remote hosts is not allowed.
Explanation: You entered multiple remote PowerChannel Servers for the -R parameter in the PcCmdget
command. You can only use the PcCmdget command to get files from a single remote
PowerChannel Server.
User Response: Run a separate PcCmd get command for each remote PowerChannel Server you want to get
files from.
70010 The value <value> provided for staging option is not valid (should be all, receiving, or none).
Explanation: You provided an invalid value for -T, the staging parameter, in the command.
User Response: Enter a valid value for staging with the -T parameter.
70013 The value <value> provided for compression level is not valid (should be 1 to 9 or none).
Explanation: The value you provided for COMPRESSION_LEVEL is not valid.
User Response: Enter a value for COMPRESSION_LEVEL from 0 to 9 with the PcCmd configuration utility.
User Response: Check the PcCmd.properties file and enter a value for ENCRYPTION_LEVEL from 0 to 3.
User Response: Use the following command parameters to provide a filter for stopping sessions: -fi, -fn, -fs, -
fa, -a.
70017 Invalid filter combination was provided for the PcCmd stop command.
Explanation: You provided invalid filter information in the PcCmd stop command.
User Response: Use the following command parameters to provide a filter for stopping sessions: -fi, -fn, -fs, -
fa, -a.
70018 Specified certificate account profile <profile> is invalid (should be oneway or twoway).
Explanation: You entered an invalid certificate account profile.
User Response: Enter a valid certificate account profile in the command. Valid certificate account profiles are
oneway and twoway.
70019 Specified user account profile is invalid (should be admin, user, or disabled).
Explanation: You entered an invalid user account profile.
User Response: Enter a valid user account profile in the command. Valid user account profiles are admin,
user, and disabled.
A
CODE_PAGE property
in the PcCmd.properties file 52
accounts commands
PowerChannel 4 starting PowerChannel as an application 12
PowerChannel certificate accounts 17 compression
PowerChannel user accounts 16 in the FileTransfer XML command 98
active listeners in the PcCmd createpipe command 62
PowerChannel security enhancing 28 in the PcCmd get command 57
ACTIVE_LISTENERS property in the PcCmd send command 59
description 30 PowerChannel 2
admin PowerChannel database data transfer 71
PowerChannel profile 16 setting the default compression level 52
architecture COMPRESSION_LEVEL property
PowerChannel 3 description 52
authentication COMPRESSOR
PowerChannel 1 PowerChannel data transformer 26
COMPRSTAGE
PowerChannel channel 25
B
configuration utility
PowerChannel properties file 37
BEA WebLogic Server connections
PowerChannel installation and configuration 7 configuring type for PowerChannel 66
connectivity
PowerChannel 24
C
CRYPTOGRAPHY property
description 31
certificate accounts in PowerChannel.properties file 53
creating with PcCmd 85
creating with the PowerChannel web client 18
displaying PowerChannel with the web client 19
editing PowerChannel with the web client 22
D
editing with PcCmd 89 data compression
importing 44 PowerChannel 2
PcCmd, displaying 87 data encryption
PcCmd, removing 92 PowerChannel 2
PowerChannel 17 data transfer
PowerChannel oneway profile 17 PowerChannel channel types 25
PowerChannel twoway profile 17 data transformers
PowerChannel, removing with web client 23 PowerChannel 26
setting a default certificate account 53 database data transfer
certificate files PowerChannel installation 8
exporting with PcCmd 85 PowerChannel, compression and encryption 71
importing 44 PowerChannel, requirements with compression and encryption 71
PowerChannel directory 34 DECOMPRESSOR
channels PowerChannel data transformer 26
PowerChannel 25 DECOMPRSTAGE
PowerChannel data transfer types 25 PowerChannel channel 25
checksum DECRYPTOR
default checksum value 52 PowerChannel data transformer 26
in the FileTransfer XML command 98 disabled
in the PcCmd get command 57 PowerChannel profile 16
in the PcCmd send command 59 disabled accounts
CHECKSUM (property) PowerChannel user profile 16
description 52 displaying accounts
clients certificate accounts with PcCmd 87
PowerChannel 3 displaying PowerChannel accounts with the web client 19
136
I
displaying PowerChannel accounts
displaying user accounts with PcCmd 86
input folder
PowerChannel file transfer 56
E INPUT_FOLDER property
description 35
encryption installing
FIPS-certified encryption for PowerChannel 2 PowerChannel on Windows 9
in the FileTransfer XML command 98
in the PcCmd createpipe command 62
J
in the PcCmd get command 57
in the PcCmd send command 59
PowerChannel 2 JVM
PowerChannel database data transfer 71 PowerChannel application, configuring 12
PowerChannel, setting 7 PowerChannel service, configuring 12
setting the default encryption level 52
setting the encryption algorithm 53
L
ENCRYPTION_LEVEL property
description 52
ENCRYPTOR LICENSE property
PowerChannel data transformer 26 description 32
error messages log level
PcCmd 132 PowerChannel log files 33
PowerChannel 103 LOG_FOLDER property
PowerChannel client common 133 description 33
PowerChannel common 124 LOG_LEVEL property
EXPORT_DIR property description 33
description 34
F M
MAX_BLOCK_SIZE property
file integrity description 32
PowerChannel 2 MAX_CONCURRENT_RUNNING_SESSIONS property
file transfer description 35
between PowerCenter and an FTP server, PowerChannel MAX_SESSIONS_MONITORED property
requirements 65 description 34
flat file data between PowerCenter and FTP server 65 memory
flat file targets, sending to 68 PowerChannel buffer memory, allocating 32
path names on UNIX 83
PcCmd get command 57
N
PcCmd send command 59
PcCmd, receiving files 57
PcCmd, sending files 59 NUM_AUTO_RECOVERY_ATTEMPTS property
PowerCenter session, receiving files 67 description 35
PowerChannel input and output folders 56
PowerChannel, overview 55
O
PowerChannel, requirements 55
PowerChannel, troubleshooting 68
pre- and post-session command requirements for PowerChannel 67 oneway
text files from Windows to UNIX 57 PowerChannel certificate account profiles 17
with XML commands 98 operating system commands
filename executing with XML commands 99
PcCmd get and PcCmd send commands 57 RUN_EXTERNAL_EXECUTE property, setting 99
FIPS-certified encryption output folder
PowerChannel 2 PowerChannel file transfer 56
FTP connections OUTPUT_FOLDER property
for PowerChannel in PowerCenter 66 description 36
FTP file transfer
monitoring in the PowerChannel session log 66
P
monitoring PowerChannel in PowerCenter 66
PASSWORD property
H description 34
in PcCmd.properties 51
HOSTS property passwords
description 53 PcCmd.properties file, setting 51
path names
Index 137
file transfer on UNIX 83 PASSWORD 51
in PcCmd commands 83 PCCMD_LOG 50
$PC_DATE SERVER_ADDRESS 50
description 40 SERVER_PORT 50
export directory path, controlling 43 SESSION_NAME 51
log file path, controlling 42 STAGE 53
source and target file path, controlling 40 USERNAME 51
$PC_USER PcCmd properties file
description 40 configuring 53
export directory path, controlling 43 description 5
controlling log file path 42 PcCmd send
source and target file path, controlling 41 filename command parameter 57
PC.dtd file PCCMD_LOG property
supporting XML command parameters 97 description 50
PcCmd pcservice.log
configuration utility 53 PowerChannel log file 9
creating a certificate account 85 PcWeb properties file
displaying certificate accounts 87 description 5
displaying user accounts 86 PIPE
editing a certificate account 89 PowerChannel channel 25
editing a user account 88 PowerCenter
flat file sources and targets, transferring file data 67 file transfer between PowerCenter and FTP server 65
PowerChannel client 3 FTP connection for PowerChannel 66
PowerChannel Servers, connecting 62 PcCmd commands in pre- and post-session commands 66
PowerChannel sessions, monitoring 92 PowerChannel, troubleshooting 68
PowerChannel sessions, stopping 93 PowerCenter session log
properties 50 PowerChannel, database data transfer 73
properties file, configuring 53 PowerChannel, pre- and post-session command messages 67
receiving files from a remote PowerChannel Server 57 PowerChannel
remote PowerChannel servers, sending files 59 architecture 3
removing a certificate account 92 overview 1
removing a user account 91 starting as an application 12
session recovery 94 PowerChannel application
stopping the PowerChannel Server 95 starting 12
user account, creating 84 PowerChannel commands
with XML command files 100 PowerChannel import 44
PcCmd commands PowerChannel reencrypt 46
overview 82 PowerChannel unlock 46
path names 82 PowerChannel version 47
PcCmd createcert 85 PowerChannel for FTP
PcCmd createpipe 62 PowerChannel Servers, connecting 62
PcCmd createuser 84 sessions, monitoring 64
PcCmd displaycert 87 status of FTP files, monitoring 64
PcCmd displayuser 86 PowerChannel properties file
PcCmd editcert 89 configuration utility 37
PcCmd edituser 88 description 5
PcCmd get 57 properties 29
PcCmd get command in pre-session commands 67 PowerChannel relational database connection
PcCmd monitor 92 configuring 11
PcCmd recover 94 PowerChannel repository
PcCmd removecert 92 accounts 4
PcCmd removeuser 91 description 4
PcCmd run 100 overview 16
PcCmd send 59 reencrypting 46
PcCmd send command in post-session commands 68 restoring 14
PcCmd stop 93 sessions 5
PcCmd stopserver 95 unlocking 46
PcCmd get version number, verifying 47
filename command parameter 57 PowerChannel Server
PcCmd properties configuring 29
CHECKSUM 52 connectivity 24
CODE_PAGE 52 description 4
COMPRESSION_LEVEL 52 overview 24
configuring 50 properties 29
CRYPTOGRAPHY 53 protocol 25
ENCRYPTION_LEVEL 52 starting 11
HOSTS 53 starting as a service 12
overview 49 stopping 13
138 Index
stopping as a service 12 PowerChannel, receiving in PowerCenter 67
stopping with PcCmd 95 sources
variables 40 PowerChannel, monitoring FTP file transfer 66
web client, stopping 48 STAGE property
PowerChannel sessions description 53
default session name, setting 51 STAGECOMPRESSOR
description 5 PowerChannel data transformer 26
managing 74 staging files
PcCmd, monitoring 92 PowerChannel 26
PcCmd, stopping 93 setting the default staging value 53
recovery 79
web client, monitoring 74
web client, recovering 80
web client, stopping 78 T
PowerChannel.properties targets
description 29 PowerChannel, monitoring FTP file transfer 66
properties file command parameter timeout
in PcCmd commands in PowerCenter sessions 67 PowerChannel, FTP with PowerCenter 66
protocol PowerChannel, FTP without PowerCenter 62
PowerChannel Server 25 TOTAL_CHANNEL_MEMORY property
description 32
transferring files
R PowerChannel, overview 55
TRANSPORT
RC2 PowerChannel channel 25
PowerChannel encryption 7 3DES
READSTREAM PowerChannel encryption 7
PowerChannel channel 25 troubleshooting
recovery PowerChannel installation and configuration 14
NUM_AUTO_RECOVERY_ATTEMPTS property 80 PowerChannel, recovery 81
PowerChannel 2 PowerChannel, transferring files 68
PowerChannel sessions, manual 80 TRUST_REMOTE_EXECUTION property
PowerChannel, automatic 80 description 36
PowerChannel, overview 79 twoway
PowerChannel, troubleshooting 81 PowerChannel certificate account profiles 17
REMOVE_LOG_FILES_ON_PURGE property
description 35
removing accounts
certificate account with PcCmd 92 U
PowerChannel account with the web client 23 uninstalling
REPOSITORY property PowerChannel from Windows 14
description 30 UNIX
RUN_EXTERNAL_EXECUTE property path names for file transfer 83
description 36 transferring text files from Windows 57
upgrading
PowerChannel 9
S user
PowerChannel profile 16
security user accounts
PowerChannel, enhancing 28 creating with the PowerChannel web client 18
server authentication displaying PowerChannel with the web client 19
PowerChannel 2 displaying with PcCmd 86
server logs editing PowerChannel with the web client 21
PowerChannel log file directory, configuring 32 editing with PcCmd 88
SERVER_ADDRESS property PowerChannel admin profile 16
description 50 PowerChannel user profile 16
SERVER_ERR_LOG property PowerChannel, creating with PcCmd 84
description 33 PowerChannel, removing with web client 23
SERVER_LOG property removing with PcCmd 91
description 32 user authentication
SERVER_PORT property PowerChannel 2
description 50 USERNAME property
service start account description 33
PowerChannel installation prerequisite 9 in the PcCmd.properties file 51
SESSION_NAME property
description 51
source connections
configuring for PowerChannel 66
source files
Index 139
V
PowerChannel sessions, monitoring 74
PowerChannel sessions, recovering 80
variables PowerChannel sessions, stopping 78
export directory path, controlling 43 Windows
log file path, controlling 42 installing PowerChannel 9
$PC_DATE 40 transferring text files to UNIX 57
$PC_USER 40 WRITESTREAM
source and target file path, controlling 41 PowerChannel channel 25
W X
wait command parameter XML command files
description 59 creating 97
in PcCmd createpipe commands 62 example 101
with the PcCmd get command 57 executing commands on a remote PowerChannel Server 99
web client operating system commands, executing 99
connecting to PowerChannel 13 overview 97
creating a PowerChannel certificate account 18 PC.dtd file 97
creating a PowerChannel user account 18 PcCmd with XML command files 100
displaying PowerChannel accounts 19 transferring files 98
editing a PowerChannel certificate account 22 XML commands
editing PowerChannel user accounts 21 ExternalExecute 99
PowerChannel accounts, removing 23 FileTransfer 98
PowerChannel client 3 RemoteExecute 99
PowerChannel Server, stopping 48
140 Index