Filter
Top Products
A-3
Embedding the WebCommander in the Web Portal
To embed the WebCommander in the Web Portal and allow the use of the
portal’s login and authentication system for accessing the WebCommander
application, the following configurations must be performed:
• Optional. In the WebCommander Web Server application, define the
appropriate Permission to be assigned to the default user and modify the
Default User properties. These properties are inherited by all users that
are automatically created when accessing the WebCommander from the
Web Portal for the first time. For more details, see the WebCommander
Web Server Manager User’s Guide, Chapter 5, “Defining Permissions”
and “Defining a New User”.
• Optional. Enabling the Create private groups for automatically added
users option in the Web Server Manager application, to automatically
create a personal address book for the newly created user. For more
details, see Chapter 5, “New Private Groups” on page 5-51”.
• Creating a database table with authorized users list that is dynamically
updated. This table will be shared by the Web Portal and the
WebCommander.
• Creating the HTTP links from the Web Portal to the appropriate
WebCommander pages.
Creating the CustomerUser Table
The CustomerUser table shared by the Web Portal and the WebCommander
databases must be created with the following fields:
When a new user who is defined in the CustomerUser table accesses the
WebCommander, the parameters are transferred to the WebCommander Users
table, and a the new user is created. The new WebCommander user inherits
the default user permission, and the UID becomes the user PIN code. The PIN
code is used to identify the user in the Optional. WebCommander Users table.
Required Fields
ID
(Internal
Auto
Numbering)
UID
(User
ID)
Name Surname Phone Email CostCenter
(billing
code)
WebCPermission
(A number - Byte
0 = No
1 = Yes)