Versions Compared

Old Version 10

changes.mady.by.user admin

Saved on

compared with

New Version 11

changes.mady.by.user admin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
The Server Information page 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
maxLevel2
minLevel2
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:


In this section:

Page Tree
rootV10:@parent
spacesV10