Installing Platform Services on UNIX

The UNIX version of the Platform Services software is distributed as a self-extracting bin file and install script.

To install the Oracle Commerce Guided Search Platform Services on UNIX:

  1. In your local environment, locate the Platform Services installation package that you downloaded from the Oracle Software Delivery Cloud. The name of the installation file is as follows:

  2. Determine where you will install Platform Services. Verify that the target directory where you plan to install has enough available disk space and has write permissions (is not read-only). For example, in this procedure we assume that the target directory is /usr/local and that you have write permissions for it. If you do not set these permissions, the install script will not run.

  3. From the /downloads directory, start the installation with the following command: 

    ./OCplatformservices11.2.0-linux64_<buildnumber>.bin

    or 

    ./OCplatformservices11.2.0-solaris_<buildnumber>.bin

  4. Select a locale.

  5. In the Introduction screen, press Enter to continue.

  6. Accept the terms of the license agreement.

  7. In the Choose Install Folder screen, enter /usr/local as the installation location.

  8. In the Choose Install Set screen, enter the number for the program features to be installed. The default is Typical.

    Install SetContents
    TypicalAll features except for Oracle Commerce Reference Implementation
    CompleteAll features
    PS & App Controller AgentApplication Controller Agent
    Reference Implementation Sample Guided Search applications, as well as JSP and .NET user interface applications.

  9. Enter the port on which the EAC service will listen. The default is 8888, but you must specifically enter that number in the prompt.

  10. Enter the shutdown port of the EAC service. The default is 8090, but you must specifically enter that number in the prompt.

  11. Enter the location (an absolute path) of the MDEX Engine root directory (for example, /usr/local/endeca/MDEX/<version> ).

    Note that the installer does not verify the existence of the directory; this allows you to install the Platform Services package before the MDEX Engine package.

  12. In the Pre-Installation Summary screen, review the settings you have selected and press Enter to continue.

  13. In the Ready to Install screen, press Enter to start the installation.

    The Installation Complete message displays at the completion of the installation.

  14. Press Enter to exit the installation.

At the completion of the installation, the installer prompts you to run the installer script that sets the Platform Services environment variables (such as ENDECA_ROOT), as well as some additional ones that are used internally.

Depending on your shell, run the following script:

For Bourne, Bash or Korn: 

source endeca/PlatformServices/workspace/setup/installer_sh.ini

or:

For csh or tcsh: 

source endeca/PlatformServices/workspace/setup/installer_csh.ini

Generally this command should be placed in a script run at the startup of the shell so the variables are set for future use.

To start the HTTP Service, change to the endeca/PlatformServices/<version>/tools/server/bin directory and run the startup.sh script. (You can also run the script from another directory by using the absolute path to the script). For information about how to control this service, see the Endeca Application Controller Guide.

Note

Platform Services must run using 64-bit java, using the -d64 argument in the startup script.

If you did not specify the MDEX Engine root directory (at Step 11), the com.endeca.mdexRoot setting (in the EAC eac.properties configuration file) will have a blank value. The file is located in the $ENDECA_CONF/conf directory. If you later install the MDEX Engine on your system, you must edit the file and add the absolute path of the MDEX Engine root directory in the setting, and then restart the EAC service. For more information on this file, see the Endeca Application Controller Guide.

Copyright © Legal Notices