There is no configuration that needs to be performed by the customer within the Constraint Optimizer. The Constraint Optimizer is a black box with respect to this integration. However, there are a couple of steps that must be performed, based on whether EAM is in the cloud or is on-prem. See the following for details:
EAM is on-prem:
-
Populate COPTMURL and COPTMKEY install parameters within EAM. This step can be performed by the EAM administrator once this information is provided by the cloud-ops team.
-
EAM tenant must be provisioned in the CO by the cloud-ops team. The step takes place entirely within the CO product.
EAM is cloud:
-
EAM application server configuration file updated for this integration by cloud-ops team.
-
EAM tenant must be provisioned in the CO by the cloud-ops team. The step takes place entirely within the CO product.
-
OPTMSCHL installation parameter, used prior to v12.1.1. for EAM cloud installs, is no longer used and has been removed from the product. EAM cloud customers upgrading to v12.1.1 should NOT need to make any changes to their CO-EAM integration at that time for the integration to continue to work.
-
OTIMEOUT installation parameter is used in both configurations.
-
If any of these steps have not been performed or the Constraint Optimizer server is down when the EAM job attempts to process records into the Constraint Optimizer, an error will be displayed on the relevant Optimized Scheduler Setup record explaining that EAM was unable to connect to the Constraint Optimizer.
Once these steps have been performed, the customer is ready to begin the EAM product configuration steps provided in the next section.