Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
OTM
- Thread starter xtract
- Start date
Below is from the NTP's
The TM 3.0 client accesses and modifies data that is stored on the TM 3.0 server. This data is made available by sharing the TM 3.0 folder on the TM 3.0 server with all TM
3.0 clients. Due to the large amounts of data transferred between the TM 3.0 server and the TM 3.0 clients, high network bandwidth is consumed. Response time and performance degrade significantly unless the TM 3.0 client and TM 3.0 server are on the same LAN. In general, a WAN connection is not suitable. Consult "Appendix A: TM
3.0 engineering guidelines" in this document for further details on bandwidth and other network requirements for the TM 3.0 client communicating with the TM 3.0 server. The
appendix also provides information about the different network configurations that are possible.
The web clients operate as thin clients connecting directly to a web server running on the TM 3.0 server. All operations performed using a web client are executed on the TM 3.0 server. The TM 3.0 server requires connectivity to the ELAN subnets of the systems managed. TM Windows and web client require that an administrator account is logged on.
The TM 3.0 client is a thick client that runs on a Windows PC. It does not operate in a traditional client-server model. Rather, the TM 3.0 client runs similar software to that running on the TM 3.0 server. The TM 3.0 client communicates directly with the managed systems, and therefore:
• requires connectivity to the ELAN subnets of those systems
• must be operational at the time any operations performed on the client are scheduled to run
• if a site or system defines a serial profile for Station Admin, physical serial connections must be present between the switch and the server, and between the switch and the client PCs. Communications profiles are defined on a site/system basis and are shared by a server and its clients.
The long and short of it is that the Server holds System Data and Common Data. Client only holds Common Data. What this will do is allow any number of clients to work off of one server. The purchased Dongle($) only has to be on the Server and all clients have access to it.
The TM 3.0 client accesses and modifies data that is stored on the TM 3.0 server. This data is made available by sharing the TM 3.0 folder on the TM 3.0 server with all TM
3.0 clients. Due to the large amounts of data transferred between the TM 3.0 server and the TM 3.0 clients, high network bandwidth is consumed. Response time and performance degrade significantly unless the TM 3.0 client and TM 3.0 server are on the same LAN. In general, a WAN connection is not suitable. Consult "Appendix A: TM
3.0 engineering guidelines" in this document for further details on bandwidth and other network requirements for the TM 3.0 client communicating with the TM 3.0 server. The
appendix also provides information about the different network configurations that are possible.
The web clients operate as thin clients connecting directly to a web server running on the TM 3.0 server. All operations performed using a web client are executed on the TM 3.0 server. The TM 3.0 server requires connectivity to the ELAN subnets of the systems managed. TM Windows and web client require that an administrator account is logged on.
The TM 3.0 client is a thick client that runs on a Windows PC. It does not operate in a traditional client-server model. Rather, the TM 3.0 client runs similar software to that running on the TM 3.0 server. The TM 3.0 client communicates directly with the managed systems, and therefore:
• requires connectivity to the ELAN subnets of those systems
• must be operational at the time any operations performed on the client are scheduled to run
• if a site or system defines a serial profile for Station Admin, physical serial connections must be present between the switch and the server, and between the switch and the client PCs. Communications profiles are defined on a site/system basis and are shared by a server and its clients.
The long and short of it is that the Server holds System Data and Common Data. Client only holds Common Data. What this will do is allow any number of clients to work off of one server. The purchased Dongle($) only has to be on the Server and all clients have access to it.
- Status
Similar threads
