Welcome to ILOG JRules > Installing the JRules Modules

Installing JRules Modules

JRules consists of the following modules:

Rule Studio: Business rule application development tools for developers, modelers, and architects.
Rule Team Server: Business rule management tools for policy managers.
Rule Execution Server: A managed business rule execution platform that embeds the JRules engine.
Rule Scenario Manager: Provides a test and simulation environment for rules created with JRules.
Rule Engine: Integrated in both Rule Studio and Rule Execution Server; and can be used to embed an engine into an open architecture.

When installing JRules, you can choose to install either ILOG JRules tools for developers (Rule Studio, Rule Team Server Desktop Edition, Rule Scenario Manager Desktop Edition, and Rule Execution Server Desktop Edition), or an ILOG JRules Server Edition (Rule Team Server, Rule Scenario Manager, Rule Execution Server). The JRules installer allows you to install one of the following:

A desktop edition, with any combination of: Rule Studio, Rule Team Server Desktop Edition, Rule Scenario Manager Desktop Edition, Rule Execution Server Desktop Edition.
A Rule Team Server server edition.
A Rule Scenario Manager server edition.
A Rule Execution Server server edition.

Note

The main installer only installs JBoss on both the desktop and server editions.

Depending on what you have installed you will then have the following options:

Change the version of Eclipse where Rule Studio is installed.
Install Rule Team Server, Rule Execution Server, and Rule Scenario Manager on a supported Java EE application server other than JBoss by downloading a separate bundle. An installation bundle installs on top of a JRules installation, it does not ask whether the installation is a desktop or a server edition, it merely uses the license that was installed beforehand.
Install Rule Execution Server and Rule Scenario Manager on a Web server, namely Tomcat 5.5.
Install Rule Execution Server on Java SE.

To install a server edition of a module on an application server other than JBoss

Download the specific bundle.
Follow the installation instructions for that module on that application server.
Provide access information for the set of potential developers: login, password, host name, JNDI name, and so on.

If you intend to install the module on several server instances you must read the cluster deployment section in the documentation.

Preparing for installation

This section contains instructions on how to install the JRules modules on the supported application servers. To use any of the JRules modules on the J2EE platform, you will need to install a set of components on one of the supported application servers.

Each of the JRules modules requires that you first prepare your application server for installation. Preparing your application server will involve creating a data source and configuring the necessary security. Installation will consist of deploying an archive (or a set of archives), enabling the online help, and in the case of Rule Team Server an additional configuration step.

This configuration step includes:

Configuring the database.
Uploading message files.
Uploading roles.
Setting the persistence locale.
Adding configuration parameters.

It is also possible to customize the behavior of Rule Team Server. For more information, see Customizing Rule Team Server in the JRules developer documentation.

The following sections provide a basic introduction to archive deployment and security.

Archive Deployment

The archive files (EAR/WAR/RAR) included in the application server installers can be deployed to a server in different ways. You should refer to the application server documentation for a full understanding of the different options.

Security

Configuration of a secure mode on an application server provides ways to increase the security of the application that you deploy.

In secure mode an application server:

Checks access to the resources (access to a class using the reflection mechanism is not permitted without the correct security rights).
Manages access rights (the Rule Execution Server Console access is managed with this mechanism).

By default, Rule Execution Server is installed with a minimum of security. The Rule Execution Server Console application defines a specific role bres_admin. This role controls the access to the various JSP/Servlets.

There are no specific permissions implementation for Rule Execution Server MBeans. All that is required to access the MBeans using JMX is the right credentials.

Note

Security configuration of the Rule Execution Server may relate to your application/domain or server scoped enterprise security policy. You should review security settings for applications that call the Rule Execution Server with your J2EE application architect/system administrator as appropriate.

The installation of Rule Team Server is completed using an installation manager. This ensures that you create the correct groups in your application server when you setup security access.

Intended Audience

The intended audience for this guide is the person who develops, assembles, and deploys J2EE applications in a corporate enterprise. This guide assumes you are familiar with the following topics:

J2EE specification
HTML
Java programming
Java APIs as defined in the Java Servlet, JavaServer Pages (JSP), Enterprise JavaBeans (EJB), and Java Database Connectivity (JDBC) specifications
Structured database query languages such as SQL
Relational database concepts
Software development processes, including debugging and source code control

Installing JRules Modules

Preparing for installation

Archive Deployment

Security

Intended Audience

Related Links