IBM System Director – Installation with Oracle Database

Posted on Posted in linux, monitoring, Oracle DB

In this post I’ll explain how install IBM System Director with Oracle remote database. For everybody that don’t know what is IBM System Director, here the official IBM description:

What’s this?

IBM Systems Director® is the platform management backbone to achieve Smarter Computing. An integral component of the IBM Smarter Systems portfolio, IBM Systems Director enables integration with Tivoli, and third party management platforms, providing the building block for integrated services management. With Systems Director you can:

  • Automate data center operations by implementing cloud-ready virtual infrastructures
  • Unify the management of physical and virtual resources for IBM servers, storage and networks
  • Simplify the management of optimized systems
  • Achieve a single view of the actual energy usage throughout your data center

IBM Systems Director provides systems management personnel with a single pane of glass, helping reduce IT management complexity and cost. Key IBM Systems Director capabilities include:

  • Simple Lifecycle Management of your workloads with intuitive usability and reduced complexity – IBM Systems Director offers a core, comprehensive, unified systems management platform. It provides tools for discovery, inventory, status, configuration, system health, resource monitoring, system updates, event notification and management automation.
  • Integration – with Tivoli, and third party management platforms, provides the foundation for virtualization and integrated services management. With an extensive suite of available platform management tasks, and automated tools, IBM Systems Director assists systems management personnel in increasing productivity, resulting in improved responsiveness and service.

The key value of IBM Systems Director is its ability to work in diverse IT environments. It dramatically reduces the number of management tools and interfaces; simplifying the way in which IT administrators perform their tasks, and freeing up their time to meet changing business requirements.

Installation

Hardware recomendations

To install IBM System Director I recommend a RHEL 5.5/6 x64 with 4G RAM, 50 G of Hard Disk and 4 CPU’s.

Oracle Administration Client

To connect with the remote Database, IBM System Director need Oracle Administration Client, download Oracle Database 11g Release 2 Client (11.2.0.1.0) for Linux  and install.

Installation

 The installation is very simple, with the oracle user extract and run the ./runinstaller (with X system), select Administration and follow the instructions.

Select the language:

Specify the installation directory

The orainventory directory

Perform Prerequisite Checks

In this case I must be install:

yum install unixODBC-devel.i386 libaio-devel.i386

After this, click in Fix & Check Again, run with the root user the script that the Installer said:

If all it’s ok finish the oracle client installation.

Environment

Finally edit the /etc/profile and add in the final of the file:

export TNS_ADMIN=/oracle/client/installation/client_1/network/admin
export LD_LIBRARY_PATH=/oracle/client/installation/client_1/lib
export PATH=/oracle/client/installation/client_1/bin:$PATH
export ORACLE_HOME=/oracle/client/installation/client_1
export ORACLE_BASE=/oracle/client/installation/ 

Oracle User creation

In your database create the IBM System Director Database User:

CREATE SMALLFILE TABLESPACE "SDIRECTOR00" DATAFILE '+DATA' SIZE 100M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;

create user SDIRECTOR identified by password
     default tablespace SDIRECTOR00
     TEMPORARY TABLESPACE TEMP
     QUOTA UNLIMITED ON SDIRECTOR00;

tnsnames.ora

Add your database in your tnsnames.ora and check the connectivity with it.

MYDB =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = db1.albertolarripa.com)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = MYDB)
    )
  )

System Director Installation

Be sure that your server have the compat-libstdc:

yum install compat-libstdc++-33.i386

Download & Extract

Download and extract the package from the official webpage:

tar xvfz SysDir6_3_Server_Linux_x86_a.tar.gz

Environmental checks

Make sure that your server meets the requirements, is something is wrong fixup and check again

cd checkds
./checkds.sh

dirserv.rsp

dirserv.rsp is the file that the installation read, edit and change the USE_MANAGED_DB for disable the DB2 IBM Database.

----------------------------------------------
# USE_MANAGED_DB
#
# Use the managed database shipped with IBM Systems Director server.
# Default setting is to use the managed database.  This is for fresh installs,
# for migration use MIGRATE_TO_MANAGED_DB2 variable above.
# USE_MANAGED_DB=1: Default
# USE_MANAGED_DB=0: Use this setting if planning on using a custom database
USE_MANAGED_DB=0

Install

Launch the installation

# ./dirinstall.server -r dirserv.rsp 
By running the installer non-interactively, you have agreed to the stated
license terms under the license directory of the installed program.

IBM Systems Director Server 6.3.0 installation.

Java: /../.../..../ibm/installation/checkds/jvm/xlinux/bin/java
Starting IBM Systems Director Pre-Installation Utility...
Finished analysing system
Creating reports... 
Install Readiness Text report being written to /tmp/checkds/reports/checkDS_Text_08142012_135009.txt
Install Readiness Error Text report being written to /tmp/checkds/reports/checkDS_Error.txt
Install Readiness Detailed HTML report being written to /tmp/checkds/reports/checkDS_Detailed_08142012_135009.html
Install Readiness Summary HTML report being written to /tmp/checkds/reports/checkDS_Summary_08142012_135011.html
........
.....

Installation of the IBM Systems Director Server 6.3.0 succeeded.

Configure the database before starting the server.
Update /opt/ibm/director/proddata/cfgdbcmd.rsp for the database.
Run /opt/ibm/director/bin/cfgdbcmd.sh to configure the database.
Then run /opt/ibm/director/bin/smreset to finish up the database configuration.
To start the server manually, run /opt/ibm/director/bin/smstart.

Configure the database

Like the installation said:

Update /opt/ibm/director/proddata/cfgdbcmd.rsp for the database.

Edit this file and add your database info (comment the DB2 Database):

cat /opt/ibm/director/proddata/cfgdbcmd.rsp
;===============================================================================
; Managed DB2
;===============================================================================
;DbmsApplication = Managed DB2
;DbmsTcpIpListenerPort = 50010
;DbmsServerName = localhost
;DbmsDatabaseHome = xxxxx
;DbmsPassword =
;===============================================================================

;===============================================================================
; Oracle
;===============================================================================
DbmsApplication = Oracle
DbmsTcpIpListenerPort = 1521
DbmsServerName = db1.albertolarripa.com
;== This is your entry in the tnsnames.ora
DbmsDatabaseName = MYDB
;=========================
DbmsUserId = sdirector
DbmsPassword = password
DbmsDatabaseAppHome = /oracle/client/installation/client_1
;===============================================================================

Create the permission schema

/opt/ibm/director/bin/cfgdbcmd.sh

In my case I had one problem, the installation process don’t found the correct JDBC driver.

[ 8/15/12 11:14 AM ] Database created successfully.
[ 8/15/12 11:14 AM ] Could not find file.  Verify database client setup and re-run cfgdbcmd.
[ 8/15/12 11:14 AM ] JDBC jar file(s) copy was unsuccessful. Either the jar file(s) do not exist, or the DbmsDatabaseAppHome value is set incorrectly in the cfgdbcmd.rsp file.

For additional information, see: /opt/ibm/director/bin/../log/cfgdbcmd.log

To resolve it create the symlink with the ojdbc5.jar

# ln -s /oracle/client/installation/client_1/jdbc/lib/ojdbc5.jar  /oracle/client/installation/client_1/jdbc/lib/ojdbc14.jar
# ll /oracle/client/installation/client_1/jdbc/lib/ojdbc14.jar
lrwxrwxrwx 1 root root 55 Aug 15 11:19 /oracle/client/installation/client_1/jdbc/lib/ojdbc14.jar -> /oracle/client/installation/client_1/jdbc/lib/ojdbc5.jar

Run again and enter your Oracle DBA user and password:

# /opt/ibm/director/bin/cfgdbcmd.sh
[ 8/14/12 2:14 PM ] Starting database configuration...
[ 8/14/12 2:14 PM ] Encrypting password in: /opt/ibm/director/bin/../proddata/cfgdbcmd.rsp
[ 8/14/12 2:14 PM ] Checking response file parameters...
[ 8/14/12 2:14 PM ] Notifying 1 database configuration extensions of requested database configuration change to Oracle Database
[ 8/14/12 2:14 PM ] Configuring database of type: Oracle
Enter the database administrator user name: sys
Enter the database administrator password: 
[ 8/14/12 2:16 PM ] Checking environment variables for: Oracle
[ 8/14/12 2:16 PM ] Creating database 'MYDB' on db1.albertolarripa.com...
[ 8/14/12 2:16 PM ] Configuring user ID for database
....
..

Create the metadata

Run this command to create the metadata info in the sdirector schema:

# smreset 
This operation will revert the IBM Systems Director database and server to the installed state. To continue, type "1" for yes or "0" for no.
1

ALR1325I: The lightweight runtime has started.

Command completed successfully

Reset completed successfully.

Agent Configuration

Configure you Agent credentials, this will be used to logon in the IBM Application

/opt/ibm/director/bin/configAgtMgr.sh
Enter 1 to use the Agent Manager installed with this server (recommended)
Enter 0 to use an existing Agent Manager (advanced) : 1
Enter Resource Manager username : admin
Enter Resource Manager password : 
Re-Enter Resource Manager password : 
Enter Agent Registration password : 
Re-Enter Agent Registration password : 
[Add] [Element]: AgentManagerUserID [Value]: root
[Add] [Element]: AgentManagerPassword [Value]: {aes:3C5SnKQL63ASHKAjash+564il1NzNvSiAzzk=}hxBgsFeAAiqEgQr+xda2Ow==
[Add] [Element]: ManagerRegistrationPassword [Value]: {aes:3C5SnKQL63ASHKAjash+564il1NzNvSiAzzk=}hxBgsFeAAiqEgQr+xda2Ow==
DataSourceConfig.sh=0
DataStoreInstall.sh=0
GenerateCertificates.sh=0
EncryptAMProps.sh=0
WebConfig.sh=0
usmi-cas-setup.sh=0

Start System Director

Finally start the system

# smstart 
Starting IBM Director...The starting process may take a while. Please use smstatus to check if the server is active.

With smstatus you’ll see if the system is Active, the first start process is very heavy, because the system connect with the database and insert some information in the SDIRECTOR schema

# smstatus -r
Starting
Active

You’ll see the process startup with the following file:

# tail -f /opt/ibm/director/lwi/logs/error-log-0.html

If all is ok you can logon in your System Director Server with this URL:

https://sdserver.albertolarripa.com:8422/ibm/console

or

http://sdserver.albertolarripa.com:8421/ibm/console

Thanks for following, for any question comment on this post or write to:

Leave a Reply

Your email address will not be published. Required fields are marked *