Installing the Informatica Adapter
To install the Informatica adapter:
Step 1 Stop the master.
For Windows:
a. Click the Start button and then select Programs>TIDAL Software>Scheduler>Master>Service Control Manager.
b. In the Service list, verify that the master is displayed and click Stop to stop the master.
For Unix:
a. Stop the master by entering tesm stop.
b. Verify the master is stopped by entering tesm status.
Step 2 Copy the.pkg file into the config folder located in the master installation directory (there should already be a master.props file there).
Step 3 Restart the master:
a. a For Windows, click Start in the Service Control Manager.
b. b For Unix, restart the master by entering tesm start.
The Master will deploy the.pkg file and will move it from the config folder to the Services folder. An Adapter GUID directory is also created under the Services folder.
For example:
For Windows: C:\Program Files\TIDAL\Scheduler\master\services\{7640B420-5530-11DE-8812-7B8656D89593}
For Unix: /opt/TIDAL/Scheduler/master/services/ {7640B420-5530-11DE-8812-7B8656D89593}
Step 4 Restart the Enterprise Scheduler Client by clicking the Windows Start button and selecting Programs>TIDAL Software>Client>Client. When the Client connects, it will download the new package.
The next several steps involve configuring the system for use with the Informatica Adapter. Once the.pkg has been deployed you must stop the Master service and restart it after completing the following steps.
Configuring the Informatica Adapter
To Install and configure the Informatica Libraries:
Note For Unix, add the following entries in user's profile located in the user's home directory. For example:.profile or.bash_profile (Linux).
You will need to source the profile after applying all profile updates. For example,.~/.profile.
Once the following steps are performed, this will require a restart of the master for the configurations to take affect.
Step 1 Extract the library from the infalib archive to the master machine
a. Create a directory under the master services directory called infa.
b. Windows Example: C:\Program Files\TIDAL\master\services\infa\
c. Unix Example: /opt/tidal/master/services/infa
d. Extract the archive to this location. The archive distribution contains directories: lib and locale. The system will be configured to refer to these locations in the next steps.
Step 2 Configure the System Path to include the Informatica Library Path (i.e. lib directory.)
Windows Example: C:\Program Files\TIDAL\master\services\infa\lib
For Windows, include the library path in the "Path" Environment Variable.
Unix Example: /opt/master/services/infa/lib or master/services/infa/lib
For Solaris/Linux, include the library path in LD_LIBRARY_PATH.
For AIX, include the path in LIBPATH. For 64-bit also include LD_LIBRARY_PATH.
For HPUX, include the path for SHLIB_PATH.
Step 3 Create or update the INFA_DOMAINS_FILE Environment Variable to the location of the Informatica domains.infa file for the PowerCenter configuration.
This requires that the domains.infa file be local to the Master machine; copy it from your PowerCenter installation as needed. Put this file in the infa directory created in step 1a).
Note To configure connections to multiple PowerCenter servers, modify the local domains.infa file that was copied to the Master machine. Add values for the vector xml tag corresponding to each Server that will be configured as an Informatica Adapter.
The following example includes server information to two PowerCenter servers, one to Dev and another for Prod. These are referred to as dev-infa and prod-infa, respectively in the sample domains.infa file.
<Portals xmlns:common="http://www.informatica.com/pcsf/common" xmlns:usermanagement="http://www.informatica.com/pcsf/usermanagement" xmlns:domainservice="http://www.informatica.com/pcsf/domainservice" xmlns:logservice="http://www.informatica.com/pcsf/logservice" xmlns:domainbackup="http://www.informatica.com/pcsf/domainbackup" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:metadata="http://www.informatica.com/pcsf/metadata" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:domainconfigservice="http://www.informatica.com/pcsf/domainconfigservice" xmlns:alertservice="http://www.informatica.com/pcsf/alertservice" xmlns:licenseusage="http://www.informatica.com/pcsf/licenseusage" xmlns:webserviceshub="http://www.informatica.com/pcsf/webserviceshub" xsi:type="common:PCSFVector" objVersion="1.1.19">
<vector xsi:type="domainservice:Portals" objVersion="1.1.19">
<domainName>Domain_dev-infa</domainName>
<address xsi:type="metadata:NodeRef" objVersion="1.1.19">
<host>dev-infa</host>
<port>6001</port>
</address>
</vector>
<vector xsi:type="domainservice:Portals" objVersion="1.1.19">
<domainName>Domain_prod-infa</domainName>
<address xsi:type="metadata:NodeRef" objVersion="1.1.19">
<host>prod-infa</host>
<port>6001</port>
</address>
</vector>
</Portals>
Example on Windows:
INFA_DOMAINS_FILE=C:\ Program Files\ TIDAL\master\services\infa\domains.infa
Example on Unix:
Export INFA_DOMAINS_FILE=/opt/TIDAL/master/services/infa/domains.infa
Step 4 Configure the Locale Path for the Informatica Library by setting the TDLINFA_LOCALE service.props value of the Informatica Adapter. In the config directory located under the Adapter’s GUID directory, create or update the service.props file, create both the directory and file if it does not yet exist. Include an entry for TDLINFA_LOCALE that points to the Load Manager Library locale directory.
Windows Example:
C:\Program Files\TIDAL\Scheduler\master\services\{7640B420-5530-11DE-8812-7B8656D89593}\config\service.props
Unix Example:
/opt/tidal/master/services/{7640B420-5530-11DE-8812-7B8656D89593}/config/service.props
Service.props entry example:
For Windows:
TDLINFA_LOCALE=C:\\Program Files\\TIDAL\\Scheduler\\master\\services\\infalib\\locale
For Unix:
TDLINFA_LOCALE=/opt/tidal/master/services/infa/locale
Step 5 You will need access to the Database JDBC Drivers for connectivity to the PowerCenter Repository database. Obtain the JDBC jar files from the vendor as needed and copy the corresponding .jar files to the services lib directory.
Windows Example:
C:\Program Files\TIDAL\Scheduler\master\services\{7640B420-5530-11DE-8812-7B8656D89593}\lib
Unix Example:
/opt/tidal/master/services/{7640B420-5530-11DE-8812-7B8656D89593}/lib
Step 6 Reboot the Master machine on Windows as needed. Source the profile file as needed on Unix.
Step 7 Restart the master.