From time to time, a Portal may need to be manually installed. To ensure successful Portal operation after a manual install, verify that the settings described below are applied to any manual installation.

Installation Instructions

From time to time, a Portal may need to be manually installed. Here are the steps to create a Portal website manually:

  1. Proceed with the Portal website installer normally. At the “Choose Components” step, un-check “Configure IIS Website” and complete the installation.

    This step is the same for all Portals and the B1WebAPI.

    Alternatively, you may manually copy web files into the desired folder.

  2. Create the website in IIS. To do this:
    • In IIS, right-click on Sites and select Add Website…
      Right-click on Sites - select Add Website...
      Right-click on Sites - select Add Website...
    • Fill in website details (Site name, Physical Path and Port). Note the default port and folder settings for each Portal in the table below.
      Fill in website details for your manual installation.
      Fill in website details for your manual installation.
      Application Default Folder Path Default Port
      B1WebAPI C:/Program Files (x86)/zedIT/zed B1WebAPI/ 4033
      Customer Portal C:/inetpub/wwwroot/zed Customer Portal/ 4035
      Employee Portal C:/Program Files (x86)/zedIT/zed Employee Portal/ 4035
      Vendor Portal C:/Program Files (x86)/zedIT/zed Vendor Portal/ 4038
      Workflow Portal C:/Program Files (x86)/zedIT/zed Workflow Portal/ 4036
  3. Configure the application pool, as shown in the screenshots below, taking note of the marked fields.
    Right-click on the application pool and open Advanced Settings.
    Right-click on the application pool and open Advanced Settings.
    Application Pool settings for Portal websites. Make sure to set the marked fields as shown. Note: Marker 5 shows Max Worker Processes for any Portal (1 worker process). B1WebAPI should have 2 worker processes.
    Application Pool settings for Portal websites. Make sure to set the marked fields as shown. Note: Marker 5 shows Max Worker Processes for any Portal (1 worker process). B1WebAPI should have 2 worker processes.
  4. If you copied the web files manually, update the web config so it points to the correct B1WebAPI details. To do this, open the website’s web.config file and update the b1clientenabler section to use the correct B1WebAPI host, username and password.
    <b1ClientEnabler
     enablerHost="http://localhost:4033"
     enablerDomain=""
     enablerUserName="b1webapi"
     enablerPassword="mySecurePassword"
     changePasswordPageURI="~/ChangePassword.aspx"
     loginPageURI="~/login/Login.aspx"
     defaultPageURI="~/index.aspx" />
    
  5. Assign Directory Security Configuration.

    Using the IIS Application Pool “Identity”, ensure the appropriate write permissions are assigned to the application folders. Typically (but not always) this is NETWORK SERVICE. See each Portal’s installation guide for detailed steps. A quick reference is shown below.

    Directory Security for B1WebAPI

    In addition to core B1WebAPI folders, two special folders require write permissions. All folders are listed below.

    Folder Description
    The configured B1WebAPI Temp Directory As configured in the Server Tools B1 Config section.

    This is used to “stage” files that need to be uploaded into B1’s attachments directory.
    The SAP Business One Attachments directory Write permissions are required on this folder when using attachments features such as Customer Portal Service Calls (with attachments), Employee Portal Sales User, or Employee Portal Expense User.
    /app_data/ This folder is used to store application data.
    /logs/ This folder is used for logging and file permissions must be set so that logs may be updated.

    Directory Security for Employee Portal

    A list of the folders for Employee Portal and each folder’s purpose is found below.

    Folder Description
    /app_data/ This folder is used to store application data. The directory /app_data/Expense/ is created as part of the install and has its ACL (Access Control List) setup to allow the .NET worker process to read, write and delete files in this directory.
    /customerdata/ This folder is used to save temporary web-only saved order drafts. Once the order is placed, it is deleted from this sub-folder and added as a full order in SAP Business One.
    /logs/ This folder is used for logging and file permissions must be set so that logs may be updated.
    /orderdata/ This folder is used to save temporary web-only saved order drafts. Once the order is placed, it is deleted from this sub-folder and added as a full order in SAP Business One.
    /signatures/ Versions 92.5 through 92.7 only.

    This folder is used for signature attachments related to Delivery Signature Capture for Sales User.

    Directory Security for Customer Portal

    A list of the folders for Customer Portal and each folder’s purpose is found below.

    Folder Description
    /app_data/ This folder is used to store application data.
    /customerData/ This folder is used to save temporary web-only saved order drafts. Once the order is placed, it is deleted from this sub-folder and added as a full order in SAP Business One.
    /logs/ This folder is used for logging and file permissions must be set so that logs may be updated.
    /uploads/ This folder is used to upload attachments related to Service Calls.

    Directory Security for Vendor Portal

    A list of the folders for Vendor Portal and each folder’s purpose is found below.

    Folder Description
    /app_data/ This folder is used to store application data.
    /logs/ This folder is used for logging and file permissions must be set so that logs may be updated.

    Directory Security for WorkFlow Portal

    A list of the folders for WorkFlow Portal and each folder’s purpose is found below.

    Folder Description
    /logs/ This folder is used for logging and file permissions must be set so that logs may be updated.
    /service/ This folder contains the WorkFlow service executable and configuration files. This must be accessible to the user assigned to the workflow service so the service can be run.
    /service/logs/ This folder is used for WorkFlow service logging. File permissions must be set so that logs may be updated by the user assigned to the workflow service..
    /service/xml/ This folder and sub-folders contain workflow definition files and must be read/write accessible to the user assigned to the workflow service.
  6. Apply application-specific and feature-specific settings:
  7. Browse the website to verify that the Portal is running properly. If not, see our Portal Troubleshooting Guide for common install errors and their resolutions.

What’s Next?

and Logging has been configured