Configuration Task | Description |
CentraSite communication configuration | You must define the communication parameters required for Mediator to exchange data with CentraSite. See Configuring Communication with
CentraSite. |
EDA destinations for publishing run-time events and metrics | Mediator can use EDA to publish run-time events and metrics to a database or a messaging server such as webMethods Universal Messaging. See EDA/Database Configuration for Publishing Run-Time Events and
Metrics. |
SNMP server destinations for publishing run-time events and metrics | Alternatively, Mediator can use the CentraSite SNMP server or a third-party SNMP server to publish run-time events and metrics. See SNMP Destinations for Run-Time Events. |
SMTP server destinations for sending alerts and logging transaction payloads | You can configure Mediator to:  Send monitoring alerts to an SMTP email server when user-specified performance conditions are violated.Log the payloads of all transactions to an SMTP email server. |
Load balancing URL configuration | Load balancing enables Mediator to distribute messages it receives between a set of listed endpoints. You can set Mediator to use either HTTP or HTTPS protocols for load balancing. See Load Balancing Configuration. |
Keystore and truststore configuration | Keystores and truststores are required for message-level security. They provide SSL authentication, encryption/decryption, and digital signing or verification services for all message content that Mediator sends. See Configuring Keystore. |
Ports configuration | You can specify one or more HTTP or HTTPS ports on which Mediator and the deployed virtual service is available. See Configuring Ports. |
Global service fault response configuration | Configure the format and content of global service fault responses that are returned to consuming applications. See Configuring Global Service Fault Responses. |
SAML support in Mediator | You can configure Mediator to act as a Security Token Service (STS) client. See Configuring SAML Support in
Mediator. |
WS-Addressing configuration | Implement WS-Addressing using Mediator, so that clients can send WS-Addressing information to native services. See WS-Addressing Processing in
Mediator. |
GZIP configuration | Reduce the volume of data that is sent by native services' SOAP responses. Mediator can compress the responses based on the transport encoding (the Accept-Encoding and Content-Encoding headers). See Mediator's GZIP Functionality. |
Custom Content-Type configuration | You can specify custom Content-Types for REST services. See Configuring Custom Content-Types. |
OAuth2 inbound processing | Describes how to configure your system for OAuth2 inbound processing. See OAuth2 Inbound Configuration. |
