Supply Chain Intelligence: Installation Guide 2013

Supply Chain
Intelligence
Installation Guide
2013
Supply Chain Intelligence
Copyright and Disclaimer

Copyright © 2000 - 2013 Manhattan Associates, Inc. All rights reserved.
This documentation, as well as the software described in it, is furnished under license and may be used
or copied only in accordance with the terms of such license. The information in this documentation is
furnished for informational use only, is subject to change without notice, and should not be construed as a
commitment by Manhattan Associates, Inc. (“Manhattan”). No third party patent liability is assumed with
respect to the use of the information contained herein. While every precaution has been taken in the
preparation of this documentation, Manhattan assumes no responsibility for errors or omissions.
EXCEPT WHERE EXPRESSLY PROVIDED OTHERWISE, ALL CONTENT, MATERIALS AND
INFORMATION, ARE PROVIDED ON AN "AS IS" AND "AS AVAILABLE" BASIS. MANHATTAN
EXPRESSLY DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
Except as permitted by license, no part of this documentation may be reproduced, stored in a retrieval
system, or transmitted, in any form by any means, electronic, mechanical, recording, or otherwise, without
the prior written permission of Manhattan Associates.
Manhattan Associates is a registered trademark of Manhattan Associates, Inc.
All other brands, products, or services are trademarks, registered trademarks, or service marks of their
respective companies or organizations.
Contact Address:
Manhattan Associates, Inc.

2300 Windy Ridge Parkway,
Atlanta, Georgia 30339
http://www.manh.com/
Region Telephone Email
+1 877.756.7435 (U.S. and Canada
Americas only) callcenter@manh.com
+1 404.965.4025
(00) 800.988.0885 (China only)
Asia asiacustomersupport@manh.com
+86 21 3311 3499
Europe, Middle East, +44 (0) 1344 318400 (UK)
emeacustomersupport@manh.com
and Africa +31 (0)30 214 3400 (NL)
Australia +61 1300787050 aucustomersupport2@manh.com Installation Guide 2013
Unsure whom to contact? Call +1 404.965.4025 and you will be routed to the appropriate support
group.
Copyright © 2013 Manhattan Associates, Inc. All rights reserved.

Table of Contents
Preface ...................................................................................................................................................... 4
About this Guide .................................................................................................................................... 4
Who Should Read this Guide? .............................................................................................................. 4
Introduction ................................................................................................................................................ 5
Assumptions .......................................................................................................................................... 5
Quick Checklist ...................................................................................................................................... 6
Installing IBM Products .............................................................................................................................. 7
Editing httpd.conf for HTTP servers. ......................................................................................................... 8
Installing Oracle/DB2 on the DB Server .................................................................................................... 9
Extracting SCI Content .............................................................................................................................. 9
Setting Environment Variables ................................................................................................................ 10
Database and Schema Configuration ..................................................................................................... 11
Oracle Installation ................................................................................................................................ 11
DB2 Installation .................................................................................................................................... 19
Configuring and Starting Cognos Configuration ...................................................................................... 26
Deploying SCI ETL Console .................................................................................................................... 32
How to Import Packaged Business Intelligence Content ........................................................................ 33
Steps to Import the Base SCI Content................................................................................................. 34
Configuring SCI Connections .................................................................................................................. 40
Configuring SCI Data Source Connections ......................................................................................... 40
Configuration for updating Cube MDL Signons ....................................................................................... 45
Configuring SCI Cube Connections: ....................................................................................................... 45
Editing createschema.properties ......................................................................................................... 46
Description for the Cube connection properties .................................................................................. 46
Configuring Control file in SCI , to exclude or Add the cubes for Datasource updation task. ............. 47
Running Cube Connections Utility ....................................................................................................... 48
Installation Guide 2013

Preface
The preface explains the contents and organization of this manual. It also defines the common
terminology, abbreviations, and documentation conventions you may encounter while reading through the
Supply Chain Intelligence (SCI) Installation Guide.
About this Guide

This manual serves as a guide for installing and configuring Supply Chain Intelligence. It describes the
purpose, features, and basic operation of SCI and it also includes setup instructions for other required
components.
Who Should Read this Guide?

This guide assumes you have experience working with IBM AIX, RHEL and Microsoft Windows. This
guide provides basic procedures for installing and configuring SCI, but it is not a tutorial on functional
operations. For information on using AIX/Linux, please refer to your AIX/Linux documentation.

Introduction
This installation guide provides instructions for installing Manhattan Associates' Supply Chain
Intelligence (SCI). It provides guidelines for hardware and software requirements and complete
instructions for a custom installation. The custom installation enables you to choose the installation
location of SCI, as well as providing selection of the Server installation.
This document provides installation and configuration procedures for SCI 2013 on the following systems:
Database
• Oracle11gR2
• DB2 V10.1
Operating Systems
• AIX 7.1
• Red Hat Linux 6.3
The information in this document is based on the experience of Manhattan Associates and is suggestive
in nature. Based on your volume of transactions, hardware configuration, and/or the nature of your
business, the parameters and settings included in this document may require alterations.
Important: Complete the steps specified in the Preinstall Checklist and have them reviewed by
Manhattan Associates before proceeding to the installation process. This checklist is available with
Manhattan Associates Services team.
Assumptions
This document assumes the following install path on the UNIX server:
• Cognos Install -> /sci01/cognos/c10/
• SCI Install -> /sci01/manh/sci/
• Oracle Install -> /sci01/oracle/OraHome_1
• DB2 Install -> /sci01/IBM/db2connect/V10
Any reference to the above mentioned directory paths must be replaced with the appropriate paths on the
UNIX server.

Quick Checklist
AIX and Linux users must follow sections 1.3,1.4,1.5,1.6 and 1.7. Use the appropriate files from the table
below.
AIX
BI Server bisrvr_aix32_10.1.1_ml.tar.gz
Metrics Server cmmsrvr_aix32_10.1.1_ml.tar.gz
Data Manager dm_aix32_10.1.1_ml.tar.gz

Transformer bitrsfrmr_aix32_10.1.1_ml.tar.gz
Go mobile cogmobmp_10.1.1_ml.tar.gz
LINUX
BI Server bisrvr_linuxi38632_10.1.1_ml.tar.gz
Metrics Server cmmsrvr_linuxi38632_10.1.1_ml.tar.gz
Data Manager dm_linuxi8632_10.1.1_ml.tar.gz
Transformer bitrsfrmr_linuxi38632_10.1.1_ml.tar.gz
Go mobile cogmobmp_10.1.1_ml.tar.gz

Installing IBM Products

Instructions for installing IBM products are provided in the following document: Installation Guide for IBM
Products. Please note that the guide is a supplement, and not intended to replace the instructions
provided by IBM.
Supplemental Instructions and guidance are provided for the following products:
• IBM Cognos 10.1.1 BI Server
• IBM Cognos 10.1.1 BI Server FP2 (Fix Pack)
• IBM Cognos 10.1.1 Mobile Server FP3 (Fix Pack)
• IBM Cognos Metrics Manager
• IBM Cognos for MS Office
• IBM Cognos Go Mobile
• IBM DataManager
• IBM Powerplay Transformer

Editing httpd.conf for HTTP servers.

Note: We assume HTTP server is already installed with all the required functionalities (Like SSL, Mod
proxy). It can IBM Http or Apache HTTP server. Please contact IT team for installing HTTP server on your
OS.
Navigate to the HTTP Server installation folder and then to the conf sub folder. Open the httpd.conf file.
Add the following lines to the end of the <IfModule alias_module> section right after the last ScriptAlias
line.
#START SCI section
ScriptAlias /sci/cgi-bin/ "/sci01/cognos/c10/cgi-bin/"
Alias /sci/help "/sci01/cognos/c10/webcontent/documentation/en"
Alias /sci "/sci01/cognos/c10/webcontent"
Alias /logs "/u13/apps/manh/sci/logs"
#END SCI section
Add the following lines right after the last <Directory> section, before the next <IfModule>section.
#START SCI section
<Directory "/sci01/cognos/c10/cgi-bin/">
Options None
AllowOverride None
Order allow,deny
Allow from all
</Directory>
<Directory "/sci01/cognos/c10/webcontent">
Options None
AllowOverride None
Order allow,deny
Allow from all
</Directory>
<Directory "/sci01/cognos/c10/webcontent/documentation/en">
Options None

AllowOverride None
Order allow,deny
Allow from all
</Directory>
<Directory "/sci01/manh/sci/logs">
Options Indexes FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all
</Directory>
#END SCI section
Note: The logs directory mentioned above will be created after installing sci and running an ETL process.
Important: If SSL is required to be configured on SCI, then httpd.conf file has to be edited to support
SSL. Refer SSL_Conf_Guide for configuration steps.
Installing Oracle/DB2 on the DB Server

Instructions for installing Oracle/DB2 on the DB server are provided in the following document: SCI 2013
Database Setup Guidelines.
Extracting SCI Content

Extract the sci2013.xx.xxx.tar.gz file contents from the SCI install path into the folder /sci01/manh.

Verify that the sci folder with the following structure is created within the /sci01/manh directory.
Setting Environment Variables

You need to set the environment variables after installing the Cognos components and the Oracle/DB2
drivers on the web server.
• Open the /sci01/manh/sci/bin/setenv.sh file and make the following changes to the section in
the file that involves environment variables, setting them to the correct installation path
export JAVA_HOME=/usr/java6
export SCI_HOME=/sci01/manh/sci
export JYTHON_HOME=$SCI_HOME/bin
export COG_ROOT=/sci01/cognos/c10
export DB2DIR=/sci01/IBM/db2connect/V10
export ORACLE_HOME=/sci01/oracle/OraHome_1
Note: In SCI 2013 Jython is shipped inside SCI_HOME. No need to install Jython independently. Hence
the environment variable JYTHON_HOME should point to SCI_HOME/bin.
• After saving the changes, execute the following command on the UNIX prompt:
. ./setenv.sh
Important: Ensure the shell script setenv.sh is executed only once.

• Copy the following files to <JAVA Install directory>/jre/lib/ext and give appropriate
permission for the Jar files to execute”
− $COG_ROOT/bin/jre/1.6.0/lib/ext/bcprov-jdk14-145.jar
− $ORACLE_HOME/jdbc/lib/ojdbc6.jar
− $DB2DIR/java/db2java.zip (rename it to db2java.jar)
10

− $DB2DIR/java/db2jcc.jar
− $DB2DIR/java/db2jcc_license_cu.jar (This jar file is present only if db2connect is

installed for IBM i. Note: Root privileges needed for DB2Connect install)
• Copy the file $ORACLE_HOME/jdbc/lib/ojdbc6.jar to $SCI_HOME/lib folder.
Database and Schema Configuration

Oracle Installation
This section will help you to install Oracle, and create users and schema objects for setting up the SCI
database. To configure the SCI database:
Step 1: Edit the createschema.properties file
Step 2: Run the script runpreconfig.sh.
Editing createschema.properties
• Ensure that setenv.sh is executed. Note that setenv.sh should be executed only once in the
UNIX session.
• Open the file $SCI_HOME/bin/createschema.properties file.
11

12

13

• Edit the properties of the individual entries, using information from the table below. All the values
are mandatory unless specified otherwise.
Property Variable Refers to Description

_db_type Database Type the database type - Enter ORACLE
_SID SID the Oracle instance name on which all SCI schemas
need to be created.
_createusers Create ‘Create User’ Enter ‘Y’ to create a createuser.sh file containing the
Script oracle create user commands.
_dba DBA User Oracle DBA user name (having SYSDBA privilege)
_dba_pwd DBA password Oracle DBA password
_is_dba_user Check for DBA user If the ‘_dba’ user has SYSDBA privilege, this value
will be ‘Y’ by default.
If a user having SYSDBA privilege is not available

for installation, ‘_dba’ may be a user having required
privileges to create other users and grant them roles
and privileges. In such a case, this value will be ‘N’.
_scinamespace Namespace specified for This is the namespace name specified if Security is
Authentication configured in Cognos configuration. (Optional if
anonymous access is turned on)
14


_scicontentuser Valid User for that User who can login to the namespace specified
namespace above. (Optional if anonymous access is turned on)
_scicontentpwd Password Password for the above user. (Optional if
_tablespace Tablespace the tablespace that would hold the SCI schemas
_temp_tablespace Temp Tablespace the temporary tablespace
_index_tablespace Index Tablespace tablespace for indexes belonging to SCI schemas
_distributedETL ETL Type Value should be 1 or 0 depending if SCI ETL
installation is of distributed type or not. 0 is the
default value.
_centralizedServer Server Type Value should be 1 if Server Type is centralized or
else 0. 1 is the default value.
_scicat Cognos Catalog user the Data Manager Catalog schema name
_scicat_pwd Cognos Catalog the Data Manager Catalog schema password
password
_scictnt Cognos Content user the Cognos BI Content schema name
_scictnt_pwd Cognos Content the Cognos BI Content schema password
password
_scimetric Cognos Metric Store the Cognos BI Metric Store schema name
user
_scimetric_pwd Cognos Metric Store the Cognos BI Metric Store schema password
password
_sciconf Config user the SCI Configuration schema name
_sciconf_pwd Config password the SCI Configuration schema password
_scidw Datawarehouse user the SCI Datawarehouse schema name
_scidw_pwd Datawarehouse the SCI Datawarehouse schema password
password
15


_sciosinstance _sciimpsi – IBM i Optional - Depending on the products SCI is
_sciextos_db_type import installed with, enter the user names, password, and
release names of the other schemas.
_sciextos _sciimpte – TMS import
If a product is not required leave all the three
_sciextospwd _sciimpeem – EEM
corresponding entries blank.
_sciextos_SID import
_osprocessorder _sciimptcs – TCS import
_sciimpsi
_sciimpsi_pwd
_sciimpsi_ver
_scisiinstance
_sciextsi_db_type
_sciextsi
_sciextsipwd
_sciextsi_SID
_siprocessorder
_sciimpte
_sciimpte_pwd
_sciimpte_ver
_sciteinstance
_sciextte_db_type
_sciextte
_sciexttepwd
_sciextte_SID
_teprocessorder
_sciimpeem
_sciimpeem_pwd
_sciimpeem_ver
_scieeminstance
_sciexteem_db_type
_sciexteem
_sciexteempwd
_sciexteem_SID
_eemprocessorder
_sciimptcs
_sciimptcs_pwd
_sciimptcs_ver
_scitcsinstance
_sciexttcs_db_type
_sciexttcs
_sciexttcspwd
_sciexttcs_SID
_tcsprocessorder
16


_silibraryname IBM i Name The Library Name for accessing IBM i source. (For
more than 1 library please edit the library name
using ETL Configurator).
_scicatalog SCI Catalog Name The SCI catalog name which should be restored.
This value is SCI_Catalog.ctg by default.
_activeinstance SCI Active Instance The SCI Instance which should be made active. The
value of this should be the same as the Instance
whose processing order is set to 1. **
_loadScenario Load Scenario The Load Scenario value specified will be the Active
Load Scenario. **
• ** The values available are specified in the createschema.properties file.
• For running ETL against a particular version of the source product , set appropriate values for the
SCI instance and the import version in createschema.properties file. The grid below lists all the
supported source products , the corresponding SCI instance for it and their import versions.
Source Product SCI Instance Name Source Import

Version Version
Warehouse Management for WAREHOUSE MANAGEMENT OPEN 2009 2009
Open Systems SYSTEMS XR 2007-13
2010 2009
2011 2009
2013 2009
WAREHOUSE MANAGEMENT OPEN 2010 2010

SYSTEMS 2010-13
2011 2011
2012 2012
2013 2013
Warehouse Management for WAREHOUSE MANAGEMENT IBM I 2010 2010

IBM i 2007-13
2011 2011
2012 2012
2013 2013
17

Source Product SCI Instance Name Source Import

Version Version
Labor Management LABOR MANAGEMENT 2009-13 2010 2010
2011 2011
2012 2012
2013 2013
Extended Enterprise EXTENDED ENTERPRISE 2011 2011

Management (for Open MANAGEMENT 2010-13
Systems)
2012 2012
2013 2013
Transportation Planning and TRANSPORTATION PLANNING AND 2010 2010

Execution EXECUTION 2009-11
Fleet Management 2011 2011
Audit, Payments and Claims
TRANSPORTATION PLANNING AND 2012 2012
EXECUTION 2012-13
2013 2013
• After making necessary changes to the file, save the file and exit the editor.
Running runpreconfig.sh
1. Navigate to $SCI_HOME/bin.
2. Run the shell script runpreconfig.sh using the command:
. ./runpreconfig.sh > runpreconfig.log &
To see the execution status of runpreconfig run the command ‘tail -n 100 –f runpreconfig.log’
3. The following scripts are automatically created and executed in the same directory:
− createusers.sh – The createuser.sh file contains the Oracle Create User command for
all the DB users.
− createschema.sh - The createschema.sh file contains the Oracle commands for

creating schema objects and data for all the schemas.
− updateconfig.sh – This script updates the SCI Config database by taking the values
from createscehma.properties to set the active SCI instance, active Load Scenario, set
the database connection strings for the instance, update the processing order for the
instance, update the IBM i library name if specified.
18

− initialisedimension.sh – This script initializes the dimensions in datawarehouse

schema.
− createcatalog.sh – This script creates the catalog tables and restores the catalog
4. If there is any error during the execution of any of the shell scripts mentioned above, the
execution is terminated. User can check the logs in $SCI_HOME/schema/oracle/logs and
runpreconfig.log in $SCI_HOME/bin
5. Resolve the errors and run the runpreconfig.sh script again. If the users were already created,
make sure that you drop the user first before running the script again.
DB2 Installation
This section will help you to install DB2 for setting up the SCI database. To configure the SCI database:
Step 1: Edit the createschema.properties file.
Step 2: Create UNIX users corresponding to the DB schemas (.
Important: Assign these UNIX users to DB2Admin group.

Also grant the following privileges to these users on the DB2 database:
DBADM,CREATETAB,BINDADD,CONNECT,CREATE_NOT_FENCED_ROUTINE,
IMPLICIT_SCHEMA,LOAD, CREATE_EXTERNAL_ROUTINE,QUIESCE_CONNECT,SECADM
Step 3: Run the script runpreconfig.sh.
• Ensure that setenv.sh is executed. Note that setenv.sh should be executed only once in the
UNIX session.
• Open the $SCI_HOME/bin/createschema.properties file.
19

20

• Edit the properties of the individual entries using the information from the table below. All the
values are mandatory unless specified otherwise.

_db_type Database Type the database type - Enter DB2
_SID SID the DB2 DB Alias name on which all SCI schemas need
to be created.
_createusers Create ‘Create User’ Enter ‘N’ since DB2 users refer to the UNIX users.
21


Script
_dba DBA User DB2 DBA user name (example : db2inst1)
_dba_pwd DBA password DB2 DBA Password
_is_dba_user Check for DBA user Should be left blank. It is a feature only for Oracle
installation.
_distributedETL ETL Type Value should be 1 or 0 depending if SCI ETL installation

is of distributed type or not. 0 is the default value.
_centralizedServer Server Type Value should be 1 if Server Type is centralized or else
0. 1 is the default value.
_scinamespace Namespace specified This is the namespace name specified if Security is
for Authentication configured in Cognos configuration. (Optional if
_scicontentuser Valid User for that User who can login to the namespace specified above.
namespace (Optional if anonymous access is turned on)
_scicontentpwd Password Password for the above user. (Optional if anonymous
access is turned on)
_tablespace Tablespace DB2 Tablespace name.
_temp_tablespace Temp Tablespace DB2 Temp Tablespace name.
_index_tablespace Index Tablespace DB2 Index Tablespace name.
_scicat Cognos Catalog user the Data Manager Catalog schema name
_scicat_pwd Cognos Catalog the Data Manager Catalog schema password
password
_scictnt Cognos Content user the Cognos BI Content schema name
_scictnt_pwd Cognos Content the Cognos BI Content schema password
password
_scimetric Cognos Metric Store the Cognos BI Metric Store schema name
user
_scimetric_pwd Cognos Metric Store the Cognos BI Metric Store schema password
password
_sciconf Config user the SCI Configuration schema name
_sciconf_pwd Config password the SCI Configuration schema password
_scidw Datawarehouse user the SCI Datawarehouse schema name
_scidw_pwd Datawarehouse the SCI Datawarehouse schema password

password
_sciosinstance Optional - Depending on the products SCI is installed
_sciextos_db_type _sciimpsi – IBM i with, enter the user names, password, release names,
instance name, source db type, source schema name,
_sciextos import
source password, source SID and processing order of
_sciextospwd _sciimpte – TMS the other schemas.
22


_sciextos_SID import If a product is not required leave all the three
_osprocessorder _sciimpeem – EEM corresponding entries blank.
_sciimpsi import
_sciimpsi_pwd _sciimptcs – TCS
import
_sciimpsi_ver
_scisiinstance
_sciextsi_db_type
_sciextsi
_sciextsipwd
_sciextsi_SID
_siprocessorder
_sciimpte
_sciimpte_pwd
_sciimpte_ver
_sciteinstance
_sciextte_db_type
_sciextte
_sciexttepwd
_sciextte_SID
_teprocessorder
_sciimpeem
_sciimpeem_pwd
_sciimpeem_ver
_scieeminstance
_sciexteem_db_type
_sciexteem
_sciexteempwd
_sciexteem_SID
_eemprocessorder
_sciimptcs
_sciimptcs_pwd
_sciimptcs_ver
_scitcsinstance
_sciexttcs_db_type
_sciexttcs
_sciexttcspwd
_sciexttcs_SID
_tcsprocessorder
_silibraryname IBM i Library Name The Library Name for accessing IBM i source. (For
more than 1 library please edit the library name using
ETL Configurator)
_scicatalog SCI Catalog Name The SCI catalog name which should be restored. This
value is SCI_Catalog.ctg by default.
23


_activeinstance SCI Active Instance The SCI Instance which should be made active. The
value of this should be the same as the Instance whose
processing order is set to 1. **
_loadScenario Load Scenario The Load Scenario value specified will be the Active
Load Scenario. **
• ** The values available are specified in the createschema.properties file.
• After making necessary changes to the file, save the file and exit the editor.
Creating UNIX Users
Create the following UNIX users:
• sci_conf
• sci_imp_< wmis, tpe, tcs, eem>
• sci_dw
• sci_cat
• scictnt
Note: Cognos 10.1.1 cannot support an underscore (‘_’) in the user name for SCI Content DB. This
applies to DB2 environments only.
• sci_mtrc
Running runpreconfig.sh
1. Navigate to $SCI_HOME/bin.
2. Run the shell script runpreconfig.sh using the command:
../runpreconfig.sh > runpreconfig.log &
To see the execution status of runpreconfig run the command ‘tail -n 100 –f runpreconfig.log’
3. If there is any error during the execution of any of the shell scripts mentioned above, the
execution is terminated. User can check the logs in $SCI_HOME/bin/runpreconfig.log and
$SCI_HOME/schema/oracle/logs.
24

The following warning may come up during Import schema creation for any of the products. Please ignore
this and proceed.
4. Resolve the errors and run the runpreconfig.sh script again. If the tables were already created,
make sure that you clean the schemas first before running the script again.
25

Configuring and Starting Cognos Configuration

1. Ensure you have started the application in your WINDOWS box, Humming Bird > Exceed.
2. Log into AIX/UNIX machine with non-root user credentials.
3. Ensure JAVA_HOME environment variable is set properly.

For instance:
$ echo $JAVA_HOME ---- (if this was set to proper JAVA HOME path; skip the below step)
$ export JAVA_HOME=/usr/java6
4. Ensure you have copied the following JAR files to <JAVA Install directory>/jre/lib/ext and
provided appropriate permission for the Jar files to execute (i.e. CHMOD – 755)
$<Cognos Installation Home>/bin/jre/1.6.0/lib/ext/bcprov-jdk14-145.jar
$<Oracle Installation Home>/jdbc/lib/ojdbc6.jar

(e.g. Oracle Installation Home could be similar to / sci01/ oracle/ OraHom e_1 )
$DB2DIR/java/db2java.zip (rename it to db2java.jar)

$DB2DIR/java/db2jcc.jar
$DB2DIR/java/db2jcc_license_cu.jar
(This jar file is present only if db2connect is installed for IBM i. Note: Root privileges needed
for DB2Connect install)
5. Set DISPLAY property in AIX/UNIX to communicate with your local WINDOWS machine as
shown below: (i.e. 10.80.18.72 is none other your local WINDOWS IP Address)
$ export DISPLAY=10.80.18.72:0.0
6. Go to <IBM Cognos 10/8 Installation Home>/bin directory
$ cd /sci01/cognos/c10/bin
7. Start the Cognos Configuration.
$ ./cogconfig.sh
The Cognos Configuration window is displayed.

7.1 Replace the following in all the URLS for Local Configuration > Environment
• Local host with your server name or IP address.
• ibmcognos with sci.
26

• 80 with your Web Server Port Number.
7.2 For Cognos Go! Mobile Configuration if any…
In the Properties window, under Go! Mobile BlackBerry Settings, for the MDS host names
and port numbers property, change the default setting localhost:8080 for the primary
BlackBerry Enterprise Server as shown below:
27

8. If you wish to create new instance for Content Manager database/Go! Mobile database; Right
click Content Manger and create a new instance.
8.1 Content Manager database…

8.1.1 Input the name and select the database type (Oracle or DB2) from the drop down list.
Click Ok.
8.1.2 Input the right database credentials for Cognos Repository:
Database server and port number:

Specify the name or TCP/IP address of the database computer and port number.
Example:
10.80.16.209:1521
28

User ID and password:

Specify the user ID and password that the database uses to connect to the
content store.
Service name:
Specify the service name (SID) for the Oracle database instance.
Example:
SCIORADV
8.2 Cognos Go! Mobile database…

8.2.1 To add a database, in the Explorer window, under Data Access, Mobile, do the
following.
8.2.2 Right click on Mobile; in the context menu click New resource, Database.
8.2.3 In the Name field, type the name you want to call your database.
8.2.4 In the Type field, click the database type that you want, and click OK.
29

8.2.5 In the Database - Resource Properties window, type the details for the database
that you chose.
Note: Please refer the steps provided in section 8.1.2
9. Adjust other options if necessary and then save configuration (from the File menu, click Save).
Note that IBM Cognos 8 Go! Mobile can use its own separate content store.
10. Post successful testing content store connection as shown above; Save & Start the Cognos 8
service using Cognos Configuration.
30

Click the Start icon to start the server.
While running Cognos configuration you may get the following warning message. This is because
the SMTP server connection is not configured. Click OK and proceed ahead by ignoring this
warning message. Click Continue on the next screen.
Once all services got started successfully, close and exit the screen.
Configure HTTP Server for IBM Cognos Go! Mobile

1. Log In with ROOT user credentials to the AIX/UNIX box.
2. For Cognos GO! Mobile Configuration; create/add/modify the MIME type for the specific
product as illustrated below:
2.1 Locate the mime.types file at <HTTP Server Installation Home>

(e.g. /sci01/HTTPServer/conf)
2.2 Open the master configuration files mime.types with edit permission.
2.3 Ensure any entry which you are adding, exists already; if exists, modify it.
2.4 For a BlackBerry installation, add the following line to the file:
application/vnd.rim.cod.
2.5 For a BlackBerry or Symbian installation, add the following line to the file:
text/vnd.sun.j2me.app-descriptor
2.6 For a Symbian installation, do the following:

application/java-archive
2.7 For a Windows Mobile installation, do the following:

application/vnd.ms-cab-compressed
31

Deploying SCI ETL Console

Step 1: Ensure that setenv.sh file is executed and the environment variables are set appropriately.
Step 2: Stop the Cognos services and HTTP server prior to any changes.
Step 3: From the /sci01/manh/cognos/c10 folder, run the command:
. ./deployetlconsole.sh
Step 4: Start the Cognos services and HTTP server.
32

How to Import Packaged Business Intelligence

Content
The SCI installation comes with pre-packaged content that is in the form of zip files. These files can be
found in the SCI Media and needs to be copied into the $COG_ROOT/deployment directory.
SCI 2013 comes with the following pre-packaged content zip files.
SCI Analytics:
Filename Content
SCI_Content_2013.0.00.x.zip Base Analytics SCI Content
WMOS_2013.0.0.x.zip WMOS SCPP Content
Labor_Management_2013.0.00.x.zip Labor Management Content
WM_IBMI_2013.0.00.x.zip WM for IBM I Content
WMOS_XR_2013.0.01.x.zip WMOS XR Content
Transportation_Planning_Execution_2013.0.00.x.zip Transportation Planning Execution Content
Extended_Enterprise_Management_2013.0.00.x.zip Extended Enterprise Management Content
SCI Operational:
Filename Content
Operational_SCI_Content_2013.0.00.x.zip Base Operational SCI Content
WMOS_OP_2013.0.01.x.zip WMOS SCPP Content
Labor_Management_OP_2013.0.01.x.zip Labor Management Content
WM_LM_SCI_Business_Insight_2013.0.01.x.zip WM LM Business Insight Content
Advanced_Planning_OP_2013.0.00.x.zip Advanced Planning Content

Total_Cost_to_Serve_OP_2013.0.01.x.zip Total Cost to Serve Content
Order_Lifecycle_Management_OP_2013.0.00.x.zip Order Lifecycle Management Content
Replenishment_IBMI_Stand-Alone_OP_2013.0.00.x.zip Replenishment IBMI Stand-Alone Content
Replenishment_OS_Integrated_OP_2013.0.00.x.zip Replenishment OS Integrated Content
33

Replenishment_OS_Stand-Alone_OP_2013.0.00.x.zip Replenishment OS Stand-Alone Content
Transportation_Planning_Execution_OP_2013.0.00.x.zip Transportation Planning and Execution

Content
Extended_Enterprise_Management_OP_2013.0.00.x.zip Extended Enterprise Management Content
Once copied, it will be necessary to import this content. Follow the steps below for importing SCI content.
Note: Base Analytics/Operational SCI Content must be imported before importing any other product
specific Analytics/Operational Content
Steps to Import the Base SCI Content

1. From the Welcome page, open IBM Cognos Connection.
2. On the IBM Cognos Connection page, select IBM Cognos Administration from the Launch
menu. Select the Configuration tab.
34

3. Select Portlets from the left menu. Click the IBM Cognos Content option.
4. Click the Properties icon for IBM Cognos Navigator.
5. In the Name field, modify the name from IBM Cognos Navigator to SCI Navigator and click OK.
6. Repeat steps 3, 4, and 5 for the IBM Cognos Viewer option. Modify the name from Cognos
Viewer to SCI Viewer and click OK.
35

7. Select Content Administration from the left menu. From the list of icons, select New Import
icon and click Next.
8. Select SCI_ Content_20XX.X.XX.X and proceed Next.
9. Enter the password and click OK.
Note: The password is available in the content password.txt file. (Installation CD)
36

10. Specify a Name and provide a brief summary in the Description field and click Next. The name
should be different from the name that comes by default.
11. Proceed Next till the below wizard appears (Select the public folders content - New Import wizard).
Select all the Content Folder and proceed Next
12. Click Next and proceed to next window.
37

13. Follow the default Steps and till the below wizard appears (Select an action - New Import wizard).
Select Save and run once option and then click Finish.
14. Select the time option as Now to run the import immediately, and click Run.
15. You can see a confirmation screen. If all information displayed is correct, click OK to import the
SCI 20XX.X.XX.X Content.
16. On successful completion, you will have below content in Public Folder.
38

Import product specific content

Note: Import SCI Base content before importing any product specific content.
1. Copy required content (Product_Name_20XX.X.XX.X.zip) to Cognos Deployment folder.

2. Go to > Cognos Connection > IBM Cognos Administration.
3. Go to Configuration tab > Content Administration > New import . icon
4. Select Product_Name_20XX.X.XX.X and proceed Next.
5. Follow the steps as mentioned above in Steps to Import the SCI Content (Step-9 to 15) to
complete the import.
Note: Follow the above section “Import product specific content” to import any product specific
packages
39

Configuring SCI Connections

Configuring SCI Data Source Connections
This step is to configure the Data Sources (other than the Cube data sources) so that they correctly point
to the appropriate database schema. Use the following steps to configure the data sources:
1. From the Welcome page, open IBM Cognos Connection.
2. On the IBM Cognos Connection page, select IBM Cognos Administration from the Launch
menu. Select the Configuration tab.
40

3. Navigate to the SCI_DW data source in the list, and click the data source name.
4. Click the Properties icon to modify the connection property of the data source.
5. Navigate to the Connection tab and edit the connection string of the SCI Datawarehouse
appropriately. Select the type of the database (Oracle or DB2) from the dropdown, and click the
Edit icon to edit the database details.
41

6. Edit the SQL *Net connect string field to contain the Service Name (SID) of the Oracle Instance
where the SCI Datawarehouse schema is installed (The subsequent screens refer to an Oracle-
SCI installation. For DB2 installations, the same steps have to be repeated selecting DB2 in the
previous step)
7. Upon clicking OK twice and arriving at the screen below, click the SCI_DW hyperlink to edit the
Signon (User Name & Password) information.
8. Click the Properties icon of the Signon object SCI_DW.
42

9. Navigate to the Signon tab, and click the Edit the signon hyperlink.
10. Enter the schema name and password of the SCI Datawarehouse schema.
11. Upon clicking OK twice and arriving at the screen below, click the SCI_DW hyperlink.
12. Click the Test Connection icon.
43

13. Click the Test button to verify whether the supplied SID, User Name and Password are correct.
14. Repeat the above mentioned steps for the following necessary data sources, which point to an
Oracle or DB2 schema.
• IBM i – Points to the Warehouse Management IBM i source database and should be edited only
in case IBM i reports are to be run.
44

Configuration for updating Cube MDL Signons

Note: This configuration is required if you want to process cubes on an environment where Custom
Authentication Namespaces are configured. Make sure this step is executed before executing Cube
processing.
When we configure multiple custom authentication namespaces in the Cognos Configuration , then to
process cubes on this environment ,we need to update the Appropriate sign on information inside cube
MDLs.
There is a utility called updatesignon.py in $SCI_HOME/bin to achieve this. You need to identify a
suitable namespace , user name and password that can be used all the time during cube processing ,
and set them in createschema.properties file.
Make sure that $SCI_HOME/bin/createschema.properties has been updated with appropriate

namespace, user and password to be used for updating sign on.
Example :
_scinamespace=CustomAuth1
_scicontentuser=system
_scicontentpwd=password
Navigate to $SCI_HOME/bin folder and run the jython script updatesignon.py using the following
command:
jython updatesignon.py
Configuring SCI Cube Connections:

A utility called “c10CubeBuilder” , which is present inside $SCI_HOME is used to update Cube
connections in SCI. This utility reads various configuration parameters from createschema.properties file.
45

The following properties inside createschema.properties has to be configured for updating SCI Cube
datasource connection details .
Description for the Cube connection properties

c10.url Cognos Install. Cognos Gateway URI. This should be same as the
Gateway URI specified in the Gateway settings of
Cognos configuration.
EX : http://ma-india-u209.asia.manh.com:80/sci/cgi-
bin/cognos.cgi
c10.authEnabled Security enabled on Set this to 'Y' if authentication is enabled , else set it
Cognos server. to 'N'.
c10.ns Security enabled on The ID of the security namespace that will be used
Cognos server. to log into C10. Use any of the namespace ID values
that are configured as custom authentication
namespaces in SCI Cognos server.
c10.user Security enabled on The username to be used to log into C10.
Cognos server.
c10.pwd Security enabled on The password to be used to log into C10.
Cognos server.
Note:
1.Overall execution details can be found in the log file c10CubeBuilder.log , inside $SCI_HOME/bin. This
log file gets generated during runtime.
2. Assumption: The Cube connection utility assumes that Transformer executable is installed at the
location $COG_ROOT/bin.
46

Configuring Control file in SCI , to exclude or Add the cubes

for Datasource updation task.
The “c10CubeBuilder” utility accepts a XML input , to update cube connections. This XML will contain the
tags to specify the cubes , for which the Datasource connection details has to be updated.
These details are stored in a file called Control_template.xml , which is present inside $SCI_HOME/
c10CubeBuilder folder.
Note: By default all the cubes in SCI (for all products) will be configured for Datasource updation task. We
can exclude or include any cube , by editing this Control_template.xml file.
Excluding a Cube :
• Identify the Data source for the Cube.
• Edit the Control_template.xml file and search with the Data source name.
• Delete the connswap Tag corresponding to this cube.
Ex: Suppose you want to exclude Data source ASN_Cube from the updation task , then following
tag has to be deleted from Control_template.xml.
<connswap connName="ASN_Cube" dsName="ASN_Cube" >

<cubesrc id="1" unixloc="<SCI_HOME> /cubes/output/ASN_Cube.mdc”/>
</connswap>
• Save the xml file.
By Doing this ,Data source ASN_Cube will not be updated when the utility runs.
Adding a Cube:
• Identify the Data source for the Cube.
• Edit the Control_template.xml file.
• Add the connswap tag for this cube.
Ex: Suppose you want to add Data source Test_Cube to the updation task , then following tag
has to be added to Control_template.xml.
<connswap connName="Test_Cube" dsName="Test_Cube" >

<cubesrc id="1" unixloc="<SCI_HOME> /cubes/output/Test_Cube.mdc”/>
</connswap>
• Save the xml file.
By Doing this ,Data source Test_Cube will be updated when the utility runs.
47

Running Cube Connections Utility

• Navigate to $SCI_HOME/bin
• Execute setenv.sh
• Run the cubeconnections.py jython script using the command:
jython cubeconnections.py
48

Supply Chain Intelligence: Installation Guide 2013

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Supply Chain Intelligence: Installation Guide 2013

Uploaded by

Copyright:

Available Formats

Supply Chain

Copyright and Disclaimer

Manhattan Associates, Inc.

Copyright © 2013 Manhattan Associates, Inc. All rights reserved.

Copyright © 2013 Manhattan Associates, Inc. All rights reserved.

About this Guide

Who Should Read this Guide?

Installation Guide 2013

Copyright © 2013 Manhattan Associates, Inc. All rights reserved.

• Red Hat Linux 6.3

• Cognos Install -> /sci01/cognos/c10/

• SCI Install -> /sci01/manh/sci/

• Oracle Install -> /sci01/oracle/OraHome_1

• DB2 Install -> /sci01/IBM/db2connect/V10

Copyright © 2013 Manhattan Associates, Inc. All rights reserved.

Metrics Server cmmsrvr_aix32_10.1.1_ml.tar.gz

Data Manager dm_aix32_10.1.1_ml.tar.gz

Data Manager dm_linuxi8632_10.1.1_ml.tar.gz

Installation Guide 2013

Copyright © 2013 Manhattan Associates, Inc. All rights reserved.

Installing IBM Products

• IBM Cognos 10.1.1 BI Server

• IBM Cognos 10.1.1 BI Server FP2 (Fix Pack)

• IBM Cognos 10.1.1 Mobile Server FP3 (Fix Pack)

• IBM Cognos Metrics Manager

• IBM Cognos for MS Office

• IBM Cognos Go Mobile

• IBM Powerplay Transformer

Installation Guide 2013

Copyright © 2013 Manhattan Associates, Inc. All rights reserved.

Editing httpd.conf for HTTP servers.

#START SCI section

ScriptAlias /sci/cgi-bin/ "/sci01/cognos/c10/cgi-bin/"

Alias /sci/help "/sci01/cognos/c10/webcontent/documentation/en"

Alias /sci "/sci01/cognos/c10/webcontent"

Alias /logs "/u13/apps/manh/sci/logs"

#END SCI section

#START SCI section

Allow from all

Allow from all

Copyright © 2013 Manhattan Associates, Inc. All rights reserved.

Allow from all

Options Indexes FollowSymLinks

Allow from all

#END SCI section

Installing Oracle/DB2 on the DB Server

Extracting SCI Content

Installation Guide 2013

Copyright © 2013 Manhattan Associates, Inc. All rights reserved.

Setting Environment Variables

Important: Ensure the shell script setenv.sh is executed only once.

− $DB2DIR/java/db2java.zip (rename it to db2java.jar)

Copyright © 2013 Manhattan Associates, Inc. All rights reserved.

− $DB2DIR/java/db2jcc_license_cu.jar (This jar file is present only if db2connect is

• Copy the file $ORACLE_HOME/jdbc/lib/ojdbc6.jar to $SCI_HOME/lib folder.

Database and Schema Configuration

Step 1: Edit the createschema.properties file

Step 2: Run the script runpreconfig.sh.

• Open the file $SCI_HOME/bin/createschema.properties file.

Installation Guide 2013

Copyright © 2013 Manhattan Associates, Inc. All rights reserved.

Installation Guide 2013

Copyright © 2013 Manhattan Associates, Inc. All rights reserved.