IBM BS029ML Self Help Guide - Page 80
Planning and considerations, Cloudscape
View all IBM BS029ML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 80 highlights
3.2.1 Planning and considerations WebSphere Portal V6 provides new options to address scalability and redundancy in your enterprise deployments. If you choose to transfer to an external database, we recommend that you do so before you add a large amount of content and preferably during the installation and configuration process. Figure 3-3 shows some points to consider before you transfer you data to a database of enterprise scale. Cloudscape DB Sche ma Admi n @ Content Node A ction Set 1 Feedback User @ MyPortal A ction Set 2 abc Resource 1 .. Resource 2 Resource1 Resource 3 Resource 2 Resource 3 .. Resource x .. .. Weak References Resource x Resource y Resour ce1 Resource 2 .. Resource x value value .. value Referential In tegrity DB Schema A dmi n @ Cont ent N ode Action Set1 LikeMinds User @ MyPortal Action Set2 abc Resource 1 .. Resource 2 Resource1 Resource 3 Resource 2 Resource 3 .. Resource x .. .. Weak References Resource x Resource y Resource1 Resource 2 .. Resource x value value .. value Referential In tegrity Po rtal Por tlets Cont ent Nodes T emplates W ps.content.r oot Applications My Portal ..... Resource DB Schema Ad mi n @ Co nt ent Nod e Act ion S et 1 JCR User @MyPortal Act ion S et 2 Resource Resource Domain prod. Re sou rce prod R esour ce 3 pr od. Resource 2 ab c Res ou rc e 1 Reso urce 1 Reso ur ce 3 .. Res ou rc e 2 .. Res ou rc e x Reso urce 2 Reso ur ce 3 .. .. Weak R eferences Reso urce x Reso ur ce y Re sou rce1 Re sou rce 2 .. Re sou rce x v alu e v alu e .. v alu e R efe rential Integrity Por tal Po rtlets Co ntent Nod es Temp lat es Wps.content.root Applications My Por tal ..... Resource DB Schem a Ad mi n@ Co nt ent No de Act io n S et 1 Resource R esour ce Customization User@MyPortal Act io n S et 2 pr od. p rod . pr od Resourc e 3 R esource R esour ce 2 Domain abc Res ou rce 1 .. Res ou rce 2 Res ou rc e1 Res ou rc e 3 Res ou rc e 2 Res ou rc e 3 .. Res ou rce x .. .. Weak R efere nces Res ou rc e x Res ou rc e y Res ourc e1 Res ourc e 2 .. Res ourc e x va lue va lue .. va lue Referential I ntegr ity Por tal Portlets Content Nod es Templat es Wps.content.root Applications My Por tal ..... Re sour ce DB Schem a Ad mi n @ Co nt en t No de Act io n S et 1 Re sour ce Release User@MyPortal Act io n S et 2 pr od. R esource Resource Domain prod. pr od Resource 3 R esour ce 2 ab c Res ou rce 1 Res ou rc e1 Res ou rc e 3 .. Res ou rce 2 .. Res ou rce x Res ou rc e 2 Res ou rc e 3 .. .. We ak R efere nc es Res ou rc e x Res ou rc e y Res ou rc e1 Res ou rc e 2 .. Res ou rc e x va lue va lue .. va lue Refere nti al Integr ity Database Domains Release JCR Customization Community Figure 3-3 Transferring to an external database Audit of your database infrastructure The database is typically the heart of any Web-based application. For the success of your deployment, it is critical that the hardware and software that will be used to house the portal database(s) be not only highly optimized but resilient. Before you begin the database transfer process, review the prerequisites discussed below. System requirements It is important to conduct a preliminary review of the hardware and software of your system in both the new and existing database infrastructures to ensure they meet the supported levels for WebSphere Portal Server. The InfoCenter is routinely updated with specific versions and recommended compatible levels of configuration. If your are considering an upgrade to your database implementation, we advise you to refer to 3.1.1, "How do I prepare my system for installation" on page 56 before attempting an upgrade of your environment. Performance and availability WebSphere Portal Server provides you with the option of installing the database server on the same server that the WebSphere Portal Server will be housed; however, if performance is of utmost importance for your portal application(s), we recommend that you provide a separate physical database server for your RDBMS. Performance tools should be utilized continuously to monitor the state of the database server(s) and the databases themselves, with mechanisms instituted to tune the entities as needed. For additional information about planning for your database infrastructure, refer to 2.7, "Database considerations" on page 46. 66 IBM WebSphere Portal V6 Self Help Guide