Professional Documents
Culture Documents
About Zookeeper
Troubleshooting
Pre-IP2017 IP2017
• Gateway data store is static – siebns.dat. Any • Gateway hosts REST API for configuration of the
change requires a Gateway restart. Enterprise and Application Interface
• Only local provisioning possible using Config • Dynamic registry, facilitating elasticity and load
Wizard. balancing
Siebel Enterprise https port Application Container Siebel Enterprise
The Siebel Application Interface and Siebel Gateway work together to provide Siebel Server load balancing. When a user
requests a new application connection, Siebel Application Interface sends a request to Siebel Gateway, which returns a
connect string for the least-loaded Application Object Manager from among the Siebel Servers supporting that component.
The user session will use this Application Object Manager.
The Siebel Gateway also includes persistent storage in the registry for configuration information for Siebel Server, Siebel
Application Interface, and other installable components. This information includes:
As this configuration information changes, such as during the configuration of Siebel Enterprise, a Siebel Server, or a Siebel
Application Interface, this data is written to the Siebel Gateway registry.
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
SAI(HTTPS)
Siebel
Database
AI:localhost_access*.log
CG_localhost_access*.log
[INFO ] 2019-11-17 14:13:02.712 [https-openssl-nio-9011-exec-10] CommonLogger - com.siebel.swsm.util.CGUtil:cgGet New CGHost after Service Discovery : crmsit.local:9021
[INFO ] 2019-11-17 14:13:02.712 [https-openssl-nio-9011-exec-10] CommonLogger - com.siebel.swsm.util.CGUtil:cgGet New CG URL after service discovery :
https://crmsit.local:9021/siebel/v1.0/cloudgateway/discovery/services/eautoobjmgr_chs/connectstring
"ConnectString" : "siebel.TCPIP.NONE.NONE://CGWHOST:2321/ENT/eautoObjMgr_chs"
UI.log from AI
Validate GatewayServiceFramework.log
If there are errors while authenticating, fix those. Otherwise it will cause issues while SvcDiscovery.
Zookeeper is a configuration coordination distributed system and we use it for that very requirement.
In simple, ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed
synchronization, and providing group services. All of these kinds of services are used in some form or another by
distributed applications.
ZooKeeper follows a simple client-server model where clients are nodes (i.e., machines) that make use of the service, and
servers are nodes that provide the service. Applications make calls to ZooKeeper through a client library. The client library
is responsible for the interaction with ZooKeeper servers.
Basically CGW does not store anything on it's own. It uses Zookeeper for storing the configuration
Windows:
Using zkCli
Under path: $gtwysrvr/zookeeper/bin
Unix: zkCli.sh -server <gatewayhost:registryport>
Windows: zkCli.cmd -server <gatewayhost:registryport>
Using ZooInspector
How To Read Zookeeper Data In Standalone Mode Using ZooInspector (Doc ID 2427936.1)
DEMO
https://<gatewayhost:HTTPSPort>/siebel/v1.0/cloudgateway/enterprises?
expand=all
AOM request will create Discovery request with Gateway as below ($ses/applicationcontainer/logs/localhost_access*log)
Go to $ses/gtwysrvr/zookeeper/bin:
Unix:
Windows:
Go to $ses/gtwysrvr/zookeeper/bin:
Unix:
Windows:
ZooKeeper responds to a small set of commands. Each command is composed of four letters. You issue the commands to
ZooKeeper via telnet or nc, at the client port.
Some of the more interesting commands: "stat" gives some general information about the server and connected clients, while
"srvr“, “wchc”, “dump” and "cons" give extended details on server and connections respectively.
Cons : List full connection/session details for all clients connected to this server. Includes information on numbers of packets received/sent,
session id, operation latencies, last operation performed, etc...
dump: Lists the outstanding sessions and ephemeral nodes. This only works on the leader.
Stat: Lists brief details for the server and connected clients.
wchc: Lists detailed information on watches for the server, by session. This outputs a list of sessions(connections) with associated watches
(paths). Note, depending on the number of watches this operation may be expensive (ie impact server performance), use it carefully.
How to Enable Zookeeper Client & Server Logs for Siebel 18.x & later ? (Doc ID 2555834.1)
Known Issues:
Bug 29025939 : CLOUD GATEWAY LOSES STATE OF OBJECT MANAGER AND REQUIRES AOM RESTART
TO FIX
The clustering feature supports both the Siebel Gateway service (application container) and the Siebel Gateway registry
(Apache ZooKeeper). You might choose to use Siebel Gateway clustering only for your production environment, for
example. Further, you can use clustering for only the Siebel Gateway service, or only the Siebel Gateway registry.
For a cluster to be always up and running, majority of the nodes in the cluster should be up. So, it is always recommended
to run zookeeper (gateway registry) cluster in odd number of servers. For example, cluster with 3 nodes, or cluster with 5
nodes, etc.
autopurge.purgeInterval=1
initLimit=10
syncLimit=5
autopurge.snapRetainCount=10
maxClientCnxns=10000
snapCount=256
clientPort=8330
tickTime=2000
dataDir=c\:\\Siebel\\ses\\gtwysrvr\\zookeeper
server.1=node1:8335:8336
server.2=node2:8335:8336
server.3=node3:8335:8336
myid: myid file consists of a single line containing only the text of that machine's id. So myid of server 1 would contain the text "1" and
nothing else. The id must be unique within the ensemble and should have a value between 1 and 255.
metadata under $ses/siebsrvr
cgclientstore
Microsoft Word
Document
APPLICATION CAN FAIL TO LOAD IF ONE OF THE GATEWAY NODES IS DOWN WITH GATEWAY CLUSTER (Doc ID
2585549.1)
Bug 30301670 : INTERMITTENT COMPONENT JOBS FAILING WHEN GATEWAY NODE IS DOWN