Scribd
Upload
100 views1 page

Informatica WKF in Unix

The document provides instructions for setting environment variables and paths for Informatica and running workflows using pmcmd commands. It also describes how to create scripts with pmcmd commands to check the status of Integration Services on a regular basis. An example UNIX shell script is given that uses pmcmd commands like pingservice, getserviceproperties, and gettaskdetails to check the status of a test Integration Service and get details of a session task if the service is running.

Uploaded by

utagore58
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
100 views1 page

Informatica WKF in Unix

The document provides instructions for setting environment variables and paths for Informatica and running workflows using pmcmd commands. It also describes how to create scripts with pmcmd commands to check the status of Integration Services on a regular basis. An example UNIX shell script is given that uses pmcmd commands like pingservice, getserviceproperties, and gettaskdetails to check the status of a test Integration Service and get details of a session task if the service is running.

Uploaded by

utagore58
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

First set the informatica bin directory in PATH Do these in .bashrc or .kshrc or .shrc PATH=/u01/Informatica/9.0.1/server/bin:$PATH export PATH LD_LIBRARY_PATH=/u01/Informatica/9.0.

1/server/bin: $LD_LIBRARY_PATH export LD_LIBRARY_PATH PATH=/u01/Informatica/9.0.1/tomcat/bin:$PATH export PATH INFA_HOME=/u01/Informatica/9.0.1 export INFA_HOME Then run pmcmd startworkflow -sv <Integration Service Name> -d <Domain Name> -u <Integrat ion Service Username> -p <Password> -f <Folder Name> <Workflow> That's it, now you can monitor the workflow progress in Workflow Monitor. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------When you use pmcmd, you might use some commands with specific options and argume nts on a regular basis. For example, you might use pmcmd to check the status of the Integration Service. In this case, you can create a script or batch file to call one or more pmcmd commands including its options and arguments. You can run scripts in command line mode. You cannot run pmcmd scripts in intera ctive mode. For example, the following UNIX shell script checks the status of Integration Se rvice "testService," and if it is running, gets details for session "s_testSessi onTask": #!/usr/bin/bash # Sample pmcmd script # Check if the service is alive pmcmd pingservice -sv testService -d testDomain if [ "$?" != 0 ]; then # handle error echo "Could not ping service" exit fi # Get service properties pmcmd getserviceproperties -sv testService -d testDomain if [ "$?" != 0 ]; then # handle error echo "Could not get service properties" exit fi # Get task details for session task "s_testSessionTask" of workflow # "wf_test_workflow" in folder "testFolder" pmcmd gettaskdetails -sv testService -d testDomain -u Administrator -p adminPass -folder testFolder -workflow wf_test_workflow s_testSessionTask if [ "$?" != 0 ]; then # handle error echo "Could not get details for task s_testSessionTask" exit fi

You might also like