Menu, toolbar and Icons of SCTS DM
1.1 Menu
1.1.1 Configuration
The Configuration menu can be used to save the changes in the devices, to clear the session pane and to remove all the configured devices.
1.1.2 Settings
The Settings menu can be used to start stop or configure transport servers. It can also be used to view the state of various transport servers. The Settings menu can be used to set the logs path. By default, the logs are saved in the path where SCTS DM is installed. The settings menu is also used to select the type of OBEX service the client has to use to connect to the obex server.
1.1.3 Tools
Currently available tool in the Tools menu is the ‘Credentials calculator’ and WBXML – XML converter.
1.1.4 Help
The Help menu has the guides which help in configuring the tool as a normal client/server or a test client/server. The Help menu can be used to report a bug to the SCTS team, which will prompt the user as to what are the necessary information that has to be sent to the SCTS team.
1.2 Toolbar
The various toolbar items are context sensitive. For example the ‘ + Add Device’ will add a ‘Client Device’ if the focus is on the ‘Client Devices’ object or will Add a ‘Server Device’ if the focus is on the ‘Server Devices’ object.
1.3 Icons
SCTS DM has different icons to represent the various internal objects. The icons corresponding to the different internal objects are shown below.
Device Management tree
DM Accounts
Connection objects
Commands
Server Device:
Client Device:
Session with Errors:
Session without Errors:
Test passed
Test failed
Not Tested
Optional Test
Not supported
Posted in: Mobile-OMA| Tags: OMA SCOMO DM Menu Toolbar Icon SCTS ServerDeployment Options (Velocity)
Security Considerations
The "Velocity" distributed cache system is designed to be operated in the corporate datacenter within the perimeter of the corporate firewall. The servers described in this topic are the server hosting the cache configuration storage location, the cache servers, the cache-enabled application servers, the development servers, and the primary data source server. All servers should be co-located on the same corporate domain.
Because cached data and the TCP/IP communications between the cache servers is not encrypted, the distributed cache system is vulnerable to malicious "sniffing" and "replay" attacks.
Note
The "Velocity" cache client is meant to reside in the application tier of your application ecosystem. End users inside or outside your corporate domain should not have direct network access to the cache servers.
When decommissioning a cache server, the "Velocity" installation program may not remove all firewall port exceptions. After "Velocity" has been uninstalled, we recommend that you reapply the corporate standard firewall configuration.
Deployment Scenarios
To simplify the discussion of deployment options, this topic will focus on three distinct examples:
-
Developer deployment: A single-computer deployment used by to develop cache-enabled applications.
-
Mid-sized deployment: A multi-computer installation that does not use SQL Server, with lead hosts performing the cluster management role.
-
Enterprise deployment: A multi-computer installation that uses SQL Server for storing cluster configuration settings and performing the cluster management role.