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 Engine is installed.
If needed, you can create multiple profiles, each of which supports
a unique Content 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 Engine configuration
profile:
- Set the application server properties. Content 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.
- Configure the Java™ Database
Connectivity (JDBC) data sources. The JDBC data source information
is used by Content Engine to
connect to Global Configuration Data (GCD) and object store databases. The application server
uses the JDBC data source information to connect Content 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 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 source task 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 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 Engine connects
to the directory service provider to authenticate users. Because the
application server uses the directory service information to connect
the Content Engine to
the directory service provider, you cannot skip this task even if
you have already configured your application server prior to installing Content 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 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 Engine bootstrap settings. The bootstrap information
is needed for creating the Global Configuration Data and
for starting Content 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.
See Editing the configure bootstrap properties settings for the procedure to set the bootstrap
properties after you have created a profile.
- Deploy the Content Engine application. This action deploys the Content 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 Engine instance
or update the Process Engine Client
files on the Content Engine,
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 Engine application, you use Enterprise Manager to
customize Content 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 Engine from 4.
An upgrade profile includes the Upgrade Bootstrap task and the Deploy
Application task. By default, the upgrade bootstrap 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.