Each BusinessEvents Archive resource in a project configures deploy-time settings for one inference agent or one query agent. A BusinessEvents Archive resource exists within an Enterprise Archive resource (EAR). The EAR is a standard TIBCO Designer component that is required to create an EAR file for project deployment (see TIBCO Designer User’s Guide for details).
For a query agent, you specify input destinations and startup and shutdown actions. On the Object Management tab, you specify the query agent group name.
Projects saved in TIBCO BusinessEvents Enterprise Suite are not intended for use with BusinessEvents Inference Edition.
Global Var? The name to appear as the label for the resource. (This name does not have to follow rules for identifiers, which are explained in the section Identifiers (Names) in TIBCO BusinessEvents Language Reference.) On the Rule Sets tab, you specify which rule sets you want to include in the deployed project, all rule sets or a selection of rule sets:The main reason to choose a selection of rule sets is to configure multiple inference agents, dividing the rule sets between the BAR resources as appropriate. You can include multiple inference agents in one EAR, or deploy multiple EAR files, each with differently configured inference agents.You can enable and disable destination listeners. You can also specify a function for use as a preprocessor by the destination. (Destinations are configured within the Channel resource. For information about configuring destinations, see Chapter 2, Working With Channels and Destinations.)
Global Var? Project path to the destination (that is path to the destination in the design-time project). This field is for information only. You can’t change the value. BusinessEvents checks the Default checkbox if the following is true:
● This destination is used as the default destination for an event AND Check the Enable checkbox to enable this destination listener for deployment. Uncheck to disable this destination listener for deployment. It will be unavailable in the deployed project. Specifies the rule function used as the preprocessor for messages entering this destination.Specifying a preprocessor is optional. If you specify a preprocessor, also specify worker thread settings. Specifies the number of worker threads to use for the preprocessor.See Worker Threading and Queue Options for more details and a discussion of the advantages and disadvantages of each option.Shared Queue and Threads Uses the BusinessEvents system-wide shared queue and threads. See Shared Queue and Threads Properties for related property settings.Caller’s Thread Uses the thread (and queue size) provided by the channel resource client.Dedicated Workers (Numbers 1-8) Specifies a number of worker threads for the input destination. Also specify the Queue Size.A value is required and used only if a preprocessor is specified. Specifies the queue size of each worker thread, if you choose a number of workers from 1-8.A value is required in this field only if the Workers field specifies a numeric value.You can add rule functions to the Startup/Shutdown tab to perform startup and shutdown actions. You can use only rule functions that take no argument and whose Validity field (in the rule function’s Configuration tab) is set to Action. BusinessEvents calls the functions in the order listed. See Working With Startup and Shutdown Rule Functions for more details.The option you select in the object management tab determines how BusinessEvents data is stored, and how the data is protected from failures. Use of the Object Management tab is documented in chapters dealing with the different object management options.
● In Memory (default) The standard JVM memory management features are used. If a machine fails, the data is lost. For In Memory, no additional configuration is required. In Memory object management is documented in Chapter 15, Configuring In Memory Object Management.
● Persistence Backs up data at checkpoint intervals to an internal database. See Chapter 16, Configuring Persistence Object Management.
● Cache Different caching options provide for various levels of failover and failback, using different deployment architectures. see Chapter 14, Understanding Object Management and Fault Tolerance and chapters following. See Table 27, Cache Cluster Properties (Sheet 1 of 3) for the reference table explaining the cache options.
Copyright © TIBCO Software Inc. All Rights Reserved.