Installing Pipeline Manager

Installation Overview

To install and configure Pipeline Manager, follows the steps in these sections:

Determining Your System Requirements

Before you install Pipeline Manager, ensure that requirements described in this section are met.

Hardware Requirements

Pipeline Manager requires the hardware listed in Table 75-1.

Table 75-1 Pipeline Manager Required Hardware

Component	Requirements
CPU	4 or more CPUs
RAM	More than 4 GB (to use 54-bit)
Disk Type	RAID disc array (RAID 5 hardware solution with appropriate cache strongly recommended, RAID 0 software solution)

Note:

The more pipelines you configure and the more CPUs you use, the more important it is to put input and output on systems that are managed by different Controllers.

Software Requirements

Pipeline Manager requires the following software:

Oracle Database server
Oracle Database client
Java Runtime Environment (JRE)

See "BRM Software Compatibility" in BRM Compatibility Matrix for the supported software versions.

Creating a User and Configuring Environment Variables

Follow these steps to create a Pipeline Manager user and set up system environment variables on a system:

Create a user that owns the Pipeline Manager software. The examples in this document use the default user integrate with the bash shell as the default shell.

Note:

You must create a Pipeline Manager user and set the user's environment before installing Pipeline Manager.
Log in as user integrate.
Go to the pipeline_home directory.
Open the source.me.sh file for your shell in a text editor.

Note:

The source.me file is for a bash shell. If you use a C shell, open the source.me.csh file.

Set the following environment variables for Pipeline Manager using the information in Table 75-2:

Table 75-2 Pipeline Manager Environment Variables

Environment Variable	Description
IFW_EVENTHANDLER_PORT	The port number on which the event handler daemon listens for events. Important: If you are starting more than one framework process, change the value of this parameter before starting each process. Each process must have a unique event handler port for all users on a host. A framework process will not start if it cannot start the event handler daemon, and the event handler daemon will not start if it cannot listen on the specified port. Do not set this variable to a well-known port number, such as port 11960 used by BRM.
IFW_HOME	The directory where the Pipeline Manager software is installed. Note: This documentation refers to this directory as the pipeline_home.
LD_LIBRARY_PATH	The library path. Set this to include pipeline_home/lib. If your system already has this variable set to another value for other applications, Pipeline Manager might not find the proper libraries. To determine if a pre-existing value is present, enter the following command: echo $LD_LIBRARY_PATH If the variable is already set in your system, add the new variable as follows: export LD_LIBRARY_PATH=${LD_LIBRARY_PATH};pipeline_home/lib C shell: setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH};pipeline_home/lib Important: After your first upgrade reset the LD_LIBRARY_PATH environment variable to the following: setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH};BRM_home/lib;pipeline_home/lib where BRM_home/lib must come before pipeline_home/lib, separated by a semicolon.
MALLOC_TRIM_THRESHOLD_ MALLOC_MMAP_MAX_ MALLOC_TOP_PAD_	On Linux Pipeline Manager platforms, modify the MALLOC_TRIM_THRESHOLD_, MALLOC_MMAP_MAX_ and MALLOC_TOP_PAD_ environment variables with these values: MALLOC_TRIM_THRESHOLD_ = -1 MALLOC_MMAP_MAX_ = 0 MALLOC_TOP_PAD_ = 268435456
MAX28DIGIT_DECIMAL_SUPPORT	By default, Pipeline Manager supports 15-digit decimal. To configure Pipeline Manager to support up to 28-digit decimal, set this to Y.
NLS_LANG	Set this to LANG American_America.AL32UTF8. Important: You must use American_America as the language and territory regardless of your locale and the UTF8 or AL32UTF8 character set. BRM 15.0 supports AL32UTF8 as its default character set. It also continues to support the UTF8 character set for BRM installations that are being upgraded to BRM 15.0 from previous versions. The unicode character set AL32UTF8 is recommended for all new BRM 15.0 deployments.
PATH	The Pipeline Manager executable path. Set this to include pipeline_home/bin.
IFW_EVENTHANDLER_PORT	The port number on which the event handler daemon listens for events. Important: If you are starting more than one framework process, change the value of this parameter before starting each process. Each process must have a unique event handler port for all users on a host. A framework process will not start if it cannot start the event handler daemon, and the event handler daemon will not start if it cannot listen on the specified port. Do not set this variable to a well-known port number, such as port 11960 used by BRM.

Save and close the updated file.
Update the environment for the current shell session:

For bash shell:
```
source source.me.sh
```
C shell:
```
source source.me.csh
```

Setting the Maximum Allowed Number of Open Files

To avoid causing a failure of Pipeline Manager, you must configure the maximum number of pipeline files allowed per process in the kernel. The recommended value is 2048. You should also set the maximum number of open files allowed for the system to 20480 (ten times the number of files per process).

To modify the number of open files allowed:

(Linux) Setting Maximum Open Files on Linux

(Linux) Setting Maximum Open Files on Linux

To set the maximum open files on Linux:

Log on as root.
Open the system file (/etc/sysctl.conf).
Add the following lines to the end of the file, or modify the values if these lines are already present:
```
# sets the hard limit on file descriptors:
fs.file-max = 2605192
```
Run sysctl -p to reload all the settings from the system file.

Installing Pipeline Manager

This section describes how to install and uninstall Pipeline Manager.

Note:

If you are installing Pipeline Manager to replace an identical release (for example, to restore a clean version of the package), you must first uninstall the existing installation. See "Uninstalling Pipeline Manager".

To install Pipeline Manager, see "Installing Individual BRM Components" in BRM Installation Guide.

Note:

Ensure that SSL/TLS is enabled in real-time and batch pipelines. See Enabling SSL/TLS in Real-Time Pipeline and Enabling SSL/TLS in Batch Pipeline in BRM System Administrator's Guide.

To upgrade Pipeline Manager, see "Upgrading BRM and Pipeline Manager from BRM 12.0 to BRM 15.0" in BRM Installation Guide.

Uninstalling Pipeline Manager

To uninstall Pipeline Manager, see "Uninstalling Optional Components" in BRM Installation Guide.

Pipeline Manager Directory Structure

Installation creates the following directory structure shown in Table 75-3:

Note:

pipeline_home is the default Pipeline Manager installation directory.

Table 75-3 Directory Structure Created by Pipeline Manager Installation

Directory	Description
pipeline_home/bin/	Server binaries, such as the main Pipeline Manager binary ifw.
pipeline_home/conf/	Contains registry files.
pipeline_home/data/	Contains source and directory files for EDRs.
pipeline_home/database/	Database creation scripts and database documentation.
pipeline_home/discount/	Balance Data Module transaction and data.
pipeline_home/etc/	Error messages. Note: You can copy the error messages to another directory and customize them; for example, as preparation for translation into other languages.
pipeline_home/formatDesc/	External file format definitions and internal container definitions.
pipeline_home/info/	Info registry, which shows the current system status.
pipeline_home/instrumentation/	Performance Data collection.
pipeline_home/iScriptLib/	iScript libraries.
pipeline_home/lib/	Shared libraries.
pipeline_home/lib64/	Shared libraries (64-bit)
pipeline_home/log/	Process log.
pipeline_home/releaseNotes/	Release notes.
pipeline_home/samples/	Sample registries that you can use for testing your Pipeline Manager setup.
pipeline_home/semaphore/	Directory that is checked regularly for semaphores.
pipeline_home/tools/	The tools such as binaries and Perl scripts.

Installing Pipeline Manager Optional Components

This section describes how to install the following Pipeline Manager optional components:

Pipeline Configuration Manager
Pipeline PDK Manager
Interconnect Manager
CIBER Roaming Manager

Note:

Before you install CIBER Roaming Manager and TAP Roaming Manager, you must install Interconnect Roaming Manager.
TAP Roaming Manager

The hardware and software requirements for CIBER Roaming Manager and TAP Roaming Manager are the same as for Pipeline Manager. For more information, see "Installing Pipeline Manager".

For more information on configuring roaming in Pipeline Manager, see BRM Configuring Roaming in Pipeline Manager.

Before installing Pipeline Manager optional components, you must install:

BRM.
Pipeline Manager.

Note:

If you are installing the optional components to replace an identical release (for example, to restore a clean version of the package), you must first uninstall the existing installation. See "Uninstalling Pipeline Manager Optional Components".

To install Pipeline Manager optional components, see "Installing Individual BRM Components" in BRM Installation Guide.

Uninstalling Pipeline Manager Optional Components

To uninstall Pipeline Manager optional components, see "Uninstalling Optional Components" in BRM Installation Guide.

Increasing Heap Size to Avoid “Out of Memory" Error Messages

To avoid "Out of Memory" error messages in the log file after installation, increase the maximum heap size used by the Java Virtual Machine (JVM). The exact amount varies greatly with your needs and system resources. By default, the JVM used has a maximum heap size of 60 MB. Increase the maximum heap size to 120 MB by entering the following sample code in a text editor:

%IF_EXISTS%("INIT_JAVA_HEAP", "@INIT_JAVA_HEAP@20m") %IF_EXISTS%("MAX_JAVA_HEAP", "@MAX_JAVA_HEAP@120m")

where 20m and 120m indicate the minimum and maximum heap sizes respectively.

Save the file as Packagename.ja in the temporary directory (temp_dir) to which you downloaded the installation software.

Packagename indicates the name of the installation software.

Configuring an Oracle Pipeline Manager Database

This section describes how to configure the Pipeline Manager database on Oracle.

Before proceeding, you should be familiar with executing database scripts.

Before setting up the Oracle database for Pipeline Manager, ensure the following:

An Oracle database instance is mounted and open.
You have administrator access to the database instance.

To install and configure the Pipeline Manager database, follow the steps in these sections:

Setting the Environment for the Pipeline Manager Database

Before setting up the database schemas for your Oracle Pipeline Manager database, you must configure database environment variables.

Open the configuration file for the login shell. This is the file in which your user profile is stored; for example, .profile or .bashrc. By default it is stored in your home directory.

Change the following variables in Table 75-4 to match your Pipeline Manager environment:

Table 75-4 Environment Variables of Pipeline Manager Database

Environment Variable	Description
ORACLE_HOME	Include or set this variable to point to the Oracle installation path.
LD_LIBRARY_PATH	(32-bit systems) Include or set entries to point to the database /lib directories. Example for Oracle databases: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib32:$ORACLE_HOME/rdbms/lib32
LD_LIBRARY_PATH_64	(64-bit systems) Include or set entries to point to the database /lib directories. Example for Oracle databases: LD_LIBRARY_PATH_64=$IFW_HOME/lib:$ORACLE_HOME/lib:$ORACLE_HOME/rdbms/lib
PATH	Include or set entries to point to the database /bin directory. Example for Oracle databases: ${ORACLE_HOME}/bin

Save and close the file.

Setting Up the Oracle JSA Database Schema

This section describes how to run scripts to set up the Oracle JSA database schema.

Run the scripts described in the following steps to set up the database schema for the JSA tables and tablespaces:

Note:

All scripts are located in the pipeline_home/database/Oracle/Scripts directory.

Open the JSA_Tablespaces.sql file with a text editor.
Replace all occurrences of the string *** with the path to the Oracle tablespace data file.
Save the file.
Log in as user database administration (DBA).
Run the JSA_Tablespaces.sql script.

This script creates the tablespaces for the JSA server.
Run the JSA_Roles.sql script.

This script creates roles and the default JSA user.
Log out and log in as user JSA.
Run the JSA_Create.sql script.

This script creates the JSA tables.
Run the JSA_Synonyms.sql script.

This script creates the JSA public synonyms.
Run the JSA_Prepare.sql script.

This script inserts some default values into the tables.

The Oracle JSQ database schema is now set up.

Setting Up the Oracle Pipeline Manager Framework Database Schema

To set up the database schema for the Pipeline Manager framework work tables and tablespaces:

Note:

All scripts are located in the pipeline_home/database/Oracle/Scripts directory.

Open the ifw_Tablespaces.sql file with a text editor.
Replace the occurrences of the string ORA_DAT_PATH and ORA_IDX_PATH with the path that leads to the *.dbf files shown in the script file.
Save the file.
Log in as user DBA.
Run the ifw_Tablespaces.sql script.

This script creates the tablespaces for the Pipeline Manager framework.
(Optional) Change the default Pipeline Manager user name (pipeline_user) from integrate to another name:
1. Open the ifw_Roles.sql file by using a text editor.
2. In the User: INTEGRATE section, replace the two occurrences of INTEGRATE in the following string with the new default user name:
```
INTEGRATE identified by INTEGRATE
```
3. In the GRANT commands that follows the QUOTA commands in the User: INTEGRATE section, replace all occurrences of INTEGRATE with the new default user name.
4. Save the file.
Run the ifw_Roles.sql script.

This script creates the appropriate roles and the default user.
Log out and log in as pipeline_user.
Run the ifw_Create.sql script.

This script creates the Pipeline Manager framework tables.
Run the ifw_Synonyms.sql script.

This script creates the public synonyms.

The Oracle Pipeline Manager framework database schema is now set up.

You can create only one instance of the pipeline schema in a particular database. You can create multiple users and give permission to access the same tables. Creating multiple instances lead to public synonym conflict.

To avoid public synonym conflicts in a multiuser environment, change the public synonyms to private synonyms for specific users. See "Changing Public Synonyms to Private for Users in Multiuser Environments" for more information.

For example, if you create table1 for user1, you can create user2 and assign permissions to access table1. Typically, you access the table as user1.table1. However, using synonyms, you can directly access the table as table1. No prefix (user1) is required.

Changing Public Synonyms to Private for Users in Multiuser Environments

Changing public synonyms to private synonyms for a user is required for avoiding public synonym conflict in a multiuser environment.

Note:

All scripts are located in the pipeline_home/database/Oracle/Scripts directory

To change public synonyms to private synonyms for a user:

Connect to the Oracle database with SQL*Plus:
```
% sqlplus system@databaseAlias
Enter password: password
```
where databaseAlias is the database alias of the Oracle database.
Drop the public synonyms for IFW tables for the user.
Grant CREATE ANY synonym access to the user you created for the Pipeline Manager tables. For example:
```
SQL> CREATE ROLE synonym_role;
SQL> GRANT CREATE ANY SYNONYM TO synonym_role;
SQL> GRANT synonym_role TO pin_user;
```
where pin_user is the BRM user.
Open the ifw_Synonyms.sql file with a text editor.
Remove the occurrences of the string public and add the Pipeline Manager database user. For example, for ifw_SEQ_AGGREGATION table, change the string to:
```
create synonym ifw_SEQ_AGGREGATION for ifw_user.ifw_SEQ_AGGREGATION;
```
where ifw_user is the is the Pipeline Manager database user.
Save the file.
Run the ifw_Synonyms.sql script.

This script creates the private synonyms for the user.
Exit SQL*Plus.

The public synonyms are now changed to private synonyms for the user.

Loading Procedures for FCT_DuplicateCheck

Before using the FCT_DuplicateCheck module, you must load the duplicate check stored procedures in the Pipeline Manager database:

Load the DuplicateCheck_Oracle.plb file from pipeline_home/database/Oracle/Scripts/DuplicateCheck.
Verify that there is an unique index BIDX_DUPCHK_DATA on the DATA column of the IFW_DUPLICATECHECK table. If not, then create it before starting Pipeline Manager.

The duplicate check stored procedures are now loaded.

Encrypting the Database Password

If your database is encrypted, use the pin_crypt_upgrade utility to migrate your data, and then use the pin_crypt_app utility to encrypt the Pipeline Manager password.

Go to the BRM_home/bin directory.
Run the pin_crypt_app utility with the -useZT parameter:
```
pin_crypt_app -useZT -enc
```
At the prompt, enter the plaintext password to encrypt.
At the next prompt, re-enter the plaintext password.

The output is the OZT-encrypted password.
Write down the encrypted password or copy it to a text editor.
Open the Pipeline Manager startup registry file.
In the DataPool section, enter the user name, encrypted password, and database name.

For example:
```
UserName     = INTEGRATOR
PassWord     = &ozt|0D5E11BFDD97D2769D9B0DBFBD1BBF7EE03F1642861DFA57502C7FB85A654267
DatabaseName = IFWDB
```
Note:

Be sure that these lines are not commented. (The default is commented).
Save the registry file.

Note:

You can align data keys with the pin_crypt_upgrade utility using the -a parameter:

pin_crypt_upgrade -a

What's Next?

You have installed Pipeline Manager and required optional components. To install Pipeline Configuration Center, see "Installing Pipeline Configuration Center" in BRM Installation Guide.