businessobjects-2
Using Contexts
A context is a rule by which determines which of two paths can be chosen when more than one path is possible in the database. With certain database structures, you may need to use contexts rather than aliases to resolve loops. A situation where this commonly occurs is a transactional database with multiple fact tables (“multiple stars”) that share lookup tables.
Contexts defined in a universe can lead to three types of queries:
• Ambiguous queries
• Inferred queries
• Incompatible queries
When you create aliases and you end up with object names that sound very different (Customer’s Country of Residence, Shipment Destination, and Products Country of Manufacture), aliases are probably the right solution. If you end up with object names that sound very similar (such as Ordered Products and Loaned Products as well as Ordered Products’ Country of Manufacture and Loaned Products’ Country of Manufacture), you should consider using contexts.
Breaking up a universe into multiple universes for WEBINTELLIGENCE users is the best way to resolve a Chasm trap when you can not use the Multiple SQL for Measures function, and using contexts is not appropriate as the SELECT statements are synchronized not joined. However, if you have both BUSINESSOBJECTS and WEBINTELLIGENCE users, you may need to consider the type of universes that you will design for both environments at the universe planning stage.
The @ functions
DESIGNER provides a number of functions for the SQL definition of objects. By using these functions, you make the definition of objects dynamic as well as database-independent. Referred to as @ functions, these functions are as follows:
• @Aggregate_Aware
• @Prompt
• @Script
• @Select
• @Variable
• @Where
Security access levels are assigned to user profiles by the supervisor from SUPERVISOR. The levels are, from highest to lowest: Private, Confidential, Restricted, Controlled, and Public.
BUSINESSOBJECTS allows two types of multidimensional analyses:
• slice and dice
• drill (available only with the BUSINESSOBJECTS EXPLORER).
With slice and dice, an end user can rotate a microcube in order to view it from different perspectives. For example, let’s say that a microcube is made up of three hierarchies: Country, Resort, and Revenue. The sales manager may wish to view Revenue by Country. By rotating the microcube, the sales manager can also view Revenue by Resort or by Region. Thus, a microcube with n dimensions has n x (n - 1) possible views.
Drill gives an end user the means to navigate through hierarchical levels of detail. The notion of hierarchy is very important in drill. It provides the framework for “drilling up” or “drilling down.”
What is Aggregate Awareness?
Aggregate awareness is a feature of DESIGNER that makes use of aggregate tables in a database. These are tables that contain pre-calculated data. The purpose of these tables is to enhance the performance of SQL transactions; they are thus used to speed up the execution of queries.
Of course, the reliability of the technique depends on the accuracy of the aggregate tables. In fact, they must be refreshed at the same time as all fact tables. A universe that is “aggregate aware” has one or more aggregate objects with alternative definitions based on these tables. These definitions correspond to levels of aggregation. For example, a Profit object can be aggregated by month, by quarter, or by year. Queries built from such a universe return information aggregated to the appropriate level at optimal speed.
End users have the ability to create their own objects in BUSINESSOBJECTS from existing objects in a universe. These customized objects, called “user objects,” serve a specific need of the end user. However, they can be used only in the universe in which they were created. Like any other objects, user objects have a name, qualification, and definition. BUSINESSOBJECTS stores user objects as files in the Universe subfolder. The names of these files are comprised of the universe name and a .udo extension.
Enterprise and Workgroup Modes
DESIGNER lets you save universes in either enterprise or workgroup mode. Enterprise mode means that you are working in an environment with a repository. Workgroup mode means that you are working without a repository. The mode in which you save your universes determines whether other designers are able to access them.
What are Linked Universes?
Linked universes are universes that share common components such as parameters, classes, objects, or joins. Among linked universes, one universe is said to be the kernel or master universe while the others are the derived universes.
A kernel or master universe represents a re-usable library of components. Derived universes may contain some or all the components of the kernel or master universe, in addition to any components that have been added to it.
Approaches to linking universes
You can use one of three approaches when linking universes:
• The kernel approach
• The master approach
• The component approach
The Benefits of Linked Universes
Some of the benefits inherent in the use of linked universes are as follows:
• A dynamic link may considerably reduce development and maintenance time. When you modify a component in the kernel universe, DESIGNER propagates the change to the same component in all the derived universes.
• Instead of re-creating common components each time you create a new universe, you can centralize such components in a kernel universe, and then include them in all new universes.
• Linked universes facilitate specialization. Development can be split between database administrators who set up a basic kernel universe, and the more specialized designers who create more functional universes based on their specific field.
WEBINTELLIGENCE
WEBINTELLIGENCE has a distributed component architecture and light query applets available in either Java or ActiveX, eliminating the need for client-side installation and maintenance of application software and database middleware.
The robustness and reliability of the WEBINTELLIGENCE system has propelled it to become the standard architecture for all Business Objects enterprise server products. These include BROADCAST AGENT, with which users can schedule documents for automatic refresh and distribution, and a new, zero-administration deployment of BUSINESSOBJECTS which brings end users all the power of the full-client version.
Distributed Object Technology
The distributed object technology underlying the WEBINTELLIGENCE system gives organizations ultimate scalability and flexibility because components of the WEBINTELLIGENCE application server can either run on a single machine or be distributed across multiple systems. The system’s distributed component architecture (DCA) provides customers with a distributed virtual server providing three major benefits:
• Failover
A distributed system can also provide failure recovery: when system components are installed on more than one server, if a server stops working, the system can continue to use the same required components on other servers. High availability is also ensured because automatic failover is provided when a machine running a WEBINTELLIGENCE component fails.
• Scalability
User populations on the Internet can be much, much larger than we have traditionally seen. As the document processing needs and the user population in your organization grow, you can manage the extra workload simply by adding servers to the system.
• Load balancing
Optimal response times are ensured because the distributed system automatically performs load balancing across component servers. Distributing components over several servers in addition allows you to decide which components are activated where, thus optimizing the use of server resources, reducing the workload on the web server, and increasing performance.
A key part of the WEBINTELLIGENCE distributed system is implemented via a state-of-the-art, CORBA-compliant (Common Object Request Broker Architecture) object request broker (ORB) licensed from VisiBroker Software.
Enhanced load balancing mechanisms
A distributed deployment can scale to a greater number of users by automatically redirecting requests to the machines that are less “loaded” in the system. This capability is called load balancing. To scale up, simply add machines. Multiple machines allow overloaded components to redirect to less-used ones.
Every enterprise server product in the Business Objects product line uses the WEBINTELLIGENCE system. They are:
• WEBINTELLIGENCE
• BROADCAST AGENT
• Zero Admin BUSINESSOBJECTS
• WEBINTELLIGENCE SDK
Yes. Despite the broad range of products using the Business Objects distributed solution, users have a single web-based portal to access all the information they need. The base module for both WEBINTELLIGENCE and BUSINESSOBJECTS, this portal is called INFOVIEW. Intuitive and customizable, it is the users’ personal gateway to their organization’s information capital. It also lets users manage, save, distribute, print and schedule documents for automated processing.
WEBINTELLIGENCE comes in three modules:
• WEBINTELLIGENCE INFOVIEW
• WEBINTELLIGENCE REPORTER
• WEBINTELLIGENCE EXPLORER
The base module of the Business Objects solution is an e-Business Intelligence portal called INFOVIEW, which provides users with a single entry point to all the documents they need. This module is user-customizable, so that their copies of INFOVIEW fit their needs as closely as possible.
INFOVIEW lets users view, refresh, manage and distribute documents, but not create or modify them. To do that, they need the WEBINTELLIGENCE and/or USINESSOBJECTS REPORTER modul es, or BUSINESSOBJECTS installed through a web browser.
The document catalog includes up to three lists containing files they can access:
• The Corporate Documents page contains files that have been saved or uploaded to a document domain in the corporate repository and made accessible to workgroups within the corporation or organization.
• The Personal Documents page contains documents users have saved for their own personal use.
• The Inbox Documents page contains documents other users have sent each user.
WebIntelligence Reporter
WEBINTELLIGENCE REPORTER allows users to create and edit WEBINTELLIGENCE documents. To do this, they use a Java applet or an ActiveX control called the Web Panel, which is automatically downloaded for users to build and edit documents.
WebIntelligence Explorer
WEBINTELLIGENCE EXPLORER allows users to drill in “drillable” WEBINTELLIGENCE documents to analyze data on different levels of detail,
Broadcast Agent
BROADCAST AGENT empowers BUSINESSOBJECTS and WEBINTELLIGENCE users to automatically process and publish their Business Objects documents via the repository, an intranet, or an extranet open to the World Wide Web. BROADCAST AGENT can also automate the use of "Push" technology on the web using channels.
BROADCAST AGENT comes with the Broadcast Agent Console, which allows administrators to track and modify the scheduled automatic processing of documents through BROADCAST AGENT. The Console is also available from BUSINESSOBJECTS so BUSINESSOBJECTS users can monitor the documents they have scheduled with BROADCAST AGENT. It can also be installed and used on any Windows machine on the same sub-net as the server cluster.
WebIntelligence SDK
WEBINTELLIGENCE SDK (Software Development Kit) is an extension of WEBINTELLIGENCE which enables you to customize the look, behavior, and workflow of a WEBINTELLIGENCE deployment. A common use of WEBINTELLIGENCE SDK is to align WEBINTELLIGENCE deployments with current corporate intranet or extranet solutions.
With WEBINTELLIGENCE SDK you can
• Personalize the user interface.
• Embed prompts in web pages. You can determine which prompts are returned depending on a user’s profile and you can determine the results sent back to the user based on their input.
• Add a hyperlink to a document which launches the Web Panel.
• Include ActiveX and other components in web pages. For example, you can display a Microsoft Excel spreadsheet in the same page as a BUSINESSOBJECTS document.
WEBINTELLIGENCE recognizes three types of documents:
• WEBINTELLIGENCE documents
• BUSINESSOBJECTS documents
• Third-party documents
Basically, third-party files are treated just the same as BUSINESSOBJECTS/ WEBINTELLIGENCE files. The differences are as follows:
• When BUSINESSOBJECTS and WEBINTELLIGENCE files are stored in the repository, they include the document ID inside the file. Third-party files are stored as binary files in the repository, these binary files are treated as a "black box" by the system, which cannot look inside the file for the ID. Instead the document IDs of third-party files are stored elsewhere in the repository.
• When you view a BUSINESSOBJECTS/WEBINTELLIGENCE document, you can see the document in your browser, but the document itself is generated on the server, from which an HTML representation is created and sent to your browser. The actual document remains on the server, and is not downloaded
to the client system.
On the other hand, when you view a third-party file, no HTML code is generated. Instead, the binary data is downloaded to the client system, from where it is automatically opened using the application in which it was originally created (e.g., Word, Excel, Acrobat, etc.).
• You cannot create, edit, update, or schedule third-party files from within the WEBINTELLIGENCE system.
• To publish and access third-party files, two new options have been added to WEBINTELLIGENCE INFOVIEW: Upload and Download. This new feature, which allows the WEBINTELLIGENCE system to handle any type of file in much the same way as a BUSINESSOBJECTS or WEBINTELLIGENCE file, is referred to as document agnosticism.
How documents are stored and organized
After you have created a document,
• Corporate documents
If you choose Publish, the document is stored in the repository of your choice as a corporate document. At the same time, you can also schedule the document for automated distribution by BROADCAST AGENT.
• Inbox documents
If you choose Send, the document is stored in the repository, in the inbox of the user or users to whom it is sent. You can also schedule the document for automated distribution to specified users by BROADCAST AGENT.
• Personal documents
If you choose Save, the document is stored in the designated storage area as a personal document.
The WEBINTELLIGENCE system has two separate mechanisms for the storage of documents and temporary system files:
• The WIStorageManager
• Temporary system caches
Distributed Architecture Overview
A distributed architecture is one in which common server resources are shared among the server products, and are distributed over several physical servers. WEBINTELLIGENCE modules, or processes, can run on different machines, and the system automatically recognizes all the machines in the WEBINTELLIGENCE system, as well as the distributed services at runtime.
You can therefore scale up the WEBINTELLIGENCE system as demand grows by adding more servers to the system to share the transaction load and provide failover capabilities. This way, if one server fails, the system automatically redirects requests to another, functioning server in the system. This type of distributed WEBINTELLIGENCE structure is called a cluster.
Clusters contain two types of servers:
• The cluster manager is the central coordinator between all the servers in the system. There must be one and only one cluster manager in a cluster.
Clusters contain two types of servers:
• The cluster manager is the central coordinator between all the servers in the system. There must be one and only one cluster manager in a cluster.
What are Linked Universes?
Linked universes are universes that share common components such as parameters, classes, objects, or joins. Among linked universes, one universe is said to be the kernel or master universe while the others are the derived universes.
A kernel or master universe represents a re-usable library of components. Derived universes may contain some or all the components of the kernel or master universe, in addition to any components that have been added to it.
Approaches to linking universes
You can use one of three approaches when linking universes:
• The kernel approach
• The master approach
• The component approach
A context is a rule by which determines which of two paths can be chosen when more than one path is possible in the database. With certain database structures, you may need to use contexts rather than aliases to resolve loops. A situation where this commonly occurs is a transactional database with multiple fact tables (“multiple stars”) that share lookup tables.
Contexts defined in a universe can lead to three types of queries:
• Ambiguous queries
• Inferred queries
• Incompatible queries
When you create aliases and you end up with object names that sound very different (Customer’s Country of Residence, Shipment Destination, and Products Country of Manufacture), aliases are probably the right solution. If you end up with object names that sound very similar (such as Ordered Products and Loaned Products as well as Ordered Products’ Country of Manufacture and Loaned Products’ Country of Manufacture), you should consider using contexts.
Breaking up a universe into multiple universes for WEBINTELLIGENCE users is the best way to resolve a Chasm trap when you can not use the Multiple SQL for Measures function, and using contexts is not appropriate as the SELECT statements are synchronized not joined. However, if you have both BUSINESSOBJECTS and WEBINTELLIGENCE users, you may need to consider the type of universes that you will design for both environments at the universe planning stage.
The @ functions
DESIGNER provides a number of functions for the SQL definition of objects. By using these functions, you make the definition of objects dynamic as well as database-independent. Referred to as @ functions, these functions are as follows:
• @Aggregate_Aware
• @Prompt
• @Script
• @Select
• @Variable
• @Where
Security access levels are assigned to user profiles by the supervisor from SUPERVISOR. The levels are, from highest to lowest: Private, Confidential, Restricted, Controlled, and Public.
BUSINESSOBJECTS allows two types of multidimensional analyses:
• slice and dice
• drill (available only with the BUSINESSOBJECTS EXPLORER).
With slice and dice, an end user can rotate a microcube in order to view it from different perspectives. For example, let’s say that a microcube is made up of three hierarchies: Country, Resort, and Revenue. The sales manager may wish to view Revenue by Country. By rotating the microcube, the sales manager can also view Revenue by Resort or by Region. Thus, a microcube with n dimensions has n x (n - 1) possible views.
Drill gives an end user the means to navigate through hierarchical levels of detail. The notion of hierarchy is very important in drill. It provides the framework for “drilling up” or “drilling down.”
What is Aggregate Awareness?
Aggregate awareness is a feature of DESIGNER that makes use of aggregate tables in a database. These are tables that contain pre-calculated data. The purpose of these tables is to enhance the performance of SQL transactions; they are thus used to speed up the execution of queries.
Of course, the reliability of the technique depends on the accuracy of the aggregate tables. In fact, they must be refreshed at the same time as all fact tables. A universe that is “aggregate aware” has one or more aggregate objects with alternative definitions based on these tables. These definitions correspond to levels of aggregation. For example, a Profit object can be aggregated by month, by quarter, or by year. Queries built from such a universe return information aggregated to the appropriate level at optimal speed.
End users have the ability to create their own objects in BUSINESSOBJECTS from existing objects in a universe. These customized objects, called “user objects,” serve a specific need of the end user. However, they can be used only in the universe in which they were created. Like any other objects, user objects have a name, qualification, and definition. BUSINESSOBJECTS stores user objects as files in the Universe subfolder. The names of these files are comprised of the universe name and a .udo extension.
Enterprise and Workgroup Modes
DESIGNER lets you save universes in either enterprise or workgroup mode. Enterprise mode means that you are working in an environment with a repository. Workgroup mode means that you are working without a repository. The mode in which you save your universes determines whether other designers are able to access them.
What are Linked Universes?
Linked universes are universes that share common components such as parameters, classes, objects, or joins. Among linked universes, one universe is said to be the kernel or master universe while the others are the derived universes.
A kernel or master universe represents a re-usable library of components. Derived universes may contain some or all the components of the kernel or master universe, in addition to any components that have been added to it.
Approaches to linking universes
You can use one of three approaches when linking universes:
• The kernel approach
• The master approach
• The component approach
The Benefits of Linked Universes
Some of the benefits inherent in the use of linked universes are as follows:
• A dynamic link may considerably reduce development and maintenance time. When you modify a component in the kernel universe, DESIGNER propagates the change to the same component in all the derived universes.
• Instead of re-creating common components each time you create a new universe, you can centralize such components in a kernel universe, and then include them in all new universes.
• Linked universes facilitate specialization. Development can be split between database administrators who set up a basic kernel universe, and the more specialized designers who create more functional universes based on their specific field.
WEBINTELLIGENCE
WEBINTELLIGENCE has a distributed component architecture and light query applets available in either Java or ActiveX, eliminating the need for client-side installation and maintenance of application software and database middleware.
The robustness and reliability of the WEBINTELLIGENCE system has propelled it to become the standard architecture for all Business Objects enterprise server products. These include BROADCAST AGENT, with which users can schedule documents for automatic refresh and distribution, and a new, zero-administration deployment of BUSINESSOBJECTS which brings end users all the power of the full-client version.
Distributed Object Technology
The distributed object technology underlying the WEBINTELLIGENCE system gives organizations ultimate scalability and flexibility because components of the WEBINTELLIGENCE application server can either run on a single machine or be distributed across multiple systems. The system’s distributed component architecture (DCA) provides customers with a distributed virtual server providing three major benefits:
• Failover
A distributed system can also provide failure recovery: when system components are installed on more than one server, if a server stops working, the system can continue to use the same required components on other servers. High availability is also ensured because automatic failover is provided when a machine running a WEBINTELLIGENCE component fails.
• Scalability
User populations on the Internet can be much, much larger than we have traditionally seen. As the document processing needs and the user population in your organization grow, you can manage the extra workload simply by adding servers to the system.
• Load balancing
Optimal response times are ensured because the distributed system automatically performs load balancing across component servers. Distributing components over several servers in addition allows you to decide which components are activated where, thus optimizing the use of server resources, reducing the workload on the web server, and increasing performance.
A key part of the WEBINTELLIGENCE distributed system is implemented via a state-of-the-art, CORBA-compliant (Common Object Request Broker Architecture) object request broker (ORB) licensed from VisiBroker Software.
Enhanced load balancing mechanisms
A distributed deployment can scale to a greater number of users by automatically redirecting requests to the machines that are less “loaded” in the system. This capability is called load balancing. To scale up, simply add machines. Multiple machines allow overloaded components to redirect to less-used ones.
Every enterprise server product in the Business Objects product line uses the WEBINTELLIGENCE system. They are:
• WEBINTELLIGENCE
• BROADCAST AGENT
• Zero Admin BUSINESSOBJECTS
• WEBINTELLIGENCE SDK
Yes. Despite the broad range of products using the Business Objects distributed solution, users have a single web-based portal to access all the information they need. The base module for both WEBINTELLIGENCE and BUSINESSOBJECTS, this portal is called INFOVIEW. Intuitive and customizable, it is the users’ personal gateway to their organization’s information capital. It also lets users manage, save, distribute, print and schedule documents for automated processing.
WEBINTELLIGENCE comes in three modules:
• WEBINTELLIGENCE INFOVIEW
• WEBINTELLIGENCE REPORTER
• WEBINTELLIGENCE EXPLORER
The base module of the Business Objects solution is an e-Business Intelligence portal called INFOVIEW, which provides users with a single entry point to all the documents they need. This module is user-customizable, so that their copies of INFOVIEW fit their needs as closely as possible.
INFOVIEW lets users view, refresh, manage and distribute documents, but not create or modify them. To do that, they need the WEBINTELLIGENCE and/or USINESSOBJECTS REPORTER modul es, or BUSINESSOBJECTS installed through a web browser.
The document catalog includes up to three lists containing files they can access:
• The Corporate Documents page contains files that have been saved or uploaded to a document domain in the corporate repository and made accessible to workgroups within the corporation or organization.
• The Personal Documents page contains documents users have saved for their own personal use.
• The Inbox Documents page contains documents other users have sent each user.
WebIntelligence Reporter
WEBINTELLIGENCE REPORTER allows users to create and edit WEBINTELLIGENCE documents. To do this, they use a Java applet or an ActiveX control called the Web Panel, which is automatically downloaded for users to build and edit documents.
WebIntelligence Explorer
WEBINTELLIGENCE EXPLORER allows users to drill in “drillable” WEBINTELLIGENCE documents to analyze data on different levels of detail,
Broadcast Agent
BROADCAST AGENT empowers BUSINESSOBJECTS and WEBINTELLIGENCE users to automatically process and publish their Business Objects documents via the repository, an intranet, or an extranet open to the World Wide Web. BROADCAST AGENT can also automate the use of "Push" technology on the web using channels.
BROADCAST AGENT comes with the Broadcast Agent Console, which allows administrators to track and modify the scheduled automatic processing of documents through BROADCAST AGENT. The Console is also available from BUSINESSOBJECTS so BUSINESSOBJECTS users can monitor the documents they have scheduled with BROADCAST AGENT. It can also be installed and used on any Windows machine on the same sub-net as the server cluster.
WebIntelligence SDK
WEBINTELLIGENCE SDK (Software Development Kit) is an extension of WEBINTELLIGENCE which enables you to customize the look, behavior, and workflow of a WEBINTELLIGENCE deployment. A common use of WEBINTELLIGENCE SDK is to align WEBINTELLIGENCE deployments with current corporate intranet or extranet solutions.
With WEBINTELLIGENCE SDK you can
• Personalize the user interface.
• Embed prompts in web pages. You can determine which prompts are returned depending on a user’s profile and you can determine the results sent back to the user based on their input.
• Add a hyperlink to a document which launches the Web Panel.
• Include ActiveX and other components in web pages. For example, you can display a Microsoft Excel spreadsheet in the same page as a BUSINESSOBJECTS document.
WEBINTELLIGENCE recognizes three types of documents:
• WEBINTELLIGENCE documents
• BUSINESSOBJECTS documents
• Third-party documents
Basically, third-party files are treated just the same as BUSINESSOBJECTS/ WEBINTELLIGENCE files. The differences are as follows:
• When BUSINESSOBJECTS and WEBINTELLIGENCE files are stored in the repository, they include the document ID inside the file. Third-party files are stored as binary files in the repository, these binary files are treated as a "black box" by the system, which cannot look inside the file for the ID. Instead the document IDs of third-party files are stored elsewhere in the repository.
• When you view a BUSINESSOBJECTS/WEBINTELLIGENCE document, you can see the document in your browser, but the document itself is generated on the server, from which an HTML representation is created and sent to your browser. The actual document remains on the server, and is not downloaded
to the client system.
On the other hand, when you view a third-party file, no HTML code is generated. Instead, the binary data is downloaded to the client system, from where it is automatically opened using the application in which it was originally created (e.g., Word, Excel, Acrobat, etc.).
• You cannot create, edit, update, or schedule third-party files from within the WEBINTELLIGENCE system.
• To publish and access third-party files, two new options have been added to WEBINTELLIGENCE INFOVIEW: Upload and Download. This new feature, which allows the WEBINTELLIGENCE system to handle any type of file in much the same way as a BUSINESSOBJECTS or WEBINTELLIGENCE file, is referred to as document agnosticism.
How documents are stored and organized
After you have created a document,
• Corporate documents
If you choose Publish, the document is stored in the repository of your choice as a corporate document. At the same time, you can also schedule the document for automated distribution by BROADCAST AGENT.
• Inbox documents
If you choose Send, the document is stored in the repository, in the inbox of the user or users to whom it is sent. You can also schedule the document for automated distribution to specified users by BROADCAST AGENT.
• Personal documents
If you choose Save, the document is stored in the designated storage area as a personal document.
The WEBINTELLIGENCE system has two separate mechanisms for the storage of documents and temporary system files:
• The WIStorageManager
• Temporary system caches
Distributed Architecture Overview
A distributed architecture is one in which common server resources are shared among the server products, and are distributed over several physical servers. WEBINTELLIGENCE modules, or processes, can run on different machines, and the system automatically recognizes all the machines in the WEBINTELLIGENCE system, as well as the distributed services at runtime.
You can therefore scale up the WEBINTELLIGENCE system as demand grows by adding more servers to the system to share the transaction load and provide failover capabilities. This way, if one server fails, the system automatically redirects requests to another, functioning server in the system. This type of distributed WEBINTELLIGENCE structure is called a cluster.
Clusters contain two types of servers:
• The cluster manager is the central coordinator between all the servers in the system. There must be one and only one cluster manager in a cluster.
Clusters contain two types of servers:
• The cluster manager is the central coordinator between all the servers in the system. There must be one and only one cluster manager in a cluster.
What are Linked Universes?
Linked universes are universes that share common components such as parameters, classes, objects, or joins. Among linked universes, one universe is said to be the kernel or master universe while the others are the derived universes.
A kernel or master universe represents a re-usable library of components. Derived universes may contain some or all the components of the kernel or master universe, in addition to any components that have been added to it.
Approaches to linking universes
You can use one of three approaches when linking universes:
• The kernel approach
• The master approach
• The component approach
posted by dwhfaq | 1:41 PM
<< Home