IBM. IBM Emptoris Suite Configuring. IBM Emptoris Suite SaaS

Transcription

1 IBM Emptoris Suite IBM IBM Emptoris Suite Configuring SaaS

2

3 IBM Emptoris Suite IBM IBM Emptoris Suite Configuring SaaS

4 ii IBM Emptoris Suite: IBM Emptoris Suite Configuring

5 Copyright Note: Before using this information and the product it supports, read the information in Notices on page 161. Copyright IBM Corporation 2012, All rights reserved. Copyright Emptoris 1999, All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GS ADP Schedule Contract with IBM Corp. Copyright IBM Corp. 2012, 2016 iii

6 iv IBM Emptoris Suite: IBM Emptoris Suite Configuring

7 Contents Copyright iii Chapter 1. Database Configurations... 1 Introduction to Database Configurations Deployment options for database servers Two DB2 Instances Schemas for Emptoris Applications Configuring Database Servers for Emptoris Products for the First Time Configurations for the Oracle Database Configurations for the DB2 Database Manually Configuring the Database Servers for Emptoris Products Emptoris Spend Analysis Database Server Upgrading Database Servers for Emptoris Products 49 Upgrading Oracle Servers Upgrading DB2 Servers Reporting Database Servers Data At Rest Encryption (DARE) Servers that are Encrypted in the Emptoris setup 52 Roles and Responsibilities for Setting Up Encryption Encryption on Oracle Encryption on DB Encryption on MySQL Troubleshooting DARE Chapter 2. Reporting Configurations.. 69 Introduction to Reporting Reporting for Emptoris Applications Installation Files that are provided by IBM Emptoris for Reporting Reporting for Emptoris Contract Management.. 71 Reporting for Emptoris Spend Analysis Reporting for Emptoris Supplier Lifecycle Management Installing and Configuring InfoSphere DataStage 106 Prerequisite Software for InfoSphere DataStage 107 Preparing to run the InfoSphere DataStage Installation Installing InfoSphere DataStage as a non-root user Installing InfoSphere DataStage Post-installation Tasks for InfoSphere DataStage 110 Installing and Configuring Cognos Prerequisite Software for Cognos Installing Cognos Upgrading Cognos to Post-Installation Tasks to Configure Cognos for Emptoris Applications Installing Database Clients Installing and Configuring Oracle Database Client Installing and Configuring the DB2 Client Upgrading Reporting Upgrading the Emptoris Contract Management Reporting Database Upgrading InfoSphere DataStage from Version to or Upgrading Cognos Business Intelligence Backing up, Restoring and Recovering Reporting Systems Difference Between Exporting Content Store and Database Backup Backup Plan before Upgrading Backing up Reporting Systems Recovery Scenarios Moving the Content Store and Data Warehouse to a Different Server Restoring Reporting Database Under a New Name Troubleshooting and Tips ETL Job Failures InfoSphere DataStage Issues Cognos Issues EchOS build fails when starting the Analytics Integration module Accessing and Configuring Reporting Components 157 Reporting Module Version in Use Downloading ISALite Installing ISALite on Linux Accessing the Cognos configuration tool on Windows Accessing the Cognos configuration tool on Linux Related Documents Notices Copyright IBM Corp. 2012, 2016 v

8 vi IBM Emptoris Suite: IBM Emptoris Suite Configuring

9 Chapter 1. Database Configurations All IBMEmptoris applications except IBM Emptoris Spend Analysis use Oracle or DB2 database servers. Emptoris Spend Analysis requires MySQL database servers. This section provides information about configuring the Oracle and DB2 servers. It does not provide the installation information for the servers. You must refer to the respective installation docs. Information for downloading and installing the MySQL server is provided in this section. Introduction to Database Configurations IBMEmptoris applications use Oracle, DB2, or MySQL database servers. You must install the required database servers before you install the Emptoris products. The databases are configured for the Emptoris applications by using the Emptoris Strategic Supply Management Installer. The following table displays the database servers that are required to be installed for the corresponding Emptoris products. Table 1. Database servers Database server DB2 database server: IBM DB2 Universal Database (UDF) Enterprise Server Edition (ESE) Oracle database server: Oracle Database 12c Server Release 1 Standard and Enterprise Editions MySQL Community Server Product Name v Emptoris Sourcing v Emptoris Contract Management* v Emptoris Strategic Supply Management Platform v Emptoris Supplier Lifecycle Management v Emptoris Program Management Note: * Emptoris Contract Management is available only on Linux. v Emptoris Sourcing v Emptoris Contract Management v Emptoris Strategic Supply Management Platform v Emptoris Supplier Lifecycle Management v Emptoris Program Management Emptoris Spend Analysis Information about database server installations is not provided. Refer to the installation guides from the respective database software vendors for the installation instructions. Deployment options for database servers You can use Oracle and DB2 database servers for all applications in the Emptoris Suite, except Emptoris Spend Analysis. For Emptoris Spend Analysis, the MySQL database server is used. Copyright IBM Corp. 2012,

10 The following diagram depicts the possible options of deployment of database servers. Figure 1. Deployment options for database servers The following products can be installed on an Oracle or DB2 server: v Emptoris Strategic Supply Management Platform v Emptoris Sourcing v Emptoris Contract Management 2 IBM Emptoris Suite: IBM Emptoris Suite Configuring

11 v Emptoris Spend Analysis v Emptoris Supplier Lifecycle Management v Emptoris Program Management v IBM InfoSphere DataStage v IBM Cognos Business Intelligence Emptoris Strategic Supply Management Platform and Emptoris Program Management share database and must be on a single server. All other potential combinations are supported for installing the databases. You can also install all databases on the same server. DB2 for Emptoris Contract Management, InfoSphere DataStage, and Cognos are supported only on Linux systems. Restriction: If you are planning to install the databases on a single DB2 server, you must install two DB2 instances. For more information, see Two DB2 Instances. Two DB2 Instances Two DB2 instances are required for the Emptoris applications and reporting. One instance is for the Emptoris applications with the Oracle Compatibility Vector property enabled. The other instance is for Reporting with the Oracle Compatibility Vector property disabled. If the property is enabled for reporting, Cognos Content Store creation fails. The two instances can be on the same or different systems. The following diagram represents the DB2 instances that are required. Figure 2. Two DB2 instances The reporting schemas can be created only in the DB2 native mode, which is the default mode. However, the Emptoris Suite schemas require DB2 in the Oracle Compatible mode. Therefore, the reporting databases must be created in a separate DB2 instance. One database instance can have all Emptoris products. The other instance can have the Contract Management Reporting database, Cognos Content Store, and InfoSphere DataStage. Chapter 1. Database Configurations 3

12 Schemas for Emptoris Applications You can use an Oracle or DB2 database for all Emptoris applications, except for Emptoris Spend Analysis. For Emptoris Spend Analysis, MySQL is used. For all the databases, schemas are required for the respective applications. The following table lists the schemas for the Emptoris applications on Oracle or DB2 and MySQL. Table 2. Schemas on Oracle or DB2 and MySQL. Schemas on Oracle or DB2 and MySQL databases. Schema SSM and PGM Sourcing SLM Contracts, Contracts RUSER, Contracts Reporting Cognos InfoSphere DataStage schemas Spend Description Schema for Emptoris Strategic Supply Management Platform and Emptoris Program Management. Schema for Emptoris Sourcing. Schema for Emptoris Supplier Lifecycle Management. Emptoris Contract Management has the following schemas. v v v Main schema: OLTP RUSER: User with read only permissions on views Reporting Schema: DW for reporting Schema for the Content Store to store the internal metadata for Cognos. InfoSphere DataStage includes the following schemas. v v Xmeta Xmetasr Schema for Emptoris Spend Analysis on MySQL. Schemas on Oracle and MySQL The Oracle database can be used for all applications except for Emptoris Spend Analysis. Emptoris Spend Analysis requires the MySQL database server. The following image shows the schema for each application on the Oracle and MySQL databases. 4 IBM Emptoris Suite: IBM Emptoris Suite Configuring

13 Figure 3. Oracle schemas for Emptoris applications In the image, the following schemas are co-located. All Emptoris applications schemas except the schema for Emptoris Spend Analysis can be co-located on the same database. However, it is a good practice to separate the transactional database from the reporting data warehouse, which is the Emptoris Contract Management reporting schema. The schema for Emptoris Spend Analysis is on the MySQL database. Tip: If you plan to use Windows, it is recommended to install the xmeta schema on a DB2 database. InfoSphere DataStage installation might fail if it is installed on a Windows operating system on Oracle. Schemas on DB2 and MySQL The DB2 database can be used for all applications except for Emptoris Spend Analysis. Emptoris Spend Analysis requires the MySQL database server. For the Emptoris applications and reporting, two instances are required on the database. The following image shows the schema for each application on the DB2 and MySQL databases. Chapter 1. Database Configurations 5

14 Figure 4. DB2 schemas for Emptoris applications One database instance can have all Emptoris products except Emptoris Spend Analysis. The other instance can have the Contract Management Reporting database, Cognos Content Store, and two schemas for InfoSphere DataStage. The schema for Emptoris Spend Analysis is on the MySQL server. Schema and Seed Data The schema for each Emptoris product is populated at various levels during installation. Seed data import is also required for Emptoris SourcingEmptoris Contract Management. The following table lists how schema and seed data is populated for Emptoris products. 6 IBM Emptoris Suite: IBM Emptoris Suite Configuring

15 Table 3. Schema and seed data. Schema and seed data Product Oracle database DB2 database v Emptoris Strategic Supply Management Platform - Emptoris Program Management v Emptoris Supplier Lifecycle Management v Emptoris Spend Analysis Emptoris Sourcing Emptoris Contract Management v Reporting v Cognos Content Store v InfoSphere DataStage Done by the application on initial start Seed data must be imported by using the import utility Seed data must be imported by running commands Done by the application on initial start Done by the application on initial start Done by the application on initial start Done by scripts Done by the application on initial start Schema Sizes The schema sizes must be monitored constantly and increased as required. The following table lists the schema sizes. Table 4. Schema sizes on Oracle, DB2, and MySQL. Schema sizes on Oracle, DB2, and MySQL Schema Database Description SSM and PGM Oracle or DB2 +10% of current size Sourcing Oracle or DB2 +10% of current size SLM Oracle or DB2 +10% of current size Contracts Oracle or DB2 +10% of current size Contracts RUSER Oracle or DB2 0 - this schema has no objects Contracts Reporting Oracle or DB % of OLTP schema Cognos Oracle or DB2 +10% of current size InfoSphere DataStage schemas Oracle or DB2 v Xmeta: 5G v Xmetasr: 5G Spend MySQL Depends on the installation Consider the following points for the schema size. v Consider 5G for each schema if the projected size has not been estimated. v For a new installation, the seed data for each schema is between 100M 200M. v If you are planning on migrating content from legacy systems, monitor the data growth as you gradually import users, organizations, contracts, and so on and adjust your size projections accordingly. Memory configuration for the DB2 database Use the values in the following table as guidelines for memory configuration for the DB2 database. Chapter 1. Database Configurations 7

16 Table 5. Memory Configuration for DB2 Server Requirements Small Medium Large Total DB size 10G 50G-100G 100G-500G Memory 16 GB 32 GB 64 GB GB CPU Configuring Database Servers for Emptoris Products for the First Time Emptoris products use Oracle, DB2, or MySQL database servers. The first-time configurations for the Oracle and DB2 servers are now completed by running scripts. Some manual tasks are still required based on the products that you choose to install. The database that is created for Emptoris Strategic Supply Management Platform is used by all other Emptoris products. Each application has its own database schema that is created either by running scripts or commands. Configurations for the Oracle Database If you choose to use Oracle as your database server, you must use Oracle 12c Release 1 Standard and Enterprise Editions for the Emptoris applications. Steps for configuring the Oracle database To configure the Oracle database for the Emptoris applications, complete the following steps: 1. Complete the following prerequisite tasks. a. Create the database. b. Configure parameters. c. Create the table space. 2. Run the script to configure the database. The following tasks are automatically completed when you run the script. v User that is required for the database is created. v Schema for the products that you choose to install is created. Prerequisites for the Oracle Database Server To configure the Oracle database server for Emptoris products, you must create the database, configure certain parameters, and create table spaces. Creating Oracle Database: Creating the Oracle database is the first prerequisite step to configure the Oracle database server for Emptoris products. Procedure To create the database, use the following parameters: 1. Character set AL32UTF8 and National Character set AL16UTF16 2. Database block size 8 K 8 IBM Emptoris Suite: IBM Emptoris Suite Configuring

17 What to do next Configuring Parameters for the Oracle Database Configuring Parameters for the Oracle Database: After you create the Oracle database, you must configure the database with certain parameters. Configuring the database is the second prerequisite step for the Oracle database. Before you begin Creating Oracle Database on page 8 Procedure To configure the Oracle database, complete the following steps: 1. Log in to the database as the database administrator. 2. For Oracle 12c, set the optimizer_adaptive_features parameter to false. ALTER SYSTEM SET OPTIMIZER_ADAPTIVE_FEATURES=FALSE ; 3. For Emptoris Contract Management or Emptoris Sourcing, if the select DBTIMEZONE from dual parameter is set to Coordinated Universal Time (UTC) offset such as +00:00, change the named time zone region to US/Eastern by using the ALTER DATABASE SET TIME_ZONE parameter. The following example shows the change in the time zone name. ALTER DATABASE SET TIME_ZONE= US/Eastern ; 4. Restart the database if you changed the time zone name. 5. Verify the time zone name by checking the output of the DBTIMEZONE from dual parameter. What to do next Creating Table Space on the Oracle Database Creating Table Space on the Oracle Database: After you created the Oracle database and configured the parameters, you must create the table space. Creating the table space is the third prerequisite step for the Oracle database. Before you begin 1. Creating Oracle Database on page 8 2. Configuring Parameters for the Oracle Database Procedure To create the table spaces on the Oracle database, complete the following steps: 1. Create one or more table spaces for the Emptoris products that you plan to install. 2. Specify a minimum of 4 GB for the table space size. 3. Periodically check the database size and adjust the table space size. 4. Configure the table space to autoextend with a maxsize such as 10 GB. Chapter 1. Database Configurations 9

18 Recommended Parameters for Oracle Database: You must configure the parameters that are required for the Oracle database in the init.ora file based on the database size. Parameters that are based on the database size Some parameters that are required for the Oracle database are based on the database size, while some others are not based on the size. The following table lists the parameters and their recommended values based on the database size. Table 6. Parameters that are based on the database size. Parameters that are based on the database size Parameters Small Medium Large DB Size 1G-50G 50G-100G 100G-500G open_cursors processes sga_max_size 8G 15G 30G sga_target 8G 15G 30G pga_aggregate_target 2G 3G 5G sessions large_pool_size 100M 100M 100M dml_locks Parameters that are not based on the database size The following table lists the parameters and their recommended values. Table 7. Parameters that are not based on the database size. Parameters that are not based on the database size. Parameters cursor_sharing Value SIMILAR sort_area_size work_area_size_policy undo_management db_keep_cache_size AUTO AUTO 32K Running the Script on Oracle After you configured the Oracle database, you must run the script that is provided in the installation files to create users and grant them permissions. Before you begin You must have the Oracle client running on the system from where you run the script. The user who runs the script must also have access to run sqlplus from the system. 10 IBM Emptoris Suite: IBM Emptoris Suite Configuring

19 About this task The database script to create users and grant them permissions is available in the dbscripts directory in the installation files in the EMP_Resources_ _xx.zip file. Procedure To create users and grant them permissions on Oracle, complete the following steps: 1. Log in to the database server as an operating system user who has database administrator rights. 2. Run the create-suite-db script. v v Windows: create-suite-db.bat Linux: create-suite-db.sh For Windows:./create-suite-db.bat "userid/password@database as sysdba" For Linux: chmod +x *.sh./create-suite-db.sh userid/password@database as sysdba Results The script prompts you to check whether the prerequisite tasks are met. It also checks the database connection. You are prompted to create the users for the products that you plan to install. The following output is seen when you run the script. [oracle@ora11g dumps]$./create-suite-db.sh sys/sa@ :1521/qadb02 as sysdba ################################################################################################## Prerequisite: **************** To configure the Oracle database for the Emptoris applications, complete the following steps: 1. Create the database with following: # Character set AL32UTF8 and National Character set AL16UTF16 # DB Block size 8K 2. Configure the database. 2.1 The database time zone must be specified using the named time zone region instead of the # This is must if you are planning to install IBM Emptoris Sourcing or IBM Emptoris Contract Example - Login as SYSDBA - If output of select DBTIMEZONE from dual is in UTC offset like +00:00 - Then it can be changed to named time zone region US/Eastern for example using below com - ALTER DATABASE SET TIME_ZONE= US/Eastern ; - Restart the Database to take this into effect - You can verify by checking output of select DBTIMEZONE from dual after restart 2.2 For 12c, we recommend to set optimizer_adaptive_features to false Example - Login as SYSDBA - ALTER SYSTEM SET OPTIMIZER_ADAPTIVE_FEATURES=FALSE ; 3. Create tablespace(s) - Create one or more tablespace that will be used for products - We recommend that you specify minimum 4 GB for table space size. - You should check the database size and adjust the tablespace periodically. - You can also configure the tablespace to autoextend with a maxsize, for example of 10 GB. Chapter 1. Database Configurations 11

20 Recommended Settings ********************* Use the following table as a guide to tune the database configuration in the init.ora file. The table includes the recommended Oracle parameters for different size configurations. ============================================================== Parameters Small Medium Large ============================================================== DB Size 1G-50G 50G-100G 100G-500G open_cursors processes sga_max_size 8G 15G 30G sga_target 8G 15G 30G pga_aggregate_target 2G 3G 5G sessions large_pool_size 100M 100M 100M dml_locks Following are the other parameters that are not dependent on the database size: ============================================================== Parameters Value ============================================================== cursor_sharing SIMILAR sort_area_size work_area_size_policy AUTO undo_management AUTO db_keep_cache_size 32K Execute Script : **************** After verifying pre-requisite, you can execute script to create user(s) Example - Login as Oracle DB owner OS user./create-suite-db.sh sys/sa as sysdba ##################################################################################################### Have you configured database to meet pre-requisite mentioned in help and want to continue (Y/N)? y Please select an option to create user for : 1 IBM Emptoris Virtual Supplier Master 2 IBM Emptoris Supplier Lifecycle Management 3 IBM Emptoris Sourcing 4 IBM Emptoris Contract Management 5 IBM Emptoris Contract Management Reporting (RUSER) 6 IBM Emptoris Reporting 7 IBM Emptoris Cognos Contents Store 0 Exit 1 Selected Option 1 Connecting to database and creating user for IBM Emptoris Virtual Supplier Master Please provide user name to be created :pranav_vsm Enter Password new User : emptoris Enter Default Tablespace name (Default USERS): 12 IBM Emptoris Suite: IBM Emptoris Suite Configuring

21 Enter Temp Tablespace name (Default TEMP): Inputs validated - Creating user pranav_vsm PL/SQL procedure successfully completed. do you want create user for other product [Press Enter or Y to continue. Enter N to Exit]? n What to do next You must import the seed data for Emptoris Contract Management and Emptoris Sourcing. For more information, see the following topics. v Importing Seed Data for Emptoris Contract Management v Importing Seed Data for Emptoris Sourcing Importing Seed Data for Emptoris Contract Management After you run the script for configuring the Oracle database and have also created the user/schema by using the script, you must import seed data for Emptoris Contract Management. About this task The seed data file for Emptoris Contract Management is ecm_seed_data.dmp, and is available in the EMP_Resources_<version>_<build>.zip file in the installation files. The seed data file contains the default table space as USERS. If you want to create a different table space, you must use the REMAP_TABLESPACE=USERS: <table space name> command when you run the import data command. Procedure To import the seed data dump for Emptoris Contract Management, complete the following steps: 1. Log in to the database with DB administrator or SYSDBA privilege. 2. Create a database directory, or use an existing directory. To know the existing database directory and its path, run the following command. select * from dba_directories; Use the following command to create the directory. create or replace directory testdir as /home/oracle/dumps ; grant read, write on directory testdir to public; -- If you want to give grant to a specific u 3. Copy the ecm_seed_data.dmp file to the directory. 4. To import the data, run the following command. impdp directory=testdir dumpfile=ecm_seed_data.dmp remap_schema=ecm:<user name> remap_tablespac The following example shows the import of data in the ecm_dp user in the ecm_new tablespace. impdp directory=testdir dumpfile=ecm_seed_data.dmp remap_schema=ecm:ecm_dp remap_tablespace=use 5. To export the seed data, use the following command. expdp ecm/emptoris file=ecm_seed_data.dmp directory=testdir logfile=expdp_ecm_seed_data.log Importing Seed Data for Emptoris Sourcing After you run the script for configuring the Oracle database, you must import seed data for Emptoris Sourcing. Chapter 1. Database Configurations 13

22 About this task The seed data file for Emptoris Sourcing is esp_seed.dmp, and is available in the EMP_Resources_<version>_<build>.zip file in the installation files. Procedure To import seed data for Emptoris Sourcing, complete the following steps: 1. Log in to the database with DB administrator or SYSDBA privilege. 2. Assign unlimited quota to the user on the default table space for the schema. 3. Create a database directory, or use an existing directory. To know the existing database directory and its path, run the following command. select * from dba_directories; Use the following command to create the directory. create or replace directory testdir as /home/oracle/dumps ; grant read, write on directory testdir to public; -- If you want to give grant to a specific use 4. Extract the Emptoris Sourcing product build file to the directory to get the esp_seed.dmp file. 5. To import the data, run the following command. impdp directory=testdir dumpfile=esp_seed.dmp remap_schema=esp:<user name> remap_tablespace=users The following example shows the importing of data into the esp_dp user and in the esp_new tablespace. impdp directory=testdir dumpfile=esp_seed.dmp remap_schema=esp:esp_dp remap_tablespace=users:esp_ 6. Emptoris Sourcing schema should have the SELECT privilege on the SYS.ALL_USERS view to avoid errors when the server starts. To make sure that the privilege is granted, complete the following steps. a. Run the following query to check if the privilege is granted. select substr(owner,1,20) owner,substr(table_name,1,20) tabname,substr(privilege,1,20) priv fr The following output is seen. OWNER TABNAME PRIV SYS ALL_USERS SELECT If the output is not seen, you must grant the privilege. b. Run the following command to grant the privilege. grant select on sys.all_users to <schema name>; 7. To export the seed data, use the following command. expdp <user name>/<password> file=esp_seed.dmp directory=testdir logfile=expdp_esp_seed.log Configurations for the DB2 Database If you choose to use DB2 as your database server, you must use DB and later for the Emptoris applications. To configure the DB2 database for Emptoris applications, complete the following steps: 1. Complete the prerequisites. The prerequisites involve the following steps: a. Set up and configure a database instance. b. Create an operating system user for every Emptoris product that you plan to install. 14 IBM Emptoris Suite: IBM Emptoris Suite Configuring

23 2. Run the database configuration script that is provided in the installation files. The following configuration steps are completed when you run the script. a. Application users are created for each Emptoris application. b. Permissions are granted to the users. c. Application schemas are created. d. Seed data for Emptoris Contract Management is created. Prerequisites for the DB2 Database Server Before you run the script to configure the DB2 database, you must create a database instance and create the operating system user for every Emptoris application that you plan to install. Setting up a DB2 Instance for Emptoris Applications: The prerequisite to configuring the DB2 database for the Emptoris applications is to set up an instance. If you are planning to use a single database server for all Emptoris applications, a single instance of DB2 is required. If you are planning to use separate servers, you must create instances on all those servers for the Emptoris applications. Two instances when using the reporting module If you are planning to use the reporting module for Emptoris Contract Management and Emptoris Spend Analysis, two instances are required on the DB2 server: one for the reporting module and the other for the Emptoris applications. Two instances are required to ensure that the Oracle Compatibility Vector property is not enabled for Cognos. If the property is enabled, Cognos Content Store creation fails. Steps for setting up an instance Prerequisite: DB2 Database Server and later on Linux Setting up an instance is a one-time activity and requires that you restart the instance after setting it up. To set up a DB2 instance, complete the following steps: 1. Log in to the server as instance owner. 2. Create a DB2 instance if does not exist by using the db2icrt command. 3. Configure the port number by setting the svcename and DB2COMM parameters. 4. Restart the instance by using the following commands. db2stop force db2start 5. Verify the parameters by using the db2set -all command. [db2inst1@ db2db ~]$ db2set -all [i] DB2COMM=TCPIP [g] DB2SYSTEM=db2db.ibm.com [g] DB2INSTDEF=db2inst1 [g] DB2ADMINSERVER=dasusr1 Chapter 1. Database Configurations 15

24 Example The following script is an example of creating a new instance in Linux and configuring the port number. [root@devdb2 ~]# useradd -u g db2iadm1 -m -d /home/db2inst2 db2inst2 -p passw0rd [root@devdb2 ~]# cd /opt/ibm/db2/v10.5/instance [root@devdb2 ~]#./db2icrt -u db2fenc1 db2inst2 [root@devdb2 ~]# vi /etc/services #new entry for db2 instance 2 db2c_db2inst /tcp [root@devdb2 ~]# su db2inst2 db2 update database manager configuration using svcename db2c_d2inst2 db2set DB2COMM=tcpip db2stop db2start Next step After setting up the instance, proceed to creating an operating system user. Creating the Operating System User: An operating system user is required on the DB2 instance. The user must also be granted permissions for the application schemas. You can have a common operating system user for all the Emptoris applications that you plan to install on the instance. However, that results in multiple schemas sharing a table space. To have separate table spaces for the Emptoris applications, create separate operating system users for the Emptoris applications that you plan to install. About this task Consider the following points for creating the user: v If you are using DB2 on Windows, the user must belong to the DB2 users group. v For Linux, the user name must be less than 8 characters and in lowercase. v If you are using DB2 on UNIX, the UNIX users, groups, and instance names must all be in lowercase. v The values that you enter in the Emptoris Strategic Supply Management Installer for the user name must match the user name on the operating system. v When you upgrade to a new version of an Emptoris product, you can reuse the current DB2 database name, schema, and user name for the installation. Example Creating a Linux user ssmdev1. [root@devdb2 ~]# adduser ssmdev1 [root@devdb2 ~]# passwd ssmdev1 Buffer Pools and Table Spaces: The suite database creation scripts create the required buffer pools and table spaces for the Emptoris applications. The following table spaces and buffer pools are created. 16 IBM Emptoris Suite: IBM Emptoris Suite Configuring

25 Table 8. Buffer pools and table spaces Name Pagesize Buffer pool Temp Buffer pool Temp table space For each product: Table space. For data and indexes Run the following commands to verify that the buffer pools and table spaces are created. CONNECT TO <Database> SELECT TBSPACE, OWNER, OWNERTYPE,PAGESIZE FROM SYSCAT.TABLESPACES; SELECT BPNAME, PAGESIZE FROM SYSCAT.BUFFERPOOLS ; Running the Scripts on DB2 After you configured the DB2 instance, you must run the scripts that are provided in the installation files to create the database, grant permissions to the users, and create schemas. About this task The scripts to create the database and schemas for the Emptoris Suite are available in the EMP_Resources_ _xx.zip file in the installation files in the db-scripts\db2\suite-scripts directory. Procedure To run the script on DB2, complete the following steps: 1. Copy the db-scripts\db2\suite-scripts file to the DB2 server. 2. Make the user, who is the instance owner, the owner of the files. 3. Run the script as the instance owner by completing the following steps. Table 9. Running the DB2 script on Linux and Windows Linux 1. Change to the DB2\suite-scripts directory. 2. Grant execute permission to the.sh files. chmod +x *.sh chmod +x bin/*.sh Windows Run the script from a DB2 command window: Start > All Programs > IBM DB2 > DB2Copy1 > DB2 Command Window Administrator Note: DB2 on Windows is not supported for Emptoris Contract Management and Reporting. 4. Run the create-suite-db script to create the database. v v Windows: create-suite-db.bat Linux: create-suite-db.sh The instance parameters are configured and DB2 is restarted. 5. Run the create-suite-schemas script to create the schemas for the applications that you plan to install. Chapter 1. Database Configurations 17

26 v v Windows: create-suite-schemas.bat <database name> Linux: create-suite-schemas.sh <database name> Note: For the <database name> parameter, use the name of the database that you created by using the create-suite-db script in the previous step. The schema is created for each application. Information that is required in the create-suite-db Database Script The create-suite-db script prompts you to provide information when you run the script. The following table lists the questions that you must answer when you run the create-suite-db script. Table 10. create-suite-db script. create-suite-db script Information that is required from the user Do you wish to configure and restart the DB2 instance? (Y/N) Description Select N if your instance has been previously configured and you are only adding new databases. Select Y If this is the first time you're using this instance. Upgrades: There are no instance level configuration changes compared to the previous release. If you're performing an 'in-place' upgrade, there's no need to reconfigure your DB2 instance. Enter the DB2 instance name Enter database name. Maximum 8 characters Enter the name of the temporary table space Are you installing C and Java UDFs for Contract Management or Sourcing? (Y/N) Enter the path for the DB2 functions that will be copied to system The name of the DB2 instance, for example, db2inst1. The name of the database that is to be created. The name of the user temporary table space that is to be created in the database. If you are planning to install Emptoris Contract Management or Emptoris Sourcing now or in the future, choose Y. Choosing Y for this option creates the IBMCOMPAT schema and loads the functions. Specify the directory on the DB2 server where user-defined functions for Emptoris Contract Management and Emptoris Sourcing will be copied. The directory should be owned by the DB2 instance owner. Important: This directory should never be deleted. The Java and C functions are searched for in this directory. Example The following example shows the values that you must provide when the script is run. 18 IBM Emptoris Suite: IBM Emptoris Suite Configuring

27 Windows: create-suite-db.bat Prerequisites: 1. Create an operating system users for each product in in the Emptoris Suite 2. Add the users to the DB2USERS group 3. Create a DB2 instance if it doesn t exist and configure the instance port number. Execute Script : Login as the DB2 instance owner and execute the script: create-suite-db.bat Please provide information about your instance and user: This script modifies instance parameters and restarts DB2. Do you wish to continue? (Y/N):?y Enter the DB2 instance name: db2inst1 Please provide the information for the database to be created: Enter database name. Maximum 8 characters: esuite1 Enter the name of the temporary table space: temp Are you installing C and Java UDFs for Contract Management or Sourcing? (Y/N): y Enter the path for the DB2 functions that will be copied to system: e:\fn1 Instance configuration starting... Database creation starting... Database configuration starting... Creating DB functions starting... Linux: [db2inst1@suite-db-pe-1 suite-scripts]$./create-suite-db.sh ################################################################################################## Prerequisites: **************** To create the DB2 database for the Emptoris applications, complete the following steps: 1. Create an operating system user. This user will be the owner of the Emptoris Suite schemas. 2. Create a DB2 instance if it doesn t exist. 3. Configure the instance port number. 4. Login to the server as the instance owner, otherwise the database may be created in incorrec Execute Script : **************** Example - Login as the DB2 instance owner../create-suite-db.sh Example - To generate a script with all the commands to be executed manually../create-suite-db.sh -m ################################################################################################## Do you wish to configure and restart the DB2 instance? (Y/N): y Please provide information about your instance and user: Enter the DB2 instance name: db2inst1 Please provide the information for the database to be created: Enter the database name. Maximum 8 characters: esuite Enter the name of the temporary table space: temp Are you installing C and Java UDFs? Answer Y if Sourcing or Contract Management will be i Enter the path for the DB2 functions that will be copied to system: /home/db2inst1/empfunc This script modifies instance parameters and restarts DB2. Do you wish to continue? (Y/N): y Instance configuration starting... 10/29/ :16: SQL1064N DB2STOP processing was successful. SQL1064N DB2STOP processing was successful. 10/29/ :16: SQL1063N DB2START processing was successful. SQL1063N DB2START processing was successful. [e] DB2INSTDEF=db2inst1 [i] DB2_DEFERRED_PREPARE_SEMANTICS=YES [i] DB2_COMPATIBILITY_VECTOR=ORA [i] DB2_USE_ALTERNATE_PAGE_CLEANING=ON Chapter 1. Database Configurations 19

28 [i] DB2COMM=TCPIP [i] DB2AUTOSTART=YES [g] DB2SYSTEM=suite-db-pe-1.vsm.emptoris.ibm.com [g] DB2INSTDEF=db2inst1 [g] DB2ADMINSERVER=dasusr1 Database creation starting... Database configuration starting... Creating DB functions... The database has been configured with the following settings: AUTO_REVAL DEFERRED_FORCE DECFLT_ROUNDING ROUND_HALF_UP USING STMT_CONC LITERALS CATALOGCACHE_SZ 1000 UPDATE DB CFG USING SOFTMAX 100 UPDATE DB CFG USING DBHEAP UPDATE DB CFG USING LOGFILSIZ UPDATE DB CFG USING LOGPRIMARY 100 UPDATE DB CFG USING LOGSECOND 20 All other configuration parameters are set to the default values. The logfile parameters can be adjusted depending on your workload. Information that is required in the create-suite-schema Database Script The create-suite-schema script prompts you to provide information when you run the script. The following table lists the questions that you must answer when you run the create-suite-schema script. Note: The Emptoris Contract Management is not supported on Windows. Table 11. create-suite-schema script. create-suite-schema script Information that is required from the user Have you configured your database to meet the prerequisites and want to continue (Y/N)? Please select an option to create the database for Please provide information about your existing database and user Enter the name of the temporary table space Enter suite user name Enter suite user password Enter the database port number Description The script does not work properly if the database and instance are not configured correctly. For a new installation, this can be accomplished with the create-suite-db script. This prompt gives the user the option to create the schemas for each product. Information about the existing database and user. Enter the name of the temporary table space in your database. If you are not sure of what to specify, check your table space names from another session by connecting to the database as the instance owner (i.e. db2inst) and running the command select * from syscat.table spaces. Enter the name of the operating system user that will be the owner of the schema. The user must exist and have a password. The password of the user entered in the previous step. This prompt is available on Linux only. The instance port number. 20 IBM Emptoris Suite: IBM Emptoris Suite Configuring

29 Table 11. create-suite-schema script (continued). create-suite-schema script Information that is required from the user Enter your local JDK/JRE installation path on system Enter the values for the new schema to be created Enter the Schema name (uppercase) Enter the name of the table space for data and indexes Description This can be found under your DB2 home folder in either of the following directories. v $DB2_HOME/sqllib/java/jdk v $DB2_HOME /sqllib/java/jdk64 Specify the values of the new schema. Enter the name of the schema to be created. Always use uppercase for the schema names. Enter the name of the table space to be created. The user will be given grants on this table space. Example The following example shows the values that you must provide when the script is run. Windows: E:\ DB2\suite-scripts>create-suite-schemas.bat esuite Have you configured your database to meet the prerequisites and want to continue (Y/N)?y Please select an option to create the database for : 1 IBM Emptoris Strategic Supply Management 2 IBM Emptoris Supplier Lifecycle Management 3 IBM Emptoris Sourcing 4 Exit Selection : 2 Please provide information about your existing database and user Enter the name of the temporary table space: temp Enter suite user name: ssm123 Enter the values for the new schema to be created: Enter the Schema name [uppercase]: SSM123 Enter the name of the table space for data and indexes: SSMTBL1 Do you want create a schema for other product [Y/N]?Y Linux: [db2inst1@d3400db suite-scripts]$./create-suite-schemas.sh esuite ################################################################################################## Prerequisites: **************** To configure the DB2 database for the Emptoris applications, complete the following steps: 1. Create an operating system user for each product (Linux users, groups, and instance names mus # Example: Login as root and issue the commands below. # adduser empusr # passwd empusr # <enter password eg. Empt0ris 2. Configure the DB2 Instance and Database according to the install guide using the script provi # Example: Login as root and issue the commands below. #./create-suite-db.sh Execute Script : Chapter 1. Database Configurations 21

30 **************** After verifying the prerequisites, execute the script to create the schema(s). Example - Login as the DB2 instance owner. Provide the database name as a parameter../create-suite-schemas.sh esuite ##################################################################################################### Have you configured database to meet prerequisites according to the installation guide and want to co Please provide information about your instance: Enter the DB2 instance name: db2inst1 Validating connection to the database... Please select an option to create the schema for : 1 IBM Emptoris Strategic Supply Management 2 IBM Emptoris Supplier Lifecycle Management 3 IBM Emptoris Sourcing 4 IBM Emptoris Contract Management 5 Exit Selection: 1 Please provide information about your existing database and user: Enter temporary table space name: temp Enter suite user name: ssmusr Enter suite user password: Pasw0rd5 Enter the values for the new schema to be created: Schema name (uppercase): ssm1 Schema name (uppercase): SSM1 table space for data and indexes: SSM1_TBSP Do you wish to continue? (Y/N): Y Creating Schema. Please wait... Do you want create a schema for other product [Press Enter or Y to continue]? N Exiting from script. [db2inst1@d3400db suite-scripts]$ Database Configuration Parameters Certain parameters are configured when you run the scripts to configure the database. You can log in to the database as an instance owner to view the parameters. Viewing the parameters To view the database code set, log in as the instance owner and run the following command. db2 get db cfg for <database name> grep Database code set To see all parameters that are configured, run the following command. db2 get db cfg for <database name> List of parameters The following table lists the parameters that are configured during the database creation. Table 12. Database parameters that are configured during the database creation Parameter Codeset Pagesize Value UTF-8 32 K The following table lists the parameters that are configure after the database creation. 22 IBM Emptoris Suite: IBM Emptoris Suite Configuring

31 Table 13. Database parameters that are configured during the database creation Parameter Value AUTO_REVAL DEFERRED_FORCE DECFLT_ROUNDING ROUND_HALF_UP STMT_CONC LITERALS CATALOGCACHE_SZ 1000 SOFTMAX 100 DBHEAP LOGFILSIZ LOGPRIMARY 100 LOGSECOND 20 Permissions for Schema Owners From release onwards, permissions for the schema owner users are more restrictive. Permissions that are available from release onwards The following table shows the permissions that are available for the schema owners from release onwards. Table 14. Permissions that are available for schema owners from release onwards. Permissions that are available for schema owners from release onwards Permission SSM/PGM SLM Sourcing Contracts IMPLICIT SCHEMA BINDADD CONNECT X X X X CREATE EXTERNAL ROUTINE CREATE NOT FENCED ROUTINE CREATETAB X X X X DATAACCESS EXPLAIN LOAD QUIESCE_CONNECT SECADM SQLADM USE OF TABLESPACE X X X X X Legend: v SSM/PGM: Emptoris Strategic Supply Management Platform/Emptoris Program Management v SLM: Emptoris Supplier Lifecycle Management v Sourcing: Emptoris Sourcing v Contracts: Emptoris Contract Management Chapter 1. Database Configurations 23

32 Permissions that are available in per releases The following table shows the permissions that are available for the schema owners in pre releases. Table 15. Permissions that are available for schema owners in per releases. Permissions that are available for schema owners in per releases Permission SSM/PGM SLM Sourcing Contracts IMPLICIT SCHEMA X X X X BINDADD CONNECT X X X X CREATE EXTERNAL ROUTINE CREATE NOT FENCED ROUTINE X X X X X CREATETAB X X X X DATAACCESS EXPLAIN LOAD QUIESCE_CONNECT SECADM SQLADM USE OF TABLESPACE X X X X X X X X X X X Legend: v SSM/PGM: Emptoris Strategic Supply Management Platform/Emptoris Program Management v SLM: Emptoris Supplier Lifecycle Management v Sourcing: Emptoris Sourcing v Contracts: Emptoris Contract Management Java and C functions Java and C functions for Emptoris Sourcing and Emptoris Contract Management included a set of Java and C functions for contracts bit-wise operations and time zone conversions to supplement the DB2 core functions. In the previous releases, the functions were not deployed automatically when a database or schema was copied to another server. The functions had to be loaded manually. With release onwards, a new schema IBMCOMPAT is created that contains the functions. Users can now use the functions whenever required. The database administrators now create the functions once on each database instead of on multiple schema. 24 IBM Emptoris Suite: IBM Emptoris Suite Configuring

33 Manually Configuring the Database Servers for Emptoris Products To manually configure the DB2 database server, you must configure the database instance, and create and configure a database. Manually Configuring the DB2 Instance To manually configure the DB2 instance, you must set the environment variable if there are multiple instances, and set certain parameters. Before you begin Complete the Prerequisites for the DB2 Database Server on page 15. Procedure To configure the DB2 instance manually, complete the following steps: 1. Connect to the DB2 server as the instance owner. 2. If there are multiple instances, set the DB2INSTDEF environment variable to the name of the instance that you want to configure. 3. On Windows, run the script from the DB2 command window: Start > All Programs > IBM DB2 > DB2Copy1 > DB2 Command Window Administrator. 4. Run the following script. export DB2INSTDEF=<instance name> db2set DB2_COMPATIBILITY_VECTOR=ORA db2set DB2_DEFERRED_PREPARE_SEMANTICS=YES db2set DB2COMM=tcpip db2set DB2_USE_ALTERNATE_PAGE_CLEANING=ON db2stop force db2start db2set -all 5. Restart the DB2 server. What to do next Manually Creating and Configuring the Database Manually Creating and Configuring the Database You can create and configure the database by providing the database name, temporary table space name, and buffer pool names. About this task The database name, table space name, and port number must be noted when the database is created. This information is required while creating the schemas. Procedure To manually create and configure the database, complete the following steps: 1. Log in as the database instance owner. 2. Run the following script. db2 -v CREATE DATABASE <database name> using codeset UTF-8 territory US PAGESIZE 32 K db2 -v CONNECT TO <database name> db2 -v CREATE BUFFERPOOL EMP_BU1 SIZE AUTOMATIC PAGESIZE 32K db2 -v "CREATE USER TEMPORARY TABLESPACE temp PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE EXTENT db2 -v CREATE BUFFERPOOL EMP_BU16k SIZE AUTOMATIC PAGESIZE 16K Chapter 1. Database Configurations 25

34 db2 -v CREATE BUFFERPOOL EMP_BU8k SIZE AUTOMATIC PAGESIZE 8K db2 -v UPDATE DB CFG USING AUTO_REVAL DEFERRED_FORCE db2 -v UPDATE DB CFG USING DECFLT_ROUNDING ROUND_HALF_UP db2 -v UPDATE DB CFG USING STMT_CONC LITERALS db2 -v UPDATE DB CFG USING CATALOGCACHE_SZ 1000 db2 -v UPDATE DB CFG USING SOFTMAX 100 db2 -v UPDATE DB CFG USING DBHEAP db2 -v UPDATE DB CFG USING LOGFILSIZ db2 -v UPDATE DB CFG USING LOGPRIMARY 100 db2 -v UPDATE DB CFG USING LOGSECOND 20 db2 -v CONNECT RESET db2 -v DEACTIVATE DB <database name> Emptoris Spend Analysis Database Server You can find information about the database installation and configurations that are required for Emptoris Spend Analysis. Information worksheet Capture the following information at the time of installing and configuring your Emptoris Spend Analysis database. v Database server name or IP address v Database server port number v Control database name v Usage database name v Reporting Node1 database name v Reporting Node2 database name v Reporting Node3 database name v Database Copy Node database name v Database user name v Database user password You require this information at the time of installing the application servers by using the Emptoris Strategic Supply Management Installer. Downloading MySQL You must download the MySQL installation files from the MySQL website. Use the following links to download the files from the downloads.mysql.com/archives/community/ website. v Windows: Compressed file: winx64.zip MSI Installer: winx64.msi Tip: Use the.zip file to install MySQL. If you plan to use the.msi or.exe files, ensure that the customization is appropriately done. v Linux: x86_64.tar.gz 26 IBM Emptoris Suite: IBM Emptoris Suite Configuring

35 Migrating from MySQL to MySQL on Windows The recommended way to upgrade or migrate to MySQL is to install the new version, import all control databases, and copy the cube data directory. Before migrating to the new version, you must take a backup of the databases. Exporting or backing up the databases From the bin directory of MySQL , run the following query to take a backup of the expensemap database. mysqldump.exe --routines -uexpmap -pexpensemap1 expensemap >c:\expensemap.sql The exported file is saved at the location that you specify. Export the following databases by using a similar query. v plinthosdb1 v plinthosdb2 v plinthosdbcopynode v sausage What to do next Installing the MySQL Database on Windows on page 28 Migrating from MySQL to MySQL on Linux The recommended way to upgrade or migrate to MySQL is to install the new version, import all control databases, and copy the cube data directory. Before migrating to the new version, you must take a backup of the databases. Exporting or backing up the databases From the bin directory of MySQL , run the following query to take a backup of the expensemap database../mysqldump --routines -uexpmap -pexpensemap1 expensemap >/cust/expensemap.sql The exported file is saved at the location that you specify. Export the following databases by using a similar query. v plinthosdb1 v plinthosdb2 v plinthosdbcopynode v sausage What to do next Installing the MySQL Database on Red Hat Enterprise Linux on page 36 Creating and Configuring the MySQL Database You can create and configure the MySQL database on Windows and Red Hat Enterprise Linux systems by creating the my.ini file on Windows and my.cnf file on Linux, importing the databases, and completing post-installation configurations. Chapter 1. Database Configurations 27

36 Installing the MySQL Database on Windows: For Emptoris Spend Analysis, MySQL can be installed on Windows Server 2008 or Windows Server Before you begin Download the installation files. For more information, see Downloading MySQL on page 26. Procedure To install MySQL on Windows, complete the following steps: 1. Create a tools directory by using the mkdir command. C:\mkdir C:\opt\emptoris\tools 2. Extract the mysql winx64.zip file to the tools directory. 3. Rename the extracted mysql directory to MySQL From the bin directory, open the my.ini file. 5. Modify the my.ini file. For more information, see Creating the my.ini File on Windows. 6. To create a Windows service for MySQL, use the following command. D:\opt\emptoris\tools\mysql winx64\bin>mysqld.exe --install MySQL --defaults-file="d:\opt\emptoris\tools\mysql winx64\my.ini" 7. When installing for the first time, from the bin directory of MySQL, start the mysqld service by using the following command. cd C:\opt\emptoris\tools\MySQL \bin 8. Close the command prompt. 9. Start the MySQL server by using the mysqld.exe command. The MySQL server is started. What to do next Creating the expmap User on Windows on page 34 Creating the my.ini File on Windows: You must create and configure the my.ini file for configuring MySQL database on Windows systems. Procedure To create and configure the my.ini file for Windows systems, complete the following steps: 1. Open the my.ini file in a text editor. 2. Add the following settings to the my.ini file in the text editor. Note: Ensure that the path for the MySQL database is correctly specified for socket. v my.ini File for Small Size Cube on page 29 v my.ini File for Mid Size Cube on page 31 v my.ini File for Large Size Cube on page IBM Emptoris Suite: IBM Emptoris Suite Configuring

37 If you are installing MySQL in a non-standard location, ensure that the following parameters are updated in the my.ini file. v v v v v For [client] section socket = C:/opt/emptoris/tools/MySQL /tmp/ mysql.sock For [mysqld] section socket = C:/opt/emptoris/tools/MySQL /tmp/ mysql.sock For data directory section update with the following datadir=c:/opt/ emptoris/tools/mysql /data InnoDB engine updates innodb_data_home_dir = C:/opt/emptoris/tools/MySQL /data/ innodb_log_group_home_dir = C:/opt/emptoris/tools/MySQL /data/ MyISAM engine updates datadir=c:/opt/emptoris/tools/mysql /data 3. Save the file. my.ini File for Small Size Cube: The my.ini file varies according to the size of the cube that you publish. Use the following parameters for the my.ini file for small size cubes. # # This is for a system with large memory (4GB - 8GB) # Use this file to configure MYSQL on the Application server. ## SMALL SIZE CUBE my.ini ## # The default location for my.ini is /etc/my.ini to set global options. # Put the my.ini file in the installation root directory for installation specific settings. # Or in the installation folder~/.my.ini to set user-specific options. # The following options will be passed to all MySQL clients [client] #password = your_password port = 3306 socket = C:/opt/emptoris/tools/MySQL /tmp/mysql.sock character-set-server=utf8 collation-server=utf8_general_ci lower_case_table_names=1 # Here follows entries for some specific programs # The MySQL server [mysqld] bind-address = :: port = 3306 socket = C:/opt/emptoris/tools/MySQL /tmp/mysql.sock #skip-locking key_buffer = 2048M key_buffer_size=2048m key_cache_block_size=1024 max_allowed_packet = 16M table_cache = 512 table_open_cache=512 sort_buffer_size = 1024M net_buffer_length = 16M read_buffer_size = 16M read_rnd_buffer_size = 64M query_cache_size = 2048M query_cache_limit=2m max_heap_table_size=1280m tmp_table_size=1280m Chapter 1. Database Configurations 29

38 myisam_sort_buffer_size = 256M myisam_max_sort_file_size=256m thread_cache_size=8 thread_concurrency=8 max_connections=350 default-storage-engine=myisam character-set-server=utf8 collation-server=utf8_general_ci lower_case_table_names=1 sql-mode = "STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,NO_AUTO_VALUE_ON_ZERO" default-storage-engine=myisam # Replication Master Server (default) # binary logging is required for replication log-bin=mysql-bin # required unique id between 1 and 2^32-1 # defaults to 1 if master-host is not set # but will not function as a master if omitted server-id = 1 # Point the following paths to different dedicated disks tmpdir = /cust/tmp/ # Uncomment the following if you are using InnoDB tables innodb_data_home_dir = C:/opt/emptoris/tools/MySQL /data/ innodb_data_file_path = ibdata1:512m:autoextend innodb_log_group_home_dir = C:/opt/emptoris/tools/MySQL /data/ #innodb_log_arch_dir = /cust/apps/mysql/data/ # You can set.._buffer_pool_size up to % # of RAM but beware of setting memory usage too high innodb_buffer_pool_size = 32M innodb_additional_mem_pool_size = 16M # Set.._log_file_size to 25 % of buffer pool size innodb_log_file_size = 5M innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 # binlog_format added for mysql version bugzilla pr no binlog_format=mixed [mysqldump] quick max_allowed_packet = 32M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] key_buffer = 1024M sort_buffer_size = 256M read_buffer = 8M write_buffer = 16M [myisamchk] key_buffer = 1024M sort_buffer_size = 256M read_buffer = 8M write_buffer = 8M [mysqlhotcopy] interactive-timeout 30 IBM Emptoris Suite: IBM Emptoris Suite Configuring

39 my.ini File for Mid Size Cube: The my.ini file varies according to the size of the cube that you publish. Use the following parameters for the my.ini file for mid size cubes. # # This is for a system with large memory (4GB - 8GB) # Use this file to configure MYSQL on the Application server. ## Mid SIZE CUBE my.ini ## # The default location for my.ini is /etc/my.ini to set global options. # Put the my.ini file in the installation root directory for installation specific settings. # Or in the installation folder~/.my.ini to set user-specific options. # The following options will be passed to all MySQL clients [client] #password = your_password port = 3306 socket = C:/opt/emptoris/tools/MySQL /tmp/mysql.sock character-set-server=utf8 collation-server=utf8_general_ci lower_case_table_names=1 # Here follows entries for some specific programs # The MySQL server [mysqld] bind-address = :: port = 3306 socket = C:/opt/emptoris/tools/MySQL /tmp/mysql.sock #skip-locking key_buffer=2048m key_buffer_size=2048m key_cache_block_size=1024 max_allowed_packet =192M table_cache = 512 table_open_cache=512 sort_buffer_size =3072M net_buffer_length = 16M read_buffer_size=384m read_rnd_buffer_size=384m query_cache_size=3072m query_cache_limit=3m max_heap_table_size=1408m tmp_table_size=1408m myisam_sort_buffer_size=384m myisam_max_sort_file_size=384m #myisam_max_extra_sort_file_size=768m thread_cache_size=8 thread_concurrency=8 max_connections=350 character-set-server=utf8 collation-server=utf8_general_ci lower_case_table_names=1 sql-mode = "STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,NO_AUTO_VALUE_ON_ZERO" default-storage-engine=myisam # Replication Master Server (default) # binary logging is required for replication log-bin=mysql-bin # required unique id between 1 and 2^32-1 # defaults to 1 if master-host is not set Chapter 1. Database Configurations 31

40 # but will not function as a master if omitted server-id = 1 # Point the following paths to different dedicated disks tmpdir =/cust/tmp/ # Uncomment the following if you are using InnoDB tables innodb_data_home_dir = C:/opt/emptoris/tools/MySQL /data/ innodb_data_file_path = ibdata1:512m:autoextend innodb_log_group_home_dir = C:/opt/emptoris/tools/MySQL /data/ #innodb_log_arch_dir = /cust/apps/mysql/data/ # You can set.._buffer_pool_size up to % # of RAM but beware of setting memory usage too high innodb_buffer_pool_size = 32M innodb_additional_mem_pool_size = 16M # Set.._log_file_size to 25 % of buffer pool size innodb_log_file_size = 5M innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 # binlog_format added for mysql version bugzilla pr no binlog_format=mixed [mysqldump] quick max_allowed_packet = 32M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] key_buffer = 1024M sort_buffer_size = 256M read_buffer = 8M write_buffer = 16M [myisamchk] key_buffer = 1024M sort_buffer_size = 256M read_buffer = 8M write_buffer = 8M [mysqlhotcopy] interactive-timeout my.ini File for Large Size Cube: The my.ini file varies according to the size of the cube that you publish. Use the following parameters for the my.ini file for large size cubes. # # This is for a system with large memory (4GB - 8GB) # Use this file to configure MYSQL on the Application server. ## LARGE SIZE CUBE my.ini #### # The default location for my.ini is /etc/my.ini to set global options. # Put the my.ini file in the installation root directory for installation specific settings. # Or in the installation folder~/.my.ini to set user-specific options. # The following options will be passed to all MySQL clients [client] #password = your_password port = 3306 socket = C:/opt/emptoris/tools/MySQL /tmp/mysql.sock 32 IBM Emptoris Suite: IBM Emptoris Suite Configuring

41 character-set-server=utf8 collation-server=utf8_general_ci lower_case_table_names=1 # Here follows entries for some specific programs # The MySQL server [mysqld] bind-address = :: port = 3306 socket = C:/opt/emptoris/tools/MySQL /tmp/mysql.sock #skip-locking key_buffer=2048m key_buffer_size=2048m key_cache_block_size=1024 max_allowed_packet =256M table_cache = 512 table_open_cache=512 sort_buffer_size =4096M net_buffer_length = 16M read_buffer_size=512m read_rnd_buffer_size=512m query_cache_size=4096m query_cache_limit=4m max_heap_table_size=1536m tmp_table_size=1536m myisam_sort_buffer_size=512m myisam_max_sort_file_size=512m #myisam_max_extra_sort_file_size=768m thread_cache_size=8 thread_concurrency=8 max_connections=350 character-set-server=utf8 collation-server=utf8_general_ci lower_case_table_names=1 sql-mode = "STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,NO_AUTO_VALUE_ON_ZERO" default-storage-engine=myisam # Replication Master Server (default) # binary logging is required for replication log-bin=mysql-bin # required unique id between 1 and 2^32-1 # defaults to 1 if master-host is not set # but will not function as a master if omitted server-id = 1 # Point the following paths to different dedicated disks tmpdir =/cust/tmp/ # Uncomment the following if you are using InnoDB tables innodb_data_home_dir = C:/opt/emptoris/tools/MySQL /data/ innodb_data_file_path = ibdata1:512m:autoextend innodb_log_group_home_dir = C:/opt/emptoris/tools/MySQL /data/ #innodb_log_arch_dir = /cust/apps/mysql/data/ # You can set.._buffer_pool_size up to % # of RAM but beware of setting memory usage too high innodb_buffer_pool_size = 32M innodb_additional_mem_pool_size = 16M # Set.._log_file_size to 25 % of buffer pool size innodb_log_file_size = 5M innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 # binlog_format added for mysql version bugzilla pr no binlog_format=mixed Chapter 1. Database Configurations 33

42 [mysqldump] quick max_allowed_packet = 32M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] key_buffer = 1024M sort_buffer_size = 256M read_buffer = 8M write_buffer = 16M [myisamchk] key_buffer = 1024M sort_buffer_size = 256M read_buffer = 8M write_buffer = 8M [mysqlhotcopy] interactive-timeout #default-storage-engine=myisam Creating the expmap User on Windows: After the MySQL server is successfully installed and started, you must create the expmap user and grant appropriate permissions to the user. Before you begin The MySQL server is installed and running. Procedure To create the expmap user on Windows, complete the following steps: 1. Log in to MySQL as root user. 2. Start the MySQL service from the bin directory by using the following command. C:\opt\emptoris\tools\MySQL \bin> mysql uroot 3. Run the following queries. mysql>create user localhost identified by expensemap1 ; mysql>create user % identified by expensemap1 ; mysql>grant ALL PRIVILEGES ON *.* to localhost identified by expensemap1 ; mysql>grant ALL PRIVILEGES ON *.* to % identified by expensemap1 ; mysql>grant ALL PRIVILEGES ON *.* to ::1 identified by expensemap1 ; mysql>grant ALL PRIVILEGES ON *.* to <IPv6 address of Database host> identified by ex mysql>exit What to do next Run the SHOW ENGINES command to ensure that the InnoDB support is set to true. Otherwise the installation of the Emptoris Spend Analysis application fails. Verifying the Default Engine Type: The default engine type should be MyISAM and InnoDB engine support must be set to True or Yes. 34 IBM Emptoris Suite: IBM Emptoris Suite Configuring

43 After logging into the MySQL server, you can run commands to verify the default engine type. Run the following commands. C:\opt\emptoris\tools\MySQL \bin>mysqld which will start the mysql server C:\opt\emptoris\tools\MySQL \bin>mysql uroot mysql>show enignes; The following image shows an example of the default engine type. Figure 5. Emptoris Spend Analysis default engine type on Windows Verifying Successful User Creation on Windows for MySQL: If you can log in to the MySQL server by using the expmap user credentials, the user creation is successful. You can use the following command to access the server. C:\opt\emptoris\tools\MySQL \bin> mysql uexpmap pexpensemap1 Importing Databases on Windows: If you are migrating from MySQL to MySQL , after you have installed MySQL , you must import the databases that you exported earlier. Before you begin You must have completed the following tasks: 1. Migrating from MySQL to MySQL on Windows on page Installing the MySQL Database on Windows on page Starting the MySQL server. Procedure To import the control database on Windows, complete the following steps: Chapter 1. Database Configurations 35

44 1. From the bin directory of the MySQL server, log in to the server by using the expmap user. C:\opt\tools\mysql \bin> mysql -uexpmap -pexpensemap1 2. Create and use the expensemap database by using the following commands. mysql> create database expensemap; mysql>use expensemap; 3. Source the exported control database that was exported from MySQL by using the following command. mysql>source c:\expensemap5515.sql 4. Repeat the steps for plinthosdb1, plinthosdb2, plinthosdbcopynode, and sausage databases. Installing the MySQL Database on Red Hat Enterprise Linux: For Emptoris Spend Analysis, MySQL can be installed on Linux 6.6, 6.7, 7.1, and 7.2. Before you begin v Download the installation files. For more information, see Downloading MySQL on page 26. v The emptoris group and mysql users must be created on the primary and database servers. Procedure To configure the MySQL database on a Red Hat Enterprise Linux machine, complete the following steps: 1. Copy the downloaded file to the /cust/home/ directory on the database server. 2. Rename the downloaded mysql linux2.6-x86_64.tar.gz file to mysql tar.gz. 3. To ensure that you have the appropriate permissions on the server, complete the following the steps: a. Log on to the server by using the WinSCP tool. b. Select the copied file and select the Properties option. c. On the Permissions tab, enter 775 as the Octal value. Alternatively, you can also select the check boxes for the Read, Write, and Execute permissions. 4. Create the my.cnf file. For more information, see Creating and Configuring the my.cnf File for Red Hat Enterprise Linux Machines on page Perform the following steps to install MySQL (64-bit) on the database server. Table 16. Installing MySQL on the database. Installing MySQL on the database # Step Commands 1. Create apps directory under /cust. $mkdir p /cust/apps 2. Extract the mysql.tar.gz file. $tar -zxvf /cust/home/mysql tar.gz -C /cust/apps/ 36 IBM Emptoris Suite: IBM Emptoris Suite Configuring

45 Table 16. Installing MySQL on the database (continued). Installing MySQL on the database # Step Commands 3. Rename the mysql directory and run the commands. 4. From the bin directory, start the mysql service. $mv /cust/apps/mysql linux2.6-x86_64 /cust/apps $ln -s mysql /cust/apps/mysql $cd /cust/apps/ $chown -R mysql.emptoris. $cd /cust/apps/mysql / $scripts/mysql_install_db --user=mysql $chmod -R 775 /cust/apps/ $chmod -R 770 /cust/apps/mysql/data/ $cp /cust/home/my.cnf /cust/apps/mysql / $cd /cust/apps/mysql / $chown -R mysql.emptoris my.cnf $cd /cust/apps/mysql/ $bin/mysqld_safe --datadir=/cust/apps/mysql/data --por 6. From the bin directory of MySQL, check the service by using the following command. $ps ef grep mysql 7. Log in to the database to create the user by using the following command. $cd /cust/apps/mysql /bin $./mysql uroot 8. Create the expmap user with the expensemap1 password by using the following commands. mysql>create user localhost identified by expensemap1 ; mysql>create user % identified by expensemap1 ; mysql>grant ALL PRIVILEGES ON *.* to localhost identified by expensemap1 ; mysql>grant ALL PRIVILEGES ON *.* to % identified by expensemap1 ; mysql>exit 9. Stop the mysql services by using the following commands. $ cd /cust/apps/mysql/bin $./mysqladmin shutdown P 3306 Creating Users and Groups: You must create users and groups only on Red Hat Enterprise Linux databases. Before you begin Before you create users and groups on the database server, you must ensure that the non-root user and non-root admin group (for example, user emptoris and primary group emptoris) exist on the system on which the application server and reporting server is installed. To check the emptoris user and group, complete the following steps: 1. Log in as root user on the system on which primary server and reporting server are installed. 2. Use the following command to check the emptoris user. cat /etc/passwd grep emptoris Note the user ID to use it to create a user on the database server. 3. Use the following command to check the emptoris primary group. cat /etc/group grep emptoris Note the group ID to use it to create the primary group on the database server. Chapter 1. Database Configurations 37

46 Note: The group ID of the emptoris group and user ID of the emptoris user on the database server must sync with the group ID and user ID of the VM node on which the primary and reporting servers are installed. OLF jobs fail if these group and user IDs are not synced with each other. Procedure To configure users and groups on the database server, complete the following steps: 1. Log in as the root user on the database server. 2. Create a group called emptoris with group ID <GROUP_ID> using the following command. $ groupadd -g < GROUP_ID> -o emptoris 3. Create a user called emptoris with the UID <USER_ID> and make the emptoris group as the primary group by using the following command. $ useradd -c Emptoris user -m -g emptoris -n -s /bin/sh -u <USER_ID> emptoris p <PASSWORD> 4. Create a user called mysql and make the emptoris group as the primary group by using the following command. $ useradd -c MySQL user -m -g emptoris -n -s /bin/sh mysql Creating and Configuring the my.cnf File for Red Hat Enterprise Linux Machines: You must create and configure the my.cnf file for configuring MySQL database on the Red Hat Enterprise Linux systems. Procedure To create and configure the my.cnf file for Red Hat Enterprise Linux systems, complete the following steps: 1. Create the my.cnf file in a text editor, and save it to the following location: /cust/apps/mysql/. 2. Add the following settings to the my.cnf file in the text editor. v my.cnf File for Small Size Cube v my.cnf File for Mid Size Cube on page 40 v my.cnf File for Large Size Cube on page 42 Note: Ensure that the path for the MySQL database is correctly specified for socket. my.cnf File for Small Size Cube: The my.cnf file varies according to the size of the cube that you publish. Use the following parameters for the my.cnf file for small size cubes. # # This is for a system with large memory (4GB - 8GB) # Use this file to configure MYSQL on the Application server. ## SMALL SIZE CUBE my.cnf ## # The default location for my.cnf is /etc/my.cnf to set global options. # Put the my.cnf file in the installation root directory for installation specific settings. # Or in the installation folder~/.my.cnf to set user-specific options. # The following options will be passed to all MySQL clients 38 IBM Emptoris Suite: IBM Emptoris Suite Configuring

47 [client] #password = your_password port = 3306 socket = /tmp/mysql.sock character-set-server=utf8 collation-server=utf8_general_ci lower_case_table_names=1 # Here follows entries for some specific programs # The MySQL server [mysqld] bind-address = :: port = 3306 socket = /tmp/mysql.sock #skip-locking key_buffer = 2048M key_buffer_size=2048m key_cache_block_size=1024 max_allowed_packet = 16M table_cache = 512 table_open_cache=512 sort_buffer_size = 1024M net_buffer_length = 16M read_buffer_size = 16M read_rnd_buffer_size = 64M query_cache_size = 2048M query_cache_limit=2m max_heap_table_size=1280m tmp_table_size=1280m myisam_sort_buffer_size = 256M myisam_max_sort_file_size=256m thread_cache_size=8 thread_concurrency=8 max_connections=350 default-storage-engine=myisam character-set-server=utf8 collation-server=utf8_general_ci lower_case_table_names=1 sql-mode = "STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,NO_AUTO_VALUE_ON_ZERO" default-storage-engine=myisam # Replication Master Server (default) # binary logging is required for replication log-bin=mysql-bin # required unique id between 1 and 2^32-1 # defaults to 1 if master-host is not set # but will not function as a master if omitted server-id = 1 # Point the following paths to different dedicated disks tmpdir = /cust/tmp/ # Uncomment the following if you are using InnoDB tables innodb_data_home_dir = /cust/apps/mysql/data/ innodb_data_file_path = ibdata1:512m:autoextend innodb_log_group_home_dir = /cust/apps/mysql/data/ #innodb_log_arch_dir = /cust/apps/mysql/data/ # You can set.._buffer_pool_size up to % # of RAM but beware of setting memory usage too high innodb_buffer_pool_size = 32M innodb_additional_mem_pool_size = 16M # Set.._log_file_size to 25 % of buffer pool size innodb_log_file_size = 5M Chapter 1. Database Configurations 39

48 innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 # binlog_format added for mysql version bugzilla pr no binlog_format=mixed [mysqldump] quick max_allowed_packet = 32M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] key_buffer = 1024M sort_buffer_size = 256M read_buffer = 8M write_buffer = 16M [myisamchk] key_buffer = 1024M sort_buffer_size = 256M read_buffer = 8M write_buffer = 8M [mysqlhotcopy] interactive-timeout my.cnf File for Mid Size Cube: The my.cnf file varies according to the size of the cube that you publish. Use the following parameters for the my.cnf file for mid size cubes. # # This is for a system with large memory (4GB - 8GB) # Use this file to configure MYSQL on the Application server. ## Mid SIZE CUBE my.cnf ## # The default location for my.cnf is /etc/my.cnf to set global options. # Put the my.cnf file in the installation root directory for installation specific settings. # Or in the installation folder~/.my.cnf to set user-specific options. # The following options will be passed to all MySQL clients [client] #password = your_password port = 3306 socket = /tmp/mysql.sock character-set-server=utf8 collation-server=utf8_general_ci lower_case_table_names=1 # Here follows entries for some specific programs # The MySQL server [mysqld] bind-address = :: port = 3306 socket = /tmp/mysql.sock #skip-locking key_buffer=2048m key_buffer_size=2048m key_cache_block_size= IBM Emptoris Suite: IBM Emptoris Suite Configuring

49 max_allowed_packet =192M table_cache = 512 table_open_cache=512 sort_buffer_size =3072M net_buffer_length = 16M read_buffer_size=384m read_rnd_buffer_size=384m query_cache_size=3072m query_cache_limit=3m max_heap_table_size=1408m tmp_table_size=1408m myisam_sort_buffer_size=384m myisam_max_sort_file_size=384m #myisam_max_extra_sort_file_size=768m thread_cache_size=8 thread_concurrency=8 max_connections=350 character-set-server=utf8 collation-server=utf8_general_ci lower_case_table_names=1 sql-mode = "STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,NO_AUTO_VALUE_ON_ZERO" default-storage-engine=myisam # Replication Master Server (default) # binary logging is required for replication log-bin=mysql-bin # required unique id between 1 and 2^32-1 # defaults to 1 if master-host is not set # but will not function as a master if omitted server-id = 1 # Point the following paths to different dedicated disks tmpdir =/cust/tmp/ # Uncomment the following if you are using InnoDB tables innodb_data_home_dir = /cust/apps/mysql/data/ innodb_data_file_path = ibdata1:512m:autoextend innodb_log_group_home_dir = /cust/apps/mysql/data/ #innodb_log_arch_dir = /cust/apps/mysql/data/ # You can set.._buffer_pool_size up to % # of RAM but beware of setting memory usage too high innodb_buffer_pool_size = 32M innodb_additional_mem_pool_size = 16M # Set.._log_file_size to 25 % of buffer pool size innodb_log_file_size = 5M innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 # binlog_format added for mysql version bugzilla pr no binlog_format=mixed [mysqldump] quick max_allowed_packet = 32M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] key_buffer = 1024M sort_buffer_size = 256M read_buffer = 8M write_buffer = 16M Chapter 1. Database Configurations 41

50 [myisamchk] key_buffer = 1024M sort_buffer_size = 256M read_buffer = 8M write_buffer = 8M [mysqlhotcopy] interactive-timeout my.cnf File for Large Size Cube: The my.cnf file varies according to the size of the cube that you publish. Use the following parameters for the my.cnf file for large size cubes. # # This is for a system with large memory (4GB - 8GB) # Use this file to configure MYSQL on the Application server. ## LARGE SIZE CUBE my.cnf #### # The default location for my.cnf is /etc/my.cnf to set global options. # Put the my.cnf file in the installation root directory for installation specific settings. # Or in the installation folder~/.my.cnf to set user-specific options. # The following options will be passed to all MySQL clients [client] #password = your_password port = 3306 socket = /tmp/mysql.sock character-set-server=utf8 collation-server=utf8_general_ci lower_case_table_names=1 # Here follows entries for some specific programs # The MySQL server [mysqld] bind-address = :: port = 3306 socket = /tmp/mysql.sock #skip-locking key_buffer=2048m key_buffer_size=2048m key_cache_block_size=1024 max_allowed_packet =256M table_cache = 512 table_open_cache=512 sort_buffer_size =4096M net_buffer_length = 16M read_buffer_size=512m read_rnd_buffer_size=512m query_cache_size=4096m query_cache_limit=4m max_heap_table_size=1536m tmp_table_size=1536m myisam_sort_buffer_size=512m myisam_max_sort_file_size=512m #myisam_max_extra_sort_file_size=768m thread_cache_size=8 thread_concurrency=8 max_connections=350 character-set-server=utf8 collation-server=utf8_general_ci lower_case_table_names=1 42 IBM Emptoris Suite: IBM Emptoris Suite Configuring

51 sql-mode = "STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION,NO_AUTO_VALUE_ON_ZERO" default-storage-engine=myisam # Replication Master Server (default) # binary logging is required for replication log-bin=mysql-bin # required unique id between 1 and 2^32-1 # defaults to 1 if master-host is not set # but will not function as a master if omitted server-id = 1 # Point the following paths to different dedicated disks tmpdir =/cust/tmp/ # Uncomment the following if you are using InnoDB tables innodb_data_home_dir = /cust/apps/mysql/data/ innodb_data_file_path = ibdata1:512m:autoextend innodb_log_group_home_dir = /cust/apps/mysql/data/ #innodb_log_arch_dir = /cust/apps/mysql/data/ # You can set.._buffer_pool_size up to % # of RAM but beware of setting memory usage too high innodb_buffer_pool_size = 32M innodb_additional_mem_pool_size = 16M # Set.._log_file_size to 25 % of buffer pool size innodb_log_file_size = 5M innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 # binlog_format added for mysql version bugzilla pr no binlog_format=mixed [mysqldump] quick max_allowed_packet = 32M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] key_buffer = 1024M sort_buffer_size = 256M read_buffer = 8M write_buffer = 16M [myisamchk] key_buffer = 1024M sort_buffer_size = 256M read_buffer = 8M write_buffer = 8M [mysqlhotcopy] interactive-timeout #default-storage-engine=myisam Importing Databases on Linux: If you are migrating from MySQL to MySQL , after you have installed MySQL , you must import the databases that you exported earlier. Before you begin You must have completed the following tasks: 1. Migrating from MySQL to MySQL on Linux on page 27 Chapter 1. Database Configurations 43

52 2. Installing the MySQL Database on Red Hat Enterprise Linux on page Starting the MySQL server. Procedure To import the control database on Linux, complete the following steps: 1. From the bin directory of the MySQL server, log in to the server by using the expmap user. #./mysql -uexpmap -pexpensemap1 2. Create and use the expensemap database by using the following commands. mysql>create database expensemap; mysql>use expensemap; 3. Source the exported control database that was exported from MySQL by using the following command. mysql> source /cust/expensemap5515.sql; 4. Repeat the steps for plinthosdb1, plinthosdb2, plinthosdbcopynode, and sausage databases. Post-installation Configurations for Red Hat Enterprise Linux Systems: If you are planning to use OLF, you must complete the post-installation configurations after installing MySQL on the Red Hat Enterprise Linux systems. Procedure To complete the post-installation configurations, complete the following steps: 1. Stop the mysql services using the following commands. $ cd /cust/apps/mysql/bin $./mysqladmin shutdown P Modify /cust/apps/mysql/bin/mysqld_safe, and below the umask 007 setting, add the following variable. UMASK_DIR=0770 export UMASK_DIR 3. Restart the MySQL server system. 4. Start the MySQL database services from the /cust/apps/mysql folder as root user by using the following command. bin/mysqld_safe --datadir=/cust/apps/mysql/data --port= Restart the NFS4 service by using the following command. service nfs restart Assigning Directory that is not /tmp for the MySQL temporary files Issues occur due to low disk space on the /tmp directory of the MySQL server and might not be monitored for disk space alerts. You can change the default /tmp directory to a directory on the MySQL server that has sufficient space and is actively monitored for disk space alert. Procedure To assign a different directory for the MySQL temporary files, complete the following steps: 1. Create a directory that is named tmp inside the MySQL directory. 44 IBM Emptoris Suite: IBM Emptoris Suite Configuring

53 /cust/apps/mysql/tmp 2. Give same permissions to the tmp directory that are given to the MySQL directory. chown -R mysql:emptoris tmp 3. Modify the tmpdir variable from my.cnf file to point to the newly created tmp directory. tmpdir = /cust/apps/mysql/tmp 4. Restart the MySQL service and ensure that there are no errors in the MySQL logs. 5. Restart the Emptoris Spend Analysis services. Configure the Database Server for Data Manager Cube Publishing and Online Feedback If you want to enable Data Manager Cube Publishing and Online Feedback (OLF), you must configure the database and change the settings when you mount the data folder. The same database is also used by the Emptoris Spend Analysis Reporting feature. You can configure the database server for Data Manager Cube for Linux and Windows systems. Configuring the Red Hat Enterprise Linux Database Server: You must make appropriate changes to the database server when you mount the data folder for configuring the Red Hat Enterprise Linux database server. About this task NFS packages are required for the Online Feedback Feature for Emptoris Spend Analysis. To submit online feedback and publish a cube, permissions to copy the cube NFS and run the portmap services must be enabled. Procedure To make changes to the database server when you mount the data folder, complete the following steps: 1. Log in as a root user. 2. Install the required NFS packages by the following command. $ yum install nfs-utils nfs4-acl-tools portmap 3. Start the nfs and portmap services by using the following commands. $ chkconfig nfs on $ chkconfig portmap on $ service portmap start $ systemctl enable nfs-server 4. Update or create /etc/default/nfs-common and add the following details. NEED_IDMAPD=yes NEED_GSSD=no # no is default 5. Change the value of Nobody-User and Nobody-Group in the /etc/idmapd.conf file to the following value. [Mapping] Nobody-User = emptoris Nobody-Group = emptoris Chapter 1. Database Configurations 45

54 CAUTION: The group ID of the emptoris group and user ID of the emptoris user on the database server must sync with the group ID and user ID of the VM node on which the primary and reporting servers are installed. Data Manager Cube Publishing and OLF jobs fail if these group and user IDs are not in sync with each other. 6. Update or create /etc/exports and add the following value. /cust/apps/ <primary_server_ip> (rw,sync,fsid=0) Example: /cust/apps/ (rw,sync,fsid=0) 7. Create or verify the /cust/apps folder. 8. Install and configure the MySQL database. For more information, see Installing the MySQL Database on Red Hat Enterprise Linux on page 36. Configuring the Windows Database Server: You must make appropriate changes to the database server when you mount the data folder for configuring the Windows database server. Before you begin You can configure the Windows database server as an administrator. Procedure To make changes to the database server when you mount the data folder, complete the following tasks: 1. Install the MySQL database at D:\Spend\mysql winx64. For more information, see Installing the MySQL Database on Windows on page Log on to the database server and run the following command. net share <sharing_name>=d:\spend\mysql winx64 /GRANT:Administrator,CHANGE Example: net share mysql=d:\spend\mysql winx64 /GRANT:Administrator,CHANGE Creating a DB2 Schema to Publish Data Sets: To integrate Emptoris Spend Analysis with Cognos, you must create a schema on the DB2 server. Prerequisites Ensure that you configure the following settings for the DB2 instance for Emptoris Spend Analysis. v Disable the compatibility mode. v Set the following environment variable: db2set DB2_USE_ALTERNATE_PAGE_CLEANING=ON. Script for creating the DB2 schema Use the following script to create a schema on the DB2 database server. db2set DB2_USE_ALTERNATE_PAGE_CLEANING=ON CREATE DATABASE <db_name> USING CODESET UTF-8 TERRITORY US PAGESIZE 32 K CONNECT TO <db_name> 46 IBM Emptoris Suite: IBM Emptoris Suite Configuring

55 UPDATE DATABASE CONFIGURATION USING LOGFILSIZ UPDATE DATABASE CONFIGURATION USING LOGPRIMARY 100 UPDATE DATABASE CONFIGURATION USING LOGSECOND 20 update db cfg for <db_name> USING STMT_CONC LITERALS Data Range for Cubes: Cube data can be classified for small, mid, and large cubes. Based on the data range for cubes, you can configure your database. The following tables provide the data range for cubes. You can also use the tables as worksheets for noting the properties for cube, measures, dimensions, and users. Table 17. Data Range for Cubes: Cube properties Fields Definition Small cube Mid cube Large cube Value Total Facts Monthly Facts Large Dimension Rows Level Max leaf node under a parent Total number of transactions Number of Transactions in Monthly Fact Number of rows in large dimension Maximum Level in a hierarchy for any Dimension Maximum number of leaf nodes in any given dimension <20 M 20 to 30 M >=30 M to <=50 M < = 10 M > 10 M to <=20 M <1 M >1 M to <=1.5 M >20 M <=30 M >1.5 M to <=2.5 M <3 3 to 5 >5 to <=8 < > = to < > to <= Table 18. Data Range for Cubes: Measures Fields Definition Small cube Mid cube Large cube Value Base Calculated Hybrid Dynamic Masking Number of Base measures available in cube Number of Measures created over base measures in Spend Analysis system Number of Measures created over base measures of Hybrid type in Spend Analysis system Measures with masking option turned On (Masking for rollup values not of a single unit) <=3 >3 and <=5 >5 to <=7 <=2 <=3 > 3 to <=5 0 <=3 >3 to <=5 0 0 >1 to <=5 Chapter 1. Database Configurations 47

56 Table 18. Data Range for Cubes: Measures (continued) Fields Definition Small cube Mid cube Large cube Value Calculated in Calculated Number of Measures created over calculated measures in Spend Analysis system 0 <=3 >3 to <=5 Table 19. Data Range for Cubes: Dimension properties Fields Total Dimensions Visible Dimensions in Viewer Max No of Attributes in Dimension Definition Total number of all dimensions in a cube Number of dimensions made visible in a Viewer Maximum numbers of attributes enabled for any dimension Small cube Mid cube Large cube Value <=18 <=21 >21 <=25 <=7 <=8 >8 to <=10 <=2 <=3 >3 to <=5 Table 20. Data Range for Cubes: Users Fields Concurrent Users Definition Total number of Concurrent Users (Total Users) Small cube Mid cube Large cube Value 8 (54) 12 (80) 15 (100) s Note: v If any two parameters change, consider the next cube size for hardware. v If any two parameters change in Large-Size cube, consider the cube to be Extra Large. Separate sizing activity must be done on actual data for deciding the hardware. You can use the Large-Size cube hardware as the starting point for the hardware. For information about hardware, see Hardware Requirements for Database and Application Servers for Emptoris Spend Analysis. Configuring the Application Server for Data Manager Cube for Red Hat Enterprise Linux Machines You can configure the application server for Data Manager Cube Publishing and Online Feedback (OLF) on Red Hat Enterprise Linux machines. Procedure To configure the application server, complete the following tasks: 1. Use the following command to check the emptoris user. cat /etc/passwd grep emptoris 2. Use the following command to check the emptoris primary group. cat /etc/group grep emptoris 3. Make the following changes to /etc/default/nfs-common: NEED_IDMAPD=yes NEED_GSSD=no # no is default 48 IBM Emptoris Suite: IBM Emptoris Suite Configuring

57 4. Make the following changes to/etc/idmapd.conf: [Mapping] Nobody-User = emptoris Nobody-Group = emptoris 5. Run the following commands to create the database and pdf directories on the primary server. mkdir p \opt\emptoris\var\data\spend\sourcedbapps chown R emptoris.emptoris \opt\emptoris\var 6. Add the following entry to the /etc/fstab file: <database server ip>:/ /opt/emptoris/var/data/spend/sourcedbapps nfs4 rw,rsize=8192,wsize= Example: :/ /opt/emptoris/var/data/spend/sourcedbapps nfs4 rw,rsize=8192,wsize= Restart the application server machine. What to do next After completing the installation of Emptoris Spend Analysis, if you want to enable OLF, you must perform the post-installation tasks to configure OLF. For more information, see the Post-Installation Tasks section of the IBM Emptoris Suite Installation Guide. Upgrading Database Servers for Emptoris Products From release onwards, Emptoris products use Oracle 12c Standard and Enterprise Editions and DB and later databases. If you are using earlier versions of Oracle or DB2, you must upgrade the databases to the supported versions. Upgrading Oracle Servers From version onwards, Emptoris applications support only Oracle 12c Standard and Enterprise editions. If you are using an earlier version of the Oracle server, you must upgrade the database. The upgrade process involves the following steps: 1. Stop the applications. 2. Take a backup of the database schemas. 3. Upgrade the database server. Complete the database upgrade process by using one of the options that are mentioned in the Oracle Database Upgrade Guide. 4. Use upgraded database schema to point to the applications. Application specific migrations are applied on database schemas when applications start. Upgrading DB2 Servers From version onwards, Emptoris applications support DB and later. If you are using an earlier version of the DB2 server, you must upgrade the database. The upgrade process involves the following steps: Chapter 1. Database Configurations 49

58 1. Upgrade the database server. 2. Take a backup of the database. 3. For Emptoris Contract Management and Emptoris Sourcing, install the UDFs in the DB2 server. 4. Install the applications. 5. Upgrade the schemas. The schemas are upgraded automatically when you install the new applications. Taking a Backup of the DB2 Databases Before you upgrade the database, you must take a backup of the database including all schemas. It is best to take the backup when all application servers are down. Procedure To take a backup of the DB2 database, complete the following steps: 1. Stop all application servers. 2. Stop InfoSphere DataStage and Cognos if you have reporting. 3. Verify that there are no connections from the application and reporting servers to the database. 4. Back up the database by using the db2 backup utility. 5. Create a copy of the database by using the db2 restore utility. What to do next v Update the statistics on all schemas. v In the newly installed database, for Emptoris Sourcing and Emptoris Contract Management, install the Java and C functions. v Test the backup to ensure that you can recover from it before you upgrade a production environment. Installing UDFs in the DB2 Server If you have Emptoris Contract Management and Emptoris Sourcing in your setup, you must have C and Java user-defined functions (UDFs) in your DB2 server. Procedure To install C and Java UDFs, complete the following steps: 1. Copy the db-scripts.zip file from the EMP_Resources_ _36.zip file to the DB2 server. 2. Make the user, who is the instance owner, the owner of the file. 3. Run the script as the instance owner by completing the following steps. 50 IBM Emptoris Suite: IBM Emptoris Suite Configuring

59 Table 21. Running the DB2 script on Linux and Windows. Running the DB2 script on Linux and Windows Linux 1. Change to the DB2\suite-scripts directory. 2. Grant execute permission to the.sh files. chmod +x *.sh chmod +x bin/*.sh Windows Run the script from a DB2 command window: Start > All Programs > IBM DB2 > DB2Copy1 > DB2 Command Window Administrator Reporting Database Servers 4. Run the create-suite-udfs script to create the database. v v Windows: create-suite-udfs.bat Linux: create-suite-udfs.sh Use the following command to run the script. create-suite-udfs.bat <databasename> <functionsdirectory> databasename: The name of the database where the functions are added. functionsdirectory: Specify the directory on the DB2 server where user-defined functions for Emptoris Contract Management and Emptoris Sourcing are copied. The directory must be owned by the DB2 instance owner. The Java and C functions are searched for in this directory. Important: Never delete this directory. Also, do not use the existing /home/db2inst1/sqllib/function directory. Create a directory, such as mkdir functionecm1001 and provide the full path. If you create multiple reporting databases, each database should have its own functions directory. Upgrading Schemas During the installation of Emptoris applications, the Emptoris Strategic Supply Management Installer prompts for the database connection information. When you specify the details, the application servers are configured to use those schemas. The schemas are upgraded automatically when you install the new applications. The Reporting feature is available for Emptoris Contract Management and Emptoris Spend Analysis. Reporting for Emptoris Contract Management Reporting for Emptoris Contract Management is available to customers for on-premise installation and also as a hosted solution by the IBM Emptoris Services team. For more information, see Reporting Database for Emptoris Contract Management. Reporting for Emptoris Spend Analysis Reporting with Emptoris Spend Analysis however, is only available as a service hosted by IBM Emptoris. Contact your Emptoris representative for more information. For more information, see Reporting Database for Emptoris Spend Analysis. Chapter 1. Database Configurations 51

60 Upgrading Reporting Database Servers The upgrade to the reporting database servers includes upgrading InfoSphere DataStage, Cognos, and the Emptoris Contract Management schema. For more information, see Upgrading Reporting on page 126. Data At Rest Encryption (DARE) You can encrypt the data at rest on Oracle, DB2, and MySQL databases. Encrypting the data is an optional step and can be completed before or after you upgrade the databases and systems, or also after you install the applications for the first time. Data At Rest Encryption (DARE) is used to protect the data in databases that is not moving through networks. The encryption is done by using Transparent Data Encryption (TDE). For MySQL, the encryption is at the file system level. No changes are made to the application logic or schema. However, for file system level encryption, the disk encryption on application servers must be completed before installing the application. This is because enabling encryption by using LUKS or BitLocker erases the data on the hard disk. Servers that are Encrypted in the Emptoris setup In the Emptoris setup, the application servers, database servers, and the reporting components are encrypted in different ways. The following image shows the servers that are encrypted. 52 IBM Emptoris Suite: IBM Emptoris Suite Configuring

61 Figure 6. Encrypted Servers The following table lists the servers that are encrypted. Table 22. Servers that are encrypted. Servers that are encrypted Servers Application servers What is encrypted File system level encryption is implemented by using LUKS for Linux and Bitlocker for Windows for the following files: v WebSphere Application Server and Emptoris directories v SOLR index directories Chapter 1. Database Configurations 53

62 Table 22. Servers that are encrypted (continued). Servers that are encrypted Servers Database servers Reporting servers What is encrypted v Oracle: Table space level encryption by using Oracle Transparent Data Encryption (TDE) v DB2: Database level encryption by using DB2 Native Encryption v MySQL: File system level encryption by using LUKS for Linux and BitLocker for Windows v InfoSphere DataStage: InfoSphere DataStage Server: File system encryption by using LUKS for Linux or BitLocker for Windows Database: Internal metadata schemas are not encrypted Database: Source and target schemas are encrypted at the database level v Cognos: Cognos Server: Temp files are encrypted through a configuration option, no file system level encryption is provided Database: Internal metadata schema is not encrypted Database: Reporting schema is encrypted at the database level Roles and Responsibilities for Setting Up Encryption Configuring encryption for the Emptoris Suite requires specialized knowledge in several areas. Security Administrator and Database Administrators must complete certain actions to set up encryption. The following table lists the roles and the corresponding responsibilities for setting up encryption. Table 23. Roles and responsibilities for setting up encryption Role Systems Security Administrator Oracle Database Administrator (if using Oracle) Responsible for v Linux or Windows administration tasks v Installing and configuring LUKS or BitLocker v Creating the encrypted disk on all applications servers, InfoSphere DataStage, and SOLR indexing servers v Testing and troubleshooting issues with the encrypted file system, such as ensuring that the user can read and write to the encrypted file system v Backing up and securing encryption keys v Oracle database administration v Creating and managing the Oracle keystore v Securing the keystore and other important files v Opening and closing the Oracle wallet v Creating encrypted table spaces v Testing and troubleshooting connectivity issues v Backing up and restoring databases 54 IBM Emptoris Suite: IBM Emptoris Suite Configuring

63 Table 23. Roles and responsibilities for setting up encryption (continued) Role DB2 Database Administrator (if using DB2) MySQL Database Administrator (if using MySQL) Responsible for v DB2 database administration v Creating and securing the keystore in DB2 v Configuring the DB2 instance with the keystore location and type v Creating an encrypted database by using provided scripts v Testing and troubleshooting connectivity issues v Backing up and restoring databases v Implementing key rotation v MySQL database administration v Creating a database in the encrypted file system v Testing and troubleshooting connectivity issues v Backing up and restoring databases Encryption on Oracle For Emptoris products, Oracle Transparent Data Encryption (TDE) at the table space level is implemented. TDE is a part of the Oracle Advanced Security Option that is available for the Oracle Enterprise Edition databases. The default AES128 encryption is used for the Oracle Enterprise Edition databases. Encryption process The encryption process on Oracle involves the following two steps: 1. Setting up encryption. 2. Encrypting the data. Each step involves more steps that must be completed to protect your data. Setting up Encryption Setting up encryption for the Oracle 12c database includes creating a directory for the keystore, setting a software keystore location, creating the keystore, opening the keystore, and setting up the TDE master encryption key. About this task Each Oracle database has one keystore file. Oracle supports software and hardware based keystores. The software keystore can be password-based, auto-login, or local auto-login. A password-based keystore must be opened before the keys can be used or retrieved. The location of the file must be defined in the sqlnet.ora file. After the location is defined, you must log in to the database to create and open the keystore, and set the TDE master encryption key. There are several variations of this task depending on your configuration. In this section, a basic example of creating a password- based keystore is provided. For additional details, see the section Configuring Transparent Data Encryption of the Oracle Database Advanced Security Guide. Chapter 1. Database Configurations 55

64 Procedure To set up encryption, complete the following steps: 1. Log in as the root user. 2. Create a directory for the keystore file and give the Oracle user ownership permissions for the directory. The following example shows the creation of the /u02/oradata/wallets/ directory. mkdir -pv /u02/oradata/wallets/ chown -R oracle:oinstall ORACLE chmod -R 700 ORACLE 3. Define the location of the keystore file in the sqlnet.ora file by providing the following details in the file. ENCRYPTION_WALLET_LOCATION= (SOURCE= (METHOD=FILE) (METHOD_DATA= (DIRECTORY=/u02/oradata/wallets/))) 4. Create the keystore file by completing the following steps. a. Log in as SYS user or user with ADMINISTER KEY MANAGEMENT or SYSKM privileges. b. Run the following command. ADMINISTER KEY MANAGEMENT CREATE KEYSTORE /u02/oradata/wallets/ IDENTIFIED BY DARE4Oracle; Verify: select STATUS from V$ENCRYPTION_WALLET; --> CLOSED 5. Open the keystore file by running the following command. ADMINISTER KEY MANAGEMENT SET KEYSTORE OPEN IDENTIFIED BY DARE4Oracle; Verify: select STATUS from V$ENCRYPTION_WALLET; --> OPEN_NO_MASTER_KEY 6. Set the TDE master encryption key by completing the following steps. a. Verify that the database is open by running the following command. select open_mode from v$database; --> READ WRITE b. Set the TDE master encryption key by running the following command. ADMINISTER KEY MANAGEMENT SET KEY IDENTIFIED BY DARE4Oracle WITH BACKUP USING emp_key_backup c. Verify the status of the wallet by running the following command. select STATUS from V$ENCRYPTION_WALLET; --> OPEN What to do next Encrypting your data Encrypting your data You can encrypt your data after you set up encryption on your systems. Encrypting the data involves setting the COMPATIBLE parameter and creating an encrypted table space. Before you begin You must have set up encryption before you encrypt the data. For information about setting up encryption, see Setting up Encryption on page 55. To create an encrypted table space, you must have the CREATE TABLESPACE system privilege. 56 IBM Emptoris Suite: IBM Emptoris Suite Configuring

65 About this task You can encrypt your data before are after you upgrade to a newer version, or after a new installation. Procedure To encrypt your data, complete the following steps: 1. View and set the COMPATIBLE Initialization parameter by running the following command. SQL> SHOW PARAMETER COMPATIBLE The COMPATIBLE parameter must be or later. The following information is displayed. NAME TYPE VALUE compatible string noncdb_compatible boolean FALSE 2. Create an encrypted table space by running the following command. CREATE TABLESPACE <table space name> ENCRYPTION DEFAULT STORAGE(ENCRYPT); The key lengths are included in the names of the algorithms. If you do not specify an encryption algorithm, the default AES128 encryption algorithm is used. ENCRYPT in the DEFAULT STORAGE clause encrypts the table space. You cannot encrypt an existing table space. However, you can import data into an encrypted table space by using Oracle Data Pump. You can also use an SQL statement such as CREATE TABLE...AS SELECT... or ALTER TABLE...MOVE... to move data to an encrypted table space. The CREATE TABLE...AS SELECT... command creates a table from an existing table. The ALTER TABLE...MOVE... command moves a table into the encrypted table space. For security reasons, you cannot encrypt a table space with the NO SALT option. 3. Verify that the table space is encrypted by using one of the following options. v Query the ENCRYPTED column of the DBA_TABLESPACES and USER_TABLESPACES data dictionary views. SQL> SELECT ENCRYPTIONALG FROM V$ENCRYPTED_TABLESPACES; ENCRYPT AES128 SQL> SELECT ENCRYPTED FROM DBA_TABLESPACES WHERE TABLESPACE_NAME = TESTDATA ; v ENC --- YES Use the following algorithm. CREATE TABLESPACE TESTDATA ENCRYPTION USING AES256 DEFAULT STORAGE(ENCRYPT); ENCRYPTION USING 'AES256' specifies the encryption algorithm and the key length for the encryption. Enclose this setting in single quotation marks (' '). You can choose from the following algorithms: 3DES168 AES128 Chapter 1. Database Configurations 57

66 AES192 AES256 Related information: asotrans_config.htm#asoag10162 Managing the keystore file As an administrator, you can complete several activities to maintain and manage the keystore file. Some of the activities that you can complete for the keystore file are as follows: v Change the password of the keystore file v Back up the keystore file v Move the keystore file to a new location v Export and import the keystore file For more information about managing the keystore file, see the Managing the Keystore and the TDE Master Encryption Key section in the Oracle Database Advanced Security Guide. Backup and Restore of keystore File and Encrypted Data By using Oracle data pump, you can export and import encrypted data in two ways. In the first method, you can set a password during export and specify the password during import. In the second method, you can use the keystore TDE master encryption key to decrypt the data. Setting a password during export and specify this password during import The following example shows the commands to set a password during export and specifying the same password during import. Sourcing database: daredb Source schema: ecm (with encrypted tablespace) In the source database, export from database where encryption is enabled: sqlplus / as sysdba sql> create directory dir_daredb as /u01/backups/daredb ; sql> grant read,write on directory dir_daredb to ecm; sql> grant read,write on directory dir_daredb to ecm_dev; sql> exit; ### Export from the command prompt expdp ecm/ecm_pwd directory=dir_daredb dumpfile=ecm_encrypted.dpmp encryption=all encryption_pwd_prom ### Import in the same database, but different schema impdp ecm_dev/ecmpwd@daredb directory=dir_daredb dumpfile=ecm_encrypted.dpmp encryption_pwd_prompt=y ###Importing in a different DB: Copy the dump file to the targer server to /u01/backups/daredb and cr sqlplus / as sysdba sql> create directory dir_daredb as /u01/backups/daredb ; sql> grant read,write on directory dir_daredb to ecm_test; 58 IBM Emptoris Suite: IBM Emptoris Suite Configuring

67 sql> exit; impdp directory=dir_daredb dumpfile=ecm_encrypted.dpmp encryption_pwd_prompt=yes t Using the keystore TDE master encryption key to decrypt the data You can export the keystore file from a source system and import it to a target system to set up encryption by using the same key. After you set up encryption on the target system, you can export the encrypted data from the source system and import it to the target system with the encrypted data. Exporting and Importing the keystore File: You can move the keystore file by exporting it from a source location and importing it to a target location. Procedure To export and import the keystore file, complete the following steps: 1. Run the following command to export the keystore file. ADMINISTER KEY MANAGEMENT EXPORT ENCRYPTION KEYS WITH SECRET "my_secret" TO /u02/oradata/walle 2. Copy the exported file to the target database. 3. Import the keys and modified keystore file by running the following command: ADMINISTER KEY MANAGEMENT IMPORT KEYS WITH SECRET "my_secret" FROM /etc/oracle/wallets/orcl/de Exporting and Importing Encrypted Data: If you imported the keystore file to a target database, you can now export the encrypted data from the source database and import it to the target database with the encryption on. Before you begin Exporting and Importing the keystore File About this task The following procedure shows the command for exporting and importing data by using data pump for encrypted data when both source and target system are set up by using same encryption key. Procedure To export and import encrypted data, complete the following steps: 1. Run the following command. expdp directory=dumps dumpfile=encrypted_ecm.dmp encryption=all ENCRYPTION_ALGORITHM=AES256 ENC 2. Copy the file to the target database. 3. Import the file by using the data pump command. Do not use the encryption option because the keystore file is already imported. Impdp directory=dumps dumpfile=encrypted_ecm.dmp logfile=import_encrypted_ecm.log REMAP_SCHEMA= If you import the data on a database that does not have the keystore file and encryption set, the following error message is displayed. Chapter 1. Database Configurations 59

68 ORA-39002: invalid operation ORA-39189: unable to decrypt dump file set ORA-28365: wallet is not open Encryption on DB2 DB2 Native Encryption is available on DB Fix Pack 5 and later to protect online data and backups. Data At Rest Encryption (DARE) for DB2 involves transparent encryption at the database level where no data or schema changes are made. DB2 Native Encryption has a built-in secure and transparent key management. With DARE, data and keystore files and passwords are encrypted. DARE on DB2 is compliant with NIST SP compliant cryptographic algorithms (modern encryption algorithms and key lengths). The encryption is done by using 10-2 certified encryption libraries. DARE is supported on all platforms that are supported by DB2. A symmetric key is used for encryption. A symmetric key is the same key that is used for encryption and decryption. Data that is encrypted The following data is encrypted on DB2 by using DARE: v System and user-defined table spaces v Data in table spaces v Transaction logs including logs in the archives v LOAD COPY data v LOAD staging files v Dump.bin files (diagnostic files) v Backup images v Encryption keys in memory, except when in use v Keystore passwords when communicated across database partitions Encryption key in DB2 The sequence that controls the operation of the cryptographic algorithm is called an encryption key. The number of bits in a key is the key length. The length reflects the difficulty to decrypt the data. A 256-bit key has values in the key space. The data in a database is encrypted by using a data encryption key. The encryption key is stored in the database. It is encrypted with a master encryption key. The master encryption key is stored and managed outside the database in a keystore file. The keystore is compliant with the Public Key Cryptography Standard #12 (PKCS#12) standard. You must take regular backups of the keystore to maintain security. Encrypting Data on DB2 To encrypt your data on DB2, you must complete certain prerequisite tasks, configure the DB2 instance, and encrypt a table space. 60 IBM Emptoris Suite: IBM Emptoris Suite Configuring

69 Procedure To encrypt data on DB2, complete the following steps: 1. Complete the prerequisites. 2. Configure the DB2 instance. 3. Create an encrypted database. Setting up Encryption on DB2: To set up encryption on DB2, you must verify the DB2 version, set the environment variables, and create a keystore file. About this task You must also choose the type of password to use for the keystore file. Procedure To set up encryption, complete the following steps: 1. Verify the DB2 version by using the db2level command. The following example shows how to run the db2level command. E:\DB2_03\BIN>db2levelDB21085I This instance or install (instance name, where applicable: "DB2_04")uses "64" bits and DB2 code release "SQL10055" with level identifier" e".informational tokens are "DB2 v ", "s141128", "IP23628", and FixPack "5".Product is installed at "E:\DB2 with DB2 Copy Name "DB2COPY3". 2. Set the value for the IBM Global Security Kit (GSKit) libraries in the environment variable PATH on Windows and LD_LIBRARY_PATH on Linux. The following table lists the operating system, location of the libraries, and the environment variable. Table 24. GSKit library location for setting the environment variables Operating system GSKit Location Environment variable Linux 32-bit Linux 64-bit Windows 32-bit Windows 64-bit $INSTHOME/sqllib/lib32/ gskit $INSTHOME/sqllib/lib64/ gskit C:\Program Files (x86)\ibm\gsk8\lib C:\Program Files\IBM\gsk8\lib64 Include $INSTHOME/sqllib/lib32/ gskit in the LIBPATH, LD_LIBRARY_PATH, or SHLIB_PATH environment variable. Include $INSTHOME/sqllib/lib64/ gskit in the LIBPATH, LD_LIBRARY_PATH, or SHLIB_PATH environment variable. Include C:\Program Files (x86)\ibm\gsk8\lib in the PATH environment variable. Include C:\Program Files\IBM\gsk8\lib64 or C:\Program Files (x86)\ibm\gsk8\lib in the PATH environment variable. 3. Choose a password type and create a keystore file by completing the following steps: a. Log in to the DB2 server as the instance owner to run the gsk8capicmd utility. Chapter 1. Database Configurations 61

70 b. Update the instance with the keystore type and location. Example: Linux - stashed password ~/sqllib/gskit/bin/gsk8capicmd_64 -keydb -create -db /home/db2inst2/esuitekeystore1.db -type pkcs12 -pw "Emptori55" stash Example: Windows - stashed password mkdir e:\db2kstr"c:\program Files\IBM\gsk8\bin\gsk8capicmd_64" -keydb -create -db e:\db2kstr\db2-inst2-kstr.db -type pkcs12 -pw "Emptori55" stash Example: Windows - interactive password "C:\Program Files\IBM\gsk8\bin\gsk8capicmd_64" -keydb -create -db e:\db2kstr\db2-inst3-kstr.db -type pkcs12 -pw "Emptori55" For information about issues that might occur when you are creating the keystore file, see Implementing DB2 native database encryption. 4. Configure the keystore instance parameters. The instance should be configured with the keystore location and type. Example: Login as the instance owner and update the instance parameters: [db2inst1@empdb2 ~]$ db2 update dbm config using KEYSTORE_LOCATION /home/db2inst1/esuitekeystore1.db KEYSTORE_TYPE PKCS12 [db2inst1@empdb2 ~]$ db2stop [db2inst1@empdb2 ~]$ db2start Configuring the DB2 Instance for Encryption: After you complete setting up the encryption on DB2, you must configure the DB2 instance. Before you begin Setting up Encryption on DB2 on page 61 About this task The DB2 instance must be updated with keystore location and type before the database is encrypted. Procedure To configure the DB2 instance, complete the following steps: 1. Log in to the instance as the instance owner. 2. Use the following commands to configure the instance. Windows db2 update dbm config using KEYSTORE_LOCATION e:\db2kstr\db2-inst2-kstr.db KEYSTORE_TYPE PKCS12 Linux db2 update dbm config using KEYSTORE_LOCATION /home/db2inst1/esuitekeystore1.db KEYSTORE_TYPE PKCS12 Restart the instance for the changes to take effect. [db2inst1@v ~]$ db2stop [db2inst1@v ~]$ db2start 3. Restart the DB2 instance. 62 IBM Emptoris Suite: IBM Emptoris Suite Configuring

71 Creating an Encrypted DB2 Database: After you set up encryption and configure the DB2 instance, you can create an encrypted database. An encrypted database is created by running a script. About this task The default encryption is AES 256. If you want to use a different algorithm, you can customize the database creation scripts. Procedure To create an encrypted database, complete the following steps: 1. Log in to the database as an administrator. 2. Create an operating system user who becomes the owner of the Emptoris schemas. 3. Set up encryption for DB2. For more information, see Setting up Encryption on DB2 on page Create a DB2 instance if it does not exist and configure the instance. For more information, see Configuring the DB2 Instance for Encryption on page Log in to the server as the instance owner. 6. Run the following script: /create-suite-db.sh -m ############################################################################## Do you wish to configure and restart the DB2 instance? (Y/N): n Please provide information about your instance and user: Enter the DB2 instance name: db2inst1 Are you creating an encrypted database? (Y/N): y Please provide the information for the database to be created: Enter the database name. Maximum 8 characters: esuite3 Please select the encryption option for your database : 1 AES 128 bits 2 AES 192 bits 3 AES 256 bits 4 3DES 168 bits 5 No encryption Selection: 2 Enter the name of the temporary tablespace: temp Are you installing C and Java UDFs? Answer Y if Sourcing or Contract Management will be Enter the path for the DB2 functions that will be copied to system: /home/db2inst1/esui Database creation starting... Creating an Encrypted Reporting Database: To create an encrypted reporting database, you must first set up encryption and configure the DB2 instance. The encrypted database is created by running a script. About this task The default encryption is AES 256. If you want to use a different algorithm, you can customize the database creation scripts. Procedure To create an encrypted database, complete the following steps: 1. Log in to the database as an administrator. Chapter 1. Database Configurations 63

72 2. Create an operating system user who becomes the owner of the Emptoris schemas. 3. Set up encryption for DB2. For more information, see Setting up Encryption on DB2 on page Create a DB2 instance if it does not exist and configure the instance. For more information, see Configuring the DB2 Instance for Encryption on page Configure the instance port number. 6. Log in to the server as the instance owner. 7. Run the following script../create-reporting-dbs.sh ################################################################################## Have you configured DB2 instance to meet the prerequisites according to the installation guide an Please provide information about your instance Enter the DB2 instance name: db2inst2 Please select an option to create the database for 1 IBM Emptoris Reporting 2 IBM Cognos Content Store 3 IBM Datastage Metadata Repository 4 Exit Selection: 1 Do you wish to configure and restart the DB2 instance? (Y/N): y Are you creating an encrypted database? (Y/N): y Please provide the information for the database to be created: Enter the database name. Maximum 8 characters: repenc1 Validating database name... Please select the encryption option for your database : 1 AES 128 bits 2 AES 192 bits 3 AES 256 bits 4 3DES 168 bits 5 No encryption Selection: 3 Enter temporary tablespace name: temp Enter the path for the DB2 functions that will be copied to system: /home/db2inst2/repenc1 This script modifies instance parameters and restarts DB2. Do you wish to continue? (Y/N): Instance configuration starting... 02/08/ :30: SQL1064N DB2STOP processing was successful. SQL1064N DB2STOP processing was successful. 02/08/ :30: SQL1063N DB2START processing was successful. SQL1063N DB2START processing was successful. Database creation scripts starting... Database configuration starting... Creating DB functions starting... Do you want create another database (Y/N)? n Exiting from script. Maintenance and Backup: To maintain the security of the keystore file that is used to encrypt the data, you can back up the file periodically. You can also choose to enforce password rotation for the keystore file. Securing the keystore file Only the DB2 instance owner must have read/write access to the keystore file. The content of the keystore file is encrypted by using a symmetric key. The key is derived from the keystore password by using a hashing algorithm. Without the password, the content of the keystore cannot be decrypted. It is important to back 64 IBM Emptoris Suite: IBM Emptoris Suite Configuring

73 up both the keystore file and the keystore password regularly. Key rotation You can rotate the database master key in DB2 as an effective way of security with the ADMIN_ROTATE_MASTER_KEY procedure. With key rotation, the database data encryption key decrypts the old master key. The database encryption key is encrypted again the new master key. When you run the ADMIN_ROTATE_MASTER_KEY command, you can choose to provide a label for the new master key or use the default. When the default label is used, a new master key is automatically generated and added to the keystore file. Encrypting an Existing Database: To encrypt your existing database, you must first back up the database, configure the database instance for encryption, and restore the database. Procedure To encrypt an existing database, complete the following steps: 1. Back up the database by running the following commands. db2 deactivate db test1 db2 backup database test1 to /u01/backups/db2/test1 2. Configure the instance and create the keystore file by running the following commands: ~/sqllib/gskit/bin/gsk8capicmd_64 -keydb -create -db /home/db2inst2/esuitekeystore1.db -type pkcs12 -pw "Emptori55" stash db2 update dbm config using KEYSTORE_LOCATION /home/db2inst1/esuitekeystore1.db KEYSTORE_TYPE P Restart the instance for the changes to take effect. [db2inst1@v ~]$ db2stop [db2inst1@v ~]$ db2start 3. To restore the database on to the same server, run the following command: db2 restore database test1 from /u01/backups/db2/test1 taken at encrypt 4. To restore the database on a different server, complete the following steps: a. On the source server, complete the following steps: 1) Back up the encrypted database. 2) Export the master key. 3) Transfer the master key and the backup files to the target server. b. On the target server, complete the following steps: 1) Configure the DB2 instance by following the steps in Configuring the DB2 Instance for Encryption on page 62. 2) Import the master key from the source server. 3) Restore the database. Backing up the server: db2 deactivate db esuite3db2 backup database esuite3to /u01/backups/db2/test1 Exporting the master key from the source: [db2inst1@emparchdb db2inst1]$ db2 connect to esuite3... [db2inst1@emparchdb db2inst1]$ db2 "select MASTER_KEY_LABEL from TABLE(SYSPROC.ADMIN_GET_ENCRYP Chapter 1. Database Configurations 65

74 MASTER_KEY_LABEL DB2_SYSGEN_db2inst1_ESUITE3_ $./sqllib/gskit/bin/gsk8capicmd_64 -cert -export -db /home/db2inst1/esuitekeystore1.db -stashed ~]$ ls -la tmp* -rw db2inst1 db2iadm1 80 Feb 15 15:54 tmp-esuite3-label.crl -rw db2inst1 db2iadm Feb 15 15:54 tmp-esuite3-label.raw -rw db2inst1 db2iadm1 80 Feb 15 15:54 tmp-esuite3-label.rdb Copy the backup and tmp* files to the target server. Creating the keystore: [db2inst3@bidb2srv02 ~]$./sqllib/gskit/bin/gsk8capicmd_64 -keydb -create -db /home/db2inst3/esui db2 update dbm config using KEYSTORE_LOCATION /home/db2inst3/esuitekeystore3.db KEYSTORE_TYPE PKC Restarting the instance: [db2inst1@v ~]$ db2stop [db2inst1@v ~]$ db2start Importing the label:./sqllib/gskit/bin/gsk8capicmd_64 -cert -import -db /home/db2ins3/backups/tmp-esuite3-label.raw - Restoring the database: db2 restore database esuite3 from /home/db2inst3/backups Encryption on MySQL Data At Rest Encryption (DARE) is provided for MySQL at the file system level. For Windows, BitLocker is used for encryption. For Linux, LUKS is used for encryption. For file system level encryption, the disk encryption on application servers must be completed before installing the application. This is because enabling encryption by using LUKS or BitLocker erases the data on the hard disk. For information about encrypting the operating system, see the following links: v Windows: Windows Server 2008 R2: BitLocker Drive Encryption Overview Windows Server 2012: How to deploy on Windows Server 2012 v Linux 7.1 and 7.2: Using LUKS Disk Encryption Troubleshooting DARE If you face issues while setting up encryption you can run some commands for DB2 for troubleshooting and share the commands with the IBM Emptoris Support team for help. For Oracle, you can complete certain actions to check database connectivity errors. Troubleshooting Oracle DARE issues While setting up encryption on Oracle, one of the major issues that might occur is database connectivity issues. You can test the connectivity though various means. 66 IBM Emptoris Suite: IBM Emptoris Suite Configuring

75 Testing connectivity from a client system You can verify whether you can connect to the Oracle database from a client system such as Cognos or InfoSphere DataStage systems by creating a session with SQL Plus or SQL Developer. Example sqlplus ecm/ecm1@ora12c If you cannot connect, you must raise a support ticket and add information about the ORA-XXXX error that is seen to the ticket. Testing connectivity from a database server You can connect to the database to verify whether the listener is working. Log in to the database server as the Oracle user and run the following command: lsnrctl status Raise a support ticket and add the output of the command to the ticket. Verifying that the database and database wallet are open On an encrypted database, connectivity errors might occur if the Oracle Wallet is not open. You can log in to the Oracle database as the Oracle user and run the following sqlplus commands to verify whether the database and database wallet are open: select open_mode from v$database; select STATUS from V$ENCRYPTION_WALLET; Raise a support ticket and add the output of the command to the ticket. Verifying that the table spaces are encrypted Before installing the applications, you can verify that the table spaces are encrypted. Connect to the database and run the following command to verify the encryption: SELECT TABLESPACE_NAME, ENCRYPTED FROM DBA_TABLESPACES; Troubleshooting DB2 DARE issues If issues occur while you set up DARE for DB2, you can verify whether the DB2 instance is configured with the keystore information and also verify that the database is encrypted. Verifying whether the instance is configured To verify whether the DB2 instance is configured with the keystore information, log in to the DB2 server as the instance owner, and run the following command: <instance owner>@emparchdb ]$ db2 get dbm config grep KEYSTORE Example db2inst1@emparchdb ]$ db2 get dbm config grep KEYSTORE Keystore type (KEYSTORE_TYPE) = PKCS12 Keystore location (KEYSTORE_LOCATION) = /home/db2inst1/esuitekeystore1.db Raise a support ticket and add the output of the command to the ticket. Chapter 1. Database Configurations 67

76 Verifying that the database is encrypted To verify whether the database is encrypted, connect to the database, run the following command: db2 "select * from table(sysproc.admin_get_encryption_info())" Raise a support ticket and add the output of the command to the ticket. 68 IBM Emptoris Suite: IBM Emptoris Suite Configuring

77 Chapter 2. Reporting Configurations Introduction to Reporting If you plan to use reporting for Emptoris Contract Management, Emptoris Spend Analysis, or Emptoris Supplier Lifecycle Management, use this section to install and configure the reporting setup. The Reporting feature is available for IBM Emptoris Contract Management, IBM Emptoris Spend Analysis, and Emptoris Supplier Lifecycle Management. This document contains information for installing and configuring reporting for Emptoris Contract Management, Emptoris Spend Analysis, and Emptoris Supplier Lifecycle Management. Do not use this document if your setup does not contain Emptoris Contract Management, Emptoris Spend Analysis, or Emptoris Supplier Lifecycle Management, or you do not intend to use reporting. Audience This document is meant for IT administrators who configure InfoSphere DataStage and Cognos Business Intelligence Platform. Configuring the reporting setup Emptoris Contract Management uses IBM Cognos Business Intelligence Platform and IBM InfoSphere DataStage for reporting. Emptoris Spend Analysis and Emptoris Supplier Lifecycle Management use only the IBM Cognos Business Intelligence Platform for reporting. To configure the reporting setup, see the following topics. v Reporting for Emptoris Applications v Installation Files that are provided by IBM Emptoris for Reporting on page 70 v Workflow to Install Reporting for Emptoris Contract Management on page 72 v Workflow to Install Reporting for Emptoris Spend Analysis on page 97 Reporting for Emptoris Applications Reporting for Emptoris Contract Management includes integrating IBM InfoSphere DataStage and IBM Cognos with Emptoris Contract Management. Reporting for Emptoris Spend Analysis and Emptoris Supplier Lifecycle Management includes integrating Cognos. For Emptoris Contract Management The reporting setup for Emptoris Contract Management includes the following items. v v InfoSphere DataStage Cognos Business Intelligence Copyright IBM Corp. 2012,

78 For Emptoris Spend Analysis The Emptoris Spend Analysis setup requires only Cognos Business Intelligence. For Emptoris Supplier Lifecycle Management The Emptoris Supplier Lifecycle Management setup requires only Cognos Business Intelligence. Installation Files that are provided by IBM Emptoris for Reporting To use Cognos and InfoSphere DataStage for Emptoris Contract Management, and Emptoris Spend Analysis, you must download the software from the Passport Advantage website. Files that are provided by Emptoris The following table lists the packages that are provided for reporting. Table 25. Files for Configuring Reporting Package echos-agent-installer.jar Purpose The EchOS agent communicates with the Emptoris Strategic Supply Management Installer system. The EchOS agent is required on the systems on which you install InfoSphere DataStage and Cognos. To install the agent, run the echos-agent-installer.jar file. CognosIntegration_ _145.zip Applicable for both Emptoris Contract Management and Emptoris Spend Analysis. The Analytics Integration Module configures the Cognos Server to operate within the IBM Emptoris Suite. This file must be present in the root installation directory on the server on which the Emptoris Contract Management and Emptoris Spend Analysis applications to be installed. ContractMgmtAnalytics_ _145.zip Only applicable for Emptoris Contract Management. The Contract Management Analytics Application extension module installs the DataStage InfoSphere projects and associated jobs components, imports the Emptoris Contract Management Cognos reporting package and configures the Cognos data-source for reporting database access. This file must be present in the root installation directory on the server on which the Emptoris Contract Management application is to be installed. db2_target_database_ _<build_number>.zip Only applicable for Emptoris Contract Management. It contains the scripts to create the DB2 database for reporting. Files that must be downloaded separately The following table lists the packages that must be downloaded separately from the Passport Advantage and Fix Central website. 70 IBM Emptoris Suite: IBM Emptoris Suite Configuring

79 Table 26. Files for Reporting that must be downloaded separately Package Cognos Business Intelligence (64-bit) InfoSphere DataStage or Infosphere DataStage 11.5 Purpose Cognos Business Intelligence is used by both Emptoris Contract Management and Emptoris Spend Analysis for reporting. InfoSphere DataStage is only used by Emptoris Contract Management for reporting. Reporting for Emptoris Contract Management The process to install reporting includes installing the reporting database, preparing machines for the installation, installing Cognos and InfoSphere DataStage, running the Emptoris Strategic Supply Management Platform Installer, installing the products, and completing the post-installation tasks. For a detailed workflow, see Workflow to Install Reporting for Emptoris Contract Management on page 72. Architecture Reporting for Emptoris Contract Management includes database servers for InfoSphere DataStage and Cognos. The InfoSphere DataStage and Cognos servers are integrated with the Emptoris Contract Management setup. The Emptoris Contract Management setup includes a database server, one or multiple application servers, and a document server. The following diagram represents the reporting setup that is integrated with the Emptoris Contract Management setup. Figure 7. Reporting Setup for Emptoris Contract Management You must configure the database servers before you can install and configure InfoSphere DataStage and Cognos. Chapter 2. Reporting Configurations 71

80 Two instances of DB2 If you are using the DB2 database for Emptoris Contract Management and for the Reporting database, you must use two separate instances of DB2. The two instances are also required to ensure that the Oracle Compatibility Vector property is not enabled for Cognos. If the property is enabled, Cognos content store creation fails. The following diagram represents the two DB2 instances that are required. Figure 8. Two DB2 Instances Workflow to Install Reporting for Emptoris Contract Management The installation and configuration of reporting for Emptoris Contract Management involves various tasks that must be completed at different stages in the installation process for the Emptoris applications. The following table lists the various tasks that must be completed and the stage in the installation during which they must be completed. Table 27. Workflow to install Reporting for Emptoris Contract Management Task Stage Description Preparing the servers for Cognos and InfoSphere DataStage Configuring the reporting database Complete this task when you prepare the servers for the Emptoris applications. Complete this task when you prepare the databases for the Emptoris applications. Before you begin installing the reporting components on server machines, you must configure the server machines for installation. For more information, see Preparing Systems for Installation in the Planning section of the Installation Portfolio. Before you install the reporting components, you must install and configure the reporting database. For more information, see Reporting Database for Emptoris Contract Management on page IBM Emptoris Suite: IBM Emptoris Suite Configuring

81 Table 27. Workflow to install Reporting for Emptoris Contract Management (continued) Task Stage Description Creating the Cognos Content Store Installing and Configuring InfoSphere DataStage Installing and Configuring Cognos Prerequisites tasks for installing the Emptoris Suite Install the Emptoris applications Complete this task when you prepare the databases for the Emptoris applications. Complete this task before you install the Emptoris applications. Complete this task before you install the Emptoris applications. Complete this task before you install the Emptoris applications. The content store is a database that the Content Manager uses to store global configuration data, global settings such as the language and currency formats that are shown in the user interface, connections to data sources, and product-specific content. Do not use the Cognos Content Store that is available by default with Cognos. You must create the Content Store on DB2 or Oracle and use it. For more information, see Creating the Cognos Content Store on Oracle on page 77 or Cognos Content Store on DB2 on page 89. Installing and configuring InfoSphere DataStage involves the following steps: v Prerequisite Software for InfoSphere DataStage on page 107 v Preparing to run the InfoSphere DataStage Installation on page 107 v Installing InfoSphere DataStage on page 108 v Post-installation Tasks for InfoSphere DataStage on page 110 Installing and configuring Cognos involves the following steps: v Prerequisite Software for Cognos on page 116 v Installing Cognos on page 117 v Upgrading Cognos to on page 118 v Post-Installation Tasks to Configure Cognos for Emptoris Applications on page 118 Complete the prerequisite tasks and ensure that the reporting packages are saved in the setup for installing Emptoris Contract Management. For more information, see Prerequisites before you Install Emptoris Contract Management on page 93. For more information, see Quick Reference for Installation. Chapter 2. Reporting Configurations 73

82 Table 27. Workflow to install Reporting for Emptoris Contract Management (continued) Task Stage Description Post-installation tasks after you install the Emptoris Suite Complete this task after you install the Emptoris applications. Complete the post-installation tasks that are required to use the reporting feature for Emptoris Contract Management. For more information, see Post-installation Tasks after you Install Emptoris Contract Management on page 93. Reporting Database for Emptoris Contract Management Emptoris Contract Management uses IBM Cognos Business Intelligence Platform and IBM InfoSphere DataStage for reporting. The Reporting Database Configurations section contains the database configurations that are required for Emptoris Contract Management reporting. It does not cover the installation process. For instructions about installing the Oracle or DB2 server, see the respective installation guide. Note: Oracle RAC is not supported. The reporting user that is required during the installation of Emptoris Contract Management is different from the Cognos reporting user. Components of the reporting module The reporting module for Emptoris Contract Management consists of the following components. v Cognos: Works as the reporting engine v InfoSphere DataStage: Responsible for data transformations v Reporting schema: Schema that is used for Emptoris Contract Management The following table lists the components of the reporting module for Emptoris Contract Management. Table 28. Reporting components Schema Cognos Content Store InfoSphere DataStage meta data Emptoris Contract Management Reporting Database Description Relational database that contains data that Cognos BI uses to operate. Database that stores design-time, run-time, glossary, and other meta data for product modules in the InfoSphere Information Server suite. Database that contains the Emptoris Contract Management data that is used in reporting: users, individuals, clauses, contracts, templates. Information worksheet: You will need the details of the reporting database and the Emptoris Contract Management database while configuring the jobs in InfoSphere DataStage. Capture the following information at the time of installing and configuring your reporting database. 74 IBM Emptoris Suite: IBM Emptoris Suite Configuring

83 Table 29. Information worksheet for Reporting database Database Information to be captured Oracle v Database server port number: v v v Database service: User name: User password: DB2 v Database server port number: v v v v Database Name: User name: User password: Reporting schema name: Schemas in the Reporting Database: The reporting database includes schemas for Emptoris Contract Management, Cognos Content Store, and multiple schemas for InfoSphere DataStage. The following table lists the schemas that are used for the reporting database. Table 30. Schemas for the reporting database Database schema Emptoris Contract Management Reporting Cognos Content Store InfoSphere DataStage v Xmeta v Xmetasr Description Contains the Emptoris Contract Management data that is used in reporting: Users, individuals, clauses, contracts, templates Relational database that contains data that Cognos BI needs to operate. Shared component that stores design-time, run-time, glossary, and other meta data for product modules in the InfoSphere Information Server suite. Database Configurations for Oracle for Reporting: All schemas that are used in reporting can co-exist in the same database as the application schemas, such as the schemas for Emptoris Contract Management and Emptoris Strategic Supply Management Platform. However, it's recommended to separate the transactional and the data warehouse databases. This section contains the database configurations that are required only for Emptoris Contract Management reporting. It does not cover the database software installation process. For instructions on installing the Oracle database server, see Oracle installation guide. To configure the Oracle database for reporting, complete the following steps: 1. Create the database on Oracle for reporting. 2. Create an Oracle schema for reporting. 3. Create the Cognos Content Store on Oracle. 4. Create the InfoSphere DataStage metadata schemas on Oracle. Chapter 2. Reporting Configurations 75

84 Creating the Database on Oracle for Reporting: The first step in configuring the Oracle database for reporting is to create a database. Upgrading from an earlier version If you are upgrading from an earlier version, take a backup of your reporting database before proceeding with the installation of the applications. Installing a new version You can use Oracle Database 11g Standard and Enterprise Edition or Oracle Database 12c Release 1 Standard and Enterprise Edition. Create an Oracle database with the following settings. v The database character set should be AL32UTF8. v The database block size should be 8K. v Database statistics must be collected on a regular basis. v Database configuration requirements. For UNDO tablespace, the size depends on the UNDO retention period and transaction activity rate. Start with 5 GB of space and adjust as the database grows. For TEMP tablespace, provide 5 GB of space. Monitor the temp space usage and make necessary adjustments. For other database configuration parameters, use the following table as a guide to tune the database configuration in the [sp]init.ora file. Table 31. Database configurations that are based on database size Parameter Small Medium Large Database size (sum of bytes of all_ segments) 10g 50g - 100g 100g - 500g open_cursors processes sga_max_size 8G 15G 30G sga_target 8G 15G 30G pga_aggregate_target 2g 3g 5g sessions large_pool_size 100M 100M 100M dml_locks v Use the following table for the parameters that are not dependent on the database size. Table 32. Database configurations that are not based on database size Parameter cursor_sharing Value SIMILAR sort_area_size workarea_size_policy AUTO 76 IBM Emptoris Suite: IBM Emptoris Suite Configuring

85 Table 32. Database configurations that are not based on database size (continued) Parameter undo_management dp_keep_cache_size Value AUTO 32K Creating an Oracle Schema for Reporting: Schema creation on Oracle for Reporting includes configuring the database and creating the schema. Before you begin Complete the Prerequisites for the Oracle Database Server on page 8. Procedure To create the Oracle schema for reporting, complete the following steps: 1. Configuring the database and schema by running the create-suite-db script. For information about running the script, see Running the Script on Oracle on page Select option 6 when you run the create-suite-db script to create the Reporting database and schema. Creating the Cognos Content Store on Oracle: The content store is a database that Content Manager uses to store global configuration data, global settings such as the language and currency formats shown in the user interface, connections to data sources, and product-specific content. Creating the Content Store includes creating a tablespace and the schema. See the following sections in the IBM Cognos Business Intelligence Installation and Configuration Guide for information about creating the Cognos Content Store database. v Guidelines for creating the Content Store. v Suggested settings for creating the Content Store in Oracle. Configuring the database and schema is done by running the create-suite-db script. For information about running the script, see Running the Script on Oracle on page 10. When you run the create-suite-db script, the Reporting database is created when you select option 6 in the script. The Cognos Content Store is configured when you select option 7 in the script. Creating InfoSphere DataStage Metadata Schemas on Oracle: You must use the installation guide of InfoSphere DataStage to create the metadata schemas. For information about how to create the InfoSphere DataStage Metadata schemas, see the following guides. Chapter 2. Reporting Configurations 77

86 v InfoSphere Information Server Installing v InfoSphere Information Server Installing For more information, see the following topics: v : Pre-installing the metadata repository database in an Oracle database system (Windows) Pre-installing the metadata repository database in an Oracle database system (AIX SolarisLinux) v : Pre-installing the metadata repository database in an Oracle database system (Windows) Pre-installing the metadata repository database in an Oracle database system (AIX SolarisLinux) and. Database Configurations for DB2 for Reporting: To use the DB2 database server for reporting, you must configure the server by creating an instance, database, user, and database schema. Transactional and reporting databases can co-exist on the same server. However, the transactional database is configured with the Oracle compatibility on, while the reporting database is configured with the Oracle compatibility off. The Oracle compatibility setting is an instance wide parameter that affects all databases that are created in that instance. Therefore, a second instance is required for reporting. For more information, see Architecture on page 71. Each instance uses memory. It is therefore necessary that the server on which two instances are created has additional memory. Process for configuring the database To configure the DB2 database, complete the following steps: 1. Complete the prerequisites. a. Creating an Instance on DB2 for Reporting on page 79 b. Creating a User for the Reporting Schema on page Download the database configuration scripts that are provided in the installation files. 3. Run the database and schema creation scripts. Related reference: Two DB2 Instances on page 3 Two DB2 instances are required for the Emptoris applications and reporting. One instance is for the Emptoris applications with the Oracle Compatibility Vector property enabled. The other instance is for Reporting with the Oracle Compatibility Vector property disabled. If the property is enabled for reporting, Cognos Content Store creation fails. The two instances can be on the same or different systems. 78 IBM Emptoris Suite: IBM Emptoris Suite Configuring

87 Prerequisites for the Reporting DB2 Database Server: Before you run the scripts to configure the DB2 database for reporting, you must create a database instance and create the reporting user. Creating an Instance on DB2 for Reporting: A new DB2 instance must be created if the reporting database is on the same server as the transactional database that contains the schemas for Emptoris Strategic Supply Management Platform and Emptoris Contract Management. If the reporting database is on a separate server, you can skip this step. Creating an instance on a Linux database To create an instance on a Linux database, complete the following steps: 1. Log in as a root user. 2. Create an operating system user and make the user the instance owner. 3. Create the instance. 4. Configure the port. 5. Set the database manager configuration and the environment variable as follows. db2 update database manager configuration using svcename db2c_d2inst2 6. If required, configure the Firewall to allow traffic on the port of the instance to communicate with other applications. Example See the following example of creating an instance. [root@devdb2 ~]# useradd -u g db2iadm1 -m -d /home/db2inst2 db2inst2 -p passw0rd [root@devdb2 ~]# cd /opt/ibm/db2/v10.5/instance [root@devdb2 ~]#./db2icrt -u db2fenc1 db2inst2 [root@devdb2 ~]# vi /etc/services #new entry for db2 instance 2 db2c_db2inst /tcp [root@devdb2 ~]# su db2inst2 db2 update database manager configuration using svcename db2c_d2inst2 db2set DB2COMM=tcpip db2stop db2start Recommended Memory Table 33. Recommended Memory for Creating DB2 Instance for Reporting Server Requirements Total DB Size Memory CPU Small Less than 50GB 16GB 4 Medium 50G-100GB 32GB 8 Large 100G-500GB 64GB 12 Creating a User for the Reporting Schema: Before you create the reporting schema, you must create an operating system user as the owner of the reporting schema. Chapter 2. Reporting Configurations 79

88 About this task Consider the following points for creating the user: v If you are using DB2 on Windows, the user must belong to the DB2 users group. v For Linux, the user name must be less than 8 characters and in lowercase. v If you are using DB2 on UNIX, the UNIX users, groups, and instance names must all be in lowercase. v The values that you enter in the Emptoris Strategic Supply Management Installer for the user name must match the user name on the operating system. v When you upgrade to a new version of an Emptoris product, you can reuse the current DB2 database name, schema, and user name for the installation. Procedure To create a user for the reporting schema, complete the following steps: 1. Log in to the DB2 server as the root user. 2. Use the guidelines to create a user. Example Creating a Linux user erep1. [root@devdb2 ~]# adduser erep1 [root@devdb2 ~]# passwd erep1 Running the Scripts on DB2 for Reporting: After you configured the DB2 database for reporting, you must run the scripts that are provided in the installation files to create database and schemas. About this task The database scripts to create databases and reporting schema are available in the EMP_Resources_ _36.zip file in the installation files in the db-scripts\db2\suite-scripts directory. Procedure To run the script on DB2 for reporting, complete the following steps: 1. Copy the db-scripts\db2\suite-scripts directory to the DB2 server. 2. Make the user, who is the instance owner, the owner of the files. 3. Extract the Common DB Scripts.zip file to a directory. 4. Run the script as the instance owner by completing the following steps. Table 34. Running the DB2 script on Linux and Windows Linux 1. Change to the DB2\suite-scripts directory. 2. Grant execute permission to the.sh files. chmod +x *.sh chmod +x bin/*.sh Windows Run the script from a DB2 command window: Start > All Programs > IBM DB2 > DB2Copy1 > DB2 Command Window Administrator 80 IBM Emptoris Suite: IBM Emptoris Suite Configuring

89 5. Run the create-reporting-dbs script to create the database. v v Windows: create-reporting-dbs.bat Linux: create-reporting-dbs.sh The instance parameters are configured and DB2 is restarted. 6. Run the create-reporting-schemas script to create the schemas for the reporting components. v v Windows: create-reporting-schemas.bat Linux: create-reporting-schemas.sh The schema is created for each reporting component. Information that is required in the create-reporting-dbs Database Script: The create-reporting-dbs script prompts you to provide information when you run the script. The following table lists the questions that you must answer when you run the create-reporting-dbs script. Table 35. create-suite-db script Information that is required from the user Do you wish to configure and restart the DB2 instance? (Y/N) Description Select N if your instance has been previously configured and you are only adding new databases. Select Y If this is the first time you're using this instance. Upgrades: There are no instance level configuration changes compared to the previous release. If you're performing an 'in-place' upgrade, there's no need to reconfigure your DB2 instance. Enter the DB2 instance name Enter database name. Maximum 8 characters Enter the name of the temporary tablespace Enter the path for the DB2 functions that will be copied to system The name of the DB2 instance, for example, db2inst1. The name of the database that is to be created. The name of the temporary tablespace of the user that is to be created in the tablespace. Specify the directory on the DB2 server where user-defined functions for Emptoris Contract Management will be copied. The directory should be owned by the DB2 instance owner. Important: This directory should never be deleted. The Java and C functions are searched for in this directory. Examples The following example shows the values that you must provide when the script is run. Windows: Chapter 2. Reporting Configurations 81

90 Prerequisites: 1. Create an operating system user for each product, Cognos, Datastage and Emptoris Reporting. 2. Add the users to the DB2USERS group 3. Create a DB2 instance if it doesn t exist and configure the instance port number. 4. Login to the server as the instance owner, otherwise the database may be created in incorrect i Execute Script : Login as the DB2 instance owner and execute the script: create-reporting-dbs.bat Have you configured the DB2 instance port number [Y/N] :?y Please provide information about your instance and user: Enter the DB2 instance name: db2_02 Validating instance name... Please select an option to create the database for : 1 IBM Emptoris Reporting 2 IBM Cognos Content Store 3 IBM Datastage Metadata Repository 4 Exit Selection : 1 Do you wish to configure the DB2 instance? The instance will be restarted. [Y/N] :?y Please provide the information for the database to be created: Enter database name. Maximum 8 characters: repdb1 Enter the name of the temporary tablespace: temp Enter the path for the DB2 functions that will be copied to system: e:\repfunct1 This script is about to configure and restart the instance. Do you wish to continue? [Y/N]:?y Instance configuration starting... Database creation starting... Database configuration starting... Creating DB functions starting... Do you want to configure another database [Y/N] :?y Please select an option to create the database for : 1 IBM Emptoris Reporting 2 IBM Cognos Content Store 3 IBM Datastage Metadata Repository 4 Exit Selection : 2 Enter user name for the Cognos Content Store: csusr Please provide the information for the database to be created: Enter database name. Maximum 8 characters: cogdb Enter the values for the new schema to be created: Enter the Schema name [uppercase]: COGNOS Database creation starting... Database configuration starting... Do you want to configure another database [Y/N] :?Y Please select an option to create the database for : 1 IBM Emptoris Reporting 2 IBM Cognos Content Store 3 IBM Datastage Metadata Repository 4 Exit Selection : 3 Enter user name for Datastage: dsusr Please provide the information for the database to be created: Enter database name. Maximum 8 characters: DSDB Enter the values for the new schema to be created: Enter the Schema name [uppercase]: DSXMETA Instance configuration starting... Database creation starting IBM Emptoris Suite: IBM Emptoris Suite Configuring

91 Linux: Creating the Emptoris Contract Management Reporting database suite-scripts]$./create-reporting-dbs.sh... < removed info message > Have you configured DB2 instance to meet the prerequisites according to the installation guide and Please provide information about your instance: Enter the DB2 instance name: db2inst2 Please select an option to create the database for : 1 IBM Emptoris Reporting 2 IBM Cognos Content Store 3 IBM Datastage Metadata Repository 4 Exit Selection: 1 Enter user name for reporting: repsur1 Please provide the information for the database to be created: Enter the database name. Maximum 8 characters: rep1 Enter the name of the temporary tablespace: temp Enter the path for the DB2 functions that will be copied to system: /home/db2inst2/repfunc This script modifies instance parameters and restarts DB2. Do you wish to continue? (Y/N): Instance configuration starting... 10/02/ :16: SQL1064N DB2STOP processing was successful. SQL1064N DB2STOP processing was successful. 10/02/ :16: SQL1063N DB2START processing was successful. SQL1063N DB2START processing was successful. Database creation starting... Database configuration starting... Linux: Creating the Cognos and InfoSphere DataStage databases [db2inst2@suite-db-pe-1 suite-scripts]$./create-reporting-dbs.sh ################################################################################################## Prerequisites: **************** To create the DB2 database for the Emptoris applications, complete the following steps: 1. Create an operating system user for each product, Cognos, Datastage and Emptoris Reporting. 2. Create a DB2 instance if it doesn t exist. 3. Configure the instance port number. 4. Login to the server as the instance owner, otherwise the database may be created in incorrec Execute Script : **************** Example - Login as the DB2 instance owner../create-reporting-dbs.sh ################################################################################################## Have you configured DB2 instance to meet the prerequisites according to the installation guide and Please provide information about your instance: Enter the DB2 instance name: db2inst2 Please select an option to create the database for : 1 IBM Emptoris Reporting 2 IBM Cognos Content Store 3 IBM Datastage Metadata Repository 4 Exit Selection: 1 Do you wish to configure and restart the DB2 instance? (Y/N): y Please provide the information for the database to be created: Enter the database name. Maximum 8 characters: repdb Validating database name... Enter temporary tablespace name: temp Enter the path for the DB2 functions that will be copied to system: /home/db2inst2/functio This script modifies instance parameters and restarts DB2. Do you wish to continue? (Y/N): Instance configuration starting... 10/29/ :16: SQL1064N DB2STOP processing was successful. SQL1064N DB2STOP processing was successful. Chapter 2. Reporting Configurations 83

92 10/29/ :16: SQL1063N DB2START processing was successful. SQL1063N DB2START processing was successful. Database creation starting... Database configuration starting... Do you want create another database (Y/N)? y Please select an option to create the database for : 1 IBM Emptoris Reporting 2 IBM Cognos Content Store 3 IBM Datastage Metadata Repository 4 Exit Selection: 2 Enter user name for Cognos: suite1 Please provide the information for the database to be created: Enter the database name. Maximum 8 characters: cognosdb Validating database name... Schema name (uppercase): COGNOS Database creation starting... Database configuration starting... Do you want create another database (Y/N)? y Please select an option to create the database for : 1 IBM Emptoris Reporting 2 IBM Cognos Content Store 3 IBM Datastage Metadata Repository 4 Exit Selection: 3 Enter user name for Datastage: suite1 Please provide the information for the database to be created: Enter the database name. Maximum 8 characters: dsdb Validating database name... Schema name (uppercase): XMETA Instance configuration starting... Database creation starting... Database configuration starting... Do you want create another database (Y/N)? n Exiting from script. [db2inst2@suite-db-pe-1 suite-scripts]$ Information that is required in the create-reporting-schemas Database Script: The create-reporting-schemas script prompts you to provide information when you run the script. The Cognos and InfoSphere DataStage reporting schemas are created when you run the script. The following table lists the questions that you must answer when you run the create-suite-schema script. Table 36. create-suite-schema script Information that is required from the user Have you configured your database to meet the prerequisites and want to continue (Y/N)? Please provide information about your existing database and user Enter the name of the temporary tablespace Description The script will not work properly if the database and instance are not configured correctly. For a new installation, this can be accomplished with the create-reportingdbs script. Information about the existing database and the user. Enter the name of the temporary tablespace in your database. If you are not sure of what to specify, check your tablespace names from another session by connecting to the database as the instance owner (i.e. db2inst) and running the command select * from syscat.tablespaces. 84 IBM Emptoris Suite: IBM Emptoris Suite Configuring

93 Table 36. create-suite-schema script (continued) Information that is required from the user Enter suite user name Enter suite user password Enter the values for the new schema to be created Enter the Schema name (uppercase) Enter the name of the tablespace for data and indexes Description Enter the name of the operating system user that will be the owner of the schema. The user must exist and have a password. The password of the user entered in the previous step. Specify the values of the new schema. Enter the name of the reporting schema to be created. Always use uppercase for the schema names. Enter the name of the tablespace to be created. The user will be given grants on this tablespace. Example The following example shows the values that you must provide when the script is run. Windows: [db2inst2@db2dbsrv suite-scripts]$./create-reporting-schemas.sh rep1... <removed info message> Have you configured database to meet prerequisites according to the installation guide and want to Please provide information about your existing database and user: Enter temporary tablespace name: temp Enter reporting user name: repusr1 Enter reporting user password: Mypasswd1 Validating user... Enter the values for the new schema to be created: Schema name (uppercase): CMREP1 Tablespace for data and indexes: cmrep1 Do you wish to continue? (Y/N): y Creating Schema. Please wait... Do you want create a schema for other product [Press Enter or Y to continue]? n Exiting from script. [db2inst2@db2dbsrv suite-scripts]$ Database Configuration Parameters for Reporting: Certain parameters are configured when you run the scripts to configure the database. You can log in to the database as an instance owner to view the parameters. Viewing the parameters To view all the parameters, log in as an administrator and run the db2set all command. [db2inst2@d3400db suite-scripts]$ db2set -all [i] DB2_DEFERRED_PREPARE_SEMANTICS=YES [i] DB2_USE_ALTERNATE_PAGE_CLEANING=ON [i] DB2_INLIST_TO_NLJN=YES [i] DB2_REDUCED_OPTIMIZATION=YES [i] DB2COMM=TCPIP Chapter 2. Reporting Configurations 85

94 [i] DB2AUTOSTART=YES [g] DB2SYSTEM=d3400db.dub.usoh.ibm.com [g] DB2INSTDEF=db2inst1 [g] DB2ADMINSERVER=dasusr1 The following table lists the parameters that are set on the database. Table 37. Database configuration parameters Parameter Value Required for DB2_INLIST_TO_NLJN YES InfoSphere DataStage DB2_USE_ALTERNATE_PAGE_CLEANING ON DB2_REDUCED_OPTIMIZATION YES InfoSphere DataStage InfoSphere DataStage QUERY_HEAP_SZ 4096 IMMEDIATE InfoSphere DataStage ASLHEAPSZ 1024 IMMEDIATE InfoSphere DataStage agent_stack_sz 768 IMMEDIATE InfoSphere DataStage DFT_MON_TIMESTAMP OFF IMMEDIATE InfoSphere DataStage MON_HEAP_SZ 5120 Emptoris Contract Management Reporting database List of parameters The following table lists the database parameters that are configured during the creation of the database. Table 38. Database parameters that are configured during the creation of the database Parameter Codeset Pagesize Value UTF-8 32 K The following table lists the database parameters that are configured after the creation of the reporting database. Table 39. Reporting database parameters that are configured after the creation of the database Parameter AUTO_REVAL DECFLT_ROUNDING EXTENDED_ROW_SZ Value DEFERRED_FORCE ROUND_HALF_UP ENABLE LOGFILSIZ LOGPRIMARY 100 LOGSECOND 8 The following table lists the parameters that are configured after the creation of the Cognos database 86 IBM Emptoris Suite: IBM Emptoris Suite Configuring

95 Table 40. Database parameters that are configured after the creation of the Cognos database Parameter Value APPLHEAPSZ 1024 LOCKTIMEOUT 240 The following table lists the parameters that are configured after the creation of the InfoSphere DataStage database Table 41. Database parameters that are configured after the creation of the InfoSphere DataStage database Parameter Value LOCKLIST MAXLOCKS 60 SHEAPTHRES_SHR APPLHEAPSZ STMTHEAP LOGBUFSZ LOGFILSIZ 5000 LOGPRIMARY 50 LOGSECOND 200 AUTO_MAINT AUTO_TBL_MAINT AUTO_RNSTATS AUTOMATIC AUTOMATIC IMMEDIATE AUTOMATIC IMMEDIATE 2048 IMMEDIATE ON ON ON Example To check the database configuration for rep1 database, run the following commands as the database instance owner. db2 get db cfg for rep1 grep Database code set To see all parameters, run the following command. db2 get db cfg for erep Buffer Pools and Table Spaces for Reporting: The reporting database creation scripts create the required buffer pools and table spaces for reporting. The following buffer pools and table spaces are created. Table 42. Buffer pools and table spaces Name Component Pagesize v Buffer pool v Temp Buffer pool v Temp table space v Table space for data and indexes Emptoris Contract Management Reporting 32 K Chapter 2. Reporting Configurations 87

96 Table 42. Buffer pools and table spaces (continued) Name Component Pagesize BUFFERPOOL cogstore_08kbp Cognos 8 K BUFFERPOOL cogstore_32kbp Cognos 32 K TEMPORARY TABLESPACE TSN_USR_cogstore Cognos User TABLESPACE TSN_REG_cogstore Cognos 8 K BUFFERPOOL XMETA InfoSphere DataStage 32 K TEMPORARY TABLESPACE XMETATEMP USER TEMPORARY TABLESPACE BGSESSIONTEMP InfoSphere DataStage InfoSphere DataStage 8 K 32 K REGULAR TABLESPACE XMETA InfoSphere DataStage 32 K 4 K Run the following commands to create the buffer pool and table space. CONNECT TO <Database> SELECT TBSPACE, OWNER, OWNERTYPE,PAGESIZE FROM SYSCAT.TABLESPACES; SELECT BPNAME, PAGESIZE FROM SYSCAT.BUFFERPOOLS ; Permissions for Reporting Schema Owners: The database and schema creation scripts configure the user permissions for the reporting schema owners: Cognos, InfoSphere DataStage, and Emptoris Contract Management Reporting Database. The following table shows the permissions that are assigned to the reporting schema owners. Table 43. Permission for reporting schema owners Permission Emptoris Contract Management Reporting Database Cognos BINDADD X X X CONNECT X X X CREATETAB X X X IMPLICIT SCHEMA X X USE OF TABLESPACE X X X CREATIN, DROPIN, ALTERIN SCHEMA LOAD X X InfoSphere DataStage X Java and C functions Java and C functions for Emptoris Sourcing and Emptoris Contract Management included a set of Java and C functions for contracts bit-wise operations and time zone conversions to supplement the DB2 core functions. In the previous releases, the functions were not deployed automatically when a database or schema was copied to another server. The functions had to be loaded manually. 88 IBM Emptoris Suite: IBM Emptoris Suite Configuring

97 With release onwards, a new schema IBMCOMPAT is created that contains the functions. Users can now use the functions whenever required. The database administrators now create the functions once on each database instead of on multiple schema. Cognos Content Store on DB2: The content store is a database that Content Manager uses to store global configuration data, global settings such as the language and currency formats shown in the user interface, connections to data sources, and product-specific content. Creating the Content Store includes creating a table space and the schema. See the following sections in the IBM Cognos Business Intelligence Installation and Configuration Guide for information about creating the Cognos Content Store database. v Guidelines for creating the Content Store. v Suggested settings for creating the Content Store in DB2. Configuring the database and schema is done by running the create-reportingdbs.sh and create-reporting-schemas.sh scripts. The Reporting database is created when you select option 1 in the create-reporting-dbs.sh script. The Cognos Content Store is created when you select option 2 in the script. Only the Reporting schema is created when you run the create-reportingschemas.sh script. The schema for the Cognos Content Store is created when you run the create-reporting-dbs.sh script. You need not run the create-reporting-schemas.sh for creating the Content Store schema. For more information about the scripts, see Running the Scripts on DB2 for Reporting on page 80. Metadata Repository for multiple instances of InfoSphere DataStage: In an standard setup, you might have multiple instances of InfoSphere DataStage for the various environments like Staging, UAT, and Production. You must have a metadata repository for each instance of InfoSphere DataStage. InfoSphere DataStage 11.3.x supports only one metadata repository per database. This means that you can have only one installation of InfoSphere DataStage per database. However, you can use one of the following options to configure the metadata repository for multiple instances of InfoSphere DataStage. Multiple instances on DB2 If you want to configure a metadata repository for multiple instances on one DB2 database, refer to one of the following topics for the instructions. v Use the built-in DB2 database for the metadata repository. For more information, see Using built-in DB2 database for the metadata repository on page 91. v Use a DB2 database for the metadata repository. For more information, see Using a DB2 database for the metadata repository on page 91. Chapter 2. Reporting Configurations 89

98 The following diagram represents multiple instances of InfoSphere DataStage by using the DB2 database for the metadata repository. Figure 9. Multiple Instances of InfoSphere DataStage A single DB2 instance is used for multiple instances of InfoSphere DataStage instances. The following databases can co-exist on a single instance of the DB2 server: v Cognos v Emptoris Contract Management Reporting v InfoSphere DataStage instances Multiple instances on Oracle If you want to configure a metadata repository for multiple instances on one Oracle database, complete the workaround steps provided to install multiple instances of InfoSphere DataStage on the same Oracle Database. For more information, see Using an Oracle database for the metadata repository on page IBM Emptoris Suite: IBM Emptoris Suite Configuring