The information for a profile is collected in XML files
in the form of properties and values that describe the associated
configuration and deployment tasks. You must provide values for the
profile properties that are specific to each configuration at your
site, such as the application server name.
The XML files are stored in a directory that is unique to a given
profile. Because the profile name is used for both the directory name
and the configuration file name, you must provide a profile name that
is a valid directory name for your operating system. By default, the
profiles are stored in the ce_install_path/tools/configure/profiles directory,
where ce_install_path is the location where Content Platform Engine is installed.
If needed, you can create multiple profiles, each of which supports
a unique Content Platform Engine instance.
These instances can be located on the same server or on different
servers, depending on your deployment preferences, the managed or
non-managed nature of your application servers, and your clustering
or high-availability requirements.
Use Configuration Manager to
perform the following tasks that are associated with a Content Platform Engine configuration profile:
- Set the application server properties. Content Platform Engine will be deployed as
an application on the application server. You must specify the application
server type, the software version number, the server name, the administrative
user name and password, and other settings. The application server
type determines some of the properties and their default values. All
profiles include the application server properties. By default, the
application server properties are stored in the ce_install_path/tools/configure/profiles/myprofile/applicationserver.xml file,
where myprofile is the name of your profile.
You
provide the application server properties when you create a profile
by using the Create New Installation Profile wizard, and you can edit
the application server properties at any time as needed. See Creating a profile for a new installation or Editing the application server properties for
detailed procedures.
- Choose
Licenses. The license choices are written into the Content Platform Engine EAR file when you run
the Bootstrap and Text Extraction task. The Listener component of IBM® System Dashboard for Enterprise
Content Management is configured with
the licensing information so that IBM License Metric Tool can make the correct
product and license association.
See Editing the Choose Licenses tasks for the procedure
to choose the licenses after you have created a profile.
- Configure the Java™ Database
Connectivity (JDBC) data sources. The JDBC data source information
is used by Content Platform Engine to
connect to global configuration database (GCD)
and object store databases. The application server uses the JDBC data
source information to connect Content Platform Engine to the database. You
must specify the JDBC provider type, the database name, the database
user name and password, and other settings. The JDBC provider type
determines some of the properties and their default values. By default,
the JDBC properties are stored in the ce_install_path/tools/configure/profiles/myprofile/configurejdbcgcd.xml file
or the ce_install_path/tools/configure/profiles/myprofile/configurejdbcos.xml file,
where myprofile is the name of your profile.
See Editing the Configure JDBC Data Sources tasks for the procedure to set the JDBC data
source properties after you have created a profile.
- Configure the application login modules. The login modules
provide authentication information for the Content Platform Engine application. Run this
task to create the login modules on the application server.
See Editing the Configure LDAP task for the procedure to create the login
modules after you have created a profile.
- Configure the directory service (LDAP) provider. Content Platform Engine connects to the directory
service provider to authenticate users. Because the application server
uses the directory service information to connect the Content Platform Engine to the directory service
provider, you cannot skip this task even if you have already configured
your application server prior to installing Content Platform Engine. You need to specify
the directory service provider type, the user and group naming conventions
for your provider, the directory service user name for the Content Platform Engine to use for authentication,
and other settings. The LDAP provider type that you select determines
some of the properties and their default values. By default, the LDAP
properties are stored in the ce_install_path/tools/configure/profiles/myprofile/configureldap.xml file,
where myprofile is the name of your profile.
See Editing the Configure LDAP task for the procedure to set the LDAP properties
after you have created a profile.
- Configure
the Content Platform Engine bootstrap
and text extraction settings. The bootstrap information is needed
for creating the global configuration database and
for starting Content Platform Engine.
By default, the bootstrap properties are stored in the ce_install_path/tools/configure/profiles/myprofile/configurebootstrap.xml file,
where myprofile is the name of your profile. The
text extraction settings are for formatting text files so that they
can be indexed.
See Editing the Configure Bootstrap and Text Extraction task for the procedure
to set the bootstrap properties after you have created a profile.
- Deploy the Content Platform Engine application.
This action deploys the Content Platform Engine EAR
file with the JDBC, LDAP, and bootstrap settings on the application
server. Any time that you update the properties for an existing deployed Content Platform Engine instance, you must
redeploy for the changes to take effect. By default, the deployment
properties are stored in the ce_install_path/tools/configure/profiles/myprofile/deployapplication.xml file,
where myprofile is the name of your profile.
Tip: After you deploy the Content Platform Engine application, you use Administration Console for Content Platform Engine to customize Content Platform Engine for your site's requirements.
See Editing the Deploy Application task for the procedure to edit the deployment
properties after you have created a profile.
- Check the status of a particular configuration task. Status messages
are displayed when you run a task. You can also explicitly display
the task status any time after you run the task.
See Checking the task status.
- Configure a profile for upgrading an existing Content Platform Engine. An upgrade profile
includes the Configure Login Modules task, the Configure Bootstrap
and Text Extraction task and the Deploy Application task. For JBoss Application Server,
the profile also includes the Configure LDAP task. By default,
the bootstrap and text extraction properties are stored in the ce_install_path/tools/configure/profiles/myprofile/upgradebootstrap.xml
file, and the deployment properties are stored in the ce_install_path/tools/configure/profiles/myprofile/deployapplication.xml file,
where myprofile is the name of your profile.
See Creating a profile for a new installation for a detailed procedure.