Multi-Pod Cluster Deployment
Multi-pod cluster deployment is more complex than the single pod deployment. However, it is more resilient to hardware failures and is suitable for horizontal scaling.
TIBCO Fulfillment Catalog attains high-availability in this deployment due to multiple instances of
TIBCO Fulfillment Catalog servers in different pods. The replacement pod joins the cluster and starts the servicing request after it is boostrapped by the Kubernetes master. The data remains safe as the database runs on a different pod under a different exposed service.
Note: To make a database (PostgreSQL or Oracle) or a server like Enterprise Message Service highly available, you must deploy it in high-availability mode.
For more information about high availability deployment of PostgreSQL, Oracle, or Enterprise Message Service, see the respective product documentation.
The TIBCO Fulfillment Catalog GUI is accessed using the IP address of TIBCO Fulfillment Catalog service. The TIBCO Fulfillment Catalog service is a Kubernetes object, which routes the request to an available TIBCO Fulfillment Catalog Pod. For example,
- http://<ip address of fc-service>:9080/eml/Login for TIBCO Fulfillment Catalog
- http://<ip address of opd service>:8070/opdesigner for Offer and Price Designer
- http://<ip address of fc-service>:6080/config for configurator
Copyright © Cloud Software Group, Inc. All rights reserved.