Installation Informatica Powercenter 9

Installation Informatica Powercenter 9.0.1 on Oracle Enterprise Linux 5.6

Ingredients:

Program	Version	Filename
Oracle Express 11G	11.2.0	oracle-xe-11.2.0-0.5.x86_64.rpm
SQL Developer	3.0	sqldeveloper-3.0.04.34-1.noarch.rpm
Informatica Powercenter	9.0.1	901HF2_Server_Installer_linux-x64.tar
Oracle Enterprise Linux	5.6	Enterprise-R5-U6-Server-x86_64-dvd.iso

For this demonstration Oracle Enterprise Linux (a.k.a. “Unbreakable Linux”) was used. Installed in a virtual environment with 1,5GB RAM and a 25GB harddisk.

In order to get Informatica Powercenter up and running on a server, you would typically need a database first. Otherwise it would be hard for the application to store it’s meta-data anywhere. Since this is an example, a not so large database was used; Oracle Express 11G.

Installation Oracle Express 11G
It’s important to check the free space in our memory first. Oracle XE needs around 4GB of swap memory for its installation. So let’s open a command line and check the memory using the commandfree

[root@fusionapps install]# free
total used free shared buffers cached
Mem: 1531688 1441668 90020 0 16128 1175480
-/+ buffers/cache: 250060 1281628
Swap: 2064376 0 2064376

Installation of the Operating System was with almost all default settings. This also means the amount of swap memory wasn’t changed. This needs to be raised before starting the installer package.

[root@fusionapps install]# dd if=/dev/zero of=/swapfile bs=1024 count=2048000
2048000+0 records in
2048000+0 records out
2097152000 bytes (2.1 GB) copied, 28.0329 seconds, 74.8 MB/s

[root@fusionapps install]# /sbin/mkswap /swapfile
Setting up swapspace version 1, size = 2097147 kB
[root@fusionapps install]# /sbin/swapon /swapfile
[root@fusionapps install]# free
total used free shared buffers cached
Mem: 1531688 1441404 90284 0 16416 1174944
-/+ buffers/cache: 250044 1281644
Swap: 4112368 0 4112368

This should do it, now onto the installation of the database itself. Locate the package and run it withrpm -i oracle-xe-11.2.0-0.5.x86_64.rpm. This should result into the following:

[root@fusionapps install]# rpm -i oracle-xe-11.2.0-0.5.x86_64.rpm
Executing post-install steps…

You must run ‘/etc/init.d/oracle-xe configure’ as the root user to configure the database.

Fine, looks alright even though you can’t see what it has done. Basically your database software is ready to be used, yet no database yet. So let’s do what the package told us to do, execute the command /etc/init.d/oracle-xe configure.

[root@fusionapps admin]# /etc/init.d/oracle-xe configure

Oracle Database 11g Express Edition Configuration
————————————————-
This will configure on-boot properties of Oracle Database 11g Express Edition. The following questions will determine whether the database should be starting upon system boot, the ports it will use, and the passwords that will be used for database accounts. Press to accept the defaults.
Ctrl-C will abort.

Specify the HTTP port that will be used for Oracle Application Express [8080]:

Specify a port that will be used for the database listener [1521]:

Specify a password to be used for database accounts. Note that the same
password will be used for SYS and SYSTEM. Oracle recommends the use of
different passwords for each database account. This can be done after
initial configuration:
Confirm the password:

Do you want Oracle Database 11g Express Edition to be started on boot (y/n) [y]:

Starting Oracle Net Listener…Done
Configuring database…Done
Starting Oracle Database 11g Express Edition instance…Done
Installation completed successfully.

At each question the answer is to hit the enter button so that the default values stay as they are. Only exception to this is where you need to enter a password for your database.
Now to test if a connection can be made to the database. Look at the top left menu and selectApplications > Oracle Database 11g Express Edition > Run SQL Command Line and review the following:

SQL> connect system/xe@xe
Connected.

SQL> select name from v$database;
NAME
—-
XE

SQL>

This looks right, the database is up and running. The installation of SQLDeveloper can begin. Note that this is not really needed, but some people prefer a more graphical way of doing their queries and other database tasks.

Installation SQLDeveloper
This installation is pretty straight forward. Look up the package and run the following from the command line: rpm –i sqldeveloper-3.0.04.34-1.noarch.rpm
This should give you:

[root@fusionapps install]# rpm -i sqldeveloper-3.0.04.34-1.noarch.rpm
[root@fusionapps install]#

Now when you look in the Applications menu, there should be a menu item called SQL Developer under the Programming submenu.

Installation Powercenter 9.0.1
In order to begin the installation of Powercenter there are some prerequisites that need to be met first:

Going through these ingredients one by one;

1.                4GB disk space, check

2.                We have an Oracle database, check

3.                Database user account is not there yet, to do

4.                Valid license key, Oracle provides one with the download from eDelivery. This isn’t meant for production purposes, but it’s very useful when trying installations like these, check

5.                Database user for domain configuration can be the same as point 4, to do

6.                Port numbers is useful to align for yourself, but since this is a totally new system we’ll use the default ports Powercenter issues (i.e. 6005-6007 and some others4GB RAM, not needed at all. For this installation a virtual machine was used with 1,5GB of RAM and it had no problem installing Powercenter at all, so check

Conclusion of the ingredients list is one more task that isn’t done yet, create a database user that Powercenter can use to do its work.

SQL> create user informatica identified by password;
User created.

SQL> grant all privileges to informatica;
Grant succeeded.

SQL>

With above statements this final task is complete as well. So with all the boxes checked the installation of Powercenter can begin.
Lookup your downloaded Powercenter installation file (901HF2_Server_Installer_linux-x64.tar) and untar it at a destination of your choice. Then it’s just a case of starting the install.sh file.

[admin@fusionappsIPC901]$ . install.sh
OS detected is Linux
unjar task is in progress………….
unjar of ESD completed…..
Do you want to continue installation (y/n) ?

Unjarring the files will take a while, obviously depending on your system specifications. When the installer asks to continue, the answer is y for yes.

Starting installation …

\***************************************************************************
\* Welcome to the Informatica 9.0.1 HotFix 2 Server Installer. *
\***************************************************************************

To verify whether a machine meets the system requirements for an Informatica installation, run the Pre-Installation System Check Tool (i9Pi) before you start the installation process. You can find the i9Pi tool in the following directory: /i9Pi

Before you continue, read the 9.0.1 HotFix 2 Installation Guide and Release Notes.
You can find the 9.0.1 HotFix 2 documentation in the Documentation Center at http://my.informatica.com Configure the LANG and LC_ALL variables to generate appropriate code pages and create and connect to repositories and Repository Services.
Do you want to continue? (Y/N)

A lot of information, so it’s wise to read them before continuing. At the end it says not to forget to set some variables. This is wise to check with the export command. When all is well, we can move on by typing y for yes again.

Installer requires operating system Linux version 2.6 and later.
Current operating system Linux version 2.6.
Current operating system meets minimum requirements.

Select a choice :
1. Install Informatica 9.0.1 with Hot Fix 2 or Upgrade from a previous version of Informatica to Informatica 9.0.1 with Hot Fix 2
2. Apply Informatica 9.0.1 Hot Fix 2 to existing 9.0.1 install.
Enter the choice(1 or 2):

Now we need to choose the installation that we want. In this case option 1 is the way to go, nothing is installed yet so no need to apply just a hotfix.

———————————————————–
Checking for existing 9.0.1 HotFix 2 product installation.
Select (G)UI mode (needs X Window support) or (C)onsole mode (G/C):

Next question is the type of installer that we want to use. Let’s be lazy and use a graphical interface (ideal for cheering up this bunch of text with some screenshots).
Launching installer in GUI mode …
Preparing to install…
Extracting the JRE from the installer archive…
Unpacking the JRE…
Extracting the installation resources from the installer archive…
Configuring the installer for this system’s environment…

Launching installer…

Preparing SILENT Mode Installation…

===========================================================================
Informatica 9.0.1 Services HotFix2 (created with InstallAnywhere)
—————————————————————————

After choosing G for GUI mode the installer will start it up with the above information. After this is done, a window opens and the graphical installer is launched.

First window let’s you choose the type of installation. Funny enough we already gave an answer to this question, but there’s no harm in answering again.

The list of prerequisites is next. You’ve seen this list before (scroll up if you missed it) and all should be good at this point. So onto the next one.

This is where we actually need to do something; showing the installer where our license key is located and where Powercenter should be installed.

The installer then gives you a small summary of what was chosen. If this looks good then the actual installation can begin by pressing the Install button.

Configuration is the next task the installer wants to do. For this fresh installation we’ll be making a brand new domain. If for any reason there is a need to join an already existing domain then the second option is the way to go.

As per default the HTTPS option is enabled. No reason to untick it if you don’t have or don’t want to add a legitimate certificate. The installer can make a dummy one for you. Not only in this case, but also with a production machine this would be harmless. Simple reason is that Powercenter is installed based on the hostname. So if you’re not on that hostname, you can’t login to the administration console. This basically means that by default you can’t use the administration console outside of the server. This can be configured however, so when you decide to do that, it would be wise to install legitimate certificates.

Next the installer wants to know where to install all its information. This is where the database user informatica comes in. And since the database is on the same machine as Powercenter will be, it’s no problem using localhost as the address for the database.

By using the button Test connection the installer enables you to check if you didn’t make any typo’s:

Final window before the Powercenter installation is properly configured is where information is requested on the domain that needs to be created.

And if all goes well, the last screen you’ll see is the one below stating this installation was a success.

And there you go, a freshly installed Informatica Powercenter 9.0.1. Ready to be decorated with repositories and to be used with (for example) Oracle Fusion Applications feeding Oracle BI components.