IBM BPM, V8.0.1, All platforms > Create processes in IBM Process Designer > Modeling processes > Building services > Building a Decision service > Export rules for use in Rule Studio

Configure a remote Decision service

You can include a rule application from a remote ILOG JRules Rule Execution Server in your Decision service.

After you have exported rules in a rule component from IBM BPM, and imported the rule project into IBM WebSphere ILOG Rule Studio, you can configure your Decision service to include a JRules Decision Service component. When you specify the correct rule execution server and port settings, the JRules Decision component establishes a connection between Process Designer and the Rule Execution Server that contains the imported rule project.


Procedure

  1. Verify that you are working in the Decision service where you want to add the JRules Decision Service.
  2. Remove the BAL Rule component that contains the rules you exported.

  3. Drag a JRules Decision Service component from the palette to the service diagram, and place it in the same location as the deleted BAL Rule component. Reconnect any sequence lines to other activities or services.

  4. Select the new JRules Decision Service component, then click Implementation in the Properties tab.

  5. In the Discovery section, enter the following information to connect to the Rule Execution Server that contains the rules that you want to use.

    Input required to connect to the Rule Execution Server
    Field Action
    Server Select the server that you want from the list of ILOG Rules Server variables. See the related topic "Setting environment variables" for more information.
    SOAP Port Specify a port for the SOAP connection if the Rule Execution Server is running on WebSphere Application Server.
    User name Enter a user name if the JRules server requires a secure connection.
    Password Enter the password if the JRules server requires a secure connection.

    The SOAP port, user name, and password fields accept embedded JavaScript expressions, so variables can be used to provide those values.

  6. Click Connect.

  7. In the Rule section, select the Rule App that you want from the menu, then select the version that you want to use. If a secure connection to the Rule Execution Server has not been established, the menu is not populated. In this case, manually enter the name and version of the Rule App and Rule Set that you want to use. The names must be accurate for the next step to work.

  8. Click Generate Types.

  9. In the Generating Types window, make sure that the Generate request/response wrapper types option is not selected. Click Next.

  10. Click Finish when type generation is complete.

  11. In the Properties section, click Data Mapping.

  12. Click the auto-map icon in upper right corner of the Input Mapping section. The Create variables for auto-mapping window opens, listing the private variables needed for input parameters from the selected Rule App.

  13. Click to select each variable to create in your Decision service and then click OK.

  14. Click the auto-map icon in upper right corner of the Output Mapping section. The Create variables for auto-mapping window opens, listing the private variables needed for output parameters from the selected Rule App.

  15. Click to select each variable to create in your Decision service and then click OK.
  16. Save the updated Decision service.

Export rules for use in Rule Studio


Related tasks:
Scenario: Exporting rules to a Rule Execution Server


Related information:

Deploying from Rule Studio