Use the following table as reference for setting up the SLB with Enterprise Manager Management Services.

Various configuration items listed in the below table will be described in subsequent sections of this document.

Cipher profiles are used to define the security, compatibility and speed of the HTTPS traffic. Ciphers are supported by Enterprise Manager and they are used by the SLB administrator to determine which ciphers may be used or which must be excluded to connect to the Enterprise Manager.

1. Create Monitors

   Monitors are used to verify the operational state of pool members. Monitors verify connections and services on nodes that are members of load-balancing pools. A monitor is designed to check the status of a service on an ongoing basis, at a set interval. If the service being checked does not respond within a specified timeout period, the load balancer automatically takes it out of the pool and will choose the other members of the pool. When the node or service becomes available again, the monitor detects this and the member is automatically accessible to the pool and able to handle traffic.

   Table 24-2 Monitors

   Enterprise Manager Service	OMS TCP Port	Monitor Name	Type	Interval	Timeout	Send String	Receive String
   Secure Console (when not using SSL)	7799	mon_ccsc	HTTPS	5	16	GET /em/consoleStatus.jsp HTTP/1.1\r\nHost: slb.example.com\r\nConnection: Close	Enterprise Manager Console is UP
   Unsecure Console (when not using SSL)	7788	mon_ccuc	HTTP	5	16	GET /em/consoleStatus.jsp HTTP/1.1\r\nHost: slb.example.com\r\nConnection: Close	Enterprise Manager Console is UP
   Secure Upload	4900	mon_ccsu	HTTPS	60	181	GET /empbs/upload HTTP/1.1\r\nHost: slb.example.com\r\nConnection: Close	Http Receiver Servlet active!
   Agent Registration	4889	mon_ccar	HTTP	60	181	GET /empbs/genwallet HTTP/1.1\r\nHost: slb.example.com\r\nConnection: Close	GenWallet Servlet activated
   Always-On Monitoring Secure Upload	8081	mon_ccaom	HTTPS	60	181	GET /upload HTTP/1.1\r\nHost: slb.example.com\r\nConnection: Close	Always On Monitoring is active
   Secure JVMD	7301	mon_ccsjvmd	HTTPS	60	181	GET /jamservlet/comm HTTP/1.1\r\nHost: slb.example.com\r\nConnection: Close	Reply to empty request
   Unsecure JVMD	7202	mon_ccujvmd	HTTPS	60	181	GET /jamservlet/comm HTTP/1.1\r\nHost: slb.example.com\r\nConnection: Close	Reply to empty request

   Note:

   Some Load Balancers require <CR><LF> characters to be added explicitly to the Send String using literal "\r\n". This is vendor-specific. Refer to your SLB documentation for details.

2. Create Pools

   A pool is a set of servers configured behind the Load Balancer and grouped together to receive traffic over a specific TCP port for each OMS service.

   Load balancing methods vary depending on the SLB vendor; with several of most common methods being round-robin, least connection, and source-IP hashing. Refer to your specific SLB documentation for available methods and to determine the most suitable for your SLB and operating environment.

   Each pool can have its own unique characteristic for a persistence definition and the load-balancing algorithm used.

   Table 24-3 Pools

   Enterprise Manager Services	Pool Name	Associated Health Monitor	Load Balancing	OMS Host:OMS Service Port
   Secure Console	pool_ccsc	mon_ccsc	Least Connections (member)	OMS Host A:7799 OMS Host B:7799
   Unsecure Console	pool_ccuc	mon_ccuc	Least Connections (member)	OMS Host A:7788 OMS Host B:7788
   Secure Upload	pool_ccsu	mon_ccsu	Least Connections (member)	OMS Host A:4900 OMS Host B:4900
   Agent Registration	pool_ccar	mon_ccar	Least Connections (member)	OMS Host A:4889 OMS Host B:4889
   Always-On Monitoring Secure Upload	pool_ccaom	mon_ccaom	Least Connections (member)	OMS Host A:8081 OMS Host B:8081
   Secure JVMD	pool_ccsjvmd	mon_ccsjvmd	Least Connections (member)	OMS Host A:7301 OMS Host B:7301
   Unsecure JVMD	pool_ccujvmd	mon_ccujvmd	Least Connections (member)	OMS Host A:7202 OMS Host B:7202

3. Create TCP Profiles

   TCP profiles are collections of TCP settings that are configurable settings for controlling the behavior of a particular type (e.g. TCP, HTTP) of network traffic. These profiles enhance control over network traffic and allow the user to control different characteristics for specific clients or applications (e.g. differing browsers).

   Separate TCP profiles can then be associated with different services or virtual servers as required for your operating environment.

   TCP profile values can have serious impacts on the network performance and should be used carefully and with careful consideration of your network and operational requirements.

   TCP profile settings are site and SLB-specific therefore there are no specific OMS requirements for TCP profile settings. Refer to your SLB documentation and network administrator for required TCP profile configuration settings.

   Table 24-4 TCP Profiles

   Enterprise Manager Service	TCP Profile Name
   Secure Console	tcp_ccsc
   Unsecure Console	tcp_ccuc
   Secure Upload	tcp_ccsu
   Agent Registration	tcp_ccar
   Always-On Monitoring Secure Upload	tcp_ccaom
   Secure JVMD	tcp_ccsjvmd
   Unsecure JVMD	tcp_ccujvmd

4. Create Persistence Profiles

   Certain types of applications may require the same client returning to the same pool member, this is called persistence or “stickiness". It can be configured using a persistence profile, and applied to the virtual server. For Oracle Enterprise Manager services, persistence needs to be configured for every service, except for the Secure Upload service.

   Some products offer session persistence support without cookies. These products depend on the IP address of the incoming request. In some circumstances, the originating IP address can change, resulting in session persistence being lost or the request redirected to the wrong backend server. If these cases occur, the service would be better defined to use cookies for persistence instead of source address affinity. Cookie persistence is only applicable when implementing SSL proxying architecture. For Layer 3 Load Balancing (formerly known as SSL Tunneling) the only Persistence Type alternative is Source Address Affinity.

   Table 24-5 Persistence Profiles

   Enterprise Manager Service	Persistence Profile Name	Type	Timeout	Expiration
   Secure Console	sourceip_ccsc	Source Address Affinity or Cookie	3600	Not Applicable
   Unsecure Console	sourceip_ccuc	Source Address Affinity or Cookie	3600	Not Applicable
   Agent Registration	cookie_ccar	Cookie	Not Applicable	3600
   Secure JVMD	sourceip_ccsjvmd	Source Address Affinity	3600	Not Applicable
   Unsecure JVMD	sourceip_ccujvmd	Source Address Affinity or Cookie	3600	Not Applicable

5. Create Rules

   Rules are scripts that run against network traffic passing through your load balancer device. Rules give you the ability to influence network traffic in a variety of ways according to your functional needs.

   Some of the following are types of rules that may be configured, depending on your local Load Balancer:

   • Access control rules which provide access to application resources based upon the source of the request.
   • Access method rules which specify the permitted HTTP methods.
   • URL redirect rules which route incoming HTTP requests to a different destination URL.
   • Request and response header rules which add, alter or remove HTTP request or response headers.
   • HTTP header rules which specify the size of the HTTP header and whether period and underscore characters are permitted within the headers.

   Rule capabilities and rule definition syntax vary according to your Load Balancer vendor. Refer to the vendor documentation for information about these capabilities and syntactic guidance.

   In the examples provided within this document, our virtual servers for Unsecure Console and Unsecure BI Publisher use notional rules for the purpose of redirecting requests to the Unsecure Console service (port 80) and Unsecure BI Publisher (port 8080) and sending them to the secure Console Service (port 443) and Secure BI Publisher (Port 5443) on the Load Balancer.

6. Create Virtual Servers

   A virtual server, with its virtual IP Address and port number, is the client- addressable hostname or IP address through which members of a load balancing pool are made available to a client. After a virtual server receives a request, it directs the request to a member of the pool based on a chosen load balancing method.

   Table 24-6 Required Virtual Servers

   Enterprise Manager Service	Virtual Server Name	Virtual IP and Port	Protocol Profile (Client)	Rule Name	Defaut Pool	Default Persistence Profile
   Secure Console	vs_ccsc443	VIP:443	tcp_ccsc	None	pool_ccsc	sourceip_ccsc
   Unsecure Console *	vs_ccuc80	VIP:80	tcp_ccuc	ccuc_httptohttps	pool_ccuc	sourceip_ccuc
   Secure Upload	vs_ccsu4900	VIP:4900	tcp_ccsu	None	pool_ccsu	None
   Agent Registration	vs_ccar4889	VIP:4889	tcp_ccar	None	pool_ccar	cookie_ccar
   Always-On Monitoring Secure Upload	vs_ccaom8081	VIP:8081	tcp_ccaom	None	pool_ccaom	sourceip_aom
   Secure JVMD	vs_ccsjvmd7301	VIP:7301	tcp_ccsjvmd	None	pool_ccsjvmd	sourceip_ccsjvmd
   Unsecure JVMD	vs_ccujvmd7202	VIP:7202	tcp_ccujvmd	None	pool_ccujvmd	sourceip_ccujvmd

   * These entries are not considered best practice and are not recommended as they provide unsecured and unencrypted access to Enterprise Manager.