How to find the Informatica service Processes

Below are some of the process names you should be knowing while working on Informatica issues or checks.

1. java
2. _Adminconsole
3. pmrepagent
4. pmserver
5. pmdtm

1. Java and Adminconsole:

java process is the main process in informatica powercenter which starts the node. If the node is configured as Gateway node, then it will spawn another process which will run admin console.

Apart from node process, there are other java processes also runs if you have configured multiple services such as Metadata Manager Service, Model Repository service, Web Service hub etc,.

2. pmrepagent:

If you want to search for power center repository service process, then search for pmrepagent. If there are multiple processes, you need to check the logs in admin console for the respective PID.

3. pmserver:

pmserver refers to the Integration service process. If the Integration service runs on grid, you will find the process on all the nodes in grid. If it is configured as primary and secondary nodes, then it will be available on only one node.

4. pmdtm:

pmdtm is the process spawned by the workflow which is also called the session task processs. When you see number of pmdtm jobs running on server then all the process are running different sessions.


If you want to get updates on new posts, click the follow button below.

What are the checks to be performed before using pmrep deployment group?

The following are the commands to be run:

1. Login to Host1 and run the following:

cd $INFA_HOME/server/bin

./pmrep connect -r <rep_name> -d <domain_name> -n <username> -x <password> -sdn <Native/LDAP domain>

2. Login to Host2 and run  the following:

cd $INFA_HOME/server/bin

./pmrep connect -r <rep_name> -d <domain_name> -n <username> -x <password> -sdn <Native/LDAP domain> 

If the $INFA_HOME/server/bin is in PATH environment variables then you can the pmrep command from anywhere.

3. Check if the below objects are created if you are using dynamic deployment groups in source repository. 

• Label
• Query

4. Check if you are able to connect source repository from target host where you run the deployment or vice versa.

The username (and password) is the one that you use to connect to the repository through the power center clients (such as repository manager).

The sdn is the security domain which is either Native or the LDAP domain. (enter the same details as the one on the PowerCenter client).

The Connect command uses the following syntax:

pmrep help connect

-r <repository_name> {-d <domain_name> |

{-h <portal_host_name>

-o <portal_port_number>}}

[{ <user_name>

[-s <user_security_domain>] [-x <password> |

-X <password_environment_variable>]} |

-u <connect_without_user_in_kerberos_mode>] [-t <client_resilience>]

To use -X option configure INFA_DEFAULT_DOMAIN_PASSWORD on UNIX:

1. At the command line, type:

pmpasswd <password>

pmpasswd returns the encrypted password.

2. In a UNIX C shell environment, type:

setenv INFA_DEFAULT_DOMAIN_PASSWORD <encrypted password>

    In a UNIX Bourne shell environment, type:

export INFA_DEFAULT_DOMAIN_PASSWORD=<encrypted password> 

Enable root user in Mac Terminal

By default in Mac, root user will be in disabled state. And hence the bash terminal will not login as root.
Use the below command to enable the root user run Mac and login as root.

1. Open the Terminal and run the below command. First enter the user password and then enter the new password for root user.

bash-3.2$ dsenableroot

username = abc

user password:

root password:

verify root password:

dsenableroot:: ***Successfully enabled root user.

bash-3.2$ su - root

Password:

abc-MBP:~ root# id

uid=0(root) gid=0(wheel) groups=0(wheel),1(daemon),2(kmem),3(sys),4(tty),5(operator),8(procview),9(procmod),12(everyone),20(staff),29(certusers),61(localaccounts),80(admin),701(1),33(_appstore),98(_lpadmin),100(_lpoperator),204(_developer),250(_analyticsusers),395(com.apple.access_ftp),398(com.apple.access_screensharing),399(com.apple.access_ssh)

abc-MBP:~ root#

Unix Command to check last reboot

Run the below command to check the last reboot and shutdown time.

Last reboot: This will show all the available entries for reboot. Refer last entry for latest reboot time.
$ last reboot

reboot    ~                         Sat Apr  7 21:58 

reboot    ~                         Sat Apr  7 21:01 

reboot    ~                         Thu Mar 29 16:33 

wtmp begins Thu Mar 29 16:33

$

Last Shutdown: This will show all the available entries for reboot. Refer last entry for latest shutdown time.
$ last shutdown

shutdown  ~                         Thu Apr 19 00:59 

shutdown  ~                         Tue Apr 17 10:34 

shutdown  ~                         Sat Apr  7 21:11 

shutdown  ~                         Thu Mar 29 16:39 

wtmp begins Thu Mar 29 16:33 

$