The following procedures show to bring a Decision Service under management
either as an independent Decision Service, or as a member of an Application.
Note: As the general steps are common to both
adding and editing a Decision Service, this topic focuses on the tasks when adding a
Decision Service, and then shows how to access a Decision Service to edit it.
To add a Decision Service:
Connect to the Web Console server where you want to add Decision
Services.
Click the Decision Services button:
Click + Add Decision Service:
The Add a new Decision Service dialog box
opens:
You can choose to create an Application for the Decision Service you
are adding:
If you choose that option and click OK,
the New Application dialog opens:
Enter a Name and Description.
Choose the server or server group where the Application's
Decision Services are to be deployed.
Set options that will apply to all Decision Services in the
Application.
Click + Add for each Decision Service
you want to add to the Application.
On either path, the New Decision Service
dialog box opens at the Decision Service tab:
Enter a name. Note that this will be its name when deployed, not
the name of the EDS file you choose.
Add a description.
Click Choose file to locate an EDS
file.
Choose a server or server group
If you started this process as a single Decision Service, you
can choose to add it to an existing application from the list that will be
offered.
Click the Datasource tab to access its
options:
Datasource Configuration
File: Specify the XML file that contains the data source access
properties. To learn how to generate this file from Corticon Studio, see the topic:Export the Datasource Configuration
file
.
You can change the EDC Access Mode
option to either Read Only or
Read/Update to extend the dialog tab to display additional configuration
settings:
In the EDC Access Mode, choose the
appropriate access option. This setting controls how a Decision Service will
access connected databases. Select Read
Only or Read/Update to then
expose additional settings that you need to configure:
EDC Entities Returned
Mode: Choosing All
Entities returns all records from the database when the
Decision Service executes. Choosing Incoming and
New Entities returns entities that were in the request
message and only those entity records that are added or modified in the
database when the Decision Service executes. Select the appropriate
option.
EDC Caching:
Database caching enables Corticon to store often-used data in a cache. This
improves the performance of the Decision Service since it can read and write
data in the cache faster than if this data was in the database. If you
choose Enabled, database caching will
be enabled for the Decision Service. To learn more about database caching,
see the topic: How to work with database
caches.
Important:Turning caching on
or off - If you want to enable or disable caching on a deployed
Decision Service, the mechanisms of caching require that you undeploy and
delete the Decision Service, and then add and deploy the Decision Service
again with the cache enablement setting you want.
Click the Advanced tab to access its options:
Consult the Server Guide for more information about these
settings.
In the Maximum Pool Size field, specify
how many execution threads for this Decision Service will be added to the
execution queue. If you leave this field blank, the Web Console will set a default
value of 1.
In the XML message style section, choose
whether request messages for this Decision Service should contain a Flat or Hierarchical payload
structure. Auto Detect accepts either style.
Click Save to store the Decision Service but
not deploy it. Click Save & Deploy to store the Decision
Service and also deploy it. Click Cancel to close without making
changes.