You create a Rule Execution Server configuration
project to store Rule Execution Server configurations.
About this task
A
Rule Execution Server configuration
provides the information that
Rule
Designer needs
to make a connection to
Rule Execution Server or
zRule
Execution Server for z/OS® when
you deploy a RuleApp.
Rule Execution Server configurations
are stored in a
Rule Execution Server configuration
project.
Procedure
To create a Rule Execution Server configuration
project:
- Click .
- On the New Project wizard page, expand Rule
Designer ,
select Rule Execution Server Configuration
Project, and click Next.
- On the New Rule Execution Server Configuration
Project page, enter the name of the project, and click Next.
The same naming constraints apply as in any Eclipse environment.
If a project with the same name exists, a message warns you and the Next button
is not available.
- On the Configure
Rule Execution Server page,
select the appropriate application server, and then click Next.
The Application server check box
is selected by default. If you clear it, the list of application servers
is disabled because you are in a Java™ SE
configuration, as displayed on the next wizard page when you click Next.
If
you are deploying to zRule
Execution Server for z/OS, you
must select Other as the type of application
server.
- If you use the Tomcat, JBoss, or WebLogic application server,
select a deployment directory.
The deployment directory
is used by the Scenario Service Provider (SSP) repackaging feature.
See Repackaging the SSP and Decision
Center archives.
- Enter your login and password for the Rule Execution Server console.
- To verify that the connection to the Rule Execution Server console
works, click Test connection.
If the application server is not configured or not started, the test fails and displays an error
message. If you use the default application server, start the sample server first (see Starting and stopping the sample server).
- Optional: Enter the URL of the client application,
and then click Next.
- On the RuleApp Deployment page, select
the persistence options.
Complete the fields as indicated
in RuleApp Deployment page.
- If you select to the Rule Execution Server Console,
the persistence settings of the console apply. This option is deactivated
for Java SE
configurations.
- If you select to a file system, RuleApps
are deployed to the res_data directory. You can
select a different deployment directory by clicking Browse.
Deploying to the file system is useful in a Java SE configuration but not in Java EE because no notification
takes place. See Rule Execution Server persistence layer.
- Select to a database for Java EE configurations
if you want to apply the notification mechanism. See Ant tasks for RuleApp management.
- Click Finish.
Results
The server name, the Rule Execution Server console
URL, and the application URL are stored in a <servername>.esc file
in the project directory. The login and password are stored in a configurations.xml file
in this directory:<workspace>/.metadata/.plugins/ilog.res.studio.res/.