Installing BIRT iHub in a cloud : Setting up iHub to use an alternative database : How to prepare the installation environment
 
How to prepare the installation environment
After extracting the contents of ActuateBIRTiHub.zip as described in “How to extract the contents of the iHub distribution package” earlier in this chapter, prepare the installation environment before running the setup script by performing the following tasks:
1 Using Windows Explorer or a command prompt, navigate to AC_SERVER_HOME\tools\install. For example:
C:\Actuate\iHub\tools\install
2 Using a text editor, open the readme.txt file that contains the preliminary setup instructions, as shown in Listing 6‑2:
Listing 6‑2 The readme.txt file
1. Install database client software onto the iHub node.
2. Configure the database client to access the databaseinstance to which you want to install the encyclopedia. In some cases, you may need to set the correct environmentvariables in the command window from which you run thescript. For example, to run the scripts on Unix with DB2as the database, you will need to configure environmentvariables such as DB2INSTANCE, INSTHOME, PATH and
LD_LIBRARY_PATH to make db2 commands accessible.
3. Create a "lib" folder under $AC_SERVER_HOME/tools/install.Copy JDBC driver jar from database client to this "lib"folder.
- For Oracle database copy ojdbc14.jar
- For DB2 database, copy db2jcc.jar
- For SQL Server database, copy sqljdbc4.jar
- For PostgreSQL database, copy postgresql-8.4-701.jdbc4.jar
4. Edit the install.properties file to add database connection properties and other required properties.
5. The script is called by other scripts, for examplestartiHub_Non_EmbeddedDB.bat. It can also be executedmanually as below:
ant -f install.xml install
3 Following the instructions in readme.txt, perform the following tasks:
1 Install an alternative database, such as DB2, Microsoft SQL Server, Oracle, or a pre-existing PostgreSQL server.
2 Run a SQL script containing the appropriate Data Definition Language (DDL) statements to create the iserver database. For example, when creating the database in a PostgreSQL server, run the following DDL commands:
1 Connect to the PostgreSQL system database as a user with full administrator privileges, typically named postgres, and execute the following SQL commands to create a database named iserver:
CREATE DATABASE iserver WITH OWNER = "postgres" TEMPLATE = template0 ENCODING = 'UTF-8';
REVOKE ALL ON DATABASE iserver FROM PUBLIC;
2 In the iserver database, create the plpgsql procedural language by executing the following SQL command:
CREATE LANGUAGE plpgsql;
plpgsql is a superset of PostgreSQL that supports advanced programming features, such as variables, conditional expressions, iterative constructs, and events. If the language is already installed, an error message appears. If so, ignore the message.
When the setupiHub script runs, as described in “How to set up iHub to use an alternative database,” later in this section, the script creates the following schema owner and application user accounts with appropriate privileges:
*iHub system schema owner
*Encyclopedia volume schema owner
*iserver application user
For more information about creating the iHub system and Encyclopedia volume schemas and iserver user in an alternative database, see Chapter 3, “Installing BIRT iHub using an alternative database.”
3 Create a lib folder in AC_SERVER_HOME/tools/install, and copy the JDBC driver JAR file specified for the database to the lib folder.
4 In a text editor, open the install.properties file, and specify all required and any necessary optional settings, as shown in Listing 6‑3.
The install.properties file requires settings for the following properties:
*AC_SERVER_HOME
iHub home folder, such as C:/Actuate/iHub. Use forward slashes in the path specification.
*SYSTEM_NAME
Set up automatically by the installation script. Do not change this property. Restrict system, schema, and the iHub application user names to alphanumeric and underscore characters with an initial alphabetic character in the pattern [a-z][a-z 0-9]*. Do not use a hyphen.
*DEFAULT_DATABASE _PASSWORD
Default database server administrator (DBA) or superuser password
if the user does not specify a password at the script prompt.
*Database-specific properties:
*jdbc.dbtype
Server type, such as DB2, Microsoft SQL Server, Oracle, or PostgreSQL.
*jdbc.serverName
Database server name.
*jdbc.portNumber
Database server port number.
*jdbc.databaseName
Database name, such as iserver.
*dba.name
Database administrator (DBA) name.
*dba.password
Database administrator (DBA) password. The installation script prompts for the password, so this value can be left at the default setting.
Listing 6‑3 specifies the required property settings for a PostgreSQL database as an example.
Listing 6‑3 The install.properties file
#Please specify the follow required properties: AC_SERVER_HOME, AC_DATA_HOME and AC_CONFIG_HOME
#for the iHub install. Do not use backslash ("\") in thepath. Always use forward slash ("/")
#on both Windows, Linux, or Unix.
 
#REQUIRED
#AC_SERVER_HOME, for example: D:/ActuateBIRTiHub/iHub
AC_SERVER_HOME=C:/Actuate/iHub
 
#OPTIONAL
#AC_DATA_HOME, for example: ${AC_SERVER_HOME}/data
 
#OPTIONAL
#AC_CONFIG_HOME, for example: ${AC_SERVER_HOME}/data/config
 
#REQUIRED
#Set up by the script automatically. User should not change it.
SYSTEM_NAME=#AC_SYSTEM_NAME#
 
#REQUIRED
#Database password that Installer asked for, which will beapplied to all DB related passwords, if user doesn'tspecify.
DEFAULT_DATABASE_PASSWORD=xxxxxx
 
#OPTIONAL
#APPLICATION_USER_PASSWORD=${DEFAULT_DATABASE_PASSWORD}
 
#OPTIONAL
#SYSTEM_SCHEMA_PASSWORD=${DEFAULT_DATABASE_PASSWORD}
 
#OPTIONAL
#VOLUME_SCHEMA_PASSWORD=${DEFAULT_DATABASE_PASSWORD}
 
#
#Specify database specifc properties. The database typessupported are Microsoft SQL Server, Oracle, DB2, andPostgreSQL.
...
jdbc.dbtype=PostgreSQL
jdbc.serverName=localhost
jdbc.portNumber=8432
jdbc.databaseName=iserver
 
#define the target database
dba.name=postgres
dba.password=xxxxxx
...