UNIX Installation Guide

Informatica SSA-NAME3 (Version 9.0.00)

c

1998–2009, Informatica Corporation. All rights reserved. All logos, brand and product names are or may be trademarks of their respective owners. THIS MANUAL CONTAINS CONFIDENTIAL INFORMATION AND IS THE SUBJECT OF COPYRIGHT, AND ITS ONLY PERMITTED USE IS GOVERNED BY THE TERMS OF AN AGREEMENT WITH INFORMATICA CORPORATION, OR ITS SUBLICENSORS. ANY USE THAT DEPARTS FROM THOSE TERMS, OR BREACHES CONFIDENTIALITY OR COPYRIGHT MAY EXPOSE THE USER TO LEGAL LIABILITY. Created on Wednesday 25th November, 2009.

Contents Table of Contents

3

Introduction

4

Installation Contents of the SSA-NAME3 Extensions Installation CD . . . . . . . . . . Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1: Transfer and extract the SSA-NAME3 Extensions software . . Step 2: On Unix, Set Up the SSA-NAME3 Environment Variables . . Step 3: On Unix, Create a Working Directory . . . . . . . . . . . . . . Step 4: On the PC, Install and Test the Installation of SSA-NAME3 . . Step 5: On the PC, Prepare and Transfer the Service Group Data File Step 6: On Unix, Create the Shared Object . . . . . . . . . . . . . . . . Step 7: On Unix, Test the Installation with Test-bed . . . . . . . . . . .

3

CONTENTS

. . . . . . . . .

. . . . . . . . .

. . . . . . . . .

. . . . . . . . .

. . . . . . . . .

. . . . . . . . .

. . . . . . . . .

. . . . . . . . .

. . . . . . . . .

. . . . . . . . .

. . . . . . . . .

5 5 5 5 6 6 7 7 7 8

Introduction Installers should follow the G ETTING S TARTED and PC I NSTALLATION manuals in conjunction with this installation documentation.

The installation and installation testing of the SSA-NAME3 Development and Run-time environment on a Unix system should be done in parallel with the installation and installation testing of the SSANAME3 Generation environment on the PC. The combined PC and Unix installation and installation testing steps are shown below: 1. On Unix, install the SSA-NAME3 development and run-time environments. 2. On Unix, create a working directory in the SSA-NAME3 development environment. 3. On the PC, install and test the installation of the SSA-NAME3 generation environment on the PC. 4. On the PC, prepare the Service Group Data File (n3sgxx.ysg) and transfer it to the working directory on the Unix platform (created in Step 2). 5. On Unix, set up the SSA-NAME3 environment variables. 6. On Unix, create the shared object that will invoke the Service Group Data File. 7. On Unix, using Test-bed, test the installation and compare the results with the test done on the PC. The results should be the same to confirm a successful installation. The following section details each of these steps. For some of the steps, the reader will be pointed to the PC Installation manual

4

Installation A list of the resources and pre-requisites required to install SSA-NAME3 is provided in the G ETTING S TARTED manual, but it is worth repeating two points here:1. The Unix system must have an ANSI standard C compiler installed prior to testing the installation of SSA-NAME3. 2. SSA-NAME3 9.0must be installed before SSA-NAME3 Extensions can be installed..

Contents of the SSA-NAME3 Extensions Installation CD The UNIX installation is supplied on CD as a compressed tar file. The file name will follow the following convention:nme_NNNN_[_FIXTAG]_TARGET.ZIP

Where nme denotes the product - SSA-NAME3 Extensions. NNNN denotes the release. (e.g. 9000) FIXTAG If present, denotes the fix level. (eg. 001) TARGET denotes the environment in which this release will run. DEMO If present, this is a demo version. For instance, the filename on the supplied CD might be: nme_9000_solaris_sparc_64.zip

Installing the Software Step 1: Transfer and extract the SSA-NAME3 Extensions software FTP the compressed tar file (from the CD or from a copy made to your disk) to the target machine in binary mode into a selected home directory. E.g ftp bin cd ids put nme_9000_solaris_sparc_64.zip

Unzip the file using the command: unzip nme_9000_solaris_sparc_64

5

INSTALLATION

Change directory to the top level directory of the (already installed) SSA-NAME3 installation. cd ids/nm39000

Then untar the file using the command: tar -xf /ids/nme_9000_solaris_sparc_64.tar

This will extract all the necessary files.

Step 2: On Unix, Set Up the SSA-NAME3 Environment Variables The SSA-NAME3 environment variables on Unix now need to be setup. Note: The SSA-NAME3 scripts were designed to be used under the Bourne shell. If you are running another shell, you need to start the Bourne shell with the sh command.

To establish the required environment, cd ids/nm32501 . ./ssaset . $SSATOP/ssaset

The environment is now ready for the shared object to be generated which will link to the Service Group Data File transferred from the PC in the previous step.

Step 3: On Unix, Create a Working Directory At this stage, the country for which the installation testing will be performed should have been decided upon. Create a working directory for that country. This directory will eventually hold the Service Group Data File from the PC. The name of this new directory should begin with the characters ’my’, followed by the name of the country’s directory as will be installed on the PC. These directory names are listed in the Definition File Overview section of the D EFINITION & C USTOMIZATION G UIDE. For example, if ’usa’ was the country directory name, the new directory would be called ’myusa’. On the Unix system, cd $SSATOP/ssaname mkdir my country

For example, if the country you are testing the installation for is the usa; On the Unix system, cd $SSATOP/ssaname mkdir myusa

If you will later be customizing for more than one country’s data, you can create a working directory for each now. Installing the Software

6

Step 4: On the PC, Install and Test the Installation of SSA-NAME3 Proceed now with the installation and installation testing of the PC components as described in the PC I NSTALLATION manual.

Step 5: On the PC, Prepare and Transfer the Service Group Data File Proceed now with the preparation of the Service Group Data File as described in the PC I NSTALLATION manual. Next, transfer the data file to the Unix working directory created in Step 2, as described in the PC I NSTALLATION manual.

Step 6: On Unix, Create the Shared Object For any application program calling SSA-NAME3, it will call a shared object that is created in this step. Change to the working directory where the PC files were transferred to, i.e. cd ssaname/my country

For example, cd ssaname/myus

Create the shared object using the Informatica Corporation supplied gendll command: $SSABIN/gendll

For example: $SSABIN/gendll n3sgus

This example assumes that you use the SSA-NAME3 naming standard for your Service Group, i.e. file names start with "n3". After this step the library n3sgus.so can access the Service Group Data File (n3sgus.ysg). The Data File contains the algorithm rules from the Fast-start Definition files that were generated on the PC. At runtime it is necessary to set an environment variable SSAUSGDIR that references the directory containing the Service Group Data File. For Example, SSAUSGDIR="$HOME/ids/ssaname/myusa" export SSAUSGDIR

and the shared object should be available within the system search path. 7

INSTALLATION

Step 7: On Unix, Test the Installation with Test-bed Finally, execute the Test-bed. The testbed executable will load the Service Group Data file (.ysg) from the current directory. Note that testbed does not use the SSAUSGDIR environment variable nor does it require the shared object generated in Step 6. Execute Test-bed as follows, $SSABIN/testbed testout.uni

Check the results of the Test-bed execution by editing or viewing the file testout.uni. The results should look something like is shown below. The main item to check is that the Response Code (RESP) is zero, as highlighted below. The other data may be different than what is shown below depending on what fast-start country is being used. If any doubts exist as to the success of this Test-bed execution, call Informatica Corporation Technical Support. PGM: TESTBED TST 1.8.2.07SOLARIS Nov 22 2007 10:47:07 DONE: TESTBED --DONE-Nov 22 2007 14:56:07 USG: S_MDT MDT 1.8.2.0900255YLN5NY SERVICE GROUP NAME: n3sgus NOTE: THIS PROGRAM CONTAINS CONFIDENTIAL INFORMATION AND IS THE SUBJECT OF COPYRIGHT, AND ITS ONLY PERMITTED USE IS GOVERNED BY THE TERMS OF AN AGREEMENT WITH INFORMATICA CORPORATION, OR ITS SUBLICENSORS. ANY USE THAT DEPARTS FROM THOSE TERMS, OR BREACHES CONFIDENTIALITY OR COPYRIGHT MAY EXPOSE THE USER TO LEGAL LIABILITY. SERVICE: TYPE: ALG: WSIZE: RESP: FUNC: INPUT:

NAMESETP NAMESET PERSON 4359 SSIZE: 1396 00 ** TESTING NAME

+

TESTING NAME

+

+ OUTPUT: + STACK: 02 1 TESTING 2 NAME KEYS: 02 1 F43366BE42 A1 2 DAE4039334 A1 STAB: DAE4039334 1 DAE4039334 DAE4039337 60 2 DAE4039000 DAE40393FF 68 3 DAE4037800 DAE40393FF 70 4 DAE4000000 DAE403FFFF 75 5 DAC0000000 DAFFFFFFFF 93 6 D6C0000000 DAFFFFFFFF 95 7 0000000000 FFFFFFFFFF 00 CATS: . WORK: A1 SSA-NAME3 TESTBED PROCESSING

Y M Y

00 00 00 06 27 37 49

T N

20 12 11 10 02 01 00

A1 A2 A3 A4 A7 A8 A9

TASTANG NAN

C C C C C C C

00 00 00 00 00 00 00 00003100000000310000

COMPLETE

Installing the Software

8

Now, compare the output from the Test-bed run on Unix with the output from the Test-bed run on the PC as follows, diff testout.pc testout.uni > diffs

View the diffs file. There may be some differences in lines that have date stamps and that report work area sizes etc. If there are no differences in the name output and keys then the installation was successful.

9

INSTALLATION