Professional Documents
Culture Documents
6
Installing the JRules Modules on
Sun Application Server 8.2
COPYRIGHT NOTICE
Copyright © 1987-2007, by ILOG S.A., 9 Rue de Verdun, 94253 Gentilly Cedex, France,
and ILOG, Inc., 1195 West Fremont Avenue, Sunnyvale, California 94087-3832, USA. All
rights reserved.
Trademarks
ILOG, the ILOG design, CPLEX, and all other logos and product and service names of
ILOG are registered trademarks or trademarks of ILOG in France, the U.S. and/or other
countries.
All other company and product names are trademarks or registered trademarks of their
respective holders.
Java and all Java-based marks are either trademarks or registered trademarks of Sun
Microsystems, Inc. in the United States and other countries.
Microsoft, Windows, and Windows NT are either trademarks or registered trademarks of
Microsoft Corporation in the United States and other countries.
C O N T E N T S
Contents
Preface
This section contains instructions on how to install the JRules modules on the Sun
Application Server, Version 8.2 (formerly Sun ONE Application Server).
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
Note: Sun Application Server 8.2 Personal Edition does not support clustering
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 roles.
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 right groups in your application server when you setup security
access.
This section provides instructions on installing the Rule Team Server JRules module on Sun
Application Servers.
In this Section
Installing Rule Team Server on Sun Application Server 8.2
Database User Permissions
Completing the Installation Using the Installation Manager
Completing the Installation Using Ant Tasks
Opening Rule Team Server
Note: If you have rule projects created before the 6.6 version of JRules, you will have to
migrate the database schema, as described in the About ILOG JRules 6.6 guide.
};
4. Click Next.
Review the connection pool general settings.
5. Click Next.
Review the settings for your connection pool.
Click Finish.
Your new connection pool is visible:
6. Test the connection before moving on:
a. Type jdbc/ilogDataSource for the JNDI Name and choose the connection pool
that you created (for example, RTSPool).
To add a user:
Note: You may want to make a copy of the EAR before modifying it.
Validator
(optional)
Eligibility
(optional)
Note: Groups declared here must be uploaded to the database after the EAR has been
deployed (see Completing the Installation Using the Installation Manager).
Note: Deploying the Rule Team Server EAR sets the persistence locale. Once you save a
rule to the database, you should no longer change the persistence locale. If you wish to
install Rule Team Server in a language other than English, take note of the instructions
provided in Persistence Locale.
<InstallDir>\teamserver\applicationservers\sunas82\jrules-
teamserver-SUNAS82.ear
5. Click Next.
<InstallDir>\teamserver\online-help\rtsonlinehelp.ear
5. Click Next.
6. Click OK.
Operation
Note: The database privilege types differ across the supported databases. The operation of
defining these privileges should be performed by a database administrator.
Using the Installation Manager is the recommended way to complete/modify the installation
once you have deployed the Rule Team Server EAR to your application server.
Note: To access the Installation Manager, you must have administrator privileges as well
as the rtsInstaller role when you log on. For example, if you followed the sample users
creation steps, log on as rtsAdmin.
Once your installation is complete, Rule Team Server will be ready to use but will not
contain a rule project. If you open Rule Team Server at this point you will see the following:
Note: If you have rule projects created before the 6.6 version of JRules, you will have to
migrate the database schema, as described in the About ILOG JRules 6.6 guide.
Related Tasks
Database Schema
Message Files
Groups
Persistence Locale
Configuration Parameters
Publish a Project
Working with the Rule Team Server Ant Tasks
Database Schema
Extensions to the Rule Team Server rule model are stored in two XML files (see the
Customizing JRules guide for more information on defining common model extensions).
One of the files contains the model description itself (usually, the .brmx extension is used),
and the second one contains data to initialize enumerations and hierarchies (usually, the
.brdx extension is used).
To configure the database using the Installation Manager:
1. Select the files that contain your rule model. You can use the default ones provided or
select your customized extensions.
Message Files
Message files contain the display text associated with the extensions to the rule model
contained in the .brmx and .brdx files, for example:
status=Status
effectiveDate=Effective Date
expirationDate=Expiration Date
new=New
defined=Defined
Note: The contents of the messages files must respect the ISO-LATIN-1 standard (see
http://java.sun.com/j2se/1.4.2/docs/api/java/util/Properties.html).
If you use the default rule model when creating your database, this default messages file will
automatically be sent to the database. Otherwise, use the Installation Manager to upload
your own message files.
You will need a messages file for each locale that you use. Messages files are identified in
the Installation Manager by their locale:
1. A locale.
Groups
In addition to creating groups in your application server when you setup security access, you
will have to use the Setup Groups page of the Installation Manager to upload groups to the
database.
Note: You only need to do this if you wish to use the Rule Team Server project access and
permissions mechanisms (see the sections on Groups and Permissions in the Rule Team
Server Online Help).
You will need to add all the groups that you wish to see appear in the available list when
enforcing project security or setting permissions in Rule Team Server. Ideally, you will not
upload the default groups rtsUser and rtsConfigManager, but rather create and upload
custom groups.
Persistence Locale
The persistence locale is used to determine the language in which rules are stored in the Rule
Team Server database. It is set initially to en_US when you deploy the Rule Team Server
EAR to your application server, which means that the rules in the database are stored in US
English.
Changing the persistence locale does not change the language in which rules appear in Rule
Team Server. Changing the persistence locale in Rule Team Server is only necessary to
match the locale of Rule Studio when synchronizing your rule projects.
You should not change the persistence locale after you save a rule to the database.
Note: The persistence locale is controlled by the value of the <locale> key in ilog/
rules/teamserver/preferences.properties in the lib/rts.jar and set when
the EAR is deployed. The Installation Manager overrides this setting.
Related Tasks
Database Schema
Message Files
Groups
Configuration Parameters
Publish a Project
Working with the Rule Team Server Ant Tasks
Configuration Parameters
Many tasks related to customizing Rule Team Server require configuration parameters to be
set or removed.
The following table gives a description of the main configuration parameters available in:
lib/rts.jar (/ilog/rules/teamserver/model/preferences.properties)
<extractorValidator>.class Specify a ruleset extractor validator class to use for the given
extractorValidator name. The class must implement the
ilog.rules.commonbrm.extractor.IlrExtractorValidator
interface. Once defined, specify this name as the extractor validator to
use when defining a ruleset extractor.
build.path Define where the cache of the IRL should be on the file system. The
path is computed as follows: first, use this property with the name of the
user who launched the server as the root for the cache
(<build.path>_<username>). If it is not defined, use the system
property java.io.tmpdir and add rtscache (for example, <temp
dir>/rtscache_<username>). If the system property is not defined,
use the server directory and add rtscache (for example, <server
dir>/rtscache_<username>).
brl.verbalizers Specify the list of locales for which a BAL verbalizer is defined.
brl.verbalizer.<locale> Specify the verbalizer class for the given locale. The class must
implement the interface:
ilog.rules.vocabulary.verbalization.IlrVerbalizer
Related Tasks
Database Schema
Message Files
Groups
Persistence Locale
Publish a Project
Working with the Rule Team Server Ant Tasks
Note: If you have rule projects created before the 6.6 version of JRules, you will have to
migrate the database schema, as described in the About ILOG JRules 6.6 guide.
Note: To execute these Ant tasks, you must use the same Java Virtual Machine version and
vendor as the one used by the application server.
The Ant task parameters start with -D and allow you to set some values such as:
◆ -Dserver.url=<server url> - Used to specify the URL of the application server to
connect to.
◆ -DdatasourceName=<data source name> - Used to specify the JNDI name of the
data source to use for the task (default is jdbc/ilogDataSource).
For example:
# Default properties
# ------------------------------------
datasourceName=jdbc/ilogDataSource
server.host=localhost
outputFile=output.sql
# JBoss 4 Settings
# ------------------------------------
# appserver.name=jboss40
# protocol=jnp://
# server.port=1099
# server.url=${protocol}${server.host}:${server.port}
# specificPortVMSettings=-
Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory -
Djava.naming.provider.url=${server.url} -
Djava.security.auth.login.config=${myenv.JBOSS_HOME}/client/auth.conf
Also, take note of any special instructions in this file concerning your application server.
The appserver.name property configures the class path for the Ant tasks. If you need to
add specific drivers to your class path, you can add them to <installDir>/teamserver/
lib/classpath-teamserver.xml.
Note: Make sure the environment variable corresponding to your application server (for
example, JBOSS_HOME) is properly set before running any Ant task.
Related Tasks
Creating the Database Schema
Defining and Uploading Message Files
Uploading Groups to the Database
Setting the Persistence Locale
Adding or Removing Configuration Parameters
Repackaging the Rule Team Server EAR
Note: Running the tasks in this section requires that your environment be correctly setup,
as described in Working with the Rule Team Server Ant Tasks.
This section describes how to create the database schema if you are using Ant tasks to
complete/configure your installation.
Extensions to the Rule Team Server rule model are stored in two XML files. One of the files
contains the model description itself (usually, the .brmx extension is used), and the second
one contains data to initialize enumerations and hierarchies (usually, the .brdx extension is
used).
You can use Ant tasks to load the rule model from the two XML files and build the SQL
script required to get the proper database schema.
To create or update the database schema:
1. Create the SQL script required to create or update the database schema (see Step 1 -
Create the Script).
2. Execute the SQL script that you created (see Step 2 - Execute the Script).
3. Once the schema is created, upload the extensions files in the database (Step 3 - Upload
the Extension).
4. Optionally, you can upload new roles.
For convenience, you can run the set-extensions Ant task, which runs gen-create-
schema + execute-schema + upload-extensions + upload-roles, with these
parameters:
◆ -Dserver.url=<server url>
Note: To execute these Ant tasks, you must use the same Java Virtual Machine version and
vendor as the one used by the application server.
Alternatively, you can do this step-by-step, which is useful if you want to look at the
generated SQL schema.
The task connects to the given data source from the given application server. It checks if this
data source points to an existing Rule Team Server database. If not, it builds the SQL script
to create a fresh database schema to store the model. Otherwise, it builds the SQL script
required to update the existing database schema.
Step 2 - Execute the Script
To execute the SQL script that you created, run the execute-schema Ant task with these
parameters:
◆ -Dserver.url=<server url>
The description is stored in the database so that Rule Team Server applications may load it
when they start. It is also used by gen-create-schema to get the current model
description in order to run a diff with the new schema.
◆ [-DoutputFile=<SQL file>] - The name of the file that stores the generated SQL
script. If this parameter is not given, the task creates a file named output.sql in the
directory defined as basedir in build.xml, (..) by default.
For example:
ant gen-drop-schema ... -DextensionModel=my_model_file.brmx -
DoutputFile=my_sql_file.sql
The task connects to the given data source from the given application server. It reads the
model description given in the parameters, and generates the SQL script required to drop the
existing schema. Since many database tables are linked through foreign keys, they have to
be dropped in a specific order, and the script generation will handle these constraints.
To execute the SQL script that you created, run the execute-schema Ant task with these
parameters:
◆ -Dserver.url=<server url>
◆ [-Dfile=<SQL file>] - The name of the file to execute, which corresponds to the
script you created. If this parameter is not given, the task attempts to execute a file
named output.sql in the directory defined as basedir in build.xml, (..) by
default.
For example:
ant execute-schema ... -Dfile=my_sql_file.sql
Related Tasks
Publish a Project
Working with the Rule Team Server Ant Tasks
Defining and Uploading Message Files
Uploading Groups to the Database
Setting the Persistence Locale
Adding or Removing Configuration Parameters
Repackaging the Rule Team Server EAR
Erasing a Project from the Database
Note: The contents of the messages files must respect the ISO-LATIN-1 standard (see
http://java.sun.com/j2se/1.4.2/docs/api/java/util/Properties.html).
You will need a messages file for each locale that you use. Upload the messages file to Rule
Team Server by running the upload-messages Ant task with these parameters:
◆ -Dserver.url=<server url>
◆ -Dlocale=<locale>
◆ -DmessageFile=<message file>
For example:
ant upload-messages ... -Dlocale=en_US -
DmessageFile=mymessages.properties
Note: Running this task requires that your environment be correctly setup, as described in
Working with the Rule Team Server Ant Tasks.
Related Tasks
Working with the Rule Team Server Ant Tasks
Creating the Database Schema
Uploading Groups to the Database
Setting the Persistence Locale
Adding or Removing Configuration Parameters
Repackaging the Rule Team Server EAR
Erasing a Project from the Database
Note: You only need to do this if you wish to use the Rule Team Server project access and
permissions mechanisms (see the sections on Groups and Permissions in the Rule Team
Server Online Help).
Add all the groups that you wish to see appear in the available list when enforcing project
security or setting permissions in Rule Team Server. Ideally, you will not upload the default
groups rtsUser and rtsConfigManager, but rather create and upload new groups.
You should not upload either the rtsAdministrator group (since the Administrator has
all security access and permissions regardless) or the rtsInstaller group (since a user
cannot be a member of this group only).
To store in the database the list of groups that will be used by the application, run the
upload-roles Ant task with these parameters:
◆ -Dserver.url=<server url>
Note: To execute these Ant tasks, you must use the same Java Virtual Machine version and
vendor as the one used by the application server.
Related Tasks
Working with the Rule Team Server Ant Tasks
Creating the Database Schema
Defining and Uploading Message Files
Setting the Persistence Locale
Note: The persistence locale is controlled by the value of the <locale> key in ilog/
rules/teamserver/preferences.properties in the lib/rts.jar and set when
the EAR is deployed. The Installation Manager overrides this setting.
Related Tasks
Working with the Rule Team Server Ant Tasks
Creating the Database Schema
Defining and Uploading Message Files
Uploading Groups to the Database
Adding or Removing Configuration Parameters
Repackaging the Rule Team Server EAR
Erasing a Project from the Database
lib/rts.jar (/ilog/rules/teamserver/model/preferences.properties)
<extractorValidator>.class Specify a ruleset extractor validator class to use for the given
extractorValidator name. The class must implement the
ilog.rules.commonbrm.extractor.IlrExtractorValidator
interface. Once defined, specify this name as the extractor validator to
use when defining a ruleset extractor.
build.path Define where the cache of the IRL should be on the file system. The
path is computed as follows: first, use this property with the name of the
user who launched the server as the root for the cache
(<build.path>_<username>). If it is not defined, use the system
property java.io.tmpdir and add rtscache (for example, <temp
dir>/rtscache_<username>). If the system property is not defined,
use the server directory and add rtscache (for example, <server
dir>/rtscache_<username>).
brl.verbalizers Specify the list of locales for which a BAL verbalizer is defined.
brl.verbalizer.<locale> Specify the verbalizer class for the given locale. The class must
implement the interface:
ilog.rules.vocabulary.verbalization.IlrVerbalizer
The following Ant tasks can be used to add or remove configuration parameters:
◆ set-config-param - Sets a configuration parameter for a given user. If the user is not
specified, it sets a global parameter.
Parameters:
● -Dserver.url=<server url>
● [-Duser=<username>]
● -Dkey=<parameter key>
● -Dvalue=<parameter value>
Example: ant set-config-param ... -Dkey=locale -Dvalue=en_US
◆ remove-config-param - Drops the given configuration parameter for a given user if
specified. Otherwise, it drops the global configuration parameter.
Parameters:
● -Dserver.url=<server url>
● -Dkey=<parameter key>
● [-Duser=<username>]
● -Dkey=<parameter key>
Note: See Working with the Rule Team Server Ant Tasks for help on setting up your
environment to correctly execute the Rule Team Server Ant tasks.
Related Tasks
Working with the Rule Team Server Ant Tasks
Creating the Database Schema
Defining and Uploading Message Files
Uploading Groups to the Database
Setting the Persistence Locale
Repackaging the Rule Team Server EAR
Erasing a Project from the Database
Note: See Working with the Rule Team Server Ant Tasks for help on setting up your
environment to correctly execute the Rule Team Server Ant tasks.
You can add new .jar files to the Rule Team Server EAR by running the repackage-ear
Ant task with these parameters:
◆ -DtargetEar=<target ear>
◆ -DsourceEar=<source ear>
Note: See Working with the Rule Team Server Ant Tasks for help on setting up your
environment to correctly execute the Rule Team Server Ant tasks.
You can erase a project from Rule Team Server, including all its content, by running the
drop-project Ant task with the following parameters:
◆ -Dserver.url=<server url>
◆ -DprojectName=<project name>
Note that the project cannot be dropped if some other projects depend on it.
Related Tasks
Working with the Rule Team Server Ant Tasks
Creating the Database Schema
Defining and Uploading Message Files
After completing the installation, Rule Team Server is ready to be used but does not contain
a rule project. If you open Rule Team Server at this point you will get the following:
Publish a Project
After completing the installation, Rule Team Server is ready to be used but does not contain
a rule project. If you open Rule Team Server at this point you will get the following:
You will have to publish a rule project from Rule Studio. Also, if you want to carry out the
tutorials found in the Rule Team Server online help, you will have to publish the following
rule projects from Rule Studio:
◆ loanvalidation-rules (with loanvalidation-xom)
◆ loanvalidation-rules-dependent
1. In Rule Studio click File > Import > General > Existing Projects into Workspace, and
click Next.
3. Select the projects and click Finish. Then publish them to Rule Team Server.
Related Tasks
Completing the Installation Using Ant Tasks
Completing the Installation Using the Installation Manager
This section provides instructions on installing the Rule Execution Server JRules module on
Sun Application Servers.
In this Section
Installing Rule Execution Server on Sun Application Server 8.2
Rule Execution Server Database Driver Issues
// XU permissions
grant {
// MBean
permission javax.management.MBeanServerPermission "findMBeanServer";
permission javax.management.MBeanTrustPermission "register";
permission javax.management.MBeanPermission "*", "*";
permission java.lang.RuntimePermission "getClassLoader";
// File persistence
permission java.io.FilePermission "${com.sun.aas.instanceRoot}${/}-",
"read";
// Tx support
permission java.io.SerializablePermission "enableSubstitution";
// XU Dump
permission java.lang.RuntimePermission "shutdownHooks";
permission java.util.PropertyPermission "*", "read,write";
// Logging
permission java.util.logging.LoggingPermission "control";
// Engine
permission java.lang.RuntimePermission "createClassLoader";
// Translation
permission java.lang.reflect.ReflectPermission "suppressAccessChecks";
// Sequential Mode
permission java.lang.RuntimePermission "setContextClassLoader";
permission java.lang.RuntimePermission "accessDeclaredMembers";
// SAM
permission java.util.PropertyPermission "user.dir", "read";
permission java.util.PropertyPermission "user.name", "read";
permission java.util.PropertyPermission "ilog.sam.*", "read";
permission java.util.PropertyPermission "ilog.sam.application",
"read,write";
permission java.lang.RuntimePermission "modifyThreadGroup";
permission java.lang.RuntimePermission "modifyThread";
permission java.lang.RuntimePermission "stopThread";
permission java.net.SocketPermission "*", "resolve";
permission java.net.SocketPermission "usagereport.p.jum1.ilog.com:80",
"connect";
permission java.net.SocketPermission "usagereport.p.jum2.ilog.com:80",
"connect";
permission java.net.SocketPermission "usagereport.p.jum3.ilog.com:80",
"connect";
permission java.lang.RuntimePermission
"accessClassInPackage.sun.util.logging.resources";
};
For the Rule Execution Server Console permissions, the codeBase is defined as:
file:${com.sun.aas.instanceRoot}${/}applications${/}j2ee-apps${/}jrules-bres-
management-SUNAS82${/}-
A readme file in this directory provides additional information on the scripts provided.
The schema_derby.sql script creates a schema named BRES, so you may need to
reconfigure your datasource so that it connects to the Derby database as user BRES.
For the Oracle database, in addition to tables and indexes, a sequence and a trigger are also
created. The SQL scripts schema_oracle.sql and schema_oracle_plsql.sql are
provided for this task. The scripts should be run in the following sequence:
1. schema_oracle.sql
2. schema_oracle_plsql.sql
When using an Oracle database, you should run all scripts in the SQL Plus client.
Any tool that can handle SQL can be used to import and run the SQL scripts. The tools
provided for each database include:
◆ cview – Cloudscape
Note: There is no optimization in the scripts. For better performance, you can modify the
parameters that create the resources to fit your database configuration and data.
2. In the left pane open Resources > JDBC, and then in the right pane click Connection
Pools.
3. In the Connection Pool window, click New.
4. Click Next.
You can change the datasource classname if needed.
5. Click Next.
Review the settings for your connection pool. Complete additional properties for the
database (for example, User, Password, ServerName and DatabaseName if you have
selected a Derby database).
6. Click Finish.
9. Click OK.
2. In the left pane click Configuration, and then in the right pane click Security.
The Default Realm used is displayed in the right pane.
3. In the left pane, under Security open Realms and click file.
6. Click OK.
The new user is displayed as follows:
Firstly, you must enable JDK logging in the XU. To configure the logging, you should use
the management console of the Sun AS.
To enable JDK logging in the XU:
############################################################
# Handler specific properties
# Describes specific configuration info for Handlers.
############################################################
#java.util.logging.FileHandler.formatter = java.util.logging.XMLFormatter
java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter
# Limit the messages that are printed on the console to INFO and above.
java.util.logging.ConsoleHandler.level = INFO
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
The logging.properties file is used directly by the virtual machine (VM). You set the
location with the properties of the VM. You can use a different file by specifying a file name
with the java.util.logging.config.file system property. For example java -
Djava.util.logging.config.file=myfile.
Note: The inclusion of the XU log in the JDK logging is not supported in J2SE.
5. Click Next.
The upload may take a few moments to complete.
6. Click OK.
The deployed module is displayed as follows:
7. In the left pane open Resources > Connectors and click Connector Connection Pools.
9. Click Next.
The connection definition selected is javax.resource.cci.ConnectionFactory.
10. Click Next.
11. Verify the Connection Pool settings. Set Transaction Support to NoTransaction.
5. Click Next. If you change the Application Name, you must also change the name in the
codeBase used in server.policy. See Step 1. Configuring Java 2 Security
Permissions for more information.
6. Click OK.
5. Click Next.
6. Click OK.
2. Open the Rule Execution Server Console by typing bres at the root URL on the host
machine:
http://localhost:8080/bres
If your browser is not running on the same host as the application server, you can replace
localhost with <host>.
3. Sign in to the Rule Execution Server Console (the default user ID and password is bres/
bres).
5. Click Next.
6. Click OK.
7. Verify that the SSP module has been correctly deployed and is working:
b. Log on as user bres (or the user you created in the bres_admin group at Step 4.
Configuring Security)
c. Verify that the message The SSP application appears to have been
loaded successfully is displayed on a blank page.
<configuration
log4jFile="./data/log4j.properties"
handler="execution.trace.Handler"/>
<j2seExecution
persistenceMode="file"
persistenceProperties="ilog.rules.bres.xu.ruleset.fs.IlrFileRulesetInformationP
rovider.repositoryDirPath=c:/res-data-v6"
traceLevel="FINE"
traceAutoflush="true"
plugins="{pluginClass=ilog.rules.bres.ras.plugin.IlrExecutionTracePlugin},
{pluginClass=ilog.rules.res.decisionservice.plugin.IlrWsdlGeneratorPlugin}"/>
</ssp-setup>
</target>
◆ Through the Rule Scenario Manager Console, by selecting Admin > SSP Servers.
5. Click Next.
6. Click OK.
ORACLE XA Features
If you need to use XA features with an Oracle 9i database, you have to configure your
database and the server JVM. To do so, you have to run the two scripts initjvm.sql and
initxa.sql that are located in the directory:
ORACLE_HOME/javavm/install
For more information, please contact your DBA or your local ORACLE support.
This section provides instructions on installing the Rule Scenario Manager JRules module
on Sun Application Servers.
In this Section
Installing Rule Scenario Manager on Sun Application Server 8.2
// SSP Permission
grant codeBase "file:${com.sun.aas.instanceRoot}${/}applications${/}j2ee-
apps${/}jrules-ssp-SUNAS82${/}-" {
permission java.io.SerializablePermission
"enableSubclassImplementation";
};
For the Rule Scenario Manager Console permissions, the codeBase is set to:
file:${com.sun.aas.instanceRoot}${/}applications${/}j2ee-apps${/}jrules-ssp-
SUNAS82${/}-
Note that jrules-ssp-SUNAS82$ is the application name given to the Rule Scenario Manager
Console during deployment. If you change the application name during deployment, you
must also change the definition in the codeBase.
Restart the server to activate changes in the server.policy file.
Note: There is no optimization in the scripts. For better performance, you can modify the
parameters that create the resources to fit your database configuration and data, described
in Step 3. Setting the JVM Memory Size.
3. In the right pane click the tab JVM Settings then JVM Options.
5. Enter the appropriate Java memory setting for your data source using the parameter -
XX:MaxPermSize.
2. In the left pane open Resources and JDBC. Click Connection Pools.
4. Click Next.
You can change the datasource classname if needed.
5. Click Next.
Review the settings for your connection pool. Complete additional properties for the
database (for example, User, Password, ServerName and DatabaseName for a Derby
database).
6. Click the Ping button to verify the connection to the datasource.
7. Click Finish.
2. In the left pane open Configuration and click Security. The Default Realm used is
displayed in the right pane.
3. Under Security, open Realms and click file.
6. Click OK.
The new user is displayed as follows:
5. Click Next.
If you change the Application Name, you must also change the name in the codeBase
used in server.policy. See Step 1. Configuring Java 2 Security Permissions for more
information.
6. Click OK.
5. Click Next.
6. Click OK.