Overview
|
|
You can configure the underlying settings for the Enterprise Gateway using the
Tasks -> Manage Settings menu option
in the Policy Studio main menu, or the Settings node in
the Policy Studio tree. The following tabs are available at the bottom of
the Settings screen.
|
Default Settings
|
|
The Default Settings entered in this screen are applied
to all instances of the Enterprise Gateway that use this particular configuration.
For example, you can change the trace level, timeouts, cache sizes,
and other such global information. For more details, see
Default Settings.
|
Logging
|
|
The Logging settings enable you to configure the default logging behavior of
the Enterprise Gateway. The Enterprise Gateway can be configured to log to a database, file,
UNIX syslog, the system console, or the Oracle Logging Console. For more
details, see Logging Configuration.
|
Namespace Settings
|
|
The Namespace settings are used to determine the versions of SOAP, Web Services
Security (WSSE) and Web Services Utility (WSU) that the Enterprise Gateway supports.
For more details, see Namespace
Settings.
|
MIME/DIME
|
|
The Enterprise Gateway can filter MIME messages based on the content types (or MIME
types) of the individual parts of the message. The MIME/DIME settings list
the default MIME types that the Enterprise Gateway can filter on. These types are
then used by the Content Types filter to determine which
MIME types to block or allow through to the back end Web Service. For more
details, see MIME/DIME Settings.
|
Passphrase
|
|
By default, Enterprise Gateway configuration data is stored unencrypted. However, you
can encrypt certain sensitive information, such as passwords and private keys,
using a passphrase. For more details, see
Setting the Encryption Passphrase.
|
Traffic Monitor
|
|
The Traffic Monitor settings enable you to configure the
web-based Traffic Monitor tool and its message traffic log. For example,
you can configure where the data is stored and what message transaction
details are recorded in the log. For more details, see
Configuring Traffic Monitor.
|
Metrics
|
|
The Metrics settings enable you to configure statistics about
the messages that the Enterprise Gateway processes in a database. The Service Monitor
monitoring tool can then poll this database, and produce charts and graphs
detailing how the Enterprise Gateway is performing. For more details, see
Real-Time Monitoring
Settings.
|
Audit Trail
|
|
The Enterprise Gateway generates an audit trail for each of the key actions that occur in the
Policy Studio on configurations, processes, and users (for example, when a user logs in,
or updates configuration). All items are written to a file-based audit trail stored on
the same machine on which the server process is running. For more details, see the
Audit Trail topic.
|
Cache Settings
|
|
If you have deployed several Enterprise Gateways throughout your network, you should configure
a distributed cache. In a distributed cache, each cache is a peer in a group and needs to
know where all the other peers in the group are located. The Cache Settings
enable you to configure settings for peer listeners and peer discovery. For more details,
see the Global Cache topic.
|
Security Service Module
|
|
You can configure the Enterprise Gateway to act as an Oracle Security Service Module
(SSM) to enable integration with Oracle Entitlements Server 10g. The Enterprise Gateway
acts as a Java SSM, which delegates to Oracle Entitlements Server 10g. For example,
you can authenticate and authorize a user for a particular resource against an
Oracle Entitlements Server 10g repository. For more details, see the
Oracle Security Service Module Settings
(10g) topic.
Important Note:
Oracle SSM is required only for integration with Oracle OES 10g. Oracle SSM is
not required for integration with Oracle OES 11g.
|
Kerberos
|
|
You can configure Kerberos settings such as the Kerberos configuration file to the
Enterprise Gateway, which contains information about the location of the Kerberos Key
Distribution Center (KDC), encryption algorithms and keys, and domain realms. You
can also configure options for APIs used by the Kerberos system, such as the Generic
Security Services (GSS) and Simple and Protected GSSAPI Negotiation (SPNEGO) APIs.
For more details, see the
Kerberos Configuration topic.
|
Tivoli
|
|
You can configure how a Gateway Process connects to an instance of an IBM Tivoli
Access Manager server. Each Gateway process can connect to a single Tivoli server.
For more details, see the Global Configuration section in the
Tivoli Integration
topic.
|
|