User manual BUSINESS OBJECTS APPLICATION FOUNDATION 6.5.2 FOR WINDOWS INSTALLATION GUIDE

[. . . ] Application Foundation Installation Guide Application Foundation6. 5. 2 Windows 2 Application Foundation Installation Guide Patents Business Objects owns the following U. S. patents, which may cover products that are offered and sold by Business Objects: 5, 555, 403, 6, 247, 008 B1, 6, 578, 027 B2, 6, 490, 593 and 6, 289, 352. Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are trademarks or registered trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names mentioned herein may be trademarks of their respective owners. [. . . ] Use the Configuration Tool to configure the orb. - Once the ORB is configured, deploy the Business Objects web applications you need, and configure the cluster's web and application server instances to work with BusinessObjects. - Install the Business Objects products and use the Configuration Tool to configure the ORB on each node hosting Business Objects and/or an application server. Start WebSphere and open a command prompt. In the deployment folder, run the following command: wdeploy WebSphere5 -DAPP=apps deploy 6. Add the following servlet calls to the plugin-cfg. xml file: <Uri Name="/apps/servlet/AAGateServlet/*"/> <Uri Name="/wijsp/servlet/com. bo. hsal. HSALServlet/*"/> <Uri Name="/wijsp/servlet/CadenzaServlet/*"/> <Uri Name="/apps/servlet/CadenzaServlet/*"/> <Uri Name="/apps/servlet/com. bo. hsal. HSALServlet/*"/> NOTE To get more information about "wdeploy" check the Manual Web and Application Server Configuration guide for your platform. For example, if you deploy Application Foundation on top of a simple WebIntelligence deployment that is configured on the single node of a single cluster deployment, then Application Foundation needs to adhere to these deployment constraints. Application Foundation WebIntelligence Primary Node WebIntelligence Cluster Deploy AF WebIntelligence Primary Node WebIntelligence Cluster Figure 4-1 Single Node WebIntelligence Deployment becomes Single Node Deployment For this reason, if your deployment requires a more complex server model, then you need to deploy first at the WebIntelligence level, and then configure Application Foundation to work within that configuration. AF WebI Primary Node WebI Secondary Node Deploy AF WebI Primary Node AF WebI Secondary Node WebIntelligence Cluster WebIntelligence Cluster Figure 4-2 Start with Multi-Node WebIntelligence to gain Multi-Node Application Foundation For more information about deploying Business Objects server products, see Deploying the Business Objects System. Deployment Application Foundation Installation Guide 21 Deployment Options From a hardware perspective, it is possible to deploy Application Foundation on a single machine, for example a demonstration laptop, but the best deployment option is to use multiple machines to maintain security and/or scalability. The following diagram shows a single machine setup in its simplest form alongside a distributed deployment that allows for extranet (DMZ) type configuration and multiple Application Foundation/ WebIntelligence servers. Single machine deployment Multiple machine deployment Web server Application server Application Foundation WebIntelligence Set Agent Database middleware Database Windows operating system Application server Application Foundation WebIntelligence Database middleware Application Foundation WebIntelligence Database middleware Web server AACONF Deployment Options 22 Application Foundation Installation Guide Simple Deployment The simplest of Business Objects server deployments is one where the entire deployment exists on a single cluster with a single cluster node, and the Application and Web servers are deployed on the same physical server machine with the rest of the Application Foundation / Business Objects system. Business Objects Primary Node Users on client applications Application server Web server Network In this case, users interact via their browsers with Web and Application servers, which then interact with the Business Objects Primary Node server components. When Application Foundation is deployed: · JSP's and user interface objects reside in the Application server layer · Raw HTML and pictures reside in the Web server layer Object persistence in a simple deployment case Different objects in the infrastructure are persisted between sessions using different methods. For example, dashboard definitions are logged in an XML file on the file system by the Application server code. However, metrics are written as objects into the Application Foundation repository, which resides in a database. Additionally, reports are managed inside the Business Objects repository, which may reside in a different database system. Deployment Application Foundation Installation Guide 23 In general, Application Foundation objects are written to four different places. · Business Objects documents and security definitions are stored in the Business Objects document and security repository. · Application Foundation metadata, for example metric definitions and values, rule definitions, and alerts are all stored in the Application Foundation metadata repository which is stored in a database. · Personal dashboards are persisted in the file system, typically in a directory in the <nodes> section of the Business Objects deployment: <$e6>\nodes\<nodename>\<clustername>\storage\user · Corporate dashboards are persisted in the file system as well, although they are persisted at a different level: <$e6>\Application Foundation\server\conf Simple Deployment 24 Application Foundation Installation Guide Multi-Node Deployment The BusinessObjects server environment enables you to deploy different CORBA objects onto different nodes of a server cluster. This means that some objects may be deployed only once on the same server, on a different server, or may be redundantly deployed on several server nodes. You deploy Application Foundation in a multi-node environment for one or more of the following reasons: · Failover - if an object can be made to run on multiple nodes of a cluster, then the cluster may be able to correct for system failures if one of the nodes goes down. · Scalability - if a high-processing portion of the system is being stressed by the current usage levels, deploying that component onto multiple nodes within the cluster can facilitate improved performance. [. . . ] To see the revised dashboard, User B needs to customize the page to force the XML to load, and click Apply. This causes Server B to run its own XSL transform and show User A's changes. If User A logs into Server A and builds or refreshes a metric, the metric engine is called, executes the SQL, and on completion sends a notification to the metrics cache in AAAnalytics to update. User A can see the new value(s) or metric in the analytics used in dashboards. [. . . ]