As explained in the other posts, we decided to go with two Weblogic Domains where the first domain was named as SOACoreDomain and had three different clusters consisting of SOACluster ,OSBCluster and WLSCoreCluster (for J2EE apps).
- OSBCluster as a front end service layer and mainaly for stateless services that doesn't require transactions.
- SOACoreCluster as a business logic layer for all the stateful services
- WLSCoreCluster as a webservice layer, deploy all the custom webapp.
- Followed almost all the steps in the Oracle EDG Guide.
- Unique Floating IP's were assigned to each of managed servers including Adminserver and this is to be able to start servers independent of physical machines. Since, we didn't had any plan to use extra box in future so decided not to go with MS migratable option and also host verification disabled.
- We used external hardware load balancer--- Configured to route to appropriate Managed Server/Adminserver listening FQIP and port
- Another Domain was named as SOAExtDomain which had only SOAExtCluster. As a well re-known concept in the industry where using Rules and Transformation as service gives a better scalability and maintainability, we always wanted to move rules and transformation related services from SOACoreDomain to this domain so that the SOACoreDomain will have minimal impact if in case if there are any memory issues seen out of these services in future. Performance issues is a common problem associated with large XML transformations as it is a DOM in memory stuff and also same goes with rules. Mostly, these services would disrupt the core services or other in-flight unrelated transactions and hence decided to go with separate domain altogether for such scenarios.
The below link will give you all the information required for installation and configuration and I hope you will enjoy a lot. For all the WLST scripts used in the document, you could refer to a separate posts in this blog.
Click Here to View the document
- OSBCluster as a front end service layer and mainaly for stateless services that doesn't require transactions.
- SOACoreCluster as a business logic layer for all the stateful services
- WLSCoreCluster as a webservice layer, deploy all the custom webapp.
- Followed almost all the steps in the Oracle EDG Guide.
- Unique Floating IP's were assigned to each of managed servers including Adminserver and this is to be able to start servers independent of physical machines. Since, we didn't had any plan to use extra box in future so decided not to go with MS migratable option and also host verification disabled.
- We used external hardware load balancer--- Configured to route to appropriate Managed Server/Adminserver listening FQIP and port
- Another Domain was named as SOAExtDomain which had only SOAExtCluster. As a well re-known concept in the industry where using Rules and Transformation as service gives a better scalability and maintainability, we always wanted to move rules and transformation related services from SOACoreDomain to this domain so that the SOACoreDomain will have minimal impact if in case if there are any memory issues seen out of these services in future. Performance issues is a common problem associated with large XML transformations as it is a DOM in memory stuff and also same goes with rules. Mostly, these services would disrupt the core services or other in-flight unrelated transactions and hence decided to go with separate domain altogether for such scenarios.
The below link will give you all the information required for installation and configuration and I hope you will enjoy a lot. For all the WLST scripts used in the document, you could refer to a separate posts in this blog.
Click Here to View the document
No comments:
Post a Comment