Customer Profitability Installation Guide R18.1

Temenos Analytics – Customer Profitability
Installation Guide R18
Information in this document is subject to change without notice.
No part of this document may be reproduced or transmitted in any form or by any means,
for any purpose, without the express written permission of TEMENOS HEADQUARTERS SA.
© 2010 Temenos Headquarters SA - all rights reserved.

Temenos Analytics – Customer Profitability Installation Guide
Table of Contents
Table of Contents........................................................................................................................................ 1
Document History........................................................................................................................................ 3
Introduction.................................................................................................................................................. 3
Initial Preparation......................................................................................................................................... 4
Application Structure/Layers................................................................................................................. 4
Application Requirements..................................................................................................................... 5
Pre-Installation..................................................................................................................................... 5
Installation Steps......................................................................................................................................... 5
Running Installer – Single Server......................................................................................................... 6
Running Installer – Multi-Server........................................................................................................... 9
Database Server................................................................................................................................ 10
Web Application Server...................................................................................................................... 13
Run ReportViewer.exe....................................................................................................................... 17
Create Local User.............................................................................................................................. 17
Report Server Access for InsightWSUser...........................................................................................18
Testing the Install....................................................................................................................................... 19
Model Configuration................................................................................................................................... 20
Importing Customers and Accounts........................................................................................................... 20
Importing from InsightStaging............................................................................................................. 20
Importing from a system other than Insight........................................................................................21
Authentication Options............................................................................................................................... 21
Error Investigation...................................................................................................................................... 22
Installation without Installer........................................................................................................................ 26
Database Server Setup...................................................................................................................... 26
Reporting Server Setup...................................................................................................................... 27
Create Local User.............................................................................................................................. 27
Web Server Setup.............................................................................................................................. 27
Web Service with Alternate Binding................................................................................................... 29
Uninstall..................................................................................................................................................... 31
Related Documentation............................................................................................................................. 33
2 TEMENOS Customer Profitability

Document History
Author Version Date
Sylvia McCullough 18.1 07/01/2019
Comments:
Introduction
Customer Profitability is both a batch and online application whose purpose is to assist Financial
Institutions in calculating and comparing profitability. It works with the Temenos Analytics Warehouse
ETL processing to calculate profitability for account data and also serves as a web application for users to
do what-if profitability analysis.
This installation guide is provided for the Insight Implementation team to assist in installing the various
components of the Customer Profitability application using the installer. This guide will also give
information on what the Installer has setup and how to troubleshoot any issues.
In addition to installing the web application and databases, components are added to the Analytics
InsightETL and InsightStaging databases. Analytics R18 must be installed before running this installer.

Initial Preparation
Application Structure/Layers
The Customer Profitability web application requires the following components:

 IIS Server
IIS Server is the web server that is used to host the Web application (InsightPricing) in addition to the
Web Services (InsightPricingWS)
 SQL server:
SQL server is the database provider for storing data in the InsightPricing database
 Reporting Services:
Reporting Services is the report provider for the internal reports.
The web application, SQL database and Report server can be installed on different servers.
The following illustration shows the Customer Profitability application components:

Application Requirements
Refer to the R18 Advanced Analytics Platform Environment Requirements document for required
software components. It you are installing without R18 Analytics as the source, here are the minimum
requirements:
Server Side
OS
 Windows Server 2012 or later
 .NET Framework 3.5 and 4.5
IIS  IIS7 +
.NET Framework  .NET 2.0 Framework with latest service pack
SQL Server
 Windows Server 2012 or later
 SQL server configured in mixed mode authentication
Report Services  SQL 2012 Reporting Services or later with latest service pack
Client Side
OS
 Microsoft Windows or Windows Server operating system.
Browser  Internet Explorer 11.0 (set in compatibly mode)
Pre-Installation
Before you run the installer you will need to know the following:
 Server name for the Web application

 Server name for the InsightPricing database
 Server name for the Reporting Services reports
Note: These can all be on the same server
 Directory where the Web application files will be copied to on the Web Server
 Name of a user to test the installation
 Name and Password of SQL user for database access (Normally InsightDBUser)

Installation Steps
This section uses the Installer to load the Customer Profitability components. The installer will do the
following:
 Setup the application and web service in IIS
 Create an InsightPricing database and load it with demo data
 Add data to AttributeCalculations and Index tables in InsightETL database
 Add stored procedures and data to InsightStaging database
 Add data to RuleDefinitions, RuleColumns and RuleValues table in InsightETL
 Add SQL user InsightDBUser for database access
 Add local user InsightWSUser for report access
 Add Reports and Data Source to Reporting Services
A log of the installation process is available in the C:\Customer Profitability Installation.log

Once complete there are some additional manual steps to the setup.
Running Installer – Single Server

Use these instructions if you are installing the database and application on the same server. Once
complete continue with the Run ReportViewer.exe step. If you are installing the database and web
application on separate servers, follow the instructions in Running Installer – Multi-Server.
1. Launch the installer by running Customer Profitability Setup.exe provided by Distribution. Click
Next to start the Installer.
2. Choose both the Database Server and Application Server, and then click Next.

3. Enter the name of the server that will host the web application in the Application Server box.
Enter the name of the SQL database server in the Database Server box including an instance
name if applicable. Enter the TFS DataPath. This is where data files will be copied and them
subsequently imported into the databases. The SQL Username and Password will be used in the
connection string for database access. Click Next to continue.

4. Enter the URL of the SSRS Report server. In the Super User Account box, enter the name of a
user who will test the installation. Until Pricing is configured, this will be the only user who can
access the web application. All others will just see a blank screen. Click Next to continue.
5. Click Install to start the installation process.
6. The window shows a status bar and informational messages about what tasks the installer is
performing. This process will take several minutes.

7. On completion click ‘Finish’ to end the installation process.
8. Go to the next step to Run Reportviewer.exe
Running Installer – Multi-Server

Use these instructions if you are installing the database and application different servers. Once complete
continue with the Run ReportViewer.exe step.

Database Server
1. Copy the installer to the Database server. Launch the installer by running Customer Profitability
Setup.exe provided by Distribution. Click Next to start the Installer.
2. Choose Database Server on the components selection screen.
Enter the name of the SQL database server in the Database Server box including the instance if
applicable. InsightDBUser will be the SQL user setup in database connection strings. It will have

owner privileges on InsightPricing database. If you change the password from the default or the
username, you will need to update the connection string in the Web.config files for the web
application. Click Next to continue.
4. Enter the URL of the SSRS Report server. In the Super User Account box, enter the name of a
user who will test the installation. Until Pricing is configured, this will be the only user who can
access the web application. All others will just see a blank screen. Click Next to continue.

6. The installer will then complete the installation process. The window shows a status bar and
informational messages about what tasks the installer is performing

Web Application Server
1. Copy the installer to the Application server. Launch the installer by running Customer
Profitability Setup.exe provided by Distribution. Click Next to start the Installer.

2. Choose Application Server on the components selection screen.
Enter the name of the SQL database server in the Database Server box including the instance if
applicable. Click Next to continue.



Run ReportViewer.exe
1. Navigate to C:\inetpub\wwwroot\Insight Application\Insight Pricing\V121

2. Run ReportViewer.exe to install the control.
3. Restart IIS by opening a command window as an Administrator. Enter IISReset. You can also
reset IIS using IIS Manager.
Create Local User

Using Computer Manager, check that the InsightWSUser was created.
If the Installer was unable to create InsightWSUser, you must create this local user account for the Web
Service and Report Server:
1. Create [InsightWSUser] and [Password] as a local windows user (Computer Management, Local
Users and groups) on the Reporting Server and Web Server (if separate), make sure to check
password never expires, and uncheck user must change password at next logon. Note the
password as it is required in a later step.
2. Give [InsightWSUser] browser rights to the InsightPricing report server folder in Report Manager.
3. Update the InsightPricing application with the correct password. This can be done by editing the
Application Settings for the InsightPricing in IIS Manager or by updating the Web.Config directly.
The Web.config will be in c:Inetpub\wwwroot\Insight Application\Insight Pricing\V121\App\
Web.config. Update the RSUser/Password for the Report Server and the WSUser/Password for
the Web server in the AppSettings section.
Web.Config Example:

IIS Manager Example:
Report Server Access for InsightWSUser
In the Reporting Services report manager, give the InsightWSUser Browser access to the InsightPricing
folder. This is used for the internal Scenario and Usage reports.

Testing the Install

Launch Insight Pricing from a web browser by entering the application’s URL. E.g.
Http://servername/InsightPricing. The server name is the application server name. You can also launch
from within the IIS Manager by choosing the Browse action on the InsightPricing application.
You should see the Case List screen as the default when the application is launched. (shown below)
If this screen is not displayed, i.e. you see a blank screen; use the Error Investigation section to
troubleshoot the issue.
If the application successfully displays the Case List screen, you can continue to configure the Pricing
model and setup an interface for importing data from a banking system source such as the Insight ETL.
The data loaded into the InsightPricing database during installation will be deleted and replaced with a
custom model for the bank.

Model Configuration
The Installer will create an InsightPricing database with one User and some test data. That one User will
be able to test the web application to determine it has been installed properly. Once the application has
been tested, the InsightPricing database will be cleared of all data and a customized Pricing model will be
loaded.
The Pricing web application will not display until the database is populated with a Pricing model and at
least one user is setup. Scripts are used to load the initial model, and then a Pricing Administrator will
maintain the model using the application screens. Follow the instructions in the Insight Pricing
Configuration Guide and use the Excel document ‘Customer Profitability ModelLoad.xlsm’ for creating
SQL scripts to load the initial model data.
Importing Customers and Accounts

Customer Profitability is designed to import customers and account data from an external source. The
following tables are imported:
 PricingSourceCustomer
 PricingSourceDate
 PricingSourceFTPRate
 PricingSourceProductRecord
 PricingSourceServiceChargeRecord
 PricingSourceTransactionRecord
Refer to the Customer Profitability Configuration guide for more details.
Importing from InsightStaging
The InsightStaging will have a stored procedure called s_InsightPricingUpdate.sql. This stored procedure
takes the accounts from the InsightStaging database and transforms them into Products that fit the
Pricing model. E.g. TermLoan in Staging could become Commercial Loan and Retail Loan in Pricing.
Once the InsightPricing model is setup, the interface s_InsightPricingUpdate.sql must be changed to
reflect the model products. If a product in InsightPricing has three attributes, the interface must setup the
product record with the same three attributes and with valid values that exist for those attributes in
InsightPricing.
NOTE: Every time the attributes and attribute values are changed in InsightPricing, this stored
procedure must be updated.
The following steps are required to import the data during the ETL process in InsightStaging:
1. Run the SQL scripts to load the Pricing model as described in the configuration guide.
2. Add classification and transaction mappings to InsightETL lookup rules
3. Upload the s_InsightPricing_Update stored procedure to the InsightStaging database; customize
it for the Pricing model.
4. Confirm the following has been setup:

 InsightStaging.dbo.S_CustomerProfit_Update
 InsightETL.dbo.AttributeCalculations has 11 entries for Configuration = ‘CustProfit’
 InsightETL.dbo.Indexes has 2 entries for Configuration = ‘CustProfit’
 InsightStaging.dbo.UpdateOrder has 1 Transform.Exec entry for Configuration =
‘CustProfit’
5. Run ETL with S_CustomerProfit_Update enabled in UpdateOrder
6. Review the PricingSource** tables created
7. Review InsightPricing.dbo.view_productRecord
8. Run the QA scripts in the Model Setup to check for load discrepancies
9. Launch the InsightPricing web application to see if the customer and product data was
successfully updated.
10. Add sp_UpdateStats of the InsightPricing database to the nightly ETL job.
Importing from a system other than Insight

If you are not importing from a source system other than Temenos Analytics Insight databases you will
need to do the following:
1. Run the SQL scripts to load the Pricing model as described in the configuration guide.
2. Create the PricingSource interface tables described in the configuration guide, making sure the
products, transactions and service charges are mapped to Pricing values.
3. Customize the s_Case_BankingSystem_AddFromInsightStaging to reference the correct
PricingSource tables.
4. Add the PricingSource table interface and s_case.. update to run in a nightly process.
Authentication Options
By default Insight Pricing is set up to use Windows Authentication. The users will not have to enter a
password when they launch Insight Pricing. The system will grant them access based on their
Domain/Username and their Pricing role setup. If Forms Authentication is used, they will be setup in
Pricing with a username and password and will be prompted for a password when they launch the
application.
For Windows authentication:
By default the web.config is set up for Window Authentication. The users will not have to enter a
password when they launch Insight Pricing. No action is needed if you are using Windows Authentication
and used the Installer.
For Forms authentication:
To configure for Forms Authentication do the following:

 For InsightPricing application change the Authentication to Anonymous Authentication =

‘Enabled’, Forms Authentication = ‘Enabled’, Windows Authentication = ‘Disabled’
 In Default Document, add login.aspx
 For InsightPricingWS application change the Authentication to Anonymous Authentication =

‘Enabled’, Windows Authentication = ‘Disabled’
Error Investigation
This section covers issues resulting from installation setup and data setup.
Blank Screen

There are several issues that will cause the application to show a blank screen when launched.
Run a SQL Server Profiler trace, filtering on the InsightPricing database. If you see any stored procedure
activity, the problem is with the data in the InsightPricing database. Otherwise the problem is with the
Web application/IIS side.
Web Application Issues:
1. Check the IIS logs to see if there are useful error messages. The logs are typically in a directory
called: c:\Inetpub\logs\logfiles\W3sVc1\
2. In IIS Manager confirm that the Web Site is active. Click on the Default Web Site and check the
Manage Website options in the Action pane. They should be Restart and Stop. If it says Start,
the web service is not running and you will have click Start to fix it.
If the Web Site will not start due to another process using the port, use netstat –aon |find “:8081”
to see what process is using the port, then check Task Manager for the PID returned.
3. Run IISReset in a command window.

4. Check that ASP.Net is installed properly.
5. Check to see if there is another app like SharePoint using port 80 and if so you will need to move
Insight Pricing or the other app from port 80. Change all references in the web.config files to
reflect the new port number.
6. Carefully check all passwords in the config files. Make sure InsightDBUser and InsightWSUser
have the correct passwords.
7. Make sure that Reporting Services is running and was setup in Native mode.
8. Check that the database connection string in the App and WS web.config files is correct. You can
try to use username/password using SQL manager to verify if the user has access to
InsightPricing DB)
9. Check that InsightWSUser was setup in the ReportServer
10. Install latest ReportView control by running the ReportViewer.exe from the InsightPricing\V121
directory or downloading it from the Microsoft web site.
11. In IIS Manager, check the providers under Authentication\Windows Authentication. Try changing
the order.
12. In Internet Explorer, launch the web service
http://servername/InsightPricingWS/SimplusWS.asmx. Review any errors generated, otherwise
try running a couple of the operations to see if they work. Check that this URL is setup correctly
in the Web.config in the application settings.
13. Change the security on the Web and App directories to ‘Full Control’ for group ‘Everyone’.
14. Check the Default Web Application settings. In ‘Bindings’ it should be Type:http, HostName: ,
port:80, IP Address:* (Unless you are using an alternate port)
15. In IIS check that InsightPricing and InsightPricingWS are using an AppPool with Managed
Pipeline mode: Integrated, Identity: NetworkService.
Data Issues:
1. Check that the Active Directory user you are using to test with is setup in the
InsightPricing..User_ table. This should have been the user entered during installation. Change
the NTUserName field to match the correct username. Use SQL Profiler to capture the
parameters sent to s_UserIDFromNTLogin_get and s_user_settings_get.
2. Check that there is a DefaultPage in the UserSettings table. It is normally
~/Scenario/CaseList.aspx.

3. Check that the data has products. Query the TargetRates table. If it is empty, you need to refer
to the Configuration guide on how to add data. The installer will have some test data already.
Technical Errors
A technical error page will appear if there is an unexpected data type or value. User SQL Profiler to
capture the stored procedure parameters. Look for a ProductRecord ID so you can query the data. You
can also review the error in the InsightPricing.LogError table.
1. Check for ‘null’ StartDate in the product record using view_ProductRecord. You will need to fix
the data in the source banking system or the interface.
2. Check for ‘null’ BaseRateID and BaseRateModifier where FixVar=’V’ in the product records.
Change the Interface for these, rerun the interface and fix the ProductRecord rows in existing
user created cases.
3. If there is a technical error on case selection on violating non-null, unique, or foreign-key
constraints:
a. Check the scenario table to see if two people created a case in the same minute.
b. In s_cases_get add userid to the rank for finding the last modified scenario
4. If the error message has #FtpDateRange in it, check that the FTP Curve is set to one with dates
in the FTPRate table.
Issues with Popups
If the Popup on the Scenario page is causing runtime errors is blank, try the following:
1. Change your Internet Explorer to run in compatibility mode
2. Run SQL Profiler, and then click on the popup. Copy the SP that is executed on the popup, and try
to run the SP in query analyzer.
3. Check if the XLST file that is associated with that popup exists and is the correct XLST file for the
result set that is returned in the SP
4. Check the UserSettings table for correct values in the Popup1-10 fields.
Home Page Errors

1. Check that InsightWSUser has access to the UserScenarioUsage report.
2. Check that Scenario Usage report is setup in the InsightPricing.Report table and is pointing to the
correct report path and server. The report type must be ‘MetricReport’.
3. Check that the InsightPricing data source in Reporting Services is using InsightDBUser with the
correct password.

4. If the home page settings are corrupted, delete the user’s record from the UserPersonalization
table.
Scenario Print Page
1. Check that InsightWSUser has access to the Scenario03 or Scenario05 report.

2. Check that Scenario report is setup in the InsightPricing.Report table and is pointing to the
correct report path and server. The report type must be ‘PrintPage.
3. Check that the InsightPricing data source in Reporting Services is using InsightDBUser with the
correct password.
4. Check the application pool is configured correctly.
FTP Rate Upload

1. If it fails on an Invalid Directory message, check that the FileUploadDirectory in the App\
Web.Config application settings exists on the Application Server.
2. Check that the number of terms in the upload file matches the number of term defined for FTP
rates. E.g. 27/Feb/2013,1.22,1.25,1.29,1.37,1.23,1.23,1.27,1.37,1.49,1.61 has 10 terms.
Missing or Invalid Customer Products
1. Check the s_InsightPricing_Update interface is creating valid Pricing Products. The products
setup in the Staging interface must match the setup of the products in the Pricing Model. Look
at the attributes and the values to make sure they match valid values in the pricing model. Run
the QA scripts in the InsightPricing_ModelLoad spreadsheet to find product mismatches.
2. Check classification and transaction mappings InsightETL to make sure banking data is mapped
to Pricing values.
3. Check the source banking system data. Often Pricing reveals mapping errors or unexpected null
values in the source banking system.
4. Check that the customer records are there. Product records are deleted if there isn’t an active
customer.
5. Check the InsightPricing.LogDB table to check any issues during the data load.
Slow System Response

1. Run sp_updateStats on the InsightPricing database. Add the sp_UpdateStats to the nightly ETL
run.
2. Check the interface tables for unusually large data fields if the update is having trouble inserting
the product records.
3. Check that the interface (s_InsightPricing_update) and
s_Case_BankingSystem_AddFromInsightStaging is using the ‘Combined’ field to join to the
Product table. If not contact the product team to get the view and stored procedure updates.
Multi-Server Environment
Internal users in the Web.config:

RSUser – Report Server User

 Local user must exist on the server that hosts the reporting services reports with specified
password
 Reports will run using this ID
 This user must have Browser access the InsightPricing folder in Reporting Services
 Check the ReportingServices..execution log to see what user executed the report
 Can be the same as the WSUser if on same server as the application
WSUser – Web Service User

 Local user must exist on the server where the web application is installed
InsightDBUser – Database User

 SQL user for database access
 Must have ‘owner’ privileges of the InsightPricing database
Reporting Services datasource setup:

 InsightPricing datasource is loaded into Insight\Datasources folder
 Connection string points to database server
 Credentials will be the InsightDbUser and Password
Report setup in the application (in the Reports table) or Admin\Client Reports in the application:
 ReportURL: http://reportservername/webserviceURL
 Path for internal report: /insight/insightpricing/User_scenario_usage
 Path for custom report: /Insight/Insightpricing
%2fTarget+Rate+Comparison&rs:Command=Render
If you are prompted for a user name from a remote server, make sure the network setup is allowing the
servers to communicate. For example: A Kerberos setup will require the App pool identity to be added
as a service principal name (SPN). Addition updates to the IIS settings may be required.
Installation without Installer
Only follow these steps if you are unable to use the Installer or if you want to review a particular part of
the installation.
Database Server Setup

1. Restore a provided InsightPricing database using Management Studio or publish from TFS to
create the InsightPricing database. Run scripts to add demo data.
2. Create a SQL server user named [InsightDBUser], choose SQL Server Authentication and
choose a strong [Password]. Remember username and password as they will be required in
setting up the connection string in the WebApp and WebService configuration later on. Uncheck
Enforce Password expiration.
3. Give [InsightDBUser] db_owner database role membership to Insight Pricing Database.
4. Copy the supplied web application files to the appropriate directory on the web server. E.g. C:\
inetput\wwwroot\Insight Application\
5. Update the InsightPricing..User_ table with your Domain\Username in the NTUsername field
for ‘JTemenos’.
6. Add InsightETL, InsightStaging and InsightETL procedures and data as provided.
Reporting Server Setup
1. Create an InsightPricing Reporting Services project or use the one provided.

2. Import the Scenario03.rdl, Scenario05.rdl and User_Scenario_Usage.rdl into the project. (Right
click Reports\Add Existing Item)
3. Under ‘Shared Data Sources’ add InsightPricing, using SQL Server Authentication with
InsightDBUser as the user
4. Point the data source for each report to the InsightPricing shared data source.
5. Deploy the 3 reports and data source to Report Manager ** note: if you don’t have access to
deploy, run Visual Studio as ‘Administrator’
6. Run the ReportViewer.exe to install the report viewer controls
Create Local User
4. Create [InsightWSUser] and [Password] as a local windows user (Computer Management, Local
Users and groups) on the Reporting Server, make sure to check password never expires, and
uncheck user must change password at next logon. Note the password as it is required in a later
step.
5. Give [InsightWSUser] browser rights to the InsightPricing report server folder in Report Manager.
This local windows user is used by the application to access the report server.
Web Server Setup

1. Open IIS Manager
2. Under Application Pools, right click to create a new application pool as:
 Name: InsightPricingAppPool
 .Net Framework version: V2.0
 Managed Pipeline: Integrated
Open Advanced Settings on InsightAppPool and set:
 Identity: Network Service
InsightPricing Application and Web Service will be configured with this application pool.

3. Create the InsightPricingWS application, this is the Insight Pricing Web Service
 Point to the Default Web Site, and right click and select Add Application
 Enter ‘InsightPricingWS’ as alias
 Choose the path where the application/code resides. Choose the WS directory path.
e.g. e:\InsightPricing\WS or c:\InetPub\wwwroot\Insight Application\Insight Pricing\V121\
WS
 Select the InsightPricingAppPool application pool.
 Configure InsightPricingWS properties as follows:
o Click on the InsightPricingWS application Features Views (toggle at bottom of centre
window)
o Double click the Authentication icon and disable Anonymous Authentication,
ASP.NET Impersonation, Forms Authentication. Enable Windows Authentication.
o *** note if Windows Authentication is missing, you will have to enable the
feature in Control Panel/Turn Windows features on-off/IIS/web
services/security
 Edit the web service web.config file (file resides on the root directory of the WS directory)
and configure WhatifConnectionString to point to the Database Server (data source),
database (Initial Catalog) and [InsightDBUser] /[Password] created above.
4. Create the ‘InsightPricing’ application, this is the Insight Pricing Web Application
 Point to the Default Web Site, and right click and select Add Application
 Enter ‘InsightPricing’ as alias
 Choose the path where the application/code resides. Choose the ‘App’ directory. e.g. e:\
InsightPricing\App or c:\InetPub\wwwroot\Insight Application\Insight Pricing\V121\App
 Select the InsightPricingAppPool application pool.
 Configure [InsightPricing] properties
o Click on the InsightPricing application Features Views (toggle at bottom of centre
window)
o Double click the Authentication icon and disable Anonymous Authentication,
ASP.NET Impersonation, Forms Authentication. Enable Windows
Authentication.
 Edit the web application web.config file (file resides on the root directory of the App
directory) and configure the following
 Search for the ‘Add ConnectionString’ line and update the Database Server (data
source), database (Initial Catalog) and [InsightWSUser] /[Password] with the values
created above.
 In the <AppSettings> configure:
 FileUploadDirectory: Directory used when uploading FTPRates

 XLSTDirectory: Directory path to App\XLST
 ImageDirectory: URL to Images
 SimplusWS.SimplusWS: URL to Web service SimplusWS.asmx
 SimplusWebApp: URL for Pricing Application
 RSUser: Local user created above, normally InsightWSUser
 RSPassword: Password that was assigned to the InsightWSUser
 RSDomain: Domain if RSUser is not a local user

 WSUser: Local for web service access – normally same as RSUser

 WSPassword: Password for WSUser
 WSDomain: Domain for WSUser
An example of the Web.Config is show below:
Web Service with Alternate Binding

There are some cases where InsightPricing needs to be set up as a separate web site and/or with an
alternate web site binding. Applications such as SharePoint are know to cause issues when
InsightPricing is also on the Default Web Site.
To create a new web site:
1. In IIS Manager, right click Sites and choose ‘Add Web Site’
2. Give the site a name such as InsightPricing Web Site, and choose the InsightPricingAppPool.
3. Choose a physical path for the website and change the Binding port to a few port.

4. Setup the InsightPricing and InsightPricingWS applications as show above.

5. Change the InsightPricing APP web.config to include the binding for the XLSTDirectory,
SimplusWS.SimpluWS and SimplusWebApp keys in the <appSettings> section.

6. Change any URL’s used to launch InsightPricing to use the alternate binding. Eg.
Http://servername:88/InsightPricing
Uninstall
To remove the application and database from the server do the following:
1. Run the Installer
2. Click on the Remove icon

3. Click the Remove button
5. Click Finish to exit the Installer

Related Documentation
The following documentation is also available:
Customer Profitability Configuration Guide – This guide is used with the ModelLoad spreadsheet to
configure and load the initial model into the Pricing database.
Customer Profitability Calculation Reference – This guide provides details on the FTP and Net Income
calculations done during the profit update.
Customer Profitability Administrators Guide – This guide is provided to users of the system who will be
maintaining the model once the system is live.
Customer Profitability User Guide – This guide is for the ‘What-if’ users of the system for creating cases
and scenarios.

Customer Profitability Installation Guide R18.1

Uploaded by

Copyright:

Available Formats

Customer Profitability Installation Guide R18.1

Uploaded by

Document Information

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

Customer Profitability Installation Guide R18.1

Uploaded by

Copyright:

Available Formats

Temenos Analytics – Customer Profitability

Installation Guide R18

Information in this document is subject to change without notice.

© 2010 Temenos Headquarters SA - all rights reserved.

2 TEMENOS Customer Profitability

Author Version Date

Sylvia McCullough 18.1 07/01/2019

3 TEMENOS Customer Profitability

The Customer Profitability web application requires the following components:

The following illustration shows the Customer Profitability application components:

4 TEMENOS Customer Profitability

Browser  Internet Explorer 11.0 (set in compatibly mode)

 Server name for the Web application

Note: These can all be on the same server

5 TEMENOS Customer Profitability

A log of the installation process is available in the C:\Customer Profitability Installation.log

Running Installer – Single Server

6 TEMENOS Customer Profitability

7 TEMENOS Customer Profitability

5. Click Install to start the installation process.

8 TEMENOS Customer Profitability

7. On completion click ‘Finish’ to end the installation process.

8. Go to the next step to Run Reportviewer.exe

Running Installer – Multi-Server

9 TEMENOS Customer Profitability

2. Choose Database Server on the components selection screen.

10 TEMENOS Customer Profitability

11 TEMENOS Customer Profitability

5. Click Install to start the installation process.

12 TEMENOS Customer Profitability

7. On completion click ‘Finish’ to end the installation process.

Web Application Server

13 TEMENOS Customer Profitability

2. Choose Application Server on the components selection screen.

14 TEMENOS Customer Profitability

4. Click Install to start the installation process.

15 TEMENOS Customer Profitability

6. On completion click ‘Finish’ to end the installation process.

16 TEMENOS Customer Profitability

1. Navigate to C:\inetpub\wwwroot\Insight Application\Insight Pricing\V121

Create Local User

17 TEMENOS Customer Profitability

IIS Manager Example:

Report Server Access for InsightWSUser

18 TEMENOS Customer Profitability

Testing the Install

19 TEMENOS Customer Profitability

Importing Customers and Accounts

Refer to the Customer Profitability Configuration guide for more details.

Importing from InsightStaging

20 TEMENOS Customer Profitability

Importing from a system other than Insight

For Windows authentication:

For Forms authentication:

To configure for Forms Authentication do the following:

21 TEMENOS Customer Profitability

 For InsightPricing application change the Authentication to Anonymous Authentication =

 In Default Document, add login.aspx

 For InsightPricingWS application change the Authentication to Anonymous Authentication =

22 TEMENOS Customer Profitability