38162554 Informatica PowerChannel 9 0 User Guide

152
Informatica PowerChannel (Version 9.0) User Guide

Transcript of 38162554 Informatica PowerChannel 9 0 User Guide

Informatica PowerChannel (Version 9.0)

User Guide

Informatica PowerChannel User Guide

Version 9 .0December 2009

Copyright (c) 1998-2009 Informatica. All rights reserved.

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreementcontaining 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 PatentsPending.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable softwarelicense agreement and as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013©(1)(ii) (OCT 1988), FAR12.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 ordocumentation, please report them to us in writing.

Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter DataAnalyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B DataTransformation, Informatica B2B Data Exchange and Informatica On Demand are trademarks or registered trademarks of InformaticaCorporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names ortrademarks of their respective owners.

Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: CopyrightDataDirect Technologies. All rights reserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All RightsReserved. 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 rightsreserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems Incorporated. Allrights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © MicrosoftCorporation. All rights reserved. Copyright © Rouge Wave Software, Inc. All rights reserved. Copyright © Teradata Corporation. All rightsreserved. 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 islicensed 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 "ASIS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specificlanguage 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, allrights reserved; software copyright © 1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under theGNU Lesser General Public License Agreement, which may be found at http://www.gnu.org/licenses/lgpl.html. The materials are providedfree of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the impliedwarranties 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 WashingtonUniversity, 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. AllRights 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, <[email protected]>. All Rights Reserved.Permissions and limitations regarding this software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission touse, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyrightnotice and this permission notice appear in all copies.

The product includes software copyright 2001-2005 (©) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding thissoftware 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 regardingthis 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 thelicense 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 ProjectCopyright © 2002 Cable & Wireless Deutschland. Permissions and limitations regarding this software are subject to terms available athttp://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 andlimitations 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 aresubject 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 thissoftware 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 CommonDevelopment 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 andlimitations regarding this software are subject to terms available at http://xstream.codehaus.org/license.html. This product includessoftware 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. InformaticaCorporation does not warrant that this software or documentation is error free. The information provided in this software or documentationmay include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change atany time without notice.

NOTICES

This Informatica product (the “Software”) includes certain drivers (the “DataDirect Drivers”) from DataDirect Technologies, an operating company of Progress SoftwareCorporation (“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 NOTLIMITED 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 OFTHE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACHOF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

Part Number: PCH-USG-90000-0001

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viInformatica 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

Chapter 1: Understanding PowerChannel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Understanding PowerChannel Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

PowerChannel Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

User and Server Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Data Compression and Decompression. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Data Encryption and Decryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

File Integrity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

PowerChannel Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

PowerChannel Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

PowerChannel Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

PowerChannel Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

PowerChannel Properties Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2: Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Installation and Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Minimum System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Installing PowerChannel with Encryption Algorithms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Working with the Sample PowerChannel Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installing and Configuring PowerChannel for File Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installing and Configuring PowerChannel for Database Data Transfer. . . . . . . . . . . . . . . . . . . . 8

Upgrading PowerChannel from a Previous Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installing PowerChannel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installing PowerChannel on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installing PowerChannel on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Configuring PowerChannel Components on PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Starting the PowerChannel Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

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

Chapter 3: Administering PowerChannel Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Administering PowerChannel Accounts Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Certificate Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Working with PowerChannel Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Creating a User Account with the Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Creating a Certificate Account with the Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Displaying Accounts with the Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Editing a User Account with the Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Editing a Certificate Account with the Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Removing an Account with the Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 4: Administering the PowerChannel Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Administering the PowerChannel Server Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

PowerChannel Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

PowerChannel Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Working with Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Working with Data Transformers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Working with PowerChannel Listeners. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Configuring Client Access Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Configuring the PowerChannel Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

PowerChannel Server Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuring the PowerChannel Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Working with PowerChannel Server Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Controlling Source and Destination File Paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Controlling the Log File Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Controlling Export Directory Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Working with PowerChannel Server Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Configuring the PowerChannel Properties File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Importing a Certificate Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Reencrypting the PowerChannel Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Unlocking the PowerChannel Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Verifying the PowerChannel Repository Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Stopping the PowerChannel Server with the Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

ii Table of Contents

Chapter 5: Configuring PcCmd Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Configuring 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

Chapter 6: Flat File Data Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Flat File Data Transfer Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Transferring Files Between PowerChannel Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Requirements for File Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Working with Input and Output Folders During File Transfer. . . . . . . . . . . . . . . . . . . . . . . . . 56

Entering Filenames in PcCmd get and PcCmd send Commands. . . . . . . . . . . . . . . . . . . . . . . 57

Transferring Text Files from Windows to UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Receiving Files from a Remote PowerChannel Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Sending Files to Remote PowerChannel Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Transferring Files Between FTP Clients and Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Requirements for Transferring Files Between FTP Clients and Servers . . . . . . . . . . . . . . . . . . 61

Transferring Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Transferring Source and Target Files in PowerCenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Transferring Files Between PowerCenter and an FTP Server. . . . . . . . . . . . . . . . . . . . . . . . . 65

Working with PcCmd Commands in PowerCenter Sessions for File Transfer. . . . . . . . . . . . . . . 66

Troubleshooting a Flat File Data Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Chapter 7: Working with Database Sources and Targets. . . . . . . . . . . . . . . . . . . . . . . . . . 70Working with Database Sources and Targets Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Requirements for Transferring Database Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Transferring Data with Compression and Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Configuring PowerChannel for Data Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Configuring the Remote PowerChannel Server Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Configuring the Local PowerChannel Server Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Table of Contents iii

Configuring a Mapping and Workflow for PowerChannel Data Transfer. . . . . . . . . . . . . . . . . . . . . 72

Viewing the PowerCenter Session Log for Database Data Transfer. . . . . . . . . . . . . . . . . . . . . . . . 73

Troubleshooting a PowerChannel Database Data Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Chapter 8: Managing PowerChannel Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Managing PowerChannel Sessions Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Monitoring PowerChannel Sessions with the Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Stopping Sessions with the Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Chapter 9: Recovering PowerChannel Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Recovering PowerChannel Sessions Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Automatic Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Manual Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Chapter 10: Running PcCmd Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Running PcCmd Commands Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Path Names in PcCmd Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Editing the Properties File with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Creating Accounts with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Creating a User Account with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Creating a Certificate Account with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Displaying Accounts with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Displaying User Accounts with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Displaying Certificate Accounts with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Editing Accounts with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Editing a User Account with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Editing a Certificate Account with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Removing Accounts with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Removing a User Account with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Removing a Certificate Account with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Monitoring PowerChannel Sessions with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Stopping PowerChannel Sessions with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Recovering PowerChannel Sessions with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Stopping the Server with PcCmd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Chapter 11: Working with XML Command Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Working with XML Command Files Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Creating an XML Command File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Transferring Files with an XML Command File (FileTransfer). . . . . . . . . . . . . . . . . . . . . . . . . 98

Executing Operating System Commands (ExternalExecute). . . . . . . . . . . . . . . . . . . . . . . . . 99

Executing Commands on a Remote PowerChannel Server (RemoteExecute). . . . . . . . . . . . . . 99

Running an XML Command File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

iv Table of Contents

XML Command File Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Appendix A: PowerChannel Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103PowerChannel Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

General Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Server Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Session Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Repository Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Common Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

PcCmd Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Client Common Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Table of Contents v

PrefaceThe Informatica PowerChannel User Guide provides information to install and configure PowerChannel, administerthe PowerChannel repository, transfer data from sources to targets, and manage PowerChannel sessions. It iswritten for information services developers and software engineers who are responsible for extracting data fromdifferent sources to implement a data warehouse.

Informatica Resources

Informatica Customer PortalAs an Informatica customer, you can access the Informatica Customer Portal site at http://my.informatica.com. Thesite contains product information, user group information, newsletters, access to the Informatica customer supportcase management system (ATLAS), the Informatica How-To Library, the Informatica Knowledge Base, theInformatica Multimedia Knowledge Base, Informatica Documentation Center, and access to the Informatica usercommunity.

Informatica DocumentationThe Informatica Documentation team takes every effort to create accurate, usable documentation. If you havequestions, comments, or ideas about this documentation, contact the Informatica Documentation team throughemail at [email protected]. We will use your feedback to improve our documentation. Let usknow 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.

Informatica Web SiteYou can access the Informatica corporate web site at http://www.informatica.com. The site contains informationabout Informatica, its background, upcoming events, and sales offices. You will also find product and partnerinformation. The services area of the site includes important information about technical support, training andeducation, and implementation services.

Informatica How-To LibraryAs an Informatica customer, you can access the Informatica How-To Library at http://my.informatica.com. The How-To Library is a collection of resources to help you learn more about Informatica products and features. It includesarticles and interactive demonstrations that provide solutions to common problems, compare features andbehaviors, and guide you through performing specific real-world tasks.

vi

Informatica Knowledge BaseAs an Informatica customer, you can access the Informatica Knowledge Base at http://my.informatica.com. Usethe 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 havequestions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team throughemail at [email protected].

Informatica Multimedia Knowledge BaseAs an Informatica customer, you can access the Informatica Multimedia Knowledge Base at http://my.informatica.com. The Multimedia Knowledge Base is a collection of instructional multimedia files that helpyou learn about common concepts and guide you through performing specific tasks. If you have questions,comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Base team throughemail at [email protected].

Informatica Global Customer SupportYou can contact a Customer Support Center by telephone or through the WebSupport Service. WebSupportrequires a user name and password. You can request a user name and password at http://my.informatica.com.

Use the following telephone numbers to contact Informatica Global Customer Support:

North America / South America Europe / Middle East / Africa Asia / Australia

Toll Free+1 877 463 2435 Standard RateBrazil: +55 11 3523 7761Mexico: +52 55 1168 9763United States: +1 650 385 5800

Toll Free00 800 4632 4357 Standard RateBelgium: +32 15 281 702France: +33 1 41 38 92 26Germany: +49 1805 702 702Netherlands: +31 306 022 797Spain and Portugal: +34 93 480 3760United Kingdom: +44 1628 511 445

Toll FreeAustralia: 1 800 151 830Singapore: 001 800 4632 4357 Standard RateIndia: +91 80 4112 5738

Preface vii

viii

C H A P T E R 1

Understanding PowerChannelThis chapter includes the following topics:

¨ Understanding PowerChannel Overview, 1

¨ PowerChannel Concepts, 1

¨ PowerChannel Architecture, 3

Understanding PowerChannel OverviewInformatica PowerChannel lets you transfer large amounts of data with encryption and compression across a widearea network (WAN) or across firewalls in an Internet environment.

You can transfer files between PowerChannel Servers and between FTP clients and servers. PowerChannel alsolets you read flat file and relational source data and write flat file and relational target data during a PowerCentersession. You can transfer relational data between PowerCenter and a database on a local area network (LAN) orWAN. You can also transfer the database data in compressed and encrypted format.

Note: PowerChannel does not support database data transfer on Linux.

PowerChannel ConceptsPowerChannel uses the following concepts to ensure fast, secure, and reliable data transfer:

¨ User and server authentication

¨ Data compression and decompression

¨ Data encryption and decryption

¨ File integrity

¨ Recovery

User and Server AuthenticationPowerChannel uses accounts to authenticate users and PowerChannel Servers. To ensure that only authorizedusers can use PowerChannel to transfer data, PowerChannel uses the following two stages of authentication:

¨ User authentication

¨ Server authentication

1

RELATED TOPICS:¨ “PowerChannel Protocol” on page 25

User AuthenticationWhen you run a command to run a PowerChannel task, you enter a PowerChannel user account name andpassword as part of the command parameters. The PowerChannel Server uses the user account name andpassword to authenticate you as a valid PowerChannel user. When the authentication succeeds, thePowerChannel Server runs the user command. PowerChannel clients use a secure protocol to communicate withthe server. It exchanges data with the server in encrypted format.

Server AuthenticationWhen you transfer data from a local PowerChannel Server to a remote PowerChannel Server, the remote servermust authenticate the local server as a trusted server. To send data to a remote server, the local server must havea certificate account in the remote PowerChannel repository. When you run a command to transfer data, you enterthe remote PowerChannel certificate account name as part of the command parameters. The remotePowerChannel Server uses the certificate account name to authenticate the local server. When the authenticationsucceeds, 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.

Data Compression and DecompressionWhen you use PowerChannel to transfer data, you can compress the data before extracting or loading it.PowerChannel uses the zip compression algorithm to compress and decompress the data.

Data Encryption and DecryptionWhen you use PowerChannel to transfer data, you can encrypt the data before extracting or loading it.PowerChannel uses the RSA Crypto-J libraries with the RC2 and 3DES encryption algorithms for data encryptionand decryption. With the RSA Crypto-J libraries, PowerChannel provides FIPS-certified encryption using the 3DESencryption algorithm.

File IntegrityPowerChannel 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. Thisprevents the file from data corruption during file transfer. PowerChannel uses the CR32 checksum algorithm toperform integrity checking.

RecoveryPowerChannel lets you recover sessions that fail due to errors. When data transfer between PowerChannelServers fails due to network failure, PowerChannel can recover the session. If the PowerChannel Server cannotrecover the session, the PowerChannel session fails. When the PowerChannel Server cannot recover a failed filetransfer PowerChannel session, use manual recovery.

RELATED TOPICS:¨ “Recovering PowerChannel Sessions” on page 79

2 Chapter 1: Understanding PowerChannel

PowerChannel ArchitectureInformatica PowerChannel architecture includes the following components:

¨ PowerChannel clients. PowerChannel uses a web client and the PcCmd command line program to runcommands to the PowerChannel Server.

¨ PowerChannel Server. PowerChannel implementation requires a PowerChannel Server installation at theremote site. When you use PowerChannel to read or write flat file data, or when you want to compress orencrypt data using PowerChannel, you also need to install a PowerChannel Server at the local site. ThePowerChannel Server listens to requests from PcCmd, the web client, the PowerCenter Client, and remotePowerChannel Servers to run PowerChannel sessions.

¨ PowerChannel repository. PowerChannel uses an encrypted repository that stores information aboutPowerChannel accounts and sessions.

¨ PowerChannel properties files. The PowerChannel Server and clients use a set of properties files. Use thedefault values set values in the properties files to run the PowerChannel Server and clients using aconfiguration utility.

PowerChannel ClientsPowerChannel uses the following client applications to run commands to the PowerChannel Server:

¨ Web client

¨ PcCmd

Web ClientUse the PowerChannel web client to manage PowerChannel accounts and sessions and stop the PowerChannelServer from a web browser. When you run a command from the web client, the web client translates the commandinto an XML request and passes the request to the PowerChannel Server. The server receives the request andruns the user command.

PcCmdPcCmd is the command line program you use to run commands to the PowerChannel Server. Use PcCmdcommands to run PowerChannel tasks. When you run a PcCmd command, PcCmd translates the command intoan XML request and passes the request to the server. The server receives the request and runs the usercommand.

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 asecure protocol. It exchanges data with the server in encrypted format for security.

Use PcCmd to complete the following tasks:

¨ Transfer files. Use PcCmd to run commands to transfer files between PowerChannel Servers. You can alsouse PcCmd to create a PowerChannel connection to transfer files between the Integration Service and an FTPserver 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 PowerChannelrepository.

PowerChannel Architecture 3

¨ Run an XML command file. Use PcCmd to run an XML command file. An XML command file lets you run filetransfer commands from an XML file. When you use an XML command file, you have more flexibility instructuring commands.

¨ Stop the PowerChannel Server. Use PcCmd to stop the PowerChannel Server.

PowerChannel ServerThe PowerChannel Server reads and writes flat file and database data. The server listens to user requests fromPcCmd, the web client, the Integration Service, and remote PowerChannel Servers on a listener port and runsPowerChannel sessions to complete the tasks. When you read or write flat file data or use compression orencryption, install a PowerChannel Server in the same LAN as the Integration Service. You also need to install aPowerChannel Server in the same LAN as the remote source or target. Local and remote PowerChannel Serverscommunicate 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. Thelocal 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 PowerChannelServer receives data from the Integration Service. It compresses and encrypts the data before sending it to theremote PowerChannel Server. The remote PowerChannel Server decrypts and decompresses the data. Theremote PowerChannel Server then writes the data to the target. You can administer the PowerChannel Serverfrom the PowerChannel command line.

RELATED TOPICS:¨ “Administering the PowerChannel Server” on page 24

PowerChannel RepositoryThe PowerChannel Server creates an encrypted file-based repository during installation. It creates thePowerChannel repository in the repository folder under the PowerChannel root directory. The PowerChannelrepository stores information that the PowerChannel Server, web client, and PcCmd use to run commands.

The PowerChannel repository stores information about the following objects:

¨ PowerChannel accounts

¨ PowerChannel sessions

AccountsPowerChannel uses accounts to authenticate users and PowerChannel Servers. PowerChannel uses useraccounts 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 accountsrequire a password for authentication. When you run a command, you provide the PowerChannel user accountname and password as part of the command parameters. Or, you provide the PowerChannel account name andpassword in the PowerChannel properties files.

To communicate with remote PowerChannel Servers to transfer data, a PowerChannel Server uses a certificateaccount to authenticate itself as a valid server. To send data to a remote server, the local PowerChannel Servermust have a certificate account in the remote PowerChannel repository.

Certificate accounts use account profiles to define privileges for the PowerChannel accounts. A certificate accountcan have a profile of oneway or twoway.

4 Chapter 1: Understanding PowerChannel

User accounts also use account profiles to define the privileges for the PowerChannel accounts. A user accountcan have a profile of admin, user, transport, or disabled.

RELATED TOPICS:¨ “Certificate Accounts” on page 17

¨ “User Accounts” on page 16

SessionsThe PowerChannel repository also stores information about PowerChannel sessions. A PowerChannel sessionincludes 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 sessionto write flat file data through PowerChannel. When the local PowerChannel Server receives the request, it initiatesa session to write the flat file to a remote PowerChannel Server. The PowerChannel repository stores sessioninformation for PowerChannel session recovery purposes.

RELATED TOPICS:¨ “Managing PowerChannel Sessions” on page 74

¨ “Recovering PowerChannel Sessions” on page 79

PowerChannel Properties FilesThe PowerChannel Server and clients use a set of properties files to run. For example, the server uses thePowerChannel.properties file to run. Similarly, PcCmd and the web client use their own properties files. Use thedefault values or set values in the properties files to run the server and clients using a configuration utility.

The following table describes the properties files for the PowerChannel Server and clients:

Properties Files Description

PowerChannel.properties PowerChannel Server uses this properties file to run.

PcCmd.properties PcCmd uses this properties file to run PcCmd commands.

PcWeb.properties Web client uses this properties file to run web client commands.

PowerChannel Architecture 5

C H A P T E R 2

Installation and ConfigurationThis chapter includes the following topics:

¨ Installation and Configuration Overview, 6

¨ Installing PowerChannel, 9

¨ Configuring PowerChannel Components on PowerCenter, 11

¨ Starting the PowerChannel Server, 11

¨ Running PowerChannel Commands, 13

¨ Restoring the Repository, 14

¨ Uninstalling PowerChannel, 14

¨ Troubleshooting a PowerChannel Installation, 14

Installation and Configuration OverviewTo run PowerChannel, you install the PowerChannel Server and PcCmd. You can also install the PowerChannelweb client on Windows to communicate with the PowerChannel Server.

The PowerChannel Server communicates with PcCmd, the web client, the Integration Service, and otherPowerChannel Servers using the TCP/IP protocol. Install the PowerChannel Server, PcCmd, the web client, andthe Integration Service on a network that can establish TCP/IP connections.

You can configure PowerCenter to use PowerChannel to transfer data between the PowerCenter IntegrationService and remote databases.

Install the PowerChannel Server on a machine with a static IP address. Otherwise, you cannot use default serverparameters 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, youmust install the PowerChannel Server on Windows. When you install PowerChannel as a service, thePowerChannel Server starts when you log in to Windows. It also stops when you shut down Windows. When yourun PowerChannel as an application, you must start and stop the PowerChannel Server manually.

6

Minimum System RequirementsThe following table describes the system requirements to run the PowerChannel Server and clients:

PowerChannelComponent

OperatingSystem

RAM Description

PowerChannelServer

Windows,UNIX

128 MB Install the PowerChannel Server on Windows or UNIX (Solaris, HP-UX,AIX, Linux).

PcCmd Windows,UNIX

64 MB Install PcCmd on Windows or UNIX (Solaris, HP-UX, AIX, Linux). Youcan install PcCmd on the machine running the PowerChannel Server oron 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 themachine running the PowerChannel Server or on a Windows clientmachine that can access the local PowerChannel Server.The web client requires BEA WebLogic Server. Make sure a web serveris installed on the web client machine.

PowerChannel uses Java Runtime Environment (JRE). The installation program installs JRE when you installPowerChannel.

Before You BeginComplete the following tasks before you install the web client on Windows:

¨ 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 webclient.

Complete the following task if you want to read data from a remote source or write data to a remote target during aPowerCenter session:

¨ Install PowerCenter. When you want PowerChannel to read data from a remote source or write data to aremote source during a PowerChannel session, you need to install and configure PowerCenter.

Installing PowerChannel with Encryption AlgorithmsWhen you install PowerChannel, the installation program provides two sample repositories with two differentencryption algorithms. The installation program asks you to select an encryption algorithm for the defaultrepository. The PowerChannel Server uses the algorithm you select to encrypt and decrypt data.

You can install one of the following encryption algorithms:

¨ 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 algorithmand replace the default repository. You must also change the encryption algorithm in the PowerChannel andPcCmd properties files using the configuration utility.

¨ PowerChannel Servers and their clients must use the same encryption algorithm to communicate with eachother.

¨ PowerChannel Servers must use the same encryption algorithm to communicate with each other.

Installation and Configuration Overview 7

Working with the Sample PowerChannel RepositoryWhen you install PowerChannel for the first time, the installation program installs two sample PowerChannelrepositories that you can use with the PowerChannel Server: 3DES and RC2. Choose the repository that matchesthe encryption algorithm you selected when you installed the PowerChannel Server.

The 3DES repository is in the following directory:

<PowerChannel>/repository.3DES

The RC2 repository is in the following directory:

<PowerChannel>/repository.RC2

Note: Select the encryption algorithm you used in the previous version of PowerChannel. Select 3DES when youwant 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 toadminister the PowerChannel Server and transfer data. The sample repository uses the following user name andpassword:

¨ User name: admin

¨ Password: Administrator

The PowerChannel installation also includes a default certificate account with a twoway profile in the samplerepository. The default certificate account allows PowerChannel Servers that use the sample repository to transferdata with each other. After you install PowerChannel, you can start the PowerChannel Server, run PowerChannelcommands, and transfer data.

Warning: Using the admin user and default certificate account to run PowerChannel does not ensure a securedata transfer environment. If you do not require a secure data transfer environment, you can continue to use theadmin user and default certificate account to run PowerChannel. If you want to ensure a secure data transferenvironment, you must implement the following security measures into the PowerChannel sample repository:

1. Delete the default certificate account.

2. Create a certificate account.

3. Change the user password.

4. Reencrypt the repository.

Installing and Configuring PowerChannel for File TransferTo install and configure PowerChannel to transfer files, complete the following steps:

1. Install PowerChannel.

2. Optionally, configure the web client on BEA WebLogic Server.

3. Start the PowerChannel Server.

Installing and Configuring PowerChannel for Database Data TransferTo install and configure PowerChannel to transfer database data, complete the following steps:

1. Install the PowerChannel Server on the same network as the remote database from which you want to readdata 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 theIntegration Service to read compressed and encrypted data from a remote database and write compressedand encrypted data to a remote database. Install the PowerChannel Server on the same machine as theIntegration Service.

8 Chapter 2: Installation and Configuration

3. Configure PowerChannel components on PowerCenter.

4. Optionally, configure the web client on BEA WebLogic Server.

5. Start the PowerChannel Server.

Upgrading PowerChannel from a Previous VersionIf you are upgrading from a previous version of PowerChannel, complete the following steps:

1. Stop the PowerChannel Server.

2. Back up the PowerChannel repository. You can back up the PowerChannel repository by copying therepository folder to a different location.

3. Back up the PcCmd.properties and the PowerChannel.properties files. To back up PcCmd.properties andPowerChannel.properties, copy the files to a different location. Use the values of the properties in the backupfiles as a reference for configuring the new properties files.

4. Back up any scripts you used to run PowerChannel and PcCmd commands and the PcPassword command.

5. Install the PowerChannel Server and clients.

6. Optionally, configure PowerCenter to transfer database data using PowerChannel.

7. Configure the web client on BEA WebLogic Server.

8. Start the PowerChannel Server.

Installing PowerChannelTo run PowerChannel, you install the PowerChannel Server and PcCmd on Windows or UNIX. You also install theweb client on Windows.

Note: You must have write permissions for the directory where you want to install PowerChannel. Other, theinstallation program might not be able to successfully install PowerChannel.

Installing PowerChannel on WindowsYou can install PowerChannel on Windows connected to a network that can establish TCP/IP connections. Whenyou install PowerChannel on Windows, you need a Windows user account with administrator rights.

Note: The installation program lets you install the PowerChannel Server on Windows XP. However, Windows XPis 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 Windowsuser account that runs the PowerChannel Server service. Before you install PowerChannel, create a user accountwith the right to run services, known as the Service Start Account. To see if this account has the correct rights, runUser Manager for Domains and select the user. Select User Rights from the Policies menu. The user must havethe Logon as a service right. Create this account specifically to run the PowerChannel Server. Do not run thePowerChannel Server as the System account.

When you install the PowerChannel Server on Windows, the installation program creates a pcservice.log file in thePowerChannel root directory. The pcservice.log file shows the status of the PowerChannel Server serviceinstallation. If you uninstall the PowerChannel Server service, check the pcservice.log file to verify if the serviceuninstalled successfully.

Installing PowerChannel 9

Note: When you install PowerChannel, the installation program only copies the web client files into the directoryyou enter. You need to configure BEA WebLogic Server to run the web client.

To install PowerChannel on Windows:

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, andthe 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 ifyou want to configure PowerChannel.

9. Click Yes to open the PowerChannel configuration utility to configure the properties file. Or, click No if youwant to configure the PowerChannel properties later, and go to 11.

10. If you clicked Yes, configure the following properties and click Next:

Property Description

Repository Absolute or relative path to the PowerChannel repository.

SERVER_LOG Absolute or relative path to the PowerChannel Server log file.

SERVER_ERR_LOG Absolute or relative path to the PowerChannel Server log file.

EXPORT_DIR Path to the export directory that PowerChannel to export all certificate files you create forcertificate 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.

Installing PowerChannel on UNIXYou can install PowerChannel on UNIX connected to a network that can establish TCP/IP connections.

To install PowerChannel on UNIX:

1. Log in to the UNIX machine.

2. On the installation CD, locate the PowerChannel directory.

3. Locate the directory specific to the platform.

10 Chapter 2: Installation and Configuration

4. Enter ./install.bin to run the installation program.

5. From the installation menu, enter 1 to install PowerChannel.

To exit the installation process, enter quit.

6. At the prompt, enter a valid license key.

7. Enter the directory where you want to install PowerChannel and press ENTER. Or, press ENTER to acceptthe default directory.

8. Select RC2 or 3DES for the encryption algorithm.

9. Press ENTER to continue.

A pre-installation summary appears.

10. Click Enter.

After the installation completes, a message appears asking if you want to configure PowerChannel.

11. Enter 1 to open the PowerChannel configuration utility to configure the properties file. Or, enter 2 if you wantto configure the PowerChannel properties later.

If you entered 1, the PowerChannel configuration utility opens to guide you through configuring the propertiesfile. The configuration utility closes when the configuration is complete.

Configuring PowerChannel Components onPowerCenter

Complete the following steps to configure PowerCenter to read and write remote database data withPowerChannel:

1. Create ODBC connections. Create ODBC connections on the PowerCenter Client machine to importdefinitions for remote database sources and targets.

2. Create relational database connections. Create connection objects in the Workflow Manager so theIntegration Service can connect to remote databases.

Note: You do not need to install PowerChannel on the PowerCenter Client or Integration Service machines toenable PowerCenter to read file data or write file data through PowerChannel.

Starting the PowerChannel ServerYou can start the PowerChannel Server as a service on Windows. You can start the server as an application onWindows and UNIX. When you run the server on Windows, do not start the server as an application and as aservice simultaneously. When you start the PowerChannel Server, it locks the repository to prevent multipleinstances of the server accessing the same repository.

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.

Configuring PowerChannel Components on PowerCenter 11

Starting the PowerChannel Server as a ServiceOn Windows, you can start the PowerChannel Server as a service from the Control Panel. You can configure theservice to start when you start Windows. Use a Service Start Account for the PowerChannel Server service login.The user account you use for the service login must have access to the source or target directories you use duringPowerChannel file transfer.

When you start the PowerChannel Server as a service, the server starts with the following Java Virtual Machine(JVM) memory configuration:

JVM Memory Configuration Memory Size

Default memory (-Xms) 40 MB

Maximum memory(-Xmx) 300 MB

You cannot change the memory configurations for the JVM if you start the PowerChannel Server as a service onWindows.

On Windows, you can stop the PowerChannel service from the Control Panel.

Starting the PowerChannel Server as an ApplicationYou can start the PowerChannel Server as an application on Windows or UNIX. You must have a PowerChanneluser account with the admin profile to start the server.

When you start the PowerChannel Server, you can configure the JVM memory. The PowerChannel Server usesJVM memory when it runs data transfer sessions. If you do not configure the JVM memory, PowerChannel datatransfer 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 canfind 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 -Xmxvalue to 60 MB.

¨ If you run 20 to 60 PowerChannel sessions concurrently, set the -Xms value to 40 MB. Set the -Xmx value to100 MB.

¨ If you run more than 60 PowerChannel sessions concurrently, set the -Xms value to 100 MB. Set the -Xmxvalue to 200 MB.

¨ If the session still fails, increase the maximum memory for Java.

To start the PowerChannel Server as an application:

1. Go to the PowerChannel directory.

2. Enter the PowerChannel start command. Use the following command syntax to start the PowerChannelServer:

PowerChannel start [-r=<properties_file>] [-u=<user_account_name>][-p=<user_account_password>]

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

12 Chapter 2: Installation and Configuration

The following table describes the parameters for the PowerChannel start command:

CommandParameters

Required/Optional

Description

r Optional Enter the name of the PowerChannel.properties file.

u Optional Enter a user account name. Otherwise, the PowerChannel Server looks for the defaultuser account name in the PowerChannel.properties file.

p Optional Enter the password for the account. Otherwise, the PowerChannel Server looks for it inthe PowerChannel.properties file.

Stopping the PowerChannel ApplicationYou can stop the PowerChannel Server application using the web client or PcCmd.

Running PowerChannel CommandsAfter you start the PowerChannel Server, use the web client or PcCmd to run commands on the PowerChannelServer. Use the web client to run account and session management commands. Use PcCmd to run account andsession management commands and file transfer commands.

You can use a web client that is a different version that the PowerChannel Server.

Running Web Client CommandsAccess the web client using a web browser.

To run commands with the web client:

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:

Login Parameter Description

Login User account name.

Password Password for the user account.

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.

Running PowerChannel Commands 13

Running PcCmd CommandsAfter you start the PowerChannel Server, use PcCmd to run commands on the server.

Restoring the RepositoryYou can restore the PowerChannel repository. You might need to restore the repository when the repository iscorrupt.

To restore the repository:

1. Stop the PowerChannel Server.

2. Remove the old repository from the PowerChannel directory.

3. Copy the backup repository to the repository location.After you restore the repository, restart the PowerChannel Server.

Uninstalling PowerChannelYou can uninstall PowerChannel from Windows.Use the Add/Remove Programs utility to uninstall thePowerChannel Server and PcCmd from Windows. When you uninstall PowerChannel from Windows, setup doesnot 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 thelocal domain.

You must have administrator privileges on the machine where you uninstall PowerChannel. If you uninstallPowerChannel without administrator privileges, PowerChannel may not uninstall properly.

To uninstall PowerChannel from Windows:

1. Run Add/Remove Programs from the Windows Control Panel.

2. Select Informatica PowerChannel.

3. Click Change/Remove.

4. Select Uninstall Informatica PowerChannel.

5. Click Next.

6. Click Finish.

Troubleshooting a PowerChannel Installation

I received a message that the PowerChannel service did not install. However, the PowerChannel installationcompleted successfully.

14 Chapter 2: Installation and Configuration

The PowerChannel service is an optional component of PowerChannel. If you do not run PowerChannel as aservice, you can still run PowerChannel as an application. Therefore, when the PowerChannel service installationfails, PowerChannel can still install and run successfully.

If you want to run PowerChannel as a service, correct the error in the service installation error message. Then, runthe PowerChannel installation again to install the service.

If you want to run PowerChannel as an application, do not take any action.

The PowerChannel scripts cannot find the shell location.

The shell location in the PowerChannel scripts may differ from your shell location.

If you want to run PcCmd or PcPassword, you need to modify the PowerChannel scripts to specify the right shelllocation.

The PowerChannel script command failed with the message:-Xms40m: argument not valid

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 -Xmscommand, 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 thePowerChannel.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).

Troubleshooting a PowerChannel Installation 15

C H A P T E R 3

Administering PowerChannelAccounts

This chapter includes the following topics:

¨ Administering PowerChannel Accounts Overview, 16

¨ Working with PowerChannel Accounts, 18

Administering PowerChannel Accounts OverviewPowerChannel uses accounts to authenticate users and to ensure secure communication between PowerChannelServers. There are two types of accounts in PowerChannel:

¨ User accounts. All PowerChannel users must have a user account to use PowerChannel.

¨ Certificate accounts. A certificate account authenticates one PowerChannel Server to another PowerChannelServer. It allows a PowerChannel Server to communicate with another PowerChannel Server.

You can administer accounts with the web client or PcCmd.

User AccountsPowerChannel requires user accounts to authenticate users. The PowerChannel administrator must create useraccounts for all PowerChannel users that run PowerChannel commands. When you create a user account, thePowerChannel 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 validuser. During the authentication protocol, the client sends the account name along with an encrypted string, which itencrypts using the password you enter. It never sends the account password across the network. ThePowerChannel Server verifies if the user account name exists in the repository. If the account exists, it decryptsthe string using the account password in the repository. After the user authentication succeeds, the PowerChannelServer 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 readdata from a remote source or write data to a remote target. The PowerChannel listener on the PowerChannelServer uses the transport profile to authenticate requests that it receives directly from the Integration Service.

User Account ProfilesWhen you create a user account, you define a profile to set account privileges. The account profile determines thetype of PowerChannel tasks you can execute from the client.

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 profilecan run all commands including user management commands to create accounts, edit accounts, display a listof 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 fromone 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 runany PowerChannel commands. The PowerChannel administrator can edit the account to enable the accountprofile. You can change a disabled account profile to admin or user.

Certificate AccountsWhen a local PowerChannel Server communicates with a remote PowerChannel Server, the PowerChannelServers 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 certificateaccount in the local PowerChannel repository.

The PowerChannel installation program includes a default certificate account in a sample repository. Use thiscertificate account to transfer data between PowerChannel Servers that contain the sample repository. Create acertificate account for secure data transfer.

When you create a certificate account for a remote PowerChannel Server, the local PowerChannel Server storesthe certificate account attributes in an encrypted file in the repository. It also creates a certificate file for the remotePowerChannel Server in the PowerChannel/export directory. The local PowerChannel administrator must providethe certificate file to the remote PowerChannel administrator.

To use a certificate account to communicate with the local PowerChannel Server, the remote PowerChanneladministrator must import the certificate file into the remote PowerChannel repository. When a remotePowerChannel user runs a command to transfer data from the remote PowerChannel Server to the localPowerChannel Server, the user must use the certificate account for the local PowerChannel Server tocommunicate with it.

Certificate Account ProfilesWhen you create a certificate account, you can set the account privileges by defining a profile for the account. Thecertificate account profile determines whether the certificate account allows one-way or two-way communicationbetween PowerChannel Servers.

You can set the following profiles for a certificate account:

¨ Oneway. Use for a certificate account that allows one-way communication from the local PowerChannel Serverto 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 remotePowerChannel Server and the local PowerChannel Server.

Administering PowerChannel Accounts Overview 17

Working with PowerChannel AccountsUse the web client and PcCmd to run the following account administration tasks:

¨ Create user and certificate accounts.

¨ Display user and certificate accounts.

¨ Edit user and certificate accounts.

¨ Remove user and certificate accounts.

Creating a User Account with the Web ClientTo create a user account, you must have a user account with the admin profile.

To create a user account with the web client:

1. Click Administration > Create User.

2. Enter the following options to create the user account:

CommandOption

Description

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.

ConfirmPassword

Re-enter the password.

Input Folder When you transfer files, enter the path of the default input folder for the new user account. If thepath 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 thepath 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

3. Click Create to create the user account.

Tip: Click Reset to clear the values you entered. Or, click Cancel to cancel the account creation.

Creating a Certificate Account with the Web ClientTo create a certificate account, you must have a user account with the admin profile.

18 Chapter 3: Administering PowerChannel Accounts

To create a certificate account with the web client:

1. Click Administration > Create Certificate.

2. Enter the following account properties to create the certificate account:

CommandOption

Description

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.

ConfirmPassword

Retype the password for confirmation.

DefaultPowerChannelHostname/IPAddress

Default IP address of the PowerChannel Server where you want to register the new certificateaccount. Otherwise, the PowerChannel Server creates the certificate account without a default IPaddress.

DefaultPowerChannelPort

Default port number of the PowerChannel Server where you want to register the new certificateaccount. Use a port number from 1 to 65535. Otherwise, the PowerChannel Server creates thecertificate 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. Ifthe 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. Ifthe 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

3. Click Create to create the certificate account.

Tip: Click Reset to clear the values you entered. Or, click Cancel to cancel the account creation.

Displaying Accounts with the Web ClientYou can display a list of accounts and account attributes in the PowerChannel repository. When you display a useror certificate account, you view the following account attributes:

¨ Account name. Name of the account.

¨ Account type. Account types are user and certificate.

¨ Account profile. Account profiles for user accounts are user, admin, and disabled. Account profiles forcertificate 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.

Working with PowerChannel Accounts 19

When you display a certificate account, you also view the following account attributes:

¨ Default IP address. Default IP address of the local PowerChannel Server.

¨ 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 useraccount with the admin profile, you can display all user or certificate accounts.

Displaying Your Account as a PowerChannel UserWhen you have a user account with the user profile, you can display your own account attributes.

To display your account as a user with the web client:

1. Click OwnAccount.

2. Click Display Account.

The web client displays the account attributes.

Displaying Accounts as a PowerChannel AdministratorWhen you have a PowerChannel user account with the admin profile, you can display all user and certificateaccounts in the repository.

To display a list of accounts as an admin with the web client:

1. Click Administration > Account Management > Account Manager.

2. Enter the following Display Accounts options:

CommandOption

Description

Account NameFilter

Enter a filter condition to filter account names. Use the following rules and guidelines:- 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 withthe letter “a,” use “a%” as the account name filter.

Account Type Select User Account or Certificate Account.

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.

20 Chapter 3: Administering PowerChannel Accounts

Editing a User Account with the Web ClientUse the web client to edit user account attributes in the repository. You can change the following user accountattributes:

¨ Password. Password for the user 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 youhave a user account with the admin profile, you can change account attributes for any user account. When editingyour own account, you cannot change the account profile.

Editing a User Account as a PowerChannel UserWhen you have a user account with the user profile, you can edit the user account attributes.

1. Click OwnAccount > Edit Account.

2. Edit the following account attributes:

Command Option Description

Password Enter an account password of at least three characters.

Confirm Password Retype the password for confirmation.

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 useraccounts, you can remove the default attributes for the input folder and output folder.

3. Click Save to save changes to the account.

Editing a User Account as a PowerChannel AdministratorWhen you have a user account with the admin profile, you can edit any user account in the repository. You canremove the default attributes for the input folder and output folder.

To edit a user account as an admin with the web client:

1. Click Administration > Account Management > Account Manager.

Use the Account Name Filter and the Records per Page options to limit the number of user accounts todisplay.

2. On Display Accounts, click Go.

The web client displays the accounts based on the filter you enter.

Tip: Click Refresh to view an updated account list.

3. Select the account you want to update, and click Edit.

Working with PowerChannel Accounts 21

4. Enter the following options to edit the account:

Command Option Description

Password Enter an account password of at least three characters.

Confirm Password Retype the password for confirmation.

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.

Editing a Certificate Account with the Web ClientUse the web client to edit certificate account attributes in the repository. You can change the following certificateaccount attributes:

¨ Default IP address. Default IP address of the local PowerChannel Server.

¨ 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 followingaccount attributes: IP address, port, input folder, and output folder. You must have a user account with the adminprofile to edit a certificate account.

To edit a certificate account with the web client:

1. Click Administration > Account Management > Account Manager.

Use the Account Name Filter and the Records per Page options to limit the number of certificate accounts todisplay.

2. On Display Accounts, click Go.

The web client displays the accounts based on the filter you enter.

Tip: Click Refresh to view an updated account list.

3. Select the account you want to update, and click Edit.

22 Chapter 3: Administering PowerChannel Accounts

4. Enter the following options to edit the account:

Command Option Description

Default PowerChannelHostname/IP Address

Changes the default IP address for the local PowerChannel Server.

Default PowerChannel Port Changes the default port for the local PowerChannel Server. Use a port number from 1 to65535.

Input Folder Changes the default input folder path for the certificate account. Do not use thisparameter when you transfer data between PowerCenter and remote databases.

Output Folder Changes the default output folder path for the certificate account. Do not use thisparameter 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.

Removing an Account with the Web ClientYou can remove an account from repository. You must have a user account with the admin profile to remove anaccount. You cannot remove your own account.

When you remove a certificate account, the PowerChannel Server also removes the certificate file for the accountfrom the PowerChannel/export directory. If you delete the certificate file prior to account removal, the server onlyremoves the certificate account. It does not provide a message for the missing certificate file.

To remove an account with the web client:

1. Click Administration > Account Management > Account Manager.

2. On Display Accounts, click Go.

Use the Account Name Filter, Account Type, and the Records per Page options to limit the number ofaccounts to display. The web client displays accounts based on the filter you enter.

3. Select the account you want to remove, and click Remove.

The web client displays the account name to remove for confirmation.

4. Click Remove.

Working with PowerChannel Accounts 23

C H A P T E R 4

Administering the PowerChannelServer

This chapter includes the following topics:

¨ Administering the PowerChannel Server Overview, 24

¨ Working with Channels, 25

¨ Working with Data Transformers, 26

¨ Working with PowerChannel Listeners, 28

¨ Configuring the PowerChannel Server, 29

¨ Working with PowerChannel Server Variables, 40

¨ Working with PowerChannel Server Commands, 44

Administering the PowerChannel Server OverviewPowerChannel can read data from remote sources and write data to remote targets. The PowerChannel Servertransfers files and database data from one PowerChannel Server to another. Also, PowerCenter can use a remotePowerChannel Server to read data from remote databases and write data to remote databases.

The PowerChannel Server listens to incoming user requests from PcCmd, the web client, and the IntegrationService on a listener port. The PowerChannel Server also listens to requests from other PowerChannel Servers ona listener port. When it receives a user request, the PowerChannel Server runs a session. A session includes aset of tasks that the server completes in response to the user request. The PowerChannel Server communicateswith 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. ThePowerChannel Server can also compress and encrypt data. When a PowerChannel Server receives compressedand 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 ConnectivityThe PowerChannel Server uses the TCP/IP protocol to communicate with the Integration Service and otherPowerChannel Servers. It listens to user requests from PcCmd, the web client, the Integration Service, and otherPowerChannel Servers on a listener port. You define the listener port for the server using the PowerChannelconfiguration utility.

24

PowerChannel ProtocolPowerChannel uses a secure protocol to communicate with PcCmd, the web client, and other PowerChannelServers. When the Integration Service uses the local and remote PowerChannel Servers to read data from remotesources and write data to remote targets, the PowerChannel Servers use the secure protocol to ensure that alldata 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 PowerChannelprotocol to initiate a handshake with the PowerChannel Server. During the handshake, PcCmd sends the useraccount 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. Ifthe user exists in the repository, the PowerChannel Server uses the user password in the repository to decrypt thestring of text. When the decryption succeeds, the PowerChannel Server acknowledges the user as a valid userand prompts PcCmd for the user command. PcCmd then sends the user command to the PowerChannel Serverencrypted with the user password. The PowerChannel Server decrypts the command using the user password inthe 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 localPowerChannel 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 textencrypted with the certificate account key for the remote PowerChannel Server. The remote PowerChannel Serverreceives this information and tries to locate the certificate account in its repository. If the account exists, it uses thecertificate account key in the repository to decrypt the string of text. When the decryption succeeds, the remotePowerChannel Server acknowledges the local PowerChannel Server as a valid server and prompts it to starttransferring database data or files. The local PowerChannel Server then transfers the database data or files to theremote 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 filetargets, the local PowerChannel Server uses the secure protocol to initiate a handshake with the remotePowerChannel Server. During this handshake, the local PowerChannel Server sends the local host informationand a string of text encrypted with the certificate account key for the remote PowerChannel Server. The remotePowerChannel Server receives this information and tries to locate the certificate account in its repository. If theaccount exists, it uses the certificate account key in the repository to decrypt the string of text. When thedecryption succeeds, the remote PowerChannel Server acknowledges the local PowerChannel Server as a validserver. The local PowerChannel Server connects to the remote PowerChannel Server that remains open until youclose it. While the connection is open, the local PowerChannel Server listens for user requests to transfer datausing the FTP connection.

Working with ChannelsWhen PowerCenter uses the local and remote PowerChannel Servers to read data from remote sources and writedata to remote targets, the PowerChannel Servers transfer data between each other using channels. A channelcontains a set of objects that read, transform, and write the data during data transfer.

When you transfer data between PowerChannel Servers, the local PowerChannel Server uses a channel to readthe data from the source location, transform it according to the user command, and then write the data to thenetwork.

Similarly, the remote PowerChannel Server uses a channel to read the data from the network, transform itaccording 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 usePcCmd to transfer files, you do not have to enter channel information in the command. PcCmd generates the XML

Working with Channels 25

command with channel information based on the compression, encryption, and staging parameters you enter inthe command.

The following table describes the types of channels the PowerChannel Server uses during data transfer:

Channel Type Description

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 thePowerChannel Server receives files from a remote PowerChannel Server, it uses this channel toread 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 thePowerChannel Server sends files to a remote PowerChannel Server, it uses this channel to write thefiles 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. Whenyou transfer files to a remote PowerChannel Server, and you stage the files at the sending andreceiving PowerChannel Servers, the sending PowerChannel Server uses this channel to transferthe 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 receivingPowerChannel Server only, the receiving PowerChannel Server uses this channel to read the files inbytes and decompress the staged files.

PIPE When you use an FTP connection to transfer files, PowerChannel uses the PIPE channel to readdata from the network and write data to the network. The PowerChannel Server uses this channel towrite data to the network in blocks. The PowerChannel Server also uses a PIPE channel to read datafrom 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 todatabases. The PowerChannel Server uses the TRANSPORT channel to transfer database data toanother PowerChannel Server. The PowerChannel Server also uses the TRANSPORT channel totransfer data between the Integration Service and remote databases. You do not specify theTRANSPORT channel when you use an XML command to transfer data.

Working with Data TransformersWhen PowerCenter sends the local PowerChannel Server a request to transfer compressed or encrypted data, thelocal and remote PowerChannel Servers use a set of data transformers to ensure rapid and secure data transfer.The PowerChannel Servers use data transformers to compress, encrypt, decompress, decrypt, and stage data.

When the Integration Service sends a request to read compressed and encrypted data from a remote source orwrite compressed and encrypted data to a remote target, the sending PowerChannel Server creates a channel tosend the data. This channel uses a set of transformers to compress and encrypt the data according to the usercommand. When the receiving PowerChannel Server receives the data from the network, it creates a channel toreceive 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 PowerChannelServer uses data transformers in a channel based on the compression, encryption, and staging parameters youenter in the command. For example, you want to send compressed and encrypted files from a remote

26 Chapter 4: Administering the PowerChannel Server

PowerChannel Server to the local PowerChannel Server. In the file transfer command, you can set thecompression level to 4 and the encryption level to 3.

When you transfer data using PcCmd, you do not have to enter data transformers in the command. However, youcan set compression and encryption levels in the PcCmd command. Also, you do not need to configure datatransformers when the PowerChannel Server transfers database data.

Note: You can only enter staging parameters in the command when you transfer files between PowerChannelServers. You cannot use staging when you transfer files between the Integration Service and an FTP server orbetween 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:

Data Transformers Channel Types Description

COMPRESSOR WRITESTREAM Use in a WRITESTREAM channel to compress data at the sendingPowerChannel Server. When you use COMPRESSOR in an XMLcommand file, you can enter the compression level for datacompression.When you run a file transfer command or a command to connectPowerChannel Servers to transfer files between PowerCenter and anFTP server or between FTP clients and servers, use the -cl parameterfor compression level in a PcCmd command. Compression levelsrange from 1 to 9, where 9 is the highest compression level. Default is5.

STAGECOMPRESSOR COMPRSTAGEWRITESTREAM

Use in a WRITESTREAM channel when you compress files at thesending PowerChannel and stage files at the receiving PowerChannelonly.Use STAGECOMPRESSOR in a COMPRSTAGE channel when youcompress and stage files at the sending PowerChannel.When you use the STAGECOMPRESSOR transformer, you can enterthe compression level for data compression. Compression levelsrange from 1 to 9, where 9 is the highest compression level.

ENCRYPTOR WRITESTREAM Use in a WRITESTREAM channel when you want to encrypt data atthe sending PowerChannel. When you use ENCRYPTOR in an XMLcommand file, you can enter the encryption level for data encryption.When you run a file transfer command or a command to connectPowerChannel Servers to transfer files between PowerCenter and anFTP server or between FTP clients and servers, use the -elparameter for encryption level in a PcCmd command. Encryptionlevels 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 atthe receiving PowerChannel.When you use DECRYPTOR in an XML command file, you do notneed to enter the decryption level for data decryption. ThePowerChannel Server determines the decryption level based on theencryption level you used for data encryption in the command.

DECOMPRESSOR READSTREAM Use in a READSTREAM channel when you want to decompress dataat the receiving PowerChannel.When you use DECOMPRESSOR in an XML command file, you donot need to enter the decompression level for data decompression.The PowerChannel Server determines the decompression level basedon the compression level you use for data compression in thecommand.

Working with Data Transformers 27

Working with PowerChannel ListenersYou can enhance security on the PowerChannel Server by configuring the ACTIVE_LISTENERS property to allowthe PowerChannel Server to restrict user requests from clients on the network based on the user’s IP address andaccount profile. For example, you can restrict clients from a certain network to run data transfer commands andenable other clients to run administrative and data transfer commands.

You also use ACTIVE_LISTENERS when the Integration Service reads data from remote sources or writes data toremote targets through PowerChannel. The PowerChannel Server uses an active listener to listen for requestsfrom the Integration Service. For example, when you want the Integration Service to read data directly from theremote 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 transferremote data through a PowerChannel Server:

¨ Provide a unique port number for each active listener you want to configure bound on the same IPaddress. 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 IPaddress you specified. If you do not configure an IP address, the PowerChannel Server uses all IP addressesof the machine on which it resides.

You can configure the ACTIVE_LISTENERS property using the PowerChannel configuration utility.

Configuring Client Access PrivilegesWhen you configure active listeners, you can determine the level of access clients have to the PowerChannelServer. You can enter a filter to limit the IP addresses from which clients can access the PowerChannel Server.You can also enter the account privileges for the clients.

If you enter a filter, only clients from IP addresses that meet the filter condition may run client commands on thePowerChannel Server or transfer data using the PowerChannel Server. This lets you prevent unknown clients fromaccessing the PowerChannel Server. When a client attempts to run a client command on the PowerChannelServer or transfer data using the PowerChannel Server, the PowerChannel Server verifies that the client meetsthe filter before it continues the session. If the client does not meet the filter, the PowerChannel Serverdisconnects the client.

You can configure the active listeners to restrict the types of commands clients can run on the PowerChannelServer 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 useraccounts on the PowerChannel Server and run commands to transfer data to and from the PowerChannelServer. Clients must use user accounts with the admin profile to run client commands on the PowerChannelServer. 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 thetransport profile.

¨ User. Use the user profile when you only want the client to be able to change its own account attributes andtransfer data to and from the PowerChannel Server. The PowerChannel Server only accepts client commands

28 Chapter 4: Administering the PowerChannel Server

that a user account with the user profile can run. It does not accept commands that require the admin profile.For example, you can transfer data. However, you cannot stop the PowerChannel Server.

¨ Transport. Use the transport profile when you want the PowerChannel Server to accept requests from theIntegration Service to read data from remote sources or write data to remote targets. The PowerChannelServer only accepts requests from the Integration Service to read data from remote sources and write data toremote targets.

Configuring the PowerChannel ServerThe PowerChannel Server uses a properties file, PowerChannel.properties, that contains a set of properties thatthe server uses to run PowerChannel. You can set the default configurations for the server properties in thePowerChannel.properties file. You can also create a properties file to store the default server properties when yourun PowerChannel as an application.

The PowerChannel Server can use the following properties files:

¨ PowerChannel.properties. The default properties file installed with the PowerChannel Server. You can set thedefault values for all the server properties in the PowerChannel.properties file. The server uses this file to runPowerChannel. The server also uses this file when you omit an optional parameter in a PowerChannelcommand, 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 attributeswhen 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. Whenyou run a PowerChannel command, use the properties file option to enter the username.properties file in thecommand. During command execution, the server uses the properties in the username.properties file to run thecommand.

PowerChannel provides a configuration utility to configure the properties file. You can launch the utility when youinstall PowerChannel. If you want to change the properties after you install PowerChannel, you can run aPowerChannel command to launch the utility.

PowerChannel Server PropertiesConfigure the PowerChannel Server properties with the PowerChannel configuration utility. You can set thefollowing server properties in the properties file:

¨ “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

Configuring the PowerChannel Server 29

¨ “PASSWORD” on page 34

¨ “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

REPOSITORYYou set the location of the PowerChannel repository using the PowerChannel configuration utility. Use only ASCIIcharacters to specify the repository directory. When you install the PowerChannel Server, the installation programcreates a file-based repository for the local PowerChannel in the repository directory. You can move the repositoryfolder to a different location. When you move the repository, you need to enter the new repository location.

The following parameter specifies the location of the repository:

REPOSITORY = <repository_path>

Note: This property is required.

ACTIVE_LISTENERSYou can configure additional listeners to enhance security for the PowerChannel Server when you transferdatabase data. When you configure additional listeners, you can restrict client access to the PowerChannelServer. 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 listenerusing the PowerChannel configuration utility. This lets you retain the configuration information for the listener forlater 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 theformat {x|y} represent the options you can use for the command parameter. Parameters followed by an asterisk (*)can contain multiple values.

30 Chapter 4: Administering the PowerChannel Server

The following table describes the attributes for the ACTIVE_LISTENERS property:

Attribute Required/Optional

Description

PORT Required Port number of the additional listener. Enter a value from 1 to 65535. The port should notbe used by other applications. For example, do not share the port with an FTP applicationor 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 Serverresides on a machine with more than one network adapter. When you start thePowerChannel Server, the server listens at the port number on the network adapter thatis identified by the IP address you specified. Otherwise, the PowerChannel Server listensfor the port on all available adapters.

FILTER Optional Enter a filter to limit the IP addresses from which clients may run commands on thePowerChannel Server or transfer data using the PowerChannel Server. This lets youprevent unknown clients from accessing the PowerChannel Server. If a client that is not inthe subnet tries to access the PowerChannel Server, the PowerChannel Serverdisconnects the client.To enter a filter, enter the IP address from which users can run client commands and avalue 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 requestsfrom addresses with the IP 128.2.0.x. For example, the PowerChannel Server will notaccept 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 usesthe encrypted protocol by default.Enter encrypted when you want the PowerChannel Server to use the standardPowerChannel encryption for secure data transfer between PowerChannel Servers. Entergeneric when you want the Integration Service to use the PowerChannel Server totransfer data without security.

USER_PROFILES

Optional Enter user, admin, and/or transport for the user profile. Enter user for the client to haveuser privileges. Enter admin for the client to have admin privileges. Enter transport whenyou want the PowerChannel Server listen for data transfer requests from the IntegrationService. You can enter more than one user profile.If you do not enter a user profile, the PowerChannel Server uses the admin and userprofiles 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 thePowerChannel Server:

ACTIVE_LISTENERS = AdminListener, TransportListenerAdminListener.PORT = 7000AdminListener.IP_ADDRESS = sunqa1AdminListener.USER_PROFILE = admin, userTransportListener.PORT = 7001TransportListener.IP_ADDRESS = sunqa2TransportListener.PROTOCOL = genericTransportListener.USER_PROFILE = transportTransportListener.FILTER = 10.1.0.0 / 255.255.0.0

CRYPTOGRAPHYPowerChannel uses an encryption algorithm to encrypt and decrypt data. During installation you set the encryptionalgorithm that you want the PowerChannel Server to use. When you set the encryption algorithm, the installationprogram configures the CRYPTOGRAPHY property.

Configuring the PowerChannel Server 31

After you install the Integration Service, you cannot change the value for the repository. To change the encryptionalgorithm, you must copy the sample repository provided for the encryption algorithm and replace the defaultrepository. You must also change the encryption algorithm in the properties file using the configuration utility.

When you select an encryption algorithm for CRYPTOGRAPHY, any PowerChannel Server or client youcommunicate with must use the same encryption algorithm. When you want to use FIPS-certified encryption, setthe value for CRYPTOGRAPHY to the 3DES encryption algorithm.

The following parameter specifies the encryption algorithm:

CRYPTOGRAPHY = {JSAFE/RC2|JSAFE/3DES}

Note: This property is required.

LICENSEWhen you install the PowerChannel Server, you must enter a valid license key. The installation program registersthe license key in the PowerChannel.properties file.

The following parameter shows the license key entered during PowerChannel Server installation:

LICENSE = <license_key>

MAX_BLOCK_SIZEPowerChannel uses data block buffers to store blocks of data during data transformation. You can set themaximum buffer size for data blocks the PowerChannel Server uses in the properties file using the PowerChannelconfiguration utility. The default block size for MAX_BLOCK_SIZE is 100 KB. You can set a default value from1000 to 100000000.

The following parameter sets the maximum buffer size for data blocks:

MAX_BLOCK_SIZE = <buffer_size_in_bytes>

Do not use special characters, such as a comma.

TOTAL_CHANNEL_MEMORYYou can set the total allocated memory for each channel that the PowerChannel Server creates from theproperties file. By default, the server allocates 1.6 MB for each channel. You can set a default value from 1000000to 100000000.

The following parameter specifies the total allocated memory for each channel:

TOTAL_CHANNEL_MEMORY = <number_of_bytes>

Do not use special characters, such as a comma.

SERVER_LOGPowerChannel 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 logmessages to a different directory.

The following parameter specifies the server log file location:

SERVER_LOG = <file_path>

Note: This property is required.

32 Chapter 4: Administering the PowerChannel Server

SERVER_ERR_LOGYou can configure the PowerChannel Server to write server error messages to a specified error log file in additionto the PowerChannel.log file. The PowerChannel Server writes server error messages to the PowerChannel.err fileby default. You can change the name and path of the server error log file by configuring SERVER_ERR_LOGusing the PowerChannel configuration utility.

The following parameter specifies the server error log filename and path:

SERVER_ERR_LOG = <file_path>

Note: This property is required.

LOG_FOLDERThe 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_sessionID. For example, the name of the session log file for a parent session with the name alice and the ID 326 isalice_326.

When you view the session log for a child session, the name for the session log is session name_parent sessionID_child session ID. For example, the name of the session log for a child session with the ID 752 and with thesession name alice_326 is alice_326_752.

The following parameter specifies the log folder location:

LOG_FOLDER = <directory_path>

Note: This property is required.

LOG_LEVELUse LOG_LEVEL to specify the level of detail in the PowerChannel log files.

The following parameter specifies the log level:

LOG_LEVEL = {0|1|2|3}

Note: This property is required.

The following table describes the LOG_LEVEL values:

LOG_LEVELValues

Description

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 thelog files.

3 PowerChannel Server writes all messages to the log files, including debug messages.

USERNAMEYou can enter a default user account name with the admin profile in the properties file using the PowerChannelconfiguration utility. When you set a default user name in the properties file, you can omit the user account nameparameter in the PowerChannel Server commands.

Configuring the PowerChannel Server 33

The following parameter sets a default user account name:

USERNAME = <user_name>

Note: This property is required when you run the PowerChannel Server as a service on Windows.

PASSWORDYou can enter a default encrypted password for the default user account in the properties file using thePowerChannel configuration utility. When you set the default encrypted password in the properties file, you canomit the password parameter in the PowerChannel Server commands.

To encrypt the default password, use the PcPassword encryption utility from the PowerChannel command line. Touse the PcPassword utility for encrypting a user account password, enter PcPassword and the password you wantto encrypt. For example, if you want to encrypt the password “Administrator,” go to the PowerChannel directoryfrom 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 avalue for PASSWORD, you can omit the password parameter in PcCmd commands.

The following parameter sets a default password in the PowerChannel.properties file:

PASSWORD = <password>

Note: This property is required when you run the PowerChannel Server as a service.

EXPORT_DIRPowerChannel uses an export directory to export all certificate files you create for certificate accounts. When youcreate a certificate account, the PowerChannel Server creates a certificate file for the certificate account. Duringinstallation, the installation program creates an export directory in the PowerChannel root directory. You canconfigure the server to store certificate files in a different export directory.

The following parameter specifies the location of the export directory:

EXPORT_DIR = <directory_path>

If the export path contains spaces, you must enclose the path in quotes.

Note: This property is required.

MAX_SESSIONS_MONITOREDThe PowerChannel Server stores session information in memory for all data transfer sessions you run. If a sessionfails, 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 configuringMAX_SESSIONS_MONITORED using the PowerChannel configuration utility. The value you enter determines thenumber of file transfer sessions to retain in memory for session monitoring. The default value forMAX_SESSIONS_MONITORED is 100. You can set a default value from 10 to 1000.

The following parameter sets the MAX_SESSIONS_MONITORED value:

MAX_SESSIONS_MONITORED = <value>

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, thePowerChannel Server removes the session information for the excess sessions. When the server removes theexcess session information, it removes the oldest session information first.

34 Chapter 4: Administering the PowerChannel Server

The PowerChannel Server does not retain session information in memory when you stop the server. If you stopand restart the server, you cannot monitor sessions that you ran before you stopped the server. You can onlymonitor failed and stopped sessions stored in the repository.

Note: This property is required.

MAX_CONCURRENT_RUNNING_SESSIONSYou can limit the number of sessions that run concurrently on the PowerChannel Server. UseMAX_CONCURRENT_RUNNING_SESSIONS in the properties file to specify the maximum number of sessions torun concurrently. The number of sessions you run concurrently determines the amount of system resources theserver uses. The default value for MAX_CONCURRENT_RUNNING_SESSIONS is 20. You can set a default valuefrom 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 asa comma.

Note: This property is required.

REMOVE_LOG_FILES_ON_PURGEYou can configure the PowerChannel Server to remove the log files for sessions that are no longer in the systemmemory. To remove log files, enter “yes” for REMOVE_LOG_FILES_ON_PURGE using the PowerChannelconfiguration utility. Otherwise, the server does not remove log files. The server removes log files when it removessession 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}

Note: This property is required.

NUM_AUTO_RECOVERY_ATTEMPTSThe PowerChannel Server attempts to recover data transfer sessions if a session fails due to network error. Forexample, PowerChannel tries to send a file to a remote PowerChannel Server, but the session fails during filetransfer.

You can set the maximum number of attempts the PowerChannel Server makes to recover the session using thePowerChannel configuration utility. When the server successfully recovers the connection between PowerChannelServers, it begins to count the maximum number of attempts from 0. When it reaches the maximum number ofrecovery attempts, the session fails due to network failure.

Use NUM_AUTO_RECOVERY_ATTEMPTS to set the maximum number of recovery attempts for the server. Thedefault value for the number or recovery attempts is 10. You can set a default value from 0 to 1000.

The following parameter specifies the maximum number of recovery attempts:

NUM_AUTO_RECOVERY_ATTEMPTS = <value>

When you enter a value for NUM_AUTO_RECOVERY_ATTEMPTS, do not use special characters, such as acomma.

Note: This property is required.

INPUT_FOLDERPowerChannel uses an input folder as the default folder for input data files during file transfer. For example, youwant to send a file from the local PowerChannel Server to a remote PowerChannel Server. In the command

Configuring the PowerChannel Server 35

parameter, you do not enter the absolute path to the file you want to send. When the PowerChannel Serverreceives the command, it looks for the file you want to send in the default input folder specified in the propertiesfile. During installation, install creates the default input folder under the PowerChannel root directory.

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

Note: This property is required.

OUTPUT_FOLDERPowerChannel 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 theabsolute path to the destination file. When the PowerChannel Server receives the file from the remote server, itwrites the file to the default output folder specified in the properties file. During installation, install creates thedefault 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>

You can also use a server variable for OUTPUT_FOLDER.

Note: This property is required.

TRUST_REMOTE_EXECUTIONYou can configure the PowerChannel Server to restrict operating system commands from a remote PowerChannelServer. Use this parameter when you want to allow only file transfer commands from a remote server. Forexample, you may want to restrict remote servers from deleting files on the local PowerChannel system. UseTRUST_REMOTE_EXECUTION in the properties file to specify the restriction.

The PowerChannel Server only allows operating system commands from remote PowerChannel Servers when youenter “yes” for TRUST_REMOTE_EXECUTION. Otherwise, the server restricts operating system commands fromremote servers.

The following parameter restricts operating system commands from remote PowerChannel Servers:

TRUST_REMOTE_EXECUTION = {yes|no}

Note: This property is required.

RUN_EXTERNAL_EXECUTEYou can configure the PowerChannel Server to control external execute commands run by any account on thelocal PowerChannel Server. Use RUN_EXTERNAL_EXECUTE to restrict users from running operating system

36 Chapter 4: Administering the PowerChannel Server

commands on the local server. For example, you may want to restrict users with user profile from deleting files onthe local PowerChannel system. Alternatively, you may want users with the admin profile to be able to runoperating system commands. The default value for RUN_EXTERNAL_EXECUTE is “all.”

The following parameter controls external execute commands by users on the local PowerChannel Server:

RUN_EXTERNAL_EXECUTE = {all|admin|none}

The following table describes the RUN_EXTERNAL_EXECUTE values:

ValidValues

Description

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.

Note: This property is required.

PLUGIN.PMREMOTEDATA.LIBTo use PowerCenter with PowerChannel, the PowerChannel plug-in requires a plug-in library. PowerChannelspecifies the PowerChannel plug-in library for PLUGIN.PMREMOTEDATA.LIB. Do not modify this property. Makesure that the entry in the PowerChannel.properties file is correct.

The following table describes values for PLUGIN.PMREMOTEDATA.LIB based on operating system:

Operating System Value

Windows pmtlserver.dll

Solaris libpmtlserver.so

AIX libpmtlserver.a

HP-UX limpmtlserver.sl

Configuring the PowerChannel Properties FileYou configure the PowerChannel.properties file using the PowerChannel configuration utility. The configurationutility launches when you install PowerChannel. Or, run the PowerChannelconfig command if you want to makechanges after you install.

Note: Enter Ctrl-C to exit the configuration utility at any time.

To configure the PowerChannel.properties file:

1. From the command line, go to the PowerChannel directory.

2. Enter the PowerChannelconfig command.

When you enter the command, you can select to configure all of the properties or the installation or plug-inproperties only.

3. Enter the absolute or relative path to the PowerChannel repository.

Configuring the PowerChannel Server 37

When you move the repository folder to a different location, enter the new path to the repository in thePowerChannel.properties file.

4. If you want to add an active listener or edit a listener, select from one of the following options:

Value Description

1 Add a listener.

2 Display listener details.

3 Edit a listener.

4 Remove a listener.

5 Finish editing listener.

When you configure a listener, enter the following attributes:

¨ Listener name (required).

¨ Port number (optional). Default port is 7000.

¨ IP Address (optional).

¨ IP Filter (optional).

¨ Protocol (optional). Default protocol is encrypted.

¨ User profile (optional). Default profile is admin.

¨ Enabled (required). Default is yes.

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

Or, press ENTER to confirm current value.

6. Enter a valid PowerChannel license key. Or, press ENTER to confirm the current value.

7. Enter the maximum block size in bytes. Or, press ENTER to confirm the current value.

Block size must be between 1000 and 100000000. Do not use special characters, such as a comma.

8. Enter the total channel memory size in bytes. Or, press ENTER to confirm the current value.

Memory size must be between 1000000 and 100000000. Do not use special characters, such as a comma.

9. Enter the absolute or relative path to the folder that contains the PowerChannel Server log files. Or, pressENTER to confirm current value.

Note: Do not use a backslash (\) to define a directory hierarchy. Java interprets a backslash as a specialcharacter in Java properties files. It uses (\) to concatenate lines of text. Therefore, use a forward slash (/) ora double backslash (\\) in its place.

This applies to all steps in which you enter a path.

38 Chapter 4: Administering the PowerChannel Server

10. Enter the absolute or relative path to the folder that contains the PowerChannel Server error log files. Or,press ENTER to confirm current value.

11. Enter the absolute or relative path to the folder that contains the PowerChannel session log files. Or, pressENTER to confirm current value.

12. Select the log level from the options shown in the following table:

Value Description

0 No messages.

1 Only error messages.

2 Error and some informational messages.

3 All messages, including debug messages.

Or, press ENTER to confirm the current value.

13. Enter a user name with the admin profile to run PowerChannel commands. Or, press ENTER to confirm thecurrent value.

14. Enter a password to run PowerChannel commands. Or, press ENTER to confirm the current value.

15. Enter the path to the folder where you want to store certificate files. Or, press ENTER to confirm current value.

16. Enter how many sessions you want the PowerChannel Server to monitor. Or, press ENTER to confirm thecurrent value.

Set a value from 10 to 1000. Do not use special characters, such as a comma.

17. Enter how many concurrent sessions can run on the PowerChannel Server. Or, press ENTER to confirm thecurrent value.

Set a value from 1 to 10000. Do not use special characters, such as a comma.

18. Specify if you want PowerChannel to remove session log files for sessions no longer in the system. Or, pressENTER to confirm the current value.

19. Enter how many automatic recovery attempts you want the PowerChannel Server to make per session. Or,press ENTER to confirm the current value.

Set a value from 0 to 1000. Do not use special characters, such as a comma.

20. Enter the absolute or relative path to the folder where the PowerChannel Server looks for outgoing files duringtransfer. Or, press ENTER to confirm the current value.

You can also use a server variable for the INPUT_FOLDER value.

21. Enter the absolute or relative path to the folder where the PowerChannel Server places incoming files duringfile transfer. Reenter the current value if there is no change in the path to OUTPUT_FOLDER.

You can also use a server variable for the OUTPUT_FOLDER value.

22. Specify if a remote PowerChannel Server is allowed to execute external commands on the localPowerChannel Server. Or, press ENTER to confirm the current value.

Configuring the PowerChannel Server 39

23. Specify what rights a user must have to execute external commands from the options in the following table:

Value Description

all Allow all users to execute operation systems commands.

admin Allow administrators to execute operating systems commands.

none Allow no one to execute operating system commands.

Or, press ENTER to confirm the current value.

The plug-in installs when you install PowerChannel.

24. If you want to add a plug-in or change a plug-in, select one of the following options:

Value Description

1 Add a plug-in. Lets you select property values if you change operating systems.

2 Displays plug-in values.

3 Edit a plug-in.

4 Remove a plug-in. Lets you remove property values.

5 Exit the plug-in configuration.

25. Enter the JVM minimum and maximum memory.

This step is required if you start the PowerChannel Server as an application.

The utility closes after configuration completes.

26. Stop and restart the PowerChannel Server for the changes to take effect.

Working with PowerChannel Server VariablesPowerChannel contains a set of built-in server variables that allow you to control the location of source anddestination files during file transfer between PowerChannel Servers. You can also use the server variables tocontrol the location of PowerChannel session log files.

The PowerChannel Server uses the following server variables:

¨ $PC_DATE. Controls the location of source and destination files during file transfer, and the location of sessionlog 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 sessionlog files based on the user account that runs the command.

Use the server variables for the following tasks:

¨ Control source and destination file paths.

¨ Control log file path.

¨ Control export directory path.

40 Chapter 4: Administering the PowerChannel Server

Controlling Source and Destination File PathsUse $PC_DATE and $PC_USER to control the location of source and destination files during file transfer betweenPowerChannel Servers. Use $PC_DATE and $PC_USER in the file transfer command to define the path for thesource and destination files. You can also use $PC_DATE and $PC_USER as values for the INPUT_FOLDER andOUTPUT_FOLDER properties in the PowerChannel.properties file using the PowerChannel configuration utility.

You can also use $PC_USER and $PC_DATE as values for the input and output folder properties for a useraccount. For example, when you create or edit a user account, use $PC_USER and $PC_DATE as values for theinput and output folder parameters.

Using $PC_USER for Source and Destination File PathsWhen you use $PC_USER as the value for the source and destination file path, the PowerChannel Server looksfor source files during file transfer in the output/user_account_name directory. It writes destination files to the input/user_account_name directory.

For example, the PowerChannel user account name is “alice,” and you want to configure the PowerChannelServer to read source files during file transfer from the output directory, and write destination files during filetransfer to the input directory. Create a directory for the source data with the name “alice” under the outputdirectory. 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/alicedirectory. It writes destination files to the input/alice directory.

Using $PC_DATE for Source and Destination File PathsUse $PC_DATE to define the source or destination file path based on the system date. For example, you want thePowerChannel Server to read source files from a directory specific to the system date. You also want the server towrite destination files to a directory specific to the system date. Create a directory for the source files under theoutput directory. Name the directory based on the system date, for example, 2007-07-01. Create a directory forthe destination files under the input directory. Name the directory based on the system date, for example2007-07-01.

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-01directory. It writes files data to the input/2007-07-01 directory.

Using $PC_USER and $PC_DATE for Source and Destination File PathsYou can also use $PC_USER and $PC_DATE together to define the path for the source and destination files. Forexample, the user account name is “tracy,” and you want to configure the PowerChannel Server to read sourcefiles on July 01, 2007, from a directory specific to the user account and the system date. You also want the serverto write destination files on July 01, 2007, to a directory specific to the user account and the system date. Createthe following directory under the output directory for the source files:

tracy/2007-07-01

Working with PowerChannel Server Variables 41

Create the following directory under the input directory for the destination 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 transfercommand. Use $PC_USER and $PC_DATE as values for the -f option in the file transfer command.

Controlling the Log File PathUse $PC_USER and $PC_DATE to control the location of the PowerChannel session log files. Use $PC_USER asthe value for the LOG_FOLDER property in the PowerChannel configuration utility.

Using $PC_USER for the Log File PathWhen you use $PC_USER as the LOG_FOLDER property value, the PowerChannel Server writes session log filesto a directory specific to the user account that runs the command. You do not have to create a directory specific tothe user account. The PowerChannel Server creates a directory under the PowerChannel root directory for theuser account and writes session log files for all sessions you run.

For example, the user account name is “bob,” and you enter the following value for the LOG_FOLDER propertyusing the PowerChannel configuration utility:

log/$PC_USER

When you run sessions, the PowerChannel Server writes session log files to the log/bob directory.

Using $PC_DATE for the Log File PathSimilarly, use $PC_DATE as a value for the LOG_FOLDER property. When you use $PC_DATE as theLOG_FOLDER property value, the PowerChannel Server writes session log files to a directory specific to thesystem date when the session runs. You do not have to create the directory with a name specific to the systemdate. The server creates a directory specific to the system date under the PowerChannel root directory and writessession log files for all sessions you run.

For example, you want to configure the server to write session log files on July 01, 2007, to a directory specific tothe system date. Enter the following value for the LOG_FOLDER property using the PowerChannel configurationutility:

log/$PC_DATE

When you run sessions, the PowerChannel Server writes session logs to the log/2007-07-01 directory.

Using $PC_USER and $PC_DATE for the Log File PathUse $PC_USER and $PC_DATE together to define the path for session log files. For example, the PowerChanneluser account name is “alice,” and you want to configure the PowerChannel Server to write session log files on July01, 2007, to a directory specific to the user account and the system date. Enter the following value using thePowerChannel configuration utility:

log/$PC_USER/$PC_DATE

42 Chapter 4: Administering the PowerChannel Server

When you run sessions on July 01, 2007, the PowerChannel Server writes session log files to the followingdirectory:

log/alice/2007-07-01

Controlling Export Directory PathThe PowerChannel Server writes certificate files for certificate accounts you create in the export directory. Use$PC_USER and $PC_DATE as values for the EXPORT_DIR property to control the location of the PowerChannelexport directory. To modify the values of EXPORT_DIR, use the PowerChannel configuration utility.

Using $PC_USER for the Export Directory PathWhen you use $PC_USER as the value for the EXPORT_DIR property, the PowerChannel Server writes certificatefiles for certificate accounts you create to a directory specific to the user account name under the PowerChannelroot directory.

For example, the user account name is “mary,” and you want the server to write certificate files for all certificateaccounts you create to a directory specific to the user account. Enter the following value for the EXPORT_DIRproperty 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 theexport/mary directory. You do not have to create a directory with a name specific to the user account. The servercreates a directory under the export directory with the account name and writes certificate files for all certificateaccounts you create.

Using $PC_Date for the Export Directory PathUse $PC_DATE to control the location of the export directory based on the system date. For example, you wantthe PowerChannel Server to write certificate files for all certificate accounts you create on July 01, 2007 to adirectory specific to the system date. Enter the following value for the EXPORT_DIR property using thePowerChannel configuration utility:

export/$PC_DATE

When you create a certificate account on July 01, 2007, the PowerChannel Server writes the certificates files tothe 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 writescertificate files for all certificate accounts you create in that directory.

Using $PC_USER and $PC_DATE for the Export Directory PathUse $PC_USER and $PC_DATE together to define the path for the export directory. For example, thePowerChannel user account name is “alice,” and you want to configure the PowerChannel Server to writecertificate files on July 01, 2007 to a directory specific to the user account and the system date. Enter the followingvalue for the EXPORT_DIR property using the PowerChannel configuration utility:

export/$PC_USER/$PC_DATE

When you create certificate accounts on July 01, 2007, the PowerChannel Server writes the certificate files to thefollowing directory:

export/alice/2007-07-01

Working with PowerChannel Server Variables 43

Working with PowerChannel Server CommandsYou can complete the following PowerChannel Server tasks from the PowerChannel command line:

¨ Configure the PowerChannel properties file.

¨ Import a certificate account.

¨ Reencrypt the PowerChannel repository.

¨ Unlock the PowerChannel repository.

¨ Verify the PowerChannel repository version.

You can also use PowerChannel Server commands to start the server.

Configuring the PowerChannel Properties FileIf you want to configure the PowerChannel.properties file, use the PowerChannel configuration utility by runningthe PowerChannelconfig command. When you run the configuration utility, you can view the details for allproperties in the properties file. You can also view the details for the installation or plug-in properties only.

To configure the PowerChannel properties file:

1. Go to the PowerChannel directory.

2. Enter the PowerChannel config command.

Use the following command syntax to configure the properties file:PowerChannel config [-r=<properties_file_name>] [-pl={all|install|plugin}]

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Values in theformat {x|y} represent the options you can use for the command parameter. Parameters followed by an asterisk (*)can contain multiple values.

The following table describes the parameters for the PowerChannel config command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the properties file you want to modify. Otherwise, thePowerChannel 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 followingvalues:- 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 allproperties.

Importing a Certificate AccountBefore you can transfer data to a remote PowerChannel Server, the local PowerChannel Server must have acertificate account in the remote PowerChannel repository. The certificate account allows the local PowerChannelServer to authenticate itself as a valid server to the remote PowerChannel Server.

Note: The sample PowerChannel repository includes a default certificate account with a twoway profile. Thedefault certificate account allows PowerChannel Server that use the sample repository to transfer data with eachother.

44 Chapter 4: Administering the PowerChannel Server

The remote PowerChannel administrator must provide the local PowerChannel administrator with a certificate filefrom the PowerChannel /export directory and a password for the certificate account. The local PowerChanneladministrator must import the certificate file for the remote PowerChannel account into the local PowerChannelrepository. You must have a user account with the admin profile to import a certificate account.

When you import a certificate account, you can set the profile for the certificate account. You can set the profile tooneway or twoway. When you set the certificate account profile to oneway, a remote PowerChannel Server cannotconnect to the local PowerChannel Server with this account. When you set the certificate account profile totwoway, 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 importsthe account with a oneway profile, neither PowerChannel Server can use the account to communicate with theother PowerChannel Server.

To import a certificate account:

1. Go to the PowerChannel directory.

2. Enter the PowerChannel import command.

Use the following command syntax to import a certificate account:

PowerChannel import [-r=<properties_file_name>] [-u=<user_account_name>] [-p=<user_account_password>] -c=<import_certificate_file_name> -P=<certificate_password> -l={oneway|twoway}

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PowerChannel import command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PowerChannel.properties file. Otherwise, thePowerChannel 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 defaultuser account name in the default PowerChannel.properties file.

p Optional Enter the password for the account. Otherwise, the PowerChannel Server looks for it inthe default PowerChannel.properties file.

c Required Enter the name and path of the remote PowerChannel certificate file that you want toimport. 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.

l Required Enter one of the following values:- Oneway. Use to only allow the local PowerChannel Server to connect to the remote

server to transfer data using this account. When you use this value, the remotePowerChannel Server cannot connect to the local server to transfer data.

- Twoway. Use if you want both the remote PowerChannel Server and the localPowerChannel Server to be able to connect to each other and transfer data using thisaccount.

Working with PowerChannel Server Commands 45

Reencrypting the PowerChannel RepositoryThe PowerChannel Server encrypts the PowerChannel repository with a randomly generated key duringinitialization. PowerChannel secures the repository key internally for security. In the event that the repository keyis compromised, the PowerChannel administrator needs to reencrypt the repository. Compromising the repositorykey can lead to compromise of repository data.

You can reencrypt the repository from the PowerChannel command line. When you reencrypt the repository, theserver decrypts the repository using the old repository key and encrypts the repository again using a newrandomly generated key. When you reencrypt the repository, you do not alter the account and session informationstored in the repository. You must have a user account with the admin profile to reencrypt the PowerChannelrepository.

To reencrypt the PowerChannel repository:

1. Go to the PowerChannel directory.

2. Enter the PowerChannel reencrypt command.

Use the following command syntax to reencrypt the PowerChannel repository:

PowerChannel reencrypt [-r=<properties_file_name>] [-u=<user_account_name>] [-p=<user_account_password>]

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PowerChannel reencrypt command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PowerChannel.properties file using the PowerChannelconfiguration 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 defaultuser account name in the default PowerChannel.properties file.

p Optional Enter the password for the account. Otherwise, the PowerChannel Server looks for it inthe default PowerChannel.properties file.

Unlocking the PowerChannel RepositoryThe PowerChannel Server locks the PowerChannel repository when you start the server. It unlocks the repositorywhen you stop the server. When you do not stop the server properly, the repository remains locked. For example,if you shut down the system running the server due to an emergency or reboot the system due to an emergencywhile the server is still running, the repository remains locked.

Before you can start the PowerChannel Server again, you must unlock the PowerChannel repository. You canunlock the repository from the PowerChannel command line. To unlock the repository, you must have a useraccount with the admin profile.

To unlock the PowerChannel repository:

1. Go to the PowerChannel directory.

2. Enter the PowerChannel unlock command.

46 Chapter 4: Administering the PowerChannel Server

Use the following command syntax to unlock the PowerChannel repository:PowerChannel unlock [-r=<properties_file_name>] [-u=<user_account_name>] [-p=<user_account_password>]

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PowerChannel unlock command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PowerChannel.properties file. Otherwise, thePowerChannel 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 defaultuser account name in the default PowerChannel.properties file.

p Optional Enter the password for the account. Otherwise, the PowerChannel Server looks for it inthe default PowerChannel.properties file.

Verifying the PowerChannel Repository VersionYou can verify the version number of the PowerChannel repository. You may need to verify the repository versionnumber before upgrading the repository or when you back up the repository.

To check the PowerChannel repository version number:

1. Go to the PowerChannel directory.

2. Enter the PowerChannel version command.

Use the following command syntax to verify the version number of the PowerChannel repository:

PowerChannel version [-r=<properties_file_name>] [-u=<user_account_name>] [-p=<user_account_password>]

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PowerChannel version command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PowerChannel.properties file. Otherwise, thePowerChannel 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 defaultuser account name in the default PowerChannel.properties file.

p Optional Enter the password for the account. Otherwise, the PowerChannel Server looks for it inthe default PowerChannel.properties file.

Working with PowerChannel Server Commands 47

Stopping the PowerChannel Server with the Web ClientYou can stop the PowerChannel Server from the web client and PcCmd. If the PowerChannel Server runs as aservice, you can stop the service from the Windows Control Panel. The PowerChannel Server runs a session tostop the server and logs the session information in the server log. You must have a user account with the adminprofile to stop the server.

To stop the PowerChannel Server from the web client:

1. Go to the Administration tab.

2. From the list of actions, click Stop Server.

3. Click Stop to stop the PowerChannel Server.

48 Chapter 4: Administering the PowerChannel Server

C H A P T E R 5

Configuring PcCmd PropertiesThis chapter includes the following topics:

¨ Configuring PcCmd Properties Overview, 49

¨ Configuring PcCmd Properties, 50

¨ Configuring the PcCmd Properties File, 53

Configuring PcCmd Properties OverviewPcCmd is the command line program you use to transfer files, administer PowerChannel accounts and sessions,and stop the PowerChannel Server. You can run PcCmd commands on the machine running the PowerChannelServer or on a client machine. The client machine hosting PcCmd must be able to communicate with thePowerChannel Server with the TCP/IP protocol.

When you use PowerChannel to transfer files for a PowerCenter source or target, you can run PcCmd commandsfrom the Workflow Manager. You can include PcCmd commands in the pre- or post-session commands dialog toread 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 PcCmduses when you run a command. You can configure the properties file with the PcCmd configuration utility.

PcCmd can use the following properties files:

¨ PcCmd.properties. The default properties file installed with PcCmd. You can set the default values for allPcCmd properties in the PcCmd.properties file. PcCmd uses this file if you do not use an optional parameter tospecify a user-defined properties file in the PcCmdconfig command.

¨ Username.properties. You can create a properties file with all the PcCmd.properties file attributes. Forexample, you can create a properties file, username.properties, and set the default values for all PcCmdproperties in the username.properties file. When you run a PcCmd command, use the properties file option tospecify the username.properties file in the command. During command execution, PcCmd uses the propertiesin 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 PropertiesPcCmd uses property values when it runs a PcCmd command. For example, you can define the default useraccount name and password values for PcCmd commands in the properties file. When you define the useraccount name and password values in the properties file, you can omit the user account name and passwordparameters in a command. PcCmd uses the user account name and password parameter values in the propertiesfile.

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_ADDRESSYou can define the default PowerChannel Server address with the PcCmd configuration utility. If you omit the localPowerChannel Server name in the PcCmd command, PcCmd uses the server name or IP address defined in theSERVER_ADDRESS property.

The following parameter sets the default PowerChannel Server address:

SERVER_ADDRESS = <IP_address>

SERVER_PORTDefine the default PowerChannel Server port in the properties file with the PcCmd configuration utility. If you omitthe local PowerChannel Server port in the PcCmd command, PcCmd uses the port defined in the SERVER_PORTproperty. You can set a default port value from 1 to 65535.

The following parameter sets the default PowerChannel Server port:

SERVER_PORT = <port_number>

Note: When you enter a value for SERVER_PORT, do not use special characters, such as a comma.

PCCMD_LOGYou can enter the name and path of the PcCmd system log filename with the PcCmd configuration utility. PcCmdwrites all PcCmd system log messages to the PcCmd system log file.

50 Chapter 5: Configuring PcCmd Properties

The following parameter sets the default PcCmd system log filename:

PcCmd_LOG = <filename>

USERNAMEYou can enter a default user account name with the PcCmd configuration utility. When you set a default useraccount name in the properties file, you can omit the user account name parameter in the PcCmd command.

The following parameter sets the default user account name:

USERNAME = <user_name>

PASSWORDYou 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 thePcCmd command.

To encrypt the default password, use the PcPassword encryption utility from the PowerChannel command line. Touse the PcPassword utility for encrypting a user account password, enter PcPassword and the password you wantto encrypt.

For example, if you want to encrypt the password “Administrator,” go to the PowerChannel directory from thecommand 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 configurationutility. When you enter a value for PASSWORD, you can omit the password parameter in PcCmd commands.

The following parameter sets a default password:

PASSWORD = <password>

SESSION_NAMEYou can set a default PowerChannel session name in the PcCmd properties file with the PcCmd configurationutility. PcCmd uses the session name to name parent and child sessions. When you configure a name for aPowerChannel session, you can easily identify the PowerChannel sessions you run in the PowerChannel sessionlog. For example, you can set the session name to a PowerChannel user account name. PcCmd names the parentsession session_name.

Each parent and child PowerChannel session also receives a session ID. The session ID values increment by oneeach time the PowerChannel Server runs a session. The session name for the child session includes the parentsession name and the parent session ID. For example, you run the PcCmdsend command. You name the sessionalice. The local PowerChannel Server creates a parent session for the file transfer with the ID 326. The remotePowerChannel 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>

Configuring PcCmd Properties 51

COMPRESSION_LEVELEnter the default compression level you want to use for data compression. Compression levels range from 0 to 9.9 is the highest compression level. Enter 0 if you do not want to compress files during file transfer. When you enterthe default compression level in the properties file, you can omit the compression parameter in the PcCmdcommand.

The following parameter sets the default compression level in the properties file with the PcCmd configurationutility:

COMPRESSION_LEVEL = <level>

ENCRYPTION_LEVELEnter the default encryption level you want to use for data encryption. Encryption levels range from 0 to 3. 3 is thehighest encryption level. Enter 0 if you do not want to encrypt files during file transfer. When you enter the defaultencryption 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>

CHECKSUMYou can configure the PowerChannel Server to calculate a checksum value to ensure data integrity during filetransfer. When you set CHECKSUM to “yes” in the properties file, the PowerChannel Server calculates a distinctlong integer value for the file you transfer at the source and the destination PowerChannel Servers. If thechecksum values for the source file and the destination file are equal at the end of the file transfer, PowerChannelcompletes 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 thePowerChannel Server. When you use an FTP connection to transfer files, you cannot use checksum. You cannotuse checksum when PowerCenter reads data from remote database sources or writes data to remote databasetargets with PowerChannel.

When you enter a default value for CHECKSUM, you can omit the checksum parameter in the command forsending or getting files.

The following parameter sets the default checksum value:

CHECKSUM = {yes|no}

CODE_PAGEEnter the code page of the machine running PcCmd. The code page of the machine running PcCmd must be asubset of the code page of the PowerChannel Server machine. If you do not ensure code page compatibilitybetween the PowerChannel Server and PcCmd, the PowerChannel Server is unable to interpret the XMLcommands 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 thatsupports Japanese characters. For example, use the MS Shift JIS code page.

52 Chapter 5: Configuring PcCmd Properties

HOSTSYou can enter a certificate account name with the IP address and port of the remote PowerChannel Server. Whenyou enter the host information in the properties file with the PcCmd configuration utility, you can omit the remotehost information in the PcCmd file transfer command.

The following parameter sets the default remote host information:

HOSTS = <certificate_account@IP_address:port>

STAGEEnter whether you want to stage files during file transfer. When you enter a default staging value, you can omit thestaging 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 aPowerChannel Server.

The following parameter sets the default staging value:

STAGE = {all|receiving|none}

Note: You can only use staging when you run commands for transferring files. You cannot use staging when youuse an FTP connection to transfer flat files. You also cannot use staging when PowerCenter reads data fromremote sources or writes data to remote targets.

CRYPTOGRAPHYPowerChannel uses an encryption algorithm to encrypt and decrypt data. You set the encryption algorithm thatyou want PcCmd to use during installation. The installation program writes the value to the CRYPTOGRAPHYproperty.

You can modify the value for CRYPTOGRAPHY. When you enter a value for CRYPTOGRAPHY, anyPowerChannel Server or client you communicate with must use the same encryption algorithm. When you want touse FIPS-certified encryption, you must specify the 3DES encryption algorithm. If you do not include a value forCRYPTOGRAPHY, PcCmd uses the RC2 encryption algorithm by default.

The following parameter specifies the encryption algorithm:

CRYPTOGRAPHY = {JSAFE/RC2|JSAFE/3DES}

Configuring the PcCmd Properties FileYou can set the default values for several PcCmd properties in a properties file with the PcCmd configurationutility. To launch the configuration utility, you must run the PcCmd config command in the PowerChannel directory.

Note: When running the PcCmd configuration utility, you can enter Ctrl-C to exit the configuration utility at anytime.

To configure the PcCmd properties file:

1. From the command line, go to the PowerChannel directory.

2. Enter the PcCmd config command.

3. Enter the IP address of the default PowerChannel Server.

Configuring the PcCmd Properties File 53

If you omit the local PowerChannel Server name in the PcCmd command, PcCmd uses the server name or IPaddress defined in the SERVER_ADDRESS property.

4. Enter the port number of the default PowerChannel Server. Or, press ENTER to confirm the current value.

The value must be between 1 and 65535. When you enter a value, do not use special characters, such as acomma.

5. Enter the absolute or relative path to the PcCmd log file. Or, press ENTER to confirm the current value.

6. Enter a user name to run PcCmd commands. Or, press ENTER to confirm the current value.

The user name must be between 3 and 32 characters.

7. Enter a password to run PcCmd commands. Or, press ENTER to confirm the current value.

The password must be greater than 3 characters.

8. Enter a default PowerChannel session name. Or, press ENTER to confirm the current value.

When you set the default session name in the properties file, you can omit the session name in the PcCmdcommand.

9. Enter the compression level for data compression. Or, press ENTER to confirm the current value.

The compression level must be between 0 and 9.

10. Enter the encryption level. Or, press ENTER to confirm the current value.

The encryption level must be between 0 and 3.

11. Enter a checksum value to ensure data integrity during file transfer. Or, press ENTER to confirm the currentvalue.

When you enter a default value for the CHECKSUM parameter in the properties file, you can omit thechecksum parameter in the command for sending or getting files.

12. Use the following syntax to enter the remote PowerChannel Server connection parameter:<certificate_account@IP_address:port>

Or, press ENTER to confirm the current value.

13. Select one of the following values to stage files during file transfer:

Value Description

all Stages files on the local and remote PowerChannel Server.

receiving Stages files on the receiving PowerChannel Server.

none No staging.

Or, press ENTER to confirm the current value.

14. Select one of the following values for the default encryption level for data encryption:

Value Description

1 JSAFE/RC2

2 JSAFE/3DES

Or, press ENTER to confirm the current value.

54 Chapter 5: Configuring PcCmd Properties

C H A P T E R 6

Flat File Data TransferThis chapter includes the following topics:

¨ Flat File Data Transfer Overview, 55

¨ Transferring Files Between PowerChannel Servers, 55

¨ Transferring Files Between FTP Clients and Servers, 61

¨ Transferring Source and Target Files in PowerCenter, 64

¨ Troubleshooting a Flat File Data Transfer, 68

Flat File Data Transfer OverviewPowerChannel transfers files between PowerChannel Servers through secure channels. Use PowerChannel forthe following file transfer tasks:

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

Transferring Files Between PowerChannel ServersUse PcCmd commands to send files to remote PowerChannel Servers and get files from a remote PowerChannelServer. When you transfer files, the local PowerChannel Server interprets the files as strings of binary bits andtransfers them across the network.

PowerChannel lets you transfer multiple files from a local PowerChannel Server to multiple remote PowerChannelServers. You can also use PowerChannel to transfer multiple files from a remote PowerChannel Server to thelocal PowerChannel Server.

Requirements for File TransferTo use PowerChannel to transfer files between PowerChannel Servers, you must meet the following requirements:

¨ 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 TransferDuring file transfer, the PowerChannel Server reads files from input folders and writes files to output folders. Youcan change the default input and output folders with the PowerChannel configuration utility. You can also enterinput and output folders for user accounts and certificate accounts. The PowerChannel Server uses the input andoutput 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 PowerChannelServer only uses the values in the default input and output folders from the PowerChannel.properties file.

Input and Output Folders in the PcCmd get CommandWhen you enter a PcCmdget command, and the certificate account you specified in the command contains arelative path to an input folder, the remote PowerChannel Server reads the files you want to transfer from thefollowing directory:

<default_input_folder>/<certificate_account_input_folder>

When the local PowerChannel Server receives the files from the remote PowerChannel Server, and the useraccount you used to run the command contains a relative path to an output folder, the local PowerChannel Serverreceives 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 thePowerChannel.properties file is output. The value for the input folder in the certificate account is cert1. The valuefor the output folder in the user account is admin. When you run PcCmdget, the remote PowerChannel Serverlooks for the files you want to transfer in the input/cert1 directory. When the local PowerChannel Server receivesthe 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, thePowerChannel 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 thefollowing 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.

Input and Output Folders in the PcCmd send CommandWhen you enter a PcCmdsend command, and the user account you specified in the command contains a relativepath to an input folder, the local PowerChannel Server reads the files you want to transfer from the followingdirectory:

<default_input_folder>/<user_account_input_folder>

When the remote PowerChannel Server receives the files from the local PowerChannel Server, and the useraccount you used to run the command contains a relative path to an output folder, the remote PowerChannelServer 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 thePowerChannel.properties file is output. The value for the input folder in the user account is admin. The value forthe output folder in the certificate account is cert1. When you run a PcCmdsend command, the localPowerChannel Server looks for the files you want to transfer in the input/admin directory. When the remotePowerChannel 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, thePowerChannel Servers ignore the default input and output folder values from the PowerChannel.properties file.

56 Chapter 6: Flat File Data Transfer

For example, you enter a PcCmdsend command, and the user account you specified in the command contains thefollowing absolute path for the input folder:

c:\powerchannel\pchserv1

When you run the command, the local PowerChannel Server looks for the files you want to transfer in the c:\powerchannel\pchserv1 directory.

Entering Filenames in PcCmd get and PcCmd send CommandsWhen you enter a PcCmdget or PcCmd send command, enter the -f parameter to specify the source anddestination name of the file you want to transfer separated by a comma. Use the following guidelines whenentering the -f parameter in the PcCmdget or PcCmd send command:

¨ If you do not enter a destination filename, the PowerChannel Server writes the source file to the destinationwith the same name as the source file.

¨ When you separate filename pairs on UNIX, escape the “;” character with a “\” character. For example, use thefollowing 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 filesinto 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 asemicolon. For example, you can enter data1.txt;data2.txt to transfer the files data1.txt and data2.txt.

Transferring Text Files from Windows to UNIXSince the PowerChannel Server transfers data in binary mode, it does not distinguish between the actual text,carriage return, and line feed characters in a text file. During file transfer, the carriage return and line feedcharacters are transferred along with the actual text data. Because UNIX does not use carriage returns, thisresults in ^M characters at the end of each line of text in the target file on UNIX when you receive the file from aWindows system. After the file transfer is complete, you need to remove the ^M characters from the target file.

Receiving Files from a Remote PowerChannel ServerUse the PcCmdget command to get files from a remote PowerChannel Servers. When you use PcCmdget, thelocal PowerChannel Server connects to the remote servers to get the files.

Warning: When you use PcCmdget to get files and you get files with the same name from multiple remotePowerChannel Servers, avoid overwriting existing files.

For example, you transfer the file data1.txt from the server PowerChannel1 to an input folder. Later, you transferanother file, data1.txt, from the server PowerChannel2 to an input folder. The file data1.txt from the serverPowerChannel2 overwrites the file of the same name from the server PowerChannel1 because it is the mostrecent 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 thefiles into separate directories according to the server you get the files from. Use the -f parameter in the PcCmdgetcommand to specify the path and filename of the files you want to transfer.

Transferring Files Between PowerChannel Servers 57

To receive files from remote PowerChannel Servers:

1. Go to the PowerChannel directory.

2. Enter the PcCmd get command.

Use the following command syntax to get a file:PcCmd get [-r=<properties_file_name>][-u=<user_account_name>] [-p=<user_account_password>] [-S=<server_hostname>[:<server_port>]] [-sn=<session_name>] -f=<source_file>[,<destination_file>] [;<source_file>[,<destination_file>]]* [-R=<remote_certificate_account>[@<remote_hostname>][:<remote_port>]] [-cl=<compression_level>] [-el=<encryption_level>] [-T={none|receiving|all}] [-w={yes|no}] [-cs={yes|no}]

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PcCmd get command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the defaultproperties file.You must enter the absolute path to the PcCmd.properties file when you read data from aflat 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 inthe PcCmd.properties file.

p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in thePcCmd.properties file.

S Optional Enter the host name or IP address and port number of the local PowerChannel Server. Ifyou 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 thePcCmd.properties file.

f Required Enter the source filename and the destination filename separated by a comma. Forguidelines on entering values for -f, see “Entering Filenames in PcCmd get and PcCmdsend Commands” on page 57.

R Optional Enter a certificate account name and host information for the remote PowerChannelServer from which you want to receive files.If you do not enter the IP address and port of the remote host, the PowerChannel Serveruses 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 thePcCmd.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 thePcCmd.properties file.

58 Chapter 6: Flat File Data Transfer

CommandParameters

Required/Optional

Description

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 configurationdefined in the PcCmd.properties file.

w Optional Use the wait option if you want the PowerChannel Server to wait until it completes asession before it responds to PcCmd with a message. This option is useful when you runmultiple 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-sessioncommand in a PowerCenter session.

cs Optional Specify whether you want the PowerChannel Server to calculate checksum for the filetransfer. Enter “yes” to enable checksum. Enter “no” to disable checksum. If you do notenter 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.

Sending Files to Remote PowerChannel ServersUse the PcCmdsend command to send files from a local PowerChannel Server to remote PowerChannel Servers.When you use PcCmdsend, the local PowerChannel Server connects to the remote servers to send the files.PowerChannel lets you transfer files to multiple servers. You can also send multiple files in a single command.

Note: When you transfer files to multiple PowerChannel Servers and the local PowerChannel Server fails toconnect to one of the remote servers, the local server fails the file transfer session.

To send files from a local PowerChannel Server to remote PowerChannel Servers:

1. Go the PowerChannel directory.

2. Enter the PcCmd send command.

Use the following command syntax to send a file:PcCmd send [-r=<properties_file_name>][-u=<user_account_name>] [-p=<user_account_password>] [-S=<server_hostname>[:<server_port>]] [-sn=<session_name>] -f=<source_file>[,<destination_file>] [;<source_file>[,<destination_file>]]* [-R=<remote_certificate_account>[@<remote_hostname>][:<remote_port>] [;<remote_certificate_account>[@<remote_hostname>][:<remote_port>]]*] [-cl=<compression_level>] [-el=<encryption_level>] [-T={none|receiving|all}] [-w={yes|no}] [-cs={yes|no}]

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

Transferring Files Between PowerChannel Servers 59

The following table describes the parameters for the PcCmd send command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the defaultproperties file.You must enter the absolute path to the PcCmd.properties file when you write data to aflat 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 inthe PcCmd.properties file.

p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in thePcCmd.properties file.

S Optional Enter the host name or IP address and port number of the local PowerChannel Server. Ifyou 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 thePcCmd.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 PowerChannelServer to which you want to send the files. If you are sending files to multiplePowerChannel Servers, you need to enter a certificate account name for each remoteserver separated by a semicolon.If you do not enter the IP address and port of the remote hosts, the PowerChannel Serveruses 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 thePcCmd.properties file.

el Optional Enter the encryption level. Valid encryption levels are from 1 to 3 or none. Enter “none” forno encryption.If you do not enter an encryption level, PcCmd uses the encryption level defined in thePcCmd.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 configurationdefined in the PcCmd.properties file.

w Optional Use the wait option if you want the PowerChannel Server to wait until it completes asession before it responds to PcCmd with a message. This option is useful when you runmultiple 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-sessioncommand in a PowerCenter session.

cs Optional Specify whether you want the PowerChannel Server to calculate checksum for the filetransfer. Enter “yes” to enable checksum. Enter “no” to disable checksum. If you do notenter 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.

60 Chapter 6: Flat File Data Transfer

Transferring Files Between FTP Clients and ServersIf you use FTP to transfer large volumes of data over a WAN or across firewalls in an Internet environment, youcan configure the FTP client to transfer the data through PowerChannel. You replace the direct connectionbetween FTP clients and servers with a fast, secure PowerChannel connection. You can then use PowerChannelto transfer the data in compressed and encrypted format between FTP clients and servers across a network.

PowerChannel can listen for FTP client requests from multiple clients and forward the requests to multiple FTPservers. 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 PowerChannelServer listens for requests from FTP clients on the same LAN as the server. You configure FTP client commandsto forward the command requests to the local PowerChannel Server. Use the PcCmd createpipe command fromthe command line of the local PowerChannel Server to start a session for the local PowerChannel Server to listenfor requests from FTP clients. The PowerChannel session opens PIPE channels between the local PowerChannelServer and a remote PowerChannel Server in the same LAN as the FTP server. The servers use the PIPEchannels 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 enterconnection information to the FTP server in PcCmd createpipe. You can also enter a timeout period in thecommand after which any idle connections between PowerChannel and FTP servers close. The localPowerChannel Server uses the connection information to forward file transfer requests from FTP clients to FTPservers through the remote PowerChannel Server. The PowerChannel Servers then transfer the data betweenFTP clients and servers.

After the PowerChannel Servers complete the file transfer tasks, the connection between PowerChannel and theremote FTP servers closes. However, the PIPE channels connecting the PowerChannel Servers remain open untilyou stop the PowerChannel session. The PIPE channels also remain open when file transfer betweenPowerCenter and the FTP server fails. Keeping the connection open allows PowerChannel to transfer datawhenever 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 withencryption and compression. You connect the local and remote PowerChannel Servers with PIPE channels. Thelocal 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. Itopens a connection to the remote FTP server through the remote PowerChannel Server. The local PowerChannelServer compresses and encrypts the data according to the user command and writes the data to the network. Theremote PowerChannel Server reads the data from the network and decompresses and decrypts the data. It writesthe data to the FTP server. The connection between the PowerChannel Server and FTP server closes. Thesession hosting the connection between the PowerChannel Servers continues to run until you stop the session.

Requirements for Transferring Files Between FTP Clients and ServersYou must meet the following requirements to transfer files between FTP clients and servers throughPowerChannel:

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

Transferring Files Between FTP Clients and Servers 61

Transferring FilesTo transfer files between FTP clients and servers complete the following steps to enable PowerChannel:

1. Create a connection between PowerChannel Servers.

2. Configure the FTP connection and run FTP commands.

When you configure PowerChannel to transfer data between FTP clients and servers, you can view the status ofthe files you transfer. You can also view the status of the PowerChannel session hosting the connection betweenthe PowerChannel Servers.

Step 1. Create a Connection Between PowerChannel ServersUse the PcCmdcreatepipe command to connect the local and remote PowerChannel Servers. When you run thecommand, the local PowerChannel Server creates a session to open PIPE channels between the PowerChannelServers. It also listens for requests from FTP clients on the same LAN.

To create a connection between PowerChannel Servers:

1. Go to the PowerChannel directory.

2. Enter the PcCmd createpipe command.

Use the following command syntax to create a connection between PowerChannel Servers:PcCmd createpipe [-r=<properties_file_name>][-u=<user_account_name>] [-p=<user_account_password>][-S=<server_hostname>[:<server_port>]][-sn=<session_name>] [-R=<remote_certificate_account>[@<remote_hostname>[:<remote_port>] -F=[<type>!][<local_param>][~<remote_param>][;[~<type>!][<local_param>][~<remote_param>]]* [-cl=<compression_level>][-el=<encryption_level][-w={yes|no}]

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PcCmd createpipe command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the defaultproperties 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 inthe PcCmd.properties file.

p Optional Enter the password for the user account. Otherwise, the PowerChannel Server looks forthe 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. Ifyou 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 thePcCmd.properties file.

R Optional Enter the certificate account name and host information for the remote PowerChannelServer.

62 Chapter 6: Flat File Data Transfer

CommandParameters

Required/Optional

Description

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 fromPowerCenter or FTP clients. If you do not enter a listener port, the local PowerChannelServer uses port 21 by default.

- The remote connector parameters. Enter the host name or IP address of the FTPserver you want to connect to through PowerChannel. You can enter a port for the FTPserver. If you do not enter a listener port, the local PowerChannel Server uses port 21by default. You can also enter a timeout period in seconds from 0 to 100000. Any idleconnections between PowerChannel and FTP servers close after the timeout periodexpires.

Note: Do not enter a timeout period when transferring target files to an FTP server inPowerCenter.

For example, you want to connect to the FTP server serv1 with a timeout period of 1,000seconds. 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 theremote connector parameters. For example, use the following to connect to the FTPserver 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 nonefor no compression.If you do not enter a compression level, PcCmd uses the compression level defined in thePcCmd.properties file.

el Optional Enter the encryption level. Valid encryption levels are from 1 to 3 or none. Enter none forno encryption.If you do not enter an encryption level, PcCmd uses the encryption level defined in thePcCmd.properties file.

w Optional Use the wait option if you want the PowerChannel Server to wait until it completes asession before it responds to PcCmd with a message. Since sessions hosting PIPEchannels do not end until you stop them, set the wait option to no.

Step 2. Configure the FTP Connection and Run FTP CommandsCreate a connection from FTP clients to the local PowerChannel Server. In the FTP commands for file transfer,define a connection to the local PowerChannel Server. This connection allows FTP clients to forward the filetransfer requests to the local PowerChannel Server. When you run an FTP command to transfer files, thePowerChannel Servers transfer files with encryption and compression.

To configure an FTP connection and run FTP commands:

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 followingparameter in the FTP command:

open pchserv 222. 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.

Transferring Files Between FTP Clients and Servers 63

For example, to use an FTP script to transfer the files data1.txt and data2.txt from the remote FTP server, enterthe following parameters in the script before running the command:

open pchserv 22admintestmget data1.txt; data2.txt!bye

Monitoring the Status of FTP FilesThe status of each file you transfer appears in the command window on the FTP client machine. The status ofeach file also appears in the session log files of the local and remote PowerChannel Servers. Since you can runmultiple FTP commands for file transfer during a single PowerChannel session, the PowerChannel session logfiles display the file transfer status for each FTP command.

Monitoring the PowerChannel SessionYou can determine the status of the PowerChannel session hosting the connection between PowerChannelServers by viewing a message in the server command window if you run PowerChannel as an application. If yourun PowerChannel as a service, you can determine the status of the PowerChannel session by viewing theWindows Event Viewer. You can also view the local PowerChannel Server session log file for the session andsession details with the web client or PcCmd.

When the session is running, the PowerChannel Server command window, the Event Viewer, and thePowerChannel 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 therequests to the FTP server at serv1:21. The timeout period is 1,000 seconds. The PowerChannel Server commandwindow and the session log file display the following message:

Pipe Listener is accepting connections at port: 21 (forward to serv1:21/Timeout=1000)

When the session stops or fails, the following message appears:

Pipe Listener stopped accepting connections at port: <port>

You can also monitor the PowerChannel session with the web client or PcCmd. For example, you can determinethe number of bytes the PowerChannel Servers transfer during the session.

You can stop the PowerChannel session with the web client or PcCmd.

Transferring Source and Target Files in PowerCenterYou can read data from flat file sources and write data to flat file targets during a PowerCenter session withPowerChannel. For example, you use an FTP connection to read flat file source data and write flat file target datain a PowerCenter mapping. You can replace the direct FTP connection between PowerCenter and the FTP serverwith a PowerChannel connection that allows fast and secure data transfer. You can also use PcCmd commands inpre- and post-session commands to transfer data in compressed and encrypted format during a PowerCentersession.

When you replace the direct FTP connection between PowerCenter and the FTP server, you create a connectionbetween PowerChannel Servers to transfer the data. You configure the FTP connection in the PowerCenterWorkflow Manager. As long as the connection between PowerChannel Servers is open, use the FTP connection toread flat file source data from an FTP server or write flat file target data to an FTP server whenever you run aPowerCenter session.

64 Chapter 6: Flat File Data Transfer

When you use PcCmd commands in pre- and post-session commands, you enter a PcCmdget command in a pre-session command each time you run a PowerCenter session to read flat file source data with PowerChannel. Youenter PcCmdsend command in a post-session command each time you run a PowerCenter session to write flat filetarget data with PowerChannel.

Transferring Files Between PowerCenter and an FTP ServerIf you use an FTP connection for a flat file source or target in PowerCenter, you can extract the source file andwrite the target file in compressed and encrypted format through PowerChannel. This is a fast and securealternative to with a direct FTP connection to transfer source and target files.

When you configure the PowerCenter session, you replace the direct connection between PowerCenter and theFTP server with a fast, secure PowerChannel connection. You create the PowerChannel connection betweenPowerCenter and the FTP server by entering the PcCmd createpipe command from the command line of the localPowerChannel Server, which resides in the same LAN as PowerCenter.

PcCmd createpipe starts a PowerChannel session to listen for requests from the Integration Service. ThePowerChannel session opens PIPE channels between the local PowerChannel Server and a remotePowerChannel Server in the same LAN as the FTP server. The servers use the PIPE channels for transferringsource 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 localPowerChannel Server uses the connection information to forward file transfer requests from PowerCenter to theFTP server through the remote PowerChannel Server. The PowerChannel Servers then transfer the file betweenPowerCenter and the FTP servers.

After the PowerChannel Servers complete the file transfer tasks, the connection between PowerChannel and theremote FTP servers closes. However, the PIPE channels connecting the PowerChannel Servers remain open untilyou stop the PowerChannel session. The PIPE channels also remain open when file transfer betweenPowerCenter and the FTP server fails. Keeping the connection open allows PowerChannel to transfer fileswhenever 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 Serverthen listens for file transfer requests from PowerCenter. When you run a PowerCenter session, the localPowerChannel Server receives the file transfer request. It opens a connection to the remote FTP server throughthe 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 thePcCmdcreatepipe command and writes the file to the network. The local PowerChannel Server reads the file fromthe network and decompresses and decrypts the file. It writes the file to the Integration Service. The connectionbetween PowerChannel Server and PowerCenter closes. The session hosting the connection between thePowerChannel 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 sessionhosting the connection between the PowerChannel Servers.

Requirements for Transferring Files Between PowerCenter and an FTP ServerYou must meet the following requirements to enable PowerCenter to read source files from an FTP server andwrite target files to an FTP server through PowerChannel:

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

Transferring Source and Target Files in PowerCenter 65

¨ 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 youwant to write files to a target, the target definition in the mapping must be flat file.

Steps for Transferring Files Between an FTP Server and PowerCenterComplete the following steps to enable PowerCenter to read source files from an FTP server and write target filesto an FTP server through PowerChannel:

1. Create a connection between PowerChannel Servers. When you create a connection betweenPowerChannel Servers to transfer data during a PowerCenter session, do not use the timeout option in the -Fparameter 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.

Configuring an FTP Connection in PowerCenterWhen you configure an FTP connection in PowerCenter, you must provide the host name or IP address of thelocal PowerChannel Server. Provide the local PowerChannel Server host name or IP address instead of the hostname of the FTP server to which you want to connect. Optionally, you can enter a port number from 1 to 65535. Ifyou do not enter a port number, the Integration Service uses the port number 21 by default. Use the followingsyntax:

<local_PowerChannel_IPaddress>[:<port>]

For example, to connect to a local PowerChannel Server at pchserv with port 22, enter the following host nameand port:

pchserv:22

Monitoring the Source and Target File TransferThe status of the PowerCenter session you run to transfer files displays in the PowerCenter Workflow Monitor.You can also monitor the PowerChannel session you run that hosts the connection between PowerChannelServers.

Working with PcCmd Commands in PowerCenter Sessions for FileTransfer

Use PcCmd commands in PowerCenter sessions to transfer source or target flat file data. You can transfer sourcefiles to PowerCenter or transfer target files from PowerCenter in compressed and encrypted format.

To transfer source or target data with PowerChannel commands in a PowerCenter session, you use PcCmdgetand send commands in pre- and post-session commands. Use PcCmdget in the pre-session command dialog boxwhen you want to read data from a flat file source. Use PcCmdsend in the post-session command dialog box whenyou 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 usethe .bat file in the pre- or post-session commands. Enter the .bat filename in the pre- or post-session commanddialog box.

For example, you want to analyze customer transactional data stored in a file at the customer site. You want to getthe customer data file from the remote location, use the file as a source in a session, and write the output to atarget. To retrieve the customer data file and run the session, use PcCmd get in the PowerCenter pre-sessioncommand. PowerCenter uses the PowerChannel command to get the customer data file before it runs the session.

66 Chapter 6: Flat File Data Transfer

Required PowerChannel Command ParametersUse the following PcCmd command parameters when you use PcCmd file transfer commands in a pre- or post-session command:

¨ -r. Use the properties file option by running the PowerChannel configuration utility to specify the absolute pathto the PcCmd.properties file.

¨ -w. Use the wait option with the PcCmd get and PcCmd send commands in the pre- and post-sessioncommands. 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 theabsolute path to the PcCmd.properties file or the username.properties file. When you do not enter the absolutepath 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-sessioncommand. When you use the wait option with PcCmdget, the PowerChannel Server waits until the file transfer iscomplete before it responds to PcCmd with a message. The Integration Service uses this prompt to start readingfrom the source. As a result, the Integration Service starts reading the source file only after the PowerChannel filetransfer is complete. If you do not use the -w option in the pre-session command, the Integration Service mightstart 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 inPcCmd send, the PowerCenter session fails when the PowerChannel file transfer fails. You can view thePowerChannel session log for details on the file transfer. If you do not use the wait option in PcCmd send, youcannot determine whether the file transfer completes successfully. You can view the PowerChannel session logfile 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.

Viewing the PowerCenter Session LogYou can view the PowerCenter session log file for information about pre- or post-session command execution. Thesession log contains messages about the success or failure of pre- or post-session commands.

Pre- and Post-Session Command File Transfer RequirementsYou must meet the following requirements to use PcCmd commands in PowerCenter sessions:

¨ 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 youwant 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 samefilename and path as the filename you enter in the PcCmd get command. Similarly, if you want to use PcCmdin a post-session command, the target file in the session must have the same filename and path as thefilename you enter in the PcCmdsend command.

¨ Enter None as the connection type for the source or target in the PowerCenter session properties.

Receiving Source Files for a PowerCenter SessionUse PowerChannel to get files from a remote PowerChannel Server to use as a source in a PowerCenter session.For example, you use PowerCenter in a data center to analyze transactional data that you collect from a satelliteoffice. You want to get the transactional data from the satellite office and write the data to a target. Use

Transferring Source and Target Files in PowerCenter 67

PowerChannel to get the transactional data file from the satellite office and run a session with PowerCentermapping to transform the data and write the data to a target. To get the transactional data file with PowerChannel,use PcCmdget in the pre-session command.

Note: To use PcCmdget in a pre-session command, the source file in the session must have the same filenameand path as the target file in the PowerChannel file transfer.

To receive source files with a pre-session command in PowerCenter:

1. In the Workflow Manager, locate the pre-session command field in the session properties of the session forwhich 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.

Sending Target Files from a PowerCenter SessionUse PowerChannel to transfer target files from a PowerCenter session. For example, you run a mapping to loaddata to a file target. You want to send the target file to a remote PowerChannel Server after the Integration Servicecompletes loading the target file. Configure the session to use a post-session command. Use PcCmd send in thepost-session command to transfer the file to a remote PowerChannel Server.

Note: To use PowerChannel in a post-session command, the target file you use in the session must have thesame filename and path as the source file in the PowerChannel file transfer.

To use a post-session command in PowerCenter:

1. In the Workflow Manager, locate the post-session command field in the session properties of the session forwhich 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.

Troubleshooting a Flat File Data Transfer

PowerCenter could not transfer a target file to a remote FTP server through PowerChannel.

You entered a timeout period in the PcCmdcreatepipe command that expired during the PowerCenter session. Asa result, the connection between PowerChannel and the FTP server closed. PowerCenter could not transfer thetarget file. Do not use a timeout period in PcCmdcreatepipe when you use PowerChannel to transfer target files ina PowerCenter session.

68 Chapter 6: Flat File Data Transfer

The machine hosting the FTP client crashed. However, the remote FTP server does not stop attempts totransfer the files. Or, the machine hosting the FTP server crashed. However, the FTP client does not stopattempts to transfer the files.

Manually stop the FTP file transfer session. After you restore the FTP client or server, transfer the files again.

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. Forexample, if you transfer the file data1.txt with staging, the target PowerChannel Server temporarily stages the filedata1.txt.zip. If you transfer the file data1.txt more than once in the same command and set staging on both thesending and receiving PowerChannel Servers, the target PowerChannel Server overwrites the first data1.txt.zipfile 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 betweenPowerChannel 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 serverdoes not stop during the session. If the FTP server stops or fails during the session, restart the FTP server andrun the session again.

Troubleshooting a Flat File Data Transfer 69

C H A P T E R 7

Working with Database Sourcesand Targets

This chapter includes the following topics:

¨ Working with Database Sources and Targets Overview, 70

¨ Configuring PowerChannel for Data Transfer, 72

¨ Configuring a Mapping and Workflow for PowerChannel Data Transfer, 72

¨ Viewing the PowerCenter Session Log for Database Data Transfer, 73

¨ Troubleshooting a PowerChannel Database Data Transfer, 73

Working with Database Sources and Targets OverviewUse PowerChannel to transfer data from remote database sources for use in a PowerCenter mapping. You canalso use PowerChannel to transfer data from the Integration Service to remote database targets.

Note: PowerChannel does not support database data transfer on Linux.

To use remote database sources and targets in a PowerCenter mapping, you need to create a mapping in theDesigner to define the data transfer. In the Workflow Manager, you configure a connection to the remote databasethrough PowerChannel. When you configure the connection, enter an active listener port number that thePowerChannel Server uses to listen for data transfer requests from the Integration Service. You then create asession for the mapping and use the PowerChannel connection to the database to extract, transform, and loaddata.

When you want PowerCenter to read or write remote database data, you connect the Integration Service to aremote PowerChannel Server. You set up the remote PowerChannel Server on the same network as the source ortarget data. When you use a remote database as a source in the mapping, the remote PowerChannel Serverreads the data from the remote database and sends it to the Integration Service. When you use a remotedatabase as a target in the mapping, the remote PowerChannel Server writes the data received from theIntegration Service to the remote database.

Note: A PowerCenter session running in ASCII mode loads invalid data when the source is not valid ASCII. Toavoid 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

Requirements for Transferring Database DataTo enable PowerCenter to run a workflow to read data from remote sources and write data to remote targetsthrough PowerChannel, you must meet the following requirements:

¨ A PowerChannel Server must exist in the same network as the remote database. The PowerChannel Serverneeds 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 theIntegration Service must be generic.

¨ The USER_PROFILE attribute for the active listener that you want to use to listen for data transfer requestsfrom the Integration Service must be transport.

¨ The remote PowerChannel Server must be running.

Transferring Data with Compression and EncryptionPowerChannel can transfer data between the Integration Service and remote databases in compressed andencrypted format to increase performance and security. When you want PowerCenter to read or write data withencryption or compression, you need to install a local and a remote PowerChannel Server. Install the localPowerChannel Server in the same network as the Integration Service.

When the Integration Service extracts data from a remote database source, the remote PowerChannel Servercompresses and encrypts the source data and sends it to the local PowerChannel Server. The localPowerChannel Server decrypts and decompresses the data and passes it to the Integration Service. When youuse a remote database target in the mapping, the local PowerChannel Server encrypts and compresses the datareceived from the Integration Service and sends it to the remote PowerChannel Server. The remote PowerChannelServer decrypts and decompresses the data and writes it to the remote database.

Requirements for Transferring Database Data with Compression and EncryptionTo enable PowerCenter to run a workflow to read data from remote sources and write data to remote targetsthrough PowerChannel, you must meet the requirements in “Requirements for Transferring Database Data” onpage 71.

You must also meet the following requirements:

¨ A PowerChannel Server must exist in the same network as the Integration Service. You can install thePowerChannel 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 remotePowerChannel Server.

¨ Create a certificate account for the local PowerChannel Server in the remote PowerChannel repository.

¨ The local and remote PowerChannel Servers must be running.

Working with Database Sources and Targets Overview 71

Configuring PowerChannel for Data TransferWhen you read data from remote databases and write data to remote databases with PowerChannel, you need toconfigure a PowerChannel Server to listen for data transfer requests from the Integration Service.

Configuring the Remote PowerChannel Server PropertiesIf you want the remote PowerChannel Server to receive data transfer requests directly from the IntegrationService, you must configure the ACTIVE_LISTENERS property in the PowerChannel configuration utility. Youmust ensure that the value for the PORT attribute is not used by other applications on the remote PowerChannelServer. You can also enhance security for the PowerChannel Server by configuring the IP address and FILTERattributes for the ACTIVE_LISTENERS property.

When you want the Integration Service to read compressed and encrypted data from databases and writecompressed and encrypted data to databases, you must configure a local PowerChannel Server in addition to aremote PowerChannel Server. The remote PowerChannel repository must contain a certificate account for thelocal PowerChannel Server.

Configuring the Local PowerChannel Server PropertiesWhen you want the Integration Service to read compressed and encrypted data from databases and writecompressed and encrypted data to databases, you must configure a local PowerChannel Server in addition to aremote PowerChannel Server. The remote PowerChannel repository must contain a certificate account for thelocal PowerChannel Server.

If you want the Integration Service to send data transfer requests to the local PowerChannel Server, you mustconfigure the ACTIVE_LISTENERS property with the PowerChannel configuration utility. You must ensure that thevalue for the PORT attribute is not used by other applications on the local PowerChannel Server. You can alsoenhance security for the PowerChannel Server by configuring the IP address and FILTER attributes for theACTIVE_LISTENERS property.

Configuring a Mapping and Workflow for PowerChannelData Transfer

Complete the following steps to configure a mapping and workflow for PowerChannel data transfer:

1. Create a mapping. Create an ODBC data source to connect to the source or target database to importdefinitions.

2. Create a PowerCenter session. Configure a PowerChannel connection to enable the Integration Service toaccess the remote database through PowerChannel.

3. Configure and start PowerChannel. Configure the remote PowerChannel Server to read data from remotedatabase sources and write data to remote database targets. If you use compression and encryption, you alsoneed to configure the local PowerChannel Server to compress and encrypt data before sending it to theremote PowerChannel Server. You also need to configure the PowerChannel.properties file on thePowerChannel Server from which the Integration Service requests data.

4. Create and schedule a workflow.

72 Chapter 7: Working with Database Sources and Targets

Viewing the PowerCenter Session Log for DatabaseData Transfer

When you run a PowerCenter session to read data from a database source or write data to a database target, youcan view the PowerCenter session log to monitor the status of the data transfer. During the PowerCenter session,the PowerChannel Server runs one PowerChannel session for each partition. For example, if you want to run aPowerCenter session to read data from a database source, and you specify two partitions for the session, thePowerChannel Server runs two PowerChannel sessions, one for each partition.

In the PowerCenter session log, the Integration Service associates each partition with its correspondingPowerChannel 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 thatthe 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 aDB2 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.

Troubleshooting a PowerChannel Database DataTransfer

PowerCenter fails to connect to the database through PowerChannel when reading data from a remote source.

You must configure the ACTIVE_LISTENERS property with the PowerChannel configuration utility. Configure thefollowing values in the ACTIVE_LISTENERS property:

¨ Set the USER_PROFILE parameter to transport.

¨ Set the PROTOCOL parameter to generic.

Viewing the PowerCenter Session Log for Database Data Transfer 73

C H A P T E R 8

Managing PowerChannel SessionsThis chapter includes the following topics:

¨ Managing PowerChannel Sessions Overview, 74

¨ Monitoring PowerChannel Sessions with the Web Client, 74

¨ Stopping Sessions with the Web Client, 78

Managing PowerChannel Sessions OverviewThe PowerChannel Server creates sessions to transfer data. When you transfer files between PowerChannelServers, the local server creates a session to transfer the files. When you transfer files between PowerCenter andan FTP server or between FTP clients and servers, the local PowerChannel Server creates a session to listen forrequests from the Integration Service or FTP clients. It also uses this session to transfer the files. When youtransfer data between PowerCenter and a remote database, the PowerChannel Server creates a session totransfer the data.

When you run a data transfer session between PowerChannel Servers, the local PowerChannel Server creates aparent session to connect to the remote PowerChannel Server. After the local server connects to the remotePowerChannel Server, the remote server creates a child session. When you transfer data between PowerCenterand a remote database, the PowerChannel Server creates a parent session and a child session for each partitionconfigured in the PowerCenter session properties.

When you transfer data between PowerCenter and a remote database with a single PowerChannel Server, thePowerChannel 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:

¨ You can monitor the status of sessions.

¨ You can stop data transfer sessions.

When you transfer data between PowerChannel Servers, you can also recover failed sessions.

Monitoring PowerChannel Sessions with the Web ClientUse the web client to monitor the status of data transfer sessions. If your user account profile is admin, you canmonitor all data transfer sessions on the PowerChannel Server. If your user account profile is user, you canmonitor sessions you run. To monitor a session for transferring data between PowerCenter and a remotedatabase, you need a user account with the admin profile.

74

When you monitor sessions, the web client displays the following information:

Session Detail Description

Session Name Name of the PowerChannel session.

Session ID PowerChannel session ID.

Account Name Account name of the user who starts the session.

Creation Time Time when PowerChannel creates the session.

Start Time Time when PowerChannel initiates the session.

End Time Time when the session completes successfully or fails. It can also refer to the time when the user stopsthe session.

First Error Msg If you are displaying session information for a failed session, the PowerChannel Server displays thereasons for the session failure.

Session Status PowerChannel Server displays the following messages:- Completed. Displays for all successful sessions.- Failed. Displays for all failed sessions with an error message.- Running. Displays for sessions that are currently running.- Stopped. Displays for sessions you stop.

Channel Name Name of the channel transferring the data. The PowerChannel Server names all channels it creates duringdata transfer. A data transfer session can contain one channel or multiple channels depending on the datatransfer 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.

Channel Status PowerChannel Server displays the following messages:- Completed. Displays for all successful channels.- Failed. Displays for all failed channels.- Running. Displays for channels that are currently running.- Stopped. Displays for channels you stop.

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 stopsthe channel. The channel stops when the user stops the session.

Monitoring PowerChannel Sessions with the Web Client 75

Session Detail Description

ForwardConnection

For file transfer between PowerCenter and an FTP server or between FTP clients and servers, thePowerChannel 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.

Source File Name and path of the source file.

Target File Name and path of the destination file.

Total Bytes toRead

Size of the file in bytes to read from the local PowerChannel Server.

Total Bytes toWrite

Size of the file in bytes to write to the remote PowerChannel Server.

Read Bytes For file transfer between PowerChannel Servers, read bytes is the number of bytes read from the filesystem.For file transfer between PowerCenter and an FTP server or between FTP clients and servers, read bytesis 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 readfrom 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 filesystem.For file transfer between PowerCenter and an FTP server or between FTP clients and servers, writtenbytes 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 byteswritten 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 BlocksCount

Number of packages the local PowerChannel Server sends to the remote PowerChannel Server.

Received Bytes Amount of data in bytes the local PowerChannel Server receives from the remote PowerChannel Server.

Received BlocksCount

Number of packages the local PowerChannel Server receives from the remote PowerChannel Server.

ConnectorSignature

For file transfer between PowerCenter and an FTP server or between FTP clients and servers, thePowerChannel 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 IntegrationService, FTP client, or FTP server when transferring files between PowerCenter and an FTP server orbetween FTP clients and servers.

Written Bytes Amount of data in bytes the PowerChannel Server writes during the connection with the IntegrationService, FTP client, or FTP server when transferring files between PowerCenter and an FTP server orbetween FTP clients and servers.

76 Chapter 8: Managing PowerChannel Sessions

Session Detail Description

Type During file transfer between PowerCenter and an FTP server or between FTP clients and server, thePowerChannel 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 IntegrationService, FTP client, or FTP server when transferring files between PowerCenter and an FTP server orbetween 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 LastAccessed

Last time PowerChannel transferred data to or from the Integration Service, FTP client, or FTP server.

To monitor sessions with the web client:

1. On the Session Management page, use the Session Filter to display sessions

You can filter sessions by the following session properties:

Display SessionsOptions

Description

Session Status Select one of the following filter options:- All Sessions- Running Sessions- Completed Sessions- Failed Sessions- Stopped Sessions

Session Name To display sessions by name, enter the name of the sessions you want to display. Or, use thewildcard character,%, as a suffix in the filter condition. For example, to display sessions thatbegin with the letter “s,” use “s%” for session name.

Sessions for transferring data between PowerCenter and a remote database always use thename 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

The web client displays a list of sessions.

Tip: Click Refresh to view an updated session list.

2. To monitor a particular session, click the session name.

The web client displays the session information for the session.

Monitoring PowerChannel Sessions with the Web Client 77

Stopping Sessions with the Web ClientUse the web client to stop sessions. The PowerChannel Server stops the sessions you indicate and displays amessage. If your user account profile is admin, you can stop any session running on the PowerChannel Server. Ifyour user account profile is user, you can only stop sessions that you run. To stop a session for transferring databetween PowerCenter and a remote database, you must have a user account with the admin profile.

To stop sessions with the web client:

1. On the Session Management page, use the Session Filter to select Running Sessions from the SessionStatus 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.

78 Chapter 8: Managing PowerChannel Sessions

C H A P T E R 9

Recovering PowerChannelSessions

This chapter includes the following topics:

¨ Recovering PowerChannel Sessions Overview, 79

¨ Automatic Recovery, 80

¨ Manual Recovery, 80

¨ Troubleshooting, 81

Recovering PowerChannel Sessions OverviewYou can recover failed data transfer sessions between PowerChannel Servers. When the PowerChannel Serverruns a session in recovery mode, it completes the failed session tasks. The PowerChannel Server reduces thetime required to complete all tasks for a session again and minimizes the time required to re-transfer data.

For example, you use the PcCmd send command to transfer a 100 MB file from a local PowerChannel Server to aremote PowerChannel Server. After transferring 50 MB, the session fails due to an error. When the local serverruns the session in recovery mode, it only transfers the part of the file that it failed to transfer. It starts transferringthe file from the first byte after the 50th megabyte.

When you transfer data between PowerChannel Servers, the local PowerChannel Server creates a parentsession. The remote PowerChannel Server creates a child session. When data transfer fails due to networkfailure, the child session terminates. During recovery, the parent session tries to reconnect to the remotePowerChannel Server. When the connection succeeds, the remote server creates a new child session with a newsession ID to complete the file transfer.

During the recovery session, the parent session communicates with the new child session to determine thenumber 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. ThePowerChannel 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 betweenPowerChannel Servers fails due to network failure.

¨ Manual recovery. If the PowerChannel Server cannot recover a failed file transfer session betweenPowerChannel Servers, you can recover the failed session manually. Before you run manual recovery, checkthe PowerChannel session log and make sure you correct the error that caused the session to fail.

79

Automatic RecoveryPowerChannel lets you recover a data transfer session between PowerChannel Servers when the session failsdue to network failure. For example, you use a file transfer command to transfer a 50 MB file from a localPowerChannel Server to a remote PowerChannel Server. After transferring 45 MB, a network error occurs and thefile 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 PowerChannelconfiguration utility. Use the NUM_AUTO_RECOVERY_ATTEMPTS parameter in the PowerChannel.propertiesfile to set the number of times the PowerChannel Server tries to recover a failed connection betweenPowerChannel Servers. For example, if you set this parameter to 10, the server tries to recover the connection 10times before it fails automatic recovery.

When you run a PowerCenter session to read data from a remote database source or write data to a remotedatabase target with two PowerChannel Servers, and the PowerChannel session fails due to network failure, thePowerCenter session continues to run while the local PowerChannel Server attempts to recover thePowerChannel session based on the NUM_AUTO_RECOVERY_ATTEMPTS configuration in thePowerChannel.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 sessionmanually. When autorecovery fails for a session transferring files between PowerCenter and an FTP server or FTPclients and servers, you must create a session with the PcCmdcreatepipe command and begin data transfer fromthe first byte. When autorecovery fails a for session transferring compressed and encrypted data betweenPowerCenter and a remote database, you must rerun the PowerCenter session.

Manual RecoveryIf the PowerChannel Server cannot recover a failed file transfer session, use the web client to recover the sessionmanually by session ID. For example, you can manually recover a session when the remote server runs out of diskspace.

If your user account profile is admin, you can recover all failed sessions in the PowerChannel repository. If youruser 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. Correctthe errors.

Note: You cannot use manual recovery for a session that transfers data between PowerCenter and an FTP serveror between FTP clients and servers. Also, you cannot use manual recovery for a session that transfers databetween PowerCenter and a remote database.

To manually recover a failed session with the web client:

1. Click the SessionManager tab.

2. On Session Filter, select Failed Sessions from the Session Status list and click Go.

Tip: Click Refresh to view an updated session list.

3. Click the session name to recover the session.

4. Click Recover.

5. Click OK.

80 Chapter 9: Recovering PowerChannel Sessions

Troubleshooting

The file transfer session failed when I specified -T=all in the command and the connection between thePowerChannel Servers failed.

The connection between the PowerChannel Servers failed during data compression. The PowerChannel Servercannot recover the session. Run manual recovery.

Troubleshooting 81

C H A P T E R 1 0

Running PcCmd CommandsThis chapter includes the following topics:

¨ Running PcCmd Commands Overview, 82

¨ Editing the Properties File with PcCmd, 83

¨ Creating Accounts with PcCmd, 83

¨ Displaying Accounts with PcCmd, 86

¨ Editing Accounts with PcCmd, 88

¨ Removing Accounts with PcCmd, 91

¨ Monitoring PowerChannel Sessions with PcCmd, 92

¨ Stopping PowerChannel Sessions with PcCmd, 93

¨ Recovering PowerChannel Sessions with PcCmd, 94

¨ Stopping the Server with PcCmd, 95

Running PcCmd Commands OverviewUse PcCmd to transfer files, run PowerChannel account and session management tasks, and stop thePowerChannel Server. You can also use PcCmd in PowerCenter to read data from flat file sources and write datato flat file targets. This chapter provides information about the PcCmd account and session managementcommands.

PcCmd uses a properties file to run commands. You can use the PcCmd configuration utility to configure PcCmdproperties.

Path Names in PcCmd CommandsComplete the following tasks when you use path names in PcCmd commands:

¨ Use double quotes for path names with spaces.

¨ Use “/” to define path names when transferring files to or from a PowerChannel Server on UNIX.

82

Path Names with SpacesThe PowerChannel Server can locate files or folders with spaces when you enclose them in quotes. Complete oneof the following tasks to specify path names or filenames with spaces:

¨ Use double quotes around the entire filename or path name.

¨ Use double quotes around the folder name that contains spaces.

Path Names for File Transfer Commands on UNIXWhen you transfer files on UNIX, use “/” to define the path of the files. For example, you run PcCmd get on aPowerChannel Server on Windows to transfer the file data1.txt to the admin2 directory. You want to get the filefrom a remote PowerChannel Server on UNIX.

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 remotePowerChannel Server on UNIX, define the path of the destination files with “/”.

Editing the Properties File with PcCmdUse PcCmd config to edit the default values for several PcCmd properties in the properties file with the PcCmdconfiguration utility.

To edit the properties file with PcCmd:

1. Go to the PowerChannel directory.

2. Enter the PcCmdconfig command.

Use the following command syntax to configure the properties file:PcCmd config [-r=<properties_file_name>]

The following table describes the parameter for the PcCmdconfig command:

CommandParameters

Required/Optional

Description

r Optional Enter the name the name of the properties file you want to modify. If you omit theproperties file, the PowerChannel Server opens the default properties file for you toconfigure.

Creating Accounts with PcCmdUse PcCmd commands to create user and certificate accounts. To create a user or certificate account, you musthave a user account with the admin profile.

Editing the Properties File with PcCmd 83

Creating a User Account with PcCmdUse PcCmd to create a user account.

To create a user account with PcCmd:

1. Go to the PowerChannel directory.

2. Enter the PcCmdcreateuser command.

Use the following command syntax to create a user account in the PowerChannel repository:PcCmd createuser [-r=<properties_file_name>] [-u=<user_account_name>] [-p=<user_account_password>] [-S=<server_hostname>[:<server_port>]] -a=<new_account_name> -P=<new_account_password> -l={admin|user|disabled} [-i=<input_folder>] [-o=<output_folder>]

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PcCmd createuser command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the defaultproperties 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 inthe PcCmd.properties file.

p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in thePcCmd.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 casesensitive.

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 remotedatabases.You can also use the $PC_USER and $PC_DATE server variables for the input foldervalue.

o Optional When you transfer files, enter the path of the default output folder for the new useraccount. If the path contains spaces, enclose the path in double quotes.You do not use this parameter when you transfer data between PowerCenter and remotedatabases.You can also use the $PC_USER and $PC_DATE server variables for the output foldervalue.

84 Chapter 10: Running PcCmd Commands

Creating a Certificate Account with PcCmdUse PcCmd to create a certificate account.

To create a certificate account with PcCmd:

1. Go to the PowerChannel directory.

2. Enter the PcCmdcreatecert command.

Use the following command syntax to create a certificate account in the PowerChannel repository:PcCmd createcert [-r=<properties_file_name>] [-u=<user_account_name>] [-p=<user_account_password>] [-S=<server_hostname>[:<server_port>]] -a=<new_account_name> -P=<new_account_password> [-H=<default_IP_address>][-t=<default_port_no>] -l={oneway|twoway} [-i=<input_folder>] [-o=<output_folder>]

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PcCmd createcert command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the defaultproperties 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 inthe PcCmd.properties file.

p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in thePcCmd.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 casesensitive.

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 thenew certificate account. Otherwise, the PowerChannel Server creates the certificateaccount without a default IP address.

t Optional Enter the default port of the PowerChannel Server where you want to register the newcertificate account. Use a port number from 1 to 65535. Otherwise the PowerChannelServer creates the certificate account without a default port.

l Required Enter one of the following values for the certificate account profile:- oneway- twoway

Creating Accounts with PcCmd 85

CommandParameters

Required/Optional

Description

i Optional When you transfer files, enter the path of the default input folder for the new certificateaccount. If the path contains spaces, enclose the path in double quotes.You do not use this parameter when you transfer data between PowerCenter and remotedatabases.You can also use the $PC_USER and $PC_DATE server variables for the input foldervalue.

o Optional When you transfer files, enter the path of the default output folder for the new certificateaccount. If the path contains spaces, enclose the path in double quotes. You do not usethis parameter when you transfer data between PowerCenter and remote databases.You do not use this parameter when you transfer data between PowerCenter and remotedatabases.You can also use the $PC_USER and $PC_DATE server variables for the output foldervalue.

Displaying Accounts with PcCmdYou display user and certificate accounts with PcCmd. If you have a user account with the user profile, you canonly display your own account attributes. If you have a user account with the admin profile, you can display alluser accounts with the user, admin, or disabled profile. You can also display certificate accounts or filter specificaccounts for display.

Displaying User Accounts with PcCmdUse PcCmd to display a list of user accounts in the PowerChannel repository. When you display a user account,you view the following account attributes:

¨ Account name. The name of the account.

¨ Account type. The account type is user account.

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

To display a list of user accounts with PcCmd:

1. Go to the PowerChannel directory.

2. Enter the PcCmd displayuser command.

Use the following command syntax to display a list of accounts in the PowerChannel repository:PcCmd displayuser [-r=<properties_file_name>] [-u=<user_account_name>] [-p=<user_account_password>] [-S=<server_hostname>[:<server_port>]] [-F=<filter>]

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

86 Chapter 10: Running PcCmd Commands

The following table describes the parameters for the PcCmd displayuser command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the defaultproperties 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 inthe PcCmd.properties file.

p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in thePcCmd.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 user account name filter.When you use the user account name filter, use the following guidelines:- Use only one entry in the user account name filter.- Use the user account name or the wildcard character, %, in the user account name

filter. Use the wildcard character as a suffix in the filter condition. For example, todisplay user account names that begin with the letter “a,” use the following commandsyntax to filter the accounts list:PcCmd displayuser -u=admin -p=test -F=a%

Displaying Certificate Accounts with PcCmdUse PcCmd to display a list of certificate accounts in the PowerChannel repository. You can view the followingaccount attributes:

¨ Account name. Name of the account.

¨ Account type. Account type is certificate account.

¨ Account profile. Account profiles for certificate accounts are oneway and twoway.

¨ Default server address. Default IP address of the local PowerChannel Server.

¨ Default server port. 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.

To display a list of certificate accounts with PcCmd:

1. Go to the PowerChannel directory.

2. Enter the PcCmd displaycert command.

Use the following command syntax to display a list of accounts in the PowerChannel repository:PcCmd displaycert [-r=<properties_file_name>] [-u=<user_account_name>] [-p=<user_account_password>] [-S=<server_hostname>[:<server_port>]] [-F=<filter>]

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

Displaying Accounts with PcCmd 87

The following table describes the parameters for the PcCmd displaycert command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the defaultproperties 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 inthe PcCmd.properties file.

p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in thePcCmd.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, todisplay certificate account names that begin with the letter “a,” use the followingcommand syntax to filter the accounts list: PcCmd displaycert -u=admin -p=test -F=a%

Editing Accounts with PcCmdYou can edit PowerChannel user and certificate accounts with PcCmd. If you have a user account with the userprofile, you can only change account attributes for your own account. If you have a user account with the adminprofile, you can change account attributes for any user account with the user, admin, or disabled profile. You canalso edit any certificate account. When editing your own account, you cannot change your own account profile.

Editing a User Account with PcCmdUse PcCmd to edit user account attributes in the PowerChannel repository. You can edit the following useraccount attributes:

¨ Password. The password for the user account.

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

To edit a user account with PcCmd:

1. Go to the PowerChannel directory.

2. Enter the PcCmd edituser command.

Use the following command syntax to edit a user account in the PowerChannel repository:PcCmd edituser [-r=<properties_file_name>] [-u=<user_account_name>] [-p=<user_account_password>] [-S=<server_hostname>[:<server_port>]]

88 Chapter 10: Running PcCmd Commands

-a=<account_name_to_edit> [-P=<new_account_password>] [-l={admin|user|disabled}] [-i=<new_input_folder>] [-o=<new_output_folder>]

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PcCmd edituser command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the defaultproperties 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 inthe PcCmd.properties file.

p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in thePcCmd.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.

P Optional Enter a password of at least three characters for the account.

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 pathcontains spaces, enclose the path in double quotes.You can also use the $PC_USER and $PC_DATE server variables for the input foldervalue.

o Optional Use this option to change the default output folder path for the user account. If the pathcontains spaces, enclose the path in double quotes.You can also use the $PC_USER and $PC_DATE server variables for the output foldervalue.

Tip: To remove default account attributes, leave the command parameter for the attribute blank. For example, toremove the default input folder, enter -i=. For user accounts, you can remove the default attributes for the inputfolder and output folder.

Editing a Certificate Account with PcCmdUse PcCmd to edit certificate account attributes in the PowerChannel repository. You can edit the followingcertificate account attributes:

¨ Default IP address. The default IP address of the local PowerChannel Server.

¨ Default port. The default port number of the local PowerChannel Server.

¨ Default input folder. The default folder for input data files during file transfer.

Editing Accounts with PcCmd 89

¨ Default output folder. The default folder for output data files during file transfer.

¨ Profile. The certificate account profile. User account profiles are oneway and twoway.

Note: You cannot change the password for a certificate account.

To edit a certificate account with PcCmd:

1. Go to the PowerChannel directory.

2. Enter the PcCmd editcert command.

Use the following command syntax to edit a certificate account in the PowerChannel repository:PcCmd editcert [-r=<properties_file_name>] [-u=<user_account_name>] [-p=<user_account_password>] [-S=<server_hostname>[:<server_port>]] -a=<account_name_to_edit> [-H=<new_default_IP_address>] [-t=<new_default_port_no>] [-l={oneway|twoway}] [-i=<new_input_folder>] [-o=<new_output_folder>]

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PcCmd editcert command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the defaultproperties 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 inthe PcCmd.properties file.

p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in thePcCmd.properties file.

S Optional Enter the host name or IP address and port number of the local PowerChannel Server. Ifyou omit this parameter, PcCmd uses the PowerChannel Server in the PcCmd.propertiesfile.

a Required Enter the name of the account you want to edit.

H Optional Changes the default IP address for the PowerChannel Server where you want to registerthe certificate account.

t Optional Changes the default port for the PowerChannel Server where you want to register thecertificate 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 containsspaces, enclose the path in double quotes.You can also use the $PC_USER and $PC_DATE server variables for the input foldervalue.

o Optional Changes the default output folder path for the certificate account. If the path containsspaces, enclose the path in double quotes.You can also use the $PC_USER and $PC_DATE server variables for the output foldervalue.

90 Chapter 10: Running PcCmd Commands

Tip: To remove default attributes for an account, leave the command parameter for the attribute blank. Forexample, to remove the default port, enter -t=. For certificate accounts, you can remove the default attributes forthe following account parameters: IP address, port, input folder, and output folder.

Removing Accounts with PcCmdYou can remove user accounts with the user, admin, or disabled profile with PcCmd. You can also removecertificate accounts with PcCmd. To remove user and certificate accounts, you must have a user account with theadmin profile. You cannot remove your own account.

Removing a User Account with PcCmdUse PcCmd to remove a user account with the user, admin, or disabled profile with PcCmd from thePowerChannel repository.

To remove a user account with PcCmd:

1. Go to the PowerChannel directory.

2. Enter the PcCmd removeuser command.

Use the following command syntax to remove a user account:PcCmd removeuser [-r=<properties_file_name>] [-u=<user_account_name>][-p=<user_account_password>] [-S=<server_hostname>[:<server_port>]] -a=<account_name_to_remove>

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PcCmd removeuser command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the defaultproperties 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 inthe PcCmd.properties file.

p Optional Enter the password for the user account. Otherwise, the PowerChannel Server looks forthe default password in the PcCmd.properties file.

S Optional Enter the host name or IP address and port number of the local PowerChannel Server. Ifyou omit this parameter, PcCmd uses the PowerChannel Server in the PcCmd.propertiesfile.

a Required Enter the name of the user account you want to remove.

Removing Accounts with PcCmd 91

Removing a Certificate Account with PcCmdUse PcCmd to remove a certificate account from the PowerChannel repository.

To remove a certificate account with PcCmd:

1. Go to the PowerChannel directory.

2. Enter the PcCmd removecert command.

Use the following command syntax to remove a certificate account:PcCmd removecert [-r=<properties_file_name>] [-u=<user_account_name>][-p=<user_account_password>] [-S=<server_hostname>[:<server_port>]] -a=<account_name_to_remove>

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PcCmd removecert command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the defaultproperties 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 inthe PcCmd.properties file.

p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in thePcCmd.properties file.

S Optional Enter the host name or IP address and port number of the local PowerChannel Server. Ifyou omit this parameter, PcCmd uses the PowerChannel Server in the PcCmd.propertiesfile.

a Required Enter the name of the certificate account you want to remove.

Monitoring PowerChannel Sessions with PcCmdUse PcCmd to monitor the status of PowerChannel data transfer sessions. If your user account profile is admin,you can monitor all data transfer sessions on the PowerChannel Server. If your user account profile is user, youcan only monitor the PowerChannel sessions you run. To monitor a session for transferring data between theIntegration Service and a remote database, you must have a user account with the admin profile.

To monitor PowerChannel sessions with PcCmd:

1. Go to the PowerChannel directory.

2. Enter the PcCmd monitor command.

Use the following command syntax to monitor PowerChannel sessions:PcCmd monitor [-r=<properties_file_name>] [-u=<user_account_name>] [-p=<user_account_password>] [-S=<server_hostname>[:<server_port>]] {-fi=<session_id1>[;<session_id2>]*|-a|[-fn=<session_name>] [-fs=<session_status>] [-fa=<session_owner_account_name>]}

92 Chapter 10: Running PcCmd Commands

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PcCmd monitor command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the defaultproperties 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 inthe PcCmd.properties file.

p Optional Enter the password for the user account.Otherwise, PcCmd looks for it in thePcCmd.properties file.

S Optional Enter the host name or IP address and port number of the local PowerChannel Server. Ifyou omit this parameter, PcCmd uses the PowerChannel Server in the PcCmd.propertiesfile.

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 sessionID, you can also use a combination filters. When you use more than one filter, thePowerChannel 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 allsessions 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 theletter “a,” use-fn=a%.

Stopping PowerChannel Sessions with PcCmdUse PcCmd to stop PowerChannel sessions by session ID, session name, or stop all sessions. The PowerChannelServer stops the PowerChannel sessions you indicate and displays a message. If your user account profile isadmin, you can stop any session running on the PowerChannel Server. If your user account profile is user, youcan only stop PowerChannel sessions that you run. To stop a session for transferring data between the IntegrationService and a remote database, you must have a user account with the admin profile.

To stop PowerChannel sessions with PcCmd:

1. Go to the PowerChannel directory.

2. Enter the PcCmd stop command.

Stopping PowerChannel Sessions with PcCmd 93

Use the following command syntax to stop PowerChannel sessions:PcCmd stop [-r=<properties_file_name>] [-u=<user_account_name>] [-p=<user_account_password>] [-S=<server_hostname>[:<server_port>]] {-fi=<session_id1>[;<session_id2>]*|-a|[-fn=<session_name>] [-fa=<session_owner_account_name>]}

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PcCmdstop command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the defaultproperties 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 inthe PcCmd.properties file.

p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in thePcCmd.properties file.

S Optional Enter the host name or IP address and port number of the local PowerChannel Server. Ifyou omit this parameter, PcCmd uses the PowerChannel Server in the PcCmd.propertiesfile.

fi | fn | fa | a Required Filter options to stop PowerChannel sessions running on the PowerChannel Server. Use asingle filter or a combination of filters. When you use more than one filter, thePowerChannel 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 theletter “a,” use -fn=a%.

Recovering PowerChannel Sessions with PcCmdUse PcCmd to manually recover failed PowerChannel file transfer sessions. You recover PowerChannel sessionsby session ID. Before you run the PcCmd recover command, see the PowerChannel session log to determine thecause of the session failure. Correct the errors and then recover the PowerChannel session manually with thePcCmd recover command.

Note: You cannot use manual recovery for a PowerChannel session to transfer data between PowerCenter and aremote database.

94 Chapter 10: Running PcCmd Commands

To recover a PowerChannel session manually:

1. Go to the PowerChannel directory.

2. Enter the PcCmd recover command.

Use the following command syntax to recover a failed PowerChannel session manually:PcCmd recover [-r=<properties_file_name] [-u=<user_account_name>][-p=<user_account_password>] [-S=<server_hostname>[:<server_port>]] -s=<session_id>

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PcCmd recover command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the defaultproperties 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 inthe PcCmd.properties file.

p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in thePcCmd.properties file.

S Optional Enter the host name or IP address and port number of the local PowerChannel Server. Ifyou omit this parameter, PcCmd uses the PowerChannel Server in the PcCmd.propertiesfile.

s Required Enter the session ID for the PowerChannel session you want to recover.

Stopping the Server with PcCmdUse PcCmd to stop the local PowerChannel Server. When you run the command to stop the PowerChannelServer, it runs a PowerChannel session to stop the server and logs the session information in the system log. Youmust have a user account with the admin profile to stop the PowerChannel Server.

Note: You cannot stop the PowerChannel Server from the PowerChannel command line.

To stop the PowerChannel Server with PcCmd:

1. Go to the PowerChannel directory.

2. Enter the PcCmd stopserver command.

Use the following command syntax to stop the PowerChannel Server:PcCmd stopserver [-r=<properties_file_name>] [-u=<user_account_name>] [-p=<user_account_password>] [-S=<server_hostname>[:<server_port>]]

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

Stopping the Server with PcCmd 95

The following table describes the parameters for the PcCmd stopserver command:

CommandParameters

Required/Optional

Description

r Optional Enter the name and path of the PcCmd.properties file. Otherwise, PcCmd uses the defaultproperties 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 inthe PcCmd.properties file.

p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in thePcCmd.properties file.

S Optional Enter the host name or IP address and port number of the local PowerChannel Server. Ifyou omit this parameter, PcCmd uses the PowerChannel Server in the PcCmd.propertiesfile.

96 Chapter 10: Running PcCmd Commands

C H A P T E R 1 1

Working with XML Command FilesThis chapter includes the following topics:

¨ Working with XML Command Files Overview, 97

¨ Creating an XML Command File, 97

¨ Running an XML Command File, 100

¨ XML Command File Example, 101

Working with XML Command Files OverviewYou can run PowerChannel commands from an XML command file. Use an XML command file to transfer data,run commands on machines hosting remote PowerChannel Servers, and run operating system commands on themachine hosting the local PowerChannel Server. After you create the command structure in an XML command file,use the PcCmd run command to run the XML command file.

Running commands from an XML command file provides more flexibility in creating a command structure. Whenyou use a PcCmd command from the command line, you can only run one command at a time. You can runmultiple commands from the same XML command file. For example, you can run a batch of PowerChannel taskssequentially.

The command syntax you use in an XML command file differs from the PcCmd command syntax. For XMLcommand usage and syntax, see the PC.dtd file in the PowerChannel installation directory. The PowerChannelServer parses the XML command file with the PC.dtd file.

Creating an XML Command FileYou can create an XML command file with any tool that lets you create an XML file. Save the command file withan .xml extension.

Use an XML command file to complete the following tasks:

¨ FileTransfer. Transfers files between PowerChannel Servers.

¨ 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 thiscommand 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 PowerChannelServers. You can transfer multiple files to multiple servers with an XML command file. You can also use a singleXML command file to run several file transfer commands. For example, you want to send five different files to fiveseparate servers. You also want to use different levels of compression and encryption for each file. Use a singleXML 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, enterthe 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 PowerChannelServers, avoid overwriting existing files. Make sure files you transfer do not use the same name. Or, you can putthe files into separate directories according to the server you get the files from. Use the FileNamePair commandelement 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 toconnect 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:

CommandElements

Required/Optional

Description

Checksum Optional Enter yes to enable checksum for data integrity during the file transfer. Enter no todisable checksum.

HostInfo Required Enter the certificate account name, IP address, and port for the remote PowerChannelServer.

FileNamePair Required Enter the local and remote filenames. The local filename is the name of the source fileyou want to transfer. The remote filename is the name of the target file. If you do notenter a remote filename, the PowerChannel Server writes the source file to the targetwith the same name as the source file. You cannot use an absolute path with the remotefilename.To transfer multiple files with the same channel information, enter a separateFileNamePair 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 thisexample, the files data1.txt and data2.txt are being transferred with an encryption level of 3 and a compressionlevel 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>

98 Chapter 11: Working with XML Command Files

Executing Operating System Commands (ExternalExecute)Use an XML command file to run operating system commands on the PowerChannel Server. For example, youcan delete a file from the local PowerChannel Server after transferring it to the remote PowerChannel Server.

To run operating system commands on the PowerChannel Server, the RUN_EXTERNAL_EXECUTE property mustbe set to all or admin. If RUN_EXTERNAL_EXECUTE is set to all, user accounts with the user or admin profilecan run external operating system commands. If RUN_EXTERNAL_EXECUTE is set to admin, only user accountswith the admin profile can run external operating system commands.

The following table describes the command elements for the ExternalExecute XML command:

Command Elements Required/Optional

Description

ExecutorType Required Enter OS.

CommandLine Required Enter the external command syntax. Use operating system specific commandsyntax.

RecoverCommandLine Optional Use this parameter if you want PowerChannel to run a different external commandduring 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>

Executing Commands on a Remote PowerChannel Server(RemoteExecute)

Use an XML command file to run commands on a remote PowerChannel Server. For example, you can monitorsessions running on a remote PowerChannel Server. Or, you can execute operating system commands from aremote PowerChannel Server.

To run commands on a remote PowerChannel Server, set TRUST_REMOTE_EXECUTE to yes with thePowerChannel configuration utility on the machine hosting the remote PowerChannel Server.

The following table describes the command elements for the RemoteExecute XML command:

Command Elements Required/Optional

Description

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.

Creating an XML Command File 99

The following example shows an XML file for monitoring sessions running on a remote PowerChannel Server:

<?xml version='1.0' encoding='us-ascii' ?> <XMLRequest Wait="no"> <XMLCmd> <RemoteExecute Account="PowerChannel1" IPAddress="208.200.214.000" PortNo="7000"> <XMLRequest Wait="no"> <XMLCmd> <ExternalExecute ExecutorType="OS" CommandLine="cmd /c del C:\data1.txt"/> </XMLCmd> </XMLRequest> </RemoteExecute> </XMLCmd> </XMLRequest>

Running an XML Command FileYou can run an XML command file from the PcCmd command line.

To run an XML command file:

1. Go to the PowerChannel directory.

2. Enter the PcCmd run command.

Use the following syntax with the PcCmd run command:PcCmd run [-r=<properties_file_name>] [-u=<user_acount_name>] [-p=<user_account_password>] [-S=<server_hostname>[:<server_port>]] [-sn=<session_name>] -x=<xml_file>

The parameters enclosed in [ ] are optional. The input values for the parameters are enclosed in < >. Valuesin the format {x|y} represent the options you can use for the command parameter. Parameters followed by anasterisk (*) can contain multiple values.

The following table describes the parameters for the PcCmd run command:

CommandParameters

Required/Optional

Description

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 inthe PcCmd.properties file.

p Optional Enter the password for the user account. Otherwise, PcCmd looks for it in thePcCmd.properties file.

S Optional Enter the host name or IP address and port number of the local PowerChannel Server. Ifyou omit this parameter, PcCmd uses the default server defined in the PcCmd.propertiesfile.

sn Optional Enter a name for the session if you are running a FileTransfer command in the XMLcommand file. If you do not enter a name for the session, PcCmd assigns a name for thesession 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 containsspaces, enclose the path in double quotes.

100 Chapter 11: Working with XML Command Files

XML Command File ExampleYou can complete a variety of PowerChannel tasks from a single XML command file. For example, with an XMLcommand file you can use multiple file transfer commands from the same XML file. You can also use operatingsystem commands in conjunction with PcCmd file transfer commands in the XML command file.

For example, you want to create an XML file that lets you complete the following tasks:

¨ Send data1.txt to PowerChannel1 with compression at level 3 and encryption at level 3.

¨ Send data2.txt to PowerChannel2 with staging at both the sending and receiving PowerChannel and encryptionat level 3.

¨ Get data3.txt from PowerChannel3 with staging at the receiving PowerChannel and encryption at level 1.

¨ Remove data1.txt and data2.txt from the local PowerChannel Server.

Create an XML command file with the following command syntax:

<?xml version='1.0' encoding='us-ascii' ?> <XMLRequest Wait="no"> <XMLCmd> <FileTransfer> <HostInfo Account="PowerChannel1" IPAddress="208.200.214.100" PortNo="7000"/> <FilenamePair LocalFilename ="c:\data1.txt" RemoteFilename="data1.txt"/> <ChannelInfo> <LocalChannelInfo ChannelType="WRITESTREAM"> <Transformer Type="COMPRESSOR" Param="3"/> <Transformer Type="ENCRYPTOR" Param="3"/> </LocalChannelInfo> <RemoteChannelInfo ChannelType="READSTREAM"> <Transformer Type="DECOMPRESSOR"/> <Transformer Type="DECRYPTOR"/> </RemoteChannelInfo> </ChannelInfo> </FileTransfer> </XMLCmd> <XMLCmd> <FileTransfer> <HostInfo Account="PowerChannel2" IPAddress="208.200.218.100" PortNo="7000"/> <FilenamePair LocalFilename ="c:\data2.txt" RemoteFilename="data2.txt"/> <ChannelInfo> <LocalChannelInfo ChannelType="COMPRSTAGE"/> <LocalChannelInfo ChannelType="WRITESTREAM"> <Transformer Type="ENCRYPTOR" Param="3"/> </LocalChannelInfo> <RemoteChannelInfo ChannelType="READSTREAM"> <Transformer Type="DECRYPTOR"/> </RemoteChannelInfo> <RemoteChannelInfo ChannelType="DECOMPRSTAGE"/> </ChannelInfo> </FileTransfer> </XMLCmd> <XMLCmd> <FileTransfer> <HostInfo Account="PowerChannel3" IPAddress="208.205.210.100" PortNo="7000"/> <FilenamePair LocalFilename ="c:\data3.txt" RemoteFilename= "data3.txt"/> <ChannelInfo> <LocalChannelInfo ChannelType="READSTREAM"> <Transformer Type="STAGECOMPRESSOR"/> <Transformer Type="ENCRYPTOR" Param="1"/> </LocalChannelInfo> <RemoteChannelInfo ChannelType="WRITESTREAM"> <Transformer Type="DECRYPTOR"/> </RemoteChannelInfo> <RemoteChannelInfo ChannelType="DECOMPRSTAGE"/> </ChannelInfo> </FileTransfer> </XMLCmd> <XMLCmd> <ExternalExecute ExecutorType="OS" CommandLine="cmd /c del c:\data1.txt c:\data2.txt"/>

XML Command File Example 101

</XMLCmd> </XMLRequest>

102 Chapter 11: Working with XML Command Files

A P P E N D I X A

PowerChannel Error MessagesThis appendix includes the following topics:

¨ PowerChannel Messages, 103

¨ Common Messages, 124

¨ PcCmd Messages, 132

¨ Client Common Messages, 133

PowerChannel MessagesThe PowerChannel Server displays messages when there is an error in the PowerChannel command. Messagesappear in the PowerChannel Server and session log files for the current instance of the session.

There are several types of PowerChannel messages:

¨ General messages

¨ Server messages

¨ Session messages

¨ Repository messages

General MessagesGeneral messages display when you encounter errors related to the server, session, or the repository.

10002 An unexpected condition occurred when connecting to remote server(account@hostname:port): <error message>.

Explanation: Network error.

User Response: Run the command again to connect to the remote PowerChannel Server.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

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

10005 Closing stream error: <error message>.Explanation: An I/O error occurred while closing the stream.

User Response: Check the network connection between the remote and local PowerChannel Servers.

10009 <filename> session log file close error: <error message>.Explanation: There is an error in closing the session log file. This is an operating system error. The system

may have run out of disk space.

User Response: Contact the internal technical support.

10010 Error closing the network connection for the session.Explanation: The PowerChannel Server encountered an error closing the network for the session due to

network error.

User Response: Check the network connection.

Server MessagesServer messages result from PowerChannel Server errors.

20013 Invalid listener port number (should be 1 to 65535).Explanation: The listener port number for the PORT parameter in the PowerChannel.properties file is

invalid. Or, the port number for the PORT attribute in the ACTIVE_LISTENERS property inthe PowerChannel.properties file is invalid.

User Response: Enter a valid listener port number from 1 to 65535 in the with the PowerChannel configurationutility.

20014 The <port> for <listener> is in use by another application.Explanation: You assigned a listener port for the PowerChannel Server that is unavailable.

User Response: Use a different port for the PowerChannel Server.

20015 Invalid administrator password (-p option).Explanation: The password that does not match the password for the account in the command.

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 theproperty when you installed the PowerChannel Server. For example, if the value for theCRYPTOGRAPHY property was JSAFE/3DES when you installed the PowerChannel Server,verify that JSAFE/3DES is the current value for the property.

20016 Listener failed: <error message>.Explanation: The PowerChannel Server listener failed.

104 Appendix A: PowerChannel Error Messages

User Response: Check the PowerChannel Server log file for more information. Or, contact Informatica GlobalCustomer Support.

20017 Cannot load session information from repository: <error message>.Explanation: The PowerChannel Server cannot read the session information from the repository. The

repository might contain inconsistencies.

User Response: Restore the repository from backup. If you have no repository backup, contact InformaticaGlobal Customer Support.

20018 Certificate account profile (-l option) is not specified.Explanation: You did not enter the -l parameter for the certificate account profile in the PowerChannel

import command.

User Response: Enter a valid certificate account profile with the -l parameter in the PowerChannel importcommand. Valid certificate account profiles are oneway and twoway.

20019 Cannot read XML DTD file: <filename>.Explanation: The XML command parser cannot read the PC.dtd file.

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.

20021 Cannot spawn session: <error message>.Explanation: The PowerChannel Server cannot spawn the session. Or, internal error.

User Response: Check the PowerChannel Server log file for more information.

20022 Cannot accept connection: <error message>.Explanation: The PowerChannel Server cannot accept the connection with a client or a remote

PowerChannel Server. This is an operating system error.

User Response: Check the PowerChannel Server log file for more information. Or, check the PowerChannelServer network settings.

20023 Server could not be stopped: <error message>.Explanation: The PowerChannel Server could not stop properly due to an error.

User Response: Check the PowerChannel Server and session log files for a related message.

20024 Server execution failed: <error message>.Explanation: The PowerChannel Server failed.

User Response: Check the PowerChannel Server log file for more information.

20025 Certificate account import failed: <error message>.Explanation: The PowerChannel Server failed to import a certificate file for the certificate account.

PowerChannel Messages 105

User Response: Check the additional error message to determine the reason for the command failure. Or,check the PowerChannel Server log file for more information.

20026 Repository reencryption failed: <error message>.Explanation: The PowerChannel Server failed to change the password for the administrator account.

User Response: Restore the repository from backup. If you have no repository backup, contact InformaticaGlobal 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 PowerChannelconfiguration utility.

20029 Invalid value for TOTAL_CHANNEL_MEMORY property: <value> (should be 1,000,000 to1,000,000,000).

Explanation: You entered the wrong value for TOTAL_CHANNEL_MEMORY in thePowerChannel.properties file. The PowerChannel Server replaces the invalid value with adefault value.

User Response: Enter a value for TOTAL_CHANNEL_MEMORY from 1000000 to 100000000 with thePowerChannel configuration utility.

20032 Invalid compression level: <level> (should be 1 to 9 or none).Explanation: You entered the wrong compression level for the COMPRESSOR transformer in the XML

command.

User Response: Enter a compression level from 1 to 9 or none for the COMPRESSOR transformer.

20034 Invalid encryption mode: <encryption mode> (should be 1 to 3 or none).Explanation: You entered a wrong encryption value for the ENCRYPTOR transformer in the XML

command.

User Response: Enter an encryption level from 1 to 3 or none for the ENCRYPTOR transformer.

20035 Invalid port value: <value> (should be 1 to 65535).Explanation: You entered the wrong value for the port number in the PowerChannel.properties file.

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.

20038 Certificate filename (-c option) is not specified.Explanation: You did not enter the -c parameter for the certificate filename in the PowerChannel import

command.

User Response: Check the command parameters and enter a certificate filename with the -c parameter.

106 Appendix A: PowerChannel Error Messages

20039 Server internal error. XML Fragmenter was not loaded for tag: <tag name>.Explanation: Installation error.

User Response: Check the PowerChannel installation for errors. If the installation fails, contact InformaticaGlobal Customer Support.

20040 Session <session name> has failed: <error message>.Explanation: The session failed.

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 numberof auto recovery attempts, in the PowerChannel.properties file.

User Response: Enter a value for NUM_AUTO_RECOVERY_ATTEMPTS from 0 to 1000 with thePowerChannel configuration utility.

20045 Unable to start server. The session repository is corrupt.Explanation: The PowerChannel Server cannot start because it cannot load repository objects. The

repository contains inconsistencies.

User Response: Restore the repository from backup. If you have no repository backup, contact InformaticaGlobal Customer Support.

Explanation: The repository does not exist.

User Response: Create a repository with the PowerChannel init command. For more information, enterPowerChannel init-help at the command line.

20046 Server failed for an unknown reason: <error message>.Explanation: The PowerChannel Server failed for an unknown reason.

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 InformaticaGlobal Customer Support.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

20048 Cannot remove session log file <filename>.Explanation: The PowerChannel Server cannot remove the session log file during repository purging. This

is probably an operating system error.

User Response: Check the operating system user privileges.

PowerChannel Messages 107

20049 Wrong value for the max count of sessions allowed for monitoring: <number> (should be 10to 10000).

Explanation: You entered a wrong value for MAX_SESSIONS_MONITORED, the maximum number ofsessions allowed for monitoring, in the PowerChannel.properties file.

User Response: Enter a value for MAX_SESSIONS_MONITORED from 10 to 10000 with the PowerChannelconfiguration utility.

20051 Admin account profile is not allowed for import operation.Explanation: You entered admin as the account profile for a certificate account in the PowerChannel

import command.

User Response: Enter a valid certificate account profile with the -l parameter. Valid certificate account profilesare oneway and twoway.

20053 Server starting error: <error message>.Explanation: Error starting the PowerChannel Server.

User Response: Check the additional error message for more information. Start the PowerChannel Serveragain.

20054 Session <session name> (ID=<session ID>) has failed.Explanation: The session failed.

User Response: Check the detailed message in the session log file.

20055 Property password decryption error: <error message>.Explanation: The PowerChannel Server cannot decrypt the encrypted password in the

PowerChannel.properties file. The password might be corrupt.

User Response: Reencrypt the password with the PcPassword utility.

20057 Server repository is locked.Explanation: You attempted to start another instance of the PowerChannel Server. A PowerChannel user

may not have properly stopped the server.

User Response: Verify that no other PowerChannel user is using the repository. Unlock the repository beforestarting the PowerChannel Server. To remove the repository lock, run the PowerChannelunlock command.

20060 Repository unlocking failed: <error message>.Explanation: The PowerChannel unlock command failed.

User Response: Check the PowerChannel Server log file for more information.

20061 Wrong value for the maximum number of concurrently running sessions: <number> (shouldbe 1 to 10000).

Explanation: You entered a wrong value for MAX_CONCURRENT_RUNNING_SESSIONS in thePowerChannel.properties file.

User Response: Enter a value for MAX_CONCURRENT_RUNNING_SESSIONS from 1 to 10000 with thePowerChannel configuration utility.

108 Appendix A: PowerChannel Error Messages

20062 The value provided for maximum number of concurrent sessions(MAX_CONCURRENT_RUNNING_SESSIONS=<number>) is greater than maximum sessionsallowed in the repository (MAX_SESSIONS_MONITORED=<number>).

Explanation: You entered a wrong value for MAX_CONCURRENT_RUNNING_SESSIONS in thePowerChannel.properties file.

User Response: Check the PowerChannel.properties file and enter a valid number forMAX_CONCURRENT_RUNNING_SESSIONS. This value must be less than the maximumnumber of sessions that can be saved in the repository. To determine the maximum numberof sessions that can be saved in the repository, check the value of theMAX_SESSIONS_MONITORED parameter in the PowerChannel.properties file with thePowerChannel 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.

20064 User account profile is not allowed for certificate accounts.Explanation: You did not enter a valid certificate account profile.

User Response: Enter a valid certificate account profile. Valid certificate account profiles are oneway andtwoway.

20065 Disabled account profile is not allowed for certificate accounts.Explanation: You entered a disabled as the account profile for a certificate account.

User Response: Enter a valid certificate account profile with the -l parameter. Valid certificate account profilesare oneway and twoway.

20067 The property <property> is not specified in the properties file.Explanation: The PowerChannel Server cannot find the default value for the parameter in the

PowerChannel.properties file.

User Response: Check the PowerChannel.properties file for the parameter with the PowerChannelconfiguration utility. Verify the spelling of the parameter.

20068 ExternalExecute task is disabled.Explanation: You cannot run operating system tasks with the ExternalExecute command. To run operating

system tasks, the RUN_EXTERNAL_EXECUTE parameter must be set to all or admin.

User Response: Check the RUN_EXTERNAL_EXECUTE parameter in the PowerChannel.properties file withthe PowerChannel configuration utility. Enter “all” to allow all users to run external commandson the local PowerChannel Server. Or, enter “admin” to only allow users with the useraccount 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 thePowerChannel.properties file.

PowerChannel Messages 109

User Response: Enter a valid RUN_EXTERNAL_EXECUTE value with the PowerChannel configuration utility.Valid values for the RUN_EXTERNAL_EXECUTE property are all, admin, and none.

20071 Cannot open session log file <filename>: <error message>.Explanation: PowerChannel could not open the session log 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, checkthe USERNAME parameter in the PowerChannel.properties file. Verify that there is a validuser 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 thePASSWORD parameter in the PowerChannel.properties file with the PowerChannelconfiguration utility.

20077 Command <command> cannot be run in a parent session.Explanation: You entered an invalid command in an XML command file.

User Response: Enter a valid command in the XML command file.

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

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, enterPcCmd createpipe -help at the command line.

20081 An unexpected header sequence number was received. Expected: <header sequencenumber>. Received: <header sequence number>.

Explanation: The PowerChannel Server received an unexpected header sequence number in the PIPEchannel. The header may be corrupt. Or, data blocks were lost.

User Response: Start a session by running the PcCmd createpipe command. For more information, enterPcCmd createpipe -help at the command line.

20083 Invalid local filename: <filename>.Explanation: You provided an invalid filename for the -f parameter in the PcCmdsend command.

110 Appendix A: PowerChannel Error Messages

User Response: Verify the name of the file you want to transfer. Enter the filename with the -f parameter in thecommand.

20084 Invalid remote filename: <filename>.Explanation: You provided an invalid filename for the -f parameter in the PcCmdget command.

User Response: Verify the name of the file you want to transfer. Enter the filename with the -f parameter in thecommand.

20089 Session spawning was interrupted.Explanation: The PowerChannel Server cannot start the session for the command. A PowerChannel

administrator may have stopped the PowerChannel Server.

User Response: Restart the PowerChannel Server. Run the command again.

20090 No listener is specified.Explanation: There is no port number for the PORT or ACTIVE_LISTENERS property in the

PowerChannel.properties file. As a result, the PowerChannel Server cannot start.

User Response: Enter a port number for the PORT attribute in the ACTIVE_LISTENERS property with thePowerChannel configuration utility.

20091 IP address cannot be determined from hostname <hostname>.Explanation: The host name is invalid.

User Response: Provide a valid hostname.

20093 Listener <listener> failed to bind port <port>.Explanation: You assigned a listener port that is unavailable.

User Response: Use a different port.

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 attributein the ACTIVE_LISTENERS property.

User Response: Verify that you entered the filter correctly with the PowerChannel configuration utility.

20095 <listener> cannot accept connection from <hostname:port> because communication isrestricted to secured protocol only.

Explanation: The protocol for the PROTOCOL attribute in the ACTIVE_LISTENERS property is set togeneric.

User Response: Set the PROTOCOL attribute to encrypted with the PowerChannel configuration utility.

20096 Filter <filter> is invalid.Explanation: The value for the FILTER attribute in the ACTIVE_LISTENERS property is invalid. The IP

address or filter may not be correct.

User Response: Enter a valid IP address. For example, enter 127.0.0.1. Or, enter a valid subnet filter with thePowerChannel configuration utility. For example, enter 255.255.0.0.

PowerChannel Messages 111

20098 Protocol type <type> is invalid. Should be encrypted or generic.Explanation: The protocol type for the PROTOCOL attribute in the ACTIVE_LISTENERS property is set to

a value other than encrypted or generic.

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.

20100 Listener <listener> failed to bind port <IP address:port>.Explanation: The PowerChannel Server could not use the specified port to listen for requests from remote

clients. They port may be in use by another application.

User Response: Make sure that the port is not in use by another application. Or, enter a port that is not in useby another application.

Session MessagesSession error messages refer to errors resulting from the current PowerChannel session.

30036 All output network connections are closed.Explanation: The PowerChannel Server was transferring files in broadcast mode with more than one

remote PowerChannel Server receiving the same file. During file transfer, all networkchannels failed, causing all output network connections to close.

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 nameand 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 forthe 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 accountwith the admin profile to complete the task. Or, verify the PROFILE attribute for theACTIVE_LISTENERS property with the PowerChannel configuration utility.

30038 Undefined channel type: <channel type>.Explanation: The PowerChannel Server cannot recognize the channel type.

User Response: Check the channel type.

30039 Invalid data transformer type: <data transformer type>.Explanation: PowerChannel cannot recognize the specified data transformer type.

User Response: Check the data transformer type. PowerChannel uses the following data transformer types:COMPRESSOR, STAGECOMPRESSOR, ENCRYPTOR, and DECRYPTOR.

30040 Invalid certificate account profile: <profile> (should be oneway or twoway).Explanation: You did not enter a valid certificate account profile.

112 Appendix A: PowerChannel Error Messages

User Response: Check the certificate account profile in the command. Enter a valid certificate account profile.Valid certificate account profiles are oneway and twoway.

30041 Invalid channel properties: <channel properties>.Explanation: At least one PowerChannel command parameter is incorrect.

User Response: Verify each parameter with the PowerChannel.properties file with the PowerChannelconfiguration utility.

30042 Transformer <transformer> execution error: <error message>.Explanation: The channel has failed for an unknown reason.

User Response: Check the additional error message and the PowerChannel Server log file for moreinformation.

30043 General system failure: <error message>.Explanation: The data transformer failed for an unknown reason.

User Response: Check the additional error message and the PowerChannel Server log file for moreinformation.

30044 Invalid XML command. Command parsing failure: <error message>.Explanation: The XML command parser cannot parse the command.

User Response: Verify the XML command parameters if you used a direct XML command.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support. Provide the XML command from the sessionlog file.

30045 XML command read failure: <error message>.Explanation: Internal error.

User Response: Contact Informatica Global Customer Support. Provide the XML command from the sessionlog file.

30046 Unknown external executor type: <error message>.Explanation: You used an undefined external executor type in the XML command.

User Response: Verify the XML command parameters.

30047 Session encountered an error declaring internal <internal variable> variable: <error message>.Explanation: PowerChannel cannot declare an internal variable.

User Response: Contact Informatica Global Customer Support.

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.

PowerChannel Messages 113

30049 Error connecting to the remote server: <error message>.Explanation: Connection to the remote PowerChannel Server failed.

User Response: Check the network connection. Or, check the account parameters.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

30050 Channel <channel name> creation error: <error message>.Explanation: The PowerChannel Server cannot create the channel. The PowerChannel Server might not

be able to find the source or target files.

User Response: Check the command syntax for errors. Check the source and target files.

30051 The channel failed while starting: <error message>.Explanation: The session cannot start the channel. Or, internal error.

User Response: Contact Informatica Global Customer Support.

30052 Error terminating the session.Explanation: Session termination failed.

User Response: Contact Informatica Global Customer Support.

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.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

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 InformaticaGlobal Customer Support.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

30055 Session encountered an error executing the <command name> external command: <errormessage>.

Explanation: PowerChannel cannot run the external command.

User Response: Verify the command syntax and operating system user privileges.

30056 Session TaskExecutor encountered an error during execution.Explanation: The PowerChannel Server failed to complete the tasks.

User Response: Check the session log file to see which tasks were completed.

114 Appendix A: PowerChannel Error Messages

30057 TaskExecutor was stopped before completing all the tasks.Explanation: The PowerChannel Server stopped the session before completing all of the tasks.

User Response: Check the session log file to see which tasks were completed.

30058 Internal <variable> variable was not declared.Explanation: Internal error. PowerChannel attempted to access an internal variable before declaring it.

User Response: Contact Informatica Global Customer Support. Provide the XML command from the sessionlog file.

30059 Wrong usage of <transformer name> transformer.Explanation: You did not use the transformer <transformer name> correctly in the XML command

parameters.

User Response: Verify the XML command parameters.

30060 Certificate account <account name> already exists.Explanation: You attempted to create a certificate account that already exists.

User Response: Create a certificate account with a different name.

30061 Data block header is corrupt.Explanation: The channel received a corrupt data block header from the network.

User Response: Verify the network connection.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

30062 Source and target transformers are incompatible. Check the order of the transformers in thecommand 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: Do not enter data transformers for DECOMPRSTAGE.

30064 Source and target channels have incompatible transformers.Explanation: Two peer channels have an incompatible set of transformers.

User Response: Check the channel parameters in the XML command.

30065 Session (ID=<session ID>) is not recoverable.Explanation: The session information object does not have enough information to recover the session. The

session might have crashed before getting important data for recovery.

User Response: Run the command again.

Explanation: The repository contains inconsistencies.

PowerChannel Messages 115

User Response: Restore the repository from backup.If you have no repository backup, contact InformaticaGlobal Customer Support.

30067 File checksum verification failed.Explanation: After file transfer is complete, the source and target copies of the file are different. This might

occur if you change the source or target file during file transfer.

User Response: Transfer the file again.

30068 Checksum verification failed. Recovery disabled for <filename>.Explanation: During recovery, the PowerChannel Server found a target file to be different from the source

file on the reader side. This might occur if you change the file between recovery attempts.

User Response: The PowerChannel Server cannot perform recovery. It will send the file from the first byte.

30069 Cannot obtain channel information.Explanation: The PowerChannel Server cannot obtain channel information.

User Response: If you receive this message during session recovery, execute the session again.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

30071 Attempt to recover the wrong session (ID=<session ID>) from the remote session ID=<sessionID> at <hostname:port>.

Explanation: The PowerChannel Server found attempts to recover a session that does not belong to arecovery request. This may be a remote PowerChannel Server error.

User Response: If you receive this message during session recovery, execute the session again.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

30072 Cannot change password for certificate accounts.Explanation: You attempted to change the password for a certificate account.

User Response: You cannot change a certificate account password.

30073 Session log failure: <error message>.Explanation: The PowerChannel Server cannot write to the session log file.

User Response: Check available operating system disk space.

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.

30075 Session failed: <session ID>.Explanation: The session failed.

User Response: Check the PowerChannel Server and session log files for more information.

116 Appendix A: PowerChannel Error Messages

30076 Cannot update <session name> session information: <error message>.Explanation: The repository contains inconsistencies.

User Response: Restore the repository from backup. If you have no repository backup, contact InformaticaGlobal Customer Support.

Explanation: Operating system error.

User Response: Contact the internal technical support.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

30077 Stopping session error: <error message>.Explanation: The PowerChannel Server could not stop the session.

User Response: Check the session log file for a related message.

30081 The repository operation failed: <error message>.Explanation: The PowerChannel Server cannot run the task you requested.

User Response: Check the error message in the PowerChannel Server and session log file for moreinformation.

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 accountprofiles are admin, user, and disabled.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

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.

30084 Cannot set empty password to the account.Explanation: You attempted to set an empty password. This is not allowed.

User Response: Do not set an empty password to an account.

30085 Account <account name> already exists.Explanation: You attempted to create an account that already exists in the repository.

User Response: Check the account name and create an account with a different name.

30086 Account <account name> does not exist in the repository.Explanation: You attempted to remove an account that does not exist in the repository.

User Response: Check the account name and re-enter the command.

PowerChannel Messages 117

30087 The account <account name> tried to delete itself. An account cannot delete itself.Explanation: You attempted to remove an account using that account name. This is not allowed.

User Response: Use a different account with the admin profile to delete the account.

30089 Operating system command failed (return code=<return code>).Explanation: An operating system command failed with a separate field return code.

User Response: Check the command parameters for errors.

30090 Error connecting to remote server (account@hostname:port).Explanation: The PowerChannel Server made the maximum number of attempts to connect to a remote

session, but failed.

User Response: Verify the network settings. Or, verify that the remote PowerChannel Server is running.

30091 Session auto recovery failed after <number> tries.Explanation: The PowerChannel session failed. The PowerChannel Server exceeded the number of

allowed auto recovery attempts.

User Response: If you want to transfer files between PowerChannel Servers, you can run manual sessionrecovery 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.

30093 Cannot send back <status> session status: <error message>.Explanation: PowerChannel encountered an error sending session status back to the client. The client was

probably disconnected.

User Response: Run the command again. Or, verify that the PowerChannel Server is running. Or, verify thatthe session exists.

30094 Server encountered an error while obtaining session information: <error message>.Explanation: The PowerChannel Server cannot get session information. Or, internal error.

User Response: Contact Informatica Global Customer Support.

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 yeswith the PowerChannel configuration utility.

30099 Duplicate variable <variable>.Explanation: Internal error. PowerChannel attempted to declare a variable with a name that is already

assigned to another variable.

User Response: Contact Informatica Global Customer Support.

118 Appendix A: PowerChannel Error Messages

30106 The account <account name> tried to change its own account profile. An account cannotchange its own account profile.

Explanation: You attempted to change the own account profile. This is not allowed.

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 certificateaccount profiles are oneway and twoway.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

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.

User Response: Verify the session status.

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.

User Response: Run the file transfer command again.

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 onetransformer: <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.

30121 <filename> file transfer failed: <error message>.Explanation: The file check procedure failed after file transfer.

PowerChannel Messages 119

User Response: Check the error message in the PowerChannel Server and session log file for moreinformation.

30124 Channel <channel name> failed: <error message>.Explanation: The channel failed.

User Response: Check the error message for more information.

30125 Cannot find file <filename>.Explanation: The reader cannot find the specified source file.

User Response: Verify that the source file exists in the specified directory.

30130 Wrong pipe listener port value: <value> (should be 1 to 65535).Explanation: You entered an invalid value for the listener port of the local PowerChannel Server.

User Response: Enter a valid listener port number from 1 to 65535 for -F of the PcCmd createpipe command.

30131 Wrong pipe connection port value: <value> (should be 1 to 65535).Explanation: You entered an invalid value for the port of the FTP server.

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 to100000).

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 moreinformation about the timeout parameter in the PcCmd createpipe command, enter PcCmdcreatepipe -help at the command line.

30155 Recovery failed. Remote server does not have enough memory.Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

30159 The stage file is corrupt.Explanation: The remote staged file contains inconsistencies. You may have altered or removed the file

during the file transfer session.

User Response: If the remote staged file is corrupt, run PcCmdget or PcCmdsend again with different namesfor the source and target files.

30165 FTP protocol failure.Explanation: There was an error in the FTP protocol.

User Response: Check if you connected to an external application with an FTP client. Verify that the remoteserver is an FTP server.

30167 Cannot connect to the external application (hostname:port): <error message>.Explanation: The PowerChannel Server cannot connect to the external application you entered in the

PcCmdcreatepipe command.

120 Appendix A: PowerChannel Error Messages

User Response: Verify that the external application is running. Or, verify that the host name and port youentered in the PcCmdcreatepipe command is correct.

30168 Missing pipe listener port value (should be 1 to 65535).Explanation: You did not enter a value for the listener port of the local PowerChannel Server.

User Response: Enter a valid listener port number from 1 to 65535 for the -F parameter of the PcCmdcreatepipe command.

30169 A read error occurred when reading the file <filename>.Explanation: PowerChannel could not read the file. You may have replaced the original source file with

another while PowerChannel was reading the file.

User Response: Verify the source file. Restart the session.

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.

30183 Session recovery initialization was interrupted.Explanation: The PowerChannel Server cannot start recovery. A PowerChannel administrator may have

stopped the PowerChannel Server when it was initializing session recovery.

User Response: Start the PowerChannel Server. Run the PcCmdrecover command again.

30195 Pipe session does not support manual recovery.Explanation: You tried to run manual recovery on a session for transferring files between the Integration

Service and an FTP server or between FTP clients and servers. This is not allowed.

User Response: Start a session by running the PcCmd createpipe command. For more information, enterPcCmd createpipe -help at the command line.

Repository MessagesRepository 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: Contact the internal technical support.

40002 Server could not find the object: <repository object>.Explanation: The object does not exist in the repository. Or, the repository might contain inconsistencies.

User Response: Restore the repository from backup. If you have no repository backup, contact InformaticaGlobal Customer Support.

40003 Server could not delete the object: <repository object>.Explanation: The PowerChannel Server cannot delete the repository object. The repository might contain

inconsistencies.

PowerChannel Messages 121

User Response: Restore the repository from backup. If you have no repository backup, contact InformaticaGlobal Customer Support.

Explanation: There is an operating system problem.

User Response: Contact the internal technical support.

40004 Server repository already exists: <error message>.Explanation: You attempted to initialize a repository that already exists. The repository might contain

inconsistencies.

User Response: Restore the repository from backup. If you have no repository backup, contact InformaticaGlobal Customer Support.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

40005 Unknown system error: <error message>.Explanation: There is an unknown system error.

User Response: Check the server log file for a related message.

40006 Cannot initialize repository: <error message>.Explanation: Repository initialization failed.

User Response: Check the additional error message and the PowerChannel Server log file for moreinformation.

40007 Invalid repository object type: <object type>.Explanation: The repository contains inconsistencies.

User Response: Restore the repository from backup. If you have no repository backup, contact InformaticaGlobal Customer Support.

40009 Property REPOSITORY not found in the properties file.Explanation: You did not enter a repository folder for the REPOSITORY property in the

PowerChannel.properties file.

User Response: For more information, check the PowerChannel.properties file.

40010 Repository creation error: <error message>.Explanation: There was a problem creating the repository. This may be an operating system error.

User Response: Check the operating system user privileges to write files.

40011 Repository already exists.Explanation: You attempted to initialize an existing repository.

User Response: Do not reinitialize an existing repository.

40012 General repository initialization error: <error message>.Explanation: Repository initialization error.

User Response: Check the PowerChannel Server log file for more information.

122 Appendix A: PowerChannel Error Messages

40013 Repository is corrupt.Explanation: The repository contains inconsistencies.

User Response: Restore the repository from backup. If you have no repository backup, contact InformaticaGlobal Customer Support.

40014 Repository is corrupt or does not exist.Explanation: The repository does not exist.

User Response: Create a repository with PowerChannel init. For more information, enter PowerChannel init-help at the command line.

Explanation: The repository contains inconsistencies.

User Response: Restore the repository from backup. If you have no repository backup, contact InformaticaGlobal 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.

40016 Repository lock does not allow the operation to complete.Explanation: The repository is locked by another running PowerChannel instance.

User Response: To remove the lock, run PowerChannel unlock.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

40017 Repository upgrade is needed. Current version is <version>. Upgrade to <version>.Explanation: You need to upgrade the repository.

User Response: Run PowerChannel upgrade to upgrade the repository to the version recommended in theerror message. For more information, enter PowerChannel upgrade -help at the commandline.

40018 Unsupported repository version: <version>.Explanation: You have an unsupported version of the repository. The PowerChannel executables are from

a previous version of PowerChannel.

User Response: Update the PowerChannel executables to a newer version.

Explanation: The repository might contain inconsistencies.

User Response: Restore the repository from backup. If you have no repository backup, contact InformaticaGlobal Customer Support.

40020 Repository upgrade failed: <error message>.Explanation: The repository upgrade failed.

User Response: Restore the repository from backup. If you have no repository backup, contact InformaticaGlobal Customer Support.

PowerChannel Messages 123

40022 Repository home directory <directory> does not exist.Explanation: Repository initialization failed because the directory containing the repository does not exist.

User Response: Check the PowerChannel.properties file to verify that the REPOSITORY property containsthe correct path to the repository.

40024 Repository is already unlocked.Explanation: You attempted to unlock a locked repository.

User Response: You cannot unlock an unlocked 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 errorduring session execution.

User Response: Check the appropriate session log file and the PowerChannel Server log file for moreinformation.

40027 Repository object <object> is corrupt.Explanation: The PowerChannel Server found a repository object that contains inconsistencies.

User Response: Restore the repository from backup. If you have no repository backup, contact InformaticaGlobal Customer Support.

40028 General repository error: <error message>.Explanation: The PowerChannel Server found a repository error.

User Response: Check the remote PowerChannel Server log for more information.

Common MessagesCommon error messages result from PcCmd, web client, or PowerChannel commands. If you get an errormessage as the result of a PcCmd command, the error message appears at the PcCmd command line and in thePcCmd log file. Web client error messages appear in the web client. PowerChannel error messages appear in thePowerChannel Server and session log files for that session.

50002 Cannot load JSAFE library: <JSAFE library name>.Explanation: The PowerChannel Server cannot load RSA JSAFE libraries.

User Response: Verify that the JSAFE libraries are in the PowerChannel/lib directory.

50003 Cannot load class: <class name>.Explanation: The PowerChannel Server cannot find one of the required class files.

User Response: Check the PowerChannel installation for the class file.

50004 Unsupported command line option: <command parameter>.Explanation: You entered a command parameter that the current command does not support.

124 Appendix A: PowerChannel Error Messages

User Response: Check the command parameters.

Explanation: If you see this message in the web client, there is an internal error.

User Response: Contact Informatica Global Customer Support.

50005 Invalid <parameter> option format.Explanation: You entered an invalid value for the command parameter.

User Response: Check the command parameters.

50006 Invalid command: <command name>.Explanation: You tried to execute an unsupported command.

User Response: Check the list of supported commands.

Explanation: If you see this message in the web client, there is an internal error.

User Response: Contact Informatica Global Customer Support.

50007 Cannot load properties file: <filename>.Explanation: PowerChannel cannot find the required properties file.

User Response: Check the installation for the properties file that uses the PowerChannel configuration utility.

50008 Cannot find <parameter> in the properties file.Explanation: PowerChannel cannot find the required parameter in the properties file.

User Response: Check the appropriate properties file for the specified parameter with the PowerChannelconfiguration utility.

50009 No user name (-u option) entered.Explanation: You did not enter a -u (user account name) option in the command.

User Response: Enter -u in the command.

Explanation: If you see this message in the web client, there is an internal error.

User Response: Contact Informatica Global Customer Support.

50010 No password entered either in command line or properties file.Explanation: You did not provide a password in the properties file or in the command line.

User Response: Enter a password with the -p parameter in the command.

50011 File <filename> does not exist.Explanation: PowerChannel cannot find the specified file.

User Response: Verify that you entered the correct directory for the filename.

50012 File <filename> or <filename> does not exist.Explanation: PowerChannel cannot find the file by its specified or default path.

User Response: Verify that the file is located in the right directory.

Common Messages 125

50014 Out of memory.Explanation: The machine hosting the PowerChannel Server is out of JVM memory.

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. Thevalue 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 JVMmemory.

50017 Invalid log level: <log level> (should be 0 to 3).Explanation: You entered the wrong value for the LOG_LEVEL parameter in the PowerChannel.properties

file.

User Response: Enter a valid value for LOG_LEVEL from 0 to 3 with the PowerChannel configuration utility.

50019 Unsupported cryptography mode: <mode>.Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

50020 Corrupt object.Explanation: A file object might be corrupt. Or, There might be a wrong object version. Or, internal error.

User Response: Contact Informatica Global Customer Support.

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 wrongversion of the certificate file.

50022 Duplicated command line option: <command line option>.Explanation: You entered a command parameter twice in the command.

User Response: Enter a command line option only once.

Explanation: If you see this message in the web client, there is an internal error.

User Response: Contact Informatica Global Customer Support.

50024 The connection request was rejected by the server <host name:port>. Check the user accountname 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. Forexample, if the encryption algorithm is set to JSAFE/RC2 for the CRYPTOGRAPHY propertyin the PowerChannel.properties file, the properties file for the client must have the samevalue for CRYPTOGRAPHY.

126 Appendix A: PowerChannel Error Messages

50025 Error connecting to the remote server.Explanation: The protocol handshake operation between the two protocols failed for an unknown reason.

User Response: Run the command again.

Explanation: Internal error.

User Response: Contact Informatica Global Customer Support.

50027 Error receiving data: <error message>.Explanation: The protocol cannot receive data. This is probably due to network failure.

User Response: Check the network connection.

50028 Error sending data: <error message>.Explanation: The protocol cannot receive data. This is probably due to network failure.

User Response: Check the network connection.

50033 Secured random initialization error: <error message>.Explanation: There is a problem initializing JSAFE libraries.

User Response: Verify that the JSAFE libraries are in the Java lib/ext directory.

50034 Cannot create DocumentBuilder: <error message>.Explanation: There is a problem with the Sun JAXP libraries.

User Response: Verify that the JAXP libraries are in the Java lib/ext directory.

50035 Invalid session ID: <session ID>.Explanation: The session ID you provided does not exist in the repository.

User Response: Check the session log file. Enter the correct session ID.

50036 Invalid entry. Only yes or no is allowed for: <command parameter>.Explanation: You entered an invalid entry for the command parameter.

User Response: Use a valid value for the parameter.

50039 Password encryption failure: <error message>.Explanation: The PowerChannel Server encountered an error during password encryption. The password

might be corrupt.

User Response: Reencrypt the password with the PcPassword utility. Replace the old encrypted passwordvalue.

50040 Corrupt encrypted password string.Explanation: The PowerChannel Server cannot decrypt encrypted password from the properties file. The

password might be corrupt.

User Response: Reencrypt the password with the PcPassword utility. Replace the old encrypted passwordvalue.

Common Messages 127

50041 Account name <account name> cannot contain special characters like <character>.Explanation: The account name contains special characters. Do not use special characters.

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.

User Response: Enter a session name without 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: Enter a user account name without special characters.

50044 Corrupt encrypted password format.Explanation: The encrypted password has a wrong or corrupt format.

User Response: Reencrypt the password with the PcPassword utility. Replace the old encrypted passwordvalue.

50045 The filter <filter> provided for session name is invalid.Explanation: You provided an invalid filter for the session 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 astring. For example, “ftsession%” is a valid filter. “ft%session” is not.

User Response: Enter a valid filter name.

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 astring. For example, “account%” is a valid filter. “us%account” is not.

User Response: Enter a valid filter name.

50047 The filter <filter> provided for session status is invalid.Explanation: You provided an invalid filter for session status. Valid filter values are: Completed, Failed,

Running, and Stopped.

User Response: Enter a valid filter value.

50048 Duplicate command line option: <error message>.Explanation: You entered a command parameter twice in the command. For example, -u=admin -u=test.

User Response: Remove the duplicate command line option.

50050 Invalid port value: <value> (should be 1 to 65535).Explanation: The port value for the -R parameter in the command is not valid.

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.

128 Appendix A: PowerChannel Error Messages

User Response: Enter a value for the SERVER_PORT property from 1 to 65535 with the PcCmd configurationutility.

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.

User Response: Enter an account name from 3 to 32 characters.

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 an account name from 3 to 32 characters.

50057 The password is too short (should contain at least 3 characters).Explanation: You entered a password, which contained fewer than three characters. This is not allowed.

User Response: Enter a password of three characters or more.

50058 The password cannot be the same as the account name.Explanation: You tried to create or change a password to be the same as the account name. This is not

allowed.

User Response: Enter a password, which is different than the account name.

50062 Undefined connector type: <error message>.Explanation: You provided a connector type that the PowerChannel Server does not support.

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 hackthe system.

User Response: Contact the internal technical support.

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 hackthe system.

User Response: Contact the internal technical support.

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 useraccount name, but the wrong account password or key.

Common Messages 129

User Response: This is likely a user error from the client. Do not take any action.

Explanation: If there are multiple sequential instances of this message, there might be an attempt to hackthe system.

User Response: Contact the internal technical support.

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 Serverwith 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 hackthe system.

User Response: Contact the internal technical support.

90001 Corrupt object or communication error.Explanation: The expected object has the wrong structure. It might contain inconsistencies.

User Response: Restore the repository from backup. If you have no repository backup, contact InformaticaGlobal Customer Support.

Explanation: Communication error.

User Response: Check the network connections.

Explanation: If you received this message when logging in to the web client, you did not enter the listenerport number of the PowerChannel Server.

User Response: Enter the listener port number of the PowerChannel Server. Verify the listener port bychecking the SERVER_PORT with the PowerChannel configuration utility.

90002 Corrupt object.Explanation: Internal error. Saved or transferring object contains inconsistencies.

User Response: Contact Informatica Global Customer Support.

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: Contact Informatica Global Customer Support.

90005 An error occurred during protocol initialization: <error message>.Explanation: Internal error. The protocol initialization failed.

User Response: Contact Informatica Global Customer Support.

90006 Error receiving data: <error message>.Explanation: Protocol cannot receive data due to network failure.

User Response: Contact Informatica Global Customer Support.

130 Appendix A: PowerChannel Error Messages

90007 Error sending data: <error message>.Explanation: Protocol cannot send data due to network failure.

User Response: Contact Informatica Global Customer Support.

90008 Error closing the protocol.Explanation: There is a problem closing the protocol network socket due to network failure.

User Response: Check the network connection.

90009 Protocol is closed.Explanation: Internal error. You attempted to send data through a closed protocol.

User Response: Contact Informatica Global Customer Support.

90010 Error connection to the server at: <hostname:port>.Explanation: The PowerChannel Server cannot connect to the PowerChannel Server.

User Response: Verify that the PowerChannel Server is running. Verify that the network is alive.

90011 Cipher stream communication error.Explanation: The cryptographic communication stream failed, possibly because of an I/O network or file

problem.

User Response: Check the network connection. Or, internal error.

90012 Remote server hostname or IP address is not specified.Explanation: You attempted to connect to the remote PowerChannel Server without a remote

PowerChannel Server IP address.

User Response: Enter the remote PowerChannel Server IP address in the command or in the accountproperties.

90013 Remote server port is not specified.Explanation: You attempted to connect to the remote PowerChannel Server without a remote server port.

User Response: Enter the remote PowerChannel Server port in the command parameters or in the accountproperties.

90014 Invalid port number: <error message>.Explanation: You entered an incorrect value for the port number for the PowerChannel Server.

User Response: Check the PowerChannel Server port value. Verify that it is between 1 and 65535.

90015 Cannot open log file: <error message>.Explanation: The PowerChannel Server cannot open the server log file.

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.

Common Messages 131

User Response: Contact the internal technical support.

90017 Remote session failed: <error message>.Explanation: A remote session failed.

User Response: Check the error message for more information.

90018 Thread (message) exception: <error message>.Explanation: Undocumented log level LOG_ALL_EXCEPTIONS is set to 4.

User Response: Contact the internal technical support.

90019 Attempt to establish connection by an unknown client.Explanation: An unknown client attempted to connect to the PowerChannel Server. It might be an attempt

to hack the system.

User Response: Contact the system security administrator.

90020 Default cryptographer is not registered.Explanation: Internal error. No default cryptographer is registered.

User Response: Contact Informatica Global Customer Support.

PcCmd MessagesPcCmd displays messages when there is an error in the PcCmd command. PcCmd messages appear at thePcCmd command line and in the PcCmd log file.

60034 PcCmd internal error: <error message>.Explanation: Internal error.

User Response: Check the session log and the additional error message for more information. Or, contactInformatica Global Customer Support.

60035 Wrong PcCmd command usage: <command>.Explanation: The PowerChannel Server cannot execute the command because you entered the wrong

command syntax.

User Response: Check the command parameters. Use PcCmd <command> -help for a list of optional andrequired 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.

60041 Invalid PcCmd.properties file entry: <property = value>.Explanation: You entered an invalid value for a property in the PcCmd.properties file.

User Response: Enter a valid value for the property.

132 Appendix A: PowerChannel Error Messages

60045 Undefined response from server.Explanation: Internal error. PcCmd received an undefined object as one of the PowerChannel Server

objects.

User Response: Contact Informatica Global Customer Support.

60046 Session name <session name> cannot contain special characters like <character> in theproperties 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 propertiesfile.

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.

Client Common MessagesThe following messages display when there is an error in the PcCmd command. They appear in the PcCmdcommand line and the PcCmd log file. These messages might also display in the web client when there is aninternal error, or if the application server settings are not correctly configured.

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 GlobalCustomer Support.

70001 Missing required parameter: <parameter>.Explanation: You did not enter one of the required command parameters in the command.

User Response: Check the command parameters. Use PcCmd <command> -help for a list of optional andrequired parameters for the command.

70002 No session ID(s) specified in the command. Enter a session ID for individual sessions or usethe -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 allsessions in the command syntax.

70003 No account information specified for modifying this account.Explanation: You did not enter any command parameters for editing the account.

User Response: Enter the account attributes you want to change. For example, if you want to change theaccount profile, enter the -l command parameter followed by the new account profile.

Client Common Messages 133

70004 No filter provided for the PcCmd monitor command. Provide a filter for monitoring.Explanation: You did not use a parameter to provide filter information to monitor a session in the PcCmd

monitor command.

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 -aparameter, do not provide any value after the parameter. For example, enter -a in thecommand.

70008 File reading error: <error message>.Explanation: The PowerChannel Server cannot read the XML file <filename>.

User Response: Verify that the XML file exists. Or, verify that you entered the correct path to the XML file inthe 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 remotePowerChannel Server.

User Response: Run a separate PcCmd get command for each remote PowerChannel Server you want to getfiles 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.

70011 Missing source and target files information.Explanation: You did not enter the source or destination files you want to transfer.

User Response: Enter files with the -f parameter in the command.

70012 Missing target host(s) information.Explanation: The remote host information does not contain a PowerChannel Server address.

User Response: Enter the appropriate PowerChannel Server address.

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.

134 Appendix A: PowerChannel Error Messages

70014 The value <value> provided for encryption level is not valid (should be 1 to 3 or none).Explanation: The value you provided for ENCRYPTION_LEVEL is not valid.

User Response: Check the PcCmd.properties file and enter a value for ENCRYPTION_LEVEL from 0 to 3.

70016 No filter provided for the PcCmd stop command.Explanation: You did not enter a filter for stopping sessions in the PcCmd stop command.

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

Client Common Messages 135

I N D E X

Aaccounts

PowerChannel 4PowerChannel certificate accounts 17PowerChannel user accounts 16

active listenersPowerChannel security enhancing 28

ACTIVE_LISTENERS propertydescription 30

adminPowerChannel profile 16

architecturePowerChannel 3

authenticationPowerChannel 1

BBEA WebLogic Server

PowerChannel installation and configuration 7

Ccertificate accounts

creating with PcCmd 85creating with the PowerChannel web client 18displaying PowerChannel with the web client 19editing PowerChannel with the web client 22editing with PcCmd 89importing 44PcCmd, displaying 87PcCmd, removing 92PowerChannel 17PowerChannel oneway profile 17PowerChannel twoway profile 17PowerChannel, removing with web client 23setting a default certificate account 53

certificate filesexporting with PcCmd 85importing 44PowerChannel directory 34

channelsPowerChannel 25PowerChannel data transfer types 25

checksumdefault checksum value 52in the FileTransfer XML command 98in the PcCmd get command 57in the PcCmd send command 59

CHECKSUM (property)description 52

clientsPowerChannel 3

CODE_PAGE propertyin the PcCmd.properties file 52

commandsstarting PowerChannel as an application 12

compressionin the FileTransfer XML command 98in the PcCmd createpipe command 62in the PcCmd get command 57in the PcCmd send command 59PowerChannel 2PowerChannel database data transfer 71setting the default compression level 52

COMPRESSION_LEVEL propertydescription 52

COMPRESSORPowerChannel data transformer 26

COMPRSTAGEPowerChannel channel 25

configuration utilityPowerChannel properties file 37

connectionsconfiguring type for PowerChannel 66

connectivityPowerChannel 24

CRYPTOGRAPHY propertydescription 31in PowerChannel.properties file 53

Ddata compression

PowerChannel 2data encryption

PowerChannel 2data transfer

PowerChannel channel types 25data transformers

PowerChannel 26database data transfer

PowerChannel installation 8PowerChannel, compression and encryption 71PowerChannel, requirements with compression and encryption 71

DECOMPRESSORPowerChannel data transformer 26

DECOMPRSTAGEPowerChannel channel 25

DECRYPTORPowerChannel data transformer 26

disabledPowerChannel profile 16

disabled accountsPowerChannel user profile 16

displaying accountscertificate accounts with PcCmd 87displaying PowerChannel accounts with the web client 19

136

displaying PowerChannel accountsdisplaying user accounts with PcCmd 86

Eencryption

FIPS-certified encryption for PowerChannel 2in the FileTransfer XML command 98in the PcCmd createpipe command 62in the PcCmd get command 57in the PcCmd send command 59PowerChannel 2PowerChannel database data transfer 71PowerChannel, setting 7setting the default encryption level 52setting the encryption algorithm 53

ENCRYPTION_LEVEL propertydescription 52

ENCRYPTORPowerChannel data transformer 26

error messagesPcCmd 132PowerChannel 103PowerChannel client common 133PowerChannel common 124

EXPORT_DIR propertydescription 34

Ffile integrity

PowerChannel 2file transfer

between PowerCenter and an FTP server, PowerChannelrequirements 65flat file data between PowerCenter and FTP server 65flat file targets, sending to 68path names on UNIX 83PcCmd get command 57PcCmd send command 59PcCmd, receiving files 57PcCmd, sending files 59PowerCenter session, receiving files 67PowerChannel input and output folders 56PowerChannel, overview 55PowerChannel, requirements 55PowerChannel, troubleshooting 68pre- and post-session command requirements for PowerChannel 67text files from Windows to UNIX 57with XML commands 98

filenamePcCmd get and PcCmd send commands 57

FIPS-certified encryptionPowerChannel 2

FTP connectionsfor PowerChannel in PowerCenter 66

FTP file transfermonitoring in the PowerChannel session log 66monitoring PowerChannel in PowerCenter 66

HHOSTS property

description 53

Iinput folder

PowerChannel file transfer 56INPUT_FOLDER property

description 35installing

PowerChannel on Windows 9

JJVM

PowerChannel application, configuring 12PowerChannel service, configuring 12

LLICENSE property

description 32log level

PowerChannel log files 33LOG_FOLDER property

description 33LOG_LEVEL property

description 33

MMAX_BLOCK_SIZE property

description 32MAX_CONCURRENT_RUNNING_SESSIONS property

description 35MAX_SESSIONS_MONITORED property

description 34memory

PowerChannel buffer memory, allocating 32

NNUM_AUTO_RECOVERY_ATTEMPTS property

description 35

Ooneway

PowerChannel certificate account profiles 17operating system commands

executing with XML commands 99RUN_EXTERNAL_EXECUTE property, setting 99

output folderPowerChannel file transfer 56

OUTPUT_FOLDER propertydescription 36

PPASSWORD property

description 34in PcCmd.properties 51

passwordsPcCmd.properties file, setting 51

path names

Index 137

file transfer on UNIX 83in PcCmd commands 83

$PC_DATEdescription 40export directory path, controlling 43log file path, controlling 42source and target file path, controlling 40

$PC_USERdescription 40export directory path, controlling 43controlling log file path 42source and target file path, controlling 41

PC.dtd filesupporting XML command parameters 97

PcCmdconfiguration utility 53creating a certificate account 85displaying certificate accounts 87displaying user accounts 86editing a certificate account 89editing a user account 88flat file sources and targets, transferring file data 67PowerChannel client 3PowerChannel Servers, connecting 62PowerChannel sessions, monitoring 92PowerChannel sessions, stopping 93properties 50properties file, configuring 53receiving files from a remote PowerChannel Server 57remote PowerChannel servers, sending files 59removing a certificate account 92removing a user account 91session recovery 94stopping the PowerChannel Server 95user account, creating 84with XML command files 100

PcCmd commandsoverview 82path names 82PcCmd createcert 85PcCmd createpipe 62PcCmd createuser 84PcCmd displaycert 87PcCmd displayuser 86PcCmd editcert 89PcCmd edituser 88PcCmd get 57PcCmd get command in pre-session commands 67PcCmd monitor 92PcCmd recover 94PcCmd removecert 92PcCmd removeuser 91PcCmd run 100PcCmd send 59PcCmd send command in post-session commands 68PcCmd stop 93PcCmd stopserver 95

PcCmd getfilename command parameter 57

PcCmd propertiesCHECKSUM 52CODE_PAGE 52COMPRESSION_LEVEL 52configuring 50CRYPTOGRAPHY 53ENCRYPTION_LEVEL 52HOSTS 53overview 49

PASSWORD 51PCCMD_LOG 50SERVER_ADDRESS 50SERVER_PORT 50SESSION_NAME 51STAGE 53USERNAME 51

PcCmd properties fileconfiguring 53description 5

PcCmd sendfilename command parameter 57

PCCMD_LOG propertydescription 50

pcservice.logPowerChannel log file 9

PcWeb properties filedescription 5

PIPEPowerChannel channel 25

PowerCenterfile transfer between PowerCenter and FTP server 65FTP connection for PowerChannel 66PcCmd commands in pre- and post-session commands 66PowerChannel, troubleshooting 68

PowerCenter session logPowerChannel, database data transfer 73PowerChannel, pre- and post-session command messages 67

PowerChannelarchitecture 3overview 1starting as an application 12

PowerChannel applicationstarting 12

PowerChannel commandsPowerChannel import 44PowerChannel reencrypt 46PowerChannel unlock 46PowerChannel version 47

PowerChannel for FTPPowerChannel Servers, connecting 62sessions, monitoring 64status of FTP files, monitoring 64

PowerChannel properties fileconfiguration utility 37description 5properties 29

PowerChannel relational database connectionconfiguring 11

PowerChannel repositoryaccounts 4description 4overview 16reencrypting 46restoring 14sessions 5unlocking 46version number, verifying 47

PowerChannel Serverconfiguring 29connectivity 24description 4overview 24properties 29protocol 25starting 11starting as a service 12stopping 13

138 Index

stopping as a service 12stopping with PcCmd 95variables 40web client, stopping 48

PowerChannel sessionsdefault session name, setting 51description 5managing 74PcCmd, monitoring 92PcCmd, stopping 93recovery 79web client, monitoring 74web client, recovering 80web client, stopping 78

PowerChannel.propertiesdescription 29

properties file command parameterin PcCmd commands in PowerCenter sessions 67

protocolPowerChannel Server 25

RRC2

PowerChannel encryption 7READSTREAM

PowerChannel channel 25recovery

NUM_AUTO_RECOVERY_ATTEMPTS property 80PowerChannel 2PowerChannel sessions, manual 80PowerChannel, automatic 80PowerChannel, overview 79PowerChannel, troubleshooting 81

REMOVE_LOG_FILES_ON_PURGE propertydescription 35

removing accountscertificate account with PcCmd 92PowerChannel account with the web client 23

REPOSITORY propertydescription 30

RUN_EXTERNAL_EXECUTE propertydescription 36

Ssecurity

PowerChannel, enhancing 28server authentication

PowerChannel 2server logs

PowerChannel log file directory, configuring 32SERVER_ADDRESS property

description 50SERVER_ERR_LOG property

description 33SERVER_LOG property

description 32SERVER_PORT property

description 50service start account

PowerChannel installation prerequisite 9SESSION_NAME property

description 51source connections

configuring for PowerChannel 66source files

PowerChannel, receiving in PowerCenter 67sources

PowerChannel, monitoring FTP file transfer 66STAGE property

description 53STAGECOMPRESSOR

PowerChannel data transformer 26staging files

PowerChannel 26setting the default staging value 53

Ttargets

PowerChannel, monitoring FTP file transfer 66timeout

PowerChannel, FTP with PowerCenter 66PowerChannel, FTP without PowerCenter 62

TOTAL_CHANNEL_MEMORY propertydescription 32

transferring filesPowerChannel, overview 55

TRANSPORTPowerChannel channel 25

3DESPowerChannel encryption 7

troubleshootingPowerChannel installation and configuration 14PowerChannel, recovery 81PowerChannel, transferring files 68

TRUST_REMOTE_EXECUTION propertydescription 36

twowayPowerChannel certificate account profiles 17

Uuninstalling

PowerChannel from Windows 14UNIX

path names for file transfer 83transferring text files from Windows 57

upgradingPowerChannel 9

userPowerChannel profile 16

user accountscreating with the PowerChannel web client 18displaying PowerChannel with the web client 19displaying with PcCmd 86editing PowerChannel with the web client 21editing with PcCmd 88PowerChannel admin profile 16PowerChannel user profile 16PowerChannel, creating with PcCmd 84PowerChannel, removing with web client 23removing with PcCmd 91

user authenticationPowerChannel 2

USERNAME propertydescription 33in the PcCmd.properties file 51

Index 139

Vvariables

export directory path, controlling 43log file path, controlling 42$PC_DATE 40$PC_USER 40source and target file path, controlling 41

Wwait command parameter

description 59in PcCmd createpipe commands 62with the PcCmd get command 57

web clientconnecting to PowerChannel 13creating a PowerChannel certificate account 18creating a PowerChannel user account 18displaying PowerChannel accounts 19editing a PowerChannel certificate account 22editing PowerChannel user accounts 21PowerChannel accounts, removing 23PowerChannel client 3PowerChannel Server, stopping 48

PowerChannel sessions, monitoring 74PowerChannel sessions, recovering 80PowerChannel sessions, stopping 78

Windowsinstalling PowerChannel 9transferring text files to UNIX 57

WRITESTREAMPowerChannel channel 25

XXML command files

creating 97example 101executing commands on a remote PowerChannel Server 99operating system commands, executing 99overview 97PC.dtd file 97PcCmd with XML command files 100transferring files 98

XML commandsExternalExecute 99FileTransfer 98RemoteExecute 99

140 Index