Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
The Server Information page in the Solutions Manager provides details about the Connected Server and allows you to manage the search locations for solution files, either through directly mapped folders or via a connected server.It also enables you to configure security settings for the Local Computer.manages where solutions are stored and accessed, supporting both local file access and remote server connections for distributed engineering.

Related Topics:

On this page:

Table of Contents
maxLevel3
stylenone



Solutions Location

Access Modes

ModeDescriptionUse CaseLicense
Local Computer FilesDirect file system accessSingle user developmentStandard
Solution ServerNetwork access via TWebServicesMulti-user collaborationEngineering users

Mode Selection

SettingOptionsDefaultNotes
Solutions list built fromLocal/ServerLocalRadio button selection
Auto-refreshOn/OffOffUpdates solution list

Local Computer Files

Local Search Folders

Directories scanned for solution files (.dbsln and .tproj):

OperationFunctionShortcut
Add Search PathInclude new folder+ button
Remove Search PathExclude folder- button
RefreshRescan foldersF5

Folder Properties

Each folder has individual settings:

PropertyDescriptionDefaultImpact
VisibleShow in solution listCheckedLocal display
Allow RemoteEnable network accessUncheckedRemote users can view
Allow Remote RunPermit remote executionUncheckedRemote users can run

Default Locations

FolderPathPurpose
User SolutionsDocuments\FrameworX\SolutionsPersonal projects
Shared SolutionsPublic\Documents\FrameworXTeam projects
TemplatesDocuments\FrameworX\TemplatesSolution templates

Solution Server Connection

Connection Parameters

FieldDescriptionRequiredDefault
ServerIP address or hostnameYeslocalhost
PortTWebServices portYes10108
Access KeySecurity passwordIf configured(none)
TimeoutConnection timeoutNo30 seconds

Common Addresses

AddressDescriptionUse Case
127.0.0.1Local loopbackTesting
localhostLocal machineDevelopment
192.168.x.xLocal networkTeam access
hostname.domainDomain nameEnterprise

Connection Actions

ButtonFunctionStatus Indicator
ConnectEstablish connectionGreen = Connected
UpdateRefresh server infoYellow = Updating
DisconnectClose connectionGray = Disconnected

Connected Server Information

Server Details Display

InformationDescriptionExample
Operating SystemServer OS versionWindows Server 2022
Server URLFull connection stringhttp://192.168.1.100:10108
Server IPNetwork address192.168.1.100
VersionFrameworX version10.2.0.1234
Platform.NET version.NET 8.0

Running Services

ServicePurposeDefault PortStatus
TWebServicesSolution access10108Required
MQTT BrokerMQTT communications1883Optional
HardKeyLicense service10109As needed
OPC UA ServerOPC UA endpoint48030Optional

Service Management

ActionFunctionRequires
Start ServiceLaunch serviceAdmin rights
Stop ServiceHalt serviceAdmin rights
Install as Windows ServiceAuto-start on bootAdmin rights
View LogsCheck service logsRead access

Local Computer Management

Access Key Configuration

Security for remote connections:

FieldDescriptionRequirements
Set AccessKeyDefine password8+ characters recommended
VerifyConfirm passwordMust match
ApplySave settingsRestarts service

?? Warning: Pressing Apply with empty fields removes the AccessKey

Security Settings

SettingDescriptionDefault
Require AccessKeyPassword for remote accessDisabled
Allow Guest AccessPermit anonymous viewingDisabled
SSL/TLSEncrypted connectionsDisabled
IP RestrictionsLimit by IP rangeNone

TWebServices Configuration

Service Requirements

ComponentRequirementCheck Method
Port Available10108 not in usenetstat -an
FirewallPort openWindows Defender
PermissionsRead/write accessFolder properties
LicenseValid runtimeLicense panel

Starting TWebServices

Method 1: From Solution Center

  1. Go to Server Information
  2. In Connected Server section
  3. Select WebService in Add Services
  4. Click Start

Method 2: Manual Start

  1. Navigate to installation folder
  2. Run TWebService.exe
  3. Check system tray icon
  4. Verify port in tooltip

Method 3: Windows Service

  1. Open Services (services.msc)
  2. Find "TWebService-FrameworX"
  3. Start service
  4. Set to Automatic

Service Status Indicators

IndicatorLocationMeaning
Tray IconSystem trayGreen = Running
Services PanelWindows ServicesStatus column
Task ManagerProcesses tabCPU/Memory usage
Server InfoSolution CenterRunning Services list

Multi-User Configuration

Requirements for Collaboration

ComponentServerClient
SoftwareFrameworX installedFrameworX installed
LicenseEngineering users > 1Valid license
ServiceTWebServices runningNetwork access
ConnectionSolution Server modeServer connection

Setup Steps

On Server:

  1. Set Solution Server to http://localhost
  2. Configure folders with Allow Remote
  3. Start TWebServices
  4. Optional: Set AccessKey

On Client:

  1. Select Solution Server mode
  2. Enter server IP:Port
  3. Enter AccessKey if required
  4. Connect

Important Notes

  • Cannot mix local and remote editing of same solution
  • Server must also connect to itself for multi-user
  • Each folder has independent remote permissions

Web Interface Access

Browser URL Format

http://<server>:10108/solutions
http://<server>:10108/solutions?accesskey=<key>
https://<server>:10108/solutions (if SSL enabled)

ClickOnce Support

For Designer launch from browser:

BrowserSupportNotes
EdgeFullRecommended
ChromeWith extensionClickOnce addon
FirefoxLimitedManual launch
SafariNoUse desktop client

Troubleshooting

Connection Issues

ProblemCauseSolution
Can't connectService not runningStart TWebServices
Access deniedWrong AccessKeyVerify password
No solutionsWrong pathCheck folder settings
TimeoutNetwork issueCheck firewall/ports

Service Issues

ProblemCauseSolution
Won't startPort in useChange port or stop conflict
CrashesPermission issueRun as administrator
Not in servicesNot installedInstall as Windows Service

File Access Issues

ProblemCauseSolution
Solutions not visibleNot in search pathAdd folder
Can't saveRead-onlyCheck permissions
Locked filesOpen elsewhereClose other instances

Log Locations

Log TypePathContent
TWebServicesLogs\WebService\Connection logs
AccessLogs\Access\Login attempts
ErrorsTraceLogs\Error details

Best Practices

Folder Organization

  • Separate folders for Dev/Test/Production
  • Use descriptive folder names
  • Set appropriate visibility per folder
  • Regular backup of solution folders

Security

  • Always use AccessKey for production
  • Limit remote access to specific folders
  • Use SSL for sensitive environments
  • Regular license audits

Performance

  • Limit search paths to active folders
  • Regular cleanup of old solutions
  • Monitor service resource usage
  • Optimize network connectivity

See Also

Parent Page:

Related Pages:

AnchorServer WorkspaceServer Workspace

Solutions Location 

The list of solutions presented can include files from your local computer or connecting with a Solution Server running the TWebServices service. If you select Solution Server, you will need to specify the server address and connect to it.

To connect to a solution server, use the IP address and port of the target Solution Server. You may be required to enter an Access Key, which is the password defined on the target server. This configuration is available under Local Computer Management.

Local Computer Files

The Solutions exhibited in the Solution Selector list are the ones set in Local Search Folders when the application starts to run.

If you copy a new Solution (.tproj or .dbsln file) to a folder listed in Local Search Folders, it will not be exhibited in the Solution Selector until you click the Refresh button. To add or remove a folder from the search paths:

  1. Click Find Solutions file.

  2. Click Add Search Path to insert a new path;

  3. Click Remove Search Path to remove a path.

  4. Check Allow Remote Access and Allow Remote Run for multi-user development. (Optional) 

Solution Server

To display the Solution List from a server running the TWebServices, the client computer must be connected to the Solution Server using its IP address and port.

If you have a computer where the solution files are stored and managed, and other computers from which you want to work remotely on those solution files, both computers must have the software platform installed and licensed. The client computer needs to connect to the solution server by using the IP address and port of the computer that stores the solutions. You can also connect to the solution server on your own computer using the IP address 127.0.0.1 and the port where the Solution Server is running. By default, the Solution Server runs on port 10108.

The TWebServices must be running to accept remote connections. See Service Verification for more information.

If using the Embedded Web Service (TWebService) platform, no configuration is required. If using Microsoft IIS web server, see Installing on Microsoft IIS.

Tip
titleSolution Server

When using Distributed Engineering, allowing users from remote computers to access the solution, you need to connect using the Solution Server instead of direct File Access.

Connected Server Information

The Connected Server Information displays details such as the operating system, server URL, server IP, installed versions, and running services. By default, the SolutionServer operates on port 10108 and includes services like Hardkey and WebServices. Additionally, you can configure services (WebServices, MQTT Broker, and Hardkey) to start as Windows services.

Local Computer Management

The Local Computer Management defines an AccessKey to connect securely with the Solution Server hosted on the local computer, adding an extra security layer for remote access. It includes configuration fields for setting and verifying the AccessKey: the "Set AccessKey" field for entering the password and the "Verify" field for re-entering the password to confirm it. The "Apply" button saves the AccessKey settings.

Warning

Pressing "Apply" with any input removes the AccessKey. 

Finding Solutions Folders

After clicking Find Solutions in the Manager Workspace, you will be addressed to the Server Information, which allows to easily set a solution to auto-startup and define if the Solution Selector list will exhibit Solutions from a local or remote computer. 

Solution Server

Field

Description

Solutions list built from

It shows the options below, where user can choose either if the Solution list will be built from local computer files or a server.

Local Computer Files

It sets Solution selector list to be built from the local computer.

Solution Server

It sets a server to build the Solution selector list from.

Connect

It connects to the Solution server set.

Update...

It updates Solution server status.

Server Information

It shows server IPs.

Running Services

It shows current server's running services.

Local Search Folders

Exhibit local folders set to search Solutions and the options below.

Add Search Path (plus)

It adds new local path to search for Solutions.

Remove Search Path (minus)

It removes a local path to search for Solutions.

Visible

It shows the local paths in the Solution List, enabling you to select the solutions in the Manager workspace.

Allow Remote

It enables remote access to the local paths set.

Info

The platform will scan for .dbSln files in the paths set. If the list is empty, check the search paths or the connection with the solution server. Also, try Creating a New Solution. If an error occurs when the Solution is loading, a log is created at "TraceLogs" folder

AnchorFolder Visibility and Remote AccessFolder Visibility and Remote Access

Folder Visibility and Remote Access configuration

Any folder included in Local Search Folders has controls for visibility and remote access.

Permissions for remote access are set by folder, so place your solutions in the folders accordingly. You can keep many solutions in one folder or create a separate folder for each one.

To manage your Solutions Folders:

  1. After adding a search path, select the one you would like to allow remote access.

  2. Check Visible to enable remote access for selected folder.

  3. Check Allow Remote to enable Solutions from selected folder to be run by remote users.

Info
titleMulti-user Development
For information about how to collaborate with other users during the Solution development, please check Multi-user Development.



In this section:

Page Tree
rootV10:@parent
spacesV10