To define OSM general preferences, from the Window menu, select Preferences, then expand Oracle Design Studio in the Preferences navigation tree, and then select Order and Service Management Preferences.
Defining Build-and-Deploy Modes for Automation Plug-ins
This field is only relevant for cartridges targeted to OSM server versions between7.0.3 and 7.2.4.x. Prior to 7.0.3, only Legacy mode is used. From 7.3 onward, only Optimized mode is used.
In the Automation plug-in Build and Deploy Mode field, specify whether you want OSM to process all automation plug-ins in a common (oms.ear) EAR file (by selecting Optimized (Default)), process each automation plug-in in its own EAR file (by selecting Legacy), or build the automation components required for OSM to process automation plug-ins in either Optimized or Legacy mode according to the automation plug-in dispatch mode defined on the OSM server (by selecting Both (Allow server preference setting to decide)). For more information on automation plug-in build-and-deploy modes, see "Defining Build-and-Deploy Modes for Automation Plug-ins."
Setting the Problem Marker Severity for Automation Task Name to Plug-in EJB Discrepancies
In the Automation Plugin EJB Name Compliance Level list, specify whether you want Design Studio to display an Error or Warning problem marker when there is a discrepancy between the automation task entity name and an associated external plug-in EJB name. If such a discrepancy occurs, you can use the Quick Fix option from either the warning or error problem marker to revert the plug-in EJB name to match the automated task name.
When installing Design Studio, you can use the install.bat script to install the Design Studio features and configure the environment automatically. If you use this script, it will automatically install the necessary libraries and configure the fields below. See Design Studio Installation Guide for more information about installing Design Studio and using the script.
If you install Design Studio without using the script, or if you want to change any of the values after the install, see the information in the table below.
| Field | Use |
|---|---|
| WebLogic Home | Specify the installation directory for WebLogic (for example, C:\Oracle\Middleware\wlserver).
If you are using Design Studio on a system that does not already have the correct version of Oracle Middleware on it, consult the software requirements in OSM installation Guide for information about the correct version of the application server to install, and then consult Fusion Middleware Installation Guide for Oracle WebLogic Server for information on installing the core WebLogic software. Do not install a WebLogic domain for Design Studio, which only needs the core software. |
| Java SDK Home | Specify the installation directory for the Java JDK (for example, C:\Program Files\Java\jdk1.7.0_85). Select the JDK in the WebLogic Server installation. |
| OSM SDK Home | Specify the installation directory for the OSM SDK (for example, C:\OSM\SDK).
If you are using Design Studio on a system that does not already have the correct version of the OSM SDK on it, first ensure that you have unpacked the correct version of JBoss on your machine. Then run the OSM installer on your machine, selecting a Custom Installation and then selecting only the SDK and (if desired) SDK Samples options when asked to select components to install. See OSM Installation Guide for information about the correct version of JBoss to use and for more information about running the installer. You should specify the location of a version of the SDK that is compatible with the value for Target Version that you are selecting in your projects. See "Project Editor Properties Tab" for more information about the Target Version field. |
Defining Orphaned Task Reference Preferences
In the Delete Orphaned Task References with Activity field, specify whether you want to delete related task entities when removing tasks from the Process editor. When you enable this option and delete tasks in the Process editor, the system checks whether deleted tasks are referenced elsewhere in the workspace. If no task references exist in the workspace, the system displays a list from which you can select related entities for removal.
Defining Order Template Inheritance Preferences
When you enable order template inheritance preferences, when an order is extended, the significance and keys defined on the order are inherited; that is, significance and keys are included in the information from the base order. In addition to keys and significance defined on the base order being inherited on the extended order, the significance of an inherited data element within the order template is also inherited from the OSM entity that contributes it. If these preferences are not enabled, the significance of an inherited data element within the order template is inherited from the data schema rather than from the OSM entity that contributes it.
Offering inheritance within the order template for inheriting significance and keys enables a level of inheritance that is more complete and increases development convenience. As such, enabling these preferences is recommended for new cartridge development. If you are upgrading existing cartridges, refer to the discussion on order template inheritance and upgrade impacts in OSM Installation Guide before enabling these preferences.
To define order template inheritance preferences:
From the Window menu, select Preferences.
The Preferences dialog box is displayed.
In the Preferences navigation tree, expand Oracle Design Studio and then select Order and Service Management Preferences.
In the Order Template Inheritance area, define your order template inheritance preferences.
When an inherited data element in the order template has its significance set as Inherited, enabling and disabling the preference for significance inheritance from order contributors works as follows:
Disabled: Significance is inherited from the data schema.
Enabled: Significance is inherited from the order template of the data contributor(s). Note that if the significance of the data contributor is set as Inherited, it inherits its significance from the data schema.
Click Apply and then click OK.
Design Studio saves your preferences.