|
|
|
Web engines help prepare web pages for the web client. All systems have one or more web engines. Zero or more web engines can exist on each server. You can navigate, add, edit, and delete web engines. Each web engine connects to an object manager for processing all requests to CA SDM objects. The default is to connect to the default object manager, but if you have more than one object manager, you can set this value to ANY.
When you define a web engine, you specify the host name. Enter primary for all web engines that start on the primary server; otherwise, enter the host name of the secondary server. The host name is case sensitive and must match the NX_LOCAL_HOST entry in the NX.env of the secondary server.
Each web engine can run and be accessed directly. In direct access, every web browser enters the specific CGI interface for that web engine and the users determine the system loading (load balancing is not automated). All clients can connect to one web engine and overburden this web engine, while the other web engines go unused. A better approach is to assign two or more web engines to a single web director. All requests that go to one of these web engines is directed to the web director for load balancing and then redirected to the most available web engine in the group.
Other configurations can include web directors. One configuration directs all logins to a single SSL secured web engine that handles all logins. After login, the client is directed to another available web engine for further processing.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |