Chapter 3. Implementation of a virtualized business intelligence cloud
3.1.2 The application server tier
The application server tier of the InfoSphere Warehouse topology is used to support the InfoSphere Warehouse
Administration Console
. The Administration Console is a web browser-based client for administering functions, such as SQLWarehousing processing, Cubing Services, Intelligent Miner, and warehouse system resources. In the Administration Console, the warehouse application packages are deployed into executable modules that can be run or scheduled for execution on a production environment. All configurations added into the
Administration Console rely on a metadata database hosted in the InfoSphere Warehouse database server and on a WebSphere Application Server
environment:
Metadata Database
This component is a required repository database for storing InfoSphere Warehouse configurations that are added in the Administration Console. You can either create the database before starting the installation or the
installation program can create it for you. The metadata database must be created in a non-partitioned database.
WebSphere Application Server
This component is an IBM runtime environment to support web accessible, distributed, and Java-based applications. This application server layer serves as a platform to deliver business application services to clients based on an SOA architecture. Every service that is created within WebSphere Application Server is secured, scalable, and reusable. The Integrated Solutions Console is the administration interface to manage the InfoSphere Warehouse
Administration Console application and its role-based security.
The application server also includes the Administration Console command-line client, DB2 10 client, and Cubing Services components. The DB2 client is a lightweight software that is installed to provide remote connectivity to the database server sources. Using the DB2 client, you can catalog database servers and databases and add them within the Administration Console.
Figure 3-3 depicts the InfoSphere Warehouse application server components.
Figure 3-3 InfoSphere Warehouse Application Server components
To install the application server component of InfoSphere Warehouse on a Linux guest:
1. First install the Installation Manager and WebSphere Application Server. The following examples provide sample commands for installing IBM Installation Manager and WebSphere Application Server V8.0 silently.
a. Install the Installation Manager as shown in Example 3-7.
Example 3-7 Command to install the installation manager
/temp/installc -acceptLicense
b. Record a response file to install the WebSphere Application Server as shown in Example 3-8.
Example 3-8 Command to record the install of WebSphere Application Server
/opt/IBM/InstallationManager/eclipse/IBMIM -skipInstall
/var/temp/imRegistry -record /var/temp/install_response_file.xml c. Use the response file to install the product as shown in Example 3-9.
Example 3-9 Command to install using the Installation Manager
/opt/IBM/InstallationManager/eclipse/tools/imcl -acceptLicense input /var/temp/install_reponse_file.xml
2. Edit the response file to meet your installation requirements. The sample PROC_ISW.rsp response file is located in the ResponseFiles directory of the installation image.
Example 3-10 illustrates a sample response file that is generated by the installation wizard to install the InfoSphere Warehouse application server.
Example 3-10 Sample response file to install application server
#Profile using variables #---
PRODUCT_NAME=IBM InfoSphere Warehouse EXCLUDED_FEATURES=
#Disable OS Pre-requisite checking #--- DS_IGNORE_OSPREREQ=FALSE
#Has the license been accepted #--- #LICENSE_ACCEPTED=TRUE #Installation Directory #--- USER_INSTALL_DIR=/opt/IBM/ISWarehouse INSTALL_NEW_COPY=true
#Selected Features in the Choosen Install Sets panel #---
CUSTOM_CHOSEN_INSTALL_FEATURE_LIST=WHADM,CLIENT,WAS,DSWeb,WEB_IM,WEB _CS,WEB_SQW,WEB_UTA,ADMINCLIS,Cubing
#WebSphere Applicaiton Server #---
was.installLocation=/opt/IBM/WebSphere/AppServer #WebSphere Applicaiton Server Profile Name #--- PROFILE_NAME=AppSrv01
#WebSphere Security #---
#set below variable if create new WAS profile WAS_SECURITY_USER=root
#---
#set below variable if work with existing WAS profile SecurityUser=dweadmin
SecurityPassword=axfe02ki3kdi383 SecurityPasswordEncrypted=true #Meta Data Panel
#---
MetaData.database.name=DSSDB MetaData.database.port=db2inst1 MetaData.database.host=iswdbserver #Option of metadata database
# -CREATE_NEW_FOR_NEW_DB : create new database # -NEWESE_REUSEDB : re-use existing database
# -CREATE_NEW_FOR_LOCAL_DB : re-use ESE and create new database # -REUSEESE_REUSEDB : re-use ESE and re-use existing database MetaData.database.dbStatus=CREATE_NEW_FOR_NEW_DB MetaData.database.user=db2inst1 MetaData.database.password=axfe02ki3kdi383 MetaData.database.encrypted=true #Database type # - DB2LUW # - DB2Z # - INFORMIX_JDBC MetaData.database.type=DB2LUW MetaData.database.idsServer= MetaData.database.createNewDB=true
#set below variable re-use ESE and create database REPDB_DB2INST_LOCATION=/opt/IBM/ISWarehouse/db2/V10.1 REPDB_DB2INST_NAME=DB2
You can edit the following information: – Product license
The product license must be accepted to continue with the installation. The default value for the LICENSE_ACCEPTED parameter is TRUE. – Installation path
You can change the installation path in the USER_INSTALL_DIR variable. By default the installation path for InfoSphere Warehouse on Linux is the /opt/IBM/ISWarehouse directory.
– Individual components
You can customize the components that are to be installed by adding or removing values from the CUSTOM_CHOSEN_INSTALL_FEATURE _LIST variable.
Example 3-11 shows the list of features that you can add for an application server installation.
Example 3-11 Edit the features list variable to add or remove features
#To add or remove Features, edit the following values from the variable Custom #Choosen Install Feature List:
# -WHADM: installs the administration console # -CLIENT: installs the db2 client
# -WAS: creates a WAS profile
# -WEB_IM: Intelligent Mining administration # -WEB_CS: Cubing Services administration # -WEB_SQW: SQL Warehouse administration # -WEB_UTA: Unstructured Text Analysis
# -ADMINCLIS: Administration Console Command Line Client # -Cubing: Cubing Services
#---
CUSTOM_CHOSEN_INSTALL_FEATURE_LIST=WHADM,CLIENT,WAS,DSWeb,WEB_IM, WEB_CS,WEB_SQW,WEB_UTA,ADMINCLIS,Cubing
– WebSphere Application Server instance, profile, and operating system user
Specify the location of the WebSphere Application Server installation, a name for a WebSphere Application Server profile, and a local operating system user to enable WebSphere Application Server global security. – Metadata connection
Provide the connection details to log in to the database server where the repository database is storing warehousing metadata. You can either create the database before starting the installation, or the installation program can create it for you. The default name of this database is DSSDB.
– Passwords
When you create a response file using the installation wizard, the passwords are encrypted by default. However, if you need to modify the passwords before the silent installation, you can set the encryption property value to false and set the value to the actual passwords that you want to use.
Example 3-12 shows how to change the password in the response file.
Example 3-12 How to change the password on the response file
MetaData.database.user=db2inst1 MetaData.database.password=apassw0rd MetaData.database.encrypted=false
The password length can be up to the maximum number of characters that are supported by your operating system.
3. After you customize or generate the response file according to your requirements, create a shell script. Embed the command to install the InfoSphere Warehouse application server silently on a new VM when it is required to be replicated.
Example 3-13 shows the command to pass the response file that you created to install the application server on Linux.
Example 3-13 Command to install the application server with a response file
iswappserver:/temp/wh_server # isw/install.bin -i silent -f /temp/PROC_ISW.rsp -Dprofile=/temp/wh_server/isw/profile/
4. When the installation is completed, a message indicates the outcome of the installation. If the installation fails, investigate the log files to troubleshoot the problem. The logs are located in the default directory for installation, the /opt/IBM/ISWarehouse/logs directory for Linux and UNIX.