IMPORTANT ANNOUNCEMENT regarding Coresuite Installer and Framework version 6.70 or higher

Introduction

We decided to introduce a major change as to how module sips are stored internally.

Traditionally, all sips (standard modules delivered by Coresystems, custom modules and additional modules delivered by our Partners) and licence files are stored in the coresuite database. The coresuite database resides along with your company databases on the same SQL server.

This traditional approach was not suitable for installations on SAP HANA or any onDemand environment (SQL and HANA). For those installations, the tables to store the sips and licence files are created in the actual company databases instead.

Both approaches have their own benefits.

Traditional (SQL onPremise) approach HANA/onDemand (SQL and HANA) approach
- import/install sips once to make them available for all databases on the same server - import/install sips independently in each database on the same server
Benefit Drawback Benefit Drawback


- sip is automatically used in all company databases where the sip is licenced and set to active

- importing/installing only needs to be performed once per server


- forced to use the same sip version across all company databases

- is not possible to test a new sip in a single company database before applying same to other/all databases

- for testing, potentially a copy of the company database needs be moved to a separate server


- sip is only used in the company database where it was imported/installed

- a new sip can easily be tested in selected company databases on the same server without affecting other company databases

- for testing, a backup of the live company database(s) can simply be restored on the same server and a new sip can easily be tested in that company database without affecting other company databases


- depending on the number of company databases, this can be a tedious job

- potentially different company databases end up using different sip versions unintentionally

 

We have harmonised the approach and combined the benefits of both. The means for modules/sips and licences we no longer use the coresuite database but rather create the @SWA_MODULES and @SWA_LICENCES tables in each company Database.

To complete this harmonisation, we have created a new external tool, the Coresuite Administration Assistant (CAA), which gives you the flexibility of installing modules/sips regardless of your environment or database type.

In addition, the structure within the coresuite folder has changed.

OLD (Coresuite Installer version 6.65 and lower) NEW (from Coresuite Installer version 6.70)
SQL onPremise HANA onPremise, HANA onDemand,
SQL onDemand
All Environments


files and folders within the coresuite folder %ProgramFiles(x86)%\SAP\SAP Business One\AddOns\COR\coresuite (%ProgramFiles%\SAP\SAP Business One\Addons\COR\coresuite)Screenshot1.JPG Note, the screenshot only displays a selection of the actual files and folders!


files and folders within the coresuite folder %ProgramFiles(x86)%\SAP\SAP Business One\AddOns\COR\coresuite (%ProgramFiles%\SAP\SAP Business One\Addons\COR\coresuite)Screenshot2.JPG
Note, there is a separate folder for each company created!


files and folders within a company folder %ProgramFiles(x86)%\SAP\SAP Business One\AddOns\COR\coresuite\Company E (%ProgramFiles%\SAP\SAP Business One\Addons\COR\coresuite\Company E) Screenshot3.JPG
Note, the screenshot only displays a selection of the actual files and folders!


files and folders within the coresuite folder %ProgramFiles(x86)%\SAP\SAP Business One\AddOns\COR\coresuite (%ProgramFiles%\SAP\SAP Business One\Addons\COR\coresuite)Screenshot4.JPG
Note, there is a separate folder for each company created!


files and folders within a company folder %ProgramFiles(x86)%\SAP\SAP Business One\AddOns\COR\coresuite\Company E (%ProgramFiles%\SAP\SAP Business One\Addons\COR\coresuite\Company E) Screenshot3.JPG
Note, the screenshot only displays a selection of the actual files and folders!

 

 

warning.png Due to this major change, a special procedure needs to be followed when initially upgrading to Coresuite Framework 6.70 or higher. You cannot simply add Coresuite Framework 6.70 but you will need to replace the Coresuite Installer as described below.

We strongly recommend following the steps below exactly to ensure a smooth and happy transition!

 

Prerequisites

  • Ensure that you have at least 9.2 PL04 installed – previous Patchlevels are NOT supported.
  • When running the OnPremise products on 64-bit SAP Business One Clients Applications, the 32-bit DI-API should also be installed.
  • Verify that your own/custom modules are compatible with the new folder structure. Please check the section "Compatibility with own/custom modules" at the end of this FAQ!
  • Ensure that you have a copy of your own/custom module sips available as those sips will need to be imported again. Please check the section "A) Create a backup your own/custom module sips".
  • Ensure that you have a copy of your coresuite licence file as you will need to import it again. Please check the section "B) Prepare your licence file".

 

Recommended Upgrade Procedure

We recommend to always create a backup of your company and coresuite (SQL only!) databases, export your customize rules and layouts as good practice before performing any upgrade.

 

A) Create a backup your own/custom module sips

    1. Go to the following path
        • SQL onPremise: %ProgramFiles(x86)%\SAP\SAP Business One\AddOns\COR\coresuite (%ProgramFiles%\SAP\SAP Business One\Addons\COR\coresuite)
        • HANA onPremise, HANA onDemand, SQL onDemand: %ProgramFiles(x86)%\SAP\SAP Business One\AddOns\COR\coresuite\Company folder %ProgramFiles%\SAP\SAP Business One\Addons\COR\coresuite\Company folder)
    2. Look for own/custom module sips
    3. Copy the respective sips to a safe location e.g. your Desktop

 

B) Prepare your licence file

As the "Coresuite Administration Assistant" does not facilitate the automatic download of licence files, the following Options are possible:

    1. Download the Licences file from our portal (login is required) and import it later using the Coresuite Administration Assistant.
    2. Use the Licence file that you initially received via Email and import it later using the Coresuite Administration Assistant.
    3. Use our "Coresuite License Exporter" addon to generate the Licence file xml and import it later using the Coresuite Administration Assistant.
      The "Coresuite License Exporter" addon can be download via the following link: Coresuite License Exporter
      NOTE: this is primarily for onPremise environments or onDemand environments where the automatic Licence download is blocked by a firewall and/or proxy settings!
    4. Later use the "Download license" Button in the License management Tab of the Coresuite Administration (this needs to be performed for every single Company Database!)

How to use the "Coresuite License Exporter" addon

SQL onPremise, HANA onPremise:

    1. Install the "Coresuite License Exporter" Lightweight addon and assign it to any database
    2. Start SAP Business One and log on to the database where the addon was assigned
    3. Go to Tools->Coresuite License Export and specify the location where you want the licence xml file saved to

SQL onDemand, HANA onDemand:

Remember that if licences of type onDemand are used, the licence file for each DB is different as it contains the database name. Therefore the following steps might only make sense if you:

  • you want to use the "Coresuite Administration Assistant" to import the licences
  • you cannot automatically download the licences in the traditional fashion via the "Download license" button in the License management tab of the Coresuite Administration
    1. Install the "Coresuite License Exporter" Lightweight addon and assign it to all required databases
    2. Start SAP Business One and log on to the Database where the addon was assigned
    3. Go to Tools->Coresuite License Export and specify the location where you want the licence xml file saved to
    4. Repeat step 2 and step 3 for each required database

 

C) Replacing the Coresuite Installer in an existing SAP Business One installation

warning.png If you are using the 32-bit and 64-bit SAP Business One Client Applications on the same workstation (server), you will need to perform step 1 through to step 5 first via the 64-bit SAP Business One Client Applications, then for the 32-bit SAP Business One Client Applications. Only after you have performed the removal procedure on both Client Applications, you can proceed with step 6!

SQL onPremise

    1. Stop the Coresuite addon (double-check via Taskmanager that NO Coresuite process is still running!)
    2. Remove the Coresuite addon via Administration->Add-Ons->Add-On Administration=>"Remove Add-On"
    3. Restart SAP Business One via right-click->Run as Administrator to complete the uninstall process
    4. Verify the Coresuite application is fully removed from your SAP Business One Client application
      warning.png Check %ProgramFiles(x86)%\SAP\SAP Business One\AddOns\ (%ProgramFiles%\SAP\SAP Business One\Addons\) for remaining COR and/or coresuite folders; should they still exists, please delete them.
    5. Delete coresuite database, unless you are using the SAP FSM solution; having the coresuite database still present will not cause the Coresuite Addon to malfunction - once SAP also creates their tables in the company databases, the coresuite database should be completely removed
    6. Download the respective Coresuite Installer for your SAP Business One version from our download area, register and install it.
    7. Start the Coresuite addon
    8. Close SAP Business One
    9. Use the Coresuite Administration Assistant to
        • download and install the latest available versions of each module as well as your own/custom modules;
        • add your licence file(s)
    10. You can still download and install the latest available versions of each module sip traditionally via Administration->Add-ons->coresuite administration->Administration->Sip Management but remember, you would need to repeat this for every company database separately!

HANA onPremise

    1. Stop the Coresuite addon (double-check via Taskmanager that NO Coresuite process is still running!)
    2. Remove the Coresuite addon via Administration->Add-Ons->Add-On Administration=>"Remove Add-On"
    3. Restart SAP Business One via right-click->Run as Administrator to complete the uninstall process
    4. Verify the Coresuite application is fully removed from your SAP Business One Client application
      warning.png Check %ProgramFiles(x86)%\SAP\SAP Business One\AddOns\ (%ProgramFiles%\SAP\SAP Business One\Addons\) for remaining COR and/or coresuite folders; should they still exists, please delete them.
    5. Remove the @SWA_MODULES and @SWA_LICENCES tables via Tools->Customisation Tools->User-Defined Table - Setup;
      This needs to be repeated for every single company database!
      warning.png DO NOT try to drop those tables via HANA Studio or SQL Management Studio as this will cause database inconsistencies! Should you forget to remove either table in a company database, you will get the following message when starting the addon.
    6. Download the respective Coresuite Installer for your SAP Business One version from our download area, register and install it.
    7. Start the Coresuite addon
    8. Close SAP Business One
    9. Use the Coresuite Administration Assistant to
        • download and install the latest available versions of each module as well as your own/custom modules;
        • add your licence file(s)
    10. You can still download and install the latest available versions of each module sip traditionally via Administration->Add-ons->coresuite administration->Administration->Sip Management but remember, you would need to repeat this for every company database separately!

HANA onDemand, SQL onDemand

    1. Stop the coresuite addon (double-check via Taskmanager that NO coresuite process is still running!)
    2. Remove the coresuite addon via the Cloud Control Center
    3. Restart SAP Business One via right-click->Run as Administrator to complete the uninstall process
    4. Verify the Coresuite application is fully removed from your SAP Business One Client application
      warning.png Check %ProgramFiles(x86)%\SAP\SAP Business One\AddOns\ (%ProgramFiles%\SAP\SAP Business One\Addons\) for remaining COR and/or coresuite folders; should they still exists, please delete them.
    5. Remove the @SWA_MODULES and @SWA_LICENCES tables via Tools->Customisation Tools->User-Defined Table - Setup;
      This needs to be repeated for every single company database!
      warning.png DO NOT try to drop those tables via HANA Studio or SQL Management Studio as this will cause database inconsistencies! Should you forget to remove either table in a company database, you will get the following message when starting the addon.
    6. Download the respective Coresuite Installer for your SAP Business One version from our download area, register and install it.
    7. Start the Coresuite addon
    8. Close SAP Business One
    9. Use the Coresuite Administration Assistant to
        • download and install the latest available versions of each module as well as your own/custom modules;
        • add your licence file(s)
    10. You can still download and install the latest available versions of each module sip traditionally via Administration->Add-ons->coresuite administration->Administration->Sip Management but remember, you would need to repeat this for every company database separately!

 

D) Using the Coresuite Installer in a new SAP Business One installation

There is no special procedure to be followed. Download the respective Coresuite Installer for your SAP Business One version from our download area, register and install it.
Use the Coresuite Administration Assistant to

  • download and install the latest available versions of each module as well as your own/custom modules;
  • add your licence file(s)

You can still download and install the latest available versions of each module sip traditionally via Administration->Add-ons->coresuite administration->Administration->Sip Management but remember, you would need to repeat this for every company database separately!

 

E) General points to remember

  • Uninstalling the addon will have no impact on your current settings (e.g. your layouts and customize rules).
  • On Terminal Servers, please remember to switch to install mode, before attempting to install the addon.
  • Please note that if you do not follow the above procedure step by step, the addon will not work.
  • Whereas we strongly recommend using the new Coresuite Administration Assistant to download and install sips, you can still continue with the traditional approach.
  • After replacing the Coresuite Installer as described above, each SAP Business One Client application on each workstation will need to be started once via right-click run as Administrator, so the Installer can be automatically replaced in each SAP Business One Client application. The uninstall and the new install will run automatically.

 

Compatibility with own/custom modules

Though we do not expect any issues, we recommend that you check your own/custom modules in your test environment before performing the upgrade in your production environments.

As long as you use the Global.BaseDirectory property from the Coresuite Framework, the files and folders from your own/custom module sip are unpacked correctly within the new folder structure. In case you have hard coded your own paths, you might need to review this based on the details provided about the new folder structure.

Was this article helpful?
2 out of 2 found this helpful
Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.