Concento 4.0 Upgrade Guide
Concento 4.0 Upgrade Guide
0 UPGRADE GUIDE
JUNE 25, 2021
pg. 1
TABLE OF CONTENTS
I. INTRODUCTION ..................................................................................................................................... 3
II. PREREQUISITES ..................................................................................................................................... 3
III. UPGRADE STEPS .................................................................................................................................... 4
STEP 1 – Rename the original C:\Publish folder OR Delete it from the drive ........................................... 4
STEP 2 - Run Concento Webpage Installer Program ................................................................................. 5
STEP 3 - Confirm Webpage Creation in IIS .............................................................................................. 10
STEP 4 – Continue Process through Installer program ........................................................................... 11
STEP 5 – Db Connection Info ................................................................................................................... 12
STEP 6 – Comparison Checks .................................................................................................................. 13
STEP 7 – How-To-Upgrade ...................................................................................................................... 14
STEP 8 – Validate the web applications are accessible ........................................................................... 16
STEP 9 – Close the Concento Webpage Installer Program ..................................................................... 17
STEP 10 – Apply License to Concento Deploy ......................................................................................... 18
STEP 11 – Configuring Concento Parameters ......................................................................................... 20
STEP 12 – UNINSTALL the Concento Scheduler ...................................................................................... 23
IV. INSTALL CONCENTO SYSTEM SEARCH ............................................................................................ 23
V. INCORPORATE USE OF DMR PUBLIC API............................................................................................. 25
VI. WINDOWS AUTHENTICATION LOGON ACCESS............................................................................... 26
Role Management for Windows Authentication .................................................................................... 27
Concento Parameters for Windows Authentication ............................................................................... 28
VII. ENRICH SPREADSHEET WEB ADD-IN ............................................................................................... 29
pg. 2
I. INTRODUCTION
NOTE: This process can be used to upgrade any previous releases starting with our 2.00.04 release.
The Concento Deploy2 Application provides ability to update the database to the latest version without
the tech lead needing to run a complex series of database scripts. The assumption is that you have full
access to the Publish zip file.
The Deploy2 web application must first be installed. (follow the Installation Guide).
Every Step in this guide is valuable, so do not skip any steps and complete all steps prior to setting the
new system live.
As of 3.2 version is the merging of CONCENTO and DEPLOY2 databases in SQLSERVER. In this version,
we will only use the DEPLOY2 database. There will be no need to access the AdminUI as a separate URL
as all the data has been moved into the DEPLOY2 database. The core database may be named as any
name, but will default as CONCENTO
This update will allow for multiple installations of Concento Systems in one server.
II. PREREQUISITES
pg. 3
The additional use of 4.0 version Enrichment Templates will require a few prerequisites:
• This release or greater of Microsoft Excel must be loaded on the laptops and desktops:
Microsoft Excel 2013 version 15.0.4981.1000 and patch Excel2013-kb3191823 (or Greater)
https://support.microsoft.com/en-us/help/3191823/april-4-
2017-update-for-excel-2013-kb3191823
• Enrich will not work on MAC OS because MAC OS does not support VBA code. It must be run
on a PC or run using Microsoft Windows running on an Apple product.
STEP 1 – Rename the original C:\Publish folder OR Delete it from the drive
Unzip the Upgrade file contents into a new C:\Publish folder as shown below:
• Documents related to this upgrade including New Features, Release Notes, Upgrade guide and
the Hardware Requirements guide
• Database Upgrade shortcut (used to open the upgrade web application)
• DEPLOY2 MAPPING TEMPLATE.xlsx (manual mapping template)
pg. 4
• Installer.exe (web screen program to check and install windows batch file)
• Launch windows batch files for Concento AdminUI and Deploy (opens the web apps)
• License Key Collection PDF (Document to request license renewal)
• Run Installer.exe program – Double click on the file name to initiate the on-screen process to
initiate the Welcome screen with current Version noted at header.
• Click Next to continue
**NOTE – User may choose to retain the webpage installation files upon exit by a click to deselect
“Delete installation files on exit?” at bottom of this window.
• Extracting files (runs quickly) – this will extract into a temporary folder the files required to
install. The temporary folder will automatically delete at end of install unless the user deselects
the message.
• Click on Next to Verify System Status and Prerequisites
pg. 5
• This step will verify that setup is prepared for the install.
pg. 6
• Enter Server Address, Custom Instance (if applies), Custom Port (if applies), Username, and
Password. The Database Name for the core application database is a required field (EX:
CONCENTO or DEPLOY).
• Most projects will want to use Windows Authentication and so the new check box is defaulted
to active. However, uncheck this box if Windows Authentication is not needed as it will update
the IIS settings to make the system require it.
Click on Verify Connection button - If successful, the screen will respond with all GREEN checked
connections.
If the version is already installed on the system, this warning message will display. Click on Yes to
continue.
NOTE: The Installer program will not install an older version, however, you can install a newer version
or the same version (this benefits validation of the current setup).
pg. 7
Next, click on Upgrade (version) button (or Reinstall button if same version) to run the Install.bat file and
complete this process. The system will display a message to click Yes if you want to start the installation
process.
NOTE: This action will update the databases within the IIS to the NEW version. Also, if the 4.0.0 version
has not yet been installed, you will see an Upgrade to 4.0.0 button.
Update the field Database Name to reflect the current base database for Concento being actively used.
pg. 8
The Installer will continue to process and if successful, a message will display that the process is
complete. Click on Next button to proceed or Red X to close the program.
pg. 9
**NOTE: Keep the Installer program active at this point.
Ensure that the Server and the Default Web Site are both running.
Note: Make sure that the IIS is started – click on the Start icon right side under Manage Website.
pg. 10
STEP 4 – Continue Process through Installer program
Return to the Installer.exe Program and click on the Next button. This will initiate the Update Database
segment of the Installer. Once the Upgrade has been completed, you may close this program by a click
on the Finish Button.
The Installer.exe will open the web page for Concento Deploy DB Upgrade.
NOTE: Alternately, you may manually open this browser by navigating to the page -
https://localhost/ConcentoSuite/Deploy2Service/DbUpgrade/
In this case, the localhost will remain as is and will direct to correct web app
pg. 11
STEP 5 – Db Connection Info
Validate that the server name is correct, and that the Connection Status is “Success.”
Check to ensure that the “Installed Db Version” matches the CURRENTLY installed version on the server.
pg. 12
STEP 6 – Comparison Checks
Click on the link “Compare” to open a page that will compare for differences between the current
database and the new upgrade version. Ideally, there should be no differences.
If there are differences in routines (triggers/views/etc.) the corrections should be accounted for prior to
the upgrade. Make sure to account for any missing tables or columns, or columns that are defined
differently than they should be. The Compare page:
pg. 13
Back out to the primary Concento Deploy Db Upgrade screen.
STEP 7 – How-To-Upgrade
NOTE: Backup the current database
The final step is the upgrade. By default, the scripting will be encrypted via the installation process.
pg. 14
To run the generate encrypted, click on Generate an upgrade plan link to generate an upgrade plan
for the existing database. The page shows all the steps that the upgrade process plans to run on the
database.
Once the contents of the upgrade plan have been verified, enter the User’s Database Password into
the text box and click the Execute Upgrade button.
NOTE: For situations where an alternative upgrade plan is required – one sent from the Developer
team, the User would upload that plan into build the scripts by a click on the ‘here’ link.
pg. 15
Within a short while a screen will display that will indicate SUCCESS/FAILURE and will provide a detailed
report of the steps taken.
Should any of the upgrade steps fail, the log will provide information indicating which step failed, and
notes to address the issue. In the case of failure, the process will roll the state of the database back to
the beginning of the process.
An alternate should the rollback not completely reverse would be to copy the backup version to live and
start the process again. Therefore, the backup is an important step.
NOTE: In the event that some of the SQL scripts in the upgrade process need to be altered, the
Execution screen may be updated. Click the “Edit” link for any of the steps. Alter the script as needed or
as directed by DMR Customer Support and then click the “Save” button.
Once the desired changes are complete, enter the User Database Password to the “Password for
Database User ‘Concento’:” field and click on the “Execute Upgrade” button.
pg. 16
STEP 9 – Close the Concento Webpage Installer Program
Return to the open window of Concento Webpage Installer Program and click on the Finish button to
close.
Once the Upgrade web page is closed and completed, you will be able to initiate closure on this
program. Click Yes to proceed to the system checks.
The Installer program will now validate that system configuration and setup are complete. The
messages in RED will need to be corrected.
The checks include validation of the application version against the database version for consistency;
validation that each of the core database can be accessed using the Concento default logon ID; and
validation that the Security and Deploy Web services are active and accessible.
pg. 17
STEP 10 – Apply License to Concento Deploy
Installer must contact to DMR Product Support to receive a License Key. The following information is
necessary:
• Client Name
• Project Name
• Client Contact Name and Email
• Technical Contact Name and Email
• Database Server Name and (optional) Instance (see below)
• Environment (DEV, QA, PROD, LOAD, Migration, Control, etc)
• Notes, if needed, to identify this Instance in the future or help with future Licenses.
• Expiration Date (based on the Project SOW)
As of Concento version 3.3 - Licensing will support Multiple Servers, or the Server named in the config
files
• SQL Server Database is using High Availability groups, so the physical database may be different
than the registered Database Name, and it may switch periodically. Allowing multiple DB
pg. 18
Servers will cover all these scenarios by allowing users to register either one or more Physical
Servers or license the Registered Server.
• Multi-Server Landscape - In cases where we are licensing an INSTANCE of Concento, we can
register all servers (DEV, QA, PROD) in a single License Key which could be applied to all
environments in an instance.
• Ease of Registrations - By showing the DB Server on the license screen, Admins in a new
installation can easily see what DB Name the server is expecting.
This is all relevant to create the license. The License is added within Concento Menu path Administer >
Security > License Details
Enter License Details and then Choose the license file and then click on UPLOAD button to read the file
and update the system. Once successfully added the license details fields will be auto populated.
NOTE: When asking for license for multiple servers, identify each in this manner – Pipe between each
server: myserverA|myserverB
instance: instA|instB
IF the db Server is not correct, this is the error message that will present when applying the license.
**NOTE: The Development team may need to add the Instance onto the end of the server name as well
as in the Instance for a successful license to apply.
If the license is applied, it will display message that License was applied successfully.
NOTE: The Admin User – Concento must have the password changed from the DMR Default to
something unique PRIOR to update of the License. If not, the License section will not display, and an
ERROR message will take its place on the screen as shown below.
pg. 19
License Details: Default Password requires change
To resolve, click on the link provided in the ERROR message or use pathway – Administer > Setup > User
Management to Edit the Concento User and change the default password.
pg. 20
Administer: Parameters Setup
Select from drop down these options for SQLSERVER, HANADB, or ORACLE.
Setup Working DB Type*
Required
This is the Govern only datasource for Reporting Cache (Default: REPORT
Setup Govern Cache Datasource
always)
Setup ETL Tool* Select the correct ETL tool for loading. (Default: SAP Data Services) Required
number of days of log history to keep online. Set this value per IT department
Setup Log Retain Days*
auditing and service level agreement (SLA) . Required
This sets the level of detail included in the Debug Log table. (Default: Info)
Setup Debug Level*
Required
Freely definable prefix that will be placed on the Deploy generated fields.
Methodology Field Prefix*
(Default: z) Required
Freely definable prefix that will be placed on the key fields of tables. (Default:
Methodology Key Prefix*
zLegacy) Required
Freely definable prefix that will be placed on the Xref fields of a table. (Default:
Methodology Xref Prefix*
to zXref) Required
After importing data elements, this will set them all to Active or Not Active
Methodology Default Elements Active
(Default: OFF)
Methodology Create Export Dataflow This will create the Export Dataflow for SAP Data Services (Default: On)
This sets how many threads will be allocated to Low Priority jobs. (Default: 3)
Job Queue Low Priority Threads*
Required
This sets how many threads will be allocated to High Priority jobs. (Default: 3)
Job Queue High Priority Threads*
Required
pg. 21
Excel Export Max Record Max number of records to export into an Excel spreadsheet (otherwise use CSV
Report Export
Count* format) Required
Excel Export Max Cell Max number of cells to export into an Excel spreadsheet (otherwise use CSV
Report Export
Count* format) Required
Commit ID Commit ID GUID for unique identifier for this set of Parameters
SMTP Settings SMTP User Name * Enter the email address for SMTP User. Required
SMTP Settings SMTP Password* Enter the Password for the SMTP User
SMTP Settings SMTP Port* Enter the Port number for this email service
SMTP Settings From Address Enter the sent from address for this service
SMTP Settings Secure Socket Select from options the secure socket (Default 3 – StartTls)
pg. 22
STEP 12 – UNINSTALL the Concento Scheduler
Projects upgrading to 4.0 from a previous version of Concento (before 2.05), will need to UNINSTALL the
old Concento Scheduler from the server, and delete the C:\Program Files(x86)\DMR folder.
The Scheduler is not internal to Concento and does not require this additional program any longer.
Concento system will provide a system search capability once two programs are executed and
installed.
• Java-1.8.0-openjdk-1.8.0.212-3.b04….
• Elasticsearch-6.6.1.msi
pg. 23
Both programs must be opened and installed to setup the Search Configuration – if on same server.
Within Concento use pathway Administer > Search Configuration update – Leave defaults as it and click
on Search Enabled and Save. Then, log in and log out to get search icon to display.
NOTE: While making considerations for the hard drive space consider that using the SEARCH features
will require approximately 25% more hard drive space than the Concento application. When the disk
reaches 95% full, the Search system will go into a READ-ONLY mode and will not continue to update
based upon changes to the Concento data. Refer to Hardware Requirements Guide for more details of
sizing.
NOTE: The program will move 5k items into the search every 5min, so it takes a bit to load up.
The column Left to Refresh refers to the number of things to update – if you make a change to things in
Concento, it might take a bit for that change to show in the search because it runs every 5 min. Runs in
the background.
More details of use for this screen are described in the online Concento Help guide.
pg. 24
V. INCORPORATE USE OF DMR PUBLIC API
The Concento Public API is a RESTful service that lives within the Concento Suite. It provides a collection
of HTTP interfaces into the data that is used by Concento, using the Open API standard. We have
chosen to use a .Net based library from swagger.io in order to implement the Open API standard.
As much as possible, DMR has attempted to make objects exposed by the API semantically descriptive.
This means that developers consuming the API should be able to derive the purpose and
implementation details of a given object simply by observing it.
As part of the install, the Public API will now be available for use. Users will be able to enter a link using
their client server and the address below.
https://ClientServer/ConcentoSuite/PublicApi/swagger
Refer to user guide – Public API User Guide for details of the use of this product.
pg. 25
VI. WINDOWS AUTHENTICATION LOGON ACCESS
Concento provides a single sign on for Users at project sites. The project site will generally use a
Network system with logon. As part of the setup of IIS, we instruct to select Windows
Authentication by default. If you can setup the IIS or have ability to advise the IT department to
ensure that this selected.
NOTE: The User may select as an option to install with Anonymous Authentication when needed.
pg. 26
Within the section for IIS double-click on Authentication (highlighted above) to display the details.
The proper settings will show Anonymous Authentication Disabled while Windows Authentication
will be Enabled.
pg. 27
also have associated Applications, Roles, and User Alias. Click on the Add icon to open a
window for User Alias. Enter the Alias Name with the Network ID and username as it is stored in the
client network. Click on Save icon to complete this process.
The resulting User access will now allow for single sign on to Concento as part of the overall process.
pg. 28
VII. ENRICH SPREADSHEET WEB ADD-IN
As of Concento v3.3 - The Enrich spreadsheet is now working with a Microsoft Web Add-in and not
built from VB scripting. This will result in better performance that allows for MAC OS and a more agile
system.
NOTE: Microsoft Office product must be for Windows Server 2016 at least version 10.0.14393 Build
14393 or later (OS is Windows 10 > = version 1903), and for Mac 16.24 or later (ExcelApi 1.9) May 2019
or newer
There should be a check that all systems are closed during this install. User will download Manifest and
then save to the client shared server. Each user will then download the web add-in from Concento
pathway – Migrate > File Management as detailed within the wiki notes in Concento.
Success!
You have now upgraded and configured Concento application. The system is now ready for the
application teams!
pg. 29