Siebel CRM System Administration Guide Siebel Innovation Pack 2015, Rev. A E24823-01 |
|
Previous |
Next |
View PDF |
The variables in the following rules have the following meaning:
enterprise is the Siebel Enterprise Server name.
AOM is the Application Object Manager name.
server is the Siebel Server name. You can change this element to the TCP/IP address of the Siebel Server, if desired.
SCBroker_port is the port assigned to the Siebel Connection Broker on the Siebel Server.
sid is the server ID of the Siebel Server. This server ID is a unique number assigned to each Siebel Server during initial configuration.
These rules are URLs for initial connection requests. The syntax of a component rule is as follows:
/enterprise
/AOM
/=server
:SCBroker_port
;...;
When the file is generated, a component rule is created for every enabled Application Object Manager found on every running Siebel Server.
These rules are URLs for server reconnection requests. The syntax of a server rule is as follows:
/enterprise
/*/!sid
.*=server
:SCBroker_port
;
The first asterisk in the syntax is a wildcard for the Application Object Manager. The exclamation point and dot-asterisk (.*) are wildcards that parse the server name to extract the Siebel Server ID.
Not all load balancers can handle a wildcard character (*) in the middle of the URL. In these cases, create URLs with the following format:
/enterprise
/AOM
/!sid
.*=server
:SCBroker_port
;
Repeat this mapping for each combination of the Application Object Manager and Siebel Server ID.
These rules are URLs for server retry requests. The syntax for a round-robin rule is as follows:
/enterprise
/AOM
/RR=server
:SCBroker_port
;...;
This syntax is the same as that of component rules, except that RR is appended to the URL. This string alerts the load balancer to apply a round-robin rule that routes this request to a different Siebel Server.