Before you start: Opening the administration console

To configure the Decision Center consoles on WebSphere® Application Server, you must follow specific steps. Some are mandatory, while others are optional.

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

   The predefined name of the first server profile is AppSrv01. 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

If you have rule projects that were created with a previous product version, refer to the Migrating topics on how to upgrade the Rule Team Server database schema.

Note: A specific integration extension for the IBM® Process Server platform is available. For more information, see IBM Operational Decision Manager Integration SupportPacs.

The following table summarizes the steps to configure Decision Center on WebSphere Application Server.

Step		Required
Step 1: Restricting database user permissions
Step 2: Configuring database connectivity	Creating a DB2 database on z/OS	Optional
	Creating a JDBC provider
	Creating a data source and a connection pool
	Creating J2C authentication data	Optional
	Changing the custom properties of your data source	Optional
	Connecting to the database
Step 3: Configuring security	Creating users and groups	Optional
	Updating the security policies	Optional
Step 4: Deploying the Decision Center EAR file	Declaring custom groups	Optional
	Deploying the EAR file
	Changing the class loading sequence
Step 5: Verifying the deployment of the Decision Center Enterprise console
Step 6: Completing the configuration of the Decision Center consoles	Completing the configuration from the Decision Center Enterprise console	Select one of the two methods. Required for distributed platforms only.
	Completing the configuration by using Ant tasks