You
can configure a deployment manager profile for Process Server using
the Profile Management Tool.
About this task
The
language of the Profile Management Tool is determined by the default
language on the system. If the default language is not one of the
supported languages, English is used. You can override the default
language by starting the Profile Management Tool from the command
line and using the
java user.language setting to
replace the default language. Enter the following command:
install_root/java/bin/java -Duser.language=locale install_root
For
example, to start the Profile Management Tool in the German language,
enter the following command:
install_root/java/bin/java -Duser.language=de install_root/bin/ProfileManagement/startup.jar
After you start the Profile Management Tool, you
must decide whether to choose
Typical or
Advanced profile
creation. Use the advanced option to:
- Specify a database design file to be used for the database configuration.
- Assign customized values to ports, to the location of the profile,
and to the names of the profile, node, host, and cell (when applicable).
- Create a system service to run the server, if your operating system
and the privileges of your user account permit the creation of services.
- Choose to configure IBM Forms Server to work with
Human Task Management widgets in Business Space.
- Configure Business Process Rules Manager.
- Use one of the following methods to
start the Profile Management Tool.
- Start the tool from the First steps console.
- Click Linux_operating_system_menus_to_access_programs >
IBM > your_product > Profile Management Tool.
- Run the command install_root/bin/ProfileManagement/pmt.sh.
- On the Welcome page,
click Launch Profile Management Tool or select
the Profile Management Tool tab.
- On the Profiles tab,
click Create.
The Environment
Selection page opens in a separate window.
- On the Environment Selection page,
locate the IBM® Business Process Manager Advanced configuration
and expand the section. Select the profile to create and click Next.
- On the Profile Creation
Options page, choose to perform a Typical or
an Advanced profile creation, and click Next. If you selected Typical profile creation,
skip to the Administrative
Security step.
- Advanced: On the Optional Application
Deployment page, select whether to deploy the administrative
console for managing the server (recommended). Click Next.
- Advanced: On the Profile Name
and Location page, perform the following steps:
- In the Profile name field, specify
a unique name or accept the default value. Each profile
that you create must have a name. When you have more than one profile,
you can tell them apart at their highest level by this name.
- In the Profile directory field,
enter the directory for the profile or use the Browse button
to go to the profile directory. The directory you specify
will contain the files that define the runtime environment, such as
commands, configuration files, and log files. The default directory
is install_root/profiles/profile_name.
- Optional: Select Make this profile
the default to make the profile you are creating the default
profile. This check box is shown only if you have an existing
profile on your system.
When a profile is the default profile,
commands work automatically with it. The first profile that you create
on a workstation is the default profile. The default profile is the
default target for commands that are issued from the bin directory
in the product installation root. When only one profile exists on
a workstation, every command operates on that profile. If more than
one profile exists, certain commands require that you specify the
profile to which the command applies.
- From the Server runtime performance tuning
setting list, select a performance tuning level appropriate
for the profile you are creating. This parameter is a WebSphere® Application
Server parameter.
- Click Next. If you
click Back and change the name of the profile,
you might have to manually change the name on this page when it is
displayed again.
- Advanced: On the Node, Host
and Cell Names page, perform the following actions for
the profile you are creating:
- In the Node name field, enter a name for
the node or accept the default value. Try to keep the node name as
short as possible, but ensure that node names are unique within your
deployment environment.
- In the Server name field, enter a name
for the server or accept the default value.
- In the Host name field, enter a name for
the host or accept the default value.
- In the Cell name field, enter a name for
the cell or accept the default value.
Click Next.
- Required: On the Administrative
Security page, enter values for the User name, Password,
and Confirm password. The password specified
during install for administrator will be used for all internal users
including tw_admin and tw_user. Because
all IBM Business Process Manager profiles
must have administrative security enabled, Next is
enabled only after you enter the values.
Click Next.
If you selected Typical profile creation, skip
to the Database Configuration
- Part 1 step.
- Advanced: On the Security Certificate
(Part 1) page, specify whether to create new certificates
or import existing certificates.
- To create a new default personal certificate and a new root
signing certificate, select Create a new default personal
certificate and Create a new root signing certificate,
and click Next.
- To import existing certificates, select Import
an existing default personal certificate and Import
an existing root signing personal certificate and provide
the following information:
- In the Path field, enter the directory
path to the existing certificate.
- In the Password field, enter the password
for the certificate
- In the Keystore type field, select the
keystore type for the certificate you are importing.
- In the Keystore alias field, select the
keystore alias for the certificate you are importing.
- Click Next to display the Security
Certificate (Part 2) page
When you import a personal certificate as the default personal
certificate, import the root certificate that signed the personal
certificate. Otherwise, the Profile Management Tool adds the signer
of the personal certificate to the trust.p12 file.
- Advanced: On the Security Certificate
(Part 2) page, verify that the certificate information
is correct, and click Next to display the Port
Values Assignment page.
If you create the
certificates, you can use the default values or modify them to create
new certificates. The default personal certificate is valid for one
year by default and is signed by the root signing certificate. The
root signing certificate is a self-signed certificate that is valid
for 15 years by default. The default keystore password for the root
signing certificate is WebAS. Change the password.
The password cannot contain any double-byte character set (DBCS) characters
because certain keystore types, including PKCS12, do not support these
characters. The keystore types that are supported depend on the providers
in the java.security file.
When you create
either or both certificates, or import either or both certificates,
the keystore files that are created are:
- key.p12: Contains the default personal certificate.
- trust.p12: Contains the signer certificate
from the default root certificate.
- root-key.p12: Contains the root signing certificate.
- default-signers.p12: Contains signer certificates
that are added to any new keystore file that you create after the
server is installed and running. By default, the default root certificate
signer and a DataPower signer
certificate are in this keystore file.
- deleted.p12: Holds certificates deleted with
the deleteKeyStore task so that they can be recovered if needed.
- ltpa.jceks: Contains server default Lightweight
Third-Party Authentication (LTPA) keys that the servers in your environment
use to communicate with each other.
These files all have the same password when you create or import
the certificates, which is either the default password, or a password
that you specify. An imported certificate is added to the
key.p12 file
or the
root-key.p12 file. If you import any certificates
and the certificates do not contain the information that you want,
click
Back to import another certificate.
- Advanced: On the Port Values
Assignment page, verify that the ports specified for the
profile are unique and click Next. The
Profile Management Tool detects ports currently used by other WebSphere products and displays
recommended port values that do not conflict with existing ones. If
you have applications other than WebSphere ones
that use specified ports, verify that the ports do not conflict. If
you chose not to deploy the administrative console on the Optional
Application Deployment page, the administrative console
ports are not available on the Port Values Assignment page.
Ports
are recognized as being in use if the following conditions are satisfied:
- The ports are assigned to a profile created under an installation
performed by the current user.
- The ports are currently in use.
Although the tool validates ports when you access the Port Values
Assignment page, port conflicts can still occur resulting from selections
you make on subsequent Profile Management Tool pages. Ports are not
assigned until profile creation completes.
If you suspect a
port conflict, you can investigate it after the profile is created.
Determine the ports used during profile creation by examining the
following file:
profile_root/properties/portdef.prop
Included
in this file are the keys and values used in setting the ports. If
you discover port conflicts, you can reassign ports manually. To reassign
ports, see "Updating ports in existing profiles" in the
WebSphere Application
Server information
center. Run the
updatePorts.ant file through the
ws_ant script
detailed in this topic.
- Advanced: If you do not have root
privileges, skip to the next step. If you have root privileges, on
the Service Definition page, indicate whether
to use a Linux service to run IBM Business Process Manager. By default, IBM Business Process Manager is
not selected to run as a Linux service.
If
the profile is configured as a Linux service, IBM Business Process Manager attempts
to start Linux services for
processes that are started by the startServer or startManager commands.
For example, if you configure a server as a Linux service and issue the startServer command,
the wasservice command starts the defined services.
You
must specify a user name under which the service runs.
To delete
a Linux service, the user must
be the root user or have the required privileges for deleting the
service. Otherwise, a removal script is created that the root user
can run to delete the service on behalf of the user.
- Advanced: Configure
the Common database using a design file.
- Select Use a database design file.
- Click Browse.
- Specify the fully qualified path name for the design
file.
- To run the database scripts automatically (as part of
the profile creation process), select Run database scripts
to create database tables. Otherwise, you
or the database administrator must run the scripts manually after
profile creation completes.
Important: If you select Run
database scripts to create database tables, ensure that Use
an existing local or remote database is not selected.
If both options are selected, errors occur.
- Click Next. If you
choose to specify a design file, the database configuration panels
in the Profile Management Tool are skipped. Instead, the design file
location is passed to the command line to complete the database configuration.
Skip to the Business Space
Configuration step
- On the Database Configuration
- Part 1 page, specify the information for the Common database.
- From the Select a database product list,
select Microsoft SQL Server.
- Optional: If you want to change the default
values, enter new names for the required databases. The
database names must be unique.
- To run the database scripts automatically as part of
the profile creation process, select Run database scripts
to initialize the databases. Otherwise, you or the database
administrator must run the scripts manually after profile creation
completes.
- Click Next.
- On the Database Configuration
- Part 2 page, complete the configuration for the Common
database. Specify the following fields.
Table 1. Required
database configuration fields for Microsoft SQL
Server - Part 2 | Field |
Action needed |
|---|
Select
the Apply Windows Authentication option to
indicate that you will connect to your databases using your Windows authentication information.
If you select this option, the Process Server database, Performance
Data Warehouse database, and Common database fields are made inactive.
|
| Common database user name |
Enter the user name to authenticate with the
database. |
| Common database password |
Enter a password to authenticate with the database. |
| Confirm password |
Confirm the password. |
| Location (directory) of JDBC driver
classpath files |
The JDBC 2.0 driver classpath files (sqljdbc4.jar)
are packaged with the product and are located in the following directory: ${WAS_INSTALL_ROOT}\jdbcdrivers\SQLServer |
| Database server host name (for example
IP address) |
Accept the default value of localhost or
enter the correct database server host name. |
| Server port |
Accept the default value of 1433 or
enter the correct server port number. |
- Advanced: On the Business
Space Configuration page, if you want to configure IBM
Forms Server to work with Human Task Management widgets in Business
Space, select Configure IBM Forms Server and
enter the HTTP location of the IBM Forms Server translator and IBM
Forms Server installation root. Then click Next.
- Advanced: Select whether to configure
a Business Process Rules Manager for the installation and click Next. Business Process Rules Manager is a web application
that customizes the business rules templates for your business application
needs.
- On the Profile Summary page,
review the information. Click Create to create
the profile or Back to change the characteristics
of the profile.
- On the Profile Complete page,
review the information. To proceed to the First Steps Console, make
sure that Launch First Steps Console is selected
and click Finish.