My webMethods Server Database Components

My webMethods Server, with or without Task Engine, the user interface for Monitor, Optimize, or Trading Networks, or the Central User Management package for Integration Server

The Central User Management package and the Common Directory Service Support runtime library for Integration Server, to use with the Integration Server Administrator user interface (preview feature).

My webMethods Server writes data about deployment, configuration, security, portal pages, and run-time operations to this database component. It uses this data to manage the My webMethods user interfaces (for example, the user interfaces for Monitor, Optimize, and Trading Networks) and to support central user management in Integration Server.

The Task Engine on My webMethods Server and the Task Engine on Integration Server write task status, task distribution, and business data. The Task Engine on My webMethods Server displays this data in its user interface in My webMethods. The Task Engine on Integration Server displays this data in its gadgets in Business Console and in a Task Engine browser-based user interface.

If you are clustering My webMethods Servers, create a single MywebMethodsServer database component for the cluster to share. If you are not clustering, create a MywebMethodsServer database component for each My webMethods Server.

The CentralConfiguration database component is automatically created when you create the MywebMethodsServer database component. If you are using Optimize, the CentralConfiguration database component stores the Optimize configuration information you enter in the Central Configurator interface in My webMethods. The CentralConfiguration database component is not automatically dropped when you drop the MywebMethodsServer database component. If you want to drop the CentralConfiguration database component, you must do so manually.