User manual BUSINESS OBJECTS VOYAGER XI ADMINISTRATORS GUIDE

[. . . ] BusinessObjects Voyager Administrator's Guide BusinessObjects Voyager XI 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. [. . . ] The configuration file MDASServer. conf contains many settings that can be tweaked to alter performance and server behavior. For more information about this file and its settings, consult the online documentation (http:// wrapper. tanukisoftware. org/doc/english/introduction. html). In addition, for information on MDAS server performance settings that are better suited to your organization's unique requirements, consult Business Objects Technical Support. 28 BusinessObjects Voyager Administrator's Guide Administering the Multi-Dimensional Analysis Services Server Configuring the MDAS server 3 Note: Changing settings in the MDASServer. conf file can have negative effects on the performance and operation of the entire Voyager application. Proceed with caution. Single or multiple MDASServer. conf files The simplest server wrapper setup is a single MDAS server with a single MDASServer. conf file; however, you can also have multiple, clustered MDAS servers controlled by a single MDASServer. conf file. Also, you can have multiple MDAS servers, each controlled by its own MDASServer. conf file. If you use a single MDASServer. conf file to control a cluster of MDAS servers, then you must pass parameters using the command line for each server to indicate information such as server name, sessions, timeout, etc. See "Generic configuration file" below. If you want to use a separate MDASServer. conf file for each of the MDAS servers, then you can put the information for each server into its respective MDASServer. conf file. See "Modified configuration file" below. For more information about clustering MDAS servers, see "Clustering MDAS servers" on page 32. Command line options Command line options are passed through the service wrapper to the application. This is performed by wrapping the command line options using: wrapper. app. parameter. n Where n is the next incremental application parameter number. You must use this wrapper, regardless of whether you decide to use a generic configuration file for all applications, or modify your configuration file for each application. Generic configuration file If you are using a single generic MDASServer. conf configuration file, you must use this method at the command line to pass all command line options to the application. For example, consider the following command line command and options that you would normally expect to use with a regular BusinessObjects Enterprise server: "C:\Program Files\Business Objects\BusinessObjects Enterprise 11. 5\win32_x86\wrapper. exe" -t "C:\Program Files\Business Objects\BusinessObjects Enterprise 11. 5\win32_x86\MDSServer. conf" -name IUSERBOX. product. businessobjects. com. MDASServer(2) -ns IUSERBOX ­ntservicename BOBJMDASServer(2) BusinessObjects Voyager Administrator's Guide 29 3 Administering the Multi-Dimensional Analysis Services Server Configuring the MDAS server The command line options would not be passed to the application. Instead, you must rewrite them as the following: "C:\Program Files\Business Objects\BusinessObjects Enterprise 11. 5\win32_x86\wrapper. exe" -t "C:\Program Files\Business Objects\BusinessObjects Enterprise 11. 5\win32_x86\MDSServer. conf" wrapper. app. parameter. 2="-name" wrapper. app. parameter. 3="IUSERBOX. product. businessobjects. co m. MDASServer(2)" wrapper. app. parameter. 4="-ns" wrapper. app. parameter. 5="IUSERBOX" wrapper. app. parameter. 6="-ntservicename" wrapper. app. parameter. 7="BOBJMDASServer(2)" Note how each option is indicated using wrapper. app. parameter. n. Because the syntax of command line arguments differs depending on the operating system, command line arguments such as ­name {name} is handled as two separate command line wrapper. app. parameter statements: wrapper. exe -t MDSServer. conf wrapper. app. parameter. 2="-name" wrapper. app. parameter. 3="IUSERBOX. product. businessobjects. co m. MDASServer(2)" Use this syntax for all command line arguments for the MDAS Server. Modified configuration file If you decide to modify the MDASServer. conf file, the wrapper. app. parameter. n arguments can be added as part of the file. For example, the command line options in the previous example are added to the configuration file: # Application parameters. from 1 Add parameters as needed starting wrapper. app. parameter. 1=com. businessobjects. multidimensional . services. server. MdsServerBootstrap wrapper. app. parameter. 2=-name wrapper. app. parameter. 3=MDASServer2 wrapper. app. parameter. 4=-ns wrapper. app. parameter. 5=IUSERBOX wrapper. app. parameter. 6=-maxSessions wrapper. app. parameter. 7=100 # MDS logging configuration wrapper. java. additional. 1=-Dlog4j. configuration=mds. log4j. pr operties 30 BusinessObjects Voyager Administrator's Guide Administering the Multi-Dimensional Analysis Services Server Configuring the MDAS server 3 Using the CMC to manage MDAS server properties and metrics When you click a server instance listed on the Servers page of the CMC, you are redirected to a set of pages that display read-only information about the selected server and allow you to specify new configuration parameters. For more information, see the following topics: · · · Set properties "Set properties" on page 31. "Manage rights" on page 32. The Properties tab contains some settings you can use to adjust client and server connections to better suit your organization's needs: · Client-Server timeout: This setting indicates the number of milliseconds of inactivity between the Voyager client and MDAS server to wait before timing out, and forcing the user to log in again. If no command line value is set, the default is 1200000. If this value is set to 0, the connection stays open indefinitely. Maximum number of sessions: This setting indicates the total number of sessions that can be concurrently opened on the MDAS server. [. . . ] To change access to workspaces In the Organize area in the CMC, select Objects. Change the Access Level, and then click Update. Seeing a list of connections linked to the workspace A Voyager workspace can be linked to several connection objects. To see a list of connection objects linked to the workspace In the Organize area in the CMC, select Objects. All connection objects that are linked to the workspace are listed. BusinessObjects Voyager Administrator's Guide 59 6 Managing Voyager Workspaces in the CMC Seeing a list of connections linked to the workspace 60 BusinessObjects Voyager Administrator's Guide Business Objects Information Resources appendix A Business Objects Information Resources Documentation and information services Documentation and information services Business Objects offers a full documentation set covering its products and their deployment. [. . . ]