Configuring components on a stand-alone profile
After creating your database, configure Decision Server and Decision Center on a stand-alone WebSphere® Application Server profile.
- Before you start: Create the database and set the JDK.
- Step 1: Create an application server profile.
- Step 2: Augment the application server profile with Decision Server or Decision Center.
- Results: See the Operational Decision Manager components that you installed.
Instructional video
Prepare for this task by watching the following video:
Before you start: Create the database and set the JDK
Before creating a profile, create the databases dedicated to the Decision Server and Decision Center data. See Mandatory: Create the databases.
If you are using version 9 of WebSphere Application Server, the JDK is set to version 8 by default, so you do not need to run the managesdk commands.
Step 1: Creating an application server profile
Create a standard application server profile by using the manageprofiles.bat -create command and the following parameters. From <WAS_InstallDir>\AppServer\:
- Windows
-
.\bin\manageprofiles.bat -create -profileName ODM01 -templatePath .\profileTemplates\default -enableAdminSecurity true -adminUserName wasadmin -adminPassword wasadmin
- Linux
-
./bin/manageprofiles.sh -create -profileName ODM01 -templatePath ./profileTemplates/default -enableAdminSecurity true -adminUserName wasadmin -adminPassword wasadmin
- -profileName
- Use this parameter if you want a specific name like
ODM01
for your profile. Otherwise, WebSphere Application Server creates anAppSrv
profile with the next available number, for exampleAppSrv01
. - -templatePath
- You must use <WAS_InstallDir>\AppServer\profileTemplates\default, which is the location of the WebSphere Application Server template for a standard application server profile.
- -enableAdminSecurity
- You must set this parameter to true to enable WebSphere Application Server administrative security. Decision Server and Decision Center will not work correctly without administrative security. With this parameter, you must also provide -adminUserName and -adminPassword.
For more information about WebSphere Application Server, see the WebSphere Application Server documentation.
Step 2: Augmenting the application server profile
After creating your application server profile, augment the profile with the Operational Decision Manager components using the Operational Decision Manager profile templates described in Summary: Configuring on WebSphere Application Server.
You cannot augment the application server profile by using the WebSphere Application Server profile management tool. You must augment the profile by using a command line as explained in this step.
wasadmin
Java
process as follows:- On Windows, replace with
-Xms2048M -Xmx4096M
in yourset PERFJAVAOPTION
command inwsadmin.bat
andlaunchWsadminListener.bat
:set PERFJAVAOPTION=-Xms256m -Xmx256m -Xquickstart
- On Linux:
- Change
PERF_JVM_OPTIONS
inwsadmin.sh
. Based on your platform, change"-Xmx256M"
to"-Xmx4096M"
. -
Change
PERF_JVM_OPTIONS
inlaunchWsadminListener.sh
. Based on your platform, change"-Xmx256M"
to"-Xmx4096M"
. - Increase operating system
"open files limit"
with the commandulimit -n 8192
.
- Change
- For Decision Server
-
Windows:
.\bin\manageprofiles.bat -augment -profileName ODM01 -templatePath .\profileTemplates\odm\decisionserver\default -odmHome C:\IBM\ODMXXX -databaseConfigFile C:\IBM\WAS\AppServer\profileTemplates\odm\decisionserver\default\DB.properties
Linux:
./bin/manageprofiles.sh -augment -profileName ODM01 -templatePath ./profileTemplates/odm/decisionserver/default -odmHome /IBM/ODMXXX -databaseConfigFile /IBM/WAS/AppServer/profileTemplates/odm/decisionserver/default/DB.properties
- For Decision Center
-
Windows:
.\bin\manageprofiles.bat -augment -profileName ODM01 -templatePath .\profileTemplates\odm\decisioncenter\default -odmHome C:\IBM\ODMXXX -databaseConfigFile C:\IBM\WAS\AppServer\profileTemplates\odm\decisioncenter\default\DB.properties
Linux:
./bin/manageprofiles.sh -augment -profileName ODM01 -templatePath ./profileTemplates/odm/decisioncenter/default -odmHome /IBM/ODMXXX -databaseConfigFile /IBM/WAS/AppServer/profileTemplates/odm/decisioncenter/default/DB.properties
- -profileName
- Use the name of the existing application server profile that you created.
- -templatePath
- The location of the Operational Decision Manager profile
template:
- <WAS_InstallDir>\AppServer\profileTemplates\odm\decisionserver\default for Decision Server.
- <WAS_InstallDir>\AppServer\profileTemplates\odm\decisioncenter\default for Decision Center.
- -odmHome
- The location of the Operational Decision Manager installation.
- -databaseConfigFile
- The location of the database configuration file. An example is
provided in
<WAS_InstallDir>\AppServer\profileTemplates\odm\decisionserver\default\derbyDBSampleSetting.properties
. This file must include the following parameters:Parameter Value Example database.type
The type of database manager. Valid values are: Derby_Embedded
Derby_NetwokServer
DB2
MSSQL
Oracle
PostgreSQL
database.type=DB2
database.jdbcDriverPath
The fully qualified location and name of the JDBC driver file.
For cases like DB2® where a license file is also required, separate the two files with a semi-colon (;).
C:/drivers/DB2/db2cc.jar;C:/drivers/DB2/db2cc_license_cu.jar. database.name
The name of the database. Typically, resdb and dcdb. database.hostname
The database server host name or IP address. localhost on your local machine. database.port
The database TCP/IP service port or listener port. This parameter can remain empty for Derby Embedded. 1527 database.user
The user ID to access the database. database.password
The password for the user ID to access the database.
-templatePath
parameter, and the -ignoreStack
parameter. For example: - Windows
-
.\bin\manageprofiles.bat -unaugment -profileName ODM01 -templatePath .\profileTemplates\odm\decisionserver\default -ignoreStack
- Linux
-
./bin/manageprofiles.sh -unaugment -profileName ODM01 -templatePath ./profileTemplates/odm/decisionserver/default -ignoreStack
Results
Action | Manual equivalent |
---|---|
Installs the JDBC provider and the data source. | Setting up a data source and connection pool |
Configures security and creates the default users. | Activating security access |
Deploys the MBean descriptors. | Deploying the Rule Execution Server MBean descriptors |
Deploys the execution unit (XU). | Deploying the XU RAR |
Deploys the Rule Execution Server console. | Deploying the Rule Execution Server management EAR |
Deploys the testing and simulation archive. | Deploying the testing and simulation archive |
Deploys the hosted transparent decision services. | Deploying the hosted transparent decision service EAR |
You can start the server, sign-in to the Rule Execution Server console, and diagnose Decision Server by following the instructions in Completing the configuration of Rule Execution Server
Action | Manual equivalent |
---|---|
Installs the JDBC provider and the data source. | Configuring database connectivity |
Configures security and creates the default users. Typically, you use the default users to complete the configuration and other IT tasks. To give access to other users on the basic registry or configure an LDAP repository, see the manual equivalent section. |
Configuring user access to Decision Center |
Deploys the Decision Center application. | Deploying the Decision Center EAR file |