Siva R Vaka: April 2013

IHS (IBM HTTP Server) v7 Installation

Setup wizard lets configure different options for the HTTP server installation

You will get the below warning if your operating system doesn't meet the prerequisites check

Specify HTTP Server installation location

Accepted the default ports

Selected checkbox and provide the user account details if you want to "Run IBM HTTP Server as a windows service"

Create userID and password to authenticate to IBM Http Server administration server using WAS console.

Select the checkbox to install the IBM HTTP server plugin directly

Installation Summary

IBM HTTP server will be installed to the following location

C:\IBM\HTTPServer

With the following configuration

HTTP Port : 80

HTTP Administration Port : 8008

HTTP Service Name : IBM HTTP Server 7.0

User ID for HTTP administration Server Authentication : ihsadmin

IBM Http Server Plug-in for IBM WebSphere Application Server will be installed to :

C:\IBM\HTTPServer\Plugins

Total Size

429 MB

Uninstalling WebSphere Portal

To uninstall WebSphere portal , start uninstallation wizard by clicking on "C:\IBM\WebSphere\PortalServer\uninstall\uninstall.bat"

Click on "uninstall.bat" (Run as Administrator if it windows)

Got warning saying , I may need to remove the WAS server manually

I have deleted leftover directory "C:/IBM/Websphere" from the uninstallation to clean up (make sure you are deleting only websphere portal server directory not any other shared install folder like "SDPShared ..etc if any)

IBM Tivoli Directory Server (TDS) v6.2 : IDSWebApp (web admin tool) installation on the Websphere

Find the IDSWebApp.war file from <TDS install dir location>\V6.2\idstools\
Deploy the war file from the ISC console with context root as "IDSWebApp". (Please refer to infocenter link provided in references section below for detailed instructions on how to install IDSWebApp) .

NOTE: Make sure choose the "Server1" as target while installing webapp , I had issues when I installed it on the portal cluster. (see Appendix for more details)

Access the IDSWebApp after successful installation (Access this IDSWebApp using the server1 ports)

https://sivapc.sivavaka.com:10002/IDSWebApp/

UserID/Password :: superadmin/secret (Default initial userid/password)

Click on manage console servers on the left hand side to add the LDAP server to admin console.

After adding the ldap server, logout and log back in with TDS admin user and apassword

Appendix:

I have installed the IDSWebApp on the portalcluster initially , and able to login to the console successfully by accessing the

https://sivapc.sivavaka.com:10032/IDSWebApp/

But when I tried to add the ldap server by clicking manager server got the following error

[2/26/12 0:13:18:649 EDT] 0000003e mdr E com.ibm.ldap.IDSCSAUserManagement.IDSCSAUser@4ba44ba4DrStateMgr.invoke()

java.lang.NoSuchMethodError: com/ibm/mdr/wcl/DrWMultiDeviceTable.getResourceBundle(Ljava/util/Locale;)Ljava/util/ResourceBundle;

at com.ibm.mdr.wcl.DrTableCreator.create(DrTableCreator.java:559)

at com.ibm.mdr.DrCreatorFactory.recurseData(DrCreatorFactory.java:147)

at com.ibm.mdr.DrContainerCreator.recurseChildren(DrContainerCreator.java:100)

at com.ibm.mdr.wcl.DrGroupCreator.create(DrGroupCreator.java:224)

at com.ibm.mdr.DrCreatorFactory.recurseData(DrCreatorFactory.java:147)

at com.ibm.mdr.DrContainerCreator.recurseChildren(DrContainerCreator.java:100)

at com.ibm.mdr.wcl.DrGroupCreator.create(DrGroupCreator.java:224)

at com.ibm.mdr.DrCreatorFactory.recurseData(DrCreatorFactory.java:147)

at com.ibm.mdr.wcl.DrGroupCreator.recurseSelectableChildren(DrGroupCreator.java:702)

at com.ibm.mdr.wcl.DrDatagroupCreator.create(DrDatagroupCreator.java:431)

at com.ibm.mdr.DrCreatorFactory.recurseData(DrCreatorFactory.java:147)

at com.ibm.mdr.DrCreatorFactory.createStateTree(DrCreatorFactory.java:81)

at com.ibm.mdr.DrStateMgr.createStateTree(DrStateMgr.java:1136)

at com.ibm.mdr.DrStateMgr.invoke(DrStateMgr.java:2801)

at com.ibm.mdr.DrRendererManager.invoke(DrRendererManager.java:396)

at com.ibm.mdr.DrRenderer.invoke(DrRenderer.java:1419)

at com.ibm.ui.framework.UserTaskManager.invoke(UserTaskManager.java:1409)

at com.ibm.ui.framework.UserTaskManager.invoke(UserTaskManager.java:1370)

at com.ibm.ldap.IDSAdmin.ConsolePropertiesPanel.init(ConsolePropertiesPanel.java:124)

at com.ibm.webnav.servlet.WnTransactionManager.processTransaction(WnTransactionManager.java:695)

at com.ibm.webnav.servlet.WnTransactionThread.run(WnTransactionThread.java:114)

Solution:

It took a while to figure the actual issue to resolve the above the problem,

While installing the IDSWebApp , make sure you have selected the "server1" as target (even though you have portal server) .

I have started the server1 from command prompt and installed the IDSWebApp from the ISC console and selected the "server1" as target but I was not able to start application from the DMGR ISC console as it says application deployed on the different server.

I have choosen to start application when server starts (from the ISC concole , click on application and configure) and restarted the "Server1" to start this application while starting the server .

Access IDSWebApp using the server1 ports.

https://sivapc.sivavaka.com:10002/IDSWebApp/

Refereces

http://www-01.ibm.com/support/docview.wss?uid=swg21443554

http://publib.boulder.ibm.com/infocenter/eserver/v1r2/index.jsp?topic=%2Fveicinfo%2Feicar_managing_startstop_dir_svr_start_tool.htm

https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014225542

IBM Tivoli Directory Server (TDS) v6.2 Directory Server Instance Creation

You can create the directory server instance in two ways

1. Creating default instance

2. Creating directory server instance by providing details manually(like db2 instance name, port numbers …etc)

Creating default directory server instance

Once the TDS installation is finished, open the "Instance Administration Tool" to create new directory server instance (make sure you open as administrator if you are installing on Windows because it will create the local system users also… )

I have provided following details

Instance owner password (dsrdbm01pwd)

encryption seed (encryption-abcdefg)

Administer dn password :: Passw0rd

This will create the directory server instance with name "dsrdbm01" , also database instance name "dsrdbm01"

Following things happen during instance creation

Creates local system user with name "dsrdbm01" and adds that user to "Administrator" , "DB2ADMNS" and "DB2USERS" groups
Creates Directory Server instance with name "dsrdbm01"
Creates database instance with name "dsrdbm01" and configure to start as windows service
Add/configures database instance(dsrdbm01) to directory service instance
Start DB manager for instance "dsrdbm01"
Adds "o=sample" suffix to directory server configuration

Troubleshooting

I have encountered the following error when I tried to start the LDAP instance ( TDS instance is starting only in config mode)

Observed the following error from the C:\idsslapd-dsrdbm01\logs\ibmslapd.log file

GLPCOM016E Logon failure: the specified account password has expired.

GLPCOM014E Failed to log on user: dsrdbm01.

GLPRDB111E The server is unable to use the username and password combination for the DB2 instance owner in the configuration file to establish a connection to the database.

GLPSRV064E Failed to initialize be_config.

GLPSRV040E Server starting in configuration only mode due to errors.

GLPCOM024I The extended Operation plugin is successfully loaded from libloga.dll.

GLPCOM024I The extended Operation plugin is successfully loaded from libidsfget.dll.

GLPSRV180I Pass-through authentication is disabled.

Following solution worked for me on windows platform:

when tds default local user account created (i.e. dsrdbm01) , by default "user must change password at next logon" is checked (lusrmgr.msc to open local users and groups manager) caused the above issue. I just unchecked and choose "password never expires" option and saved .

Reference:

http://tech.ivkin.net/wiki/IBM_Tivoli_Directory_Server_Fixes

IBM Tivoli Directory Server (TDS) v6.2 Installation

Have installed and published article related to TDS 6.2 installation earlier but I felt its not so clear, added more screen shots with better description this time (http://blog.sivavaka.com/2011/03/installing-tivoli-directory-server-62.html )

Extract and execute the "install_tds.exe"
Select the language and click ok

Click "Next" --> Accept the terms and click next -->

It detects DB2 location if you already have the DB2 installed on your machine

Select the installation location

Select the installation type i.e. typical or custom

Select the WAS application server location to install TDS web admin application, but have choosen to "deploy it manually later"

Click on "install" in the final summary page

Installation is successful

DB2 v9.7 Applying Fixpack (FP002)

NOTE : This fix need to apply or required if you are planning to create the TDS instance (IBM Tivoli Directory Server) on same DB2

Downloaded the fixpack (DB2-ntx64-universal_fixpack-9.7.200.358-FP002) from : http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg27007053

After download finished , extract it to temporary folder and click on /temp/universal/setup.exe to start setup launchpad

Click on the "install a product" and select the "existing product" and it displays the already installed db2 (make sure to stop if any db instances are running)

Once the installation is successful , validate the DB2Level just to make sure fix pack is applied properly

C:\IBM\DB2\BIN>db2level

DB21085I Instance "DB2" uses "64" bits and DB2 code release "SQL09072" with level identifier "08030107".

Informational tokens are "DB2 v9.7.200.359", and Fix Pack "2".

Product is installed at "C:\IBM\DB2" with DB2 Copy Name "DB2COPY1".

DB2 v9.7 database instance creation

NOTE: Click Here for DB2 Augmenting/Configuring to create the DB instance specific to Websphere Portal (where it require to additional tablespaces for JCR …etc specific to WebSphere Portal) .

Following describes how to create a simple database instance using the "DB2 first steps" wizard.

Following wizard allows to configure new DB database , allocate diskspace, notification, maintenance strategry and performances options . Give the DB2 database name

You can specify the storage space (Look at appendix below to resolve the problem while changing storage path )

You can specify maintenance strategy ( It is good to run the "RUNSTATS" periodically to calculate the table sizes … that will improve the overall DB performance )

Optionally , To enable the DB health notifications you can specify the unauthenticated SMTP server details

Following commands gets execute at backend

CREATE DATABASE RELDB AUTOMATIC STORAGE YES ON 'C:\';

UPDATE DB CFG FOR RELDB USING AUTO_MAINT ON;

UPDATE DB CFG FOR RELDB USING AUTO_TBL_MAINT ON;

UPDATE DB CFG FOR RELDB USING AUTO_RUNSTATS ON;

UPDATE ALERT CFG FOR DATABASE ON RELDB USING db.db_backup_req SET THRESHOLDSCHECKED YES;

UPDATE ALERT CFG FOR DATABASE ON RELDB USING db.tb_reorg_req SET THRESHOLDSCHECKED YES;

UPDATE ALERT CFG FOR DATABASE ON RELDB USING db.tb_runstats_req SET THRESHOLDSCHECKED YES;

Appendix

Changing the default storage path while creating the instance using wizard caused problem like below

SQL's executed for this are

CREATE DATABASE WPS7DB AUTOMATIC STORAGE YES ON 'C:\DB2\wps7db' DBPATH ON 'C:\IBM\DB2';

UPDATE DB CFG FOR WPS7DB USING AUTO_MAINT ON;

UPDATE DB CFG FOR WPS7DB USING AUTO_TBL_MAINT ON;

UPDATE DB CFG FOR WPS7DB USING AUTO_RUNSTATS ON;

UPDATE ALERT CFG FOR DATABASE ON WPS7DB USING db.db_backup_req SET THRESHOLDSCHECKED YES;

UPDATE ALERT CFG FOR DATABASE ON WPS7DB USING db.tb_reorg_req SET THRESHOLDSCHECKED YES;

UPDATE ALERT CFG FOR DATABASE ON WPS7DB USING db.tb_runstats_req SET THRESHOLDSCHECKED YES;

Error Details are :

SQL1052N The database path "C:\IBM\DB2" does not exist.

Explanation:

The path specified in the "<path>" parameter of the command is not valid. Either there is no path with that name, or a path has been specified when the DB2_CREATE_DB_ON_PATH registry variable is disabled (Windows only).

In a partitioned database environment on Windows or UNIX environments, each node in the partitioned database group must have the same hard drive specification (path) available with usable space for the CREATE DATABASE command to succeed. The hard drive path is specified in the database manager configuration. If DFTDBPATH is left blank the default will be the hard drive path where DB2 is installed on the instance owning machine (db2 installation path).

The command cannot be processed.

User response:

Resubmit the command with the correct database path.

In a partitioned database environment on Windows or UNIX environments, follow the following steps:

* Determine which hard drive specification (path) is required. The path is specified in the error message.

* Determine which node/s of the database partition are experiencing the problem. You can usually find this information in the db2diag log file of the instance owning node.

* Correct the drive problem on the node that is experiencing the problem, or change the drive specification in the database manager configuration so that the same drive is available and has sufficient space on each node of the partitioned database group.

* Re-issue the command.

* On Windows if all applications that will access the database are built on at least Version 9 external APIs then the DB2_CREATE_DB_ON_PATH registry variable can be enabled to support a

path as the database path.

To avoid this problem

stop the database
From the command prompt , run "db2set DB2_CREATE_DB_ON_PATH=YES"

C:\IBM\DB2\BIN>db2set DB2_CREATE_DB_ON_PATH=YES

Now , create the database as in above steps.

Reference

http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=%2Fcom.ibm.db2.udb.uprun.doc%2Fdoc%2Fr0022380.htm

DB2 v9.7 Installation

Open DB2 Setup Launchpad to install the DB2 Enterprise Server Edition v9.7 , it will install the DB2 copy with name "DB2COPY1

Selected Typical installation type

Give a path to save the installation settings in response file

Select the installation folder

Provide DB2 admin user and password

Default instance ("DB2") will be created during the installation (it stores application data)

You can configure this DB2 instance like port numbers ,named pipes and run as windows service

Named pipes are disabled by default but I have changed to NOT start DB2 service at system startup(Changed the auto start to manual)

DB2 Tools catalog must be created in order to use the Task center and scheduler. These tools allows you to schedule common tasks such as backups and this information stores in the DB2 database created above.

Unchecked or disabled the DB2 server automatic health notifications to alert admins (Need to provide the unauthenticated SMTP server details to enable these notifications)

Enabled the Operating System security for the DB2 files , folders and other objects . This step will create DB2ADMNS and DB2USERS groups in operating system.

Review all inputs before click finish.

Product to install	DB2 Enterprise Server Edition - DB2COPY1
Installation type	Typical
DB2 copy name	DB2COPY1
Set as default DB2 copy	Yes
Set as default IBM database client interface copy	Yes
Selected features	DB2 Update Service Base application development tools Base client support Configuration Assistant Connect support Control Center IBM Data Server Provider for .NET First Steps Spatial Extender client JDBC Support IBM Software Development Kit (SDK) for Java(TM) DB2 LDAP support ODBC Support OLE DB Support Replication tools Sample database source SQLJ Support DB2 WMI Provider
Languages	English
Target directory	C:\IBM\DB2
Space required	966 MB
Installation specific driver details
IBM Data Server Driver for ODBC and CLI name	IBM DB2 ODBC DRIVER - DB2COPY1
New instances
Instance name	DB2
Start instance on reboot	No
TCP/IP configuration
Service name	db2c_DB2
Port number	5OOOO
Instance user information
User name	db2admin

DB2 Administration server
Instance user information
User name	db2admin

DB2 tools catalog
Name	TOOLSDB
Schema	SYSTOOLS
Instance	DB2
Location	Local

Response file name	C:\Users\Siva\Documents\PROD_ESE.rsp

Successfully installed or copied the required files .

Need to make sure the following once the installation finished

DB2 Users and Groups

As we have enabled the DB2 security , need to make sure that all users ids(all users ids that interact with db2) are members of "DB2ADMNS" or "DB2USERS" group.

DB2 Installation Validation

Optionally to validate the DB2 installation files , instance and database functionality, run the " C:\IBM\DB2\bin\db2val.exe"
Make sure run as administrator (if using the different user other than db2admin)

C:\IBM\DB2\BIN>db2val

DBI1379I The db2val command is running. This can take several minutes.

DBI1333I Installation file validation for the DB2 copy DB2COPY1 was successful.

DBI1337I The partitioned database environment validation for the instance DB2 was successful.

DBI1339I The instance validation for the instance DB2 was successful.

DBI1343I The db2val command completed successfully. For details, see

the log file C:\Users\Siva\DOCUME~1\DB2LOG\db2val-Wed Mar 06 17_03_21 2012.log.

Check the response file for any exception during the installation (C:\Users\Siva\Documents\PROD_ESE.rsp)
Install DB2 License ( import db2ese_o.lic file)

References

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.wn.doc/doc/c0052035.html