IBM Support

Known limitations in WebSphere Business Rules Management System V7.1.1

Question & Answer


Question

This document lists the known limitations in each Fix Pack in V7.1.1. For each documented limitation it provides a comment or workaround.

Cause

Fix Pack 5 (7.1.1.5)


Fix Pack 4 (7.1.1.4)


Fix Pack 3 (7.1.1.3)


Fix Pack 1 (7.1.1.1)



Known limitations and issues in V7.1.1.5



Rule Studio

Errors

Comments and workarounds
Writing an IlrXMLObject result of an execution by using the IlrXmlDataDriver generates text
where the schema file name and location are escaped to HTML by using the characters &#xxxx, and are no longer in the original encoding of the string. This problem is identified as APAR RS00844.
The engine property ilog.rules.xml.stringFullEncoding must be set to false to prevent the name space encoding.
You have two options to set this property:
1) Use an engine configuration file to create a file containing the following lines:
node ilog.rules.xml
{
element stringFullEncoding = false;
};

Then reference this file in Rule Studio in the ruleset properties. Finally in a Java application, it is enabled as explained in the product documentation: Decision Server Rules V7.5 > Developing rule projects in Rule Designer > Optimizing execution > Configuring the rule engine.
2) Configure using an API. If you prefer controlling this property within your application code, you need to change the way you create your IlrXmlDefaultDataDriver with the following code:

IlrResources encodingResource = new IlrResources();
encodingResource.putBoolean( "ilog.rules.xml.stringFullEncoding", false);
IlrXmlDefaultDataDriver driver = new IlrXmlDefaultDataDriver ( context.getRuleset().getReflect(),  encodingResource);


Then use this driver to write your IlrXMLObject.



Rule Execution Server .NET

ErrorsComments and workarounds
After the installation of RES.NET, the user may not be able to deploy a rule project to the local RES because of this error message:

Service cannot be started. TargetInvocationException: Exception has been thrown by the target of an invocation. ---> ApplicationException: RESMS_ERROR_0018: Management initialization failed. An error occurred when trying to access the Persistence Service. ---> EndpointNotFoundException: Could not connect to net.tcp://localhost:8102/PersistenceService/. The connection attempt lasted for a time span of 00:00:00.9218750. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:8102. ---> SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:8102
at DoConnect(EndPoint endPointSnapshot, SocketAddress? socketAddress)
at System.Net.Sockets.Socket.Connect( EndPoint remoteEP)
at SocketConnectionInitiator?.Connect( Uri uri, TimeSpan timeout)

You must start RES manually:
  1. In Command Prompt, open the Windows Services console by entering services.msc and pressing Enter.
  2. Start the ILOG Rule Execution Management Service.
  3. Set it to automatic.



Rule Authoring

ErrorsComments and workarounds
In complex operations where the order of parameters infers on the type, the BigDecimal cast fails.Verbalize a casting methods through B2X.
The drop-down completion menu in the Intellirule editor might contain items from several domains in your BOM.To resolve the problem, see Unexpected values in domain drop-down


Known limitations and issues in V7.1.1.4



Rule Studio



ErrorsComments and workarounds
The following API should not be public:
Interface:
  • ilog.rules.studio.model.builder.
    IlrFormattableCodeConverter
Classes:
  • ilog.rules.studio.model.
    IlrStudioModelPluginPreferenceInitializer
  • ilog.rules.studio.ui.dialogs.wizards.templates.
    IlrNewRuleProjectTemplatePluginContentWizard
  • ilog.rules.studio.res.ui.generator.impl.wizard.
    IlrAbstractRESConfigurationSelectionDialog.
    SafeWorkbenchLabelProvider
Do not use.
BOM Update does not handle generics correctly.Ignore the action related to generic classes that are not found in the XOM, the actions are erroneous.
Errors in IRL transition are not reported in the ruleflow editor Diagram view.Errors in IRL are reported in the problems view and the IRL view of the ruleflow editor.
Prefer using BAL to write transition.
If Rule Studio automatic build is disabled, problems in a ruleflow are only reported in the Problem View, and not in the ruleflow graph.Close and reopen the Ruleflow Editor to update the graph with the errors.
Cut, copy and paste do not always work as expected in the Ruleflow Editor. If the Edit > Paste command does not work, use Ctrl+V to complete the operation.
Shortcuts do not work in the documentation, use the right-click menu.
In a ruleflow, if you join two transitions with a branch node a compilation error is thrown,Remove the branch node and connect the transitions directly to the next task.
If a rule and a decision table have similar names, a naming conflict is detected during ruleset parsing.Rename the rule so that the generated name of the decision table does not conflict with it.
When refactoring a ruleset parameter name, templates that use this name are not refactored.Refactor the rule templates manually using the errors reported.
The "ruleflows which may select this rule" query does not find results if a ruleflow contains a subflow. Do not use this query if you have subflows.
GB 18030 Phase 2 characters are lost when pasting from an external source into the Condition Column window in Rule Studio. Do not copy GB 18030 Phase 2 characters in a decision column editor.
In BAL, when assigning a literal value to an attribute of type java.lang.Float, the literal is considered as a double (15.5d) and then cast to a float. This causes a rounding error. Use either the float or the double attribute.
In the Decision Table Editor, when you select a double/float value and use the auto-filled value (drag the lower right corner of the cell and select the destination rows), some of the auto-filled values are not precise.
For example, if the original value in the first row is 1.39, the auto-filled value in the second row becomes 1.3899999999999997.
This problem only happens to some auto-filled values. To resolve the problem, either manually adjust the erroneous values or avoid using the auto-fill feature.
A class that has the same name as a package can lead to a LinkageError exception during ruleset parsing if you use this package to initialize a parameter value.Remove the reference to the package in the method used to initialize the parameter.
You cannot edit rules created in a locale that is different to the Rule Studio locale. Parameters and variables cannot be found in this case.Only use Rule Studio in the locale of the project that you intend to edit. Do not mix rules in different locales in the same rule project.
If an automatic variable and a parameter have the same name, conflicts are detected when writing rules. Sometimes the incorrect variable is used in the translated IRL.Either disable the automatic variable or rename the parameter or local binding to avoid the conflict with the automatic variable name.
There is an issue regarding dynamic domains when migrating rule projects from JRules V6 to V7.1. There is a difference in the way dynamic domain elements are deprecated between V6.7 and V7.
  • In V6.7, the element is noted as deprecated in both the .voc and the .bom files.
  • In V7, it is only noted in the .bom file.

If you deprecate an element in V6.7, migrate the project to V7, then restore the element in the domain. In V7, the element remains as deprecated unless you remove the deprecated property from the .voc file.
Business rules written in Simplified Chinese that use Date.isAtDayTime() in a previous version of JRules raises a build error in JRules V7.1.1.3. An error is raised because the verbalization has changed. If you see this error in a migrated project, fix the business rules using the new verbalization. The word 事件 must be changed to 时间.
Ruleset Properties PanelIn JRules V7.1, ruleset properties entered in the Ruleset Properties Panel require double quotes around a java.lang.String type. Other types should not be enclosed in quotes.
After importing a rule project from a previous version of JRules into Rule Studio, you must modify the ruleset properties in each of the migrated rule projects to comply with this new notation.
There are some known bugs related to the management of JDK generic classes. These bugs generate a NullPointerException or ClassCastException in Rule Studio.If you get one of these exceptions while using Rule Studio, and if the associated Java stack contains references to the XOM or to the BOM to XOM mapping, you can resolve the problem by adding a file named engine.conf to your rule project. The engine.conf file should contain the following code:

node ilog.rules.engine
{
element enableGenerics=false;
};

This file can be added in your rule project using the Ruleset Project Properties dialog.
When exporting a report with a chart or other images to the Microsoft Excel format, the charts and images are not displayed in the exported file. BIRT allows you export reports to different formats (.pdf, .ppt, .xls, and so on). However, there is a bug that prevents the export of images to Excel, therefore if you have a ruleflow or decision table, they are not exported to Excel. This is a known limitation in BIRT referenced in Bugzilla as Bug 198623. To workaround this issue, manually copy and paste the charts and images from the source report to the exported Excel file.
Some Microsoft Excel add-ins prevent Microsoft Excel 2007 files from being opened within Rule Studio. Although not strictly related to Rule Studio, you may encounter this incompatibility between Eclipse and Microsoft Excel 2007. If you do, try disabling or uninstalling Excel add-ins.
SUN and IBM JDK limitations prevent Eclipse from running the Run and Debug launch configurations on projects that contain Japanese, Korean, Chinese (simplified and GB18030 encoding) characters.This is a known limitation in Eclipse Java development tools (JDT) referenced in Bugzilla as Bug 32206 and in the SUN Bug Database as Bug 4947220. To workaround this issue, take one of the following actions:
  • Use a localized Windows platform. For example, Windows localized in Japanese.
  • Use an international Windows platform with the following Regional and Language Options settings:
  • Regional Options tab: Standards and formats set to your locale, for example Japanese.
  • Advanced tab: Language for non-Unicode programs set to your locale, for example Japanese.
No support for IPV6 in JRulesThere is a limitation in the commons-httpclient library that is embedded preventing synchronization with Rule Team Server and publication to Rule Execution Server from working properly when IPV6 addresses are used.


Rule Studio for .NET



ErrorsComments and workarounds
The date format for parameters in a decision table are not localized. The parameters are always displayed in English.
Priority values are not checked during synchronization between Rule Studio and Rule Team Server.During synchronization, Rule Studio does not check that a value entered for a priority is a valid value.
Verbalizers are overwritten when installing different versions of Rule Studio on the same machine.This issue may arise when you install an update of Rules for .NET V7.1.1.3. We recommend you uninstall any previous version before installing an update.

If two different versions of Rule Studio for .NET are installed on the same machine, the verbalizers registered on the machine registry are overwritten by the latest installation. Therefore, in the first installation, only English languages are available in the language options. To repair this installation issue:

  1. Click Start > Control Panel, and then open Add or Remove Programs.
  2. In the Add or Remove Programs window, locate and click the entry for ILOG Rule Studio for .NET, and then click Change.
    The ILOG Rule Studio installation wizard appears.
  3. Click Repair ILOG Rule Studio for .NET, and then click Finish.
    Your installation is repaired and the verbalizers are re-registered.
The following message appears when publishing in the Rules for .NET Getting Started: "The Rule Team Server and Rule Studio extensions are not consistent, which may lead to problems when you try to edit rules." You can safely ignore this message when you are doing the Rules for .NET Getting Started.
When viewing the Workflow Foundation integration sample, there are errors in the workflow diagram. For example:
Error 1 Path resolved to Referenced activity Property 'Status' whose PropertyType 'WorkflowApplication. Eligibility.Status' does not match with the Target Type 'WorkflowApplication. Eligibility.Status'. 0 0
Error 1 Path resolved to Referenced activity Property 'RentalAgreement' whose PropertyType 'WorkflowApplication. Pricing.RentalAgreement' does not match with the Target Type 'WorkflowApplication. Pricing.RentalAgreement'. 0 0
These errors are resolved when you build the workflow.
The reference for the documentation and tutorials is the English version. If you have difficulties following any part of the localized documentation or tutorials, refer to the English version for clarification.You can change the language of the information center using these instructions:
1. Open a browser window and click Tools > Options.
2. Open the Language preferences.
3. Select English [en-us], move this language to the top of the list, and then click OK.
4. When you are finished, clear the cache to ensure that when you open the help system you see the refreshed files.
Integrated help is not available from Rule Studio when using Visual Studio 2010.The most current version of the documentation is available from the IBM WebSphere ILOG Rules for .NET BRMS information center. The documentation for Rule Studio is based on the Visual Studio 2008 user interface.
The Brazilian Portuguese BAL has been changed in this version.
The <a number> is more than <a number> operator is now translated as à maior instead of é maior.
The previous operator is marked as deprecated. Upgrade your business rules to use the new operator with the corrected translation.
In Visual Studio 2010, when a BOM references an assembly file built from managed C++ code in CopyLocale mode, this assembly file is locked after the build.To unlock the assembly file, close Visual Studio 2010.
If you have custom properties in your rule project, you must create an extension model to publish to Rule Team Server, but this is not documented.Follow the steps described in the following technote.


Rule Solutions for Office



ErrorsComments and workarounds
The shortcut to the Rule Solutions for Office documentation in the Start menu does not work.The language of the OS and the language of Visual Studio and Office must be the same. The documentation is available online here.
Verbalizers are overwritten when installing different versions of Rule Solutions for Office on the same machine.This issue may arise when you install an update of Rule Solutions for Office V7.1.1.2. You are recommended to uninstall any previous version before installing an update.

If two different versions of Rule Solutions for Office are installed on the same machine, the verbalizers registered on the machine registry are overwritten by the latest installation. Therefore, in the first installation, only English languages are available in the language options. To repair this installation issue:

  1. Click Start > Control Panel, and then open Add or Remove Programs.
  2. In the Add or Remove Programs window, locate and click the entry for IBM WebSphere ILOG Rule Solutions for Office, and then click Change.
    The Rule Solutions for Office installation wizard appears.
  3. Click Repair, and then click Finish.
    Your installation is repaired and the verbalizers are re-registered.
Tutorial RuleDocs cannot be edited in Web controlsIf you try and edit the tutorial RuleDocs into a Rules for .NET Web control, the following message is displayed: "The selected rule document contains no rule artifact."
RuleDocs (.docx or .xlsx) must be associated with Microsoft Office Word or Excel and not with Microsoft Word or Excel Viewer.When working with RuleDocs, you must have the correct file association for .docx and .xlsx files. Otherwise you will get errors when trying to edit them.
The reference for the documentation and tutorials is the English version. If you have difficulties following any part of the localized documentation or tutorials, refer to the English version for clarification.You can change the language of the information center using these instructions:
  1. Open a browser window and click Tools > Options.
  2. Open the Language preferences.
  3. Select English [en-us], move this language to the top of the list, and then click OK.
  4. When you are finished, clear the cache to ensure that when you open the help system you see the refreshed files.
A small number of topics that should be localized in this release are only available in English.The translated topics are available on the IBM WebSphere ILOG Rules for .NET BRMS information center.
The tutorials in the Rule Solutions for Office online help are not translated in Portuguese (Brazilian).These tutorials must be followed in English.
The installer reports that Visual Studio Tools for Office Runtime (VSTOR) 4.0 is missing, but you have installed VSTOR.If you installed VSTOR before .NET Framework 4.0, the VSTOR runtime does not use version 4.0 of .NET Framework, but version 3.5. For VSTOR to use .NET Framework 4.0, you must uninstall and reinstall it.


Decision Validation Services



ErrorsComments and workarounds
Cannot test the content in collections of complex type in Excel scenario file templates.The column headings of the Excel scenario file template are defined by the attributes of the BOM class. Each column corresponds to an attribute.
Each attribute for which a test is defined in the Expected Results sheet:
  • must be verbalized, since the name used in the column heading is the verbalization of the attribute
  • must not be a collection of complex type

If the attribute is a collection of simple type (int, String, and so on), the domain must be defined.


Rule Team Server



ErrorsComments and workarounds
In Chinese and Japanese the completion menu of the Web Intellirule Editor does not appear if CTRL+space is used after an ideograph.Insert space characters or use the Guided Editor.
Properties defined in the common model are not visible in the ruleflow. The ruleflow is not a managed artifact in Rule Team Server and does not inherit the common properties. You need to define the properties specifically on the ruleflow element.
If you try to copy or paste some text in the Web Intellirule Editor, an error message explains what you have to do in order to authorize the copy-paste operations in Rule Team Server.
The suggested content for user.js is incorrect, quotes around property names and values are missing.
The correct content to add in user.js is:
user_pref( "capability.policy. policynames", "allowclipboard");
user_pref( "capability.policy. allowclipboard.sites", "localhost:8080");
user_pref( "capability.policy. allowclipboard.Clipboard.cutcopy", "allAccess");
user_pref( "capability.policy. allowclipboard.Clipboard.paste", "allAccess");
When using a DB2 database you could encounter a "Statement is closed" exception at the end of a long ruleset archive generation.Increase the connection timeout: in the WAS administration console, at the data source level, in the "connection pool properties" panel.
The Publish command in Rule Team Server is enabled while a publish of RuleDocs is running. If you publish a second time the resulting file may be corrupted. Click the Publish button once. If the file is corrupted delete the document and republish it.
After synchronizing a rule project with a BOM entry that is deleted and replaced by another BOM entry with the same name, no conflicts are detected. This causes duplication in the Rule Team Server database. Delete the project in Rule Team Server and republish it.
If there are double quotes added to an entry of a collection in the inline cell editor of a decision table, all subsequent operations on the cell use a lot of memory and processor usage is high. As a result it look like the decision table is locked. If you intend to have a double quote in one entry of a collection, use the editor at the top of the decision table to make the modification.
You can also change the value of the ilog.rules.brl.parsing. ErrorRecoveryTimeout parameter to 2000 for example, to get a better response time. The parameter is in the ilog.rules.brl.parsing.parser.earley/ preferences.properties file (in brlparsing.jar).
If you edit a decision table using Internet Explorer 7 in a non-maximized window, the size of a drop down list is limited even though there is extra space after performing the right scroll. This is a limitation of Internet Explorer 7. Maximize the Internet Explorer 7 window and the drop down list displays as expected.
Using the Web Intellirule Editor to edit a rule in a locale that is different from the persistence locale raises an exception on the server if the vocabulary is incomplete.Restart the server. and make sure you have a complete vocabulary for the language. Alternatively, edit with the Guided Editor.
When editing decision tables you cannot select predefined values of a domain directly within a cell. A domain is a set of predefined values in the vocabulary of the project. However, you can add predefined values to your conditions by inserting values from a drop-down list in the conditions editor, which is located above the decision table.To select a predefined value in a cell:
  1. Click the cell, then click the object placeholder in the conditions editor.
  2. Click the necessary placeholders to reach your domain.
  3. Use the drop-down menu to select a predefined value from the domain.
In the Russian locale, the Rule Team Server tutorial projects are not available in Russian, so you must use the projects in English.To open Rule Team Server with the data source in English go to: http://localhost:8080/teamserver?datasource=jdbc/ilogDataSource_en_US.
The Windows shortcut JRules (en_US) > Tutorials > Rule Team Server opens the data source in English.
In the Brazilian Portuguese locale, the Rule Team Server tutorial documentation is only provided in English, The tutorial projects are provided in English in the data source named ilogDataSource_en_US. Note that the tutorial projects are also provided in Brazilian Portuguese in the data source named ilogDataSource_pt_BR, but the English documentation refers to the English projects.To open Rule Team Server with the data source in English go to: http://localhost:8080/teamserver?datasource=jdbc/ilogDataSource_en_US.
The Windows shortcut JRules (en_US) > Tutorials > Rule Team Server opens the data source in English.
The Windows shortcut JRules (pt_BR) > Tutorials > Rule Team Server opens the data source in Brazilian Portuguese.
You cannot have more than one Mozilla Firefox browser connected to Rule Team Server at the same time with different users.This is because Mozilla Firefox shares the default profile among all sessions on the same machine, which means that the data is shared among all browser instances. So, if you are connected to Rule Team Server as rtsAdmin and you want to connect as rtsUser1, you must first sign out from the rtsAdmin session before connecting as rtsUser1.
For more information see this page. If you are an advanced Mozilla Firefox user, you can create different profiles for each Rule Team Server user, as described in this document.
Note that Internet Explorer behaves differently. Different Internet Explorer browsers do not share data, so you can have one Internet Explorer browser connected to Rule Team Server as rtsAdmin, and one Internet Explorer browser connected to Rule Team Server as rtsUser1.
The web installer in Rule Team Server does not work for IBM DB2 for i.Download the SQL scripts generated by the web installer, then run the tables creation script and the data inserting script using the database tool.
The Testing a set of rules tutorial does not work if you have repackaged the SSP .war or the Rule Team Server.war files.
 
To restore the SSP and Rule Team Server files and perform the Testing a set of rules tutorial:
  • Click Restore Server in the Samples Console.
When the number of conditions in a decision table partition is very large, and an otherwise is used in this partition, a Stack Overflow might be raised when compiling the decision table. Avoid the use of otherwise in decision tables that contain a large number of conditions.
In JRules V7 the priority attribute in IlrTechnicalRule has been moved to the IlrRule super class. This change hides custom priority attributes from subclasses such as IlrBusinessRule and its subclasses when you migrate your model.If you defined a custom priority property in IlrBusinessRule or a subclass, using one of the default extensions for example, you must rename this extended attribute in your custom class before you run the migration tool. For example, if your default extension model includes:

<add-property className="BusinessRule">
    <property extractable="true" name="
priority" type="String">
      <annotation id="column-name" value="priority_ext"/>
    </property>
</add-property>


Change the model before migration to:

<add-property className="BusinessRule">
   <property extractable="true" name="
myPriority" type="String">
     <annotation id="column-name" value="priority_ext"/>
   </property>
</add-property
>

In JRules 6.x, upload the modified model using Upload Only in the Rule Team Server Installation Manager. In JRules V7, use the same model to create the new Rule Team Server schema. The custom priority property on your business rules is stored in a new myPriority custom property that can then be copied to the JRules V7 priority property, which is now part of the base rule model.
You cannot redeploy a RuleApp that includes extracted rulesets from one or more common projects.This limitation is identified in the following cases:
  • If you have one rule project from which you extract two different rulesets.
  • If you have two rule projects that depend on a common project.
  • If you have two rulesets that extract different elements from a common project.

To redeploy a RuleApp that matches one of these cases, do one of the following:
  • Download the previously deployed RuleApp archive from the Rule Execution Server Console, and then redeploy it.
  • Generate the rulesets individually in Rule Team Server and upload them in the Rule Execution Server Console one by one.
RuleDocs (.docx or .xlsx) must be associated with Microsoft Office Word or Excel and not with Microsoft Word or Excel Viewer.When working with RuleDocs, you must have the correct file association for .docx and .xlsx files. Otherwise you will get errors when trying to edit RuleDocs, either after publishing from Rule Team Server, or when using the Edit in Rule Solutions for Office option from the rule tables in the Explore tab.


Rule Execution Server



ErrorsComments and workarounds
WebSphere Application Server Community Edition not listed in the list of provided EJB3 rule sessions.EJB3 rule sessions are provided for:
  • WebSphere Application Server Community Edition 2.1
  • WebSphere Application Server 7.0
  • JBoss 4.2
  • JBoss 5.0
  • WebLogic 10.3
The list of parameters in the deployment descriptor for the Rule Execution Server Console has been updated. The list of the parameters in the topic WebSphere ILOG JRules BRMS V7.1 > Rule Execution Server Console online help > Monitoring and managing the server > Configuring the Rule Execution Server Console Web application is not up-to-date. The updated context parameters contained in the /WEB-INF/web.xml file are documented in the file itself. The list of context parameters is as follows:
  • ilog.rules.res.HELP_CONTEXT
    The Rule Execution Server online help context-root.
  • ilog.rules.res.HELP_INDEX
    The Rule Execution Server online help index.
  • ilog.rules.res.HELP_TOPIC
    The Rule Execution Server online help topic.
  • ilog.rules.res.HTDS_CONTEXT
    The Hosted Transparent Decision Services context-root.
  • ilog.rules.res.SSP_CONTEXT
    The default context-root used for ssp.
  • ilog.rules.res.RTS_CONTEXT
    The Rule Team Server context-root.
  • log4j-init-filename
    The LOG4J configuration file.
  • persistenceType
    The persistence type, either data source or file.
  • filePersistenceDirectory
    Used only when the persistenceType parameter is set to file. It is the root directory for the file persistence, this can be an absolute or relative path.
  • ilog.rules.res.trace. DECISIONWAREHOUSE_CONFIGURATIONS
    The list of decision warehouse configurations available in the Rule Execution Server Console. This is a list of names separated with a comma. For each decision warehouse configuration, a <context-param> with the same name must be declared in the web.xml file. The value of this parameter is a string that begins with factoryClassname= FULLY_QUALIFIED_NAME_OF _THE_TRACE_DAO_FACTORY_ FOR_THIS_CONFIGURATION, optionally followed by a semicolon (;) and the list of properties to initialize the trace DAO factory. Each property in the list is defined as PROPERTY_NAME=PROPERTY_VALUE and the properties are separated by a semicolon (;).
  • defaultDWConfiguration
    The default decision warehouse configuration. Traces are saved in the decision warehouse database that is created during the installation of Rule Execution Server.
  • ilog.sam.application
    Specify an application name for SAM.
  • JMX_XU_QUERY_PART
    Specify a subset of XUs visible from the console.
  • JMX_DS_QUERY_PART
    Specify a subset of decision services visible from the console. Possible keys and values depend on the application server. For example, on WebSphere the cell name, node name, and server name are added to MBean object names so you can search for decision services deployed under a specific WebSphere node with node=mynode.
When using Hosted Transparent Decision Services in WebSphere Integration Developer you could experience the following issues:
  • A namespace conflict if you import more than one decision service into a single process.
  • Duplicated business items if you import the WebSphere Process Server data model into the same process module.
For the HTDS integration, use the mediation flow capability of WebSphere Enterprise Service Bus (WebSphere ESB) or microflow (short-running process flow) in conjunction with HTDS. For more information see the Redbook: Integrating WebSphere ILOG JRules with IBM Software.

For the duplicated business items issue, you must generate a HTDS WSDL without the schemas in your rule project. To do that, go to the dynamic object model settings in your rule project, expand the section Schemas to be included in Ruleset archive for enabling the Transparent Decision Service, and deselect All schemas.

Note:
This limitation has been resolved in V7.1.1.3 as described in the section Configuring namespaces in a hosted transparent decision service WSDL of the Documentation Supplement in the README.
If you encounter a decision service runtime exception after migrating from V7.0 to V7.1, it is likely that this is the result of the newly introduced DecisionID element in the WSDL.According to the documentation, a client application that uses the WSDL generated with V7.0 works if you set the Compatibility parameter in the web.xml file of the V7.1 HTDS artifact to "7.0".

<context-param>
   <param-name>Compatibility</param-name>
   <param-value>7.0</param-value>
</context-param>

After this parameter is added, the WSDL generated for a decision service in V7.1 does not include the DecisionID.
An error is thrown if you call a monitored ruleset from a Hosted Transparent Decision Service running on an application server using Sun JDK 1.6. The Sun JDK includes JAXP 1.4, a custom version of Xerces and Xalan, which causes this error.To monitor a ruleset and store the results in Decision Warehouse using Hosted Transparent Decision Services with Sun JDK 1.6:
  1. Repackage the HTDS WAR with the Xalan JAR.
    For example, on Tomcat copy the file xalan-2.7.0.jar from the folder<InstallDir>/executionserver/lib/ into the WEB-INF/lib folder of the file DecisionService.war in the folder <InstallDir>/shared/tools/apache-tomcat/webapps.
  2. Set the monitored.enabled and ruleset.bom.enabled ruleset properties to true.
  3. Deploy the repackaged HTDS archive file and the enabled ruleset to your application server,
  4. Expose the deployed ruleset as a transparent decision service.
  5. Call the decision service from your client application.
Inconsistent return value of IlrUserRuntimeException isInConditions() and isInActions() in different execution modes. 
It has been noted that IlrUserRuntimeException methods isInConditions() and  isInActions() do not return the same value in RETEplus and sequential modes. This apparent inconsistency is because sequential mode and Fastpath mode both perform a deep compilation of the rules. In these circumstances the condition part and the action part of a rule cannot be distinguished anymore at runtime. Any exception thrown from a rule executed in sequential mode or in Fastpath mode is already wrapped in an IlrUserRuntimeException but the isInConditions() and the isInActions() methods of this exception class will always return false


Rule Execution Server .NET



ErrorsComments and workarounds
On Microsoft Windows Server 2008 R2, you may have difficulties to launch the Rule Execution Server Console from a non-administrator account. Edit the <InstallDir>\\Rule Execution Server for .NET\Bin\Management\Rule Execution Server Console.bat file, and change “Rule Execution Server Console.msc” by the full path of this file. This file is in the same directory as the .bat file.
Then, start the Rule Execution Server Console from the Start menu, using a “run as administrator” command, or by launching the “Rule Execution Server Console.bat” file, using the “run as administrator” command.
Note that you can check the “Advanced” section of the shortcut properties and select an option to run it as administrator each time you use it.
When installing Rules for .NET into a folder that contains non-English characters in the name, the rule execution persistence service and the rule execution management services fail to start.The issue comes from the characters encoded in this configuration file :
C:\Program Files\IBM\WebSphere\ILOG Rules for .NETアイウか鯵表噂ソ竹十\Rule Execution Server for .NET\Bin\Public Assemblies\ILOGExecutionServerPersistenceService.exe.config

Add the encapsulating elements to the following line to start the services:
<add key="ILOG.Rules.ExecutionServer.Persistence.BaseDirectory" value="C:\Program Files\IBM\WebSphere\ILOG Rules for .NETアイウか鯵表噂ソ竹十\Rule Execution Server for .NET\Bin\Persistence"></add>
After installing Rule Execution Server, if the performance counters are not available, these could be corrupted on your system.To repair the installation of performance counters:
  1. Repair your system by using the command lodctr.exe /R, or by following the instruction on this page: kb 300956.
  2. Repair the Rule Execution Server installation by opening the Control panel and clicking Repair for IBM WebSphere ILOG Rules for .NET.
In some cases, the ILOG Management Service does not start automatically on Windows Server 2003, and tutorials and samples do not work.The ILOG Management and Persistence Services should start automatically when you start Windows. However, when you start a computer with Windows Server 2003, only the ILOG Persistence Service starts automatically. You need both Services for the samples and tutorials. For information on how to start the Management Service manually, see WebSphere ILOG Rules for .NET V7.1.1.3 Documentation> Rule Execution Server Console online help> Stopping and starting the Management and Persistence Services.
The documentation for configuring the Execution Service for IIS is based on ASP 2.0.
WebSphere ILOG Rules for .NET BRMS V7.1 > Configuring > Configuring Rule Execution Server > Setting up the Execution Service environment > Step 3: Configuring the Execution Service for IIS > Launch the IIS Configuration Wizard
. If you have installed Rules for .NET on .NET Framework 4.0, you use ASP 4.0.
The procedure for configuring the Execution Server for IIS is the same with ASP 4.0.
If ASP.NET 4.0 is not registered with IIS, open the Visual Studio 2010 command prompt or use the aspnet_regiis executable (located in %SYSTEMROOT%\Microsoft.NET\Framework\v4.x for x86 systems, or in %SYSTEMROOT%\Microsoft.NET\Framework64\v4.x for x64 systems).
The MMC Console does not run under CLR 4.0, which is mandatory to run Rule Execution Server Console when built with .NET Framework 4.0. As a consequence, the Rule Execution Server Console does not run on .NET Framework 4.0 if you start it manually, either by adding it to an existing MMC console, or by opening the Rule Execution Server Console.msc file which is part of the distribution. The Rule Execution Server Console runs on .NET Framework 4.0 with no necessary setup if you start it from the shortcut menu.Before you run the MMC Console (mmc.exe) you must configure it in one of the following ways:
  • Set the environment variable COMPLUS_Version to v4.0.30319. You do not have set this variable permanently, for example you can set this variable temporarily by placing COMPLUS_Version=v4.0.30319 at the beginning of a DOS batch script that you use to call mmc.exe.
  • Create an mmc.exe.config file that you place next to the %WINDIR%\System\mmc.exe file, and that contains the following declaration:
<?xml version="1.0">
<configuration>
<startup useLegacyV2RuntimeActivationPolicy= "true">                        <supportedRuntime version='v4.0' />
</startup>
</configuration>


Rules for COBOL



ErrorsComments and workarounds
The reference for the documentation and tutorials is the English version. If you have difficulties following any part of the localized documentation or tutorials, refer to the English version for clarification.You can change the language of the information center using these instructions:
1. Open a browser window and click Tools > Options.
2. Open the Language preferences.
3. Select English [en-us], move this language to the top of the list, and then click OK.
4. When you are finished, clear the cache to ensure that when you open the help system you see the refreshed files.
Task 3: Creating a BOM from a COBOL copybook. If you are working in a language that requires an extended character set, such as Chinese, Japanese or Korean, you need an additional step in the tutorial to enable copybook encoding.On the BOM Entry page, click the Enable encoding check box, and from the drop-down menu select one of encodings supported by your locale. For example, you might select Big5 for Traditional Chinese, GB18030 for Simplified Chinese, EUC-KR for Korean, EUC-JP for Japanese.
Task 3: Creating a BOM from a COBOL copybook. For localized versions of Rules for COBOL, the tutorial should tell you to verbalize your classes in the language of your locale.When you create a BOM from a COBOL copybook, the default verbalization is in English. In a localized version of Rules for COBOL, you must verbalize your classes in the language in which you are working before you start writing rules. For example, in the Rules for COBOL tutorial, you must verbalize the Borrower and Loan classes.

Refer to the rules in Task 5: Writing some business rules to verify how to verbalize each of these classes in your locale.
Task 7: Generating COBOL code. Sample code is applicable only to English version.In Task 7 of the Rules for COBOL tutorial, step 7 points you to a file containing a sample of the generated COBOL code. This code sample is applicable only to the English version.
Usage data collection. The default setting has changed from 'enabled' to 'disabled'.The section entitled 'Setting the usage data collection flag' includes a note that states that the default setting is 'enabled'. From version 7.1.1.3 the default has changed, so this statement is no longer true.


Rule Studio Scorecard Modeler



ErrorsComments and workarounds
Partial Rule Team Server supportYou can only publish scorecard technical rules to the Rule Team Server repository. You cannot view or edit scorecard artifacts in Rule Team Server.
Reports are not supportedBusiness rule reports do not contain scorecard tables or their details.
Queries are not supportedQueries such as Find all scorecards such that are not supported.
Scorecard variables and parameters are not copiedWhen a scorecard is copied and pasted, the variables and parameter corresponding to the new scorecard are not created. You need to create new variables and parameters with the name same in the new scorecard.
Scorecard rules do not support rule refactoringWhen a scorecard is renamed or moved, its rule reference is not automatically updated. You need to update the corresponding references manually.
The Java Enum,BigDecimal,BigInteger data type is not supportedYou cannot select a field of type Enum, BigDecimal or BigInteger when creating an attribute.
Double-clicking on an error or warning message does not highlight or scroll to the attributeWhen you double-click on an error or warning message in a view containing errors, the cursor does not automatically move to the attribute.
Unable to delete cells using the Delete key in the scorecard editorWhen you press the Delete key in the scorecard editor, the cell is not deleted.
Redo/Undo history lost issues
  • When you switch from a scorecard page to a page of the editor in Rule Studio, the redo/undo history is lost
  • When you use the brl editor to edit a score or a weight, the redo/undo history is lost.
Precision definition with double and float data type should be set explicitlyExplicitly set precision if the attribute data type is double or float.
Scorecard attribute score should be set explicitlyExplicitly set Max Score and Segment Score to avoid any warning.


Installers



ErrorsComments and workarounds
While running the Japanese installer, in the step to select a JVM the requirements regarding the supported JDK for WebSphere CE is not displayed. Choosing a non-supported JVM could prevent you from using the Sample Server. When choosing the Java Virtual Machine be aware that the Sample Server runs on IBM WebSphere Server CE, which supports only the following JDKs:
* Sun JDK Version 5.0
* IBM 32-bit SDK for Windows version 5.0 or 6.0
* IBM 32-bit SDK for Linux x86 version 6.0
When installing DVS on Windows an Error message is displayed regarding existing files.You can ignore the message and press Yes to All to replace existing files.
While installing the Rules for .NET product in a localized version the prerequisite HTML page does not display properly. Use the feedback in the installer panel to identify what is missing from the prerequisites and take the appropriate action.


Samples



ErrorsComments and workarounds
If you encounter a runtime error about mismatching versions in the Sample server when you run the samples or the Getting Started, it is likely that the Samples server is using a version of the JDK that is non-compatible with the JDK used at compilation time in Rule studio.The default installation uses a JDK compiler compliance level of 1.6 for both the Samples Server and Rule Studio. To remove the error, make sure that you use the same version of the JDK in both the Sample server and in your compilation environment in Rule Studio.
Inconsistent behavior when running consecutive samples.If you encounter problems when you finish one Rule Team Server sample and try to start the next sample, you can resolve it by restoring the Rule Team Server samples environment. You can do this manually, or by using an Ant task:
  • In the Samples Console, click Restore Server.
When running the Rule Team Server GUI customization sample with Internet Explorer you cannot access the Options page or Sign out from a custom tab such as BOM or Category.The sample works as expected if you use Mozilla Firefox.


Known limitations in an environment with multiple locales



ErrorsComments and workarounds
Some elements cannot be fully localized in Rule Solutions for Office. This limitation applies to the elements listed here.
  • Rule Categories: you cannot define translations for category identifiers, for example, "Any".
  • Ruleset Parameters: the name of the Ruleset Parameters is not localized.
  • Custom Rule Properties definitions: custom rule properties are defined in an XML Schema. The definition of these properties (display name, documentation) is not localized.
  • Boolean values: these are not localized in property grids. For example, a rule property value or a BOM member value will have a value of "True" or "False" in all locales.
The consequence of this limitation is that for these elements, in Rule Solutions for Office, the parameter name is displayed and not the localized verbalization. When the parameter name is in the target language this limitation can go unnoticed. However, if the target environment has more than one locale, this limitation becomes more apparent. Choose your parameter names with care, and give preference to names in the language that are the most common within your user community.
If your browser does not use the same locale as the Getting Started, the miniloan application does not open in the appropriate locale and does not behave as expected. To follow the Getting Started in a given locale, set this locale in your default browser.


Known issues in documentation


ErrorsComments and workarounds
Documentation does not explain what JRules libraries to use in the following topic: WebSphere ILOG JRules BRMS V7.1 > Customizing > Customizing Rule Studio > Customizing rule authoring > Implementing dynamic domains > Creating a dynamic domain.The implemented interface is defined in vocbom.jar (ilog.rules.vocabulary.bom plug-in).
To be able to implement this interface, you must reference the correct libraries in your Java project.
Add the following libraries as dependencies of your project:
  • vocbom.jar from the ilog,rules.vocabulary.bom eclipse plug-in
  • ruleshared.jar from the ilog.rules.shared eclipse plug-in
  • jrules-engine.jar from <InstallDir>/studio/lib
When viewing topics in the Rule Team Server online help in Japanese, you see corrupted characters. Your browser can usually determine the correct language encoding, as long as the language encoding auto-select feature is turned on.
You can view the Japanese correctly by changing the language encoding of your browser to UTF-8.
The reference for the documentation and tutorials is the English version. If you have difficulties following any part of the localized documentation or tutorials, refer to the English version for clarification.You can change the language of the information center using these instructions:
  1. Open a browser window and click Tools > Options.
  2. Open the Language preferences.
  3. Select English [en-us], move this language to the top of the list, and then click OK.
  4. When you are finished, clear the cache to ensure that when you open the help system you see the refreshed files.
A small number of topics that should be localized in this release in the Rule Team Server and Rule Solutions for Office online helps are only available in English.The translated topics are available on the IBM WebSphere ILOG JRules BRMS information center.
The tutorials in the Rule Team Server and Rule Solutions for Office online helps are not translated in Brazilian Portuguese.These tutorials must be followed in English.
The help on how to use Decision Warehouse currently mentions a false Decision Validation Services license limitation. Unfortunately, the documentation could not be updated to reflect the change in this version, and the Decision Warehouse documentation is located in the Decision Validation Services help. Decision Warehouse is now part of IBM WebSphere ILOG JRules instead of WebSphere ILOG Decision Validation Services. This change has been made to simplify the product architecture, and make it easier for users to install, manage, and audit their BRMS. As a consequence of this change, the Decision Warehouse tab is now always available in the Rule Execution Server Console.

The product documentation will reflect the repositioning of Decision Warehouse in a future release.
The documentation for the Getting Started tutorial does not describe how to change the vocabulary for the miniloan rule project if you are using a localized version of JRules. The default verbalization for the project is English, so you must import the vocabulary that corresponds to your locale to see the appropriate verbalization.To change the verbalization, import the vocabulary file for your locale into the <miniloan-rules-localized> project that you created. The <miniloan-rules-localized> project is the localized version of the miniloan-rules project.
You must import the vocabulary when you get to Task 1: Designing the rule project > Step 4: Create the BOM > Step 11.

To import the vocabulary into the rule project:

  1. In Rule Studio, click File > Import.
  2. In the Import wizard, select General > File System, and click Next.
  3. In the From directory field, click Browse and select
    <InstallDir>/
     gettingstarted/
       locale/<locale>/
         <miniloan-rules-localized>/bom
    ,
    and then click OK.
  4. On the right pane, select the check box next to <miniloan-localized>_<locale>.voc.
  5. In the Into folder field, ensure that <miniloan-rules-localized>/bom is selected.
  6. Select the Overwrite existing resources without warning option.
  7. Click Finish.
  8. In the Rule Explorer, right-click the <miniloan-rules-localized> project, and click Refresh.

To check the vocabulary:
  1. In the Rule Explorer, double-click the Borrower class to open it in the BOM editor (<miniloan-rules-localized> > bom > <miniloan-localized> > miniloan > Borrower).
  2. In the Members section, double-click the name attribute. In the Member Verbalization section, you can see that the navigation phrase uses the new verbalization.
In the Rule Team Server customization documentation (WebSphere ILOG JRules BRMS V7.1 > Customizing > Customizing Rule Team Server), the example Ant task commands do not specify all the arguments needed for the repackaging of the Rule Team Server archive.Depending on your application server, you must use the repackage-ear or the repackage-war Ant task. For more information on the arguments to use for the repackaging of the Rule Team Server archive, see WebSphere ILOG JRules BRMS V7.1 > Installing > Installing JRules modules on WebSphere Community Edition > Installing Rule Team Server on WebSphere Application Server Community Edition V2.1 > Completing the installation using Ant tasks > Repackaging the Rule Team Server WAR.
Contrary to a number of references in the installation topics, Rule Execution Server and Rule Team Server are not supported on Tomcat clusters.Installation instructions that imply Tomcat clustering support should be ignored.
The following topic contains a misleading restriction on custom value providers:
WebSphere ILOG JRules BRMS V7.1 > Samples > Rule Studio samples > Rule Studio authoring extension samples > Custom value editor for Rule Studio sample.
The restriction states "Only Swing graphical components can be used as custom value providers", which implies that Rule Studio only supports Swing based editors.
In fact, this sample is using a Swing based custom editor, but it is also possible to attach custom SWT editors inside the Intellirule editor. The support for SWT editors, as well as Swing editors is described in: WebSphere ILOG JRules BRMS V7.1 > Customizing > Customizing Rule Studio > Customizing rule authoring > Extending BOM value types > Implementing a value editor > Creating a value editor.
The documentation does not include information on creating J2C authentication data when configuring Rule Team Server on WebSphere Application Server. After you have created your data source and connection pool, you create the J2C authentication data. J2C is a secure mechanism for integrating enterprise information systems to an application server and enterprise applications.

This step uses resAdmin as the user ID and resAdmin as the password. Your user ID and password might be different, depending on the user or schema that is used to execute the Rule Execution Server SQL script. If you perform the step as described, tables are created under the resAdmin schema.

In the case of a Derby database, if the connect command does not contain the user ID, then the user ID and password use the default values APP and APP. If you create the tables under the APP schema, you do not need to perform this step.

Procedure
1. In the Integrated Solutions Console, open Resources > JDBC and Data sources.
2. Click ilogDataSource.
3. Under Related Items, click JAAS - J2C authentication data.
4. Click New and set the fields Alias, User ID, and Password. For example, this procedure uses the following values:
Alias: RtsDerbyUser
User ID: rtsAdmin
Password: rtsAdmin
5. Click Apply and Save to save directly to the master configuration.
6. Open Resources > JDBC and Data sources, and click ilogDataSource.
7. In the Security settings section, for Component-managed authentication alias, select the <NodeName>/RtsDerbyUser alias, where <NodeName> is the name of the WebSphere Application Server node on which you are configuring Rule Execution Server.
8. For Container-managed authentication alias, select <node name>/RtsDerbyUser.
9. Click Apply and Save to save directly to the master configuration.


Known limitations and issues in V7.1.1.3




Rule Studio


ErrorsComments and workarounds
BOM Update does not handle generics correctly.Ignore the action related to generic classes that are not found in the XOM, the actions are erroneous.
Errors in IRL transition are not reported in the ruleflow editor Diagram view.Errors in IRL are reported in the problems view and the IRL view of the ruleflow editor.
Prefer using BAL to write transition.
If Rule Studio automatic build is disabled, problems in a ruleflow are only reported in the Problem View, and not in the ruleflow graph.Close and reopen the Ruleflow Editor to update the graph with the errors.
Cut, copy and paste do not always work as expected in the Ruleflow Editor. If the Edit > Paste command does not work, use Ctrl+V to complete the operation.
Shortcuts do not work in the documentation, use the right-click menu.
In a ruleflow, if you join two transitions with a branch node a compilation error is thrown,Remove the branch node and connect the transitions directly to the next task.
If a rule and a decision table have similar names, a naming conflict is detected during ruleset parsing.Rename the rule so that the generated name of the decision table does not conflict with it.
When refactoring a ruleset parameter name, templates that use this name are not refactored.Refactor the rule templates manually using the errors reported.
The "ruleflows which may select this rule" query does not find results if a ruleflow contains a subflow. Do not use this query if you have subflows.
GB 18030 Phase 2 characters are lost when pasting from an external source into the Condition Column window in Rule Studio. Do not copy GB 18030 Phase 2 characters in a decision column editor.
In BAL, when assigning a literal value to an attribute of type java.lang.Float, the literal is considered as a double (15.5d) and then cast to a float. This causes a rounding error. Use either the float or the double attribute.
In the Decision Table Editor, when you select a double/float value and use the auto-filled value (drag the lower right corner of the cell and select the destination rows), some of the auto-filled values are not precise.
For example, if the original value in the first row is 1.39, the auto-filled value in the second row becomes 1.3899999999999997.
This problem only happens to some auto-filled values. To resolve the problem, either manually adjust the erroneous values or avoid using the auto-fill feature.
A class that has the same name as a package can lead to a LinkageError exception during ruleset parsing if you use this package to initialize a parameter value.Remove the reference to the package in the method used to initialize the parameter.
You cannot edit rules created in a locale that is different to the Rule Studio locale. Parameters and variables cannot be found in this case.Only use Rule Studio in the locale of the project that you intend to edit. Do not mix rules in different locales in the same rule project.
If an automatic variable and a parameter have the same name, conflicts are detected when writing rules. Sometimes the incorrect variable is used in the translated IRL.Either disable the automatic variable or rename the parameter or local binding to avoid the conflict with the automatic variable name.
There is an issue regarding dynamic domains when migrating rule projects from JRules V6 to V7.1. There is a difference in the way dynamic domain elements are deprecated between V6.7 and V7.
  • In V6.7, the element is noted as deprecated in both the .voc and the .bom files.
  • In V7, it is only noted in the .bom file.

If you deprecate an element in V6.7, migrate the project to V7, then restore the element in the domain. In V7, the element remains as deprecated unless you remove the deprecated property from the .voc file.
Business rules written in Simplified Chinese that use Date.isAtDayTime() in a previous version of JRules raises a build error in JRules V7.1.1.3. An error is raised because the verbalization has changed. If you see this error in a migrated project, fix the business rules using the new verbalization. The word 事件 must be changed to 时间.
Ruleset Properties PanelIn JRules V7.1, ruleset properties entered in the Ruleset Properties Panel require double quotes around a java.lang.String type. Other types should not be enclosed in quotes.
After importing a rule project from a previous version of JRules into Rule Studio, you must modify the ruleset properties in each of the migrated rule projects to comply with this new notation.
There are some known bugs related to the management of JDK generic classes. These bugs generate a NullPointerException or ClassCastException in Rule Studio.If you get one of these exceptions while using Rule Studio, and if the associated Java stack contains references to the XOM or to the BOM to XOM mapping, you can resolve the problem by adding a file named engine.conf to your rule project. The engine.conf file should contain the following code:

node ilog.rules.engine
{
element enableGenerics=false;
};

This file can be added in your rule project using the Ruleset Project Properties dialog.
When exporting a report with a chart or other images to the Microsoft Excel format, the charts and images are not displayed in the exported file. BIRT allows you export reports to different formats (.pdf, .ppt, .xls, and so on). However, there is a bug that prevents the export of images to Excel, therefore if you have a ruleflow or decision table, they are not exported to Excel. This is a known limitation in BIRT referenced in Bugzilla as Bug 198623. To workaround this issue, manually copy and paste the charts and images from the source report to the exported Excel file.
Some Microsoft Excel add-ins prevent Microsoft Excel 2007 files from being opened within Rule Studio. Although not strictly related to Rule Studio, you may encounter this incompatibility between Eclipse and Microsoft Excel 2007. If you do, try disabling or uninstalling Excel add-ins.
SUN and IBM JDK limitations prevent Eclipse from running the Run and Debug launch configurations on projects that contain Japanese, Korean, Chinese (simplified and GB18030 encoding) characters.This is a known limitation in Eclipse Java development tools (JDT) referenced in Bugzilla as Bug 32206 and in the SUN Bug Database as Bug 4947220. To workaround this issue, take one of the following actions:
  • Use a localized Windows platform. For example, Windows localized in Japanese.
  • Use an international Windows platform with the following Regional and Language Options settings:
  • Regional Options tab: Standards and formats set to your locale, for example Japanese.
  • Advanced tab: Language for non-Unicode programs set to your locale, for example Japanese.


Rule Studio for .NET




ErrorsComments and workarounds
The date format for parameters in a decision table are not localized. The parameters are always displayed in English.
Priority values are not checked during synchronization between Rule Studio and Rule Team Server.During synchronization, Rule Studio does not check that a value entered for a priority is a valid value.
Verbalizers are overwritten when installing different versions of Rule Studio on the same machine.This issue may arise when you install an update of Rules for .NET V7.1.1.3. We recommend you uninstall any previous version before installing an update.

If two different versions of Rule Studio for .NET are installed on the same machine, the verbalizers registered on the machine registry are overwritten by the latest installation. Therefore, in the first installation, only English languages are available in the language options. To repair this installation issue:

  1. Click Start > Control Panel, and then open Add or Remove Programs.
  2. In the Add or Remove Programs window, locate and click the entry for ILOG Rule Studio for .NET, and then click Change.
    The ILOG Rule Studio installation wizard appears.
  3. Click Repair ILOG Rule Studio for .NET, and then click Finish.
    Your installation is repaired and the verbalizers are re-registered.
The following message appears when publishing in the Rules for .NET Getting Started: "The Rule Team Server and Rule Studio extensions are not consistent, which may lead to problems when you try to edit rules." You can safely ignore this message when you are doing the Rules for .NET Getting Started.
When viewing the Workflow Foundation integration sample, there are errors in the workflow diagram. For example:
Error 1 Path resolved to Referenced activity Property 'Status' whose PropertyType 'WorkflowApplication. Eligibility.Status' does not match with the Target Type 'WorkflowApplication. Eligibility.Status'. 0 0
Error 1 Path resolved to Referenced activity Property 'RentalAgreement' whose PropertyType 'WorkflowApplication. Pricing.RentalAgreement' does not match with the Target Type 'WorkflowApplication. Pricing.RentalAgreement'. 0 0
These errors are resolved when you build the workflow.
The reference for the documentation and tutorials is the English version. If you have difficulties following any part of the localized documentation or tutorials, refer to the English version for clarification.You can change the language of the information center using these instructions:
1. Open a browser window and click Tools > Options.
2. Open the Language preferences.
3. Select English [en-us], move this language to the top of the list, and then click OK.
4. When you are finished, clear the cache to ensure that when you open the help system you see the refreshed files.
Integrated help is not available from Rule Studio when using Visual Studio 2010.The most current version of the documentation is available from the IBM WebSphere ILOG Rules for .NET BRMS information center. The documentation for Rule Studio is based on the Visual Studio 2008 user interface.
The Brazilian Portuguese BAL has been changed in this version.
The <a number> is more than <a number> operator is now translated as à maior instead of é maior.
The previous operator is marked as deprecated. Upgrade your business rules to use the new operator with the corrected translation.
In Visual Studio 2010, when a BOM references an assembly file built from managed C++ code in CopyLocale mode, this assembly file is locked after the build.To unlock the assembly file, close Visual Studio 2010.
If you have custom properties in your rule project, you must create an extension model to publish to Rule Team Server, but this is not documented.Follow the steps described in the following technote.


Rule Solutions for Office



ErrorsComments and workarounds
The shortcut to the Rule Solutions for Office documentation in the Start menu does not work.The language of the OS and the language of Visual Studio and Office must be the same. The documentation is available online here.
Verbalizers are overwritten when installing different versions of Rule Solutions for Office on the same machine.This issue may arise when you install an update of Rule Solutions for Office V7.1.1.2. You are recommended to uninstall any previous version before installing an update.

If two different versions of Rule Solutions for Office are installed on the same machine, the verbalizers registered on the machine registry are overwritten by the latest installation. Therefore, in the first installation, only English languages are available in the language options. To repair this installation issue:

  1. Click Start > Control Panel, and then open Add or Remove Programs.
  2. In the Add or Remove Programs window, locate and click the entry for IBM WebSphere ILOG Rule Solutions for Office, and then click Change.
    The Rule Solutions for Office installation wizard appears.
  3. Click Repair, and then click Finish.
    Your installation is repaired and the verbalizers are re-registered.
Tutorial RuleDocs cannot be edited in Web controlsIf you try and edit the tutorial RuleDocs into a Rules for .NET Web control, the following message is displayed: "The selected rule document contains no rule artifact."
RuleDocs (.docx or .xlsx) must be associated with Microsoft Office Word or Excel and not with Microsoft Word or Excel Viewer.When working with RuleDocs, you must have the correct file association for .docx and .xlsx files. Otherwise you will get errors when trying to edit them.
The reference for the documentation and tutorials is the English version. If you have difficulties following any part of the localized documentation or tutorials, refer to the English version for clarification.You can change the language of the information center using these instructions:
  1. Open a browser window and click Tools > Options.
  2. Open the Language preferences.
  3. Select English [en-us], move this language to the top of the list, and then click OK.
  4. When you are finished, clear the cache to ensure that when you open the help system you see the refreshed files.
A small number of topics that should be localized in this release are only available in English.The translated topics are available on the IBM WebSphere ILOG Rules for .NET BRMS information center.
The tutorials in the Rule Solutions for Office online help are not translated in Portuguese (Brazilian).These tutorials must be followed in English.
The installer reports that Visual Studio Tools for Office Runtime (VSTOR) 4.0 is missing, but you have installed VSTOR.If you installed VSTOR before .NET Framework 4.0, the VSTOR runtime does not use version 4.0 of .NET Framework, but version 3.5. For VSTOR to use .NET Framework 4.0, you must uninstall and reinstall it.

Decision Validation Services



ErrorsComments and workarounds
Cannot test the content in collections of complex type in Excel scenario file templates.The column headings of the Excel scenario file template are defined by the attributes of the BOM class. Each column corresponds to an attribute.
Each attribute for which a test is defined in the Expected Results sheet:
  • must be verbalized, since the name used in the column heading is the verbalization of the attribute
  • must not be a collection of complex type

If the attribute is a collection of simple type (int, String, and so on), the domain must be defined.


Rule Team Server



ErrorsComments and workarounds
In Chinese and Japanese the completion menu of the Web Intellirule Editor does not appear if CTRL+space is used after an ideograph.Insert space characters or use the Guided Editor.
Properties defined in the common model are not visible in the ruleflow. The ruleflow is not a managed artifact in Rule Team Server and does not inherit the common properties. You need to define the properties specifically on the ruleflow element.
If you try to copy or paste some text in the Web Intellirule Editor, an error message explains what you have to do in order to authorize the copy-paste operations in Rule Team Server.
The suggested content for user.js is incorrect, quotes around property names and values are missing.
The correct content to add in user.js is:
user_pref( "capability.policy. policynames", "allowclipboard");
user_pref( "capability.policy. allowclipboard.sites", "localhost:8080");
user_pref( "capability.policy. allowclipboard.Clipboard.cutcopy", "allAccess");
user_pref( "capability.policy. allowclipboard.Clipboard.paste", "allAccess");
When using a DB2 database you could encounter a "Statement is closed" exception at the end of a long ruleset archive generation.Increase the connection timeout: in the WAS administration console, at the data source level, in the "connection pool properties" panel.
The Publish command in Rule Team Server is enabled while a publish of RuleDocs is running. If you publish a second time the resulting file may be corrupted. Click the Publish button once. If the file is corrupted delete the document and republish it.
After synchronizing a rule project with a BOM entry that is deleted and replaced by another BOM entry with the same name, no conflicts are detected. This causes duplication in the Rule Team Server database. Delete the project in Rule Team Server and republish it.
If there are double quotes added to an entry of a collection in the inline cell editor of a decision table, all subsequent operations on the cell use a lot of memory and processor usage is high. As a result it look like the decision table is locked. If you intend to have a double quote in one entry of a collection, use the editor at the top of the decision table to make the modification.
You can also change the value of the ilog.rules.brl.parsing. ErrorRecoveryTimeout parameter to 2000 for example, to get a better response time. The parameter is in the ilog.rules.brl.parsing.parser.earley/ preferences.properties file (in brlparsing.jar).
If you edit a decision table using Internet Explorer 7 in a non-maximized window, the size of a drop down list is limited even though there is extra space after performing the right scroll. This is a limitation of Internet Explorer 7. Maximize the Internet Explorer 7 window and the drop down list displays as expected.
Using the Web Intellirule Editor to edit a rule in a locale that is different from the persistence locale raises an exception on the server if the vocabulary is incomplete.Restart the server. and make sure you have a complete vocabulary for the language. Alternatively, edit with the Guided Editor.
When editing decision tables you cannot select predefined values of a domain directly within a cell. A domain is a set of predefined values in the vocabulary of the project. However, you can add predefined values to your conditions by inserting values from a drop-down list in the conditions editor, which is located above the decision table.To select a predefined value in a cell:
  1. Click the cell, then click the object placeholder in the conditions editor.
  2. Click the necessary placeholders to reach your domain.
  3. Use the drop-down menu to select a predefined value from the domain.
In the Russian locale, the Rule Team Server tutorial projects are not available in Russian, so you must use the projects in English.To open Rule Team Server with the data source in English go to: http://localhost:8080/teamserver?datasource=jdbc/ilogDataSource_en_US.
The Windows shortcut JRules (en_US) > Tutorials > Rule Team Server opens the data source in English.
In the Brazilian Portuguese locale, the Rule Team Server tutorial documentation is only provided in English, The tutorial projects are provided in English in the data source named ilogDataSource_en_US. Note that the tutorial projects are also provided in Brazilian Portuguese in the data source named ilogDataSource_pt_BR, but the English documentation refers to the English projects.To open Rule Team Server with the data source in English go to: http://localhost:8080/teamserver?datasource=jdbc/ilogDataSource_en_US.
The Windows shortcut JRules (en_US) > Tutorials > Rule Team Server opens the data source in English.
The Windows shortcut JRules (pt_BR) > Tutorials > Rule Team Server opens the data source in Brazilian Portuguese.
You cannot have more than one Mozilla Firefox browser connected to Rule Team Server at the same time with different users.This is because Mozilla Firefox shares the default profile among all sessions on the same machine, which means that the data is shared among all browser instances. So, if you are connected to Rule Team Server as rtsAdmin and you want to connect as rtsUser1, you must first sign out from the rtsAdmin session before connecting as rtsUser1.
For more information see this page. If you are an advanced Mozilla Firefox user, you can create different profiles for each Rule Team Server user, as described in this document.
Note that Internet Explorer behaves differently. Different Internet Explorer browsers do not share data, so you can have one Internet Explorer browser connected to Rule Team Server as rtsAdmin, and one Internet Explorer browser connected to Rule Team Server as rtsUser1.
The web installer in Rule Team Server does not work for IBM DB2 for i.Download the SQL scripts generated by the web installer, then run the tables creation script and the data inserting script using the database tool.
The Testing a set of rules tutorial does not work if you have repackaged the SSP .war or the Rule Team Server.war files.
 
To restore the SSP and Rule Team Server files and perform the Testing a set of rules tutorial:
  • Click Restore Server in the Samples Console.
When the number of conditions in a decision table partition is very large, and an otherwise is used in this partition, a Stack Overflow might be raised when compiling the decision table. Avoid the use of otherwise in decision tables that contain a large number of conditions.
In JRules V7 the priority attribute in IlrTechnicalRule has been moved to the IlrRule super class. This change hides custom priority attributes from subclasses such as IlrBusinessRule and its subclasses when you migrate your model.If you defined a custom priority property in IlrBusinessRule or a subclass, using one of the default extensions for example, you must rename this extended attribute in your custom class before you run the migration tool. For example, if your default extension model includes:

<add-property className="BusinessRule">
    <property extractable="true" name="
priority" type="String">
      <annotation id="column-name" value="priority_ext"/>
    </property>
</add-property>


Change the model before migration to:

<add-property className="BusinessRule">
   <property extractable="true" name="
myPriority" type="String">
     <annotation id="column-name" value="priority_ext"/>
   </property>
</add-property
>

In JRules 6.x, upload the modified model using Upload Only in the Rule Team Server Installation Manager. In JRules V7, use the same model to create the new Rule Team Server schema. The custom priority property on your business rules is stored in a new myPriority custom property that can then be copied to the JRules V7 priority property, which is now part of the base rule model.
You cannot redeploy a RuleApp that includes extracted rulesets from one or more common projects.This limitation is identified in the following cases:
  • If you have one rule project from which you extract two different rulesets.
  • If you have two rule projects that depend on a common project.
  • If you have two rulesets that extract different elements from a common project.

To redeploy a RuleApp that matches one of these cases, do one of the following:
  • Download the previously deployed RuleApp archive from the Rule Execution Server Console, and then redeploy it.
  • Generate the rulesets individually in Rule Team Server and upload them in the Rule Execution Server Console one by one.
RuleDocs (.docx or .xlsx) must be associated with Microsoft Office Word or Excel and not with Microsoft Word or Excel Viewer.When working with RuleDocs, you must have the correct file association for .docx and .xlsx files. Otherwise you will get errors when trying to edit RuleDocs, either after publishing from Rule Team Server, or when using the Edit in Rule Solutions for Office option from the rule tables in the Explore tab.


Rule Execution Server



ErrorsComments and workarounds
The list of parameters in the deployment descriptor for the Rule Execution Server Console has been updated. The list of the parameters in the topic WebSphere ILOG JRules BRMS V7.1 > Rule Execution Server Console online help > Monitoring and managing the server > Configuring the Rule Execution Server Console Web application is not up-to-date. The updated context parameters contained in the /WEB-INF/web.xml file are documented in the file itself. The list of context parameters is as follows:
  • ilog.rules.res.HELP_CONTEXT
    The Rule Execution Server online help context-root.
  • ilog.rules.res.HELP_INDEX
    The Rule Execution Server online help index.
  • ilog.rules.res.HELP_TOPIC
    The Rule Execution Server online help topic.
  • ilog.rules.res.HTDS_CONTEXT
    The Hosted Transparent Decision Services context-root.
  • ilog.rules.res.SSP_CONTEXT
    The default context-root used for ssp.
  • ilog.rules.res.RTS_CONTEXT
    The Rule Team Server context-root.
  • log4j-init-filename
    The LOG4J configuration file.
  • persistenceType
    The persistence type, either data source or file.
  • filePersistenceDirectory
    Used only when the persistenceType parameter is set to file. It is the root directory for the file persistence, this can be an absolute or relative path.
  • ilog.rules.res.trace. DECISIONWAREHOUSE_CONFIGURATIONS
    The list of decision warehouse configurations available in the Rule Execution Server Console. This is a list of names separated with a comma. For each decision warehouse configuration, a <context-param> with the same name must be declared in the web.xml file. The value of this parameter is a string that begins with factoryClassname= FULLY_QUALIFIED_NAME_OF _THE_TRACE_DAO_FACTORY_ FOR_THIS_CONFIGURATION, optionally followed by a semicolon (;) and the list of properties to initialize the trace DAO factory. Each property in the list is defined as PROPERTY_NAME=PROPERTY_VALUE and the properties are separated by a semicolon (;).
  • defaultDWConfiguration
    The default decision warehouse configuration. Traces are saved in the decision warehouse database that is created during the installation of Rule Execution Server.
  • ilog.sam.application
    Specify an application name for SAM.
  • JMX_XU_QUERY_PART
    Specify a subset of XUs visible from the console.
  • JMX_DS_QUERY_PART
    Specify a subset of decision services visible from the console. Possible keys and values depend on the application server. For example, on WebSphere the cell name, node name, and server name are added to MBean object names so you can search for decision services deployed under a specific WebSphere node with node=mynode.
When using Hosted Transparent Decision Services in WebSphere Integration Developer you could experience the following issues:
  • A namespace conflict if you import more than one decision service into a single process.
  • Duplicated business items if you import the WebSphere Process Server data model into the same process module.
For the HTDS integration, use the mediation flow capability of WebSphere Enterprise Service Bus (WebSphere ESB) or microflow (short-running process flow) in conjunction with HTDS. For more information see the Redbook: Integrating WebSphere ILOG JRules with IBM Software.

For the duplicated business items issue, you must generate a HTDS WSDL without the schemas in your rule project. To do that, go to the dynamic object model settings in your rule project, expand the section Schemas to be included in Ruleset archive for enabling the Transparent Decision Service, and deselect All schemas.

Note:
This limitation has been resolved in V7.1.1.3 as described in the section Configuring namespaces in a hosted transparent decision service WSDL of the Documentation Supplement in the README.
If you encounter a decision service runtime exception after migrating from V7.0 to V7.1, it is likely that this is the result of the newly introduced DecisionID element in the WSDL.According to the documentation, a client application that uses the WSDL generated with V7.0 works if you set the Compatibility parameter in the web.xml file of the V7.1 HTDS artifact to "7.0".

<context-param>
   <param-name>Compatibility</param-name>
   <param-value>7.0</param-value>
</context-param>

After this parameter is added, the WSDL generated for a decision service in V7.1 does not include the DecisionID.
An error is thrown if you call a monitored ruleset from a Hosted Transparent Decision Service running on an application server using Sun JDK 1.6. The Sun JDK includes JAXP 1.4, a custom version of Xerces and Xalan, which causes this error.To monitor a ruleset and store the results in Decision Warehouse using Hosted Transparent Decision Services with Sun JDK 1.6:
  1. Repackage the HTDS WAR with the Xalan JAR.
    For example, on Tomcat copy the file xalan-2.7.0.jar from the folder<InstallDir>/executionserver/lib/ into the WEB-INF/lib folder of the file DecisionService.war in the folder <InstallDir>/shared/tools/apache-tomcat/webapps.
  2. Set the monitored.enabled and ruleset.bom.enabled ruleset properties to true.
  3. Deploy the repackaged HTDS archive file and the enabled ruleset to your application server,
  4. Expose the deployed ruleset as a transparent decision service.
  5. Call the decision service from your client application.


Rule Execution Server .NET



ErrorsComments and workarounds
When installing Rules for .NET into a folder that contains non-English characters in the name, the rule execution persistence service and the rule execution management services fail to start.The issue comes from the characters encoded in this configuration file :
C:\Program Files\IBM\WebSphere\ILOG Rules for .NETアイウか鯵表噂ソ竹十\Rule Execution Server for .NET\Bin\Public Assemblies\ILOGExecutionServerPersistenceService.exe.config

Add the encapsulating elements to the following line to start the services:
<add key="ILOG.Rules.ExecutionServer.Persistence.BaseDirectory" value="C:\Program Files\IBM\WebSphere\ILOG Rules for .NETアイウか鯵表噂ソ竹十\Rule Execution Server for .NET\Bin\Persistence"></add>
After installing Rule Execution Server, if the performance counters are not available, these could be corrupted on your system.To repair the installation of performance counters:
  1. Repair your system by using the command lodctr.exe /R, or by following the instruction on this page: kb 300956.
  2. Repair the Rule Execution Server installation by opening the Control panel and clicking Repair for IBM WebSphere ILOG Rules for .NET.
In some cases, the ILOG Management Service does not start automatically on Windows Server 2003, and tutorials and samples do not work.The ILOG Management and Persistence Services should start automatically when you start Windows. However, when you start a computer with Windows Server 2003, only the ILOG Persistence Service starts automatically. You need both Services for the samples and tutorials. For information on how to start the Management Service manually, see WebSphere ILOG Rules for .NET V7.1.1.3 Documentation> Rule Execution Server Console online help> Stopping and starting the Management and Persistence Services.
The documentation for configuring the Execution Service for IIS is based on ASP 2.0.
WebSphere ILOG Rules for .NET BRMS V7.1 > Configuring > Configuring Rule Execution Server > Setting up the Execution Service environment > Step 3: Configuring the Execution Service for IIS > Launch the IIS Configuration Wizard
. If you have installed Rules for .NET on .NET Framework 4.0, you use ASP 4.0.
The procedure for configuring the Execution Server for IIS is the same with ASP 4.0.
If ASP.NET 4.0 is not registered with IIS, open the Visual Studio 2010 command prompt or use the aspnet_regiis executable (located in %SYSTEMROOT%\Microsoft.NET\Framework\v4.x for x86 systems, or in %SYSTEMROOT%\Microsoft.NET\Framework64\v4.x for x64 systems).
The MMC Console does not run under CLR 4.0, which is mandatory to run Rule Execution Server Console when built with .NET Framework 4.0. As a consequence, the Rule Execution Server Console does not run on .NET Framework 4.0 if you start it manually, either by adding it to an existing MMC console, or by opening the Rule Execution Server Console.msc file which is part of the distribution. The Rule Execution Server Console runs on .NET Framework 4.0 with no necessary setup if you start it from the shortcut menu.Before you run the MMC Console (mmc.exe) you must configure it in one of the following ways:
  • Set the environment variable COMPLUS_Version to v4.0.30319. You do not have set this variable permanently, for example you can set this variable temporarily by placing COMPLUS_Version=v4.0.30319 at the beginning of a DOS batch script that you use to call mmc.exe.
  • Create an mmc.exe.config file that you place next to the %WINDIR%\System\mmc.exe file, and that contains the following declaration:
<?xml version="1.0">
<configuration>
<startup useLegacyV2RuntimeActivationPolicy= "true">                        <supportedRuntime version='v4.0' />
</startup>
</configuration>


Rules for COBOL



ErrorsComments and workarounds
The reference for the documentation and tutorials is the English version. If you have difficulties following any part of the localized documentation or tutorials, refer to the English version for clarification.You can change the language of the information center using these instructions:
1. Open a browser window and click Tools > Options.
2. Open the Language preferences.
3. Select English [en-us], move this language to the top of the list, and then click OK.
4. When you are finished, clear the cache to ensure that when you open the help system you see the refreshed files.
Task 3: Creating a BOM from a COBOL copybook. If you are working in a language that requires an extended character set, such as Chinese, Japanese or Korean, you need an additional step in the tutorial to enable copybook encoding.On the BOM Entry page, click the Enable encoding check box, and from the drop-down menu select one of encodings supported by your locale. For example, you might select Big5 for Traditional Chinese, GB18030 for Simplified Chinese, EUC-KR for Korean, EUC-JP for Japanese.
Task 3: Creating a BOM from a COBOL copybook. For localized versions of Rules for COBOL, the tutorial should tell you to verbalize your classes in the language of your locale.When you create a BOM from a COBOL copybook, the default verbalization is in English. In a localized version of Rules for COBOL, you must verbalize your classes in the language in which you are working before you start writing rules. For example, in the Rules for COBOL tutorial, you must verbalize the Borrower and Loan classes.

Refer to the rules in Task 5: Writing some business rules to verify how to verbalize each of these classes in your locale.
Task 7: Generating COBOL code. Sample code is applicable only to English version.In Task 7 of the Rules for COBOL tutorial, step 7 points you to a file containing a sample of the generated COBOL code. This code sample is applicable only to the English version.
Usage data collection. The default setting has changed from 'enabled' to 'disabled'.The section entitled 'Setting the usage data collection flag' includes a note that states that the default setting is 'enabled'. From version 7.1.1.3 the default has changed, so this statement is no longer true.


Rule Studio Scorecard Modeler



ErrorsComments and workarounds
Partial Rule Team Server supportYou can only publish scorecard technical rules to the Rule Team Server repository. You cannot view or edit scorecard artifacts in Rule Team Server.
Reports are not supportedBusiness rule reports do not contain scorecard tables or their details.
Queries are not supportedQueries such as Find all scorecards such that are not supported.
Scorecard variables and parameters are not copiedWhen a scorecard is copied and pasted, the variables and parameter corresponding to the new scorecard are not created. You need to create new variables and parameters with the name same in the new scorecard.
Scorecard rules do not support rule refactoringWhen a scorecard is renamed or moved, its rule reference is not automatically updated. You need to update the corresponding references manually.
The Java Enum,BigDecimal,BigInteger data type is not supportedYou cannot select a field of type Enum, BigDecimal or BigInteger when creating an attribute.
Double-clicking on an error or warning message does not highlight or scroll to the attributeWhen you double-click on an error or warning message in a view containing errors, the cursor does not automatically move to the attribute.
Unable to delete cells using the Delete key in the scorecard editorWhen you press the Delete key in the scorecard editor, the cell is not deleted.
Redo/Undo history lost issues
  • When you switch from a scorecard page to a page of the editor in Rule Studio, the redo/undo history is lost
  • When you use the brl editor to edit a score or a weight, the redo/undo history is lost.
Precision definition with double and float data type should be set explicitlyExplicitly set precision if the attribute data type is double or float.
Scorecard attribute score should be set explicitlyExplicitly set Max Score and Segment Score to avoid any warning.


Installers



ErrorsComments and workarounds
While running the Japanese installer, in the step to select a JVM the requirements regarding the supported JDK for WebSphere CE is not displayed. Choosing a non-supported JVM could prevent you from using the Sample Server. When choosing the Java Virtual Machine be aware that the Sample Server runs on IBM WebSphere Server CE, which supports only the following JDKs:
* Sun JDK Version 5.0
* IBM 32-bit SDK for Windows version 5.0 or 6.0
* IBM 32-bit SDK for Linux x86 version 6.0
When installing DVS on Windows an Error message is displayed regarding existing files.You can ignore the message and press Yes to All to replace existing files.
While installing the Rules for .NET product in a localized version the prerequisite HTML page does not display properly. Use the feedback in the installer panel to identify what is missing from the prerequisites and take the appropriate action.


Samples



ErrorsComments and workarounds
If you encounter a runtime error about mismatching versions in the Sample server when you run the samples or the Getting Started, it is likely that the Samples server is using a version of the JDK that is non-compatible with the JDK used at compilation time in Rule studio.The default installation uses a JDK compiler compliance level of 1.6 for both the Samples Server and Rule Studio. To remove the error, make sure that you use the same version of the JDK in both the Sample server and in your compilation environment in Rule Studio.
Inconsistent behavior when running consecutive samples.If you encounter problems when you finish one Rule Team Server sample and try to start the next sample, you can resolve it by restoring the Rule Team Server samples environment. You can do this manually, or by using an Ant task:
  • In the Samples Console, click Restore Server.
When running the Rule Team Server GUI customization sample with Internet Explorer you cannot access the Options page or Sign out from a custom tab such as BOM or Category.The sample works as expected if you use Mozilla Firefox.


Known limitations in an environment with multiple locales



ErrorsComments and workarounds
Some elements cannot be fully localized in Rule Solutions for Office. This limitation applies to the elements listed here.
  • Rule Categories: you cannot define translations for category identifiers, for example, "Any".
  • Ruleset Parameters: the name of the Ruleset Parameters is not localized.
  • Custom Rule Properties definitions: custom rule properties are defined in an XML Schema. The definition of these properties (display name, documentation) is not localized.
  • Boolean values: these are not localized in property grids. For example, a rule property value or a BOM member value will have a value of "True" or "False" in all locales.
The consequence of this limitation is that for these elements, in Rule Solutions for Office, the parameter name is displayed and not the localized verbalization. When the parameter name is in the target language this limitation can go unnoticed. However, if the target environment has more than one locale, this limitation becomes more apparent. Choose your parameter names with care, and give preference to names in the language that are the most common within your user community.
If your browser does not use the same locale as the Getting Started, the miniloan application does not open in the appropriate locale and does not behave as expected. To follow the Getting Started in a given locale, set this locale in your default browser.


Known issues in documentation



ErrorsComments and workarounds
Documentation does not explain what JRules libraries to use in the following topic: WebSphere ILOG JRules BRMS V7.1 > Customizing > Customizing Rule Studio > Customizing rule authoring > Implementing dynamic domains > Creating a dynamic domain.The implemented interface is defined in vocbom.jar (ilog.rules.vocabulary.bom plug-in).
To be able to implement this interface, you must reference the correct libraries in your Java project.
Add the following libraries as dependencies of your project:
  • vocbom.jar from the ilog,rules.vocabulary.bom eclipse plug-in
  • ruleshared.jar from the ilog.rules.shared eclipse plug-in
  • jrules-engine.jar from <InstallDir>/studio/lib
When viewing topics in the Rule Team Server online help in Japanese, you see corrupted characters. Your browser can usually determine the correct language encoding, as long as the language encoding auto-select feature is turned on.
You can view the Japanese correctly by changing the language encoding of your browser to UTF-8.
The reference for the documentation and tutorials is the English version. If you have difficulties following any part of the localized documentation or tutorials, refer to the English version for clarification.You can change the language of the information center using these instructions:
  1. Open a browser window and click Tools > Options.
  2. Open the Language preferences.
  3. Select English [en-us], move this language to the top of the list, and then click OK.
  4. When you are finished, clear the cache to ensure that when you open the help system you see the refreshed files.
A small number of topics that should be localized in this release in the Rule Team Server and Rule Solutions for Office online helps are only available in English.The translated topics are available on the IBM WebSphere ILOG JRules BRMS information center.
The tutorials in the Rule Team Server and Rule Solutions for Office online helps are not translated in Brazilian Portuguese.These tutorials must be followed in English.
The help on how to use Decision Warehouse currently mentions a false Decision Validation Services license limitation. Unfortunately, the documentation could not be updated to reflect the change in this version, and the Decision Warehouse documentation is located in the Decision Validation Services help. Decision Warehouse is now part of IBM WebSphere ILOG JRules instead of WebSphere ILOG Decision Validation Services. This change has been made to simplify the product architecture, and make it easier for users to install, manage, and audit their BRMS. As a consequence of this change, the Decision Warehouse tab is now always available in the Rule Execution Server Console.

The product documentation will reflect the repositioning of Decision Warehouse in a future release.
The documentation for the Getting Started tutorial does not describe how to change the vocabulary for the miniloan rule project if you are using a localized version of JRules. The default verbalization for the project is English, so you must import the vocabulary that corresponds to your locale to see the appropriate verbalization.To change the verbalization, import the vocabulary file for your locale into the <miniloan-rules-localized> project that you created. The <miniloan-rules-localized> project is the localized version of the miniloan-rules project.
You must import the vocabulary when you get to Task 1: Designing the rule project > Step 4: Create the BOM > Step 11.

To import the vocabulary into the rule project:

  1. In Rule Studio, click File > Import.
  2. In the Import wizard, select General > File System, and click Next.
  3. In the From directory field, click Browse and select
    <InstallDir>/
     gettingstarted/
       locale/<locale>/
         <miniloan-rules-localized>/bom
    ,
    and then click OK.
  4. On the right pane, select the check box next to <miniloan-localized>_<locale>.voc.
  5. In the Into folder field, ensure that <miniloan-rules-localized>/bom is selected.
  6. Select the Overwrite existing resources without warning option.
  7. Click Finish.
  8. In the Rule Explorer, right-click the <miniloan-rules-localized> project, and click Refresh.

To check the vocabulary:
  1. In the Rule Explorer, double-click the Borrower class to open it in the BOM editor (<miniloan-rules-localized> > bom > <miniloan-localized> > miniloan > Borrower).
  2. In the Members section, double-click the name attribute. In the Member Verbalization section, you can see that the navigation phrase uses the new verbalization.
In the Rule Team Server customization documentation (WebSphere ILOG JRules BRMS V7.1 > Customizing > Customizing Rule Team Server), the example Ant task commands do not specify all the arguments needed for the repackaging of the Rule Team Server archive.Depending on your application server, you must use the repackage-ear or the repackage-war Ant task. For more information on the arguments to use for the repackaging of the Rule Team Server archive, see WebSphere ILOG JRules BRMS V7.1 > Installing > Installing JRules modules on WebSphere Community Edition > Installing Rule Team Server on WebSphere Application Server Community Edition V2.1 > Completing the installation using Ant tasks > Repackaging the Rule Team Server WAR.
Contrary to a number of references in the installation topics, Rule Execution Server and Rule Team Server are not supported on Tomcat clusters.Installation instructions that imply Tomcat clustering support should be ignored.
The following topic contains a misleading restriction on custom value providers:
WebSphere ILOG JRules BRMS V7.1 > Samples > Rule Studio samples > Rule Studio authoring extension samples > Custom value editor for Rule Studio sample.
The restriction states "Only Swing graphical components can be used as custom value providers", which implies that Rule Studio only supports Swing based editors.
In fact, this sample is using a Swing based custom editor, but it is also possible to attach custom SWT editors inside the Intellirule editor. The support for SWT editors, as well as Swing editors is described in: WebSphere ILOG JRules BRMS V7.1 > Customizing > Customizing Rule Studio > Customizing rule authoring > Extending BOM value types > Implementing a value editor > Creating a value editor.


Known limitations and issues in V7.1.1.1





Rule Studio


ErrorsComments and workarounds
BOM Update does not handle generics correctly. Ignore the action related to generic classes that are not found in the XOM, the actions are erroneous.
If Rule Studio automatic build is disabled, problems in a ruleflow are only reported in the Problem View, and not in the ruleflow graph.Close and reopen the Ruleflow Editor to update the graph with the errors.
Cut, copy and paste do not always work as expected in the Ruleflow Editor. If the Edit > Paste command does not work, use Ctrl+V to complete the operation.
Shortcuts do not work in the documentation, use the right-click menu.
In a ruleflow, if you join two transitions with a branch node a compilation error is thrown.Remove the branch node and connect the transitions directly to the next task.
If a rule and a decision table have similar names, a naming conflict is detected during ruleset parsing.Rename the rule so that the generated name of the decision table does not conflict with it.
When refactoring a ruleset parameter name, templates that use this name are not refactored.Refactor the rule templates manually using the errors reported.
The "ruleflows which may select this rule" query does not find results if a ruleflow contains a subflow. Do not use this query if you have subflows.
GB 18030 Phase 2 characters are lost when pasting from an external source into the Condition Column window in Rule Studio. Do not copy GB 18030 Phase 2 characters in a decision column editor.
In BAL, when assigning a literal value to an attribute of type java.lang.Float, the literal is considered as a double (15.5d) and then cast to a float. This causes a rounding error. Use either the float or the double attribute.
In the Decision Table Editor, when you select a double/float value and use the auto-filled value (drag the lower right corner of the cell and select the destination rows), some of the auto-filled values are not precise.
For example, if the original value in the first row is 1.39, the auto-filled value in the second row becomes 1.3899999999999997.
This problem only happens to some auto-filled values. To resolve the problem, either manually adjust the erroneous values or avoid using the auto-fill feature.
A class that has the same name as a package can lead to a LinkageError exception during ruleset parsing if you use this package to initialize a parameter value.Remove the reference to the package in the method used to initialize the parameter.
You cannot edit rules created in a locale that is different to the Rule Studio locale. Parameters and variables cannot be found in this case.Only use Rule Studio in the locale of the project that you intend to edit. Do not mix rules in different locales in the same rule project.
If an automatic variable and a parameter have the same name, conflicts are detected when writing rules. Sometimes the incorrect variable is used in the translated IRL.Either disable the automatic variable or rename the parameter or local binding to avoid the conflict with the automatic variable name.
There is an issue regarding dynamic domains when migrating rule projects from JRules V6 to V7.1. There is a difference in the way dynamic domain elements are deprecated between V6.7 and V7.
  • In V6.7, the element is noted as deprecated in both the .voc and the .bom files.
  • In V7, it is only noted in the .bom file.

If you deprecate an element in V6.7, migrate the project to V7, then restore the element in the domain. In V7, the element remains as deprecated unless you remove the deprecated property from the .voc file.


Rule Team Server



ErrorsComments and workarounds
In Chinese and Japanese the completion menu of the Web Intellirule Editor does not appear if CTRL+space is used after an ideograph.Insert space characters or use the Guided Editor.
Properties defined in the common model are not visible in the ruleflow. The ruleflow is not a managed artifact in Rule Team Server and does not inherit the common properties. You need to define the properties specifically on the ruleflow element.
If you try to copy or paste some text in the Web Intellirule Editor, an error message explains what you have to do in order to authorize the copy-paste operations in Rule Team Server.
The suggested content for user.js is incorrect, quotes around property names and values are missing.
The correct content to add in user.js is:
user_pref("capability.policy.policynames", "allowclipboard");
user_pref("capability.policy.allowclipboard.sites", "localhost:8080");
user_pref("capability.policy.allowclipboard.Clipboard.cutcopy", "allAccess");
user_pref("capability.policy.allowclipboard.Clipboard.paste", "allAccess");
When using a DB2 database you could encounter a "Statement is closed" exception at the end of a long ruleset archive generation.Increase the connection timeout: in the WAS administration console, at the datasource level, in the "connection pool properties" panel.
The Publish command in Rule Team Server is enabled while a publish of RuleDocs is running. If you publish a second time the resulting file may be corrupted. Click the Publish button once. If the file is corrupted delete the document and republish it.
After synchronizing a rule project with a BOM entry that is deleted and replaced by another BOM entry with the same name, no conflicts are detected. This causes duplication in the Rule Team Server database. Delete the project in Rule Team Server and republish it.
If there are double quotes added to an entry of a collection in the inline cell editor of a decision table, all subsequent operations on the cell use a lot of memory and processor usage is high. As a result it look like the decision table is locked. If you intend to have a double quote in one entry of a collection, use the editor at the top of the decision table to make the modification.
You can also change the value of the ilog.rules.brl.parsing.ErrorRecoveryTimeout parameter to 2000 for example, to get a better response time. The parameter is in the ilog.rules.brl.parsing.parser.earley/preferences.properties file (in brlparsing.jar).
If you edit a decision table using Internet Explorer 7 in a non-maximized window, the size of a drop down list is limited even though there is extra space after performing the right scroll. This is a limitation of Internet Explorer 7. Maximize the Internet Explorer 7 window and the drop down list displays as expected.
Using the Web Intellirule Editor to edit a rule in a locale that is different from the persistence locale raises an exception on the server if the vocabulary is incomplete.Restart the server. and make sure you have a complete vocabulary for the language. Alternatively, edit with the Guided Editor.


Rule Execution Server



ErrorsComments and workarounds
The list of parameters in the deployment descriptor for the Rule Execution Server Console has been updated. The list of the parameters in the topic WebSphere ILOG JRules BRMS V7.1 > Rule Execution Server Console online help > Monitoring and managing the server > Configuring the Rule Execution Server Console Web application is not up-to-date. The updated context parameters contained in the /WEB-INF/web.xml file are documented in the file itself. The list of context parameters is as follows:
  • ilog.rules.res.HELP_CONTEXT
    The Rule Execution Server online help context-root.
  • ilog.rules.res.HELP_INDEX
    The Rule Execution Server online help index.
  • ilog.rules.res.HELP_TOPIC
    The Rule Execution Server online help topic.
  • ilog.rules.res.HTDS_CONTEXT
    The Hosted Transparent Decision Services context-root.
  • ilog.rules.res.SSP_CONTEXT
    The default context-root used for ssp.
  • ilog.rules.res.RTS_CONTEXT
    The Rule Team Server context-root.
  • log4j-init-filename
    The LOG4J configuration file.
  • persistenceType
    The persistence type, either data source or file.
  • filePersistenceDirectory
    Used only when the persistenceType parameter is set to file. It is the root directory for the file persistence, this can be an absolute or relative path.
  • ilog.rules.res.trace.DECISIONWAREHOUSE_CONFIGURATIONS
    The list of decision warehouse configurations available in the Rule Execution Server Console. This is a list of names separated with a comma. For each decision warehouse configuration, a <context-param> with the same name must be declared in the web.xml file. The value of this parameter is a string that begins with factoryClassname=FULLY_QUALIFIED_NAME_ OF_THE_TRACE_DAO_FACTORY_ FOR_THIS_CONFIGURATION, optionally followed by a semicolon (;) and the list of properties to initialize the trace DAO factory. Each property in the list is defined as PROPERTY_NAME=PROPERTY_VALUE and the properties are separated by a semicolon (;).
  • defaultDWConfiguration
    The default decision warehouse configuration. Traces are saved in the decision warehouse database that is created during the installation of Rule Execution Server.
  • ilog.sam.application
    Specify an application name for SAM.
  • JMX_XU_QUERY_PART
    Specify a subset of XUs visible from the console.
  • JMX_DS_QUERY_PART
    Specify a subset of decision services visible from the console. Possible keys and values depend on the application server. For example, on WebSphere the cell name, node name, and server name are added to MBean object names so you can search for decision services deployed under a specific WebSphere node with node=mynode.


Installers



ErrorsComments and workarounds
While running the Japanese installer, in the step to select a JVM the requirements regarding the supported JDK for WebSphere CE is not displayed. Choosing a non-supported JVM could prevent you from using the Sample Server. When choosing the Java Virtual Machine be aware that the Sample Server runs on IBM WebSphere Server CE, which supports only the following JDKs:
* Sun JDK Version 5.0
* IBM 32-bit SDK for Windows version 5.0 or 6.0
* IBM 32-bit SDK for Linux x86 version 6.0
While installing the Rules for .NET product in a localized version the prerequisite HTML page does not displayed properly. Use the feedback in the installer panel to identify what is missing from the prerequisite and take the appropriate actions.

Rule Studio for .NET



ErrorsComments and workarounds
The date format for parameters in a decision table are not localized. The parameters are always displayed in English.

Rule Solutions for Office



ErrorsComments and workarounds
The shortcut to the Rule Solutions for Office documentation in the Start menu does not work.The language of the OS and the language of Visual Studio and Office must be the same. The documentation is available online here.

Rule Execution Server .NET



ErrorsComments and workarounds
When installing Rules for .NET into a folder that contains non-English characters in the name, the rule execution persistence service and the rule execution management services fail to start.The issue comes from the characters encoded in this configuration file :
C:\Program Files\IBM\WebSphere\ILOG Rules for .NETアイウか鯵表噂ソ竹十\Rule Execution Server for .NET\Bin\Public Assemblies\ILOGExecutionServerPersistenceService.exe.config

Add the encapsulating elements to the following line to start the services:
<add key="ILOG.Rules.ExecutionServer.Persistence.BaseDirectory" value="C:\Program Files\IBM\WebSphere\ILOG Rules for .NETアイウか鯵表噂ソ竹十\Rule Execution Server for .NET\Bin\Persistence"></add>


Known issues in documentation



ErrorsComments and workarounds
Documentation does not explain what JRules libraries to use in the following topic: WebSphere ILOG JRules BRMS V7.1 > Customizing > Customizing Rule Studio > Customizing rule authoring > Implementing dynamic domains > Creating a dynamic domain.The implemented interface is defined in vocbom.jar (ilog.rules.vocabulary.bom plug-in).
To be able to implement this interface, you must reference the correct libraries in your Java project.
Add the following libraries as dependencies of your project:
  • vocbom.jar from the ilog,rules.vocabulary.bom eclipse plug-in
  • ruleshared.jar from the ilog.rules.shared eclipse plug-in
  • jrules-engine.jar from <InstallDir>/studio/lib

[{"Product":{"code":"SS6MTS","label":"WebSphere ILOG JRules"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Maintenance","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.1.5;7.1.1.4;7.1.1.3;7.1.1.2;7.1.1.1;7.1.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SS6MUU","label":"WebSphere ILOG Rule Team Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Maintenance","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}},{"Product":{"code":"SS6MXF","label":"WebSphere ILOG Decision Validation Services"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Maintenance","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"7.1.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SS6MYC","label":"WebSphere ILOG Rule Solutions for Office"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Maintenance","Platform":[{"code":"PF033","label":"Windows"}],"Version":"7.1.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SS6MVU","label":"WebSphere ILOG Rules for .NET"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":null,"Platform":[{"code":"PF033","label":"Windows"}],"Version":"7.1.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21498138