terryissackanichai
Member
Dear Team,
I'm new to this community, hence my apologies, if there is something wrong in my way of asking questions. Please help me in getting a better understanding of the below scenario.
1) We are planning to design our JDE servers(Enterprise, JAS, AIS, RTE, BSSV) in OCI to be in an elastic model, where we will be scaling out(Adding new servers, not resources) and scaling in(Removing these servers) based on our workloads. What are the main factors to be considered while we do the scale in or removal of theses additional servers from a working environment?
2) How do we manage the logs generated in each of these servers which we are planned to be deleted at the time of scaling in?
3)Should we take the servers like BIP, Portal, Identity management also in the scope of elasticity? We have purposefully excluded the Database server and deployment server from our scope of elasticity.
A few of our findings while scaling down servers are as below :
Enterprise Server:
Thanks & Regards,
Terry
I'm new to this community, hence my apologies, if there is something wrong in my way of asking questions. Please help me in getting a better understanding of the below scenario.
1) We are planning to design our JDE servers(Enterprise, JAS, AIS, RTE, BSSV) in OCI to be in an elastic model, where we will be scaling out(Adding new servers, not resources) and scaling in(Removing these servers) based on our workloads. What are the main factors to be considered while we do the scale in or removal of theses additional servers from a working environment?
2) How do we manage the logs generated in each of these servers which we are planned to be deleted at the time of scaling in?
3)Should we take the servers like BIP, Portal, Identity management also in the scope of elasticity? We have purposefully excluded the Database server and deployment server from our scope of elasticity.
A few of our findings while scaling down servers are as below :
Enterprise Server:
- Should be able to handle the UBE workloads without terminating the Jobs(P/W).
- Should be able to handle the ongoing transactions of Interactive application from JAS server without any business interruption.
- Should be able to handle third-party interface logics.
- Should be able to handle the HTML build requests uninterruptedly
- Should be able to handle the JAVA API requests uninterruptedly
- To handle the loads from Orchestrations and ensure it can successfully interact with E1 servers
- Should be able to perform Event Generation, Event transfer, Event Deliver without any disruption.
Thanks & Regards,
Terry