A NEW TODAY IS DAWNING!

TB0009 - Configuring a BuildPro Server on Windows Server/XP/VISTA

Number: TB0009

Availability: As of BuildPro 8.00, Windows Server/XP/VISTA.


Summary

The following guide explains how to configure BuildProfessional to run as a server under the Microsoft Windows environment. This allows BuildPro Windows Clients (thin clients) to connect to applications running on Windows (Server). The BuildPro Server for Windows currently only support 50 concurrent user sessions.
 

Requirements / Prerequisites

Ensure you have the latest release of BuildProfessional for the Windows environment. For remote access from a different PC you will need to install the BuildProfessional Windows Client. 
 

Instructions

The current release of BuildProfessional Server requires that certain manual installation procedures be performed for the server to operate correctly.

  1. Install BuildProfessional Server.
    The following are the main steps in installing the BuildPro server. steps where you just say yes or next have been omitted:

    a. Download the latest version of BuildPro Server (named BPServer.exe) from the ftp server and save it on your hard drive.

    b. Close any other programs you have running, and double click BPServer.exe.

    c. Select BuildPro Server Installation and press next.

    d. Enter license info including the activation code in the format XXXX-XXXX-XXXX/XXXXXXXX for all three sections. If you do not enter the information here you will have to later manually brand every file. See section 9.

    e. Enter company information and press next.

    f. Select the directory you wish to install it into and press next. Make sure there are no spaces in the directory name. e.g.: default dir: c:\BuildPro. Do NOT use C:\BuildPro

    g. Select the program folder name, e.g. Build Pro Server.
     

  2. If BuildPro has been installed previously you may get some warning messages saying that some extensions have already been registered, and it will ask you whether to override this. Say YES to all of them.

    a. Download the latest version of BuildPro Client (named BPClient.exe) from the ftp server and save it on your hard drive.

    b. Close any other programs you have running, and double click BPClient.exe.

    c. Select the directory you wish to install it into and press next. Make sure there are no spaces in the directory name. e.g.: default dir: c:\BuildProClient. Do NOT use c:\Build Pro Client. It should be a different directory to where the server is installed.

    d. Select the program folder name, e.g. Build Pro Client.

    e. If BuildPro has been installed previously you may get a warning message saying that .BPC extension has already been registered, and it will ask you whether to override this. Say YES.

    f. Then it will say complete and give you the option to reboot by selecting the box. It is not essential to reboot unless dll's have been updated or you require auto startup of port mapper and session manager but is recommended. If you do not reboot see sections 4 and 10.

    g. Install the BuildProfessional Client on the server if you wish. This is not essential.
    The following are the main steps in installing the BuildPro client. steps where you just say yes or next have been omitted:
     

  3. Edit nimconf.ini in your BuildPro\bin directory (on the server):
    Configure the Logfile and Trace preferences according to your needs. e.g.:
    LogFile=C:\BuildPro\bin\sessout.txt
    Add the line
    TraceMode=0,9
     
  4. Ensure PortMapper and SessionManager are running. To check run:
    C:\BuildPro\bin\rpcinfo -p
    This will produce a window listing three entries, two identified as portmapper, a third as SessionManager. If portmapper is not running, start it from ControlPanel/Services.
    Also check that sessmgr.exe and smpoker.exe are running in the Windows NT task list under processes (smpoker is started automatically by sessmgr). If not, start Session Manager from ControlPanel / Services.
    #
     
  5. The basics of networking must also be installed and functioning correctly. E.g.:
    TCP/IP
    DNS (optional, but requires forward and reverse lookups)
    DHCP (optional)
     
  6. Ensure a system environment variable TMP is set appropriately (ControlPanel / System / Environment). This will be used for temporary SessionManager files.
     
  7. When a BuildPro Client has been installed along with the server you will have to configure the "UseLocalPortmapper" settings in the wintoday.ini file. If not the default settings are correct.
    - on the client in C:\BuildProClient\bin_net directory change to:
    UseLocalPortmapper=true
     
  8. If the licensing failed during the install brand sessmgr.exe, smpoker.exe, portmapper.exe, wintdyx.exe and wintdyxs.exe binaries. To check if a binary is branded use:
    C:\BuildPro\bin\brandv3 -a <exefile> -r
    To brand a binary use:
    C:\BuildPro\bin\brandv3 -a <exefile> -b <base lic> -e <ext lic>
     
  9. If you did not reboot or had troubles with portmapper or session manager they can be installed as follows:
    a. Install the Portmapper as a service using the following command:
    C:\BuildPro\bin\portmapper -i
    b. Install the Session Manager as a service using the following command:
    C:\BuildPro\bin\sessmgr -i
    Check that it is installed as a service from ControlPanel/Services. Ensure that "interact with the desktop" is enabled under "Startup..." options.