Overview
|
The configuration options on the Preferences
dialog enable you to customize the look-and-feel of the Policy Studio,
to configure the level at which the Policy Studio traces diagnostic output,
and timeout for the Policy Studio's connection to the Enterprise Gateway. Each of
the available settings are discussed in the following sections.
|
Logging
|
You can set the level that the Policy Studio logs output at by
selecting the appropriate level from the Logging
drop-down box. Logging output is written to a file in the
/logs directory of your Policy Studio installation.
|
Show Management Services
|
The Enterprise Gateway exposes certain interfaces that are purely used for management purposes
only, and should only be edited under strict advice from the Oracle Support team.
By default, the Management Services policies and interfaces, and the
Policy Center interfaces and server process are hidden from view in the Policy Studio.
You can display them by selecting the Show Management Services
checkbox.
When this setting is enabled, you can view the Management Services
policy container in the Policies tree. Similarly, the Management
Services HTTP interfaces are displayed under the Server Process in the
Services tree. If you are running Policy Center, the Policy Center
Service is displayed in the Services tree. The Policy Center Server
Process is also displayed on the Enterprise Gateway Dashboard tab.
For more details, see
Note on Management Services.
Important Note:
As stated earlier, you should only modify Management Services under
strict advice and supervision from the Oracle Support team.
|
Policy Colors
|
The Policy Colors page allows you to customize the
look-and-feel of the Policy Canvas in the Policy Studio. For example, it
is possible to alter the colors of the following components:
-
Policy Background:
Changes the background color of the Policy Canvas.
-
Missing Attribute:
You can right-click the Policy Canvas, and select Show All
Attributes from the context menu. When this is selected,
each filter displays the list of required and generated message attributes
that are relevant for that filter. If a required attribute has not been
generated by a previous filter in the policy, the attribute is highlighted
in a different color (red by default). You can change this color by selecting
an appropriate color using this setting.
-
Success Path:
You can change the color of the Success Path link using this
setting.
-
Failure Path:
Similarly, you can change the color of the Failure Path link here.
-
Show Link Labels:
If this option is selected, a Success Path will be labeled with the
letter S, while a Failure Path will be labeled F.
|
Server Connection
|
When an update is made to a configuration setting in the Policy Studio,
the update is stored locally until you deploy it to the Enterprise Gateway.
After making one or more configuration updates, you can deploy to the
Enterprise Gateway by selecting Settings -> Deploy in the
main menu. Alternatively, you can click the Deploy
button in the toolbar, or press F6.
The updated configuration is then pushed to the Enterprise Gateway, which
finishes processing any current messages before flushing its cached
policy configurations. The new configuration is then stored and
loaded. Any subsequent messages received by the Enterprise Gateway then
use the new configuration.
When deploying to the Enterprise Gateway, the Policy Studio sends a deployment request
to the server. If necessary, you can configure the socket timeout value for this
connection in the Policy Studio Preferences dialog. Enter the
timeout value in milliseconds in the Server Socket Connection Timeout
field.
|
WS-I Settings
|
Before importing a WSDL file that contains the definition of a Web Service
into the Web Services Repository, you can test the WSDL file for compliance
with the Web Service Interoperability (WS-I) Basic Profile. The WS-I
Basic Profile contains a number of Test Assertions
that describe rules for writing WSDL files for maximum interoperability
with other WSDL authors, consumers, and other related tools.
The WS-I Settings are described as follows:
WS-I Setting |
Description |
WS-I Tool Location |
Use the Browse button to specify the full path to
the Java version of the WS-Interoperability Testing tools (for example,
C:\Program Files\WSI_Test_Java_Final_1.1\wsi-test-tools ).
The WS-I testing tools are used to check a WSDL file for WS-I compliance. You
can download them from www.ws-i.org.
|
Results Type |
Select the type of WS-I test results that you wish to view in the generated
report from the drop-down list. You can select from all ,
onlyFailed , notPassed , or notInfo .
|
Message Entry |
Specify whether message entries should be included in the
report using the checkbox (selected by default).
|
Failure Message |
Specify whether the failure message defined for each test
assertion should be included in the report using the checkbox
(selected by default).
|
Assertion Description |
Specify whether the description of each test assertion should be
included in the report using the checkbox (unselected by default).
|
Verbose Output |
Specify whether verbose output is displayed in the Policy Studio console
window using the checkbox (unselected by default). To view the console
window, select Window -> Show Console
from the Policy Studio main menu.
|
For details on running the WS-I Testing Tools, see the
Web Service Repository or
Global Schema Cache topics.
|
|