Overview
|
|
You can configure the underlying configuration settings for the Enterprise Gateway using the
the Policy Studio Settings menu option. You can also use the
Settings and Deploy buttons in the toolbar.
The following configuration options are available.
|
Deploy
|
|
Whenever you make changes to a filter or policy using the Policy Studio,
you must deploy to the Enterprise Gateway for the changes to take affect.
You can use the Settings -> Deploy menu option
or the Deploy button in the toolbar to achieve this.
If the server is processing a number of messages when the deploy command
is issued, all of the messages are processed using the existing policy.
New messages are queued until this batch of messages are completely processed.
When the new policy data has been stored and loaded by the server,
the queued messages are processed using the new policy.
Important:
To deploy to the Enterprise Gateway, the Policy Studio sends a deployment request to
the Enterprise Gateway server. If necessary, you can configure the socket timeout value
for this connection in the Policy Studio Preferences dialog,
available from Window -> Preferences. For more details, see
Policy Studio Preferences.
|
Default Settings
|
|
The Default Settings entered in this dialog 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.
Note:
You can overwrite these settings at the Process level. You can do this by
right-clicking the Process in the Policy Studio tree view, and selecting
Settings -> Custom.
|
Default Logging Settings
|
|
This option enables 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.
|
MIME/DIME Settings
|
|
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 dialog lists 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.
|
Namespace Settings
|
|
The Namespace Settings dialog can be used to determine
the versions of SOAP, WSSE (Web Services Security), and WSU (Web Services
Utility) that the Enterprise Gateway supports. For more details, see
Namespace Settings.
|
Change 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.
|
|