Content Platform Engine, Version 5.2.1              

Configuring Content Platform Engine instances by using the graphical user interface

You use the graphical user interface version of Configuration Manager to configure and deploy a Content Platform Engine application instance on an application server.

About this task

First, you create a configuration profile that defines:
  • The license choices
  • The JDBC data source settings
  • The login modules for the Content Platform Engine application
  • The directory service provider (LDAP) settings
  • The Content Platform Engine bootstrap settings

You can follow the recommended order to edit and run the individual configuration tasks. Or you can save your edits, switch between tasks, close the tasks, and reopen tasks as needed. You do not need to complete work on one configuration task before starting another. You can edit and run them in any order, with one exception: You must run the Configure Bootstrap and Text Extraction task after running the Choose Licenses task. Also, you must edit and run all of these tasks before you deploy the application.

  1. Starting the Configuration Manager graphical user interface
    You can start the graphical interface version of Configuration Manager to configure a Content Platform Engine application instance on a web application server.
  2. Changing the password save preference
    By default, any passwords that you enter in the graphical user interface in Configuration Manager are not saved to a file. The passwords are stored in memory as long as you have the profile open in Configuration Manager. You can change the password save preference to save the passwords each time that you save your changes to a profile.
  3. Creating a new configuration profile
    Configuration Manager stores your settings for deploying a Content Platform Engine application instance in a configuration profile. The profile defines the application server settings, the JDBC data source settings, the login modules settings, the directory service provider (LDAP) settings, the Content Platform Engine bootstrap settings, and the application deployment settings. You must create a new profile for each Content Platform Engine instance that you are configuring.
  4. Choosing licenses
    You must provide licensing information about your installed products so that IBM® License Metric Tool can make the correct product license association.
  5. Configuring the global configuration database JDBC data source settings
    You must provide property information about the JDBC data sources for the global configuration database (GCD). Content Platform Engine uses the data source information to connect to and update the GCD.
  6. Configuring the initial object store data sources by using the graphical user interface
    Content Platform Engine uses the data source information to connect to and update the object store database. By default, each profile includes a task for creating the data sources for an object store.
  7. Configuring the login modules (WebSphere and JBoss only)
    You must configure the login modules for the Content Platform Engine application. The login modules provide authentication information for the Content Platform Engine application.
  8. Configuring Content Platform Engine application server authentication (LDAP) settings
    You must configure the Content Platform Engine application server's authentication settings. These settings define the (LDAP) repository and search mechanism, which the application server uses to authenticate a user requesting Content Platform Engine service.
  9. Configuring bootstrap and text extraction settings
    The bootstrap settings are for creating the global configuration database (GCD) and for starting Content Platform Engine. The text extraction setting is needed for updating the Content Platform Engine EAR file with the IBM Content Search Services API JAR files and text extraction modules.
Parent topic: Configuring Content Platform Engine instances

Last updated: March 2016
p8pin014.htm

© Copyright IBM Corporation 2013, 2016.