This is my first post. I will start with basics of Informatica Server Administration.

To determine the overall status of a domain, including its nodes and server processes, simply navigate to the Administrative console for that domain: http://{Server}:{Port}/

If Successful, you are presented with a screen similar to

If the website does not appear (i.e., “Internet Explorer cannot display the webpage”), then perhaps the Informatica web-service is not running on that machine. In this situation, you may attempt to log into the domain using another node (for example,abcddb2 also manages the Domain_abcddb1 domain).

Understand Service Status

After logging into the Administrator Console for a domain, Informatica displays currently list of services and the nodes on which the services are running. For example, the following shows three integration services

1. Running on node 15, and node 18 is on standby, in case service on 15 goes down

2. Running on both nodes 15 and 18 (obviously on a grid), if one service fails, the other takes all incoming processing requirements; and

3. Disabled, and is not running on either.

Shutdown / Startup / Bounce a Domain

Shutting Down a Domain

Shutting down a domain stops all Informatica Unix processes from running on any and all nodes in the domain. If there are any jobs running on any of the nodes, they will also be stopped.

There are two methods for shutting down a domain: the first via the Administration Console, the other via the Unix command line.

1. 1. From Administration Console

Important Note: There are no means to start a domain from the Administration Console
If you are required to restart (bounce) the domain, make sure you have proper Unix access to all nodes so that the services can be properly restarted.

1. Login in to domain’s website

2. In the domain hierarchy (on the left of the page), select the name of the domain.

3. Press the Shutdown button (off to the right), and choose Yes when prompted to shutdown (note: you will kill jobs if they are running)

1. 2. From the UNIX command line
For each of the server nodes in the domain, log in with the appropriate Unix credentials

1. Navigate to the tomcat server’s bin directory
cd {Unix Home Path}/server/tomcat/bin

2. Execute ./infaservice.sh shutdown

Startup a Domain

Starting up a domain can only occur from the Unix command line. If the domain has multiple nodes (refer to Appendix A), then the primary node must be started first.

1. Navigate to the tomcat server’s bin directory
cd {Unix Home Path}/server/tomcat/bin

2. Execute ./infaservice.sh startup

3. When the web server has been loaded and initialized (process /java/bin/java) then navigate to the Administrative Console for that node. Review all services as they come up.

4. If additional domain nodes need to be started, wait until after logging into the Administrative Console (step 3). Log in to the Unix shell for the remaining nodes and executes steps 1 and 2 until all nodes are started.

Bouncing a Domain

There is no automated way of bouncing a domain. You must manually stop the domain and then bring up each node individually. Since brining up a node requires Unix commands, it is easiest to shutdown/startup a domain all from the command line.

Shutdown / Startup / Bounce a Single Node

Starting and stopping a services without directly affecting other nodes in the domain.

Important Note: Starting and stopping a node may cause Informatica to automatically switch processes (from the node being shutdown) to another, operating node. Make sure that this is what you want.

1. 3. From Administration Console

Important Note: There are no means to start a node from the Administration Console
If you are required to restart (bounce) the node, then make sure you have proper Unix access to the node so that the services can be properly restarted.

1. 1. Login in to domain’s website

2. In the domain hierarchy (on the left of the page), select the name of the node.

1. 3. Press the Shutdown button (off to the right), and choose Yes when prompted to shutdown the node (note: you will kill jobs if they are running)

1. 4. From the UNIX command line
For each of the server nodes in the domain, log in with the appropriate Unix credentials

1. Navigate to the tomcat server’s bin directory
cd {Unix Home Path}/server/tomcat/bin

2. Execute ./infaservice.sh shutdown

Startup a Node

Starting up a node can only occur from the Unix command line.

1. Navigate to the tomcat server’s bin directory
cd {Unix Home Path}/server/tomcat/bin

2. Execute ./infaservice.sh startup

3. When the web server has been loaded and initialized (process /java/bin/java) then navigate to the Administrative Console for that node. Review all services as they come up.

Bouncing a Node

There is no automated way of bouncing a node. You must manually stop and restart the node. Since brining up a node requires Unix commands, it is easiest to perform both shutdown / startup from the command line.

Bounce a Specific Service (i.e., Repository or Integration Service)

Bouncing a service does not involve Unix commands. All actions must be performed using the Administration Console.

If Informatica is version 8.6.1, then

If the Service is not a Repository Service, then

Choose Domain tab and the locate the service in the domain hierarchy.
In the content panel to the right, press the Disable button.

1. Informatica then prompts you how to shut down the service.

Choose the following option that best fits your scenario.
In most cases, the service is being bounced because there is a problem, and the Abort option is immediate and effective.

2. Wait for the service to be stopped.
The text “The service is running” is replaced with “Stopping services on <node name>”.

3. Enable the Service
Once the service indicates that it has been stopped, simply press Enable to restart the process on the node. Wait until the green message “The service is running” appears.

If the service is a Repository Service, then

In version 8.6.1, all Integration Services associated with a repository must be Disabled before disabling the Repository itself. In addition, the Repository Service must be up and running before re-enabling any dependent Integration Service. Failure to manage in this order will lock-out all users.

This means that you must first identify all Integration Services first. There is no easy way to do this except to look on the Properties tab of each integration service.

Integration services are typically named to help identify the master repository, but manual review is safer.

1. Shut down all Integration Services (associated with Repository)

Select the Integration Service from the Domain hierarchy and choose the Associated Repository tab. If the Integration Service belongs to the repository, then Disable it.

2. Shut down the Repository Service
Wait for all Integration Services to be stopped (disabled)
Choose the Repository Service in the hierarchy list, and choose Disable.

3. Enable Repository Service

4. Enable each of the dependent Integration Services (from Step 1).

If Informatica is version 9.1, then

Important Note: Informatica 9.1 does not require Integration Services to be shut down prior to shutting down the Repository Service. It is safe to ‘recycle/bounce’ an Integration Service without impact to other services.

1. To bounce a service (disable/enable), simply select the recycle button

2. You can also choose the appropriate buttons in the “Actions” menu to the far right

Informatica Security and User Management

Informatica Security and User Management rely on multiple sets of tools and is a bit more complex. Each section identifies the tools needed to accomplish specific tasks. They are presented in the same

order as a process workflow to create a new user, assign permissions, and enable account security on specific objects. All tasks require the Administration Console unless otherwise noted.