Task 10: Starting or Restarting the Services

See TIBCO OPE Resource Allocation, if you want to use resource allocation for TIBCO OPE services.

Note: You can choose to provide 'Xms Xmx' or 'MinRAMPercentage MaxRAMPercentage' parameters based on your requirements.
    Procedure
  1. To restart the authorization service, navigate to the $OPE_HOME/roles/authorization-service/stanalone/bin directory and run the ./start.sh script.

  2. To restart the configurator service, navigate to the $OPE_HOME/roles/configurator/stanalone/bin directory and run the ./start.sh script.

  3. To restart the configurator-ui service, navigate to the $OPE_HOME/roles/configurator-ui/stanalone/bin directory and run the ./start.sh script.

  4. To start the other services, navigate to the $OPE_HOME/roles/<service-name>/standalone/config and update the application.properties file for configuratorServiceUrl, value is the IP or DNS name of configurator service.

  5. Navigate to the $OPE_HOME/roles/<service-name>/standalone/bin/ directory and run the ./start.sh script in the following sequence:

    • catalog-service

    • ope

    • offersearchindex-service

    • shoppingcart

    • recommendation-engine-data-store

    • recommendation-engine-data-mapper

    • recommendation-engine-api

    • recommendation-engine-core

Note: You must start the Authorization and configurator service first and then all the other services.

Note: For recommendation-engine-core, you must run the python scripts for the requirements.txt before running the $./start.sh script. See $OPE_HOME/roles/recommendation-engine-core/standalone/README.md file.