This is a helper to quickly getting started with Web Port. Here the basic steps that need to be done to create a functioning process picture with dynamic values are described. The chapter is also a guide to the rest of the documentation.
The guide assumes that Web Port has been installed in accordance with chapter Installation.
Also make sure that the Web Port server is started. If not, run Web Port Server from the start menu and make sure the Start button is pressed.
If Web Port has been installed as a service, the program must be run as Administrator (Applies to Windows Vista or later) in order to start the service.
Web Port's control application
Web Port's control application (WebPort Server) allows you to view the status of Web Port, start and stop Web Port both as standalone mode and as a service. Under Archive you can choose whether Web Port should be run as a service or standalone. To install/uninstall the service and start/stop the service, the control application must be run with administrator permissions.
Web Port can, with the help of a command line argument, be indicated to use a specific port or start a project. The following arguments are used for this:
webportserver.exe -port # Where # is port number.
webportserver.exe - project name Where name is the directory name for the project.
Start by opening a web browser or any installed client for Web Port. If the Web Port server is installed on the same computer and the default port 8090 is used, the web server is accessed at http://localhost:8090.
There is only one administrator user at install. This user has full permissions to the system and cannot be deleted. However, it is strongly recommended that the password be changed!
Change the password of the admin user.
In addition to a password, a user can also have a PIN code that can be used when this function is activated for the connection at hand (see chapter "Connections"). This can be used to simplify the login-process when Web Port is installed on a panel PC. However, the administrator account cannot use PIN code.
The menus in Web Port are built around a main menu at the top. This menu changes depending on the level of authorization and the current page. However, the MENU option is always available. If the screen resolution is high enough and settings for hiding the side menu have not been made, the entire MENU will always be displayed on the left. If not, a drop-down menu is displayed instead. From this menu you can navigate between the pages of Web Port. Here, system settings are also accessed if the user has sufficient permissions.
In the menu there is also a search box, which can search for page or folder names. This can be helpful for large installations.
If multiple pages have been visited one after the other, the previous page can be reached using the arrow to the left in the top menu.
If Web Port is installed with default settings, program files are installed to the following directories
C:\Program Files (x86)\WebPort\
Web Port application data is saved under the following directories
C:\Document and Settings\All Users\application data\WebPort\
Windows Vista or later
The data directories in Windows are often hidden. To display these, the setting to show hidden files and folders must be enabled.
The Web Port data directory can always be accessed through the start menu by clicking the Data icon under the Web Port folder.
Web Port projects are saved in the Web Port data directory. By default, an empty project is added directly to the root where the assets, db and system directories contain project-specific data.
Create a new project
A new project is created by creating a new directory of any name directly in the data directory. Then place a copy of the assets, db and systems, in the newly created directory.
After installing Web Port, copy the three project directories (assets, db. system) to a template project that can easily be copied to create new projects.
You select which project Web Port should start by clicking on the existing project (if not changed named default) in the control application which is loaded, and then selecting one from the list. If a project is already running, this must first be stopped.
A project should, if possible, be configured in the same Web Port version which is to be used when going live. Subsequent upgrades should not present a problem, but it is nevertheless a good idea to backup your project before opening it in a new version of Web Port. Configuring the project in a newer version of Web Port than what is to be used is not recommended.
In order to not mistakenly upgrading a project to a newer version of Web Port, the system will warn (if running in stand-alone mode) if the project is opened in another version of Web Port compared to last time. The version history of a project is also saved in the file version.info in the root folder of the project.
The first step in setting up a working Web Port system is to verify a valid license. For information on different types of licenses, (see chapter "Installation").
Set up communication
The second step is to set up communication against current control systems. For information on how communication is set up, first read "Communication", and then the help document for the driver that will be used.
When communication is set up, tags are created to link the naming structure used in Web Port to the technical addresses used for the different control systems. For more information about how tags are created, (read chapter "Tags", and "Symbol library".
To create pages and attach tags to dynamic objects, read chapter "System Pages".
Activate alarm functionality
To activate alarms see chapter "Alarms".
Activate a trend functionality
To activate a trend, see chapter "Trend".
To activate schedules, see chapter "Scheduling".
Users and access permissions
To set up users and access permissions, see chapter "Access management".
For information on advanced settings, see the following chapters:
For information on available system settings, see chapter "System settings".
For information on how components can be collected in groups, see chapter "Collections".
For information on how scripts can be used for automating tasks, see chapter "Scripts".