In Oracle JDeveloper, in the Overview mode of weblogic.xml, select Libraries

Using Declarative Components and Task Flows 25-19 Figure 25–28 Adding the Oracle Rules Editor Component This step enables you to refer to these libraries, but does not deploy these libraries by default. Therefore, the jars are not included in your project WAR file. 7. In the project that has to be deployed where you create the EAR file: a. Add the following lines to the weblogic-application.xml: library-ref library-nameoracle.ruleslibrary-name library-ref b. Add the following lines to weblogic.xml in the project WAR file: library-ref library-nameoracle.soa.rules_editor_dc.webapplibrary-name library-ref c. Deploy the EAR file in the Weblogic server. For more information about creating an EAR file, see How to Create an EAR File for Deployment in Oracle Fusion Middleware Java EE Developers Guide for Oracle Application Development Framework.

25.2.4 What You May Need to Know About the Custom Permissions for the Rules Editor Component

For the role based authorization, Rules DC implements custom JAAS permissions extending oracle.adf.share.security.authorization.ADFPermission class to ensure that the permission can be used by ADF Security. If a Rules Editor application supports ADF security, which means there is support for role-based authentication and authorization, then security is enforced by implementing custom JAAS permissions by extending the oracle.adf.share.security.authorization.ADFPermission class to ensure that the permission can be used by ADF Security. You have to create ADF security policies by granting the following permissions to the user roles based on your application requirement: ■ oracle.rules.adf.permission.AddRulePermission: Displays Add Rule button; if the permission is not granted, the Add Rule button is not visible to the user. 25-20 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite ■ oracle.rules.adf.permission.DeleteRulePermission: Displays the Delete Rule button; if the permission is not granted, the Delete Rule button is not visible to the user. ■ oracle.rules.adf.permission.EditRulePermission: Displays the Edit Rule button for rules inside a ruleset; if the permission is not granted, then the rules are View-Only. ■ oracle.rules.adf.permission.AddDTPermission: Displays the Add Decision Table button; if the permission is not granted, the Add Decision Table button is not visible to the user. ■ oracle.rules.adf.permission.DeleteDTPermission: Displays the Delete Decision Table button; if the permission is not granted, the Delete Decision Table button is not visible to the user. ■ oracle.rules.adf.permission.EditDTPermission: Displays the Edit Decision Table button for decision tables within a ruleset; if the permission is not granted, the decision tables are View-Only. ■ oracle.rules.adf.permission.RulesEditorPermission: A global permission that sets all the preceding permissions to true. For example, to grant the delete rule permission to a role, specify the following code in the jazn-data.xml file of the application: grant grantee principals principal classoracle.security.jps.service.policystore.ApplicationRoleclass namerole2name principal principals grantee permissions permission classoracle.rules.adf.permission.DeleteRulePermissionclass nameDeleteRulePermissionname actionsaccessactions permission permissions grant If you do not want to use the individual permissions, such as AddRulePermission or DeleteRulePermission, you can just set the RulesEditorPermission in the jazn-data.xml file to set global permissions.

25.2.5 What You May Need to Know About the Supported Tags of the Rules Editor Component

This section lists the tags and attributes that are supported by the Rules Editor component. Table 25–1 lists the supported facets.