WiseManager Documentation

From OS2World.Com Wiki
Revision as of 01:24, 26 February 2015 by Martini (talk | contribs) (Created page with "==Planning== The Serenity System Managed Client package consists of three basic software components: WiseManager, WiseServer and WiseClient. A key feature of the Managed ...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Planning

   The Serenity System Managed Client package consists of three basic software components: WiseManager, WiseServer and WiseClient. A key feature of the Managed Client environment as implemented by WiseManager is the fact that this application executes from the system administrator's workstation, which can be any workstation on the network, including a remote workstation using a dial up connection. This means that WiseManager can even be implemented and executed from the same system being used as the server. The WiseServer application resides and executes on the server. The WiseClient application resides and executes on each of the remote boot clients.

Software

Server Prerequisites

The server must be running either the Warp Server Entry, Warp Server Advanced, Warp Server SMP, or the newly released OS/2 Warp Server for e-business (a.k.a Aurora) with "Remote IPL", "File and Print Service", and "TCP/IP" installed. A fresh installation with NO fixpaks applied is highly recommended.

Limitations of Remote Boot Clients

WiseManager supports OS/2 Warp 4 as a remote boot client. Users should be aware that it is not possible to invoke Netbios/Netbeui peer resource sharing from a remote boot client. For example, a printer attached to a remote boot client cannot be shared as a peer resource. Sharing a printer is accomplished by attaching the printer to a server, a non-remote boot Warp 4 client, or using a printer which has a built in adaptor to make it a network resource. However, printers CAN be accessed and shared through TCP/IP printing.

The fact that a client has or does not have local drives is not the issue. A remote boot client does not have to be diskless. Once the machine is booted from the network, the local hard drives can be used in exactly the same way as a non-remote boot Warp 4 client system. However, even then, if the client is utilizing local drives, the restriction regarding peer resource sharing remains in effect. Peer resource sharing is not available.

Hardware

Server=

System

Any system capable of running Warp Server should be acceptable for the evaluationprograms which limits the number of clients to five Managed Clients. However larger installations should utilize an SMP version of Warp Server, either Warp Server Advanced SMP, or Warp Server for e-business with the extra SMP option.

Processor

Pentium class processor(s) or equivalent. Because all of the client stations perform their own processing, they create little additional demand on the server processor.

Memory

Sufficient memory should be available to achieve a cache hit ratio of more than 95%. 64M is acceptable for small installations (a few client stations). 128M should be considered the minimum for medium size installations (10 to 30 client stations), and 256M (or more) is recommended for larger installations (more than 30 client stations per boot server).

Hard Disk

For small installations, the minimum requirement is a large capacity IDE drive with at least a RAID 1 hardware mirroring controller. For larger installations, fast ultrawide-SCSI drives with hardware RAID support is highly recommended.

Network Interface Card (NIC)

A bus-mastering NIC is recommended. Users can also use multiple NICs to benefit from Warp Server's automatic load balancing capability.

Client

System

Generally, systems capable of running Warp 4 will provide acceptable performance. The IBM Network Station 2800, or other NLX form factor small foot-print PCs are highly recommended.

Processor

Pentium class processor or equivalent.

Memory

Same requirement as Warp 4.

Video

For best results, use video cards that are supported by the IBM GenGradd or Scitech display doctor drivers see http://service.boulder.ibm.com/os2ddpak/html/gradd/ and http://www.scitech.com). =====Hard Disk The use of a local hard disk for client systems is discouraged. This is an issue of design and implementation. Diskless clients provide more benefits from a standpoint of reliability, manageability, and problem resolution. However, some users may opt to utilize a small local harddrive to host the machine's swapper file. This will help reduce network bandwidth demand by the client system. For small installations, the benefit provided by use of local hard drives is negligible and use of local drives should be avoided.

Network Interface Card (NIC)
               The Managed Client environment is specialized and while many NICs support this environment, it is not always an easy task to determine which NICs fall into this category. Even different model NICs from the same manufacturer have provided mixed results. It is recommended that NICs tested and supported by Serenity Systems be utilized.

Network=

A 16 MB/s token ring or 100BaseT ethernet network is highly recommended. A 10BaseT nework will work fine for small installations.

Server Network Resource Requirements

IBMLAN.INI
               [server] section
NUMREQBUF

This is the number of request buffers. Four (4) should be defined for each requester.

Maximum value is 408.

MAXOPENS

Number of files, pipes, and devices which can be open simultaneously on the server. This value is ignored by the server under the HPFS386 file system.

Maximum value is 8000.

MAXSESSOPENS

Number of files, pipes, and devices simultaneously open for a requester. This value is ignored by the server under the HPFS386 file system.

Maximum value is 8000.

[remoteboot] section

MAXTHREADS

Number of threads that the Remote IPL service starts in order to perform asynchronous reading of the configuration files.

Maximum value = MAXTHREADS in the server's config.sys.

This value should be no greater than 6.

Increasing this parameter can decrease performance in larger installations.

PROTOCOL.INI
[protocol] section
NCBS

Should be set to 4 x n where n is the number of remote boot clients supported by this server.

SESSIONS

Total number of DOS and OS/2 remote boot clients supported by this server.