Appendix SAP NW SDK Files download - 24.1

Automate Evolve Installation
Product type
Software
Portfolio
Integrate
Product family
Automate
Product
Automate > Automate Evolve
Version
24.1
Language
English
Product name
Automate Evolve
Title
Automate Evolve Installation
Copyright
2024
First publish date
2018
Last edition
2024-07-22
Last publish date
2024-07-22T13:01:12.334902

The following sections contains the steps to download SAP NW SDK Files when these files are not present in c:\windows\system32\ path.

  1. Go to https://launchpad.support.sap.com/

    Prerequisites- User should have valid S-User ID and can access the https://launchpad.support.sap.com/ also user should be able to download the sap content from SAP portal.

  2. In downloads, Search for “sap nw rfc”
  3. Click on SAP NW RFC SDK 7.50
  4. After downloading the zip files, open the nwrfcsdk > Lib folder and copy the below files.
    • sapnwrfc.dll
    • icudt50.dll
    • icuin50.dll
    • icuuc50.dll
  5. Place the copied files into below Destination Folder.

    Path: c:\windows\system32\

    Installer Improvements

    Improvement Skip generating the temporary log file during installation and provide a command to generate in on-demand

    As part of improvement, we have skipped generating this temp log file(default behavior) and have provided a switch/command to generate it on-demand, whenever we need to debug/trouble-shoot any customer installation issue. Below command can be used create temp.log in temp directory in case of all installation types i.e. fresh,modify,repair,upgrade and is applicable only using command line.

Installer_Name.exe/v"CREATE_TEMP_LOG=yes"

Digital Signing of all powershell scripts used inside installers

We have implemented automatic signing of all the PowerShell scripts during the build process.

Pre-requisite checks functionality change

As part of improvementthe default nature of Pre-requisite checks has been changed to failed icon (earlier which was success) . As incase if any failure happens while checking any prerequisite it should be showing failure icon in that.

Encryption changes for Evolve Installer in Web.config

Password in SQL connection string for key FinxDB, FinxReportingDB is now being stored in encrypted form in web.config file. This behavior is applicable for all installation types i.e. fresh,modify,repair,upgrade.

Change in System Requirements URLs to generic ones

Old url links have been changed to new precisely ones as below.

Azure Active Directory-Password Mode Authentication Support in Installers

For Azure SQL managed Instances we are now also supporting Azure Active Directory-Password Mode in authentication.For Application database setup the AAD User must have DB creator and Security admin roles.

Incase Installer account does not have Dbcreator and SecurityAdmin role

If Installer account does not have Dbcreator and SecurityAdmin role then also, Evolve can be installed by executing below queries for the login account.This is applicable for all authentication types supported by installer that is windows,SQL and AAD.

GRANT ALTER ANY LOGIN TO [LoginName] WITH GRANT OPTION;

GRANT CREATE ANY DATABASE TO [LoginName] WITH GRANT OPTION;

Here LoginName is the name of the user required for Installer Authentication.

Security Admin Check removal in Upgrade installation

We have removed Security Admin checks for Installer account user for Upgrade installation.

With new implementation these are the challenges which can be encountered and are as below :-

  • In case user migrates database from one database server to another database server and performs upgrade directly (without running the modify installer feature) then now as we have removed security admin check so login creation and permission for App pool user on database will not be granted automatically in case login/role is not present after migration. Earlier we were making sure in our pre-requisites to have security admin role for Upgrade.

Workaround :

In this scenario the installer account user should have Security admin and dbowner privileges so that after migration login creation and permission for App pool user will be granted automatically by installer else any security admin user can manually perform all these tasks.

  • In case user upgrades to this or above release from old one and if in case there is any change in App pool user and permission in database since fresh installation so in that case login creation and permission for App pool user on database will not be granted automatically in case security admin role is not present for installer account user. Earlier we were making sure in our pre-requisites to have security admin role and we use to reconfigure or create login and permission for App pool user in case of Upgrade.

    Workaround :

    We need to make sure in case of upgrade the users , Installer account user permissions and roles on the SQL server database should be kept intact or the installer account user should have Security admin so login creation and permission for App pool user can be reconfigured or created.

Multiple WFEs fresh installation

In case of existing Multiple WFE different AppPool users setup, user should provide any one of the existing App pool user while adding new WFE to the setup.

NOTE: It is recommended to use same App pool user for all the WFEs.