0094-movingnodetootherdomain

7
© 2009-2013 Informatica Corporation. 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. Moving a Node to Another PowerCenter Domain

Upload: tata-sairamesh

Post on 26-Oct-2015

71 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: 0094-MovingNodeToOtherDomain

© 2009-2013 Informatica Corporation. 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.

Moving a Node to Another PowerCenter Domain

Page 2: 0094-MovingNodeToOtherDomain

2

Abstract

A node is a logical representation of a physical machine in a PowerCenter domain. You can remove a node from one PowerCenter domain and add it to another PowerCenter domain.

Table of Contents

Overview ........................................................................................................................................................................... 2

Step 1. Shut Down the Node ............................................................................................................................................ 2

Step 2. Back Up the nodemeta.xml File ............................................................................................................................ 3

Step 3. Remove the Node from the Current PowerCenter Domain .................................................................................. 3

Step 4. Define the Node for the Other PowerCenter Domain ........................................................................................... 3

Using infasetup DefineGatewayNode ........................................................................................................................... 4

Using infasetup DefineWorkerNode ............................................................................................................................. 5

Step 5. Add the Node to the Other PowerCenter Domain ................................................................................................ 5

Step 6. Start the Node ...................................................................................................................................................... 6

Step 7. Assign Application Services to Run on the Node ................................................................................................. 6

Overview

A node is a logical representation of a physical machine in a PowerCenter domain. You can remove a node from one PowerCenter domain and add it to another PowerCenter domain.

When you remove a node from a PowerCenter domain, all application services that were running on the node are also removed. If you have the high availability option and the services run on multiple nodes, then the services fail over to a backup node when you remove the node. If you do not have the high availability option, note the configuration of the services before you remove the node.

After moving the node to another PowerCenter domain, you must assign existing services in the new domain to run on the node or create services to run on the node.

To move a node from one PowerCenter domain to another PowerCenter domain, complete the following steps:

1. Shut down the node.

2. Back up the nodemeta.xml file.

3. Remove the node from the current PowerCenter domain.

4. Define the node for the other PowerCenter domain.

5. Add the node to the other PowerCenter domain.

6. Start the node.

7. Assign application services to run on the node.

Step 1. Shut Down the Node

Shut down the node that you want to move. You can shut down a node from the Administration Console or from the operating system. When you shut down a node, you stop Informatica Services and abort all processes running on the node.

Page 3: 0094-MovingNodeToOtherDomain

3

Note: To avoid loss of data or metadata when you shut down a node, disable all running processes in complete mode.

To shut down the node from the Administration Console:

1. Select the node in the Navigator.

2. Click Shutdown in the right pane.

The Administration Console displays the list of service processes running on that node.

3. Click Yes to stop all processes.

To stop the node on Windows:

1. From the Start Menu, click Administrative Tools > Services.

2. Double-click Informatica Services.

3. Click Stop.

To stop the node on UNIX:

1. At the command prompt, switch to the directory where the infaservice executable is located.

By default, infaservice installs in the following location:

<PowerCenter Installation Directory>\server\tomcat\bin

2. At the command prompt, type the following command:

infaservice shutdown

Step 2. Back Up the nodemeta.xml File

The nodemeta.xml file stores the configuration metadata of the node. A gateway node uses information in nodemeta.xml to connect to the domain configuration database. A worker node uses the information in nodemeta.xml to connect to the domain. The metadata file is stored in the following location:

<PowerCenter Installation Directory>\server\config

Create a backup of this file by copying it to another location outside of the PowerCenter installation directory. If needed, you can use the backup copy to restore the node to the initial domain.

Step 3. Remove the Node from the Current PowerCenter Domain

Use the Administration Console to remove the node.

To remove the node from the current PowerCenter domain:

1. In the Administration Console, select the node in the Navigator.

2. Click the Remove button.

3. In the warning message that appears, click OK.

Step 4. Define the Node for the Other PowerCenter Domain

You can define the node to function as a gateway node or a worker node in the new PowerCenter domain. When you define a node, you specify the host name and port number for the machine that hosts the node. You also specify the node name. The Administration Console uses the node name to identify the node.

Use either of the following programs to define the node:

The PowerCenter installation program. Run the installation program on the machine you want to define as the gateway or worker node. For more information, see the PowerCenter Installation Guide.

Page 4: 0094-MovingNodeToOtherDomain

4

infasetup command line program. Run the infasetup DefineGatewayNode or DefineWorkerNode command on the machine you want to serve as the gateway or worker node.

Using infasetup DefineGatewayNode

The infasetup DefineGatewayNode command defines a gateway node on the current machine. This command overwrites the nodemeta.xml file that stores the configuration metadata for the node.

To define the node as a gateway node:

1. At the command prompt, switch to the directory where the infasetup executable is located.

By default, infasetup installs in the following location:

<PowerCenter Installation Directory>\server

2. Enter infasetup on Windows or infasetup.sh on UNIX followed by the DefineGatewayNode command name and its required options and arguments.

For example on Windows, enter the following command:

infasetup DefineGatewayNode –DatabaseConnectionString

<database_connection_string> -DatabaseUserName <database_user_name>

-DatabasePassword <database_password> -DatabaseType <database_type> -DomainName

<domain_name> -NodeName <node_name> -NodeAddress <node_host:port>

-LogServiceDirectory <log_service_directory> -ResourceFile <resource_file>

The following table describes the required infasetup DefineGatewayNode options and arguments:

Option Argument Description

-DatabaseConnectionString

database_connection_string

Connection string used to connect to the domain configuration database. Specify the database host, database port, and the database service name as part of the connection string. Enclose the connection string in quotes.

-DatabaseUserName database_user_name Account for the database containing the domain configuration information.

-DatabasePassword database_password Domain configuration database password corresponding to the database user.

-DatabaseType database_type Type of database that stores the domain configuration metadata. Database types include:

db2

oracle

sqlserver

sybase

-DomainName domain_name Name of the domain the gateway node links to.

-NodeName node_name Name of the node. Node names must be between 1 and 79 characters and cannot contain spaces or the following characters: \ / * ? < > " |

-NodeAddress node_host:port Host name and port number for the machine hosting the node. Choose an available port number.

-LogServiceDirectory log_service_directory Shared directory path used by the Log Manager to store log event files.

-ResourceFile resource_file File that contains the list of available resources for the node. Use the file, nodeoptions.xml, located in the server\tomcat\bin directory.

For more information about using infasetup, see the PowerCenter Command Reference.

Page 5: 0094-MovingNodeToOtherDomain

5

Using infasetup DefineWorkerNode

The infasetup DefineWorkerNode command defines a worker node on the current machine. This command overwrites the nodemeta.xml file that stores the configuration metadata for the node.

To define the node as a worker node:

1. At the command prompt, switch to the directory where the infasetup executable is located.

By default, infasetup installs in the following location:

<PowerCenter Installation Directory>\server

2. Enter infasetup on Windows or infasetup.sh on UNIX followed by the DefineWorkerNode command name and its required options and arguments.

For example on Windows, enter the following command:

infasetup DefineWorkerNode -DomainName <domain_name> -NodeName <node_name>

-NodeAddress <node_host:port> -GatewayAddress <domain_gateway_host:port>

-UserName <user_name> -Password <password> -ResourceFile <resource_file>

The following table describes the required infasetup DefineWorkerNode options and arguments:

Option Argument Description

-DomainName domain_name Name of the domain the worker node links to.

-NodeName node_name Name of the node. Node names must be between 1 and 79 characters and cannot contain spaces or the following characters: \ / * ? < > " |

-NodeAddress node_host:port Host name and port number for the machine hosting the node. Choose an available port number.

-GatewayAddress domain_gateway_ host:port

Gateway host machine name and port number.

-UserName user_name User name used to connect to the domain.

-Password password User password.

-ResourceFile resource_file File that contains the list of available resources for the node. Use the file, nodeoptions.xml, located in the server\tomcat\bin directory.

For more information about using infasetup, see the PowerCenter Command Reference.

Step 5. Add the Node to the Other PowerCenter Domain

After you define the node, add it to the PowerCenter domain using the infacmd AddDomainNode command.

Note: You can also add the node to the PowerCenter domain from the Administration Console.

To add the node to the other PowerCenter domain:

1. At the command prompt, switch to the directory where the infacmd executable is located.

By default, infacmd installs in the following location:

<PowerCenter Installation Directory>\server\bin

2. Enter infacmd on Windows or infacmd.sh on UNIX followed by the AddDomainNode command name and its required options and arguments.

For example on Windows, enter the following command:

infacmd AddDomainNode -DomainName <domain_name> -UserName <user_name>

-Password <password> -SecurityDomain <security_domain> -Gateway

<gateway_host1:port gateway_host2:port...> -NodeName <node_name>

-FolderPath <full_folder_path>

Page 6: 0094-MovingNodeToOtherDomain

6

The following table describes the required infacmd AddDomainNode options and arguments:

Option Argument Description

-DomainName domain_name Name of the domain.

-UserName user_name User name used to connect to the domain.

-Password password User password.

-SecurityDomain security_domain Required if you use LDAP authentication. Name of the security domain that the user belongs to. Default is Native.

-Gateway gateway_host1:port gateway_host2:port ...

Host names and port numbers for the gateway nodes in the domain. Updates the gateway connectivity information in the domains.infa file.

-NodeName node_name Name of the node you want to add to the domain.

-FolderPath full_folder_path Full path, excluding the domain name, to the folder in which you want to add the node. Must be in the following format:

/parent_folder/child_folder

Default is “/”(the domain).

For more information about using infacmd, see the PowerCenter Command Reference.

Step 6. Start the Node

You must start the node before you can assign application services to run on the node.

To start the node on Windows:

1. From the Start Menu, click Administrative Tools > Services.

2. Double-click Informatica Services.

3. Click Start.

To start the node on UNIX:

1. At the command prompt, switch to the directory where the infaservice executable is located.

By default, infaservice installs in the following location:

<PowerCenter Installation Directory>/server/tomcat/bin

2. At the command prompt, type the following command:

infaservice startup

Step 7. Assign Application Services to Run on the Node

When you remove a node from a PowerCenter domain, all application services that were running on the node are also removed. After moving the node to another PowerCenter domain, assign application services to run on the node in the following ways:

Assign existing services in the new domain to run on the node. If you have the high availability option, you can assign existing services in the new domain to run on the node. You designate primary and backup nodes to run the service. By default, the service runs on the primary node. If the node becomes unavailable, the service fails over to a backup node.

Create services to run on the node. Use the Administration Console or the infacmd command line program to create the services to run on the node. For more information, see the PowerCenter Administrator Guide or the PowerCenter Command Reference.

Page 7: 0094-MovingNodeToOtherDomain

7

Author

Vijayaraghavan Amirisetty Software Engineer

Acknowledgements

Rupal Shah Senior Software Engineer QA

Alison Taylor Technical Writer

Girish Warrier Lead Technical Support Engineer