Use this procedure to create a deployment manager profile using
the Profile Wizard graphical user interface (GUI).
Before you begin
Before
using this procedure, ensure that:
- You have an existing installation of WebSphere Process Server
with an underlying installation of WebSphere Application Server Network Deployment.
If you do not, see Installing the product for
installation procedures.
- You want to create a deployment
manager profile and that you want to do so interactively. If you do not, see Creating and augmenting profiles by using the Profile Wizard for descriptions
of other profile creation or augmentation procedures.
- If you plan to locate the repository for WebSphere Process
Server on a remote server, that you create it before beginning this procedure.
The Profile Wizard will let you create a repository on the local server or
use an existing one on a remote server.
- You have enough disk and temporary space to create the new profile. See Required disk space for the minimum
disk space required.
- If you have enabled global security on your installation of WebSphere
Process Server, you disable it before creating the profile. For information
on enabling and disabling global security, see the WebSphere Application Server
Network Deployment, version 6.0 information center at http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp.
- If you plan to use DB2 Universal Database for your repository, you perform
the following steps before creating the profile:
- If you are configuring a DB2 database on a DB2 client with the server
on a remote system, make sure the client system is configured to communicate
with the server and that the DB2 node is cataloged. For more information,
refer to the DB2 Universal Database documentation.
On Linux and UNIX platforms: If you are
configuring a DB2 database on a Linux or UNIX system, source the database
environment by doing the following: - Modify /etc/group and make sure root is in the same group as
the db2instance.
- Source the database environment by running the db2instance/sqllib/db2profile script
(replace db2instance with the name of your database instance).
Why and when to perform this task
The Complete installation procedure for WebSphere Process Server
creates one stand-alone profile named default with a server named server1.
However, to take advantage of the product's networking capabilities, you can
use the Profile Wizard to create additional profiles.
To create a new
deployment manager profile, use the following procedure.
Steps for this task
- Log on as the root user on a Linux or UNIX system, or as a member
of the Administrator group on a Windows system.
- Start the WebSphere Process Server Profile Wizard to create a new
runtime environment.
See Starting the Profile Wizard for descriptions of the many ways to start
the Profile Wizard on various platforms.
The wizard
loads the Java 2 SDK and then displays its Welcome panel.
- In the Welcome panel,
select Next. One of the following panels is displayed, depending
on whether a WebSphere Application Server Network Deployment profile exists:
- If a WebSphere Application Server Network Deployment profile
exists, the Existing profile detection panel is displayed. This procedure
assumes that you want to create a new profile, rather than augment an existing
one into a WebSphere Process Server profile. To create a new profile, select
the Create a new WebSphere Process Server profile radio button and
select Next. The Profile type selection panel is displayed. If you
want to augment an existing profile instead, rather than continuing to follow
this procedure, see the procedure described in Augmenting an existing WebSphere Application Server Network Deployment deployment manager profile into a WebSphere Process Server deployment manager profile, and begin at the step in that
procedure that describes the Existing profile detection panel.
- If no profile exists, the Profile type selection panel is displayed.
- In the Profile type selection
panel, select the Deployment manager profile radio button, then select Next.
- In the Profile name panel, specify
a unique name for the profile or accept the default name. If any other profiles
exist, you can make this profile the default profile by selecting the Make
this profile the default check box. Then select Next.
Each
profile that you create must have a name. When you have more than one profile,
you can distinguish them at their highest level by this name. See Naming considerations for profiles, nodes, hosts, and cells for information on issues you must consider
when naming the profile, such as restrictions on the length of the directory
name.
- In the Profile directory panel,
either accept the default directory location for the profile, or select Browse to
specify another location, then select Next.
This
directory will contain the files that define the runtime environment, such
as commands, configuration files, and log files. By default, this directory
location is:
On Linux and UNIX platforms: install_root/profiles/profile_name
On Windows platforms: install_root\profiles\profile_name
where
profile_name is the name that was specified in step
5. This directory location can be changed to any valid directory
location on the system. If the directory already exists, it must be empty
or an error will be displayed.
If you select Back and change
the name of the profile, you might have to manually change the name on this
panel when it is displayed again.
- In the Node, host, and cell names panel, specify a unique node
name, the actual host name of the machine, and a unique cell name for the
deployment manager, or accept the defaults, then select Next.
Use a unique name for each deployment manager that you create. See Naming considerations for profiles, nodes, hosts, and cells for information on reserved terms and other
issues you must consider when naming the node, host, and cell.
- In the Port value assignment panel, verify that the ports specified
for the deployment manager are unique, then select Next.
On Windows
platforms: Choose whether to run the server as a Windows service. If the profile is configured as a Windows service, the product starts
Windows services for server deployment manager processes started by a startManager command.
For example, if you configure a deployment manager as a Windows service and
issue the startManager command, the wasservice command starts
the defined service.
To run the server as a Windows service, perform
the following steps:
- Ensure that the Run the WebSphere Process Server process
as a Windows service check box is selected.
- Choose to log on as either a local system account or a specified
user account by selecting the radio button beside the appropriate entry. If you choose to log on as a local system account, you do not have to
specify a user ID or password. If you choose to log on as a specified user
account, you must specify the user ID and the password for the user who is
to run the service, and the startup type (default is Manual). The
user ID must not have spaces in its name, it must belong to the Administrator
group, and it must have the advanced user rights Act as part of the operating
system and Log on as a service. If the user ID belongs to the Administrator
group, the Profile Wizard grants it the advanced user rights if it does not
already have them.
- Select Next.
To not create a Windows service, clear the check box and select Next.
- In the Service Component Architecture
configuration panel, choose whether to configure the Service Integration Bus
in a secured mode. To configure the Service Integration Bus in a secured mode,
perform the following steps:
- Select the Configure the Service Integration Bus in a secured
mode check box.
- Enter the user ID and password, and confirm the password, used
to authenticate with a secured Service Integration Bus.
- Select Next.
To not configure the Service Integration Bus in a secured mode, leave
the check box clear and select Next.
- In the Database configuration
panel, configure database authentication.
Several WebSphere
Process Server components use a database, including:
- Recovery
- Relationship service
- Mediation
- Application Scheduler
- Business rule group
- Selector
The information requested on this and the following panel correctly
configure a new local or existing database for use with these components.
Configure
database authentication by performing the following steps.
- Select to either create a new database or use
an existing one by selecting the appropriate radio button. If
you choose to create a new database, no other database by that same name can
exist or the procedure will fail.
- Choose the database you want to use, or accept the default value
of DB2 Universal.
You can select the following databases
from this panel (each entry that can be selected from the list is shown, followed
by the database it represents):
- DB2 Universal (DB2 Universal Database)
- DB2 Universal OS/390 V7.1 (DB2 Universal Database for OS/390
V7.1)
- DB2 Universal OS/390 V8.1 (DB2 Universal Database for OS/390
V8.1)
- DB2 CLI (DB2 Call Level Interface)
- Informix (Informix Dynamic Server)
- MSSQL Server Embedded (Microsoft SQL Server Embedded)
- MSSQL Server Data Direct (Microsoft SQL Server
DataDirect)
- Oracle OCI (Oracle OCI client)
- Oracle Thin (Oracle Thin)
- Enter your database name or accept the default WPRCSDB.
If the database name WPRCSDB is already associated with another WebSphere
Process Server profile, you must use a different database name.
- Select Next.
One of the following panels is displayed:
- If you select the default value of DB2 Universal, the Additional
database configuration information panel is displayed. Proceed to step 13.
- The business rule group and selector components support only DB2
Universal, DB2 Universal OS/390 V7.1, DB2 Universal OS/390
V8.1, or DB2 CLI for their repository.
In
WebSphere Process Server, version 6.0.1, these components also support Oracle
OCI (Oracle OCI client) and Oracle Thin (Oracle Thin).
If
you select any database other than these, a warning panel is displayed, which
explains this restriction. Proceed to step 12.
Remember: This warning
panel is displayed only the first time you select a database other than these.
If you select Back, select another database other than these, and then
select Next, the warning panel is not displayed.
Restriction: You cannot create a new database if
you are using DB2 Universal OS/390 V7.1, DB2 Universal OS/390
V8.1, Oracle OCI, or Oracle Thin as your database product.
If you select one of these combinations on the Database configuration panel,
a message panel is displayed, informing you that you must either use an existing
database or select a different database product. Select OK to close
this message panel, and make different selections on the Database configuration
panel.
- In the warning
panel, if you intend to use the business rule group and selector components
and you still want to use a database for the other components that the business
rule group and selector components do not support, you have to configure the
repository database for the business rule group and selector components manually. Select OK to keep your selections or Back to return to
the Database configuration panel to change your settings. For information
on configuring the repository database for the business rule group and selector
components manually, see the following topic in this information center: Administering
WebSphere Process Server > Administering applications and application services
> Business rules > Installing the business rules dynamic repository for network
deployment. This procedure assumes you select OK. The
Additional database configuration information panel is displayed, with fields
specific to the database you have selected. (This panel lets you configure
a database for components other than the business rule group and selector
components.)
- Complete the fields in the Additional
database configuration information panel and select Next. The
fields are detailed in Additional database configuration information for common databases.
- In the Profile summary panel,
review the profile characteristics, and select Next to create the profile
or select Back to change the characteristics of the profile.
The Profile Wizard shows a progress panel to indicate that the profile
is being created. If no errors are detected, the Profile creation is complete
panel is displayed at the end of the process.
Attention: If
errors are detected during profile creation, other panels might be displayed
in place of the Profile creation is complete panel. Examples include the following:
- Profile creation is complete with warnings panel, which indicates that
a profile was created but warnings were generated.
- Profile creation is incomplete panel, which indicates that a profile was
created but exists in an unusable state.
- Profile creation failed panel, which indicates that a profile was unable
to be created.
Each of these panels identifies the log file to reference in order to
troubleshoot the problems. Also refer to
Recovering from profile creation or augmentation failure for troubleshooting tips.
- Ensure the check box to launch the First Steps console is selected,
and select Finish to close the Profile Wizard and start the First Steps
console.
Result
A new deployment manager profile exists. The node within the profile
has a deployment manager with the name you specified in step 5.
What to do next
Check server operation by selecting
Start the deployment manager from
the First Steps console. An output window opens. If you see a message similar
to the following, your deployment manager is operating properly:
ADMU3000I: Server dmgr open for e-business; process id is 3072