Vision33 Server Tools allows for configuration of B1WebAPI connection settings, licensing and meta-data installation.

Starting Vision33 Server Tools

To start Vision33 Server Tools:

  1. Log onto the server where Vision33 Server Tools is installed. Typically this is the SAP Business One license server.
  2. Run Vision33 Server Tools as Admin. To do this, go to Windows Start menu: Start > All Programs > zedIT Solutions > B1WebAPI > zedSuite Server Tools and right-click on the menu option to select Run as Administrator…

    Administrator mode grants Vision33 Server Tools access to configuration files that are usually write-protected when not running as an admin.

    Run Vision33 Server Tools as Admin from the start menu.
    Run Vision33 Server Tools as Admin from the start menu.
  3. If you’ve previously started Server Tools, it will continue to run in the task bar (see marker 1 in the screenshot below) until explicitly exited. In this case, double-click on the icon for Vision33 Server Tools to open the Server Tools window.

    Vision33 Server Tools runs in the task bar by default. Double-click the icon (1) to open the dialogue.
    Vision33 Server Tools runs in the task bar by default. Double-click the icon (1) to open the dialogue.
    Vision33 Server Tools dialogue. Use the B1 Config button to edit B1WebAPI details. Use the Licenses button to manage licensing.
    Vision33 Server Tools dialogue. Use the B1 Config button to edit B1WebAPI details. Use the Licenses button to manage licensing.

Using Vision33 Server Tools

Create or update B1WebAPI profiles.
Create or update B1WebAPI profiles.
Install or update customized metadata.
Install or update customized metadata.
Manage licenses and install/update standard product metadata.
Manage licenses and install/update standard product metadata.

Creating or Updating B1WebAPI Profiles (B1 Config)

B1WebAPI profiles are used to maintain connection details to SAP Business One companies. Each profile connects to one SAP Business One company, but multiple profiles can be configured within the “B1 Config” section of Vision33 Server Tools.

B1WebAPI connection configuration screen. Edit connection details for one or more SAP Business One companies. Press Save when complete.
B1WebAPI connection configuration screen. Edit connection details for one or more SAP Business One companies. Press Save when complete.
Defines which B1WebAPI config file will be loaded and updated.
Defines which B1WebAPI config file will be loaded and updated.
Configure B1WebAPI Settings - Config File
FieldDescription
Config File

Typically, this is not edited. This field is used to define where connection details are saved for the B1WebAPI.

The only reason to change this value is when you require multiple versions of B1WebAPI installed on the same system. This is not recommended, speak with your Vision33 consultant if you require this type of advanced setup.

Defines settings for connecting to SAP Business One database and licensing servers
Defines settings for connecting to SAP Business One database and licensing servers
Configure B1WebAPI Settings - B1WebAPI SAP Settings
FieldDescription
DB Server

Database settings used by the B1WebAPI to connect to the SAP Business One database.

In the case of Hana, this is the Linux-based Hana server connection settings.

DB Username
DB Password
License Server

This defines the connection to the SAP Business One License Server.

Defines credentials used to connect into B1WebAPI.
Defines credentials used to connect into B1WebAPI.
Configure B1WebAPI Settings - B1WebAPI IIS Settings
FieldDescription
Host

This sets the default web address for the B1WebAPI. A different address may be set during IIS config, so ensure the same address is set in both places. If a difference exists, the IIS settings will determine where the website runs.

Username

Use this field to define the B1WebAPI user which will be used by all portals to connect to the B1WebAPI. Good security practice is to choose a meaningful username that is not obvious (for example, B1WebAPIUser instead of just simply User.

This field is case sensitive.

Password

Use this field to define the B1WebAPI password which will be used by all portals to connect into the B1WebAPI. Good security practice is to choose a long password.

This field is case sensitive.

Defines company-specific connection details.
Defines company-specific connection details.
Configure B1WebAPI Settings - Business One Profiles
FieldDescription
Profiles navigation (bottom left-hand pane)

This section determines which profile is the default. The first profile will be used by connections that don't specify a profile. The profile with the name "Default" will only be the default profile if it's at the top of the profiles list.

Use the right-hand buttons to move profiles up or down the list.

Name

Profile name, which will be used by portals to connect into the B1WebAPI company defined in that profile.

For example "production" could be used to define connection details for a live B1 company, while "test" could be used to define connection details for a testing/development B1 company.

Company DB

This is the SQL Database name, not the SAP Business One company name.

For example, "SBODemoUS" is the database, while "OEC Computers" is the company name.

DB User

Typically these credentials are for the same DB User assigned to the SAP Business One company configuration in the section above. It's used to permit database access via the DI-API.

DB Password
B1 User Name

This defines the B1 user credentials that will be assigned to the B1WebAPI. This may be an indirect user.

B1 Password
Attachments Dir

This defines the B1 attachments directory, as set in the B1 company settings. This is used for importing Expense User attachments into B1 purchase orders.

Enable Advanced Options

This section is used to define advanced setup options for Interconnect, including Hana installations.

Hana workflow settings

See Hana Settings section below.

Activate workflows for Interconnect

If checked, this permits this profile to use the Interconnect Workflow Service.

These settings are related to file paths for attachments, temporary files, etc.
These settings are related to file paths for attachments, temporary files, etc.

This section typically remains unedited, as most installations of SAP Business One rely on the same file paths. The Attachments Directory field is the only detail you must configure for every installation.

These settings are specific to Hana implementations. Do not configure for SQL Server installations.
These settings are specific to Hana implementations. Do not configure for SQL Server installations.
Configure B1WebAPI Settings - Hana Settings
FieldDescription
Hana Implementation

Hana only Enable this option if you are currently connecting to a Hana database. This section defines your Portal licensing, and Interconnect Workflow settings.

SQL Express Server

These settings define SQL Express connection details that are used to store Portal Licensing and Interconnect workflow information.

Express User Name
Express Password
Hana workflow settings - Database Name Override

This option may be enabled to allow you to manually name the Interconnect workflow database. By default, this database name matches the Company DB name, plus \_zic.

Hana workflow settings - Database

This setting is only enabled if the Database Name Override setting is enabled.

Updating changed passwords

If the database server password or SAP Business One password have changed, each password must be updated in every applicable profile. For example, if multiple companies all use the same SQL user, then all profiles DB Password must be updated.

In addition to profiles, the B1WebAPI SAP Settings section (on the upper-left) should also be updated if the SQL password has changed.

Installing MetaData

MetaData can be updated or added to SAP Business One using the MetaData button of Vision33 Server Tools.

Load custom MetaData from the MetaData screen, as described below.
Load custom MetaData from the MetaData screen, as described below.

To load MetaData:

  1. Select a profile from the Company drop-down.
  2. Browse to the custom MetaData folder. Note that the MetaData package must include a ConfigXML folder which contains the actual MetaData files.
  3. Confirm the file path.
  4. Overwrite existing queries, if desired. The selected MetaData package can optionally overwrite existing versions of the same MetaData (for example, default portal queries can overwrite customized versions).
  5. Import the MetaData using the Import button.
  6. Review system messages for updates to the metadata install status.

Managing Licenses

Licenses can be managed from Vision33 Server Tools for both application licenses and per-user licenses.

See Applying Product Licenses for a walkthrough.

Manage licenses using the Licenses screen, as described below.
Manage licenses using the Licenses screen, as described below.

Referring to the screenshot above, see the following description for each of the license Administration screen functions:

  1. Select a company profile. This will load that profile’s assigned licenses.
  2. Select license type, if using a development license. Production is the default.
  3. If configured, Select a user when applying per-user license modules.
  4. Assign the desired per-user licenses.
  5. Assign per-application licenses. This may prompt for metadata installation. When applying metadata, this will disrupt B1 usage for a few moments, so ensure this is scheduled ahead of time.
  6. Create a license request if new products or licenses must be added.
  7. Import License File to load a new or updated license.

Applying Licenses

There are two license types Per-Application and Per-User.

Per-Application licenses enable a product for use, and ensure that product’s core metadata is installed.

Per-User licenses can be assigned to configured users, and enable specific functionality for the assigned user only.

Manage licenses using the Licenses screen, as described below.
Manage licenses using the Licenses screen, as described below.

To update Per-application licenses:

  1. Select the company profile from the Company drop-down (marker 1 above). If the license is for development, select this from the Development/Production drop-down (marker 2 above)
  2. Enable product licenses in the Per-application Modules section. To do this, place a check-mark in the “Used” column for applications (marker 5 above). This will assign one Available license to the selected company profile.

    If applicable, a prompt will appear asking if it is okay to install MetaData. In this case, SAP Business One usage will be temporarily disrupted while the relevant MetaData is installed.

    Sample MetaData is also provided for Employee Portal. This provides additional sample roles, menu options and queries that would otherwise not be installed. These are not required for any feature functionality and may be ignored if desired.

  3. Once the per-application licenses have been applied, the number of available licenses will be decreased.

To update Per-user licenses:

  1. Configure a user in SAP Business One, otherwise they will not be available for licensing.
  2. Restart Vision33 Server Tools if you have added any new users. The user list must be refreshed if you make changes, which requires Vision33 Server Tools to be restarted.
  3. Select the configured user from the Active Users section.
  4. Apply licenses to selected user by placing a check-mark in the Used column of the Per-user License Modules section (marker 4 above). Repeat for each user that should be licensed for that module.
  5. Once a per-user license has been applied, the total number of Available per-user licenses will be decreased.