Vision33 offers an array of Portals that allow access to SAP Business One for different user audiences. Each Portal has its own website, but uses common infrastructure to connect to a specific SAP Business One company database. Details of infrastructure requirements and software prerequisites are outlined below.

Confirm infrastructure

For a detailed outline of possible configurations, see Infrastructure Architecture. The configurations below describe the most common server arrangement.

Hana Infrastructure Example (Portals and Interconnect)

Hana Infrastructure Example - Portals with or without Interconnect.
Hana Infrastructure Example - Portals with or without Interconnect.

Hana Infrastructure Example (Interconnect only)

Hana Infrastructure Example - Interconnect (no Portals).
Hana Infrastructure Example - Interconnect (no Portals).

Hana Component Summary

Summary of Hana architecture components.
Summary of Hana architecture components.

SQL Infrastructure Example (Portals and Interconnect)

SQL Infrastructure Example - Portals with or without Interconnect.
SQL Infrastructure Example - Portals with or without Interconnect.

SQL Infrastructure Example (Interconnect only)

SQL Infrastructure Example - Interconnect (no Portals).
SQL Infrastructure Example - Interconnect (no Portals).

SQL Component Summary

Summary of SQL architecture components.
Summary of SQL architecture components.

Detailed examples for SQL and Hana are shown in Infrastructure Architecture.

Before Installing a Portal

  • Identify the web server where the Portal website(s) will be installed.
  • Identify the SAP Business One server and Hana Application Server (if applicable) where B1WebAPI and Vision33 Server Tools will be installed.

  • Ensure Typical Hardware and Software Requirements are met.
  • Ensure full administrative rights are assigned to the user who will be installing the software.
  • Create a back-up of all SAP Business One databases prior to installing new products.
  • Carefully review this Implementation Guide prior to performing the installation and basic configuration.
  • Download the latest version of the Portal package.

Review Hardware and Software Recommendations

Typical Hardware/Software Requirements

  • End User (Customer)
    Hardware

    A typical home computer, at minimum:

    • 512 MB RAM
    • 100Mb Network
    • 5GB hard drive space available
    • 1GHz processor
    Software

    A standard web browser, such as:

    • Internet Explorer (11 or higher)
    • Mozilla Firefox
    • Google Chrome
    • Apple Safari
  • Firewall
    Hardware

    Network usage minimums are below. Consider improved bandwidth if high volumes of web traffic are involved.

    • 1.5 Mb down
    • 1 Mb up
    Software
    • Network Address Translation
    • Able to alert and report an outage
    • Capable of creating DMZ
  • Web Server Requirements
    Hardware Minimums

    Below are the minimum requirements. Consider improved hardware if high volumes of web traffic or large numbers of B1 users are involved.

    • 4 GB RAM
    • 2GHz Dual Core processor
    • 100 GB hard drive
    • 100 Mb Network
    Software
    • Windows Server (32-bit or 64-bit) Enterprise, Standard or Web Edition. See Release Notes for supported versions. Ensure all stable security patches have been applied.

    • IIS including IIS6 Compatibility Modules (See: How to Configure IIS)

    • ASP.Net 4.0 (or higher). Note: on Windows 2008, ASP.Net 4.5 (or higher) is required for Employee Portal installations.
    • The web server must have access to the B1WebAPI instance.
  • SAP Business One Server Requirements
    (SQL Server version only)
    Hardware

    Speak with your SAP Business One consultant.

    Software
    • Windows Server (32-bit or 64-bit) Enterprise, Standard or Web Edition. See Release Notes for supported versions. Ensure all stable security patches have been applied.

    • Microsoft SQL Server, Enterprise or Standard Edition. See Release Notes for supported versions.

    • IIS including IIS6 Compatibility Modules (See: How to Configure IIS)

    • ASP.Net 4.0 (or higher)
    • SAP Business One Server 9.2 (If performing a standard installation)

    • SAP Business One Client 9.2 with DI-API. Requires both 32-bit and 64-bit DI-API versions if on a 64-bit machine.
  • Hana Database Server Requirements
    (Hana version only)
    Hardware/Software

    Speak with your SAP Business One consultant.

  • Application Server Requirements
    (Hana version only)
    Hardware Minimums

    Speak with your SAP Business One consultant to confirm these details also cover other third-party application requirements.

    • 4-8 GB RAM
    • 2GHz Dual Core processor
    • 100 GB hard drive
    • 100 Mb Network
    Software
    • Windows Server Datacenter, Enterprise, Standard or Web Edition. See Release Notes for supported versions. Ensure all stable security patches have been applied.

    • Microsoft SQL Server, 64-bit Express Edition or 64-bit Standard Edition. See Release Notes for supported versions.

    • IIS including IIS6 Compatibility Modules (See: How to Configure IIS)

    • ASP.Net 4.0 (or higher)
    • SAP Business One 9.2. Requires both 32-bit and 64-bit versions of:
      • B1 Client
      • Hana Client
      • DI-API
    • ODBC Hana drivers installed.

Infrastructure Cheat Sheets

Common configurations are summarized below. Refer to details above for specific versions.

Server Cheat Sheet

(See version details noted above)

Hana B1 Database Customer Portal Employee Portal Vendor Portal Interconnect SPS Cloud EDI
Hana Database Server
(Linux)
required required required required required
Application and Product Database Server
(Windows)
required required required required required
Web Server*
(Windows)
required required required not-required not-required
SQL B1 Database Customer Portal Employee Portal Vendor Portal Interconnect SPS Cloud EDI
Hana Database Server
(Linux)
not-required not-required not-required not-required not-required
Application and B1/Product Database Server
(Windows)
required required required required required
Web Server*
(Windows)
required required required not-required not-required
  • *Web Server must be distinct from the Application/Product DB server

Component Cheat Sheet

(See version details noted above)

App Server Web Server
(if applicable)
SQL Server required not-required
.Net required required
IIS required required
DI-API - 32-bit required not-required
DI-API - 64-bit required not-required

Download the Latest Version

http://www.zedsuite.com/downloads-customers.aspx contains the latest download packages.

To download installation files, a username and password are required. Contact support (support@vision33.com) for access.

The latest version of the Portal installation package is displayed in the top section and is labelled zedSuite Portals installation files for the appropriate version of SAP Business One. To download the installation files, click on the link and enter the username/password information when prompted.

Upgrades

Components for each Portal

Customer Portal

Required Components:

  • B1WebAPI
  • Vision33 Server Tools
  • Manager Add-On
  • Customer Portal website

Employee Portal

Required Components:

  • B1WebAPI
  • Vision33 Server Tools
  • Manager Add-On
  • Employee Portal website

Vendor Portal

Required Components:

  • B1WebAPI
  • Vision33 Server Tools
  • Manager Add-On
  • Vendor Portal website

Interconnect

Required Components:

  • B1WebAPI
  • Vision33 Server Tools
  • Manager Add-On
  • Workflow Portal

Component Upgrade Chart

The following upgrade chart shows which components need to be upgraded between versions. All components for versions prior to Service Pack 4 for B1 9.1 (version 91.4) require upgrade.

Portal Upgrade Version Chart - Required   - Recommended   - None
SP4
(B1 9.1)
SP0
(B1 9.2)
SP1
(B1 9.2)
SP5
(B1 9.2)
B1WebAPI Upgrade Required No upgrade required No upgrade required Upgrade Recommended
Vision33 Server Tools Upgrade Required No upgrade required No upgrade required No upgrade required
Vision33 Server Tools (Meta-data only) Upgrade Required No upgrade required Upgrade Required Upgrade Required
Customer Portal Upgrade Required No upgrade required Upgrade Required Upgrade Required
Employee Portal Upgrade Required No upgrade required Upgrade Recommended Upgrade Required
Vendor Portal Upgrade Required No upgrade required No upgrade required No upgrade required
Workflow Portal Upgrade Required No upgrade required No upgrade required No upgrade required

Upgrading B1WebAPI (All Products)

Not every version requires an upgrade of B1WebAPI. Review the upgrade chart above to determine if this is required for your upgrade.

Before upgrading B1WebAPI, make a backup of any customizations. Also, make a backup of the configuration file, typically C:/Program Files (x86)/zedIT/zed B1WebAPI/bin/b1enabler.config.

To safely back up these files, save them into another folder (such as C:/backups/) so they are not deleted or overwritten by the installer during the upgrade.

Confirm data migration tasks before beginning an upgrade. Certain versions require special data handling. Speak with your Vision33 consultant for more details.

Upgrading Vision33 Server Tools (All Products)

Not every portal upgrade requires an upgrade of Vision33 Server Tools. Otherwise, there are no special instructions for upgrading this component.

Review the upgrade chart above to determine if this is required for your upgrade.

Upgrading the Manager Add-On (All Products)

Every upgrade from one Service Pack to another requires an upgrade of the Manager Add-On.

Before upgrading the Manager Add-On, backup any custom configuration settings, such as payment settings, welcome messages, menus, etc. To do this, open each config screen found under zedSuite Manager > Administration, and take a screenshot or copy/paste any field that is too long for a screenshot. Save this information in case updates to the add-on overwrite this.

Specifically, upgrading from version 5 or 6 to version 7+ will delete Payment Gateway configuration and Order Pad configuration. Pay extra attention to payment gateway settings before performing an upgrade from versions 5 or 6.

Menus have changed as of Service Pack 2 for B1 9.2 (version 92.2). Ensure all menus are migrated properly after an upgrade.

Upgrading Customer Portal Website

  • Back up the Manager Add-On settings. Be sure to perform backups of any Customer Portal settings found in the Manager Add-On for SAP Business One.

    Specifically, Payment Options must be backed up when upgrading from version 7 or lower. Payment settings were changed in later versions. This requires a complete re-configuration of this setting.

  • Back up custom web files. Any file found outside of the Customer Portal folder /customs/ may be deleted during a website upgrade. If customizations are found outside of that folder, copy customized files into another location to back them up.
  • Merge customizations over a new installation. When upgrading web files, recommended best practice is to install the standard Customer Portal web files in a new location, then merge in custom/updated files from the old version. This avoids certain odd behavior due to caching and deprecated files. These types of display issues may be resolved manually if they occur on a system that was upgraded instead of merged.
  • Identify multi-language upgrade tasks. Multi-language support has changed. If you are upgrading a version of Customer Portal that already includes multi-language support, please contact your Vision33 consultant to ensure this is migrated to the new multi-language format.

Upgrading Employee Portal Website

  • Back up the Manager Add-On settings. Be sure to perform backups of any Employee Portal settings found in the Manager Add-On for SAP Business One. Note that as of version 92.5, settings have changed considerably.
  • Back up custom web files. Any file found outside of the Employee Portal /customs/ folder may be deleted during a website upgrade. If customizations are found outside of that folder, copy customized files into another location to back them up.
  • Merge customizations over a new installation. When upgrading web files, recommended best practice is to install the standard Employee Portal web files in a new location, then merge in custom/updated files from the old version. This avoids certain odd behavior due to caching and deprecated files. These types of display issues may be resolved manually if they occur on a system that was upgraded instead of merged.

    Also ensure to copy any signature image files found in the website’s /signatures/ folder. This will ensure web users can continue to view older signature capture.

Sales User Upgrades for versions 91.2 and lower

An upgrade from a version prior to SP2 for B1 9.1 will require special attention related to Sales User. These steps must be completed whether or not Sales User was active prior to the upgrade.

The following steps must be completed whenever an upgrade is applied and Sales User will be used, whether or not Sales User was used in the old version.

If upgrade of Employee Portal was completed in-place instead of as a side-by-side install with merge, ensure that you rename (or delete) the old Sales User folder salesuser to ensure these files do not conflict with new sales user. If customizations were applied to the old sales user, these will need to be migrated to the new Sales User format.

After base Employee Portal has been upgraded, perform the following tasks:

Sales User Upgrade pre-91.2 - Modify Menus

This will remove deprecated menu entries and update other entries for the newer

  1. Remove the following menu entries completely. To do this, in B1, go to zedSuite Manager > Manage My Menus > Employee Portal. These menu entries are no longer valid:
    • Sales User/Sales Pipeline (deprecated)
    • Sales User/Activities in the last 30 days (deprecated)
    • Sales User/Sales Order Analysis (this report is a duplicate of Sales Reports - Order Analysis)
  2. Update the “My Opportunities” menu entry to point to /salesuser/board instead of the old opportunities screen. See screenshot below.

    Update the My Opportunities link to point to the new opportunity board, as shown.
    Update the My Opportunities link to point to the new opportunity board, as shown.
  3. Update any custom report links and golden arrow drill-downs which point to old Sales User links. For example, customer detail drill-downs on a customized customer report will need to point to the new sales user customer details page.
Sales User Upgrade pre-91.2 - Assess the need for customizations

After an upgrade to the latest version, new Sales User features may be available out-of-the-box that once required customization. Assess the new Sales User features to see if further customization is required. In this case, you may create new customizations.

Note that the old sales user and its customizations may be activated, however this will not be supported via the normal product support. Speak with your Vision33 consultant if this is your preferred option.

Upgrading Vendor Portal Website

  • Back up the Manager Add-On Settings. Prior to upgrade, perform backups of any Vendor Portal settings found in the Manager Add-On for SAP Business One.

  • Back up custom web files. Any file found outside of the Vendor Portal /customs/ folder may be deleted during a website upgrade. If customizations are found outside of that folder, copy customized files into another location to back them up.

  • Merge customizations over a new installation. When upgrading web files, recommended best practice is to install the standard Vendor Portal web files in a new location, then merge in custom/updated files from the old version. This avoids certain odd behavior due to caching and deprecated files. These types of display issues may be resolved manually if they occur on a system that was upgraded instead of merged.

Upgrading Interconnect workflows

Interconnect projects are fully customized and require extra attention to avoid loss of functionality and settings during an upgrade. Speak with your Vision33 consultant before performing an upgrade.

When upgrading from version 93.0 or lower, the following manual updates must be applied prior to upgrade:

  • Remove Workflow message hooks from the SBO_SP_TransactionNotification stored procedure. Prior to upgrade, all Workflow message hooks must be removed from the SBO_SP_TransactionNotification stored procedure and inserted in the SBO_SP_PostTransactionNotice stored procedure.

  • Insert the Workflow message hooks in the SBO_SP_PostTransactionNotice stored procedure. The Workflow message hooks removed from SBO_SP_TransactionNotification must be inserted into SBO_SP_PostTransactionNotice.

Relocating Workflow message hooks ensures that Workflow messages will be created after validation is completed.