Overview
This page provides details about the Server Information available on the Solution Manager. It includes technical specifics about the Solution Server connection, such as Solution Location, Local Computer Management, Local Search Folders, and Connected Server Information. In the Manager workspace, click on Server Information to manage remote server settings and services.
On this page:
| Table of Contents | ||||
|---|---|---|---|---|
|
Anchor Server Workspace Server Workspace
Solutions Location
The list of solutions presented can include files from your
This page presents how to select search folders to show in the Project Manager Welcome page, and to setup auto-start options.Easy Heading Macro headingIndent 40 navigationTitle On this page selector h2,h3 wrapNavigationText true navigationExpandOption disable-expand-collapse
Server Workspace
Allows to easily define a Project to auto-startup. Defines if the Project List will be built upon projects in the local computer or from a remote computer.
LocalHost: The system scans the Search Folders defined at the Find Project button interface, looking for Project files (.tProj extension)
Remoter: The system will connect to the server specified in the Remote name field, creating the list with the Projects enabled to remote access on that Project Server.
| Info |
|---|
If the list is empty, check the Search paths at the Find button or the connection with the remote Server. Try to Create a New Project. If an error occurs when the project is loading, a log is created at the folder "C:\Users\Public\Documents\TLocalSettings\". |
server. If you select Remote, you will need to specify the server address and connect to it.
To connect to a remote 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 remote server. This configuration is available under Local Computer Management.
Local Computer
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
Finding Projects
The ProjectServer denies if the Projects list is using the Local or Remote computer <<<<. what does ghd ProjectServer deny? or is the ProjectServer denied?>>>>. This configuration is located at the Server tab, and the currently defined ProjectServer is displayed in the bottom left on the Project List page.
This section defines how to find additional project on the Local or Remote computer, according to the ProjectServer Configuration.
On the Local Computer
The project presented are the ones found on the Search Paths field, when the application started to run. The Search Paths can be viewed using the Find Project button.
If you copy a new Project (file with extension tProj) to a folder listed in the Search Paths, it will not be exhibited in the list right away; it is necessary to Solution Selector until you click the Refresh button to refresh the list.In order to Add or Remove . To add or remove a folder from the search Pathspaths:
Click
"Find
Project..." to display a list of existing search paths. If the "Find Project..." button is not visible, check the Project Server configuration and change it to Localhost.- Add or remove paths from the search list
- Define other search criteria below
Finding Projects settings
Field
Description
Current Project Server
Display-only. Shows from which computer the Project List is being queried.
Include Sample Projects
Selected by default. Uncheck to exclude sample projects from the list.
Include Published Projects
Selected by default. Uncheck to exclude published projects from the list.
Find
Click to navigate to a Project. The folder for the project you select is automatically added to the Search Paths list, so all the Projects on that folder will be added to the list.
Search Paths
Add or remove paths from the search list
Allowing Remote Access
Any folder included on Search Paths can be enabled or not for Remote Access.
The permissions for remote users access is by Folder, therefore place your projects on the folders accordingly. You can keep many projects in one folder, or create a folder for each one.
To manage remote access for your projects:
Remote Access Settings
Field
Description
Allow Remote Access
Defines if the projects in the selected path shall be visible to remote users.
Allow Remote Run
Defines if the projects in the selected path can have the execution started by remote users.
Virtual Path
For each search path you enable remote access, an extra layer of security can be added by defining the Virtual Path. That string works as a key that needs to be type by the remote user to access the project in that folder.
If the folder allows remote access and no Virtual Path is defined, any remote user connected with this Server will gain access to query projects from that folder.
| title | ProjectServer Service |
|---|
Solutions file.
Click Add Search Path to insert a new path;
Click Remove Search Path to remove a path.
Check Allow Remote Access and Allow Remote Run for multi-user development. (Optional)
Remote Server
To display the Solution List from a remote server, 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
ProjectServer must be running to accept the remote connections. If using the platform Embedded Web Server (TWebServer), no configuration is required. If using Microsoft IIS web server,
seesee Installing
servicesOn the Remote Computer
When connected with a Remote Computer, the Search Paths and allowing access to the projects shall be executed on the Remote Computer.
On the client side, you can only connect with Server and input the Virtual Path key that define which paths from the remote computer you have access.
The process to check if the remote Server meets all requirements to allow remote access is described in the following section.
Multi-User Collaborative Development
Engineering users can configure the server project by using workstations, which are attached to the network, instead of having to work on the server itself.
To use this feature on all computers connected to the same network, the following configurations are required:
Work Faster
Speed up development by having a developers/engineers team working simultaneously in the same project — no need for merging or importing!
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 | It adds new local path to search for Solutions. |
Remove Search Path | 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 remote server. Also, try Creating a New Solution. If an error occurs when the Solution is loading, a log is created at "TraceLogs" folder |
| Anchor | ||||
|---|---|---|---|---|
|
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:
After adding a search path, select the one you would like to allow remote access.
Check Visible to enable remote access for selected folder.
Check Allow Remote to enable Solutions from selected folder to be run by remote users.
| Info | ||
|---|---|---|
| ||
For information about how to collaborate with other users during the Solution development, please check Multi-user Development. |
In this section:
| Page Tree | ||
|---|---|---|
|
Work Safer
Remote Engineering allows you to have developers utilize a central shared repository and edit a project even when remote (not logged into the project server itself).
As long as the developers are on the same network, they can get to their projects, keeping your server safer by reducing the number of people who need to directly and remotely log into it.
To use this feature on all computers connected to the same network, the following configurations are required:
Server Licensing Verification
Open the Welcome Screen and go to theLicense tab. You should see a square box with information on the license.Under the Engineering Userfield, you will find the amount of concurrent engineering users that are supported by the current license.
Setup the Project Server to Remote:Localhost, instead of Local (Direct local file access, not using Project Server)
A Project cannot be opened for editing on local and remote simultaneously. If this occurs, anyone that remotely connects to the Project will view the project as ReadOnly.
ProjectServer Service Verification
Check if the ProjectServer service is running on both local and remote computers using the procedure described at Service Verification.
In this section...
| Page Tree | ||||
|---|---|---|---|---|
|