Logical Servers

Edit online

Logical servers represent Optimize components. Optimize may contain one or more components that provide a specific function or process. For example, the Analytic Engine is an Optimize component, and its primary function is to analyze business, system, and process data.

During the environment configuration process, each logical server is mapped to one or more physical servers. Mapping logical servers to physical servers allows processes to be shared where physical infrastructure differs. For example, you could run two or more Analytic Engine processes on the same physical server. Each logical server also might have network endpoints and local configurations specified. When you deploy a configuration instance, the My webMethods Define Environments page uses the logical-to-physical server mapping to know where to deploy all of the defined configuration files to the product component.

Each logical server contains subcomponents that also can be configured using the My webMethods Define Environments page.

Logical Server Subcomponents

Edit online

Each logical server contains a set of configurable subcomponents.

The following table lists the webMethods components and subcomponents that the My webMethods BAM configuration functionality supports.
webMethods Product Supported Logical Servers Supported Logical Server Subcomponents
Optimize Analytic Engine The following Analytic Engine subcomponents are configurable through the My webMethods Define environments page:
  • Analytic Engine settings
  • Database settings
  • Data maintenance settings
  • Event Publication settings
  • JMSEventAction settings
  • JNDI configuration
  • Journal logging
  • Mail settings
  • Monitor behavior settings
  • Process Tracker settings
  • SNMP alert settings
  • Station settings
  • WS action settings
  Web Service Data Collector The following Data Collection Service subcomponents are configurable through the My webMethods Define environments page:
  • Data collector settings
  • JNDI configuration
  • Journal logging
  Infrastructure Data Collector The following Infrastructure Data Collector subcomponents are configurable through the My webMethods Define environments page:
  • Adabas SOA Gateway (Deprecated) resource module settings
  • Apama (Deprecated) resource module settings
  • Broker resource module settings
  • Collector settings
  • Com-plete (Deprecated) Resource module settings
  • EntireX resource module settings
  • ETS resource module settings
  • Integration Server resource module settings
  • JNDI configuration
  • MashZone NextGen (Deprecated) resource module settings
  • IBM My webMethods Server resource module settings
  • Presto (Deprecated) resource module settings
  • Terracotta resource module settings
  • Universal Messaging Cluster resource module settings
  • Universal Messaging resource module settings
Integration Server Informational only. Integration Servers provide an endpoint connection to the Analytic Engine.
JMS Server Informational only. The JMS Server provides an endpoint connection to the Analytic Engine.
IBM My webMethods Server Informational only. IBM My webMethods Server provides an endpoint connection to the Broker Server (deprecated).