Configure IBM ILog DOC Enterprise 3.8.0.2 for Maximo Scheduler

Configure IBM ILog DOC Enterprise 3.8.0.2 for Maximo Scheduler
Configure IBM ILog DOC Enterprise 3.8.0.2 for
Maximo Scheduler 7.6.2
Index
1. Installation ...................................................................................................... 3
1.1 System Requirements............................................................................... 3
1.2. Configuring DOC Enterprise datasource.................................................. 4
1.2.1. Create the database .......................................................................... 4
1.2.2. Create odme user for MXODME database ........................................ 4
1.2.2.1. DB2 database ............................................................................. 4
1.2.2.2. Oracle database ......................................................................... 8
1.2.2.3. SQL Server database ............................................................... 13
1.2.3. Database initialization ..................................................................... 17
1.2.3.1. DB2 database ........................................................................... 17
1.2.3.2. Oracle database ....................................................................... 19
1.2.3.3. SQL Server database ............................................................... 20
1.2.4. Create an ODME Server ................................................................. 22
1.2.5. JDBC providers configuration .......................................................... 25
1.2.5.1. DB2 database ........................................................................... 25
1.2.5.2. Oracle database ....................................................................... 27
1.2.5.3. SQL Server database ............................................................... 30
1.2.6. Data sources configuration .............................................................. 32
1.3. Configuring ODME Enterprise messaging ............................................. 38
1.3.1. Create the bus ................................................................................. 38
1.3.2. Add ODME Servers to the bus ........................................................ 40
1.3.3. Create a Topic ................................................................................. 43
1.3.4. Create a Topic Connection Factory ................................................. 45
1.3.5. Create a Queue Connection Factory ............................................... 48
1.3.6. Create an Activation specification ................................................... 50
1.4. Deploying the common ODM Enterprise server EAR ............................ 52
1.5. Virtual host configuration ....................................................................... 55
1.6. Verifying the common ODM Enterprise Server EAR .............................. 57
1.7. Data Server installation, deploy and configure the Data Management
EAR .............................................................................................................. 58
1.8. Optimization Server installation, deploy and configure the Job
Management EAR ........................................................................................ 61
1.9. Optimization Server installation, deploy and configure the Job Processor
EAR .............................................................................................................. 64
1.9.1. Oracle database .............................................................................. 64
1.9.2. SQL Server database ...................................................................... 64
1.9.3. Install, deploy and Configure the Job Job Processor EAR .............. 65
1.10. Configuring the Deployment Directory ................................................. 68
2. Start ODME Server ...................................................................................... 70
3. Security ........................................................................................................ 71
3.1. Create Users/ Group roles ..................................................................... 71
3.2. Security Role Mapping ........................................................................... 76
3.3. SSL Configuration .................................................................................. 79
Page 1 of 84
DOC Setup Guide
Sarika Budhiraja
3.3.1. Certificate Signing Request ............................................................. 79
3.3.2. Server and Trust/Signer Certificate ................................................. 79
3.3.3. Maximo/Client Web Servers Trust/Signer Certificate ...................... 80
4. Configuration of DOC Server at IBM Maximo Scheduler .............................. 81
Page 2 of 84
DOC Setup Guide
Sarika Budhiraja
This document is created for configuring the DOC 3.8.0.2 server for Scheduler 7.6.2.1. All the following
steps are after installing database(Oracle/DB2), WebSphere and DOC 3.8.0.2.
1. Installation
1.1 System Requirements
Before you proceed with the instructions provided in the document, make sure your system matches the
system requirements mentioned in this following link.
http://www-969.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html
Search For Decision Optimization Center, Version : 3.8.0.2
The system requirement detail report will be displayed.
Page 3 of 84
DOC Setup Guide
1.2. Configuring DOC Enterprise datasource
1.2.1. Create the database
Create a database MXODME.
1.2.2. Create odme user for MXODME database
Now you can create an user at OS and then grant permissions to the user over the database created:
MXODME.
1.2.2.1. DB2 database
First create the user at OS level.
Then go to the database at DB2 Control Center, right click, connect to the database.
Page 4 of 84
DOC Setup Guide
Then add odme user and grant all. The odme user has to be a schema owner and should have DBA
privileges for all the table created.
Page 5 of 84
DOC Setup Guide
Repeat the process for odmea and odmep users. The odmea is a user for Work Assign odme application.
The odmep is a user for Work Plan odme application.
First create them in MMC Server Manager for OS.
Then add them to the database
Page 6 of 84
DOC Setup Guide
After that you need to execute the following statement:
create schema odme authorization odme;
create schema odmep authorization odmep;
create schema odmea authorization odmea;
Page 7 of 84
DOC Setup Guide
1.2.2.2. Oracle database
Create database MXODME.
Go to Database Configuration Assistant.
Page 8 of 84
DOC Setup Guide
Provide database configuration information.
Click Finish.
Page 9 of 84
DOC Setup Guide
Close the Create Database window after database creation is completed.
Page 10 of 84
DOC Setup Guide
Connect to MXODME database.
Page 11 of 84
DOC Setup Guide
Run the following commands to create users. The ODME user is a schema owner . The ODMEA is the
Work Assign odme application user. The ODMEP is the Work Plan odme application user.
create tablespace odme datafile 'c:\oracle\oradata\MXODME\odme.dbf' size 500M autoextend on;
create user odme identified by maximo default tablespace odme temporary tablespace temp;
grant connect, dba to odme;
create user odmea identified by maximo default tablespace odme temporary tablespace temp;
grant connect, dba to odmea;
create user odmep identified by maximo default tablespace odme temporary tablespace temp;
grant connect, dba to odmep;
Page 12 of 84
DOC Setup Guide
1.2.2.3. SQL Server database
Create database MXODME.
Go to Microsoft SQL Management Studio.
Right Click on Databases and Create Database.
Page 13 of 84
DOC Setup Guide
Database Name : MXODME
Set Initial Size. For example, 500 MB
Run the following commands to create users. The ODME user is a schema owner . The ODMEA is the
Work Assign odme application user. The ODMEP is the Work Plan odme application user.
Connect to MXOME as odme user. Run the following commands. Set 'yourpassword'.
Create Work Plan users:
sp_addlogin odmep, 'yourpassword'
go
create user odmep for login odmep with default_schema = odmep
go
create schema odmep authorization odmep
go
exec sp_addrolemember 'db_owner', odmep
go
Page 14 of 84
DOC Setup Guide
Create Workassign users:
sp_addlogin odmea, 'yourpassword'
go
create user odmea for login odmeb with default_schema = odmea
go
create schema odmea authorization odmea
go
exec sp_addrolemember 'db_owner', odmea
go
Page 15 of 84
DOC Setup Guide
Page 16 of 84
DOC Setup Guide
1.2.3. Database initialization
1.2.3.1. DB2 database
Then connect to MXODME database using user odme
And open a Command window in order to run config DB scripts.
As we are creating the DB for first time, we should select the file:
db2-create-tables.sql
You can open it in, for example, Notepad++ and then copy and paste to the DB2 command editor
Page 17 of 84
DOC Setup Guide
Then you press
and wait
Click Close
You have a result like that:
Page 18 of 84
DOC Setup Guide
1.2.3.2. Oracle database
Connect to MXODME database using odme user.
And open a Command window in order to run config DB scripts.
As we are creating the DB for first time, we should select the file:
oracle-create-tables.sql
You can open it in, for example, Notepad++ and then copy and paste to the Oracle SQL developer.
Page 19 of 84
DOC Setup Guide
1.2.3.3. SQL Server database
Go to Microsoft SQL Server Management Studio to run config DB scripts. Connect to MXODME
database using odme user.
As we are creating the DB for first time, we should select the file:
mssql-create-tables.sql
You can open it in, for example, Notepad++ and then copy and paste to the Microsoft SQL Server
Management Studio.
Connect to MXODME as odme user.
Page 20 of 84
DOC Setup Guide
Page 21 of 84
DOC Setup Guide
1.2.4. Create an ODME Server
Create ODME Server. At WAS console go to Server > Server Types > Websphere Application Servers
Click New
Click Next
Click Next
Page 22 of 84
DOC Setup Guide
Click Next
Finish
Click Next
Click Next.
Page 23 of 84
DOC Setup Guide
Click Finish
Click Save
At this point you can configure JDBC providers and Data sources.
Page 24 of 84
DOC Setup Guide
1.2.5. JDBC providers configuration
1.2.5.1. DB2 database
Locate the required db2jcc.jar. You need it to create the JDBC provider. It can found in Maximo or
WebSphere sub folders.
For example,
C:\Maximo\lib
In our case this file was located at:
Then go to WAS Console > Resources > JDBC > JDBC providers
Set the scope for ODME Server. Click New and follow the wizard, after to click Finish, the result must
be:
Page 25 of 84
DOC Setup Guide
And the detail will be
Page 26 of 84
DOC Setup Guide
1.2.5.2. Oracle database
Locate the required ojdbc6.jar. You need it to create the JDBC provider. It can be found in Maximo or
Oracle sub folders.
For example,
C:\Oracle\Administrator\product\11.2.0\dbhome_1\jdbc\lib
In our case this file was located at:
Then go to WAS Console > Resources > JDBC > JDBC providers
Set the Scope. In this example, we are setting Scope to ODME Server.
Click New and follow the wizard, after to click Finish, the result must be:
Page 27 of 84
DOC Setup Guide
And the detail will be
Page 28 of 84
DOC Setup Guide
Page 29 of 84
DOC Setup Guide
1.2.5.3. SQL Server database
You need it to create the JDBC provider. To use SQL Server as your ODM Scenario Repository, you
must first download the appropriate driver from the Microsoft SQL Server JDBC Driver 4.0 driver from
the following location:
http://www.microsoft.com/en-us/download/details.aspx?id=11774.
You must use the sqljdbc4.jar which requires a Java Runtime Environment (JRE) of version 6.0 or later.
(Using a sqljdbc4.jar with JRE 1.4 or 5.0 will throw an exception.) .
Then go to WAS Console > Resources > JDBC > JDBC providers.
Set the Scope. In this example, we are setting Scope to ODME Server.
Click New and follow the wizard, after to click Finish, the result must be:
And the detail will be
Page 30 of 84
DOC Setup Guide
Page 31 of 84
DOC Setup Guide
1.2.6. Data sources configuration
Go to WAS Console > Resources > JDBC > Data sources
Set up Scope. In this example, we are setting Scope to ODMEServer.
You should click New and fill the wizard, after to click Finish the result should be:
Page 32 of 84
DOC Setup Guide
Where JAAS – J2C authentication data is:
Page 33 of 84
DOC Setup Guide
After the data source is configured, make sure to test the connection is working by using the “Test
Connection” button
You must see a message that indicates that the connection was successful as shown below.
Page 34 of 84
DOC Setup Guide
If you are using DB2, make sure to set the following custom properties as mentioned in the installation
guide. At the page 46 of the official installation guide, it recommends this extra configuration when you
use DB2.
Page 35 of 84
DOC Setup Guide
Click Save
Page 36 of 84
DOC Setup Guide
For Microsoft SQL Server users:
Before installing a JOBS database on an SQL Server database you must enable the
READ_COMMITTED_SNAPSHOT row versioning mode, in order to improve concurrency. This can
be done by executing the following command on your SQL Server database instance:
ALTER DATABASE <MY_JOBS_DB> SET READ_COMMITTED_SNAPSHOT ON;
where <MY_JOBS_DB> corresponds to your JOBS database name.
For example,
ALTER DATABASE MXODME READ_COMMITTED_SNAPSHOT ON;
Page 37 of 84
DOC Setup Guide
1.3. Configuring ODME Enterprise messaging
1.3.1. Create the bus
At WAS console go to Service Integration>Buses and choose the option to create a new bus.
Bus name: OptimizationServerBus
Click Next
Click Finish
Page 38 of 84
DOC Setup Guide
Click Save
Page 39 of 84
DOC Setup Guide
1.3.2. Add ODME Servers to the bus
Now Add the ODMEServer to the created bus.
Click Next
Click Next
Page 40 of 84
DOC Setup Guide
Click Next
Click Next
Click Finish
Page 41 of 84
DOC Setup Guide
Click Save
Page 42 of 84
DOC Setup Guide
1.3.3. Create a Topic
At WAS console go to Resources > Topics
Topic name: OptimizationServerTopic
JNDI name: jms/optimserver/Topic
Scope (in this example): Node=ctgCell01, Server=ODMEServer
Click New
Click OK
Page 43 of 84
DOC Setup Guide
Click Save
Page 44 of 84
DOC Setup Guide
1.3.4. Create a Topic Connection Factory
At WAS console go to Resources > Topic connection factories
Topic connection factory name: OptimizationServerConnectionFactory
JNDI name: jms/optimserver/TopicConnectionFactory
Scope (in this example): Node=ctgCell01, Server=ODMEServer
Click New
Page 45 of 84
DOC Setup Guide
Click Next
Page 46 of 84
DOC Setup Guide
Click OK
Page 47 of 84
DOC Setup Guide
1.3.5. Create a Queue Connection Factory
At WAS console go to Resources > Queue Connection Factories
Queue name: OptimizationServerQueueConnectionFactory
JNDI name: jms/optimserver/QueueConnectionFactory
Scope (in this example): Node=ctgCell01, Server=ODMEServer
Click New
Click OK
Page 48 of 84
DOC Setup Guide
Click Save
Page 49 of 84
DOC Setup Guide
1.3.6. Create an Activation specification
At WAS console go to Resources > Activation specifications
Activation specification name: OptimizationServerTopicSpec
JNDI name: jms/optimserver/TopicSpec
Scope (in this example): Node=ctgCell01, Server=ODMEServer
Click New
Click OK
Page 50 of 84
DOC Setup Guide
Click Save
Page 51 of 84
DOC Setup Guide
1.4. Deploying the common ODM Enterprise server EAR
At WAS console go to Applications > Application types > Websphere enterprise applications
Select odme-application-mgmt application.Click Install.
Click Next
Click Next
Page 52 of 84
DOC Setup Guide
Click Next
Fill as indicated in the image and click Next
Page 53 of 84
DOC Setup Guide
Click Finish and wait
Click Save
Page 54 of 84
DOC Setup Guide
Now you should configure Virtual hosts.
1.5. Virtual host configuration
In the image you can see that we have created a new virtual host called odme_hosts. Make sure all the
default ports of the server are included in the odme_hosts.
Then
Page 55 of 84
DOC Setup Guide
Then
Then
Page 56 of 84
DOC Setup Guide
1.6. Verifying the common ODM Enterprise Server EAR
At WAS console go to Servers > Server types > web servers
Select webserver1 and press Generate Plug-in button, then select webserver1 and press Propagate
Plug-in button.
Page 57 of 84
DOC Setup Guide
1.7. Data Server installation, deploy and configure the Data
Management EAR
Select odme-application-mgmt application. Click Install.
Click Next
Click Next
Page 58 of 84
DOC Setup Guide
Click Next
Fill as in the image and then click Next
Page 59 of 84
DOC Setup Guide
Click Finish and wait
Click Save
Page 60 of 84
DOC Setup Guide
1.8. Optimization Server installation, deploy and configure the Job
Management EAR
Select odme-data-mgmt application. Click Install.
Click Next
Click Next
Page 61 of 84
DOC Setup Guide
Click Next
Fill as it is in the image and then click Next
Page 62 of 84
DOC Setup Guide
Click Finish and wait
Click Save
Page 63 of 84
DOC Setup Guide
1.9. Optimization Server installation, deploy and configure the Job
Processor EAR
1.9.1. Oracle database
This step is only if you are using Oracle database.
Locate ojdbc6.jar from the oracle folder. For example,
C:\Oracle\Administrator\product\11.2.0\dbhome_1\jdbc\lib
Copy ojdbc6.jar copy to your configure-scripts folder. For example,
$<ILOG_Folder>\ODME38\server\configure-scripts
Open the commad window.
Check JAVA_HOME is set. If not set, set your JAVA_HOME.
For example: set JAVA_HOME='C:\Program Files\Java\jdk1.7.0_51'
Install Apache Ant if Ant is not already installed. Make sure its bin folder is in your PATH.
Run the following command:
ant.bat -f "build.xml" oracle.configure
OR
Run repackageEARWithOracle.bat from ilog configure-scripts folder.
1.9.2. SQL Server database
This step is only if you are using SQL Server database.
Locate sqljdbc4.jar that you downloaded in section 1.2.5.3.
Copy sqljdbc4.jar copy to your configure-scripts folder.
For example, $<ILOG_Folder>\ODME38\server\configure-scripts
Open the commad window.
Check JAVA_HOME is set. If not set, set your JAVA_HOME.
For example: set JAVA_HOME='C:\Program Files\Java\jdk1.7.0_51'
Install Apache Ant if Ant is not already installed. Make sure its bin folder is in your PATH.
Run the following command:
ant.bat -f "build.xml" mssql.configure
OR
Run repackageEARWithMSSQL.bat from ilog configure-scripts folder.
Page 64 of 84
DOC Setup Guide
1.9.3. Install, deploy and Configure the Job Job Processor EAR
Go to Enterprise Applications in WAS Console.
Select odme-optimserver-processor application. Click Install.
Click Next
Page 65 of 84
DOC Setup Guide
Click Next
Click Next
Fill it as in the image and then click Next
Page 66 of 84
DOC Setup Guide
Click Finish and wait
Click Save
Page 67 of 84
DOC Setup Guide
1.10. Configuring the Deployment Directory
Deployment Directory (in this example): C:\ILOG\ODME_Deployement_Directory
At WAS console go to Enterprise Applications > odme-optimserver-processor > Manage modules >
optimserver-processor-rar.rar > Resource adapter > Custom properties and change the value of the
property DeploymentDirectoryLocation.
Page 68 of 84
DOC Setup Guide
Repeat with Enterprise Applications > odme-data-mgmnt > Manage modules > odme-data-mgmntrar.rar > Resource adapter > Custom properties and change the value of the property
DeploymentDirectoryLocation
Page 69 of 84
DOC Setup Guide
2. Start ODME Server
At WAS console go to Servers > Server Types > WebSphere applications servers, select
ODMEServer and click Start.
Go to Applications > Application Types > Websphere enterprise applications and check that all odme
applications are up and running.
Page 70 of 84
DOC Setup Guide
3. Security
3.1. Create Users/ Group roles
The IBM Decision Optimization Center 3.8 requires security to be configured to protect the DOC
applications. The security can be configured using WAS security and can take advantage of any
Directory Servers that are setup that already contain user accounts. All that is needed is mapping of the
security role to the users or groups in the Directory Server for each DOC application that is deployed. To
do this, first setup WAS to use Directory Server security and then go to each deployed application and
select security role mapping option and pick the users or groups and assign them to the roles already
defined for the application.
It is also possible to setup the security using a simple file based database mechanism provided by WAS.
This can be used as a quick configuration for test environments, where there may not already be a
Directory Server available. The following explains how this can be done.
Set up Security. For example, go to Global security. Add user, e.g wasadmin
Page 71 of 84
DOC Setup Guide
Click on Security Configuration Wizard.
Click Next.
Click Next.
Page 72 of 84
DOC Setup Guide
Click Next.
Click Finish.
Page 73 of 84
DOC Setup Guide
Set up user/groups account.
Set up custom properties.
Page 74 of 84
DOC Setup Guide
Sample Scripts
Sample Script #1
#---------------------------------------------------------------# Licensed Materials - Property of IBM
# 5724-Y04
# Copyright IBM Corporation 2005,2013. All Rights Reserved.
#
# Note to U.S. Government Users Restricted Rights:
# Use, duplication or disclosure restricted by GSA ADP Schedule
# Contract with IBM Corp.
#---------------------------------------------------------------# Default group definitions for ODM Enterprise access control
# The groups listed in this file are used to populate the list of
# groups and their user assignments created by default on both
# WAS and WAS-CE.
#
# This default list can be overridden by creating a copy of this file
# with extension `hostname`.properties
#
# odmeusers group will be mapped to role odmeuser
# odmeadmins group will be mapped to roles odmeuser and odmeadmin
odmeadmins=__odmesystem,tim,steve,odme38admin
odmeusers=anne,keith,__odmesystem,tim,steve,odme38admin
Sample Script # 2
# (C) COPYRIGHT International Business Machines Corp. 1997, 2005
# All Rights Reserved * Licensed Materials - Property of IBM
#
# Format:
# name:passwd:uid:gids:display name
# where name = userId/userName of the user
#
passwd = password of the user
#
uid = uniqueId of the user
#
gid = groupIds of the groups that the user belongs to
#
display name = a (optional) display name for the user.
wasadmin:maximo:wasadmin:wasadmins:WAS Admin User
__odmesystem:maximo:__odmesystem:odmeadmins,odmeusers:ODME Admin
tim:maximo:tim:odmeadmins,odmeusers:Tim
steve:maximo:steve:odmeadmins,odmeusers:Steve
anne:maximo:anne:odmeusers:Anne
keith:maximo:keith:odmeusers:Keith
Page 75 of 84
DOC Setup Guide
3.2. Security Role Mapping
Perform "Security role to user/group mapping" for the following applications:
odme-application-mgmt
odme-data-mgmt
odme-optimserver-mgmt
Select roles. Then, click on "Map Users".
Page 76 of 84
DOC Setup Guide
Page 77 of 84
DOC Setup Guide
Then, Click on "Search" button to search users.
Select users and click OK .
Page 78 of 84
DOC Setup Guide
3.3. SSL Configuration
The IBM Decision Optimization Center (DOC) version 3.8 requires all the HTTP communication
between a client (Maximo Server) and the DOC Server to be secured using SSL. This requires SSL
configuration to be to enabled for the DOC Server and also requires valid certificates to provide identity
to the server. Apart from the server certificates, the certificate issuing authority (CA) certificates also
need to be imported into the trust stores of the client programs (MAXIMO Servers or any Web Server).
Please follow the WAS documentation on setting up the SSL and certificates. Getting a certificate
involves creating a Certificate Signing Request (CSR) with the host name of the DOC Server and then
submitting this request to the Certificate Authority and then obtaining a signed certificate from the
Certificate Authority. This signed certificate needs to be imported into the DOC Server key certificate
store. As part of this, the Certificate Authority also sends the root CA Certificates that are used to sign the
certificate that was issues. These root Certificates need to be imported into the DOC Server trust store.
These root Certificates also need to be imported into the client programs (Maximo Servers or Web
Server) into the appropriate Trust stores. Without the proper installation of these certificates, the
communication between the client programs (MAXIMO Servers or Web Servers) and the DOC Server
would not be possible using SSL.
At WAS console go to Security > Configure SSL certificate and key management. The odme server and
server certificate has to be set up to work with SSL.
3.3.1. Certificate Signing Request
The server certificate request (CSR) can be created from WAS Console.
Go to Security> Configure SSL certificate and key management>Key stores and
certificates>Cell/NodeDefaultKeyStore>Personal certificate requests. Click "New" button. Add
server information, path and type. Click ok. The certificate request will get created in the path mentioned
in the request.
3.3.2. Server and Trust/Signer Certificate
The server certificate needs to imported at Cell/Node key stores. At WAS console, go to
Security> Configure SSL certificate and key management>Key stores and
certificates>CellDefaultKeyStore>Personal certificate. Click on "Receive from a certificate authority"
to receive the certificate.
or
Security> Configure SSL certificate and key management>Key stores and
certificates>NodeDefaultKeyStore>Personal certificate. Click on "Receive from a certificate
authority" to receive the certificate.
Page 79 of 84
DOC Setup Guide
The trusted/signer certificate(s) needs to be added to Node/Cell Default Trust Store. At WAS console,
go to
Security> Configure SSL certificate and key management>Key stores and
certificates>CellDefaultTrustStore>Signer certificate> Click on "Add" button to add the certificate.
or
Security> Configure SSL certificate and key management>Key stores and
certificates>NodeDefaultTrustStore>Signer certificate > Click on "Add" button to add the certificate.
3.3.3. Maximo/Client Web Servers Trust/Signer Certificate
The client certificate needs to added at Cell/Node trust stores.
The trusted/signer certificate(s) needs to be added to Node/Cell Default Trust Store. At WAS console, go
to
Security> Configure SSL certificate and key management>Key stores and
certificates>CellDefaultTrustStore>Signer certificate. Click on "Add" button to add the certificate.
or
Security> Configure SSL certificate and key management>Key stores and
certificates>NodeDefaultTrustStore>Signer certificate. Click on "Add" button to add the certificate .
Page 80 of 84
DOC Setup Guide
4. Configuration of DOC Server at IBM Maximo
Scheduler
Final step is to setup Maximo Scheduler to execute optimizations over ODME.
Go to Maximo application.
1. Set Admin username and Password
You need to go to System Configuration > Platform Configuration > System Properties
Set mxe.skd.optimization.adminuser (Admin username for DOC). For example, __odmesystem
Set mxe.skd.optimization.adminpassword (Admin password for DOC)
2. Go to Planning and Scheduler
Page 81 of 84
DOC Setup Guide
Then you need to Select Action Menu and choose Configure Optimization Server
In the screen that appears you need to fill both options: WORKPLAN and WORKASSIGN.
Note that each one use a different User Name for database configuration.
Page 82 of 84
DOC Setup Guide
Then select both and click Deploy
Page 83 of 84
DOC Setup Guide
After to do that you should see the following at DOC Console
Now the next step is to create a schedule, then to create a Scenario to optimize and run optimization.
Then you should see something like this at DOC Console.
Page 84 of 84
DOC Setup Guide
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising