Before you start: Opening the administration console

To configure Rule Execution Server on WebSphere® Application Server, you must follow specific steps. Some of them depend on the persistence type.

1. Make sure that you have a WebSphere Application Server profile.

   The predefined name of the first server profile is AppSrv01. If the profile does not exist, use the Profile Management Tool or the manageprofiles command to create it. Refer to the WebSphere Application Server documentation if necessary.

2. Start the server by clicking Start > All programs > IBM WebSphere > IBM WebSphere Application Server version_number > Profiles > AppSrv01 > Start the server
   Tip: As an alternative, first open the First Steps window from the Windows Start menu, and then start the server, and later the console, from the First Steps window.
3. Start the console by clicking Start > All programs > IBM WebSphere > IBM WebSphere Application Server version_number > Profiles > AppSrv01 > Administrative console You might have to pass the security steps of your browser.
4. Log in by entering the user name and password that you defined when you created the profile.

   For example: wasadmin and wasadmin.

   The WebSphere Integrated Solutions Console opens.

What to do next

In the first four steps, you set up a dedicated database and data source. Then, you activate security, create the database schema, and deploy the management EAR file, execution unit resource archive, and optionally the EAR file for transparent decision services.

The Rule Execution Server console includes an Installation Settings wizard. If you sign in as the administrator, you can use the wizard to create the database schema and run SQL drop statements that clear any existing Rule Execution Server database.

Note: Specific integration extensions are available from this URL: WebSphere Operation Decision Management Integration SupportPacs.

The following table summarizes the steps to configure Rule Execution Server on WebSphere Application Server, depending on the type of persistence.

Installation Steps		Persistence
		File	Data source	JDBC
Step 1: Selecting and applying the persistence type			Default persistence mode
Step 2: Restricting database user permissions
Step 3: Setting up your database		Not applicable
Step 4: Setting up a data source and connection pool	Creating a JDBC provider	Not applicable
	Creating a data source and connection pool	Not applicable
	Creating J2C authentication data	Not applicable
	Setting custom properties	Not applicable
	Testing the connection to the database	Not applicable
Step 5: Activating security on WebSphere Application Server	Creating users and groups
	Mapping user groups to the Monitor role
	Security policies for the Rule Execution Server console
Step 6: Deploying the Rule Execution Server MBean descriptors
Step 7: Deploying the XU RAR
Step 8: Deploying the Rule Execution Server management EAR file
Step 9: Creating a Rule Execution Server database schema		Not applicable
Step 10: Deploying the hosted transparent decision service EAR file		Optional	Optional	Optional
Step 11: Setting the DecodeUrlAsUTF8 custom property		Required if you deployed the EAR file for hosted transparent decision services (previous step).	Required if you deployed the EAR file for hosted transparent decision services (previous step).	Required if you deployed the EAR file for hosted transparent decision services (previous step).
Verifying the deployment and configuration		Optional	Optional	Optional