Sunday, 12 May 2019

Informatica Linux Installation

TABLE OF CONTENTS


1 Overview
2 Download Software
3 Setup of Database Parameters, Users & Tablespace
3.1 Database Parameter
3.2 Repository Account
3.3 Repository Tablespace
4 Operating System
4.1 Processor
4.2 Temporary Disk Space Requirements
4.3 UNIX User Account
4.4 Port Validation
5 Environment Variables
5.1 Obtain the locale values
6 File Descriptor
7 Installation directory and Permission
8 Pre-Installation System Check
9 Initial Server Software Installation
10 Port Configuration
10.1 Guidelines for Port Configuration


1 Overview

This document is for informatica administration team, providing the detailed steps on installation of Power Center 9.1 on Linux & Oracle Environment.

2 Download Software

Download Software from informatica Corporation and make sure to get proper keys based on environment (Dev/ Prod).

3 Setup of Database Parameters, Users & Tablespace

3.1 DATABASE PARAMETER

Set the open_cursors parameter to 1000
SQL> SHOW parameter open_cursor;

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
open_cursors integer 300
SQL> ALTER system SET open_cursors=1000;

System altered.

SQL> ALTER system SET open_cursors=1000 SCOPE=BOTH;

System altered.

SQL> SHOW parameter open_cursors;

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
open_cursors integer 1000

3.2 REPOSITORY ACCOUNT

At least two database user accounts (Domain and Repository) are required to host repository, Taking sample names as
USER_REP for the repository Database
USER_DOM for the domain Configuration Database
Both user need to create with the CONNECT, RESOURCE, and CREATE VIEW privileges.
For Oracle, you must perform the following instruction:
CREATE USER USER_REP IDENTIFIED BY USER_REP
DEFAULT tablespace users
TEMPORARY tablespace temp
quota unlimited ON users;

GRANT CONNECT, resource, CREATE VIEW TO USER_REP;

CREATE USER UASER_DOM IDENTIFIED BY USER_DOM
DEFAULT tablespace users
TEMPORARY tablespace temp
quota unlimited ON users;

GRANT CONNECT, resource, CREATE VIEW, SELECT ANY dictionary TO USER_DOM;

The grant "select dictionary privilege" to the user INFA_DOM is only needed to verify the parameter Open_Cursor during the prerequisite check.

3.3 Repository Table-space

Set the storage size for the table-space to a small number to prevent the repository from using an excessive amount of space.
Also verify that the default tablespace for the user that owns the repository tables is set to a small size. The following example shows how to set the recommended storage parameter for a tablespace named PC_TABLESPACE.
ALTER TABLESPACE "PC_TABLESPACE" DEFAULT STORAGE ( INITIAL 10K NEXT 10K MAXEXTENTS UNLIMITED PCTINCREASE 50 );

4 Operating System

4.1 Processor

Verify that the process match the software (x86_64)
Display the Linux platform = uname - p
List the basic system information, OS release, and OS version = uname -orv
-bash-3.2$ uname -p
x86_64

-bash-3.2$ uname –arv

Linux ServerName 12.66.18-164.el5 #1 SMP Thu Sep 3 04:15:13 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

4.2 TEMPORARY DISK SPACE REQUIREMENTS

The installer writes temporary files to the hard disk. When the installation completes, the installer deletes the temporary files and releases the disk space.
Installer UNIX
1 GB
Informatica Services UNIX
2 GB
Verification of the temporary space with the df
-bash-3.2$ df -h /tmp

4.3 UNIX USER ACCOUNT

On UNIX, create a user account infa91 specifically to run the Informatica daemon required for installation having group privileges' on Oracle and java groups

4.4 PORT VALIDATION

Verify that the port numbers are available on the machines where you install Informatica Services.
-bash-3.2$ netstat -tulpn|grep 6005
The installer validates the port numbers that you specify to ensure that there will be no port conflicts in the domain.
-bash-3.2$ netstat -tulpn|grep 6001
(Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.)
tcp 0 0 :::6001 :::* LISTEN 4935/java
-bash-3.2netstat -tulpn|grep 6002
(Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.)
tcp 0 0 ::ffff:127.0.0.1:6002 :::* LISTEN 4935/java
-bash-3.2$ netstat -tulpn|grep 6003
(Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.)
-bash-3.2$ netstat -tulpn|grep 6004
(Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.)

5 Environment Variables

Most UNIX systems use the LANG variable to specify the desired locale but you can use also the set locale function.

5.1 OBTAIN THE LOCALE VALUES

To obtain the locale names for your UNIX system, enter the following:
infa@chetltst201 $ locale -a | grep -i en
en_AU
en_AU.iso88591
en_AU.utf8
en_BW
en_BW.iso88591
en_BW.utf8
en_CA
en_CA.iso88591
en_CA.utf8
en_DK
en_DK.iso88591
en_DK.utf8
en_GB
en_GB.iso88591
en_GB.iso885915
en_GB.utf8
en_HK
en_HK.iso88591
en_HK.utf8
en_IE
en_IE.iso88591
en_IE.utf8
en_IE@euro
en_IN
en_IN.utf8
en_NZ
en_NZ.iso88591
en_NZ.utf8
en_PH
en_PH.iso88591
en_PH.utf8
en_SG
en_SG.iso88591
en_SG.utf8
en_US
en_US.iso88591
en_US.iso885915
en_US.utf8
en_ZA
en_ZA.iso88591
en_ZA.utf8
en_ZW
en_ZW.iso88591
en_ZW.utf8
french
slovene
slovenian

6 File Descriptor

Informatica service processes can use a large number of files. Set the Linux - File Descriptorlimit per process to 3000 or higher.
In the file /etc/security/limits.conf, add this line:
# PowerCenter
Infa91 hard nofile 3001
Infa91 soft nofile 2500
And verify with the ulimit function logged as the power center system user account:
-bash-3.2$ ulimit -Hn
3001
The limit is set to 3001 to prevent an error with the value 300 during the prerequisites check

7 Installation directory and Permission

As root, create the installation base directory:
Pwd
/infa
mkdir /informatica
chown 755 informatica
cd informatica
mkdir pc91
chown 755 pc91
cd /infa
mkdir software
chmod 755 software
As the installer (powercenter), copy the file to software directory, unzip and untar it:
-bash-3.2$ tar -xf 910HF3_Server_Installer_linux-x64.tar

-rw-r--r-- 1 infa91 infadmin 3990835200 May 1 19:30 910HF3_Server_Installer_linux-x64.tar
-bash-3.2$ tar -xf 910HF3_Server_Installer_linux-x64.tar

-bash-3.2$ ls -ltr
total 3901232
-rw-r--r-- 1 infa91 infadmin 2307 Sep 9 2011 SilentInput_upgrade.properties
-rw-r--r-- 1 infa91 infadmin 5093 Sep 9 2011 SilentInput_upgrade_NewConfig.properties
-rw-r--r-- 1 infa91 infadmin 5650 Sep 9 2011 SilentInput.properties
-rwxr-xr-x 1 infa91 infadmin 10674 Sep 16 2011 silentinstallHotFix.sh
-rw-r--r-- 1 infa91 infadmin 976 Sep 16 2011 SilentInput_hotFix.properties
-rw-r--r-- 1 infa91 infadmin 866 Sep 16 2011 SilentInput_DT.properties
-rwxr-xr-x 1 infa91 infadmin 4848 Nov 17 12:23 unjar_esd.sh
-rwxr-xr-x 1 infa91 infadmin 10683 Nov 17 12:23 silentinstall.sh
-rwxr-xr-x 1 infa91 infadmin 10723 Nov 17 12:23 silentinstallDT.sh
-rwxr-xr-x 1 infa91 infadmin 13242 Nov 17 12:23 install.sh
drwxr-xr-x 5 infa91 infadmin 4096 Nov 29 06:21 i9Pi
drwxr-xr-x 4 infa91 infadmin 4096 Nov 29 06:28 Server
drwxr-xr-x 2 infa91 infadmin 4096 Nov 29 06:28 Messages
drwxr-xr-x 3 infa91 infadmin 4096 Nov 29 06:28 upgrade_utils
drwxr-xr-x 2 infa91 infadmin 4096 Nov 29 06:28 properties
drwxr-xr-x 4 infa91 infadmin 4096 Nov 29 06:28 sapsolutions
drwxr-xr-x 4 infa91 infadmin 4096 Nov 29 06:28 saptrans
drwxr-xr-x 3 infa91 infadmin 4096 Nov 29 06:39 source
-rw-r--r-- 1 infa91 infadmin 3990835200 May 1 19:30 910HF3_Server_Installer_linux-x64.tar
-bash-3.2$ pwd
/infa/informatica/pc91

Change the permission of the file install.sh to execute
chmod -R 755 /infa/informatica/pc91/install.sh

8 Pre - Installation System Check

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: <InstallerExtractDirectory>/i9Pi
-bash-3.2$ ./i9Pi.bin
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...

-bash-3.2$ ./i9Pi.bin
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...
Graphical installers are not supported by the VM. The console mode will be used instead...
Preparing CONSOLE Mode Installation...
===============================================================================
Informatica 9.1 PreInstall (created with InstallAnywhere)
-------------------------------------------------------------------------------
===============================================================================
Pre-Installation System Check
-----------------------------
Use this tool to verify that this machine meets the minimum system and database Requirements for installation of Informatica 9 services.

Run this tool before you run the Informatica server installer.

Respond to each prompt to proceed to the next step in the installation. If you
want to change something on a previous step, type 'back'.

You may cancel this installation at any time by typing 'quit'.

PRESS <ENTER> TO CONTINUE:
===============================================================================
System and Database Information
===============================================================================
System and Database Information
-------------------------------
Drive to check (DEFAULT: ): /infa
Informatica starting port number (DEFAULT: ): 6001
===============================================================================
Domain Configuration Repository Database
----------------------------------------
Database Type
1- Oracle
2- DB2
3- SQL
4- Sybase

ENTER THE NUMBER OF THE DESIRED CHOICE: 1
ENTER THE NUMBER OF THE DESIRED CHOICE: 1
===============================================================================
Domain Configuration Repository Database
----------------------------------------------------------------------------------------------------------------------------------
Database user ID (DEFAULT: ): USER_DOM
User password (DEFAULT: ): USER_DOM
===============================================================================
Database Connection Type
----------------------------------------------------------------------------------------------------------------------------------
Custom String
1- Yes
2- No
ENTER THE NUMBER OF THE DESIRED CHOICE: 1
===============================================================================
Connection Configuration Repository Database
----------------------------------------------------------------------------------------------------------------------------------
Custom String (DEFAULT: ): pcd91


Installing...
----------------------------------------------------------------------------------------------------------------------------------

[==================|==================|==================|==================]
[------------------|------------------|------------------|------------------]
===============================================================================
System Check Report
-------------------
i9Pi System Check Summary:

TestStatusMessageInformatica9 Installation Directory /infa Informatica starting
port number 6001
Database Type Oracle
Operating System Version
Operating system version: 2.6.18-164.el5.
Disk Space Available diskspace: 87,436 MB. Sufficient for installation.
Processors Available number of processors: 10. Sufficient for installation.
RAM Memory module identified: MemTotal:
98867016 kB. Physical Memory Available physical memory: 96,549 MB.
Sufficient for installation.
Temporary Space Available temporary diskspace: 55,697 MB. Sufficient for installation.
Ports Port range 6,001 - 6,006: All port numbers available.
LANG Environment Variable LANG set to en_US.UTF-8; LC_ALL set to null.
JRE_HOME Environment Variable
JRE_HOME environment variable is empty.
File Descriptors File descriptors limit set to 1024 It should be at least set to 3K.
Sybase Procedure/rule Verify that the database user has the following privileges: Create Procedure and Create rule.

A pdf is available in the tool directory if you want more information.
The report files are stored in the directory where you extract the Pre-Installation System Check tool files:
  • HTML format: <i9Pi Directory>/i9Pi/i9Pi_summary.html
  • Text format: <i9Pi Directory>/i9Pi_summary.log

9 Initial Server Software Installation


-bash-3.2$ ./install.sh
OS detected is Linux

\***************************************************************************
\* Welcome to the Informatica 9.1.0 HotFix 3 Server Installer. *
\***************************************************************************

Before you continue, read the following documents:
* Informatica 9.1.0 HotFix 3 Installation Guide and Release Notes.
* B2B Data Transformation 9.1.0 HotFix 3 Installation and Configuration Guide and Release Notes.

You can find the 9.1.0 HotFix 3 documentation in the Product Documentation section at http://mysupport.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)Y
Installer requires operating system Linux version 2.6.16 and later. Current operating system Linux version 2.6.18. Current operating system meets minimum requirements.

Select to install or upgrade:

1.Install or upgrade Informatica.
Select this option if the machine does not have Informatica services installed
or if it has Informatica 9.0.x or an earlier version installed.
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: <InstallerExtractDirectory>/i9Pi

2.Install Data Transformation Engine Only.
Select this option to install only Data Transformation Engine.

3.Select this option if the machine has Informatica 9.1.0 or an Informatica 9.1.0 hotfix installed.

Enter the choice(1,2 or 3):1

-----------------------------------------------------------
Checking for existing 9.1.0 HotFix 3 product installation.
Select (G)UI mode (needs X Window support) or (C)onsole mode (G/C):C
DISPLAY is not set. Cannot run installer in console mode.
Installer will run in console mode.
Select 'Y' to run in console mode, select 'N' to exit.
Do you want to continue? (Y/N)Y
Launching installer in console 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.1.0 HotFix3 Services (created with InstallAnywhere)
-------------------------------------------------------------------------------

***************************************************************
Installation Type
**************************************************************
[ Type 'back' to go to the previous panel or 'quit' to cancel the installation at any time. ]

Select to install or upgrade:
* 1->Install Informatica 9.1.0 with HotFix 3.
Select this option to perform a full installation of Informatica 9.1.0 HotFix 3.
2->Upgrade to Informatica 9.1.0 with HotFix 3.
Select this option to upgrade previous versions of Informatica products to Informatica 9.1.0 HotFix 3.
1
***************************************************************
Installation Pre-Requisites
**************************************************************
[ Type 'back' to go to the previous panel or 'quit' to cancel the installation at any time. ]
Verify the installation pre-requisites and complete the
pre-installation tasks before you continue.
Disk Space Requirement: 4 GB
Memory Requirement (RAM): 4 GB
Database Requirements
- Requires Oracle, IBM DB2, Microsoft SQL Server or Sybase ASE.
- Database user account must have permission to create and drop tables
and views and insert, update, and delete data.
Pre-installation Tasks
- Verify that you have a valid license key.
- Set up a database user account for the domain configuration.
- Determine the port numbers to use for the node and domain services.

***************************************************************
License Key
**************************************************************
[ Type 'back' to go to the previous panel or 'quit' to cancel the installation at any time. ]
Enter the license key file (default :- /home/infa91/license.key) :
/infa/informatica/pc91/Dev_Licence_Key_2102_01_01.KEY

***************************************************************
Installation Directory
**************************************************************
[ Type 'back' to go to the previous panel or 'quit' to cancel the installation at any time. ]
Enter the installation directory (default :- /home/infa91/Informatica/9.1.0) : /infa/informatica/pc91
***************************************************************
Pre-Installation Summary
**************************************************************
[ Type 'back' to go to the previous panel or 'quit' to cancel the installation at any time. ]
Product Name : Informatica 9.1.0 HotFix 3 Services
Installation Type : Fresh Installation
Installation Directory : /infa/informatica/pc91
Disk Space Requirements
Required Disk Space : 5,292 MB
Available Disk Space : 80,565 MB
Press <Enter> to continue ...
***************************************************************
Installing
**************************************************************
[==================|==================|==================|==================]
[==================|==================|==================|==================]
[==================|==================|==================|==================]
[==================|==================|==================|==================]
===============================================================================
Configuring Installation...
---------------------------
[==================|==================|==================|==================]
[------------------|------------------|------------------|------------------]

***************************************************************
Domain Selection
**************************************************************
[ Type 'back' to go to the previous panel or 'quit' to cancel the installation at any time. ]

* 1->Create a domain
2->Join a domain
:1

Enable Transport Layer Security (TLS) for the domain
1->No
* 2->Yes
:2
* 1->Enable HTTPS for Informatica Administrator
2->Disable HTTPS
:1

Port: (default :- 8443) :8443
1->Use a keystore file generated by the installer
* 2->Use an existing keystore file
:1
Generating keystore...
--
***************************************************************
Domain Configuration Repository
**************************************************************
[ Type 'back' to go to the previous panel or 'quit' to cancel the installation at any time. ]
Configure the database for the domain configuration repository:
Database type:
* 1->Oracle
2->SQLServer
3->DB2
4->Sybase
:1
Database user ID: (default :- admin) :USER_DOM
User password: :
Configure the database connection
* 1->JDBC URL
2->Custom JDBC Connection String
:2

Custom String (default :- jdbc:informatica:oracle://host_name:port_no;ServiceName=):jdbc:informatica:Oracle://11.22.333.111:1521;SID=pc91

***************************************************************
Domain and Node Configuration
**************************************************************
[ Type 'back' to go to the previous panel or 'quit' to cancel the installation at any time. ]

Enter the following information for the Informatica domain.
Domain name: (default :- Domain_servername) :domain_abc_dev
Node host name: (default :- servername) :servername
Node name: (default :- node01_servername) :node1_abc_dev
Node port number: (default :- 6001) :6001
Domain user name: (default :- Administrator) :Administrator
Domain password: (default :- ) :
Confirm password: (default :- ) :
Display advanced port configuration page
1->No
* 2->Yes
:1

Defining domain...
-----------
Starting service...
--
Pinging domain...
-----
Pinging domain...
--
Pinging domain...
--
Adding license...
--
Pinging Administrator...
--
Pinging Administrator...
--
***************************************************************
Post-Installation Summary
**************************************************************
Installation Status SUCCESS
The Informatica 9.1.0 HotFix 3 installation is complete.
For more information, see the debug log file:
/infa/informatica/pc91/Informatica_9.1.0_Services_HotFix3.log
Installation Type :Fresh Installation
Informatica Administrator Home Page::
Product Name: Informatica 9.1.0 HotFix 3 Services
Press <Enter> to continue ...
Installation Complete

10 Port Configuration


Port Type
Default
Description
Domain port
6005
Port number used by the domain.
Service Manager port
6006
Port number used by the Service Manager on the node. The Service Manager listens for incoming connection requests on this port. Client applications use this port to communicate with the services in the domain. This is the port that the Informatica command line programs use to communicate to the domain. This is also the port for the SQL data service JDBC/ODBC driver.
Service Manager shutdown port
6008
Port number that controls server shutdown for the domain Service Manager. The Service Manager listens for shutdown commands on this port.
Informatica Administrator port
6007
Port number used by the Administrator tool.
Informatica Administrator shutdown port
6009
Port number that controls server shutdown for the Administrator tool. The Administrator tool listens for shutdown commands on this port.
Range of ports for application services
6013 to 6113
Range of port numbers that can be assigned to the application service processes that run on the node. When you create an application service in the domain, the Service Manager assigns the first available port in this range to the service process. At a minimum, the number of ports in the range must be equal to the number of application service processes that will run on the node.

10.1 Guidelines for Port Configuration

Use the following guidelines to determine the port numbers:
  • The port number you specify for the domain and for each component in the domain must be unique.
  • The port number for the domain and domain components cannot be within the range of the port numbers that you specify for the application service processes.
  • The highest number in the range of port numbers that you specify must be at least three numbers higher than the lowest port number. For example, if the minimum port number in the range is 6400, the maximum port number must be at least 6403.
  • The port numbers that you specify for the domain, domain and node components, and application service processes cannot be lower than 1025 or higher than 65535.
  • Login to the Administration console with the Administrator user (Administration/Administrator)




infa .bash_profile:

export INFA_HOME=/infa
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/10\.2\.0/db_1
export ORACLE_SID=poporcl
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/infa/server:$ORACLE_HOME/lib
export LC_CTYPE=en_US.utf8
export PATH=$PATH:$HOME/bin:$ORACLE_HOME/bin::$INFA_HOME/server/bin
export LANG=en_US.utf8
export LC_ALL=en_US.utf8
export TNS_ADMIN=$ORACLE_HOME/network/admin
export NLS_LANG=AMERICAN_AMERICA.UTF8
unset USERNAME

oracle .bash_profile

PATH=$PATH:$HOME/bin

export PATH
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/10\.2\.0/db_1
export ORACLE_SID=poporcl
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export LC_CTYPE=en_US.utf8
export LC_ALL=en_US.utf8
export PATH=$PATH:$HOME/bin:$ORACLE_HOME/bin
export NLS_LANG=american_america.utf8
export ORA_NLS33=$ORACLE_HOME/nls/data
export TNS_ADMIN=$ORACLE_HOME/network/admin
unset USERNAME

Wednesday, 28 November 2018

Config Mule Managment Console backend as MSSQL Database

Mule Management Console which is also known as MMC in short,  is a centralizes management and monitoring functions for all our on-premise Mule ESB Enterprise deployments, that includes running as a standalone instances, as a cluster, or embedded in application servers.

MMC as an enterprise management and monitoring tool is designed specifically for Mule on-premises instances. It provides all the functionality for managing and monitoring running Mule on premises servers, Mule clusters, deployed applications within Mule servers, and the flows within those applications. Another important feature is it also provides ways of looking at specific transactions through pre-defined business events, as well as transactions in flight.

MMC by default supports internal derby database to persist environment and transaction data. If we start our MMC  application under Apache Tomcat server, we can see under the bin folder there is a folder named as  mmc-data is created where it stores all the MMC related data to support all the MMC functionalities:-

untitled

 

If we enter into that folder, we will see the derby database is created with all other folders:-.

untitled

From MMC  version 3.4.2 or later it supports external database which means we can connect to any external remote database instead of using our default internal derby database. It is very easy to connect our MMC  with an external database and in this post we are going to demonstrate this in 5 simple stepsJ.

Currently it can be connected with any of the following databases other than derby :-

Externalizing with MS-SQL server:-

So, we will see here connecting our MMC  with external MS-SQL Server.

Before we start, we can delete the mmc-data folder from <MMC_HOME> /bin folder path after taking a backup.

<MMC_HOME> is the directory where MMC is installed.

Step 1:- First step is simple. Since we are connecting our MMC  with MS-SQL Server  we need the driver and copy it into <Mule install path>/apps/mmc/webapps/mmc/WEB-INF/lib folder:-

untitled

Step 2:- In the folder <MMC_HOME>/WEB-INF we need to configure our web.xml. By default in spring.profiles.active section we will see the parameter string as env-derby which is pointing for default derby configuration:-

untitled

We need to replace it with env-mssql as follows:-

untitled

We also need to delete the string tracking-h2 and replace it with tracking-mssql to Persist Transaction Data to MS-SQL Server.

Step 3:- We will be creating a database say MMC_DB_3.8 in our MS-SQL Server which will be connected to our MMC :-

untitled

Step 4:- In the directory <MMC_HOME>/WEB-INF/classes/META-INF/databases, we need to locate the file mmc-mssql.properties, and then do the editing for are env.username, env.password, env.host, env.port and env.dbschema:-

untitled

Step 5:- The final stage will be in directory <MMC_HOME>/WEB-INF/classes/quartz there is a .sql file called tables_sqlServer.sql, and we execute that in SQL DB server:-

untitled

This will create the required tables in our database.

And that's it! We are done here.

If we start our Apache Tomcat server and browse the MMC portal in a browser, we will see the application has started successfully:-

untitled

And now if we go back to bin folder we will see the mmc-data folder is created which contains all the MMC related data:-

untitled

If we browse into the folder we will find no internal database folder created as we have already configured it with our MS-SQL Server and hence leaving only repository and workspace folder:-

untitled

So, we can see how easy it is to configure the MMC application with an external MS-SQL Server database.

Hope you like the post and please do share your feedback and experiences in the below section for comments.

Thursday, 31 May 2018

DB2 Federation between two DB2 databases on same instance

Step 1:
 
Go to db2 prompt
 
db2=>

Step 2: (Optional) Create database if necessary
 
create database Tom
 
create database Jerry
Step 3: Connect to DB1 and create table (Example Tom) (Optional)
 
connect to tom
 
create table db2inst1.tab1 (cod1 int)
 
insert into db2inst1.tab1 values (1)

Step 4: Connect to DB2 and create table (Example Jerry)
 
connect to jerry
 
create table db2inst1.tab2 (name1 char)
 
insert into db2inst1.tab2 values ('a')

Step 5: Create server and mappings in 1st DB (Tom) to access 2nd DB (Jerry)
connect to tom
 

create server fedserver TYPE DB2/UDB VERSION 10.5 WRAPPER drda  AUTHORIZATION "db2inst1" password "password" OPTIONS(DBNAME 'jerry')
 
create user mapping for db2inst1 SERVER fedserver OPTIONS(REMOTE_AUTHID 'db2inst1',REMOTE_PASSWORD 'password')
create nickname mytable for fedserver.db2inst1.tab1

Step 6: 

Executing Select statement from 1st Db (Tom) to query results from 2nd DB (Jerry)
 
select * from mytable

--
Regards
Sandeep C

Wednesday, 24 January 2018

Users from LDAP nested groups don't appear in BPM Process Admin Console

BPM uses the WebSphere UserRegistry.getUsersForGroup() call to retrieve user members of nested groups.

In order to get nested members from the API call getUsersForGroup(), you need to add/set a custom property:

"com.ibm.ws.wim.adapter.ldap.returnNestedNonGroupMembers" with value "true".

In order to set this property, do the following:

1) Stop all the servers and node agents.

2) From the deployment manager bin directory.

#./wsadmin.sh

Run below commands:

$AdminTask setIdMgrCustomProperty { -id my_Ldap_Repository_Id -name com.ibm.ws.wim.adapter.ldap.returnNestedNonGroupMembers -value true}

$AdminConfig save

3) Sync your nodes as needed.

4) Start your servers.