Known servers can be organized from Window->Preferences->Variant Management->Known Servers in pure::variants. Known servers are used by many connectors. This page provides an organized view and actions for servers of the corresponding connectors. The known server table has following components.
Each existing connectors are represented as categories. Categories have unique ID and name. It is possible to see the ID by hoovering mouse pointer on any category.
Servers are shown under each corresponding connector categories. Each server has a name and an URL. More information of the server can be viewed through tooltip.
The following actions can be performed on the list.
Add: The Add button only enables when a category is selected. To add a server, select any connector category, then clickAdd . A dialog box will open, enter server name in Name text box and server URL in URL text box. PressOK to add the server into the category.
If the server fails to connect, a Save anyway dialog will open if user want to keep it.
Edit: The Edit button enables if any server is selected. A server name or URL can be modified by clicking Edit button. A dialog box pops up where changes can be made.
Remove: To remove a server from any category, select it from the list and pressRemove button.
Password: Password change is only available for servers which are in pure::variants Model Server category. To change the password of such server, pressPassword button.
Import: Servers from a external XML file can be added to their corresponding categories. UseImport button to perform an import. The import XML has to have the similar structure as central deployment XML.
An example is shown in Central deployment XML structure
The predefined XML file with categorized servers can be stored in file named "pv.servers.xml" on "C:\ProgramData\pure-variants-5" directory for central deployment of servers with user's choices of category/categories. An example XML is shown in Central deployment XML structure .
These servers can not be edited by the user and will be shown in
their corresponding
connector categories with "lock" (
) decorated icons. For example, a pure::variant model server from
central deployment
file would look like (
).
Category IDs are mandatory for central deployment XML. pure::variants connectors of corresponding server categories are using category IDs with the following schema: We take the feature ID of the connector and replace "pure-variants" with "servercategory".
Example: For connector with ID com.ps.consul.eclipse.pure-variants.toolxyz the category ID com.ps.consul.eclipse.servercategory.toolxyz is used.
There are some categories which do not follow this schema:
User can have proposal for pure::variants Floating License server in
-> -> -> -> by adding a License category server in the central deployment file. The pure::variants Floating License Server category is not shown in Known Servers preference page but can be used from central deployment file.
Table 6.8. Table of server category IDs
Server Category Name | Server Catagory ID |
---|---|
pure::variants Model Server | com.ps.consul.pvserver.model |
pure::variants Floating License Server | com.ps.consul.pvserver.license |
Uncategorized Server | com.ps.consul.pvserver.unknown.category |
The structure of the central deployment server xml file is:
<?xml version="1.0" encoding="UTF-8"?> <servers> <server name="Name of the server 1" description="Description of the server 1" category="ID of the category" url="URL of the server 1" /> <server name="Name of the server 2" description="Description of the server 2" category="ID of the category" url="URL of the server 2" /> ... </servers>
Name, category and url are mandatory. The description is optional.
<?xml version="1.0" encoding="UTF-8"?> <servers> <server name="PV Model Server" description="This is an example server" category="com.ps.consul.pvserver.model" url="http://127.0.0.1:4711" /> <server name="Another Model Server" category="com.ps.consul.pvserver.model" url="http://model.server.local:8080" /> </servers>
Eclipse restart is required to reflect the modification of central deployment file.